CN109661835B

CN109661835B - Method for configuring PDCP entity, receiving device and transmitting device

Info

Publication number: CN109661835B
Application number: CN201780054214.9A
Authority: CN
Inventors: 唐海
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-02-23
Filing date: 2017-02-23
Publication date: 2020-06-26
Anticipated expiration: 2037-02-23
Also published as: WO2018152751A1; CN109661835A

Abstract

The application discloses a method for configuring a Packet Data Convergence Protocol (PDCP) entity, a receiving device and a sending device, wherein the method comprises the following steps: the receiving end receives Sequence Number (SN) indication information sent by a first sending end, wherein the SN indication information is used for indicating the SN of the last data protocol unit (PDU) sent to the receiving end by the first sending end by using a first SN length; and when the receiving end receives the PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end so that the receiving end can receive the PDU sent by the first sending end by using the second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity. The receiving end reconfigures the PDCP entity of the receiving end when receiving the last PDU which is sent by the sending end by using the first SN length, so that packet loss in the reconfiguration process of the PDCP entity is avoided.

Description

Method for configuring PDCP entity, receiving device and transmitting device

Technical Field

The embodiment of the application relates to the field of wireless communication, and in particular relates to a method for configuring a Packet Data Convergence Protocol (PDCP) entity, a receiving device and a transmitting device.

Background

In a Long Term Evolution (Long Term Evolution, LTE for short) Packet Data Convergence Protocol (PDCP), a header of a Protocol Data Unit (PDU for short) is mainly composed of a Sequence Number (SN) and used to indicate a specific PDU Sequence to an opposite PDCP entity, so as to ensure that the PDU can be delivered to a higher layer according to a received Sequence. In the existing protocol, SN mainly supports length configuration of 7bits, 12bits, 15bits, 16bits, 18bits and the like. Different length SNs can be used to indicate packets of different traffic sizes, with a longer length SN indicating a greater number of PDUs but a greater corresponding overhead. Such as SN for 7bits, theoretically can support indicating 128 PDUs simultaneously.

However, in some scenarios, for example, when a terminal switches between two base stations or a PDCP entity of the same base station needs to be reconfigured, the length of the SN may change, and if the PDCP entity cannot identify the SN with the changed length, packet loss may result.

For example, when a terminal is handed over between a conventional base station (eNodeB) and a base station supporting Carrier Aggregation (CA), since the SN of the conventional base station is only 12bits and the SN of the base station supporting CA is 15bits, there is a reconfiguration process that the SN is changed from short to long or the SN is changed from long to short when the terminal is handed over between the two base stations. If the PDCP entity of the terminal is reconfigured when the PDUs generated by the original base station are transmitted to the terminal, the PCDP protocol layer of the terminal will not support and the generated PDUs will be discarded. When the terminal device in the LTE system performs such a handover between the original base station and the target base station, the PDCP entity of the terminal is reconfigured immediately after the handover so as to receive the PDU sent by the target base station according to the SN length of the target base station, and the PDU generated in the original base station according to the SN of the original base station is not retransmitted in the newly configured PDCP entity, thereby causing a problem of handover packet loss.

For example, in a non-handover scenario, when the PDCP entity of the same base station needs to be reconfigured, if the SN length is shortened from long to short in the reconfiguration process, the PDCP entity of the terminal cannot identify the PDU sent by the base station using the original SN length after reconfiguration, and thus packet loss may occur in this case as well.

Disclosure of Invention

The embodiment of the application provides a method, a receiving device and a sending device for configuring a Packet Data Convergence Protocol (PDCP) entity, which avoid packet loss in the process of reconfiguring the PDCP entity.

In a first aspect, a method for configuring a packet data convergence protocol PDCP entity is provided, which includes:

a receiving end receives sequence number SN indication information sent by a first sending end, wherein the SN indication information is used for indicating the SN of the last data protocol unit PDU sent to the receiving end by the first sending end by using a first SN length;

and when the receiving end determines to receive the PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end, so that the receiving end can receive the PDU sent by the first sending end by using the second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity.

Therefore, the method for configuring the PDCP entity according to the embodiment of the present application, by receiving the SN of the last PDU sent by the sending end using the first SN length, and performing reconfiguration on the PDCP entity of the receiving end only when receiving the PDU carrying the SN, avoids packet loss during reconfiguration of the PDCP entity.

Optionally, in an implementation manner of the first aspect, before the receiving end receives the SN indication information sent by the first sending end, the method further includes: the receiving end is switched from the first sending end to the second sending end, the SN length of the first sending end for sending the PDU is the first SN length, and the SN length of the second sending end for sending the PDU is the second SN length; wherein the reconfigured PDCP entity of the receiving end is configured to receive the PDU sent by the second sending end using the second SN length.

Optionally, in an implementation manner of the first aspect, before the receiving end receives SN indication information sent by a first sending end, the first sending end reconfigures a PDCP entity of the first sending end, so that after the first sending end sends the last PDU to the receiving end by using the first SN length, the first sending end can send a PDU to the receiving end by using the second SN length through the reconfigured PDCP entity of the first sending end; wherein the reconfigured PDCP entity of the receiving end is used for receiving the PDU transmitted by the first transmitting end by using the second SN length.

Optionally, in an implementation manner of the first aspect, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, where when the receiving end determines to receive the PDU carrying the SN, reconfiguring the PDCP entity of the receiving end includes: and when the receiving end determines to receive the PDU carrying the SN, the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

Optionally, in an implementation manner of the first aspect, the method further includes: and the receiving end sends a reconfiguration completion message to the first sending end.

Optionally, in an implementation manner of the first aspect, the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

In a second aspect, a method for configuring a packet data convergence protocol PDCP entity is provided, which includes:

a first sending end sends sequence number SN indicating information to a receiving end, wherein the SN indicating information is used for indicating the SN of the last PDU sent to the receiving end by the first sending end by using a first SN length, so that the receiving end reconfigures a PDCP entity of the receiving end when determining to receive the PDU carrying the SN.

Therefore, in the method for configuring the PDCP entity of the embodiment of the present application, the sending end sends the SN of the last PDU sent by the sending end with the first SN length to the receiving end through the end, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN, thereby avoiding packet loss during the reconfiguration process of the PDCP entity.

Optionally, in an implementation manner of the second aspect, before the first sending end sends the SN indication information to the receiving end, the method further includes: the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end by the second SN length through the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end by the first SN length; wherein the reconfigured PDCP entity of the receiving end is used for receiving the PDU transmitted by the first transmitting end by using the second SN length.

Optionally, in an implementation manner of the second aspect, before the first sending end sends SN indication information to a receiving end, the receiving end has been switched from the first sending end to the second sending end, where an SN length used by the first sending end to send a PDU is the first SN length, and an SN length used by the second sending end to send a PDU is the second SN length; wherein the reconfigured PDCP entity of the receiving end is configured to receive the PDU sent by the second sending end using the second SN length.

Optionally, in an implementation manner of the second aspect, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, and the receiving end reconfigures the data PDCP entity of the receiving end by invoking a control PDCP entity of the receiving end when receiving the PDU carrying the SN.

Optionally, in an implementation manner of the second aspect, the method further includes: and the first sending end receives the reconfiguration finishing message sent by the receiving end.

Optionally, in an implementation manner of the second aspect, the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

In a third aspect, a receiving apparatus is provided, where the receiving apparatus may perform operations of the receiving end in the first aspect or any optional implementation manner of the first aspect. In particular, the receiving apparatus may include a module unit configured to perform operations of the receiving end in the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, a sending apparatus is provided, which may perform the operations of the sending end in the second aspect or any optional implementation manner of the second aspect. In particular, the transmitting apparatus may include a module unit configured to perform the operations of the transmitting end in the second aspect or any possible implementation manner of the second aspect.

In a fifth aspect, a receiving apparatus is provided, which includes: a processor, a transceiver, and a memory. Wherein the processor, the transceiver and the memory are in communication with each other via an internal connection path. The memory is configured to store instructions and the processor is configured to execute the instructions stored by the memory. When the processor executes the instructions stored by the memory, the execution causes the receiving apparatus to perform the method of the first aspect or any possible implementation manner of the first aspect, or the execution causes the receiving apparatus to implement the receiving apparatus provided by the third aspect.

In a sixth aspect, there is provided a transmission apparatus including: a processor, a transceiver, and a memory. Wherein the processor, the transceiver and the memory are in communication with each other via an internal connection path. The memory is configured to store instructions and the processor is configured to execute the instructions stored by the memory. When the processor executes the instructions stored by the memory, the execution causes the transmitting apparatus to perform the method of the second aspect or any possible implementation manner of the second aspect, or the execution causes the transmitting apparatus to implement the transmitting apparatus provided by the fourth aspect.

In a seventh aspect, a computer-readable storage medium is provided, which stores a program for causing a receiving apparatus to execute the method for configuring a PDCP entity according to the first aspect and any of its various implementations.

