Data switching method, communication equipment, communication device and medium

Abstract

The invention relates to a data switching method, communication equipment, a communication device and a medium. In the disclosure, when the source PDCP entity in the source cell acquires the data sent to the source RLC entity in the source cell, the data is not backed up, and the data is directly sent to the source RLC entity, so that the processing load increased by the source PDCP entity due to data backup is reduced. And when the source PDCP entity determines to execute data switching, the backup data is not used as switching data, but a switching data request message is sent to the source RLC entity so as to receive a switching data confirmation message sent by the source RLC entity. And the source PDCP entity extracts the address pointer of the switching data from the switching data confirmation message, and obtains the switching data based on the address pointer, thereby avoiding the problems that part of data is not backed up and the switching data is lost due to memory limitation of the source PDCP entity. And the source PDCP entity sends the switching data to the target PDCP entity in the target cell, and the switching data is complete and not lost.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of communication technology, and in particular to a data switching method, communication equipment, communication device and medium. Background Art

[0002] In wireless communication, when a user device moves from one cell (i.e., source cell) to another cell (i.e., target cell), a cell handover is required to keep the user device communicating without interruption. When performing a cell handover, a lossless handover is performed according to the communication service requirements, and the source cell data is switched to the target cell.

[0003] The Packet Data Convergence Protocol (PDCP) entity of the source cell needs to back up the sent data and use the backup data for switching when switching data. However, due to memory limitations, the PDCP entity of the source cell cannot completely cache all the sent data, resulting in the loss of switching data, and the backup data needs to be copied, increasing the processing load of the PDCP entity. Summary of the invention

[0004] At least one embodiment of the present disclosure provides a data switching method, a communication device, a communication apparatus, and a medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a data switching method, which is applied to a source cell during cell switching. The data switching method includes:

[0006] When the source PDCP entity in the source cell obtains data sent to the source RLC entity in the source cell, the data is not backed up, and the obtained data is directly sent to the source RLC entity;

[0007] When the source PDCP entity determines to perform data switching, it sends a data switching request message to the source RLC entity;

[0008] After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message;

[0009] The source PDCP entity obtains the switching data based on the address pointer and sends the switching data to the target PDCP entity in the target cell.

[0010] In some embodiments, the source PDCP entity determines to perform data switching, including:

[0011] The source PDCP entity receives an intra-base station cell switching request, an inter-base station cell switching request, an intra-base station re-establishment request or an inter-base station re-establishment request, and determines to perform data switching.

[0012] In some embodiments, sending a data switching request message to a source RLC entity includes:

[0013] The source PDCP entity sends a data switching request message to the source RLC entity via the confirmed mode data radio bearer AM DRB.

[0014] In some embodiments, the address pointer of the switching data carried in the switching data confirmation message includes:

[0015] Array of pointers to data packets addresses for switching data.

[0016] In some embodiments, sending the switching data to a target PDCP entity in a target cell includes:

[0017] If the data encryption algorithm is not enabled, the source PDCP entity directly sends the switching data to the target PDCP entity in the target cell; or,

[0018] If the data encryption algorithm is turned on, the source PDCP entity obtains the decrypted data of the switched data and sends the decrypted data to the target PDCP entity in the target cell.

[0019] In some embodiments, the source PDCP entity obtains decrypted data of the switching data, including:

[0020] The source PDCP entity sends the switching data to the hardware accelerator for decryption processing, and obtains the decrypted data from the hardware accelerator.

[0021] In some embodiments, the switching data confirmation message also carries the number of data packets of the switching data; the source PDCP entity obtains the switching data based on the address pointer, and sends the switching data to the target PDCP entity in the target cell, including:

[0022] The source PDCP entity obtains the data packet of the switching data based on the data packet address pointer array of the switching data;

[0023] If the number of data packets is greater than a preset first number threshold, the source PDCP entity sends the data packets of the switching data to the target PDCP entity in the target cell in multiple times, wherein the number of data packets sent each time is less than or equal to the first number threshold.

[0024] In a second aspect, the embodiment of the present disclosure further proposes a data switching method, which is applied to a source cell during cell switching. The data switching method includes:

[0025] After receiving the data sent by the source PDCP entity in the source cell, the source RLC entity in the source cell backs up the data;

[0026] After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data;

[0027] The source RLC entity sends a data switching confirmation message to the source PDCP entity. The data switching confirmation message carries an address pointer of the switching data.

[0028] In some embodiments, determining the switching data from the backed-up data includes:

[0029] The source RLC entity determines the unconfirmed data of the confirmation mode data radio bearer AM DRB as the switching data; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the sent data sequence number;

[0030] as well as,

[0031] The source RLC entity determines the unsent data of the AM DRB as the switching data; wherein the unsent data is the data that the AM DRB receives from the source PDCP entity and has not yet sent.

