WO2018152751A1

WO2018152751A1 - Method for configuring pdcp entity, receiving device and sending device

Info

Publication number: WO2018152751A1
Application number: PCT/CN2017/074594
Authority: WO
Inventors: 唐海
Original assignee: 广东欧珀移动通信有限公司
Priority date: 2017-02-23
Filing date: 2017-02-23
Publication date: 2018-08-30
Also published as: CN109661835B; CN109661835A

Abstract

Disclosed are a method for configuring a packet data convergence protocol (PDCP) entity, a receiving device and a sending device. The method comprises: a receiving end receives serial 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 by the first sending end using the first SN length to the receiving end; and when receiving a PDU carrying the SN, the receiving end reconfigures the PDCP entity of the receiving end so that the receiving end can receive, by means of the reconfigured PDCP entity, a PDU sent by the first sending end using a second SN length or a PDU sent by a second sending end using the second SN length. Since the receiving end reconfigures the PDCP entity of the receiving end after receiving the last PDU sent by the sending end using the first SN length, packet loss during PDCP entity reconfiguration is avoided.

Description

Method, receiving device and transmitting device for configuring PDCP entity

Technical field

The embodiments of the present application relate to the field of wireless communications, and, more particularly, to a method, a receiving apparatus, and a transmitting apparatus for configuring a packet data convergence protocol PDCP entity.

Background technique

In the Long Term Evolution ("LTE") Packet Data Convergence Protocol (PDCP), the header of a Protocol Data Unit ("PDU") is mainly composed of a header. The sequence number ("SN") is used to indicate a specific PDU sequence to the peer PDCP entity, so as to ensure that the PDUs can be delivered in the order of receipt when submitted to the upper layer. In the existing protocol, SN mainly supports 7bits, 12bits, 15bits, 16bits, 18bits and other length configurations. SNs of different lengths can be used to indicate packets of different traffic sizes. The longer the length of the SN, the more PDUs can be indicated, but the corresponding overhead is greater. For example, the 7-bit SN can theoretically support simultaneous indication of 128 PDUs.

However, in some scenarios, for example, when the terminal switches between two base stations or the PDCP entity of the same base station needs to be reconfigured, the length of the SN may change. If the PDCP entity cannot identify the SN after the length change, the packet loss may occur. .

For example, when a terminal switches between a legacy base station (eNodeB) and a base station supporting carrier aggregation ("CAR"), since the SN of the legacy base station is only 12 bits, and the SN of the base station supporting the CA has 15 bits, the terminal is in two. When switching between base stations, there is a reconfiguration process in which the SN changes from short to long or SN from long to short. If the PDCP entity of the terminal has been reconfigured when the PDU that has been generated by the original base station is sent to the terminal, the PCDP protocol layer of the terminal will not be supported, and the generated PDUs will be discarded. When the terminal device performs the handover between the original base station and the target base station in the LTE system, the PDCP entity of the terminal immediately reconfigures after receiving the handover to receive the PDU transmitted by the target base station according to the SN length of the target base station, and the original base station A PDU that has been generated according to the SN of the original base station is not retransmitted in the newly configured PDCP entity, so that the problem of handover loss occurs.

For example, in a non-handover scenario, when the PDCP entity of the same base station needs to be reconfigured, if the length of the SN is shortened from long to long, the PDCP entity of the terminal is reconfigured. The PDU transmitted by the base station using the original SN length cannot be identified, so packet loss also occurs in this case.

Summary of the invention

The embodiment of the present application provides a method, a receiving device, and a sending device for configuring a packet data convergence protocol (PDCP) entity, which avoids packet loss during PDCP entity reconfiguration.

A first aspect provides a method for configuring a packet data convergence protocol (PDCP) entity, including:

The receiving end receives the sequence number SN indication information sent by the first sending end, where the SN indication information is used to indicate the SN of the last data protocol unit 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 the PDU that carries the SN is received, so that the receiving end can receive the first sending end by using the reconfigured PDCP entity. The PDU transmitted using the second SN length or the PDU transmitted by the second transmitting end using the second SN length.

Therefore, the method for configuring a PDCP entity in the embodiment of the present application receives the SN of the last PDU sent by the sender using the first SN length, and reconfigures the PDCP entity at the receiving end when receiving the PDU carrying the SN. , avoiding packet loss during PDCP entity reconfiguration.

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 switches from the first sending end To the second sending end, the SN length of the first transmitting end for transmitting the PDU is the first SN length, and the SN length used by the second sending end to send the PDU is the second SN length; The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the second sending end by using the second SN length.

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 first sending end has performed heavy on the PDCP entity of the first sending end. So that the first sending end can use the second PDCP entity of the first sending end by reconfiguring the first PDU after sending the last PDU to the receiving end by using the first SN length. The SN length sends a PDU to the receiving end, where the reconfigured PDCP entity of the receiving end is configured to receive, by the first sending end, the second SN length to send PDU.

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 the receiving end determines that the PDU carrying the SN is received, The reconfiguration of the PDCP entity at the receiving end includes: when the receiving end determines that the PDU carrying the SN is received, the receiving end reconfigures the data PDCP entity of the receiving end by calling the controlling PDCP entity of the receiving end.

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

Optionally, in an implementation manner of the first aspect, the receiving end is a terminal device, 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.

A second aspect provides a method for configuring a packet data convergence protocol (PDCP) entity, including:

The first sending end sends the sequence number SN indication information to the receiving end, where the SN indication information is used to indicate that the first sending end uses the first SN length to send the SN of the last PDU to the receiving end, so that the The receiving end reconfigures the PDCP entity of the receiving end when determining that the PDU carrying the SN is received.

Therefore, in the method for configuring a PDCP entity in the embodiment of the present application, the transmitting end sends the SN of the last PDU that is sent by using the first SN length to the receiving end, so that the receiving end receives the PDU carrying the SN. The PDCP entity at the receiving end performs reconfiguration to avoid packet loss during PDCP entity reconfiguration.

Optionally, in an implementation manner of the second aspect, before the first sending end sends the sequence number SN indication information to the receiving end, the method further includes: the first sending end is configured by the first sending end The PDCP entity performs reconfiguration, so that the first sending end can use the reconfigured PDCP entity of the first sending end after sending the last PDU to the receiving end by using the first SN length. The second SN length sends a PDU to the receiving end, where the reconfigured PDCP entity of the receiving end is configured to receive the PDU sent by the first sending end by using the second SN length.

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

Optionally, in an implementation manner of the second aspect, the PDCP entity at the receiving end is a data PDCP entity of the receiving end, and the receiving end receives the PDU when carrying the SN by calling the The controlling PDCP entity at the receiving end reconfigures the data PDCP entity of the receiving end.

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

Optionally, in an implementation manner of the second aspect, the receiving end is a terminal device, 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. device.

In a third aspect, a receiving device is provided, which can perform the operations of the receiving end in the first aspect or any alternative implementation of the first aspect. In particular, the receiving means may comprise a modular unit for performing the operations of the receiving end in the first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, a transmitting apparatus is provided, which can perform the operations of the transmitting end in any of the optional implementations of the second aspect or the second aspect described above. In particular, the transmitting means may comprise a modular unit for performing the operations of the transmitting end in any of the possible implementations of the second aspect or the second aspect described above.

In a fifth aspect, a receiving device is provided, the receiving device comprising: a processor, a transceiver, and a memory. The processor, the transceiver, and the memory communicate with each other through an internal connection path. The memory is for storing instructions for executing instructions stored by the memory. When the processor executes the instructions stored by the memory, the executing causes the receiving device to perform the method of the first aspect or any possible implementation of the first aspect, or the performing causes the receiving device to implement the receiving provided by the third aspect Device.

In a sixth aspect, a transmitting apparatus is provided, the transmitting apparatus comprising: a processor, a transceiver, and a memory. The processor, the transceiver, and the memory communicate with each other through an internal connection path. The memory is for storing instructions for executing instructions stored by the memory. When the processor executes the instruction stored by the memory, the executing causes the transmitting device to perform the method in any of the possible implementations of the second aspect or the second aspect, or the performing causes the transmitting device to implement the fourth The transmitting device provided by the aspect.

In a seventh aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program causing a receiving device to perform the first aspect described above, and configuring the PDCP in any of the various implementations thereof The method of the entity.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program causing a transmitting device to perform the second aspect described above, and configuring the PDCP in any of the various implementations thereof The method of the entity.