In an eighth aspect, there is provided a computer-readable storage medium storing a program for causing a transmitting apparatus to execute the second aspect described above and any of its various implementations to configure a PDCP entity.

In a ninth aspect, there is provided a system-on-chip comprising an input interface, an output interface, a processor and a memory, the sharer being configured to execute instructions stored in the memory, the processor being configured to implement the method of any one of the preceding first aspect and its various implementations when the instructions are executed.

In a tenth aspect, there is provided a system-on-chip comprising an input interface, an output interface, a processor and a memory, the sharer being configured to execute instructions stored by the memory, the processor being configured to implement any of the methods of the foregoing second aspect and its various implementations when the instructions are executed.

In an eleventh aspect, a method for configuring a packet data convergence protocol PDCP entity is provided, which includes:

a receiving end receives sequence number SN indication information and a trigger instruction sent by a sending end, wherein the SN indication information is used for indicating the SN of the last data protocol unit PDU sent to the receiving end by the first sending end by using a first SN length, and the trigger instruction is used for indicating the receiving end to start a reconfiguration timer;

the receiving end starts the reconfiguration timer according to the trigger instruction and determines whether the PDU carrying the SN is received before the reconfiguration timer is overtime according to the SN indication information;

if the receiving end receives the PDU carrying the SN before the reconfiguration timer is overtime, the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN, or

If the receiving end does not receive the PDU carrying the SN before the reconfiguration timer is overtime, the receiving end reconfigures the PDCP entity of the receiving end when the reconfiguration timer is overtime, so that the receiving end can receive the PDU sent by the first sending end by using the second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity.

Therefore, in the method for configuring the PDCP entity according to the embodiment of the present application, the receiving end receives the SN of the last PDU sent by the sending end with the first SN length and starts the reconfiguration timer, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN or when the timer is overtime, thereby receiving the PDU sent by the sending end or other sending ends with the second SN length, reducing packet loss in the reconfiguration process of the PDCP entity by the receiving end, and preventing too long time delay caused when the receiving end receives the PDU sent by the sending end with the first SN length, so that the receiving end can receive the generated PDU sent by the sending end with the first SN length as much as possible within the preset time length of the configuration timer.

Optionally, in an implementation manner of the eleventh aspect, before the receiving end receives the SN indication information and the trigger instruction sent by the first sending end, the method further includes:

the receiving end is switched from the first sending end to the second sending end, the SN length of the first sending end for sending the PDU is the first SN length, and the SN length of the second sending end for sending the PDU is the second SN length;

wherein the reconfigured PDCP entity of the receiving end is configured to receive the PDU sent by the second sending end using the second SN length.

Optionally, in an implementation manner of the eleventh aspect, before the receiving end receives the sequence number SN indication information and the trigger instruction sent by the first sending end, the first sending end reconfigures the PDCP entity of the first sending end, so that after the first sending end sends the last PDU to the receiving end by using the first SN length, the first sending end can send a PDU to the receiving end by using the second SN length through the reconfigured PDCP entity of the first sending end;

wherein the reconfigured PDCP entity of the receiving end is used for receiving the PDU transmitted by the first transmitting end by using the second SN length.

Optionally, in an implementation manner of the eleventh aspect, before the receiving end receives the SN indication information and the trigger instruction sent by the sending end, the method further includes: and the receiving end receives a high-level signaling sent by the first sending end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

Optionally, in an implementation manner of the eleventh aspect, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, where the reconfiguring, by the receiving end, the PDCP entity of the receiving end includes: and the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

Optionally, in an implementation manner of the eleventh aspect, the method further includes: and the receiving end sends the reconfiguration completion message to the first sending end.

Optionally, in an implementation manner of the eleventh aspect, the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

In a twelfth aspect, a method for configuring a packet data convergence protocol PDCP entity is provided, which includes:

a first sending end sends Sequence Number (SN) indication information and a trigger instruction to a receiving end, wherein the SN indication information is used for indicating the SN of the last data protocol unit (PDU) sent to the receiving end by the first sending end by using a first SN length, and the trigger instruction is used for indicating the receiving end to start a reconfiguration timer, so that the receiving end reconfigures a PDCP entity of the receiving end when receiving the PDU carrying the SN or the reconfiguration timer is overtime.

Therefore, in the method for configuring a PDCP entity according to the embodiment of the present application, the sending end sends, to the receiving end, the SN of the last PDU sent by using the first SN length through the end, and instructs the receiving end to start the reconfiguration timer, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN or when the timer is overtime, thereby receiving the PDU sent by the sending end or other sending ends using the second SN length, reducing packet loss during reconfiguration of the PDCP entity by the receiving end, and preventing too long delay caused when the receiving end receives the PDU sent by the sending end using the first SN length, so that the receiving end can receive the generated PDU sent by the sending end using the first SN length as much as possible within the preset duration of the configuration timer.

Optionally, in an implementation manner of the twelfth aspect, before the first sending end sends the sequence number SN indication information and the trigger instruction to the receiving end, the method further includes: the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end by the second SN length through the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end by the first SN length;

Optionally, in an implementation manner of the twelfth aspect, before the first sending end sends sequence number SN indication information and a trigger instruction to a receiving end, the receiving end has switched from the first sending end to the second sending end, where an SN length used by the first sending end to send a PDU is the first SN length, and an SN length used by the second sending end to send a PDU is the second SN length;

Optionally, in an implementation manner of the twelfth aspect, before the first sending end sends SN indication information and a trigger instruction to a receiving end, the method further includes: and the first sending end sends a high-level signaling to the receiving end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

Optionally, in an implementation manner of the twelfth aspect, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, and the receiving end reconfigures the data PDCP entity of the receiving end by invoking the control PDCP entity of the receiving end when receiving the PDU carrying the SN or when the reconfiguration timer expires.

Optionally, in an implementation manner of the twelfth aspect, the method further includes: and the first sending end receives the reconfiguration finishing message sent by the receiving end.

Optionally, in an implementation manner of the twelfth aspect, the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

In a thirteenth aspect, a receiving apparatus is provided, which can perform the operations of the receiving end in the above eleventh aspect or any optional implementation manner of the eleventh aspect. In particular, the receiving apparatus may include a module unit for performing the operation of the receiving end in the eleventh aspect or any possible implementation manner of the eleventh aspect.

In a fourteenth aspect, a transmitting apparatus is provided, which may perform the operations of the transmitting end in the above twelfth aspect or any optional implementation manner of the twelfth aspect. In particular, the transmitting apparatus may include a module unit configured to perform the operations of the transmitting end in the twelfth aspect or any possible implementation manner of the twelfth aspect.

In a fifteenth aspect, a receiving apparatus is provided, which includes: a processor, a transceiver, and a memory. Wherein the processor, the transceiver and the memory are in communication with each other via an internal connection path. The memory is configured to store instructions and the processor is configured to execute the instructions stored by the memory. When the processor executes the instructions stored by the memory, the execution causes the receiving apparatus to perform the method of the eleventh aspect or any possible implementation manner of the eleventh aspect, or the execution causes the receiving apparatus to implement the receiving apparatus provided by the thirteenth aspect.

In a sixteenth aspect, there is provided a transmission apparatus including: a processor, a transceiver, and a memory. Wherein the processor, the transceiver and the memory are in communication with each other via an internal connection path. The memory is configured to store instructions and the processor is configured to execute the instructions stored by the memory. When the processor executes the instructions stored in the memory, the execution causes the transmitting apparatus to execute the method of the twelfth aspect or any possible implementation manner of the twelfth aspect, or the execution causes the transmitting apparatus to implement the transmitting apparatus provided by the fourteenth aspect.

In a seventeenth aspect, there is provided a computer-readable storage medium storing a program for causing a receiving apparatus to execute the method of configuring a PDCP entity of the eleventh aspect and any of its various implementations.

In an eighteenth aspect, there is provided a computer readable storage medium storing a program for causing a transmitting apparatus to execute the twelfth aspect described above and any of its various implementations of the method for configuring a PDCP entity.

In a nineteenth aspect, there is provided a system chip comprising an input interface, an output interface, a processor and a memory, the sharer being configured to execute instructions stored in the memory, the instructions when executed, the processor being configured to implement any of the methods of the eleventh aspect and its various implementations.

In a twentieth aspect, there is provided a system-on-chip comprising an input interface, an output interface, a processor and a memory, the sharer being configured to execute instructions stored in the memory, the processor being configured to implement the method of the twelfth aspect and any of its various implementations when the instructions are executed.

Drawings

Fig. 1 is a schematic architecture diagram of an application scenario according to an embodiment of the present application.

Fig. 2 is a flowchart of a method for configuring a PDCP entity according to an embodiment of the present application.

Fig. 3 is a flowchart of a method for configuring a PDCP entity according to an embodiment of the present application.