[0032] In some embodiments, switching the address pointer of the data includes:

[0033] Array of pointers to data packets addresses for switching data.

[0034] In some embodiments, the data switching method further includes:

[0035] If the number of data packets of the switched data is greater than a preset second number threshold, the source RLC entity splits the data packet address pointer array into a plurality of sub-arrays, and the number of elements in each sub-array is less than or equal to the second number threshold;

[0036] The source RLC entity sends a switching data confirmation message to the source PDCP entity, including:

[0037] The source RLC entity sends a plurality of switching data confirmation messages to the source PDCP entity, and each switching data confirmation message carries a subarray.

[0038] In a third aspect, an embodiment of the present disclosure further provides a communication device, which is applied to a source cell during cell switching, and the communication device includes a source PDCP entity and a source RLC entity;

[0039] When the source PDCP entity obtains data sent to the source RLC entity, it does not back up the data, but directly sends the obtained data to the source RLC entity;

[0040] When the source PDCP entity determines to perform data switching, it sends a data switching request message to the source RLC entity;

[0041] After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message;

[0042] The source PDCP entity obtains the switching data based on the address pointer and sends the switching data to the target PDCP entity in the target cell.

[0043] In a fourth aspect, an embodiment of the present disclosure further provides a communication device, which is applied to a source cell during cell switching, and the communication device includes a source PDCP entity and a source RLC entity;

[0044] After receiving the data sent by the source PDCP entity, the source RLC entity backs up the data;

[0045] After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data;

[0046] The source RLC entity sends a data switching confirmation message to the source PDCP entity. The data switching confirmation message carries an address pointer of the switching data.

[0047] In a fifth aspect, an embodiment of the present disclosure further provides a communication device, including a memory, a transceiver, and a processor:

[0048] A memory for storing a computer program; a transceiver for sending and receiving data under the control of a processor; a processor for reading the computer program in the memory and executing the data switching method of any embodiment of the first aspect or executing the data switching method of any embodiment of the second aspect.

[0049] In the sixth aspect, the embodiments of the present disclosure further propose a processor-readable storage medium, which stores a program, and the program is used to enable the processor to execute the data switching method of any embodiment of the first aspect or the data switching method of any embodiment of the second aspect.

[0050] In at least one embodiment of the present disclosure, when the source PDCP entity in the source cell obtains data to be sent to the source RLC entity in the source cell, the data is not backed up, and the obtained data is directly sent to the source RLC entity, thereby reducing the copy operation performed by the source PDCP entity due to the backup data, thereby reducing the processing load of the source PDCP entity. Furthermore, when the source PDCP entity determines to perform data switching, it does not use the backup data as the switching data, but sends a switching data request message to the source RLC entity in order to receive the switching data confirmation message sent by the source RLC entity. Thus, the source PDCP entity extracts the address pointer of the switching data from the switching data confirmation message, and obtains the switching data based on the address pointer of the switching data, thereby avoiding the problem of some data not being backed up and the switching data being lost due to memory limitations of the source PDCP entity. Finally, the source PDCP entity sends the obtained switching data to the target PDCP entity in the target cell to achieve data switching, and the switching data is intact and not lost. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure, and a person skilled in the art can also obtain other drawings based on these drawings.

[0052] Figure 1 A flowchart of a data switching method provided by an embodiment of the present disclosure;

[0053] Figure 2 A flowchart of another data switching method provided by an embodiment of the present disclosure;

[0054] Figure 3 A schematic diagram of a communication device provided in an embodiment of the present disclosure;

[0055] Figure 4 A schematic diagram of another communication device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0056] In order to more clearly understand the above-mentioned purposes, features and advantages of the present disclosure, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It is understood that the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. The specific embodiments described herein are only used to explain the present disclosure, rather than to limit the present disclosure. Based on the described embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in the field belong to the scope of protection of the present disclosure.

[0057] It should be noted that, in this document, relational terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0058] In the 5G (5th Generation Mobile Communication Technology) scenario, when intra-base station cell switching, inter-base station cell switching, intra-base station re-establishment, or inter-base station re-establishment occurs, the source PDCP entity in the source cell needs to perform source-side data switching in AM mode (Acknowledged Mode), where data switching means synchronizing the data originally processed by the source PDCP entity in the source cell to the target PDCP entity in the target cell for processing, so as to achieve cell switching without affecting the communication of user equipment. The source PDCP entity backs up the PDCP SDU (Service Data Unit) that is sent to the source RLC (Radio Link Control) entity but not confirmed by the source RLC entity, so that the backed-up data can be switched to the target cell when the downlink data is switched. This method has multiple defects:

[0059] (1) The backup buffer window size of the PDCP entity does not match the sending window size of the RLC entity (the default sending window of the RLC entity is N1. Due to memory limitations, the default buffer queue size of the PDCP entity is N2, where N1 is much larger than N2). Not all unconfirmed data packets of the RLC entity are saved. When there are more than N2 unconfirmed data packets, the PDCP entity will discard the old backup data. Data switching will cause the loss of data packets with SN (Sequence Number). The PDCP entity of the target cell will have a sorting timeout caused by packet loss, which increases the service plane delay.

[0060] (2) The PDCP entity needs to perform a backup copy operation on each downlink data packet, which increases the processing load of the PDCP entity and affects the overall performance of the base station in scenarios such as high traffic and multiple users or when burst data is sent.

[0061] (3) The confirmation data sent by the RLC entity to the PDCP entity is now a continuous packet confirmation. Only when the sending window TX_NEXT_ACK moves backward can all the data packets before TX_NEXT_ACK be confirmed. Among them, TX_NEXT_ACK is a variable representing the ACK state. The variable stores the SN value of the next RLC SDU to receive a positive ACK in sequence. The variable corresponds to the lower edge of the sending window. For discontinuous data packets that have received ACK, the PDCP entity will directly switch, resulting in repeated transmission of some data.

[0062] Based on at least one of the above defects, the embodiment of the present disclosure proposes to optimize the backup of PDCP entity downlink data (i.e., data sent to RLC entity), that is, to remove the PDCP entity backup, and when cell switching occurs and data switching is required, request cached data from the RLC entity and perform switching with SN data.

[0063] At least one embodiment of the present disclosure provides a data switching method, PDCP entity, RLC entity, device or medium. When the source PDCP entity in the source cell obtains the data sent to the source RLC entity in the source cell, the data is not backed up, and the data is directly sent to the source RLC entity, thereby reducing the processing load of the source PDCP entity increased by the backup data. Furthermore, when the source PDCP entity determines to perform data switching, it does not use the backup data as the switching data, but sends a switching data request message to the source RLC entity in order to receive the switching data confirmation message sent by the source RLC entity. Thus, the source PDCP entity extracts the address pointer of the switching data from the switching data confirmation message, and obtains the switching data based on the address pointer of the switching data, thereby avoiding the problem that some data is not backed up and the switching data is lost due to memory limitations of the source PDCP entity. Finally, the source PDCP entity sends the obtained switching data to the target PDCP entity in the target cell to achieve data switching, and the switching data is complete and not lost.

[0064] Figure 1 The present disclosure provides a flow chart of a data switching method, which is applied to a source cell during cell switching. Figure 1 As shown, the data switching method may include but is not limited to steps 101 to 104:

[0065] In step 101, when a source PDCP entity in a source cell obtains data to be sent to a source RLC entity in the source cell, the obtained data is directly sent to the source RLC entity without backing up the data.

[0066] In this embodiment, the data sent by the source PDCP entity to the source RLC entity is PDCP PDU (Protocol Data Unit). Different from the prior art, the source PDCP entity no longer backs up the data (such as data with SN) sent to the source RLC entity, so there is no need to apply for memory to copy the sent data, thereby reducing the processing load of the source PDCP entity.

[0067] In the present embodiment, since the source PDCP entity no longer backs up the transmitted data, unlike the prior art, the source PDCP does not need to set the length of the backup queue, thereby avoiding wasting resources. There is no problem in the prior art of setting the length of the backup queue too large, thereby wasting resources, nor is there the problem in the prior art of setting the length of the backup queue too small, thereby causing backup data to be cyclically overwritten and resulting in backup failure. The computational overhead of maintaining backup queue management is eliminated.

[0068] In this embodiment, since the source PDCP entity no longer backs up the transmitted data, unlike the prior art, when releasing the user or releasing the bearer, the source PDCP entity does not need to delete the backup queue.

[0069] In this embodiment, since the source PDCP entity no longer backs up the transmitted data, unlike the prior art, the source PDCP entity will not receive a notification message for deleting the backup data sent by the source RLC entity, thereby reducing signaling overhead.

[0070] In this embodiment, when the source PDCP entity obtains data to be sent to the source RLC entity, the data is not backed up. Therefore, the source PDCP entity obtains only one copy of the data and there is no backup. The source PDCP entity directly sends the obtained data to the source RLC entity, and the source RLC entity backs up the data.

[0071] In step 102, when the source PDCP entity determines to perform data switching, it sends a data switching request message to the source RLC entity.

[0072] In this embodiment, the source PDCP entity receives an intra-base station cell switching request, an inter-base station cell switching request, an intra-base station re-establishment request, or an inter-base station re-establishment request, and determines to perform data switching.

[0073] In this embodiment, when the source PDCP entity determines to perform data switching, since the source PDCP entity has no backup data, the source PDCP entity does not use the backup data as switching data, but sends a switching data request message to the source RLC entity to obtain the switching data.