According to a ninth aspect, a system chip is provided, the system chip includes an input interface, an output interface, a processor, and a memory, where the weapon is used to execute an instruction stored by the memory, and when the instruction is executed, the processor can implement Any of the foregoing first aspects and various implementations thereof.

According to a tenth aspect, a system chip is provided, the system chip includes an input interface, an output interface, a processor, and a memory, where the edge device is configured to execute an instruction stored by the memory, and when the instruction is executed, the processor can implement Any of the foregoing second aspects and various implementations thereof.

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

The receiving end receives the sequence number SN indication information and the triggering instruction sent by the sending end, where the SN indication information is used to indicate the SN of the last data protocol unit PDU sent by the first sending end to the receiving end by using the first SN length. The triggering instruction is used to instruct the receiving end to start a reconfiguration timer;

The receiving end starts the reconfiguration timer according to the triggering instruction, and determines, according to the SN indication information, whether a PDU carrying the SN is received before the reconfiguration timer expires;

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, or

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. And the PDU that is 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, by the PDCP entity that enables the receiving end to be reconfigured.

Therefore, in the method for configuring a PDCP entity in the embodiment of the present application, the receiving end receives the transmitting end by receiving Using the SN of the last PDU sent by the first SN length, and starting the reconfiguration timer, so that the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN or the timer expires, thereby receiving The transmitting end or the other sending end uses the PDU sent by the second SN length, which reduces the packet loss during the reconfiguration process of the PDCP entity by the receiving end, and prevents the receiving end from causing the receiving end to use the PDU sent by the first SN length. The delay is too long, so that the receiving end can receive as much as possible the generated PDU sent by the sending end using the first SN length within the preset duration of the configuration timer.

Optionally, in an implementation manner of the eleventh aspect, before the receiving end receives the SN indication information and the triggering 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 transmitting the PDU is the first SN length, and the second sending end is used for sending The SN length of the PDU is the second SN length;

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

Optionally, in an implementation manner of the eleventh aspect, before the receiving end receives the serial number SN indication information and the triggering instruction sent by the first sending end, the first sending end sends the first sending The PDCP entity of the terminal has been reconfigured to enable the first transmitting end to pass the reconfigured PDCP entity of the first transmitting end after transmitting the last PDU to the receiving end by using the first SN length. Transmitting, by using the second SN length, the PDU to the receiving end;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the first sending 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 triggering instruction sent by the sending end, the method further includes: the receiving end receiving the first sending The high layer signaling sent by the terminal, where the high layer signaling includes information of a 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 receiving end reconfigures the PDCP entity of the receiving end, including: The receiving end reconfigures the data PDCP entity of the receiving end by calling a control PDCP entity of the receiving end.

Optionally, in an implementation manner of the eleventh aspect, the method further includes: a reconfiguration complete message sent by the receiving end to the first sending end.

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

A twelfth aspect provides a method for configuring a packet data convergence protocol (PDCP) entity, including:

The first sending end sends the sequence number SN indication information and the triggering instruction to the receiving end, where the SN indication information is used to indicate that the first sending end sends the last data protocol unit PDU to the receiving end by using the first SN length. The SN, the triggering instruction is used to instruct the receiving end to start a reconfiguration timer, so that the receiving end receives the PDU carrying the SN or when the reconfiguration timer expires The PDCP entity is reconfigured.

Therefore, in the method for configuring a PDCP entity in the embodiment of the present application, the transmitting end sends the SN of the last PDU that is sent by using the first SN length to the receiving end, and instructs the receiving end to start the reconfiguration timer, so that the receiving end is receiving. When the PDU carrying the SN or the timer expires, the PDCP entity at the receiving end is reconfigured to receive the PDU sent by the sending end or other transmitting end using the second SN length, thereby reducing the reconfiguration of the PDCP entity by the receiving end. The packet loss in the process is prevented, and the delay caused by the receiving end to receive the PDU sent by the first SN is too long, so that the receiving end can receive and send as much as possible within the preset duration of the configuration timer. The generated PDU transmitted by the terminal using the first SN length.

Optionally, in an implementation manner of the twelfth aspect, before the first sending end sends the sequence number SN indication information and the triggering instruction to the receiving end, the method further includes: the first sending end pair The PDCP entity of the first sending end performs reconfiguration, so that the first sending end can pass the first of the reconfiguration after sending the last PDU to the receiving end by using the first SN length. The PDCP entity at the transmitting end sends the PDU to the receiving end by using the second SN length;

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

The PDCP entity of the receiving end that is reconfigured is configured to receive the second sending end A PDU transmitted with the second SN length.

Optionally, in an implementation manner of the twelfth aspect, before the first sending end sends the SN indication information and the triggering instruction to the receiving end, the method further includes: the first sending end is to the The receiving end sends high layer signaling, where the high layer signaling includes information of a preset duration of the reconfiguration timer.

Optionally, in an implementation manner of the twelfth aspect, the PDCP entity at the receiving end is a data PDCP entity of the receiving end, and the receiving end receives the PDU carrying the SN or the reconfiguration When the timer expires, the data PDCP entity of the receiving end is reconfigured by calling the controlling PDCP entity of the receiving end.

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

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

In a thirteenth aspect, a receiving apparatus is provided, which can perform the operation of the receiving end in any of the optional implementations of the eleventh or eleventh aspect. In particular, the receiving means may comprise a modular unit for performing the operation of the receiving end in any of the possible implementations of the eleventh or eleventh aspect described above.

In a fourteenth aspect, there is provided a transmitting apparatus, which can perform the operation of the transmitting end in any of the optional implementations of the twelfth aspect or the twelfth aspect. In particular, the transmitting means may comprise a modular unit for performing the operations of the transmitting end in any of the possible implementations of the twelfth aspect or the twelfth aspect.

In a fifteenth aspect, a receiving device is provided, the receiving device comprising: a processor, a transceiver, and a memory. The processor, the transceiver, and the memory communicate with each other through an internal connection path. The memory is for storing instructions for executing instructions stored by the memory. When the processor executes the instruction stored by the memory, the executing causes the receiving device to perform the method in any of the possible implementations of the eleventh or eleventh aspect, or the execution causes the receiving device to implement the thirteenth aspect Receiver provided.

In a sixteenth aspect, a transmitting apparatus is provided, the transmitting apparatus comprising: a processor, a transceiver, and a memory. The processor, the transceiver, and the memory communicate with each other through an internal connection path. The memory is for storing instructions for executing instructions stored by the memory. When When the processor executes the instruction stored by the memory, the executing causes the transmitting device to perform the method of any of the possible implementations of the twelfth aspect or the twelfth aspect, or the execution causes the transmitting device to implement the fourteenth aspect Sending device.

In a seventeenth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program causing a receiving device to perform any of the eleventh aspect described above, and various implementations thereof The method of configuring a PDCP entity.

In a eighteenth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program causing a transmitting device to perform the twelfth aspect described above, and any of its various implementations The method of configuring a PDCP entity.

According to a nineteenth aspect, a system chip is provided, the system chip includes an input interface, an output interface, a processor, and a memory, where the weapon is used to execute an instruction stored by the memory, and when the instruction is executed, the processor can Any of the foregoing eleventh aspects and various implementations thereof are implemented.

According to a twentieth aspect, a system chip is provided, the system chip includes an input interface, an output interface, a processor, and a memory, where the weapon is used to execute an instruction stored by the memory, and when the instruction is executed, the processor can A method of any of the aforementioned twelfth aspects and various implementations thereof is implemented.

DRAWINGS

FIG. 1 is a schematic structural diagram of an application scenario of an embodiment of the present application.

2 is a process interaction diagram of a method for configuring a PDCP entity according to an embodiment of the present application.

FIG. 3 is a flow diagram of a process for configuring a PDCP entity according to an embodiment of the present application.

4 is a process interaction diagram of a method for configuring a PDCP entity according to another embodiment of the present application.

FIG. 5 is a flow diagram of a process 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 structural diagram of a receiving apparatus according to an embodiment of the present application.

FIG. 9 is a schematic structural diagram of a transmitting apparatus according to an embodiment of the present application.

FIG. 10 is a schematic block diagram of a receiving apparatus according to 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 structural diagram of a receiving apparatus according to another embodiment of the present application.