Fig. 4 is a flowchart of a method for configuring a PDCP entity according to another embodiment of the present application.

Fig. 5 is a flowchart of a method for configuring a PDCP entity according to another embodiment of the present application.

Fig. 6 is a schematic block diagram of a receiving apparatus according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a transmitting apparatus according to an embodiment of the present application.

Fig. 8 is a schematic configuration diagram of a receiving apparatus according to an embodiment of the present application.

Fig. 9 is a schematic configuration diagram of a transmission device according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a receiving apparatus of another embodiment of the present application.

Fig. 11 is a schematic block diagram of a transmitting apparatus according to another embodiment of the present application.

Fig. 12 is a schematic configuration diagram of a receiving apparatus according to another embodiment of the present application.

Fig. 13 is a schematic configuration diagram of a transmitting apparatus according to another embodiment of the present application.

Fig. 14 is a schematic structural diagram of a system chip according to an embodiment of the present application.

Fig. 15 is a schematic structural diagram of a system chip of another embodiment of the present application.

Detailed Description

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

It should be understood that the technical solutions of the embodiments of the present application may be applied to various communication systems, for example: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, Long Term Evolution (LTE) System, LTE Frequency Division Duplex (FDD) System, LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), and future 5G Communication System.

Various embodiments are described herein in connection with a terminal device. Terminal equipment may also refer to User Equipment (UE), an access terminal, 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 device. The access terminal 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 or a terminal device in a future evolved PLMN network, etc.

Various embodiments are described herein in connection with a network device. The network device may be a device for communicating with the terminal device, and for example, the network device may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB) in an LTE system, or an eNodeB, or the network device may be a relay Station, an access point, a vehicle-mounted device, a wearable device, a network-side device in a future 5G network, or a network-side device in a future evolved PLMN network.

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application. The communication system in fig. 1 may include a network device 10, a network device 20, and a terminal device 30. Network device 10 and network device 20 may each be configured to provide communication services to terminal device 30. The arrows shown by solid lines in fig. 1 may represent uplink/downlink transmissions over the cellular link between terminal device 30 and network device 10, and the arrows shown by dashed lines in fig. 1 may represent uplink/downlink transmissions over the cellular link between terminal device 30 and network device 20.

Terminal device 30 may perform a connection handover between network device 10 and network device 20, e.g., terminal device 30 receives PDUs transmitted by network device 10 before the handover and terminal device 30 receives PDUs transmitted by network device 20 after the handover. Assuming that the SN length supported by the network device 10 is different from the SN length supported by the network device 20, the terminal device 30 has a reconfiguration process in which the SN is changed from a short length to a long length or from a long length to a short length when switching between the network device 10 and the network device 20. When the PDUs already generated by the network device 10 are transmitted to the terminal device 30, if the PDCP entity of the terminal device 30 has been reconfigured, the PDCP protocol layer of the terminal device 30 will not support it, and therefore these generated PDUs will be discarded.

For example, in a non-handover scenario, when the PDCP entity of the same base station needs to be reconfigured, for example, when the PDCP entity of the network device 10 communicating with the terminal device 30 needs to be reconfigured, if the length of the SN is changed from long to short or from short to long in the reconfiguration process, the PDCP entity of the terminal device 30 cannot identify the PDU sent by the network device 10 using the original SN length after reconfiguration, so that packet loss may occur in this case as well.

In the embodiment of the application, the sending end sends the SN of the last PDU sent by the sending end by using the first SN length to the receiving end, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN, and packet loss in the reconfiguration process of the PDCP entity is avoided.

It should be understood that the Network in the embodiment of the present application may refer to a Public Land Mobile Network (PLMN), a Device to Device (D2D), a Machine to Machine/Man (M2M), or other networks, and fig. 1 is a simplified schematic diagram of an example, and the Network may further include other Network devices or terminal devices, which are not shown in fig. 1.

Fig. 2 is a flowchart of a method 200 for configuring a PDCP entity according to an embodiment of the present application. The receiving end in the method 200 may be a terminal device, and the transmitting end is a network device; or the receiving end is network equipment and the sending end is terminal equipment. In the embodiment of the present application, only the receiving end is taken as a terminal device, and the sending end is taken as a network device for example. As shown in fig. 2, the specific procedure of reconfiguring the packet data convergence protocol PDCP entity includes:

in 210, the first transmitting end transmits SN indication information to the receiving end.

In 220, the receiving end receives the SN indication information sent by the first sending end.

Wherein the SN indication information in 210 and 220 is used to indicate the SN of the last PDU that the first transmitting end transmits to the receiving end using the first SN length.

In 230, when the receiving end receives the PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end, so that the receiving end can receive the PDU sent by the first sending end using the second SN length or the PDU sent by the second sending end using the second SN length.

Specifically, after receiving the SN indication information sent by the first sending end, the receiving end determines whether it receives the PDU carrying the SN according to the SN indicated by the indication information, and when receiving the PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end, thereby receiving the PDU with the second SN length used by the first sending end or the second sending end. Here, the PDCP entity at the receiving end supports a first SN length before the reconfiguration, and the PDCP entity at the receiving end supports a second SN length after the reconfiguration, so that it can receive PDUs transmitted using the second SN length.

Optionally, in 210, before the first sending end sends the SN indication information to the receiving end, the method further includes: the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end by using the second SN length through the reconfigured PDCP entity after sending the last PDU to the receiving end by using the first SN length; wherein the PDCP entity of the receiving end reconfigured in 230 is configured to receive the PDUs transmitted by the first transmitting end using the second SN length.

Specifically, when the first transmitting end PDCP entity needs to be reconfigured, the SN length is shortened or shortened, the first transmitting end transmits the PDU to the receiving end using the first SN length before the PDCP entity reconfiguration, after the PDCP entity reconfiguration, the first transmitting end transmits the PDU to the receiving end by using the second SN length, and simultaneously, the first transmitting end transmits the SN indication information to the receiving end, the SN indication information indicates the SN of the last PDU sent by the first sending end to the receiving end by using the first SN length, the receiving end reconfigures the PDCP entity of the receiving end when receiving the last PDU sent by the first sending end by using the first SN length, so that in case it is guaranteed that the generated PDU transmitted by the first transmitting end using the first SN length is received, the PDU sent by the first sender with the second SN length is received, thereby avoiding packet loss.

Optionally, in 220, before the receiving end receives the SN indication information sent by the first sending end, the method further includes: the receiving end is switched from a first sending end to a second sending end, the SN length of the first sending end for sending the PDU is a first SN length, and the SN length of the second sending end for sending the PDU is a second SN length; wherein the reconfigured PDCP entity of the receiving end in 230 is configured to receive the PDUs transmitted by the second transmitting end using the second SN length.

Specifically, after the receiving end switches between the transmitting ends, for example, after the terminal device switches from the first network device to the second network device, because the SN length (first SN length) used by the first network device to transmit the PDU is different from the SN length (second SN length) used by the second network device to transmit the PDU, the terminal device needs to reconfigure the PDCP entity of the terminal device, so that the PDCP entity of the terminal device can support the second SN length used by the second network device after the switching, and thus receive, by using the configured PDCP entity, the PDU sent by the second network device using the second SN length.

At this time, the terminal device determines whether it receives the last PDU sent by the first network device with the first SN length according to the SN indication information received from the first network device, and the terminal device reconfigures the PDCP entity when it receives the last PDU sent by the first network device with the first SN length, so as to receive the PDU sent by the second network device only when it is ensured that the PDU generated by the first network device is received, thereby avoiding packet loss.

Generally, only one PDCP entity may be in the receiving end or the transmitting end, and the PDCP entity may be configured to transmit control PDUs and data PDUs, where control information is carried by the control PDUs; the PCDP entity in the receiving end or the transmitting end may include a control PDCP entity for transmitting control class PDUs and a data PDCP entity for transmitting data class PDUs.

Optionally, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, wherein when the receiving end receives the PDU carrying the SN, reconfiguring the PDCP entity of the receiving end includes: when receiving PDU carrying SN, the receiving end carries out reconfiguration to the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

For example, if the receiving end includes two PDCP entities, namely, a control PDCP entity and a data PDCP entity, and the transmitting end also includes two PDCP entities, as shown in fig. 3, which is a flow interaction diagram of the method for configuring a PDCP entity in the embodiment of the present application, the receiving end reconfigures the data PDCP entity of the receiving end by invoking the control PDCP entity of the receiving end when reconfiguring the PDCP entity of the receiving end. Fig. 3 includes a first network device and a terminal device, as shown in fig. 3:

in 310, the network device reconfigures a data PDCP entity of the network device by invoking a control PDCP entity of the network device.

Fig. 3 illustrates a non-handover scenario, in which a first network device performs reconfiguration of a data PDCP entity after sending a PDU to a terminal device using a first SN length, so that the PDU continues to be sent to the terminal device using a second SN length after reconfiguration.