[0074] In some embodiments, the source PDCP entity sends a data switching request message to the source RLC entity via an Acknowledged Mode Data Radio Bearer (AM DRB).

[0075] It should be noted that after the source PDCP entity sends a data switching request message to the source RLC entity, it does not perform SN data switching, but waits for the RLC entity to send a response message, namely, the data switching confirmation message mentioned below.

[0076] In step 103, after receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message.

[0077] In this embodiment, after receiving the switching data confirmation message, the source PDCP entity can extract the address pointer of the switching data carried in the switching data confirmation message, wherein the address pointer of the switching data is an address pointer generated by the source RLC entity based on the storage address of the switching data. It should be noted that the source PDCP entity and the source RLC reuse an address and can access each other.

[0078] In step 104, the source PDCP entity obtains switching data based on the address pointer, and sends the switching data to the target PDCP entity in the target cell.

[0079] In this embodiment, since the source PDCP entity and the source RLC share an address and can access each other, after the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message, it can obtain the switching data stored in the corresponding storage space based on the address pointer and send the switching data to the target PDCP entity in the target cell.

[0080] In this embodiment, the switching data obtained by the source PDCP entity based on the address pointer includes the following data 1 and data 2:

[0081] Data 1: unconfirmed data of the confirmed mode data radio bearer AM DRB; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the transmitted data sequence number. For example, the unconfirmed data between the confirmed data sequence number (TX_NEXT_ACK) and the transmitted data sequence number (TX_NEXT) carried by all DRBs in the user AM mode.

[0082] Data 2: unsent data of AM DRB, wherein the unsent data is data received by AM DRB from source PDCP but not sent. For example, all DRBs in user AM mode carry SDU data received from PDCP but not sent.

[0083] In some embodiments, the source PDCP entity may also send the received data sent by the core network as switching data to the target PDCP entity in the target cell.

[0084] It can be seen that in the above embodiments, when the source PDCP entity of the source cell obtains the data to be sent to the source RLC entity, it does not back up the data, but directly sends the obtained data to the source RLC entity, thereby reducing the copy operation performed by the source PDCP entity due to the backup data, thereby reducing the processing load of the source PDCP entity. Furthermore, when the source PDCP entity determines to perform data switching, it does not use the backup data as the switching data, but sends a switching data request message to the source RLC entity in order to receive the switching data confirmation message sent by the source RLC entity. Thus, the source PDCP entity extracts the address pointer of the switching data from the switching data confirmation message, and obtains the switching data based on the address pointer of the switching data, thereby avoiding the problem of some data not being backed up and the switching data being lost due to memory limitations of the source PDCP entity. Finally, the source PDCP entity sends the obtained switching data to the target PDCP entity in the target cell to achieve data switching, and the switching data is intact and not lost.

[0085] Based on the above embodiments, Figure 1 An implementation manner of sending the switching data to the target PDCP entity in the target cell in step 104 includes the following steps (A1) and (A2):

[0086] (A1) If the data encryption algorithm is not enabled, the source PDCP entity directly sends the switching data to the target PDCP entity in the target cell.

[0087] (A2) If the data encryption algorithm is turned on, the source PDCP entity obtains the decrypted data of the switched data and sends the decrypted data to the target PDCP entity in the target cell.

[0088] In this embodiment, the source PDCP entity sends the switching data to the hardware accelerator for decryption processing, obtains the decrypted data from the hardware accelerator, and the decrypted data is unencrypted switching data. Then the source PDCP entity sends the unencrypted switching data to the target PDCP entity in the target cell.

[0089] Based on the above embodiments, Figure 1 The address pointer of the switching data carried in the switching data confirmation message in step 103 includes: an array of address pointers of the data packets of the switching data. The switching data confirmation message may also carry the number of data packets of the switching data. Accordingly, Figure 1In step 104, the source PDCP entity obtains the switching data based on the address pointer and sends the switching data to the target PDCP entity in the target cell, including but not limited to the following steps (B1) and (B2):

[0090] (B1) The source PDCP entity obtains the data packet of the switching data based on the data packet address pointer array of the switching data.

[0091] (B2) If the number of data packets is greater than a preset first number threshold, the source PDCP entity sends the data packets of the switched data to the target PDCP entity in the target cell in multiple times, wherein the number of data packets sent each time is less than or equal to the first number threshold.

[0092] In this embodiment, in order to avoid a task execution taking a long time during the data switching process, the source PDCP entity sets a first quantity threshold, which can be understood as the maximum number of data packets processed each time, and the first quantity threshold can be set based on the performance of the baseband board. If the number of data packets of the acquired switching data is greater than the first quantity threshold, the source PDCP entity groups the data packets of the switching data, and the number of data packets in each group is less than or equal to the first quantity threshold, and then the source PDCP entity sends the data packets of the switching data to the target PDCP entity in the target cell in multiple times, wherein a group of data packets of the switching data is sent each time.