FIG. 13 is a schematic structural 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 according to 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 can be applied to various communication systems, for example, Global System of Mobile Communication ("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 Telecommunication System (UMTS), and future 5G communication systems.

The present application describes various embodiments in connection with a terminal device. A terminal device may also be referred to as a User Equipment ("UE"), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication device. , user agent or 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, or a personal digital assistant (Personal Digital Assistant, Referred to as "PDA"), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, or a terminal device in a future evolved PLMN network. Wait.

The present application describes various embodiments in connection with a network device. The network device may be a device for communicating with the terminal device, for example, may be a base station (Base Transceiver Station, abbreviated as "BTS") in the GSM system or CDMA, or may be a base station (NodeB, referred to as "NB" in the WCDMA system. ”), may also be an evolved base station (Evolutional Node B, “eNB” or “eNodeB”) in the LTE system, or the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and a future 5G network. A network side device in a network side device 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 Figure 1 can The network device 10, the network device 20, and the terminal device 30 are included. Both network device 10 and network device 20 can be used to provide communication services for terminal device 30. The arrow shown by the solid line in FIG. 1 may indicate the uplink/downlink transmission by the cellular link between the terminal device 30 and the network device 10, and the arrow shown by the broken line in FIG. 1 may indicate that the terminal device 30 and the network are Up/down transmission of cellular links between devices 20.

The terminal device 30 can perform connection switching between the network device 10 and the network device 20, for example, the terminal device 30 receives the PDU transmitted by the network device 10 before the handover, and the terminal device 30 receives the PDU transmitted by the network device 20 after the handover. It is assumed that the SN length supported by the network device 10 is different from the SN length supported by the network device 20. When the terminal device 30 switches between the network device 10 and the network device 20, there is a reconfiguration of the SN from short to long or SN from long to short. process. When the PDU that has been generated by the network device 10 is 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, and thus 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, the PDCP entity of the network device 10 that communicates with the terminal device 30 needs to be reconfigured, if the length of the SN is shortened from long to long during the reconfiguration process. Or, from short to long, the PDCP entity of the terminal device 30 cannot recognize the PDU transmitted by the network device 10 using the original SN length after reconfiguration, so packet loss may also occur in this case.

In the embodiment of the present application, the transmitting end sends the SN of the last PDU that is sent by using the first SN length to the receiving end, so that the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN. Packet loss during PDCP entity reconfiguration 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) or a Device to Device (D2D) network or a machine to machine/person ( Machine to Machine/Man, referred to as "M2M" network or other network, FIG. 1 is only a simplified schematic diagram of the example, and the network may also include other network devices or terminal devices, which are not shown in FIG.

2 is a flow diagram of a process 200 of a method 200 of configuring a PDCP entity, in accordance with an embodiment of the present application. The receiving end of the method 200 may be a terminal device, and the sending end is a network device; or the receiving end is a network device, and the sending end is a terminal device. In the embodiment of the present application, only the receiving end is a terminal device, and the sending end is a network device as an example. As shown in FIG. 2, the specific process of the reconfiguration packet data convergence protocol PDCP entity includes:

In 210, the first sending end sends the SN indication information to the receiving end.

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

The SN indication information in 210 and 220 is used to indicate the SN of the last PDU sent by the first sending end to the receiving end by using the first SN length.

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

Specifically, after receiving the SN indication information sent by the first sending end, the receiving end determines, according to the SN indicated by the indication information, whether the PDU carrying the SN is received, and the receiving end receives the PDU carrying the SN. The PDCP entity at the receiving end is reconfigured to receive the PDU of the second SN length by the first transmitting end or the second transmitting end. Here, before the reconfiguration of the PDCP entity at the receiving end, the supported SN length is the first SN length, and after the PDCP entity at the receiving end performs reconfiguration, the supported SN length is configured as the second SN length, so that the second SN length can be received. PDU sent by SN length.

Optionally, in 210, before the first sending end sends the sequence number 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 After transmitting the last PDU to the receiving end by using the first SN length, the PDU can be sent to the receiving end by using the second SN length by the reconfigured PDCP entity; wherein the PDCP entity of the reconfigured receiving end in 230 is configured to receive the PDU. A PDU that is sent by the sender using the second SN length.

Specifically, when the PDCP entity of the first transmitting end needs to perform reconfiguration, there is a case where the SN length is shortened from long to short or from short to long. The first transmitting end uses the first SN length to the receiving end before the PDCP entity is reconfigured. The PDU is sent, and after the PDCP entity is reconfigured, the PDU is sent to the receiving end by using the second SN length, and the first sending end sends the SN indication information to the receiving end, where the SN indication information indicates that the first sending end uses the first The SN of the last PDU sent by the SN to the receiving end, the receiving end reconfigures the PDCP entity of the receiving end when receiving the last PDU sent by the first transmitting end using the first SN length, thereby ensuring After receiving the generated PDU sent by the first sending end using the first SN length, the PDU sent by the first sending end using the second SN length is received, thereby avoiding packet loss.

Optionally, before the receiving end receives the SN indication information sent by the first sending end, the method further includes: the receiving end switches from the first sending end to the second sending end, where the first sending end is used to send The length of the SN of the PDU to be sent is the length of the first SN, and the length of the SN used by the second transmitting end to transmit the PDU is the length of the second SN; wherein, the PDCP entity of the reconfigured receiving end in the 230 is configured to receive the second transmitting end and use the second PDU sent by SN length.

Specifically, the receiving end performs switching between the transmitting end, 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 send the PDU, and The SN length (second SN length) of the second network device used to transmit the PDU is different, so 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 switched second network device. The second SN length used, thereby receiving, by the configured PDCP entity, the PDU transmitted by the second network device using the second SN length.

At this time, the terminal device determines, according to the SN indication information received from the first network device, whether it has received the last PDU sent by the first network device using the first SN length, and the terminal device receives the first network device usage first. The PDCP entity is reconfigured only when the last PDU sent by the SN length is received, so that the PDU sent by the second network device is received only after receiving the PDU that has been generated by the first network device, thereby avoiding Lose the package.

Generally, there may be only one PDCP entity in the receiving end or the transmitting end. The PDCP entity may be used to transmit control PDUs and data PDUs. The control information is carried by the control PDU. The PCDP entity in the receiving end or the transmitting end may The control PDCP entity and the data PDCP entity are controlled, the control PDCP entity is used to send a control class PDU, and the data PDCP entity is used to send a data class PDU.

Optionally, the PDCP entity at the receiving end is a data PDCP entity of the receiving end, where the receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN, and the receiving end passes the PDU carrying the SN. The control PDCP entity that invokes the receiving end reconfigures the data PDCP entity at the receiving end.

For example, if the receiving end includes two kinds of PDCPs, which are the PDCP entity and the data PDCP entity, the PDCP is also included in the sending end, and the PDCP entity and the data PDCP entity are included in the sending end, as shown in FIG. The process interaction diagram of the method of the PDCP entity, when the receiving end reconfigures the PDCP entity at the receiving end, the receiving end reconfigures the data PDCP entity of the receiving end by calling the controlling PDCP entity of the receiving end. Figure 3 includes the first network device and the terminal device, as shown in Figure 3:

At 310, the network device reconfigures the data PDCP entity of the network device by invoking a controlling PDCP entity of the network device.

3, taking the non-handover scenario as an example, after the first network device sends the PDU to the terminal device by using the first SN length, the data PDCP entity is reconfigured, so that after the reconfiguration, the second SN length is used to continue to send to the terminal device. PDU.

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 is used to indicate the SN of the last PDU sent by the first network device to the terminal device using the first SN length.

In 330, the controlling PDCP entity of the terminal device receives the SN indication information, thereby obtaining 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 by using the control PDCP entity, so that the terminal device can receive the first network device. A PDU transmitted using a 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 completes the reconfiguration.

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

Therefore, in the method for configuring a PDCP entity in the embodiment of the present application, the transmitting end sends the SN of the last PDU that is sent by using the first SN length to the receiving end, so that the receiving end receives the PDU carrying the SN. The PDCP entity at the end performs reconfiguration to avoid packet loss during PDCP entity reconfiguration.

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

4 is a flow diagram of a process 400 of a method 400 of configuring a PDCP entity in accordance with an embodiment of the present application. The receiving end of the method 400 may be a terminal device, and the sending end is a network device; or the receiving end is a network device, and the sending end is a terminal device. In the embodiment of the present application, only the receiving end is a terminal device, and the sending end is a network device as an example. As shown in FIG. 4, the specific process of the reconfiguration packet data convergence protocol PDCP entity includes:

In 410, the first transmitting end sends the sequence number SN indication information and the triggering instruction to the receiving end.

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

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

Optionally, before the sending, by the sending end, before the first sending end sends the SN indication information and the triggering instruction to the receiving end, the method further includes: the first sending end sends the high layer signaling to the receiving end, where the upper layer The signaling includes information of a preset duration of the reconfiguration timer.

In 420, the receiving end receives the serial number SN indication information and the triggering instruction sent by the transmitting end.

Optionally, before receiving 420, that is, before the receiving end receives the SN indication information and the triggering instruction sent by the sending end, the method further includes: receiving, by the receiving end, the high layer signaling sent by the first sending end, the upper layer The signaling includes information of a preset duration of the reconfiguration timer.

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

If the receiving end receives the PDU carrying the SN before the reconfiguration timer expires, perform 440. If the receiving end does not receive the PDU carrying the SN before the reconfiguration timer expires, execute 450.

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

In the 450, if the receiving end does not receive the PDU carrying the SN before the reconfiguration timer expires, the receiving end sends a PDCP entity to the receiving end when the reconfiguration timer expires. Reconfigure.

Specifically, after receiving the SN indication information and the triggering command 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 by using the first SN, thereby determining Whether the PDU carrying the SN is received before the timer expires. If the receiving end receives the PDU carrying the SN before the configuration timer expires, 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 expires, the receiving end reconfigures the PDCP entity of the receiving end when the configuration timer expires. Here, before the reconfiguration of the PDCP entity at the receiving end, the supported SN length is the first SN length, and after the PDCP entity at the receiving end performs reconfiguration, the supported SN length is configured as the second SN length, and thus the first sending can be received. The PDU transmitted by the second or the second sender using the second SN length.

Optionally, in 410, before the first sending end sends the sequence number SN indication information and the triggering 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 After transmitting the last PDU to the receiving end by using the first SN length, the transmitting end can send the PDU to the receiving end by using the second SN length by using the reconfigured PDCP entity; wherein, the PDCP of the reconfigured receiving end in 440 or 450 The entity is configured to receive the PDU sent by the first sending end by using the second SN length.

Specifically, when the PDCP entity of the first transmitting end needs to perform reconfiguration, there is a case where the SN length is shortened from long to short or from short to long. The first transmitting end uses the first SN length to the receiving end before the PDCP entity is reconfigured. The PDU is sent, and after the PDCP entity is reconfigured, the PDU is sent to the receiving end by using the second SN length, and the first sending end sends the SN indication information and the triggering instruction to the receiving end, where the SN indication information indicates the first sending. The SN of the last PDU sent by the first SN length to the receiving end, the triggering instruction is used to instruct the receiving end to start a reconfiguration timer, and the receiving end starts the reconfiguration timer according to the triggering instruction, and determines whether the timer expires. The SN indication information was previously received.

The receiving end receives the last PDU sent by the first sending end using the first SN length before the timer expires, and then reconfigures the PDCP entity of the receiving end when receiving the PDU, thereby ensuring that the first sending is received after receiving the PDU. The generated PDU sent by the first SN length is used to receive the PDU sent by the first sending end using the second SN length, thereby avoiding packet loss.

The receiving end does not receive the last PDU sent by the first sending end using the first SN length before the timer expires, and then reconfigures the PDCP entity of the receiving end when the timer expires, preventing the receiving end from receiving the first sending end. The delay caused by using the PDU sent by the first SN length is too long, and it is ensured that the receiving end can receive as much as possible the generated content sent by the first transmitting end using the first SN length within the preset duration of the configuration timer. PDU, which reduces the occurrence of packet loss.

Optionally, in 420, before the receiving end receives the SN indication information and the triggering instruction sent by the first sending end, the method further includes: the receiving end switches from the first sending end to the second sending end, where the first sending end uses The SN length of the transmitted PDU is the first SN length, and the second transmitting end is used to send the PDU. The SN length is the second SN length; wherein the PDCP entity of the reconfigured receiving end in 440 or 405 is configured to receive the PDU sent by the second transmitting end using the second SN length.

Specifically, the receiving end switches between the sending end, for example, after switching from the first sending end to the second sending end, because the first sending end is used to send the SN length of the PDU (the first SN length), and the second The SN length (second SN length) used by the transmitting end to transmit the PDU is different. Therefore, the receiving end needs to reconfigure the PDCP entity at the receiving end, so that the PDCP entity at the receiving end can support the second used by the switched second transmitting end. The second SN is configured to receive, by the configured PDCP entity, the PDU sent by the second sending end using the second SN length.

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

The receiving end receives the last PDU sent by the first sending end using the first SN length before the timer expires, and then reconfigures the PDCP entity of the receiving end when the PDU is received, and then the PDCP entity is reconfigured. Therefore, after receiving the generated PDU sent by the first sending end using the first SN length, the PDU transmitted by the second sending end using the second SN length is received, thereby avoiding packet loss.

The receiving end does not receive the last PDU sent by the first sending end using the first SN length before the timer expires, and then reconfigures the PDCP entity of the receiving end when the timer expires, preventing the receiving end from receiving the first sending end. The delay caused by using the PDU sent by the first SN length is too long, and it is ensured that the receiving end can receive as much as possible the generated content sent by the first transmitting end using the first SN length within the preset duration of the configuration timer. PDU, reducing packet loss.

There may be only one type of PDCP entity in the receiving end or the transmitting end. The PDCP entity may be used to transmit control PDUs and data class PDUs. The PCDP entity in the receiving end or the transmitting end may also include a PDCP entity and a data PDCP entity to control PDCP. The entity is used to send a control class PDU, and the data PDCP entity is used to send a data class PDU.

Optionally, the PDCP entity at the receiving end is a data PDCP entity at the receiving end, where, in 440 or 450, the receiving end reconfigures the PDCP entity of the receiving end, including: receiving, by the receiving end, the PDCP entity that controls the PDCP entity of the receiving end to the data of the receiving end Reconfigure.

For example, if the receiving end includes the PDCP of the PDCP entity and the data PDCP entity, the PDCP is also included in the sending end, and the PDCP entity and the data PDCP entity are also included in the sending end, as shown in FIG. Process interaction diagram of the PDCP entity method, the receiving end is When the PDCP entity at the receiving end is reconfigured, the PDCP entity of the receiving end is reconfigured by calling the controlling PDCP entity of the receiving end. The first network device and the terminal device are shown in FIG. 5, as shown in FIG.

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

5 is a non-switching scenario. The first network device performs reconfiguration of the data PDCP entity after transmitting the PDU to the terminal device by using the first SN length, so that after the reconfiguration, the second SN length is used to send to the terminal device. PDU.

In 520, the control PDCP entity of the network device sends the SN indication information and the triggering instruction to the control PDCP entity of the terminal device, where the SN indication information is used to indicate that the first network device uses the first SN length to send the last PDU to the terminal device. SN, the triggering instruction is used to instruct 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 triggering instruction.

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

At 540, the terminal device initiates a reconfiguration timer.

If the terminal device receives the PDU carrying the SN before the reconfiguration timer expires, performing 550, if the terminal device does not receive the PDU carrying the SN before the reconfiguration timer expires, executing 560.

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

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 completes the reconfiguration.

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

Therefore, in the method for configuring a PDCP entity in the embodiment of the present application, the transmitting end sends the SN of the last PDU that is sent by using the first SN length to the receiving end, and instructs the receiving end to start the reconfiguration timer, so that the receiving end receives the reconfiguration timer. When the PDU carrying the SN or the timer expires, The PDCP entity at the receiving end is reconfigured to receive the PDU sent by the sending end or other sending end by using the second SN length, which reduces the packet loss during the reconfiguration process of the PDCP entity by the receiving end, and prevents the receiving end from receiving and sending. The delay caused by the PDU sent by the first SN length is too long, 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.

FIG. 6 is a schematic block diagram of a receiving device 600 in accordance with an embodiment of the present application. As shown in FIG. 6, the receiving device 600 includes a receiving unit 610 and a processing unit 620. among them:

The receiving unit 610 is configured to receive sequence number SN indication information sent by the first sending device, where the SN indication information is used to indicate that the first sending device sends the last data protocol unit to the receiving device by using the first SN length. SN of the PDU;

The processing unit 620 is configured to: when receiving the PDU carrying the SN, reconfigure the PDCP entity of the receiving apparatus, so that the receiving apparatus can receive the first by using the reconfigured PDCP entity The transmitting device uses the PDU transmitted by the second SN length or the PDU transmitted by the second transmitting device using the second SN length.

Therefore, the receiving apparatus of the embodiment of the present application receives the SN of the last PDU sent by the sending apparatus using the first SN length, and reconfigures the PDCP entity of the receiving apparatus when receiving the PDU carrying the SN, thereby avoiding Packet loss during PDCP entity reconfiguration.

Optionally, the processing unit 620 is further configured to: switch from the first sending device to the second sending device, before the receiving unit 610 receives the SN indication information sent by the first sending device, where the first sending device is used by The length of the SN for transmitting the PDU is the length of the first SN, and the length of the SN used by the second sending device to send the PDU is the length of the second SN;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the second sending device by using the second SN length.

Optionally, before the receiving unit 610 receives the SN indication information sent by the first sending device, the first sending device reconfigures the PDCP entity of the first sending device, so that the first sending device is After transmitting the last PDU to the receiving device by using the first SN length, the PDU can be sent to the receiving device by using the second SN length by the PDCP entity of the first sending device that is reconfigured;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the first sending device by using the second SN length.

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

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

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

It should be understood that the receiving device 600 may correspond to the receiving end in the method embodiment, and the corresponding function of the receiving end may be implemented. For brevity, no further details are provided herein.

FIG. 7 is a schematic block diagram of a transmitting device 700 in accordance with an embodiment of the present application. As shown in FIG. 7, the sending apparatus 700 includes a sending unit 710, and the sending unit 710 is configured to:

Sending sequence number SN indication information to the receiving device, the SN indication information being used to indicate the SN of the last PDU sent by the first sending device to the receiving device by using the first SN length, so that the receiving device is receiving When the PDU carrying the SN is carried, the PDCP entity of the receiving device is reconfigured.

Therefore, the transmitting apparatus of the embodiment of the present application transmits the SN indicating the last PDU transmitted by the sending apparatus using the first SN length to the receiving apparatus, so that the receiving apparatus receives the PDU carrying the SN, and then the receiving apparatus The PDCP entity performs reconfiguration to avoid packet loss during PDCP entity reconfiguration.

Optionally, the first sending device device further includes a processing unit 720, configured to: before the sending unit 710 sends the serial number SN indication information to the receiving device, to the first sending device Reconfiguring the PDCP entity to enable the first transmitting device to pass the reconfigured PDCP entity of the first transmitting device after transmitting the last PDU to the receiving device by using the first SN length, Transmitting a PDU to the receiving device by using the second SN length;

Optionally, before the sending unit 710 sends the SN indication information to the receiving device, the receiving device has switched from the first sending device to the second sending device, where the first sending device is configured to send the PDU. The SN length is the first SN length, and the SN length used by the second sending device to send the PDU is the second SN length;

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, and when receiving the PDU carrying the SN, the receiving device is configured by calling a control PDCP entity of the receiving device The data PDCP entity of the receiving device is reconfigured.

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

It should be understood that the receiving device 700 may correspond to the receiving end in the method embodiment, and the corresponding function of the receiving end may be implemented. For brevity, no further details are provided herein.

FIG. 8 is a schematic structural 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 for storing instructions, and the processor 810 is configured to execute instructions stored by the memory 830 to control the transceiver 820 to receive signals or send signals. among them,

The transceiver 820 is configured to receive the sequence number SN indication information sent by the first sending device, where the SN indication information is used to indicate that the first sending device sends the last data protocol unit to the receiving device by using the first SN length. SN of the PDU;

The processor 810 is configured to: when receiving the PDU carrying the SN, reconfigure the PDCP entity of the receiving apparatus, so that the receiving apparatus can receive the first by using the reconfigured PDCP entity The transmitting device uses the PDU transmitted by the second SN length or the PDU transmitted by the second transmitting device using the second SN length.

Optionally, the processor 810 is further configured to: switch from the first sending device to the second sending device before the transceiver 820 receives the SN indication information sent by the first sending device, where the first sending device is used by the first sending device The length of the SN for transmitting the PDU is the length of the first SN, and the length of the SN used by the second sending device to send the PDU is the length of the second SN;

Wherein the PDCP entity of the reconfigured receiving device is configured to receive the second sending device A PDU transmitted using the second SN length is placed.

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 is After transmitting the last PDU to the receiving device by using the first SN length, the PDU can be sent to the receiving device by using the second SN length by the PDCP entity of the first sending device that is reconfigured;

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, where the processor 810 is specifically configured to: when receiving the PDU carrying the SN, by calling the receiving device The PDCP entity is controlled to reconfigure the data PDCP entity of the receiving device.

Optionally, the transceiver 820 is configured to: send 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). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

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