In 320, the control PDCP entity of the network device sends SN indication information to the control PDCP entity of the terminal device, the SN indication information indicating a SN of a last PDU sent by the first network device to the terminal device using the first SN length.

In 330, the control PDCP entity of the terminal device receives the SN indication information, so as to know the SN of the last PDU sent by the first network device to the terminal device using the first SN length.

In 340, when the control PDCP entity of the terminal device receives the PDU carrying the SN, the terminal device reconfigures the data PDCP entity of the terminal device through the control PDCP entity, so that the terminal device can receive the PDU sent by the first network device with the second SN length.

In 350, the control PDCP entity of the terminal device sends a reconfiguration complete message to the control PDCP entity of the first network device for feedback after the data PDCP entity completes reconfiguration.

Optionally, after 230, the method further comprises: the receiving end sends a reconfiguration complete message to the first sending end.

Therefore, in the method for configuring the PDCP entity of the embodiment of the present application, the sending end sends the SN of the last PDU sent by the sending end with the first SN length to the receiving end, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN, thereby avoiding packet loss during the reconfiguration process of the PDCP entity.

In the above embodiment, before receiving the PDU sent by the first sender or the second sender with the second SN length, the receiver must first receive all the PDUs sent by the first sender with the first SN. However, in order to prevent the receiving end from causing too long time delay when receiving the PDU transmitted by the first transmitting end using the first SN length, a configuration timer may be set at the receiving end, so that the receiving end receives the PDU transmitted by the first transmitting end using the first SN length within a preset duration of the timer "as much as possible". A method for configuring a PDCP entity according to another embodiment of the present application is described below with reference to fig. 4 and 5.

Fig. 4 is a flowchart of an interaction of a method 400 for configuring a PDCP entity according to an embodiment of the present application. In the method 400, a receiving end may be a terminal device and a transmitting end is a network device; or the receiving end is network equipment and the sending end is terminal equipment. In the embodiment of the present application, only the receiving end is taken as a terminal device, and the sending end is taken as a network device for example. As shown in fig. 4, the specific procedure of reconfiguring the packet data convergence protocol PDCP entity includes:

in 410, the first sending end sends the SN indication information and the trigger instruction to the receiving end.

The SN indication information is used to indicate that the first sending end uses the SN of the last data protocol unit PDU sent by the first SN length to the receiving end, and the trigger instruction is used to indicate the receiving end to start the reconfiguration timer.

It should be understood that the first sending end may send the SN indication information and the trigger instruction to the receiving end simultaneously, or may send the SN indication information and the trigger instruction separately.

Optionally, before the sending end executes 410, that is, before the first sending end sends the SN indication information and the trigger instruction to the receiving end, the method further includes: and the first sending end sends a high-level signaling to the receiving end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

In 420, the receiving end receives the SN indication information and the trigger command of the sequence number sent by the sending end.

Optionally, before the receiving end performs 420, that is, before the receiving end receives the SN indication information and the trigger instruction sent by the sending end, the method further includes: and the receiving end receives a high-level signaling sent by the first sending end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

In 430, the receiving end starts the reconfiguration timer according to the trigger instruction, and determines whether to receive the PDU carrying the SN before the reconfiguration timer times out according to the SN indication information.

If the receiving end receives the PDU carrying the SN before the reconfiguration timer times out, 440 is executed, and if the receiving end does not receive the PDU carrying the SN before the reconfiguration timer times out, 450 is executed.

In 440, if the receiving end receives the PDU carrying the SN before the reconfiguration timer expires, the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN.

In 450, if the receiving end does not receive the PDU carrying the SN before the reconfiguration timer expires, the receiving end reconfigures the PDCP entity of the receiving end when the reconfiguration timer expires.

Specifically, after receiving the SN indication information and the trigger instruction sent by the first sending end, the receiving end starts the reconfiguration timer and obtains the SN of the last PDU sent by the first sending end using the first SN, thereby determining whether the receiving end receives the PDU carrying the SN before the configuration timer times out. If the receiving end receives the PDU carrying the SN before the configuration timer is overtime, the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN; if the receiving end does not receive the PDU carrying the SN before the configuration timer is overtime, the receiving end reconfigures the PDCP entity of the receiving end when the configuration timer is overtime. Here, the PDCP entity at the receiving end supports a first SN length before the reconfiguration, and the PDCP entity at the receiving end supports a second SN length after the reconfiguration, so that the PDU sent by the first sending end or the second sending end using the second SN length can be received.

Optionally, in 410, before the first sending end sends the sequence number SN indication information and the trigger instruction to the receiving end, the method further includes: the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end by using the second SN length through the reconfigured PDCP entity after sending the last PDU to the receiving end by using the first SN length; wherein, the PDCP entity of the receiving end reconfigured in 440 or 450 is configured to receive the PDUs transmitted by the first transmitting end using the second SN length.

Specifically, when the PDCP entity of the first sending end needs to be reconfigured, the SN length is shortened or shortened, the first sending end sends a PDU to the receiving end using the first SN length before the PDCP entity is reconfigured, and then sends a PDU to the receiving end using the second SN length after the PDCP entity is reconfigured, meanwhile, the first sending end sends SN indication information and a trigger instruction to the receiving end, where the SN indication information indicates the SN of the last PDU sent by the first sending end to the receiving end using the first SN length, and the trigger instruction is used to indicate the receiving end to start a reconfiguration timer, and the receiving end starts the reconfiguration timer according to the trigger instruction and determines whether to receive the SN indication information before the timer expires.

When the receiving end receives the last PDU sent by the first sending end by using the first SN length before the timer is overtime, the PDCP entity of the receiving end is reconfigured when the PDU is received, so that the PDU sent by the first sending end by using the second SN length is received only when the generated PDU sent by the first sending end by using the first SN length is received, and packet loss is avoided.

The receiving end does not receive the last PDU which is sent by the first sending end by using the first SN length before the timer is overtime, the PDCP entity of the receiving end is reconfigured when the timer is overtime, the phenomenon that the time delay caused when the receiving end receives the PDU which is sent by the first sending end by using the first SN length is overlong is prevented, the receiving end can receive the generated PDU which is sent by the first sending end by using the first SN length as much as possible within the preset time length of the timer, and the occurrence of packet loss is reduced.

Optionally, in 420, before the receiving end receives the SN indication information and the trigger instruction sent by the first sending end, the method further includes: the receiving end is switched from a first sending end to a second sending end, the SN length of the first sending end for sending the PDU is a first SN length, and the SN length of the second sending end for sending the PDU is a second SN length; wherein, the PDCP entity of the receiving end reconfigured in 440 or 405 is configured to receive the PDUs transmitted by the second transmitting end using the second SN length.

Specifically, after the receiving end switches between the transmitting ends, for example, after switching from the first transmitting end to the second transmitting end, because the SN length (first SN length) used by the first transmitting end to transmit the PDU is different from the SN length (second SN length) used by the second transmitting end to transmit the PDU, the receiving end needs to reconfigure the PDCP entity of the receiving end so that the PDCP entity of the receiving end can support the second SN length used by the second transmitting end after switching, and thus receive the PDU transmitted by the second transmitting end using the second SN length through the configured PDCP entity.

At this time, the receiving end starts its own reconfiguration timer according to the trigger instruction received from the first sending end, and determines whether the last PDU sent by the first sending end with the first SN length is received before the configuration timer expires according to the SN indication information received from the first sending end.

When the receiving end receives the last PDU sent by the first sending end by using the first SN length before the timer is overtime, the PDCP entity of the receiving end is reconfigured when the PDU is received, and the PDCP entity is reconfigured, so that the PDU sent by the second sending end by using the second SN length is received only when the generated PDU sent by the first sending end by using the first SN length is received, and packet loss is avoided.

The receiving end does not receive the last PDU which is sent by the first sending end by using the first SN length before the timer is overtime, the PDCP entity of the receiving end is reconfigured when the timer is overtime, the phenomenon that the time delay caused when the receiving end receives the PDU which is sent by the first sending end by using the first SN length is overlong is prevented, the receiving end can receive the generated PDU which is sent by the first sending end by using the first SN length as much as possible within the preset time length of the timer, and the packet loss is reduced.

Only one PDCP entity can be arranged in a receiving end or a transmitting end, and the PDCP entity can be used for transmitting control PDU and data PDU; the PCDP entity in the receiving end or the transmitting end may also include a control PDCP entity and a data PDCP entity, where the control PDCP entity is configured to send a control PDU and the data PDCP entity is configured to send a data PDU.

Optionally, the PDCP entity of the receiving end is a data PDCP entity of the receiving end, wherein in 440 or 450, the reconfiguring, by the receiving end, the PDCP entity of the receiving end includes: the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