[0093] In some embodiments, if the number of data packets is less than or equal to a preset first number threshold, the source PDCP entity directly sends all data packets of the switched data to the target PDCP entity in the target cell at one time.

[0094] Figure 2 FIG. 1 is a flow chart of another data switching method provided by an embodiment of the present disclosure, and the data switching method is applied to a source cell during cell switching. Figure 2 As shown, the data switching method includes but is not limited to the following steps 201 to 203:

[0095] In step 201, after receiving data sent by a source PDCP entity in the source cell, a source RLC entity in the source cell backs up the data.

[0096] In this embodiment, the source PDCP entity no longer backs up the data, but the source RLC entity backs up the data after receiving the data sent by the source PDCP entity.

[0097] In step 202, after receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data.

[0098] In this embodiment, the data switching request message is a data switching request message sent by the source PDCP entity when determining to perform data switching. The source RLC entity determines the switching data from the backup data in response to the data switching request message.

[0099] In some embodiments, the source RLC entity determines the switching data from the backup data in two ways:

[0100] Method 1: The source RLC entity determines the unconfirmed data of the confirmation mode data radio bearer AM DRB as the switching data; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the transmitted data sequence number. For example, the source RLC entity determines the unconfirmed data between the confirmed data sequence number (TX_NEXT_ACK) and the transmitted data sequence number (TX_NEXT) of all DRB bearers in the user AM mode as the switching data.

[0101] Mode 2: The source RLC entity determines the unsent data of the AM DRB as the switching data; wherein the unsent data is the data received by the AM DRB from the source PDCP and not sent. For example, the source RLC entity determines the SDU data received and not sent by all DRBs carrying the user AM mode from the PDCP as the switching data.

[0102] In step 203, the source RLC entity sends a data switching confirmation message to the source PDCP entity. The data switching confirmation message carries an address pointer of the switching data.

[0103] In this embodiment, after the source RLC entity determines the switching data from the backup data, it can further determine the address pointer of the switching data, for example, generate the address pointer based on the storage address of the switching data. It should be noted that the source PDCP entity and the source RLC multiplex an address and can access each other.

[0104] In this embodiment, the source RLC entity carries the address pointer of the switching data in the switching data confirmation message, and sends the switching data confirmation message to the source PDCP entity. After receiving the switching data confirmation message, the source PDCP entity can extract the address pointer of the switching data carried in the switching data confirmation message, and then obtain the switching data stored in the corresponding storage space based on the address pointer, and send the switching data to the target PDCP entity in the target cell.

[0105] In some embodiments, the source RLC entity may carry the number of data packets of the switching data in addition to the address pointer of the switching data in the switching data confirmation message, so that the source PDCP entity can determine whether it is necessary to send the data packets of the switching data to the target PDCP entity in the target cell in batches based on the number of data packets of the switching data. For specific details, please refer to the aforementioned related embodiments and will not be repeated here.

[0106] In some embodiments, the source RLC entity may directly send the data packets of the switching data to the source PDCP entity. In order to prevent the loss of data packets due to a large number of data packets sent, the data packets may be forwarded in batches, and the number of data packets forwarded each time is less than or equal to a preset second quantity threshold, wherein the second quantity threshold may be determined based on the performance of the baseband board, for example, 512 data packets are forwarded per second). It should be noted that the second quantity threshold may be the same as or different from the first quantity threshold in the aforementioned embodiment.

[0107] Correspondingly, if the number of data packets of the switching data is greater than a preset second quantity threshold, the source RLC entity splits the data packet address pointer array into multiple sub-arrays, and the number of elements in each sub-array is less than or equal to the second quantity threshold. Furthermore, the source RLC entity may send multiple switching data confirmation messages to the source PDCP entity, each switching data confirmation message carrying a sub-array.

[0108] It can be seen that in the above disclosed embodiments, since the source PDCP entity no longer backs up data, the source PDCP entity does not need to apply for memory resources to back up data, but requests the source RLC entity to switch data, thereby saving memory resources.

[0109] In addition, since the source PDCP entity no longer backs up data, the source PDCP entity does not need to copy the sent data, thereby reducing the processing load of the source PDCP entity and reducing unnecessary memory operations, thereby improving system performance.

[0110] In addition, since the source RLC entity caches data, data for which ACK is not received continuously can be deleted in time in the cache queue of the source RLC entity, so that the switching data does not have duplicate data and has uniqueness.

[0111] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all described as a series of action combinations, but those skilled in the art can understand that the embodiments of the present disclosure are not limited by the described action sequence, because according to the embodiments of the present disclosure, some steps can be performed in other sequences or simultaneously. In addition, those skilled in the art can understand that the embodiments described in the specification are all optional embodiments.