In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 810 or an instruction in a form of software. The steps of the positioning method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor 810. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in memory 830, and processor 810 reads the information in memory 830 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.

The receiving apparatus 800 according to an embodiment of the present application may correspond to the method 200 described above for execution. The receiving end of 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 used to perform each action or process performed by the receiving end in the foregoing method 200, where Avoid the details and omit the detailed description.

FIG. 9 is a schematic structural diagram of a receiving device 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 communicate with each other through an internal connection path. The memory 930 is for storing instructions, and the processor 910 is configured to execute instructions stored by the memory 930 to control the transceiver 920 to receive signals or transmit signals. The transceiver 920 is specifically configured to:

Optionally, the processor 910 is configured to: before the transceiver 920 sends the sequence number SN indication information to the receiving device, reconfigure the PDCP entity of the first sending device, so that the first sending After transmitting the last PDU to the receiving device by using the first SN length, the device can send the second SN length to the receiving device by using the reconfigured PDCP entity of the first sending device. PDU;

Optionally, before the transceiver 920 sends the SN indication information to the receiving device, the receiving device has switched from the first transmitting device to the second transmitting device, and the first transmitting device is configured to send the PDU. The SN length is the first SN length, and the SN length used by the second sending device to send the PDU is the second SN length;

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, and the receiving device receives the PDU carrying the SN by calling the receiving device. Controlling the PDCP entity to reconfigure the data PDCP entity of the receiving device.