For example, if the receiving end includes two PDCP entities, namely, a control PDCP entity and a data PDCP entity, and the transmitting end also includes two PDCP entities, as shown in fig. 5, in the method for configuring a PDCP entity in the embodiment of the present application, the receiving end performs reconfiguration on the data PDCP entity of the receiving end by invoking the control PDCP entity of the receiving end when performing reconfiguration on the PDCP entity of the receiving end. The first network device and the terminal device are shown in fig. 5, as shown in fig. 5:

at 510, the network device reconfigures a data PDCP entity of the network device by invoking a control PDCP entity of the network device.

Fig. 5 illustrates a non-handover scenario, in which the first network device performs reconfiguration of the data PDCP entity after sending the PDU to the terminal device using the first SN length, so that the PDU is sent to the terminal device using the second SN length after reconfiguration.

In 520, the control PDCP entity of the network device sends, to the control PDCP entity of the terminal device, SN indication information and a trigger instruction, where the SN indication information is used to indicate a SN of a last PDU sent by the first network device to the terminal device by using the first SN length, and the trigger instruction is used to indicate the terminal device to start a reconfiguration timer.

In 530, the controlling PDCP entity of the terminal device receives the SN indication information and the trigger instruction.

The terminal device learns the SN of the last PDU sent by the first network device to the terminal device by using the first SN length according to the SN indication information, and starts the reconfiguration timer according to the trigger instruction, that is, executes 540.

In 540, the terminal device starts a reconfiguration timer.

If the terminal equipment receives the PDU carrying the SN before the reconfiguration timer is overtime, executing 550, and if the terminal equipment does not receive the PDU carrying the SN before the reconfiguration timer is overtime, executing 560.

In 550, when receiving the PDU carrying the SN, the terminal device reconfigures the PDCP entity of the terminal device.

In 560, the terminal device reconfigures the PDCP entity of the terminal device when the reconfiguration timer expires.

In 570, the control PDCP entity of the terminal device sends a reconfiguration complete message to the control PDCP entity of the first network device for feedback after the data PDCP entity completes reconfiguration.

Optionally, after 440 or 450, the method further comprises: the receiving end sends a reconfiguration complete message to the first sending end.

Therefore, in the method for configuring a PDCP entity according to the embodiment of the present application, the sending end sends the SN of the last PDU sent by the sending end with the first SN length to the receiving end, and instructs the receiving end to start the reconfiguration timer, so that the receiving end reconfigures the PDCP entity of the receiving end only when receiving the PDU carrying the SN or when the timer is overtime, thereby receiving the PDU sent by the sending end or other sending ends with the second SN length, reducing packet loss during reconfiguration of the PDCP entity by the receiving end, preventing an excessively long time delay caused when the receiving end receives the PDU sent by the sending end with the first SN length, and enabling the receiving end to receive the generated PDU sent by the sending end with the first SN length as much as possible within the preset time length of the configuration timer.

Fig. 6 is a schematic block diagram of a receiving apparatus 600 according to an embodiment of the present application. As shown in fig. 6, the receiving apparatus 600 includes a receiving unit 610 and a processing unit 620. Wherein:

a receiving unit 610, configured to receive SN indication information of a sequence number SN sent by a first sending apparatus, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send an SN of a last data protocol unit PDU to the receiving apparatus;

a processing unit 620, configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

Therefore, the receiving apparatus in the embodiment of the present application, by receiving the SN of the last PDU sent by the sending apparatus using the first SN length and receiving the PDU carrying the SN, reconfigures the PDCP entity of the receiving apparatus, so as to avoid packet loss during the reconfiguration process of the PDCP entity.

Optionally, the processing unit 620 is further configured to: before the receiving unit 610 receives SN indication information sent by a first sending apparatus, switching from the first sending apparatus to the second sending apparatus, where an SN length used for sending a PDU is the first SN length, and an SN length used for sending a PDU is the second SN length;

wherein the reconfigured PDCP entity of the receiving apparatus is used to receive the PDU transmitted by the second transmitting apparatus using the second SN length.

Optionally, before the receiving unit 610 receives the SN indication information sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that after the first sending apparatus sends the last PDU to the receiving apparatus by using the first SN length, the first sending apparatus can send a PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus;

wherein the reconfigured PDCP entity of the receiving apparatus is used to receive the PDU transmitted by the first transmitting apparatus using the second SN length.

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processing unit 620 is specifically configured to: and when receiving the PDU carrying the SN, reconfiguring a data PDCP entity of the receiving device by calling a control PDCP entity of the receiving device.

Optionally, the receiving apparatus further includes a sending unit, where the sending unit is configured to: sending a reconfiguration complete message to the first sending device.

Optionally, the receiving apparatus is a terminal device, and the first sending apparatus is a network device; or the receiving device is a network device, and the first transmitting device is a terminal device.

It should be understood that the receiving apparatus 600 may correspond to a receiving end in the method embodiment, and may implement corresponding functions of the receiving end, which is not described herein again for brevity.

Fig. 7 is a schematic block diagram of a transmitting apparatus 700 according to an embodiment of the present application. As shown in fig. 7, the transmitting apparatus 700 includes a transmitting unit 710, where the transmitting unit 710 is configured to:

and sending Sequence Number (SN) indication information to a receiving device, wherein the SN indication information is used for indicating that the first sending device uses a first SN length to send the SN of the last PDU to the receiving device, so that the receiving device reconfigures a PDCP entity of the receiving device when receiving the PDU carrying the SN.

Therefore, the sending apparatus in the embodiment of the present application, by sending the SN indicating that the sending apparatus uses the last PDU sent by the first SN length to the receiving apparatus, enables the receiving apparatus to reconfigure the PDCP entity of the receiving apparatus only when receiving the PDU carrying the SN, thereby avoiding packet loss during reconfiguration of the PDCP entity.

Optionally, the first sending apparatus further comprises a processing unit 720, and the processing unit 720 is configured to: before the sending unit 710 sends the SN indication information of the sequence number to the receiving apparatus, reconfiguring the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, before the sending unit 710 sends the SN indication information to the receiving apparatus, the receiving apparatus has switched from the first sending apparatus to the second sending apparatus, the SN length of the first sending apparatus for sending the PDU is the first SN length, and the SN length of the second sending apparatus for sending the PDU is the second SN length;

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, and when the receiving apparatus receives the PDU carrying the SN, the receiving apparatus reconfigures the data PDCP entity of the receiving apparatus by invoking the control PDCP entity of the receiving apparatus.

Optionally, the first sending apparatus further includes a receiving unit, where the receiving unit is configured to: and receiving the reconfiguration completion message sent by the receiving device.

It should be understood that the receiving apparatus 700 may correspond to a receiving end in the method embodiment, and the corresponding functions of the receiving end may be implemented, which are not described herein again for brevity.

Fig. 8 is a schematic configuration diagram of a receiving apparatus 800 according to an embodiment of the present application. As shown in fig. 8, the receiving device includes a processor 810, a transceiver 820 and a memory 830, wherein the processor 810, the transceiver 820 and the memory 830 communicate with each other through an internal connection path. The memory 830 is used for storing instructions, and the processor 810 is used for executing the instructions stored in the memory 830 to control the transceiver 820 to receive signals or transmit signals. Wherein the content of the first and second substances,

a transceiver 820, configured to receive SN indication information of a sequence number, SN, sent by a first sending apparatus, where the SN indication information is used to indicate an SN of a last data protocol unit, PDU, sent by the first sending apparatus to the receiving apparatus by using a first SN length;

a processor 810, configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

Optionally, the processor 810 is further configured to: before the transceiver 820 receives the SN indication information sent by the first sending apparatus, switching from the first sending apparatus to the second sending apparatus, where the SN length of the first sending apparatus for sending the PDU is the first SN length, and the SN length of the second sending apparatus for sending the PDU is the second SN length;

Optionally, before the transceiver 820 receives the SN indication information sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processor 810 is specifically configured to: and when receiving the PDU carrying the SN, reconfiguring a data PDCP entity of the receiving device by calling a control PDCP entity of the receiving device.

Optionally, the transceiver 820 is configured to: sending a reconfiguration complete message to the first sending device.

It should be understood that, in the embodiment of the present application, the processor 810 may be a Central Processing Unit (CPU), and the processor 810 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 830 may include both read-only memory and random access memory and provides instructions and data to the processor 810. A portion of memory 830 may also include non-volatile random access memory. For example, memory 830 may also store device type information.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 810. The steps of the positioning method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor 810. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 830, and the processor 810 reads the information in the memory 830 and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The receiving apparatus 800 according to the embodiment of the present application may correspond to the receiving end for executing the method 200 in the method 200 and the receiving end 600 according to the embodiment of the present application, and each unit or module in the receiving apparatus 800 is respectively configured to execute each action or processing procedure executed by the receiving end in the method 200, and a detailed description thereof is omitted here for avoiding redundancy.