[0112] A communication device provided by an embodiment of the present disclosure is applied to a source cell during cell switching, and the communication device includes a source PDCP entity and a source RLC entity.

[0113] When the source PDCP entity obtains data sent to the source RLC entity, it does not back up the data, but directly sends the obtained data to the source RLC entity;

[0114] When the source PDCP entity determines to perform data switching, it sends a data switching request message to the source RLC entity;

[0115] After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message;

[0116] The source PDCP entity obtains the switching data based on the address pointer and sends the switching data to the target PDCP entity in the target cell.

[0117] In some embodiments, the source PDCP entity determines to perform data switching, including:

[0118] The source PDCP entity receives an intra-base station cell switching request, an inter-base station cell switching request, an intra-base station re-establishment request or an inter-base station re-establishment request, and determines to perform data switching.

[0119] In some embodiments, sending a data switching request message to a source RLC entity includes:

[0120] The source PDCP entity sends a data switching request message to the source RLC entity via the confirmed mode data radio bearer AM DRB.

[0121] In some embodiments, the address pointer of the switching data carried in the switching data confirmation message includes:

[0122] Array of pointers to data packets addresses for switching data.

[0123] In some embodiments, sending the switching data to a target PDCP entity in a target cell includes:

[0124] If the data encryption algorithm is not enabled, the source PDCP entity directly sends the switching data to the target PDCP entity in the target cell; or,

[0125] If the data encryption algorithm is turned on, the source PDCP entity obtains the decrypted data of the switched data and sends the decrypted data to the target PDCP entity in the target cell.

[0126] In some embodiments, the source PDCP entity obtains decrypted data of the switching data, including:

[0127] The source PDCP entity sends the switching data to the hardware accelerator for decryption processing, and obtains the decrypted data from the hardware accelerator.

[0128] In some embodiments, the switching data confirmation message also carries the number of data packets of the switching data; the source PDCP entity obtains the switching data based on the address pointer, and sends the switching data to the target PDCP entity in the target cell, including:

[0129] The source PDCP entity obtains the data packet of the switching data based on the data packet address pointer array of the switching data;

[0130] If the number of data packets is greater than a preset first number threshold, the source PDCP entity sends the data packets of the switching data to the target PDCP entity in the target cell in multiple times, wherein the number of data packets sent each time is less than or equal to the first number threshold.

[0131] The embodiment of the present disclosure also provides a communication device, which is applied to a source cell during cell switching. The communication device includes a source PDCP entity and a source RLC entity.

[0132] After receiving the data sent by the source PDCP entity, the source RLC entity backs up the data;

[0133] After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data;

[0134] The source RLC entity sends a data switching confirmation message to the source PDCP entity. The data switching confirmation message carries an address pointer of the switching data.

[0135] In some embodiments, determining the switching data from the backed-up data includes:

[0136] The source RLC entity determines the unconfirmed data of the confirmation mode data radio bearer AM DRB as the switching data; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the sent data sequence number;

[0137] as well as,

[0138] The source RLC entity determines the unsent data of the AM DRB as the switching data; wherein the unsent data is the data that the AM DRB receives from the source PDCP entity and has not yet sent.

[0139] In some embodiments, switching the address pointer of the data includes:

[0140] Array of pointers to data packets addresses for switching data.

[0141] In some embodiments, the data switching method further includes:

[0142] If the number of data packets of the switched data is greater than a preset second number threshold, the source RLC entity splits the data packet address pointer array into a plurality of sub-arrays, and the number of elements in each sub-array is less than or equal to the second number threshold;

[0143] The source RLC entity sends a switching data confirmation message to the source PDCP entity, including:

[0144] The source RLC entity sends a plurality of switching data confirmation messages to the source PDCP entity, and each switching data confirmation message carries a subarray.

[0145] The embodiment of the present disclosure also provides a processor-readable storage medium, the processor-readable storage medium stores a program, and the program is used to enable the processor to execute the steps of each embodiment of the data switching method. The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid state drive (SSD)), etc.

[0146] Figure 3 A schematic diagram of a communication device provided in an embodiment of the present disclosure, such as Figure 3 As shown, the communication device provided in the embodiment of the present disclosure includes a memory 31, a transceiver 32, and a processor 33:

[0147] The memory 31 is used to store computer programs; the transceiver 32 is used to send and receive data under the control of the processor 33; the processor 33 is used to read the computer program in the memory 31 and execute:

[0148] When the source PDCP entity in the source cell obtains data sent to the source RLC entity in the source cell, the data is not backed up, and the obtained data is directly sent to the source RLC entity;

[0149] When the source PDCP entity determines to perform data switching, it sends a data switching request message to the source RLC entity;

[0150] After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message;

[0151] The source PDCP entity obtains the switching data based on the address pointer and sends the switching data to the target PDCP entity in the target cell.