Optionally, the transceiver 920 is configured to: receive a reconfiguration complete 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). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 930 can include 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 a non-volatile random access memory. For example, the memory 930 can also store information of the device type.

In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 910 or an instruction in a form of software. The steps of the positioning method disclosed in the embodiment of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor 910. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 930, and the processor 910 reads the information in the memory 930 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

The receiving apparatus 900 according to the embodiment of the present application may correspond to the transmitting end for performing the method 200 in the foregoing method 200, and the transmitting end 700 according to the embodiment of the present application, and each unit or module in the sending apparatus 900 is used for respectively The operations or processes executed by the transmitting end in the above method 200 are performed. Here, in order to avoid redundancy, detailed description thereof will be omitted.

FIG. 10 is a schematic block diagram of a receiving device 1000 in accordance with an embodiment of the present application. As shown in FIG. 10, the receiving device 1000 includes a receiving unit 1010 and a processing unit 1020. among them,

The receiving unit 1010 is configured to receive the sequence number SN indication information and the triggering instruction sent by the first sending device, where the SN indication information is used to indicate that the first sending device sends the last one sent to the receiving device by using the first SN length. The SN of the data protocol unit PDU, the triggering instruction is used to instruct the receiving device to start a reconfiguration timer;

The processing unit 1020 is configured to start the reconfiguration timer according to the triggering instruction, and according to The SN indication information determines whether a PDU carrying the SN is received before the reconfiguration timer expires;

If the receiving unit 1010 receives the PDU carrying the SN before the reconfiguration timer expires, the processing unit 1020 is further configured to: when receiving the PDU carrying the SN, to the receiving device The PDCP entity is reconfigured, 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: when the reconfiguration timer expires, to the receiving device Reconfiguring the PDCP entity to enable the receiving device to receive, by the reconfigured PDCP entity, the PDU sent by the first sending device using the second SN length or the second transmitting device transmitting using the second SN length PDU.

Therefore, the receiving apparatus in the embodiment of the present application receives the SN of the last PDU sent by the sending apparatus using the first SN length, and starts the reconfiguration timer, so that the receiving apparatus receives the PDU carrying the SN or the timer is super At the same time, the PDCP entity at the receiving end is reconfigured to receive the PDU transmitted by the transmitting device or other transmitting device using the second SN length, which reduces the packet loss during the reconfiguration of the PDCP entity by the receiving device, and prevents the receiving device. The delay caused by the receiving transmitting device using the PDU transmitted by the first SN length is too long, so that the receiving device can receive as much as possible the generated transmitting device transmits using the first SN length within the preset duration of the configuration timer. PDU.

Optionally, the processing unit 1020 is further configured to: switch from the first sending device to the second sending device, before the receiving unit 1010 receives the SN indication information and the triggering command sent by the first sending device, The SN length of the first sending device used to send the PDU is the first SN length, and the SN length used by the second sending device to send the PDU is the second SN length;