Fig. 9 is a schematic configuration diagram of a receiving apparatus 900 according to an embodiment of the present application. As shown in fig. 9, the receiving device includes a processor 910, a transceiver 920 and a memory 930, wherein the processor 910, the transceiver 920 and the memory 930 are communicated with each other through an internal connection path. The memory 930 is used for storing instructions, and the processor 910 is used for executing the instructions stored in the memory 930 to control the transceiver 920 to receive signals or transmit signals. Wherein, the transceiver 920 is specifically configured to:

Optionally, the processor 910 is configured to: before the transceiver 920 sends the SN indication information to the receiving apparatus, reconfiguring the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus with the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus with the first SN length;

Optionally, before the transceiver 920 sends SN indication information to a receiving apparatus, the receiving apparatus has switched from the first sending apparatus to the second sending apparatus, the SN length of the first sending apparatus for sending PDUs is the first SN length, and the SN length of the second sending apparatus for sending PDUs is the second SN length;

Optionally, the transceiver 920 is configured to: and receiving the reconfiguration completion message sent by the receiving device.

It should be understood that, in the embodiment of the present application, the processor 910 may be a Central Processing Unit (CPU), and the processor 910 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 930 may include both read-only memory and random access memory and provides instructions and data to the processor 910. A portion of the memory 930 may also include non-volatile random access memory. For example, the memory 930 may also store device type information.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 910. The steps of the positioning method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor 910. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 930, and the processor 910 reads the information in the memory 930, and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The receiving apparatus 900 according to the embodiment of the present application may correspond to the transmitting end used for executing the method 200 in the method 200 and the transmitting end 700 according to the embodiment of the present application, and each unit or module in the receiving apparatus 900 is respectively configured to execute each action or processing procedure executed by the transmitting end in the method 200, and here, detailed descriptions thereof are omitted to avoid redundancy.

Fig. 10 is a schematic block diagram of a receiving apparatus 1000 according to an embodiment of the present application. As shown in fig. 10, the receiving apparatus 1000 includes a receiving unit 1010 and a processing unit 1020. Wherein the content of the first and second substances,

a receiving unit 1010, configured to receive sequence number SN indication information and a trigger instruction sent by a first sending apparatus, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send a SN of a last data protocol unit PDU to the receiving apparatus, and the trigger instruction is used to indicate that the receiving apparatus starts a reconfiguration timer;

a processing unit 1020, configured to start the reconfiguration timer according to the trigger instruction, and determine whether to receive the PDU carrying the SN before the reconfiguration timer expires according to the SN indication information;

if the receiving unit 1010 receives the PDU carrying the SN before the reconfiguration timer expires, the processing unit 1020 is further configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, or

If the receiving unit 1010 does not receive the PDU carrying the SN before the reconfiguration timer expires, the processing unit 1020 is further configured to reconfigure the PDCP entity of the receiving apparatus when the reconfiguration timer expires, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

Therefore, in the receiving apparatus of the embodiment of the present application, by receiving the SN of the last PDU sent by the sending apparatus with the first SN length and starting the reconfiguration timer, the receiving apparatus reconfigures the PDCP entity at the receiving end only when receiving the PDU carrying the SN or when the timer is overtime, so as to receive the PDU sent by the sending apparatus or other sending apparatuses with the second SN length, reduce packet loss in the reconfiguration process of the PDCP entity by the receiving apparatus, and prevent an excessively long time delay caused when the receiving apparatus receives the PDU sent by the sending apparatus with the first SN length, so that the receiving apparatus can receive the generated PDU sent by the sending apparatus with the first SN length as much as possible within the preset duration of the configuration timer.

Optionally, the processing unit 1020 is further configured to: before the receiving unit 1010 receives SN indication information and a trigger instruction sent by a first sending apparatus, switching from the first sending apparatus to the second sending apparatus, where an SN length used for sending a PDU is the first SN length, and an SN length used for sending a PDU is the second SN length;

Optionally, before the receiving unit 1010 receives the sequence number SN indication information and the trigger instruction sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, the receiving unit 1010 is further configured to: and before receiving SN indication information and a trigger instruction sent by a first sending device, receiving a high-level signaling sent by the first sending device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processing unit 1020 is specifically configured to: reconfiguring a data PDCP entity of the receiving apparatus by invoking a control PDCP entity of the receiving apparatus.

Optionally, the receiving apparatus further includes a sending unit, where the sending unit is configured to: a reconfiguration complete message sent to the first sending device.

It should be understood that the receiving apparatus 1000 may correspond to a receiving end in the method embodiment, and may implement corresponding functions of the receiving end, which is not described herein again for brevity.

Fig. 11 is a schematic block diagram of a transmitting apparatus 1100 according to an embodiment of the present application. As shown in fig. 11, the transmitting apparatus 1100 includes a transmitting unit 1110, and the transmitting unit 1110 is configured to:

sending, to a receiving apparatus, Sequence Number (SN) indication information and a trigger instruction, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send a SN of a last data protocol unit (PDU) to the receiving apparatus, and the trigger instruction is used to indicate the receiving apparatus to start a reconfiguration timer, so that the receiving apparatus reconfigures a PDCP entity of the receiving apparatus when receiving the PDU that carries the SN or when the reconfiguration timer is overtime.

Therefore, the sending apparatus in this embodiment of the application, by sending, to the receiving apparatus, the SN indicating that the sending apparatus uses the last PDU sent by the first SN length, and instructing the receiving apparatus to start the reconfiguration timer, so that the receiving apparatus reconfigures the PDCP entity at the receiving end only when receiving the PDU carrying the SN or when the timer is overtime, so as to receive the PDU sent by the sending apparatus or other sending apparatuses using the second SN length, reduce packet loss during reconfiguration of the PDCP entity by the receiving apparatus, and prevent an excessively long time delay caused when the receiving apparatus receives the PDU sent by the sending apparatus using the first SN length, so that the receiving apparatus can receive, within a preset time length of the configuration timer, as many generated PDUs sent by the sending apparatus using the first SN length as possible.

Optionally, the sending apparatus further includes a processing unit 1120, and the processing unit 1120 is configured to: before the sending unit 1110 sends the sequence number SN indication information and the trigger instruction to the receiving apparatus, reconfiguring the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, before the first sending apparatus sends the sequence number SN indication information and the trigger instruction to the receiving apparatus, the receiving apparatus has switched from the first sending apparatus to the second sending apparatus, where the SN length of the first sending apparatus for sending the PDU is the first SN length, and the SN length of the second sending apparatus for sending the PDU is the second SN length;

Optionally, the sending unit 1110 is further configured to: and before sending SN indication information and a trigger instruction to a receiving device, sending a high-level signaling to the receiving device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, and the receiving apparatus reconfigures the data PDCP entity of the receiving apparatus by invoking a control PDCP entity of the receiving apparatus when receiving the PDU carrying the SN or when the reconfiguration timer expires.

It should be understood that the receiving apparatus 1100 may correspond to a receiving end in the method embodiment, and may implement corresponding functions of the receiving end, which is not described herein again for brevity.

Fig. 12 is a schematic configuration diagram of a receiving apparatus 1200 according to an embodiment of the present application. As shown in fig. 12, the receiving device includes a processor 1210, a transceiver 1220 and a memory 1230, wherein the processor 1210, the transceiver 1220 and the memory 1230 are communicated with each other through an internal connection path. The memory 1230 is configured to store instructions, and the processor 1210 is configured to execute the instructions stored in the memory 1230 to control the transceiver 1220 to receive signals or transmit signals. Wherein the content of the first and second substances,

a transceiver 1220, configured to receive sequence number SN indication information and a trigger instruction sent by a first sending apparatus, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send a SN of a last data protocol unit PDU to the receiving apparatus, and the trigger instruction is used to indicate that the receiving apparatus starts a reconfiguration timer;

a processor 1210, configured to start the reconfiguration timer according to the trigger instruction, and determine whether a PDU carrying the SN is received before the reconfiguration timer expires according to the SN indication information;

if the transceiver 1220 receives the PDU carrying the SN before the reconfiguration timer expires, the processor 1210 is further configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, or

If the transceiver 1220 does not receive the PDU carrying the SN before the reconfiguration timer expires, the processor 1210 is further configured to reconfigure the PDCP entity of the receiving apparatus when the reconfiguration timer expires, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

Optionally, the processor 1210 is further configured to: before the transceiver 1220 receives the SN indication information and the trigger instruction sent by the first sending apparatus, switching from the first sending apparatus to the second sending apparatus, where an SN length used for sending the PDU is the first SN length, and an SN length used for sending the PDU is the second SN length;

Optionally, before the transceiver 1220 receives the sequence number SN indication information and the trigger instruction sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, the transceiver 1220 is further configured to: and before receiving SN indication information and a trigger instruction sent by a first sending device, receiving a high-level signaling sent by the first sending device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