[0152] In some embodiments, the source PDCP entity determines to perform data switching, including:

[0153] The source PDCP entity receives an intra-base station cell switching request, an inter-base station cell switching request, an intra-base station re-establishment request or an inter-base station re-establishment request, and determines to perform data switching.

[0154] In some embodiments, sending a data switching request message to a source RLC entity includes:

[0155] The source PDCP entity sends a data switching request message to the source RLC entity via the confirmed mode data radio bearer AM DRB.

[0156] In some embodiments, the address pointer of the switching data carried in the switching data confirmation message includes:

[0157] Array of pointers to data packets addresses for switching data.

[0158] In some embodiments, sending the switching data to a target PDCP entity in a target cell includes:

[0159] If the data encryption algorithm is not enabled, the source PDCP entity directly sends the switching data to the target PDCP entity in the target cell; or,

[0160] If the data encryption algorithm is turned on, the source PDCP entity obtains the decrypted data of the switched data and sends the decrypted data to the target PDCP entity in the target cell.

[0161] In some embodiments, the source PDCP entity obtains decrypted data of the switching data, including:

[0162] The source PDCP entity sends the switching data to the hardware accelerator for decryption processing, and obtains the decrypted data from the hardware accelerator.

[0163] In some embodiments, the switching data confirmation message also carries the number of data packets of the switching data; the source PDCP entity obtains the switching data based on the address pointer, and sends the switching data to the target PDCP entity in the target cell, including:

[0164] The source PDCP entity obtains the data packet of the switching data based on the data packet address pointer array of the switching data;

[0165] If the number of data packets is greater than a preset first number threshold, the source PDCP entity sends the data packets of the switching data to the target PDCP entity in the target cell in multiple times, wherein the number of data packets sent each time is less than or equal to the first number threshold.

[0166] Figure 3In the embodiment, the transceiver 32 is used to receive and send data under the control of the processor 33. The bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by the processor 33 and the memory represented by the memory 31 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 32 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 33 is responsible for managing the bus architecture and general processing, and the memory 31 may store data used by the processor 33 when performing operations.

[0167] Figure 3 In the embodiment, the processor 33 can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 33 or the instructions in the form of software. The processor 33 can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0168] Figure 4 A schematic diagram of another communication device provided in an embodiment of the present disclosure, such as Figure 4 As shown, the communication device provided in the embodiment of the present disclosure includes a memory 41, a transceiver 42, and a processor 43:

[0169] The memory 41 is used to store computer programs; the transceiver 42 is used to send and receive data under the control of the processor 43; the processor 43 is used to read the computer program in the memory 41 and execute:

[0170] After receiving the data sent by the source PDCP entity in the source cell, the source RLC entity in the source cell backs up the data;

[0171] After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data;

[0172] The source RLC entity sends a data switching confirmation message to the source PDCP entity. The data switching confirmation message carries an address pointer of the switching data.

[0173] In some embodiments, determining the switching data from the backed-up data includes:

[0174] The source RLC entity determines the unconfirmed data of the confirmation mode data radio bearer AM DRB as the switching data; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the sent data sequence number;

[0175] as well as,

[0176] The source RLC entity determines the unsent data of the AM DRB as the switching data; wherein the unsent data is the data that the AM DRB receives from the source PDCP entity and has not yet sent.

[0177] In some embodiments, switching the address pointer of the data includes:

[0178] Array of pointers to data packets addresses for switching data.

[0179] In some embodiments, the data switching method further includes:

[0180] If the number of data packets of the switched data is greater than a preset second number threshold, the source RLC entity splits the data packet address pointer array into a plurality of sub-arrays, and the number of elements in each sub-array is less than or equal to the second number threshold;

[0181] The source RLC entity sends a switching data confirmation message to the source PDCP entity, including:

[0182] The source RLC entity sends a plurality of switching data confirmation messages to the source PDCP entity, and each switching data confirmation message carries a subarray.

[0183] Figure 4 In the embodiment, the transceiver 42 is used to receive and send data under the control of the processor 43. The bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by the processor 43 and the memory represented by the memory 41 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 42 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 43 is responsible for managing the bus architecture and general processing, and the memory 41 may store data used by the processor 43 when performing operations.

[0184] Figure 4 In the embodiment, the processor 43 can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 43 or the instructions in the form of software. The processor 43 can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0185] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0186] Those skilled in the art will appreciate that although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features from different embodiments is meant to be within the scope of the present disclosure and to form different embodiments.

[0187] Those skilled in the art will appreciate that the description of each embodiment has its own emphasis, and for parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0188] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A data switching method, applied to a source cell during cell switching, the method comprising: When the source PDCP entity in the source cell acquires data to be sent to the source RLC entity in the source cell, the source PDCP entity does not back up the data, but directly sends the acquired data to the source RLC entity; When the source PDCP entity determines to perform data switching, sending a data switching request message to the source RLC entity; After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message; The source PDCP entity obtains switching data based on the address pointer, and sends the switching data to a target PDCP entity in a target cell.