Optionally, before the receiving unit 1010 receives the sequence number SN indication information and the triggering instruction sent by the first sending device, the first sending device reconfigures the PDCP entity of the first sending device, so that After the first transmitting device sends the last PDU to the receiving device by using the first SN length, the first sending device can use the second SN length direction by using the reconfigured PDCP entity of the first sending device. The receiving device sends a PDU;

Optionally, the receiving unit 1010 is further configured to: before receiving the SN indication information and the triggering instruction sent by the first sending apparatus, receive the high layer signaling sent by the first sending apparatus, where the high layer signaling includes the Reconfigure the preset duration information of the timer.

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, where the processing unit 1020 is specifically configured to: by calling a PDCP entity of the receiving device, data PDCP of the receiving device The entity is reconfigured.

It should be understood that the receiving device 1000 may correspond to the receiving end in the method embodiment, and the corresponding function of the receiving end may be implemented. For brevity, no further details are provided herein.

FIG. 11 is a schematic block diagram of a transmitting device 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 sending unit 1110 is configured to:

Sending sequence number SN indication information and a triggering instruction to the receiving device, the SN indication information being used to indicate an SN of the last data protocol unit PDU sent by the first sending device to the receiving device by using the first SN length, The triggering instruction is used to instruct the receiving device to start a reconfiguration timer, so that the receiving device performs the PDCP entity of the receiving device when receiving the PDU carrying the SN or when the reconfiguration timer expires Reconfiguration.

Therefore, the transmitting apparatus of the embodiment of the present application transmits the SN indicating the last PDU sent by the sending apparatus by using the first SN length to the receiving apparatus, and instructs the receiving apparatus to start the reconfiguration timer, so that the receiving apparatus receives the carrying When the SN PDU or the timer expires, the PDCP entity at the receiving end is reconfigured to receive the PDU sent by the sending device or other sending device using the second SN length, which reduces the receiving device to reconfigure the PDCP entity. The packet is lost, and the delay caused by the receiving device when receiving the PDU transmitted by the transmitting device using the first SN length is too long, so that the receiving device can receive the transmitting device as much as possible within the preset time period of configuring the timer. A generated PDU transmitted by an SN length.

Optionally, the sending device further includes a processing unit 1120, configured to: before the sending unit 1110 sends the sequence number SN indication information and the triggering instruction to the receiving device, to the first sending device The PDCP entity performs reconfiguration such that the first transmitting device can pass the last PDU after sending the last PDU to the receiving device by using the first SN length Reconfiguring the PDCP entity of the first sending device to send the PDU to the receiving device by using the second SN length;

Optionally, before the first sending device sends the serial number SN indication information and the triggering instruction to the receiving device, the receiving device has switched from the first sending device to the second sending device, the first The SN length of the sending device for transmitting the PDU is the first SN length, and the SN length of the second sending device for transmitting the PDU is the second SN length;

Optionally, the sending unit 1110 is further configured to: before sending the SN indication information and the triggering instruction to the receiving apparatus, send the high layer signaling to the receiving apparatus, where the high layer signaling includes the preprocessing of the reconfiguration timer. Set the length of information.

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, and when the receiving device receives the PDU carrying the SN or the reconfiguration timer expires, by calling the The control PDCP entity of the receiving device reconfigures the data PDCP entity of the receiving device.

It should be understood that the receiving device 1100 may correspond to the receiving end in the method embodiment, and the corresponding function of the receiving end may be implemented. For brevity, no further details are provided herein.

FIG. 12 is a schematic structural diagram of a receiving device 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 communicate with each other through an internal connection path. The memory 1230 is configured to store instructions for executing the instructions stored by the memory 1230 to control the transceiver 1220 to receive signals or transmit signals. among them,

The transceiver 1220 is configured to receive the serial number SN indication information and the triggering instruction sent by the first sending device, where the SN indication information is used to indicate that the first sending device sends the last one sent to the receiving device by using the first SN length. SN of the data protocol unit PDU, the trigger instruction is used to refer to Instructing the receiving device to initiate a reconfiguration timer;

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

If the transceiver 1220 receives the PDU carrying the SN before the reconfiguration timer expires, the processor 1210 is further configured to: when receiving the PDU carrying the SN, to the receiving device The PDCP entity is reconfigured, 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: when the reconfiguration timer expires, to the receiving device Reconfiguring the PDCP entity to enable the receiving device to receive, by the reconfigured PDCP entity, the PDU sent by the first sending device using the second SN length or the second transmitting device transmitting using the second SN length PDU.

Optionally, the processor 1210 is further configured to: switch from the first sending device to the second sending device before the transceiver 1220 receives the SN indication information and the triggering command sent by the first sending device, The SN length of the first sending device used to send the PDU is the first SN length, and the SN length used by the second sending device to send 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 device, the first sending device reconfigures the PDCP entity of the first sending device, so that After the first transmitting device sends the last PDU to the receiving device by using the first SN length, the first sending device can use the second SN length direction by using the reconfigured PDCP entity of the first sending device. The receiving device sends a PDU;

Optionally, the transceiver 1220 is further configured to: before receiving the SN indication information and the triggering instruction sent by the first sending apparatus, receive the high layer signaling sent by the first sending apparatus, where the high layer signaling includes the Reconfigure the preset duration information of the timer.

Optionally, the PDCP entity of the receiving device is a data PDCP entity of the receiving device, where the processor 1210 is specifically configured to: by calling a control PDCP entity of the receiving device, data PDCP of the receiving device The entity is reconfigured.

Optionally, the transceiver 1220 is further configured to: send a reconfiguration complete message 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). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

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

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1210 or an instruction in a form of software. The steps of the positioning method disclosed in the embodiment of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor 1210. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1230, and the processor 1210 reads the information in the memory 1230 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.

The receiving device 1200 according to the embodiment of the present application may correspond to the receiving end of the method 400 for performing the method 400, and the receiving end 1000 according to the embodiment of the present application, and each unit or module in the receiving device 1200 is used for The operations or processes executed by the receiving end in the above method 400 are performed. Here, in order to avoid redundancy, detailed description thereof will be omitted.

FIG. 13 is a schematic structural diagram of a receiving device 1300 according to an embodiment of the present application. As shown in FIG. 13, the receiving device 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 internal connection path. The memory 1330 is configured to store instructions for executing 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:

Sending sequence number SN indication information and triggering instruction to the receiving device, where the SN indication information is used The SN indicating the first data protocol unit PDU sent by the first sending device to the receiving device by using the first SN length, the triggering instruction is used to instruct the receiving device to start a reconfiguration timer, so that the The receiving device reconfigures the PDCP entity of the receiving device when receiving the PDU carrying the SN or when the reconfiguration timer expires.

Optionally, the sending device further includes a processor 1310, configured to: before the transceiver 1320 sends the sequence number SN indication information and the trigger instruction to the receiving device, to the first sending device Reconfiguring the PDCP entity to enable the first transmitting device to pass the reconfigured PDCP entity of the first transmitting device after transmitting the last PDU to the receiving device by using the first SN length, Transmitting a PDU to the receiving device by using the second SN length;

Optionally, the transceiver 1320 is further configured to: before sending the SN indication information and the triggering instruction to the receiving apparatus, send the high layer signaling to the receiving apparatus, where the high layer signaling includes the preprocessing of the reconfiguration timer. Set the length of information.