Optionally, the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processor 1210 is specifically configured to: reconfiguring a data PDCP entity of the receiving apparatus by invoking a control PDCP entity of the receiving apparatus.

Optionally, the transceiver 1220 is further configured to: a reconfiguration complete message sent to the first sending device.

It should be understood that, in the embodiment of the present application, the processor 1210 may be a Central Processing Unit (CPU), and the processor 1210 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 1230 may include both read-only memory and random-access memory, and provides instructions and data to the processor 1210. A portion of the memory 1230 may also include non-volatile random access memory. For example, memory 1230 may also store device type information.

In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1210. The steps of the positioning method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor 1210. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1230, and the processor 1210 reads the information in the memory 1230 and performs the steps of the method in combination with the hardware. To avoid repetition, it is not described in detail here.

The receiving apparatus 1200 according to the embodiment of the present application may correspond to the receiving end for executing the method 400 in the method 400 and the receiving end 1000 according to the embodiment of the present application, and each unit or module in the receiving apparatus 1200 is respectively configured to execute each action or processing procedure executed by the receiving end in the method 400, and a detailed description thereof is omitted here for avoiding redundancy.

Fig. 13 is a schematic structural diagram of a receiving apparatus 1300 according to an embodiment of the present application. As shown in fig. 13, the receiving apparatus includes a processor 1310, a transceiver 1320, and a memory 1330, wherein the processor 1310, the transceiver 1320, and the memory 1330 communicate with each other through an interconnection. The memory 1330 is configured to store instructions and the processor 1310 is configured to execute the instructions stored by the memory 1330 to control the transceiver 1320 to receive signals or transmit signals. The transceiver 1320 is specifically configured to:

Optionally, the sending apparatus further includes a processor 1310, where the processor 1310 is configured to: before the transceiver 1320 sends the sequence number SN indication information and the trigger instruction to the receiving apparatus, reconfiguring the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

Optionally, the transceiver 1320 is further configured to: and before sending SN indication information and a trigger instruction to a receiving device, sending a high-level signaling to the receiving device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

Optionally, the transceiver 1320 is further configured to: and receiving the reconfiguration completion message sent by the receiving device.

It should be understood that, in the embodiment of the present application, the processor 1310 may be a Central Processing Unit (CPU), and the processor 1310 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 1330 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1310. A portion of the memory 1330 may also include non-volatile random access memory. For example, the memory 1330 may also store information of device types.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 1310. The steps of the positioning method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor 1310. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1330, and the processor 1310 reads the information in the memory 1330 and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The receiving apparatus 1300 according to the embodiment of the present application may correspond to the transmitting end used for executing the method 400 in the method 400 and the transmitting end 1100 according to the embodiment of the present application, and each unit or module in the receiving apparatus 1300 is respectively configured to execute each action or processing procedure executed by the transmitting end in the method 400, and here, detailed descriptions thereof are omitted to avoid redundancy.

Fig. 14 is a schematic structural diagram of a system chip according to an embodiment of the present application. The system chip 1400 of fig. 14 includes an input interface 1401, an output interface 1402, at least one processor 1403, and a memory 1404, wherein the input interface 1401, the output interface 1402, the processor 1403, and the memory 1404 are connected to each other through an internal connection path. The processor 1403 is used to execute the code in the memory 1404.

Optionally, when the code is executed, the processor 1403 may implement the method 200 executed by the receiving end in the method embodiment. For brevity, no further description is provided herein.

Optionally, when the code is executed, the processor 1403 may implement the method 200 performed by the transmitting end in the method embodiment. For brevity, no further description is provided herein.

Fig. 15 is a schematic structural diagram of a system chip according to an embodiment of the present application. The system chip 1500 in fig. 15 includes an input interface 1501, an output interface 1502, at least one processor 1503, and a memory 1504, wherein the input interface 1501, the output interface 1502, the processor 1503, and the memory 1504 are connected to each other through an internal connection path. The processor 1503 is configured to execute code in the memory 1504.

Optionally, when the code is executed, the processor 1503 may implement the method 400 executed by the receiving end in the method embodiment. For brevity, no further description is provided herein.

Optionally, when the code is executed, the processor 1503 may implement the method 400 performed by the transmitting end in the method embodiment. For brevity, no further description is provided herein.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

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 application.

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 several embodiments provided in the present application, 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 unit is only one logical functional 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 application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

This functionality, 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 solution of the present application or portions thereof that substantially contribute to the prior art may be embodied 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 method according to the embodiments of the present application. 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 embodiments are only specific embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in the embodiments of the present application, and all such changes or substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of configuring a packet data convergence protocol, PDCP, entity, the method comprising:

and when receiving the PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end so that the receiving end can receive the PDU sent by the first sending end by using the second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity.

2. The method of claim 1, further comprising:

when the receiving end receives the PDU carrying the SN, the receiving end is switched to the second sending end from the first sending end, the SN length of the first sending end used for sending the PDU is the first SN length, and the SN length of the second sending end used for sending the PDU is the second SN length;

3. The method of claim 1, wherein after the receiving end receives the SN indication information sent by the first sending end, the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send PDUs to the receiving end by using the second SN length through the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end by using the first SN length;

4. The method according to any one of claims 1 to 3, wherein the PDCP entity of the receiving end is a data PDCP entity of the receiving end, and wherein the reconfiguring the PDCP entity of the receiving end when the receiving end receives the PDU carrying the SN comprises:

and when the receiving end receives the PDU carrying the SN, the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

5. The method according to any one of claims 1 to 3, further comprising:

and the receiving end sends a reconfiguration completion message to the first sending end.

6. The method according to claim 1 or 3, wherein the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

7. A method of configuring a packet data convergence protocol, PDCP, entity, the method comprising:

a receiving end receives sequence number SN indication information and a trigger instruction sent by a sending end, wherein the SN indication information is used for indicating a SN of a last data protocol unit PDU sent to the receiving end by a first sending end by using a first SN length, and the trigger instruction is used for indicating the receiving end to start a reconfiguration timer;

8. The method of claim 7, further comprising:

9. The method of claim 7, wherein after the receiving end receives the SN indication information and the trigger instruction sent by the first sending end, the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end with the second SN length through the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end with the first SN length;

10. The method according to any one of claims 7 to 9, wherein before the receiving end receives the SN indication information and the trigger instruction sent by the sending end, the method further comprises:

and the receiving end receives a high-level signaling sent by the first sending end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

11. The method according to any one of claims 7 to 9, wherein the PDCP entity of the receiving end is a data PDCP entity of the receiving end, and wherein the reconfiguring, by the receiving end, the PDCP entity of the receiving end comprises:

and the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

12. The method according to any one of claims 7 to 9, further comprising:

and the receiving end sends the reconfiguration completion message to the first sending end.

13. The method according to claim 7 or 9, wherein the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

14. A method of configuring a packet data convergence protocol, PDCP, entity, the method comprising:

a first sending end sends sequence number SN indication information to a receiving end, wherein the SN indication information is used for indicating the SN of the last PDU sent to the receiving end by the first sending end by using a first SN length, so that the receiving end reconfigures a PDCP entity of the receiving end when receiving the PDU carrying the SN, and the receiving end can receive the PDU sent by the first sending end by using a second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity.

15. The method of claim 14, wherein after the first sender sends the SN indication information to the receiver, the method further comprises:

the first sending end reconfigures the PDCP entity of the first sending end, so that the first sending end can send the PDU to the receiving end by using a second SN length through the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end by using the first SN length;

16. The method according to claim 14, wherein the receiving end switches from the first sending end to a second sending end when receiving the PDU carrying the SN, the SN length of the PDU sent by the first sending end is the first SN length, and the SN length of the PDU sent by the second sending end is a second SN length;

17. The method according to any of claims 14 to 16, wherein the PDCP entity of the receiving end is a data PDCP entity of the receiving end,

18. The method according to any one of claims 14 to 16, further comprising:

and the first sending end receives the reconfiguration finishing message sent by the receiving end.

19. The method according to claim 14 or 15, wherein the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

20. A method of configuring a packet data convergence protocol, PDCP, entity, the method comprising:

a first sending end sends sequence number SN indication information and a trigger instruction to a receiving end, wherein the SN indication information is used for indicating the SN of the last data protocol unit PDU sent to the receiving end by the first sending end by using a first SN length, the trigger instruction is used for indicating the receiving end to start a reconfiguration timer, so that the receiving end reconfigures a PDCP entity of the receiving end when receiving the PDU carrying the SN or the reconfiguration timer is overtime, and the receiving end can receive the PDU sent by the first sending end by using a second SN length or the PDU sent by the second sending end by using the second SN length through the reconfigured PDCP entity.

21. The method of claim 20, wherein after the first sender sends the SN indication information and the trigger instruction to a receiver, the method further comprises:

22. The method according to claim 20, wherein the receiving end switches from the first sending end to a second sending end when receiving the PDU carrying the SN, the SN length of the PDU sent by the first sending end is the first SN length, and the SN length of the PDU sent by the second sending end is a second SN length;

23. The method according to any of claims 20 to 22, wherein before the first sending end sends SN indication information and a trigger instruction to a receiving end, the method further comprises:

and the first sending end sends a high-level signaling to the receiving end, wherein the high-level signaling comprises the information of the preset duration of the reconfiguration timer.

24. The method according to any of claims 20 to 22, wherein the PDCP entity of the receiving end is a data PDCP entity of the receiving end,

when the receiving end receives the PDU carrying the SN or the reconfiguration timer is overtime, the receiving end reconfigures the data PDCP entity of the receiving end by calling the control PDCP entity of the receiving end.

25. The method of any one of claims 20 to 22, further comprising:

26. The method according to claim 20 or 21, wherein the receiving end is a terminal device, and the first sending end is a network device; or the receiving end is a network device and the first sending end is a terminal device.

27. A receiving apparatus, characterized in that the receiving apparatus comprises:

a receiving unit, configured to receive SN indication information of a sequence number SN sent by a first sending apparatus, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send an SN of a last data protocol unit PDU to the receiving apparatus;

a processing unit, configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

28. The receiving device of claim 27, wherein the processing unit is further configured to:

when the receiving unit receives the PDU carrying the SN, switching from the first sending device to the second sending device, where an SN length used by the first sending device to send the PDU is the first SN length, and an SN length used by the second sending device to send the PDU is the second SN length;

29. The receiving apparatus according to claim 27, wherein after the receiving unit receives the SN indication information sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus by using the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus by using the first SN length;

30. The receiving apparatus according to any of claims 27 to 29, wherein the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processing unit is specifically configured to:

and when receiving the PDU carrying the SN, reconfiguring a data PDCP entity of the receiving device by calling a control PDCP entity of the receiving device.

31. The receiving apparatus according to any one of claims 27 to 29, wherein the receiving apparatus further comprises a transmitting unit configured to:

sending a reconfiguration complete message to the first sending device.

32. The receiving apparatus according to claim 27 or 29, wherein the receiving apparatus is a terminal device, and the first transmitting apparatus is a network device; or the receiving device is a network device, and the first transmitting device is a terminal device.

33. A receiving apparatus, characterized in that the receiving apparatus comprises:

a receiving unit, configured to receive sequence number SN indication information and a trigger instruction sent by a first sending apparatus, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send the SN of a last data protocol unit PDU to the receiving apparatus, and the trigger instruction is used to indicate that the receiving apparatus starts a reconfiguration timer;

the processing unit is used for starting the reconfiguration timer according to the trigger instruction and determining whether the PDU carrying the SN is received before the reconfiguration timer is overtime according to the SN indication information;

if the receiving unit receives the PDU carrying the SN before the reconfiguration timer expires, the processing unit is further configured to reconfigure the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, or

If the receiving unit does not receive the PDU carrying the SN before the reconfiguration timer expires, the processing unit is further configured to reconfigure the PDCP entity of the receiving apparatus when the reconfiguration timer expires, so that the receiving apparatus can receive, through the reconfigured PDCP entity, the PDU sent by the first sending apparatus using the second SN length or the PDU sent by the second sending apparatus using the second SN length.

34. The receiving device of claim 33, wherein the processing unit is further configured to:

35. The receiving apparatus according to claim 33, wherein after the receiving unit receives the SN indication information and the trigger instruction sent by the first sending apparatus, the first sending apparatus reconfigures the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus with the second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus with the first SN length;

36. The receiving apparatus according to any one of claims 33 to 35, wherein the receiving unit is further configured to:

and before receiving SN indication information and a trigger instruction sent by a first sending device, receiving a high-level signaling sent by the first sending device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

37. The receiving apparatus according to any of claims 33 to 35, wherein the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus, wherein the processing unit is specifically configured to:

reconfiguring a data PDCP entity of the receiving apparatus by invoking a control PDCP entity of the receiving apparatus.

38. The receiving apparatus according to any one of claims 33 to 35, wherein the receiving apparatus further comprises a transmitting unit configured to:

a reconfiguration complete message sent to the first sending device.

39. The receiving apparatus according to claim 33 or 35, wherein the receiving apparatus is a terminal device, and the first transmitting apparatus is a network device; or the receiving device is a network device, and the first transmitting device is a terminal device.

40. A transmitting apparatus, wherein the transmitting apparatus is a first transmitting apparatus, and the first transmitting apparatus includes a transmitting unit configured to:

and sending Sequence Number (SN) indication information to a receiving device, wherein the SN indication information is used for indicating that the first sending device uses a first SN length to send the SN of the last PDU to the receiving device, so that the receiving device reconfigures a PDCP entity of the receiving device when receiving the PDU carrying the SN, and the receiving device can receive the PDU sent by the first sending end using a second SN length or the PDU sent by the second sending end using the second SN length through the reconfigured PDCP entity.

41. The transmitting device of claim 40, wherein the first transmitting device apparatus further comprises a processing unit configured to:

after the sending unit sends the Sequence Number (SN) indication information to the receiving device, reconfiguring the PDCP entity of the first sending device, so that the first sending device can send the PDU to the receiving device by using a second SN length through the reconfigured PDCP entity of the first sending device after sending the last PDU to the receiving device by using the first SN length;

42. The transmitting apparatus according to claim 40, wherein the receiving apparatus switches from the first transmitting apparatus to a second transmitting apparatus when receiving the PDU carrying the SN, the SN length used by the first transmitting apparatus for transmitting the PDU is the first SN length, and the SN length used by the second transmitting apparatus for transmitting the PDU is a second SN length;

43. The transmitting apparatus according to any of claims 40 to 42, wherein the PDCP entity of the receiving apparatus is a data PDCP entity of the receiving apparatus,

and when the receiving device receives the PDU carrying the SN, the receiving device reconfigures the data PDCP entity of the receiving device by calling the control PDCP entity of the receiving device.

44. The transmitting device according to any of claims 40 to 42, wherein the first transmitting device further comprises a receiving unit configured to:

and receiving the reconfiguration completion message sent by the receiving device.

45. The transmitting apparatus according to claim 40 or 41, wherein the receiving apparatus is a terminal device, and the first transmitting apparatus is a network device; or the receiving device is a network device, and the first transmitting device is a terminal device.

46. A transmitting apparatus, wherein the transmitting apparatus is a first transmitting apparatus, and the first transmitting apparatus includes a transmitting unit configured to:

sending, to a receiving apparatus, sequence number SN indication information and a trigger instruction, where the SN indication information is used to indicate that the first sending apparatus uses a first SN length to send a SN of a last data protocol unit PDU to the receiving apparatus, and the trigger instruction is used to indicate that the receiving apparatus starts a reconfiguration timer, so that the receiving apparatus reconfigures a PDCP entity of the receiving apparatus when receiving a PDU carrying the SN or when the reconfiguration timer is overtime, so that the receiving apparatus can receive, through the reconfigured PDCP entity, a PDU sent by the first sending end using a second SN length or a PDU sent by the second sending end using the second SN length.

47. The transmitting device of claim 46, further comprising a processing unit configured to:

after the sending unit sends the sequence number SN indication information and the trigger instruction to the receiving apparatus, reconfiguring the PDCP entity of the first sending apparatus, so that the first sending apparatus can send the PDU to the receiving apparatus with a second SN length through the reconfigured PDCP entity of the first sending apparatus after sending the last PDU to the receiving apparatus with the first SN length;

48. The transmitting apparatus according to claim 46, wherein the receiving apparatus switches from the first transmitting apparatus to a second transmitting apparatus when receiving the PDU carrying the SN, the SN length of the PDU sent by the first transmitting apparatus is the first SN length, and the SN length of the PDU sent by the second transmitting apparatus is a second SN length;

49. The transmitting device according to any of claims 46 to 48, wherein said transmitting unit is further configured to:

and before sending SN indication information and a trigger instruction to a receiving device, sending a high-level signaling to the receiving device, wherein the high-level signaling comprises information of preset duration of the reconfiguration timer.

50. The transmitting device according to any of claims 46 to 48, wherein the PDCP entity of the receiving device is a data PDCP entity of the receiving device,

when the receiving device receives the PDU carrying the SN or the reconfiguration timer is overtime, the receiving device reconfigures the data PDCP entity of the receiving device by calling the control PDCP entity of the receiving device.

51. The transmitting device according to any of claims 46 to 48, wherein the first transmitting device further comprises a receiving unit configured to:

52. The transmitting apparatus according to claim 46 or 47, wherein the receiving apparatus is a terminal device, and the first transmitting apparatus is a network device; or the receiving device is a network device, and the first transmitting device is a terminal device.