2. The method according to claim 1, wherein: The source PDCP entity determines to perform data switching, including: The source PDCP entity receives an intra-base station cell switching request, an inter-base station cell switching request, an intra-base station re-establishment request or an inter-base station re-establishment request, and determines to perform data switching.

3. The method according to claim 1, wherein: The sending a data switching request message to the source RLC entity comprises: The source PDCP entity sends a data switching request message to the source RLC entity through an acknowledged mode data radio bearer AM DRB.

4. The method according to claim 1, wherein: The address pointer of the switching data carried in the switching data confirmation message includes: Array of pointers to data packets addresses for switching data.

5. The method according to claim 1, wherein: The sending the switching data to a target PDCP entity in a target cell includes: If the data encryption algorithm is not enabled, the source PDCP entity directly sends the switching data to the target PDCP entity in the target cell; or, If the data encryption algorithm is turned on, the source PDCP entity obtains the decrypted data of the switching data and sends the decrypted data to the target PDCP entity in the target cell.

6. The method according to claim 5, wherein: The source PDCP entity obtains the decrypted data of the switching data, including: The source PDCP entity sends the switching data to the hardware accelerator for decryption processing, and obtains the decrypted data from the hardware accelerator.

7. The method according to claim 4, wherein: The switching data confirmation message also carries the number of data packets of the switching data; The source PDCP entity acquires switching data based on the address pointer, and sends the switching data to a target PDCP entity in a target cell, including: The source PDCP entity acquires the data packet of the switching data based on the data packet address pointer array of the switching data; If the number of data packets is greater than a preset first number threshold, the source PDCP entity sends the data packets of the switching data to the target PDCP entity in the target cell multiple times, wherein the number of data packets sent each time is less than or equal to the first number threshold.

8. A data switching method, applied to a source cell during cell switching, the method comprising: After receiving the data sent by the source PDCP entity in the source cell, the source RLC entity in the source cell backs up the data; After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data; The source RLC entity sends a switching data confirmation message to the source PDCP entity, and the switching data confirmation message carries an address pointer of the switching data.

9. The method according to claim 8, wherein: The step of determining the switching data from the backed-up data includes: The source RLC entity determines the unconfirmed data of the confirmation mode data radio bearer AM DRB as the switching data; wherein the unconfirmed data is the unconfirmed data between the confirmed data sequence number and the sent data sequence number; as well as, The source RLC entity determines the unsent data of the AM DRB as switching data; wherein the unsent data is data that the AM DRB receives from the source PDCP entity and has not yet sent.

10. The method according to claim 8, wherein: The address pointer of the switching data includes: Array of pointers to data packets addresses for switching data.

11. The method according to claim 10, wherein: The method further comprises: If the number of data packets of the switched data is greater than a preset second number threshold, the source RLC entity splits the data packet address pointer array into a plurality of sub-arrays, and the number of elements of each sub-array is less than or equal to the second number threshold; The source RLC entity sends a switching data confirmation message to the source PDCP entity, including: The source RLC entity sends a plurality of switching data confirmation messages to the source PDCP entity, each of the switching data confirmation messages carrying one of the subarrays.

12. A communication device, applied to a source cell during cell handover, the communication device comprising a source PDCP entity and a source RLC entity; When the source PDCP entity obtains data to be sent to the source RLC entity, the source PDCP entity does not back up the data, but directly sends the obtained data to the source RLC entity; When the source PDCP entity determines to perform data switching, sending a data switching request message to the source RLC entity; After receiving the switching data confirmation message sent by the source RLC entity, the source PDCP entity extracts the address pointer of the switching data carried in the switching data confirmation message; The source PDCP entity obtains switching data based on the address pointer, and sends the switching data to a target PDCP entity in a target cell.

13. A communication device, applied to a source cell during cell handover, the communication device comprising a source PDCP entity and a source RLC entity; After receiving the data sent by the source PDCP entity, the source RLC entity backs up the data; After receiving the data switching request message sent by the source PDCP entity, the source RLC entity determines the switching data from the backup data; The source RLC entity sends a switching data confirmation message to the source PDCP entity, and the switching data confirmation message carries an address pointer of the switching data.

14. A communication device, characterized in that: Including memory, transceiver, processor: Memory for storing computer programs; A transceiver for sending and receiving data under the control of the processor; a processor for reading the computer program in the memory and executing the data switching method according to any one of claims 1 to 7 or the data switching method according to any one of claims 8 to 11.

15. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a program, and the program is used to enable the processor to execute the data switching method according to any one of claims 1 to 7 or the data switching method according to any one of claims 8 to 11.

Images