Optionally, the transceiver 1320 is further configured to: receive a reconfiguration complete 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 another general-purpose processor. Digital signal processor (DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

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

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1310 or an instruction in a form of software. The steps of the positioning method disclosed in the embodiment of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor 1310. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. 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 its hardware. To avoid repetition, it will not be described in detail here.

The receiving apparatus 1300 according to the embodiment of the present application may correspond to the transmitting end for performing the method 400 in the foregoing method 400, and the transmitting end 1100 according to the embodiment of the present application, and each unit or module in the sending apparatus 1300 is used for respectively The operations or processes executed by the transmitting end in the above method 400 are executed. Here, in order to avoid redundancy, detailed description thereof will be omitted.

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. The input interface 1401, the output interface 1402, the processor 1403, and the memory 1404 are interconnected by an internal connection path. . The processor 1403 is configured to execute code in the memory 1404.

Alternatively, when the code is executed, the processor 1403 can implement the method 200 performed by the receiving end in the method embodiment. For the sake of brevity, it will not be repeated here.

Alternatively, when the code is executed, the processor 1403 can implement the method 200 performed by the transmitting end in the method embodiment. For the sake of brevity, it will not be repeated here.

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

Alternatively, when the code is executed, the processor 1503 can implement the method 400 performed by the receiving end in the method embodiment. For the sake of brevity, it will not be repeated here.

Alternatively, when the code is executed, the processor 1503 may implement the method 400 performed by the transmitting end in the method embodiment. For the sake of brevity, it will not be repeated here.

It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

This function is implemented as a software functional unit and sold or used as a standalone product It can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a disk, or an optical disk. A medium that can store program code.

The above is only a specific embodiment of the present application, but the scope of protection of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application. , should be covered in the scope of protection of this application for personal gain. Therefore, the scope of protection of the embodiments of the present application should be determined by the scope of protection of the claims.

Claims

A method for configuring a packet data convergence protocol PDCP entity, the method comprising:

The receiving end receives the sequence number SN indication information sent by the first sending end, where the SN indication information is used to indicate the SN of the last data protocol unit PDU sent by the first sending end to the receiving end by using the first SN length;

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 first sending end by using the reconfigured PDCP entity. The PDU transmitted by the second SN length or the second transmitting end uses the PDU transmitted by the second SN length.
The method according to claim 1, wherein 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 transmitting the PDU is the first SN length, and the second sending end is used for sending The SN length of the PDU is the second SN length;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the second sending end by using the second SN length.
The method according to claim 1, wherein the first transmitting end reconfigures the PDCP entity of the first transmitting end before the receiving end receives the SN indication information sent by the first sending end, After the first transmitting end sends the last PDU to the receiving end by using the first SN length, the second SN length can be used by the PDCP entity of the first sending end that is reconfigured. Sending a PDU to the receiving end;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the first sending end by using the second SN length.
The method according to any one of claims 1 to 3, wherein the PDCP entity at the receiving end is a data PDCP entity of the receiving end, wherein the receiving end receives the PDU carrying the SN Reconfiguring the PDCP entity at the receiving end includes:

When receiving the PDU carrying the SN, the receiving end reconfigures the data PDCP entity of the receiving end by calling the controlling PDCP entity of the receiving end.
The method according to any one of claims 1 to 4, further comprising:

The receiving end sends a reconfiguration complete message to the first sending end.
The method according to any one of claims 1 to 5, wherein the receiving end is a terminal device, the first transmitting end is a network device; or the receiving end is a network device, the first The sender is a terminal device.
A method for configuring a packet data convergence protocol PDCP entity, the method comprising:

The receiving end receives the sequence number SN indication information and the triggering instruction sent by the sending end, where the SN indication information is used to indicate the SN of the last data protocol unit PDU sent by the first sending end to the receiving end by using the first SN length. The triggering instruction is used to instruct the receiving end to start a reconfiguration timer;

The receiving end starts the reconfiguration timer according to the triggering instruction, and determines, according to the SN indication information, whether a PDU carrying the SN is received before the reconfiguration timer expires;

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, or

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. And the PDU that is 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, by the PDCP entity that enables the receiving end to be reconfigured.
The method according to claim 7, wherein before the receiving end receives the SN indication information and the triggering 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 transmitting the PDU is the first SN length, and the second sending end is used for sending The SN length of the PDU is the second SN length;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the second sending end by using the second SN length.
The method according to claim 7, wherein the first transmitting end is configured to the PDCP entity of the first transmitting end before the receiving end receives the serial number SN indication information and the triggering instruction sent by the first transmitting end. Reconfiguration has been performed such that the first sender is using the After the first SN is sent to the receiving end, the first PDU can be sent to the receiving end by using the second SN length by the PDCP entity of the first sending end that is reconfigured;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the first sending end by using the second SN length.
The method according to any one of claims 7 to 9, wherein before the receiving end receives the SN indication information and the triggering instruction sent by the transmitting end, the method further includes:

The receiving end receives the high layer signaling sent by the first sending end, where the high layer signaling includes information about a preset duration of the reconfiguration timer.
The method according to any one of claims 7 to 10, wherein the PDCP entity at the receiving end is a data PDCP entity of the receiving end, wherein the receiving end reconfigures the PDCP entity of the receiving end ,include:

The receiving end reconfigures the data PDCP entity of the receiving end by calling a control PDCP entity of the receiving end.
The method according to any one of claims 7 to 11, wherein the method further comprises:

a reconfiguration complete message sent by the receiving end to the first sending end.
The method according to any one of claims 7 to 12, wherein the receiving end is a terminal device, the first transmitting end is a network device; or the receiving end is a network device, the first The sender is a terminal device.
A method for configuring a packet data convergence protocol PDCP entity, the method comprising:

The first sending end sends the sequence number SN indication information to the receiving end, where the SN indication information is used to indicate that the first sending end uses the first SN length to send the SN of the last PDU to the receiving end, so that the The receiving end reconfigures the PDCP entity of the receiving end when receiving the PDU carrying the SN.
The method according to claim 14, wherein before the first transmitting 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 pass the last PDU after sending the last PDU to the receiving end by using the first SN length. Reconfiguring the PDCP entity of the first sending end to send the PDU to the receiving end by using the second SN length;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the first sending end by using the second SN length.
The method according to claim 14, wherein before the first transmitting end sends the SN indication information to the receiving end, the receiving end has switched from the first transmitting end to the second sending end, The length of the SN used by the first sending end to send the PDU is the length of the first SN, and the length of the SN used by the second sending end to send the PDU is the length of the second SN;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the second sending end by using the second SN length.
The method according to any one of claims 14 to 16, wherein the PDCP entity at the receiving end is a data PDCP entity of the receiving end,

When receiving the PDU carrying the SN, the receiving end reconfigures the data PDCP entity of the receiving end by calling the controlling PDCP entity of the receiving end.
The method according to any one of claims 14 to 17, wherein the method further comprises:

The first sending end receives the reconfiguration complete message sent by the receiving end.
The method according to any one of claims 14 to 18, wherein the receiving end is a terminal device, the first transmitting end is a network device; or the receiving end is a network device, the first The sender is a terminal device.
A method for configuring a packet data convergence protocol PDCP entity, the method comprising:

The first sending end sends the sequence number SN indication information and the triggering instruction to the receiving end, where the SN indication information is used to indicate that the first sending end sends the last data protocol unit PDU to the receiving end by using the first SN length. The SN, the triggering instruction is used to instruct the receiving end to start a reconfiguration timer, so that the receiving end receives the PDU carrying the SN or when the reconfiguration timer expires The PDCP entity is reconfigured.
The method according to claim 20, wherein before the first transmitting end sends the sequence number SN indication information and the triggering 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 pass the last PDU after sending the last PDU to the receiving end by using the first SN length. Reconfiguring the PDCP entity of the first sending end to send the PDU to the receiving end by using the second SN length;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the first sending end by using the second SN length.
The method according to claim 20, wherein the receiving end has switched from the first transmitting end to the first transmitting end before transmitting the serial number SN indication information and the triggering instruction to the receiving end a second sending end, the SN length of the first transmitting end used to send the PDU is the first SN length, and the SN length used by the second sending end to send the PDU is the second SN length;

The PDCP entity of the receiving end that is reconfigured is configured to receive the PDU that is sent by the second sending end by using the second SN length.
The method according to any one of claims 20 to 22, wherein before the first transmitting end sends the SN indication information and the triggering instruction to the receiving end, the method further includes:

The first sending end sends high layer signaling to the receiving end, where the high layer signaling includes information of a preset duration of the reconfiguration timer.
The method according to any one of claims 20 to 23, wherein the PDCP entity at the receiving end is a data PDCP entity of the receiving end,

The receiving end reconfigures the data PDCP entity of the receiving end by calling the controlling PDCP entity of the receiving end when receiving the PDU carrying the SN or when the reconfiguration timer expires.
The method according to any one of claims 20 to 24, wherein the method further comprises:

The first sending end receives the reconfiguration complete message sent by the receiving end.
The method according to any one of claims 20 to 25, wherein the receiving end is a terminal device, the first transmitting end is a network device; or the receiving end is a network device, the first The sender is a terminal device.
A receiving device, characterized in that the receiving device comprises:

a receiving unit, configured to receive sequence number SN indication information sent by the first sending device, where the SN indication information is used to indicate that the first sending device sends the last data protocol unit PDU to the receiving device by using the first SN length. SN;

a processing unit, configured to: when receiving the PDU carrying the SN, reconfigure a PDCP entity of the receiving device, so that the receiving device can receive the first sending by using the reconfigured PDCP entity The device transmits the PDU or the second transmitting device using the second SN length A PDU transmitted using the second SN length.
The receiving device according to claim 27, wherein the processing unit is further configured to:

Before the receiving unit receives the SN indication information sent by the first sending device, switching from the first sending device to the second sending device, where the SN length of the first sending device for transmitting the PDU is the An SN length, the SN length of the second sending device used to send the PDU is the second SN length;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the second sending device by using the second SN length.
The receiving device according to claim 27, wherein the first transmitting device has performed heavy on the PDCP entity of the first transmitting device before the receiving unit receives the SN indication information sent by the first transmitting device Configuring to enable the first transmitting device to use the PDCP entity of the first transmitting device by reconfiguring after transmitting the last PDU to the receiving device by using the first SN length Transmitting a PDU to the receiving device by a second SN length;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the first sending device by using the second SN length.
The receiving device according to any one of claims 27 to 29, wherein the PDCP entity of the receiving device is a data PDCP entity of the receiving device, wherein the processing unit is specifically configured to:

Upon receiving the PDU carrying the SN, the data PDCP entity of the receiving device is reconfigured by invoking a control PDCP entity of the receiving device.
The receiving device according to any one of claims 27 to 30, wherein the receiving device further comprises a transmitting unit, the transmitting unit is configured to:

A reconfiguration complete message is sent to the first transmitting device.
The receiving device according to any one of claims 27 to 31, wherein the receiving device is a terminal device, the first transmitting device is a network device; or the receiving device is a network device, the A transmitting device is a terminal device.
A receiving device, characterized in that the receiving device comprises:

a receiving unit, configured to receive a sequence number SN indication information and a triggering instruction sent by the first sending device, where the SN indication information is used to indicate that the first sending device uses the first SN length to Receiving, by the receiving device, an SN of a last data protocol unit PDU, where the triggering instruction is used to instruct the receiving device to start a reconfiguration timer;

a processing unit, configured to start, according to the triggering instruction, the reconfiguration timer, and determine, according to the SN indication information, whether a PDU carrying the SN is received before the reconfiguration timer expires;

If the receiving unit receives the PDU carrying the SN before the reconfiguration timer expires, the processing unit is further configured to: when receiving the PDU carrying the SN, the PDCP entity of the receiving device Reconfigure, 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: when the reconfiguration timer expires, the PDCP entity of the receiving device Performing reconfiguration to enable the receiving device to receive, by the PDCP entity of reconfiguration, the PDU transmitted by the first transmitting device using the second SN length or the PDU transmitted by the second transmitting device using the second SN length.
The receiving device according to claim 33, wherein the processing unit is further configured to:

Before the receiving unit receives the SN indication information and the triggering instruction sent by the first sending device, switching from the first sending device to the second sending device, where the SN length of the first sending device for transmitting the PDU is The first SN length, the SN length of the second sending device used to send the PDU is the second SN length;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the second sending device by using the second SN length.
The receiving apparatus according to claim 33, wherein before the receiving unit receives the serial number SN indication information and the triggering instruction sent by the first transmitting device, the first transmitting device is configured by the first transmitting device The PDCP entity has been reconfigured to enable the first transmitting device to pass the reconfigured PDCP entity of the first transmitting device after transmitting the last PDU to the receiving device using the first SN length Transmitting, by using the second SN length, the PDU to the receiving device;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the first sending device by using the second SN length.
The receiving device according to any one of claims 33 to 35, wherein the receiving unit is further configured to:

Before receiving the SN indication information and the triggering command sent by the first sending device, receiving the high layer signaling sent by the first sending device, where the high layer signaling includes information of a preset duration of the reconfiguration timer.
The receiving device according to any one of claims 33 to 36, wherein the PDCP entity of the receiving device is a data PDCP entity of the receiving device, wherein the processing unit is specifically configured to:

The data PDCP entity of the receiving device is reconfigured by invoking a control PDCP entity of the receiving device.
The receiving device according to any one of claims 33 to 37, wherein the receiving device further comprises a transmitting unit, the transmitting unit is configured to:

A reconfiguration complete message sent to the first transmitting device.
The receiving device according to any one of claims 33 to 38, wherein the receiving device is a terminal device, the first transmitting device is a network device; or the receiving device is a network device, the A transmitting device is a terminal device.
A transmitting device, wherein the transmitting device is a first transmitting device, the first transmitting device includes a sending unit, and the sending unit is configured to:

Sending sequence number SN indication information to the receiving device, the SN indication information being used to indicate the SN of the last PDU sent by the first sending device to the receiving device by using the first SN length, so that the receiving device is receiving When the PDU carrying the SN is carried, the PDCP entity of the receiving device is reconfigured.
The transmitting device according to claim 40, wherein the first transmitting device device further comprises a processing unit, the processing unit is configured to:

Reconfiguring the PDCP entity of the first transmitting device before the sending unit sends the sequence number SN indication information to the receiving device, so that the first transmitting device uses the first SN length to receive the After the device sends the last PDU, the PDU can be sent to the receiving device by using the second SN length by the PDCP entity of the first sending device that is reconfigured;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the first sending device by using the second SN length.
The transmitting apparatus according to claim 40, wherein said receiving apparatus has cut from said first transmitting apparatus before said transmitting unit transmits SN indication information to said receiving apparatus Switching to the second sending device, the SN length of the first transmitting device for transmitting the PDU is the first SN length, and the SN length of the second transmitting device for transmitting the PDU is the second SN length ;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the second sending device by using the second SN length.
The transmitting device according to any one of claims 40 to 42, wherein the PDCP entity of the receiving device is a data PDCP entity of the receiving device,

When receiving the PDU carrying the SN, the receiving device reconfigures the data PDCP entity of the receiving device by calling a control PDCP entity of the receiving device.
The transmitting device according to any one of claims 40 to 43, wherein the first transmitting device device further comprises a receiving unit, the receiving unit is configured to:

Receiving a reconfiguration complete message sent by the receiving device.
The transmitting device according to any one of claims 40 to 44, wherein the receiving device is a terminal device, the first transmitting device is a network device; or the receiving device is a network device, the A transmitting device is a terminal device.
A transmitting device, wherein the transmitting device is a first transmitting device, the first transmitting device includes a sending unit, and the sending unit is configured to:

Sending sequence number SN indication information and a triggering instruction to the receiving device, the SN indication information being used to indicate an SN of the last data protocol unit PDU sent by the first sending device to the receiving device by using the first SN length, The triggering instruction is used to instruct the receiving device to start a reconfiguration timer, so that the receiving device performs the PDCP entity of the receiving device when receiving the PDU carrying the SN or when the reconfiguration timer expires Reconfiguration.
The transmitting device according to claim 46, wherein the transmitting device further comprises a processing unit, the processing unit is configured to:

Before the sending unit sends the sequence number SN indication information and the triggering instruction to the receiving device, reconfiguring the PDCP entity of the first sending device, so that the first sending device is using the first SN length After the receiving device sends the last PDU, the PDU can be sent to the receiving device by using the second SN length by the PDCP entity of the first sending device that is reconfigured;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the first sending device by using the second SN length.
The transmitting apparatus according to claim 46, wherein said receiving apparatus has switched from said first transmitting apparatus to said before said first transmitting means transmits serial number SN indicating information and a triggering instruction to said receiving means The second sending device, the SN length of the first sending device for transmitting the PDU is the first SN length, and the SN length of the second sending device for transmitting the PDU is the second SN length;

The PDCP entity of the receiving device that is reconfigured is configured to receive a PDU that is sent by the second sending device by using the second SN length.
The transmitting device according to any one of claims 46 to 48, wherein the transmitting unit is further configured to:

Before transmitting the SN indication information and the triggering instruction to the receiving device, the high-level signaling is sent to the receiving device, where the high-level signaling includes information of a preset duration of the reconfiguration timer.
The transmitting device according to any one of claims 46 to 49, wherein the PDCP entity of the receiving device is a data PDCP entity of the receiving device,

The receiving device, when receiving the PDU carrying the SN or when the reconfiguration timer expires, reconfigures the data PDCP entity of the receiving device by calling a control PDCP entity of the receiving device.
The transmitting device according to any one of claims 46 to 50, wherein the first transmitting device device further comprises a receiving unit, the receiving unit is configured to:

Receiving a reconfiguration complete message sent by the receiving device.
The transmitting device according to any one of claims 46 to 51, wherein the receiving device is a terminal device, the first transmitting device is a network device; or the receiving device is a network device, the A transmitting device is a terminal device.