A data transmission method and apparatus

Abstract

The present application proposes a data transmission method and apparatus applicable to a PDCP entity, where the PDCP entity is associated with an RLC entity of UM. The method includes determining a target operating mode of the PDCP entity and sending the data packets to a higher-layer protocol entity in sequential order based on the target operating mode. In the present application, different operating modes can be configured for the PDCP entity based on different service scenarios, improving the flexibility of data transmission of the PDCP entity. Moreover, each operating mode can perform reordering, and some operating modes can more quickly deliver data packets to the application service, thereby reducing latency. Some operating modes have the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

Description

Technical Field

[0001] This application relates to the field of mobile communications, and particularly to a data transmission method and apparatus. Background Art

[0002] Multimedia Broadcast and Multicast Service (MBMS) or Multicast Broadcast Service (MBS) can be transmitted through specific MRB radio bearers. MBS services can include normal MBS bearers and split MBS bearers. Among them, a normal MBS bearer includes a Packet Data Convergence Protocol (PDCP) entity associated with a Radio Link Control (RLC) entity. A split MBS bearer includes a PDCP associated with two RLC entities.

[0003] The RLC entity can adopt any one of the following three working modes according to the configuration of the network side:

[0004] Transparent Mode (TM): The data received from the Media Access Control (MAC) layer is directly passed through to the PDCP entity.

[0005] Unacknowledged Mode (UM): The data received from the MAC layer is packetized and then transmitted to the PDCP entity, but the RLC entity does not support feedback to the peer RLC entity on whether the RLC data packet is successfully received.

[0006] Acknowledged Mode (AM): The data received from the MAC layer is packetized and then transmitted to the PDCP entity. The RLC entity supports feedback to the peer RLC entity on whether the RLC data packet is successfully received. Then, the RLC entity can retransmit the data packets that have not been received according to the feedback message.

[0007] In the related art, the PDCP entity associated with the RLC entity adopting UM often directly delivers the received data packets to the high-layer protocol entity during the handover process. Summary of the Invention

[0008] The data transmission method, apparatus, communication device, and storage medium proposed in this application are used to solve the problem that the PDCP entity often directly delivers the received data packets to the high-layer protocol entity in the related art.

[0009] A data transmission method according to an embodiment of the first aspect of the present application is applicable to a PDCP entity, and the PDCP entity is associated with a UM RLC entity. The method includes: determining a target operating mode of the PDCP entity; and sending data packets to a higher-layer protocol entity in sequential order based on the target operating mode.

[0010] A data transmission device according to an embodiment of the second aspect of the present application is applicable to a PDCP entity, and the PDCP entity is associated with a UM RLC entity. The device includes: a mode determination module configured to determine a target operating mode of the PDCP entity; and a sending module configured to send data packets to a higher-layer protocol entity in sequential order based on the target operating mode.

[0011] A communication device according to an embodiment of the third aspect of the present application includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the data transmission method according to the embodiment of the first aspect of the present application, or the data transmission method according to the embodiment of the second aspect of the present application.

[0012] A computer storage medium according to an embodiment of the fourth aspect of the present application stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the data transmission method according to the embodiment of the first aspect of the present application, or the data transmission method according to the embodiment of the second aspect of the present application can be implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the accompanying drawings, where:

[0014] Figure 1 is a schematic diagram of a data transmission method provided by an embodiment of the present application;

[0015] Figure 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application;

[0016] Figure 3 is a schematic diagram of a reordering window provided by an embodiment of the present application;

[0017] Figure 4 is a schematic diagram of another data transmission method provided by an embodiment of the present application;

[0018] Figure 5 is a schematic diagram of another data transmission method provided by an embodiment of the present application;

[0019] Figure 6 Schematic diagram of another data transmission method provided by an embodiment of the present application;

[0020] Figure 7 Schematic diagram of another data transmission method provided by an embodiment of the present application;

[0021] Figure 8 Schematic diagram of a data transmission device provided by an embodiment of the present application;

[0022] Figure 9 Schematic diagram of another data transmission device provided by an embodiment of the present application;

[0023] Figure 10 Schematic diagram of a communication device provided by an embodiment of the present application. Detailed implementation manners

[0024] The embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the drawings, where the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary and are intended to explain the present application, and should not be construed as limiting the present application.

[0025] Figure 1 Flow schematic diagram of a data transmission method provided by an embodiment of the present application. The execution subject of this data transmission method is a PDCP entity, and it is associated with an RLC entity of UM. Optionally, at least one of the one or more RLC entities associated with the PDCP entity is configured as UM. Among them, the PDCP entity can be a PDCP entity in a UE or a network device. The PDCP entity in the UE and the PDCP entity in the network device are peer PDCP entities.

[0026] As Figure 1 shown, this data transmission method includes the following steps:

[0027] S101, determine the target working mode of the PDCP entity.

[0028] In the embodiments of the present application, multiple working modes are configured for the PDCP entity. The target working mode can be determined for the PDCP entity from multiple working modes by means of protocol agreement or configuration indication information.

[0029] As a possible implementation, the target operating mode of the PDCP entity can be determined by protocol agreement. Optionally, in response to the need to reconstruct the PDCP entity, determine the operating modes adopted by each radio link control (RLC) entity associated with the PDCP entity, and based on the operating modes adopted by the RLC entities, determine the target operating mode adopted by the PDCP entity.

[0030] As a possible implementation, each operating mode can have an identification information, and further, indication information can be configured, where the indication information is configured with the identification information of the target operating mode to be selected. The PDCP entity determines the target operating mode to be used based on the indication information.

[0031] S102, send the data packets to the higher layer protocol entity in sequence number order based on the target operating mode.

[0032] The operating mode of the PDCP entity can be one of the following operating modes:

[0033] Operating mode A, which is a direct delivery mode for the old protocol data unit (PDU) data packets stored in the PDCP entity. In some implementations, operating mode A can include a first operating mode and a second operating mode. Optionally, the first operating mode is marked as operating mode 1-1, and the second operating mode is marked as operating mode 1-2. This is only an example here and cannot be used as a limitation of this application.

[0034] Optionally, operating mode 1-1 can be that before receiving new data packets, the PDCP entity reorders all the old data packets stored, for example, in ascending order of the serial numbers, and then delivers them to the higher layer protocol entity in sequence number order. Further, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers them to the higher layer protocol entity in sequence number order.

[0035] Optionally, operating mode 1-2 can be that before receiving new data packets, the PDCP entity reorders all the old data packets stored, for example, in ascending order of the serial numbers, then delivers them to the higher layer protocol entity in order, and initializes the relevant variables of the reordering window. Further, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers them to the higher layer protocol entity in sequence number order.

[0036] It should be noted that operating mode 1-1 does not initialize the reordering window compared to operating mode 1-2, so that the data packets can be continuously sent using the packet numbers, thereby reducing the data transmission delay.

[0037] In working mode B, the PDCP entity waits for new data packets while storing the old data packets, and then delivers them after overall reordering. Optionally, before receiving new data packets, the PDCP entity first processes all the stored old data packets. Further, the PDCP entity receives and processes new data packets. The PDCP entity performs overall reordering on the processed old data packets and the processed new data together, and delivers them to the upper-layer protocol entity in sequence number order. In the embodiments of the present application, working mode B can be referred to as the third working mode.

[0038] As a possible implementation, the timer for reordering can be stopped. In some implementations, a reordering timer (t-Reordering) is preconfigured for reordering, which starts timing from the start of reordering and stops in response to reaching the reordering timing value. For example, before delivering a received data packet with a larger serial number to the upper-layer protocol entity, if a data packet with a smaller serial number has not been received, wait within the timing duration of the reordering timer for the data packet with a smaller serial number to arrive. In response to the reordering timer timing out, do not wait for the data packet with a smaller serial number and directly deliver the data packet with a larger serial number to the upper-layer protocol entity, and stop the reordering timer. That is, when the timing duration of the reordering timer is reached, the PDCP entity does not wait for the data packet with a smaller serial number that has not been received yet, and directly delivers the sorted received data packets to the upper-layer protocol entity.

[0039] The PDCP entity adopts a reordering window (reordering Window_) mechanism and performs reordering based on the data packet number (COUNT) of the data packets. The maximum number of PDCP COUNT numbers for which the PDCP entity can perform reordering is half of the maximum number of PDCP sequence numbers (Serial Number, SN), that is, the size of the reordering window Window_Size = 2[pdcp - SN - Size DL] – 1, where “pdcp - SN - SizeDL” is the number of bits of the PDCP SN.

[0040] In the embodiments of the present application, different working modes can be configured for the PDCP entity based on different service scenarios, improving the flexibility of data transmission of the PDCP entity. Moreover, reordering can be performed for each working mode. Working mode A can achieve a faster delivery of data packets to the application service, thus reducing latency. Working mode B has the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

[0041] Taking the target working mode configured for the PDCP entity as working mode 1 - 1 in working mode A, that is, the first working mode, as an example, the data transmission process of the PDCP entity will be explained below. Figure 2It is a schematic flowchart of another data transmission method provided in an embodiment of the present application. The execution entity of this data transmission method is a PDCP entity, and it is associated with an RLC entity using UM.

[0042] S201, determine the target operating mode of the PDCP entity.

[0043] Any possible implementation manner in the embodiments of the present application can be adopted for step S201, and will not be elaborated here.

[0044] S202, in response to the target operating mode being the first operating mode, before using the newly configured PDCP configuration information, send the first data packet received from the first connection to the higher layer protocol entity in the order of numbers.

[0045] It should be noted that, in order to distinguish the newly configured PDCP configuration information from the previously configured PDCP configuration information, in the embodiments of the present application, the previously configured PDCP configuration information is referred to as the first PDCP configuration information, and the newly configured PDCP configuration information is referred to as the second PDCP configuration information. That is to say, the first PDCP configuration information is the PDCP configuration information used by the PDCP entity before using the second PDCP configuration information.

[0046] For example, the network side configures to instruct the PDCP entity to adopt operating mode 1-1. Before receiving this configuration instruction, the old configuration adopted by this PDCP entity is the first PDCP configuration information. Optionally, when the network side configures to instruct the PDCP entity to adopt operating mode 1-1 or after that, the network side instructs the new configuration of this PDCP entity, and the newly adopted configuration of this PDCP entity is the second PDCP configuration information.

[0047] The following embodiments will illustrate the data transmission method provided in the present application using the first PDCP configuration information and the second PDCP configuration information.

[0048] Before using the second PDCP configuration information, according to the first PDCP configuration information, process the first data packet received from the first connection before sending it to the higher layer protocol entity, and send the processed first data packet to the higher layer protocol entity in the order of numbers.

[0049] For example, the first connection can be the source connection during the handover process, and the first data packet can be the data packet delivered by the RLC entity associated with the source connection to the PDCP entity.

[0050] In the embodiments of the present application, the data that has been received by the PDCP entity before using the second PDCP configuration information is included and referred to as the first data packet, and this first data packet is the old data stored in the PDCP entity.

[0051] Optionally, the first data may include at least one of the following:

[0052] PDU data packets cached by the PDCP entity;

[0053] PDU data packets received from the first connection before using the second PDCP configuration information; for example, if the PDCP entity is an entity on the UE side, the received PDU data packets may be the PDU data packets received from the source cell during the UE handover process.

[0054] PDU data packets delivered to the PDCP entity during the reconstruction process of the underlying protocol entity before using the second PDCP configuration information. For example, during the reconstruction process of the RLC entity, the data packets stored in the RLC entity are delivered to the PDCP entity.

[0055] For the first PDCP configuration information and the second PDCP configuration information, optionally, the PDCP configuration information at least includes: encryption algorithm and encryption key.

[0056] Optionally, the PDCP configuration information may further include at least one of the following:

[0057] Packet header decompression / compression configuration; wherein, the packet header decompression / compression configuration includes at least one of the following: Robust Header Compression (ROHC) configuration, Ethernet Header Compression (EHC) configuration. Optionally, the ROHC configuration includes ROH decompression / compression configuration; the EHC configuration includes EHC decompression / compression configuration.

[0058] Integrity protection algorithm and integrity protection key.

[0059] Optionally, the second PDCP configuration information further includes indication information for indicating whether the packet header decompression / compression configuration context configured in the first PDCP configuration information continues to be used.

[0060] For example, in the case where the ROHC configuration is configured, the second PDCP configuration information may further indicate whether the ROHC compression context configured in the first PDCP configuration information can continue to be used. In implementation, the second PDCP configuration information may carry the drb-ContinueROHC indication information, and use this drb-ContinueROHC indication information to indicate whether the ROHC compression context configured in the first PDCP configuration information can continue to be used.

[0061] For the case where the EHC configuration is configured, the second PDCP configuration information may further indicate whether the EHC compression context configured by the first PDCP configuration information can continue to be used. In implementation, the second PDCP configuration information may carry the drb-ContinueEHC indication information, and use this drb-ContinueEHC indication information to indicate whether the EHC compression context configured by the first PDCP configuration information can continue to be used.

[0062] Optionally, the second PDCP configuration information configures header decompression / compression and does not indicate that the header decompression / compression context configured by the first PDCP configuration information can continue to be used. The PDCP entity uses the header decompression / compression configured in the second PDCP configuration information to perform header decompression on the second data packet. For example, for ROHC, there is no indication of "drb-ContinueROHC", or for EHC, there is no indication of "drb-ContinueEHC", that is, there is no indication that the header decompression / compression context configured in the first PDCP configuration information can continue to be used. In this case, when the PDCP entity applies the header decompression / compression configuration configured in the second PDCP configuration information, the header decompression / compression configuration configured in the first PDCP configuration information is no longer available.

[0063] Optionally, the second PDCP configuration information configures header decompression / compression and indicates that the header decompression / compression context configured by the first PDCP configuration information can continue to be used. The PDCP entity uses the header decompression / compression configured in the first PDCP configuration information to perform header decompression on the second data packet. For example, for ROHC, there is an indication of "drb-ContinueROHC", or for EHC, there is an indication of "drb-ContinueEHC", that is, it indicates that the header decompression / compression context configured in the first PDCP configuration information can continue to be used. In this case, the PDCP entity applies the header decompression / compression configuration configured in the first PDCP configuration information to perform header decompression on the second data packet.

[0064] In the example of this application, the processing performed on the first data packet at least includes: decryption processing and reordering.

[0065] Before using the second PDCP configuration information, the PDCP entity reorders the received first data packets according to the first PDCP configuration information. In some implementations, the PDCP entity decrypts the first data packets according to the first PDCP configuration information, and reorders the decrypted first data packets according to their numbers.

[0066] Optionally, the processing performed on the first data packet may further include at least one of header decompression / compression processing and integrity verification processing.

[0067] It should be noted that in response to the header decompression / compression configuration being configured in the first PDCP configuration information, the processing of the first data packet may include header decompression / compression processing. Among them, the header decompression can be performed in the order of the data packet numbers. For example, the decompression can be performed in ascending order of the numbers.

[0068] In response to the integrity protection algorithm and integrity protection key being configured in the first PDCP configuration information, the processing of the first data packet may include integrity verification processing.

[0069] As a possible implementation, in response to the first data packet being a processed data packet, the PDCP entity no longer uses the first PDCP configuration information to perform the above processing on the first data packet. For example, decryption processing, header decompression / compression processing, and / or integrity verification processing. That is to say, before determining the target working mode adopted by the PDCP entity, if the PDCP entity has used the first PDCP configuration information to perform the above processing on the first data packet, the PDCP entity no longer uses the first PDCP configuration information for processing. For example, when the PDCP entity receives the first data packet, it generally immediately uses the first PDCP configuration information to decrypt the first data packet, and does not wait to decrypt after reordering according to the data packet numbers. In the embodiments of the present application, when receiving an indication of the working mode and the first data packet is a decrypted data packet, the PDCP entity does not perform a decryption process on the stored first data packet.

[0070] Furthermore, the PDCP entity reorders the processed first data packets in the order of the data packet numbers. For example, the reordering can be performed in ascending order of the data packet numbers.

[0071] The PDCP entity uses a reordering window mechanism to reorder the data packets. Figure 3 is a schematic diagram of the reordering window. As Figure 3As shown, the variable of the lower boundary of the reordering window is "RX_DELIV", and this "RX_DELIV" identifies the packet number of the first PDU packet that has not been delivered to the higher layer protocol entity. The PDCP entity updates the variable "RX_DELIV" of the lower boundary of the reordering window according to the packet numbers of the PDU packets delivered to the higher layer protocol entity. For the PDU packets waiting to be received, the PDCP entity starts a reordering timer. When this reordering timer times out, the PDCP entity ignores the "packet number of the PDU packet waiting to be received" and updates the lower boundary of the reordering window. If the PDCP receives a packet outside the reordering window, the PDCP entity discards this packet. The "RX_REORD" variable identifies the packet number of the packet that starts the reordering timer. Among them, "RX_NEXT" marks the packet number of the next PDU packet to be received. As Figure 3 As shown, the initial values of "RX_DELIV" and "RX_NEXT" of the PDCP entity are "0". When a PDU packet with the number "1" is received, it means that the PDU packet with the number "0" has not been received. The PDCP entity updates "RX_NEXT" to "2", and when it is necessary to start the reordering timer, sets "RX_REORD" to "2". When a PDU packet with the number "2" is received, "RX_NEXT" is updated to "3".

[0072] In the embodiment of the present application, when the PDCP entity adopts working mode 1-1, it directly delivers the first packet in the order of the numbers without waiting for the subsequent packets to be received.

[0073] When the PDCP entity reorders the first packet, there will be missing packet numbers in the reordering window. In the embodiment of the present application, the PDCP does not need to wait for the packets corresponding to the missing numbers to be received and can directly deliver the first packet to the higher layer protocol entity in the order of the numbers. For example, the PDCP entity processes the PDU packet -1 / 3 according to the first PDCP configuration information and delivers it to the higher layer protocol entity. Since the reordering window is not initialized, the PDCP entity will continue to use the previous numbers, receives the PDU packets -0 / 2 / 4, and the PDU packets -1 / 3 will create a vacancy in the reordering window. The PDCP entity can ignore receiving the PDU packets -1 / 3 corresponding to the missing numbers. For example, the reordering timer may not be started.

[0074] S203, after using the second PDCP configuration information, the second packet received from the second connection is sent to the higher layer protocol entity in the order of the numbers.

[0075] In some implementations, the PDCP entity processes the second data received from the second connection according to the second PDCP configuration information, and reorders the processed second data packets according to the packet numbers. For example, the second connection may be the target connection during a handover process. The second data packet may be a data packet delivered by the RLC entity associated with the target connection to the PDCP entity.

[0076] In the embodiments of the present application, the processing performed on the second data packet at least includes: decryption processing and reordering.

[0077] Optionally, the processing performed on the second data packet may further include at least one of header decompression / compression processing and integrity verification processing.

[0078] It should be noted that in response to the header decompression / compression configuration being configured in the second PDCP configuration information, the processing performed on the second data packet may include header decompression / compression processing.

[0079] In response to the integrity protection algorithm and integrity protection key being configured in the second PDCP configuration information, the processing performed on the second data packet may include integrity verification processing.

[0080] Furthermore, the PDCP entity reorders the processed second data packets in the order of the packet numbers. For example, the reordering may be performed in ascending order of the packet numbers.

[0081] In the embodiments of the present application, since the PDCP entity does not initialize the relevant variables of the reordering window, when the peer PDCP entity uses the second PDCP configuration information to number the new data packet, i.e., the second data packet, the number of the second data packet is the subsequent number of the number of the first data packet. Correspondingly, the number of the second data packet received by the PDCP entity is a consecutive number of the number of the first data packet and is the subsequent number of the number of the first data packet. For example, after the PDCP entity processes the PDU packet -1 / 3 using the first PDCP configuration information and delivers it to the higher layer protocol entity, since the reordering window is not initialized in working mode 1-1, the numbering of the data sent by the peer PDCP entity of this PDCP entity starts from 4, and the peer PDCP entity sends the PDU packet -4 / 5 to the PDCP entity.

[0082] Furthermore, the PDCP entity delivers the second data packets to the higher layer protocol entity in the reordered number order.

[0083] The description is given with the target working mode configured as working mode 1-1. Before receiving a new data packet or before using the second configuration information, the PDCP entity processes the stored first data packet according to the first PDCP configuration information, reorders the processed packets in the order of the packet numbers, for example, in ascending order, and delivers them to the upper-layer protocol entity in sequence. For example, in the first PDCP configuration information, an encryption configuration -1 and a header compression configuration -1 are configured for the PDCP entity. PDCP packets -2 and PDCP packet -4 are stored in the reordering window of the PDCP entity, and these packets are the first data packets received by the PDCP entity. If PDCP packets -2 / 4 have been decrypted by the encryption configuration -1 but not decompressed, the header compression configuration -1 needs to be used to decompress PDCP packets -2 / 4 and deliver them to the upper-layer protocol entity in the order of the packet numbers. That is to say, the PDCP entity does not need to wait for PDCP packet -1 and PDCP packet 3 to be received before delivering PDCP packets -1 / 2 / 3 / 4 to the upper-layer protocol entity in sequence.

[0084] In some embodiments, the above method of the embodiment of the present application may further include:

[0085] S204, feedback the packet number information of the first data packet delivered to the upper-layer protocol entity to the peer PDCP entity.

[0086] Among them, the number information includes at least one of the following:

[0087] The maximum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity;

[0088] The maximum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity plus 1;

[0089] The maximum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity minus 1;

[0090] The minimum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity;

[0091] The minimum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity plus 1;

[0092] The minimum number of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity minus 1;

[0093] The total data volume of the first data packets processed by the first PDCP configuration information and delivered to the upper-layer protocol entity.

[0094] In an embodiment of the present application, in response to a reconstruction indication for a PDCP entity and with the target operating mode configured as operating mode 1-1, the PDCP entity can obtain second PDCP configuration information at this time. Among them, the second PDCP configuration information configures encryption configuration-2 and header compression configuration-2. The PDCP entity receives a new data packet, that is, the second data packet, based on the second PDCP configuration information and processes the second data packet. That is to say, the PDCP entity decrypts the PDCP packet-2 / 4 using encryption configuration-2, decompresses it using header compression configuration-2, and then delivers it to the higher-layer protocol entity in the order of the packet numbers.

[0095] In an embodiment of the present application, when the target operating mode of the PDCP entity is configured as operating mode 1-1, data transmission is performed based on operating mode 1-1. Since there is no need to wait for missing data packets, it is possible to more quickly deliver the data packets to the application service, thereby reducing the latency. Moreover, operating mode 1-1 does not initialize the reordering window, so the packet numbers can be continuously used for data transmission, thereby reducing the data transmission latency.

[0096] Taking the target operating mode configured for the PDCP entity as operating mode 1-2 in operating mode A, that is, the second operating mode, as an example, the data transmission process of the PDCP entity will be explained below. Figure 4 It is a schematic flowchart of another data transmission method provided in an embodiment of the present application. The execution subject of this data transmission method is the PDCP entity and is associated with the RLC entity of the UM.

[0097] S401, determine the target operating mode of the PDCP entity.

[0098] S402, in response to the target operating mode being the second operating mode, before using the second PDCP configuration information, send the first data packet received from the first connection to the higher-layer protocol entity in the order of the numbers.

[0099] Regarding steps S401 to S402, any possible implementation manner in the embodiments of the present application can be adopted, and will not be elaborated here.

[0100] S403, initialize the relevant variables of the reordering window.

[0101] Continue to refer to Figure 3 As shown, in an embodiment of the present application, setting the relevant variables of the reordering window to the initial values includes at least one of the following:

[0102] Set the variable "used to mark the next data packet to be received" to the initial value. For example, "RX_NEXT" can be set to the initial value "0".

[0103] Set the variable "used to mark the lower boundary of the reordering window" to its initial value. For example, "RX_DELIV" can be set to the initial value "0".

[0104] S404: Based on the initialized reordering window, use the second PDCP configuration information to process the second data packet received from the second connection.

[0105] After initializing the reordering window, the relevant variables of the reordering window start counting from the initial value. Further, in the example of this application, the processing of the second data packet at least includes: decryption processing and reordering. Optionally, the processing of the second data packet may further include at least one of header decompression / compression processing and integrity verification processing.

[0106] It should be noted that when the header decompression / compression configuration is configured in the second PDCP configuration information, the processing of the second data packet may include header decompression / compression processing. When the integrity protection algorithm and the integrity protection key are configured in the second PDCP configuration information, the processing of the second data packet may include integrity verification processing.

[0107] After the PDCP entity processes the PDU packet - 1 / 3 using the first PDCP configuration information and delivers it to the higher-layer protocol entity, since the working mode 1-2 initializes the reordering window, the peer PDCP entity will re-number the numbers of the undelivered PDU packet - 2 / 4, that is, start sending from the initial number 0. Thus, there will be no number gap of number 1 / 3 in the reordering window as in the working mode 1-1.

[0108] S405: Send the second data packet to the higher-layer protocol entity in the order of the numbers.

[0109] Further, the PDCP entity reorders the processed second data packets in the order of the numbers of the data packets, and then sends the second data packets to the higher-layer protocol entity in the order of the numbers. For example, the reordering can be performed in ascending order of the numbers of the data packets.

[0110] For the introduction of the first PDCP configuration information and the second PDCP configuration information, reference can be made to the relevant content recorded in the above embodiments, which will not be elaborated here.

[0111] For the process of processing the first data packet based on the first PDCP configuration information and the process of processing the second data packet based on the second PDCP configuration information, reference can be made to the relevant content recorded in the above embodiments, which will not be elaborated here.

[0112] In the embodiments of the present application, when the target working mode of the PDCP entity is configured to be working mode 1-2, data transmission is performed based on working mode 1-2. Since the reordering window is initialized, there will be no missing numbers, and thus there is no need to wait for missing data packets, reducing the sorting delay. Therefore, it is possible to more quickly deliver data packets to the application service.

[0113] Taking the target working mode configured for the PDCP entity as working mode B, i.e., the third working mode, as an example, the data transmission process of the PDCP entity will be explained below. Figure 5 It is a schematic flowchart of another data transmission method provided in the embodiments of the present application. The execution subject of this data transmission method is the PDCP entity, and it is associated with the RLC entity of UM.

[0114] S501, determine the target working mode of the PDCP entity.

[0115] Regarding step S501, any possible implementation manner in the embodiments of the present application can be adopted, and details will not be described here again.

[0116] S502, in response to the target working mode being the third working mode, perform overall reordering on the first data packet and the second data packet according to their respective PDCP configuration information, and send them to the higher-layer protocol entity in the order of numbers.

[0117] It should be noted that the first data packet is the data packet received from the first connection. The first data packet corresponds to the first PDCP configuration information, and the first PDCP configuration information is the previously configured PDCP configuration information. Optionally, the first connection can be the source connection during the handover process, and the first data packet is the data packet sent by the RLC entity associated with the source connection to the PDCP entity.

[0118] The second data packet is the data packet received from the second connection. The second data packet corresponds to the second PDCP configuration information, and the second PDCP configuration information is the newly configured PDCP configuration information. Optionally, the second connection can be the target connection during the handover process, and the second data packet is the data packet sent by the RLC entity associated with the target connection to the PDCP entity.

[0119] Before the PDCP entity uses the second PDCP configuration information, it processes the first data packet using the first PDCP configuration information. Among them, this processing process can at least include decryption processing. The process of decrypting the first data packet using the first PDCP configuration information can refer to the relevant content recorded in the above embodiments, and details will not be described here.

[0120] The PDCP entity processes the second data packet using the second PDCP configuration information. Among them, the processing process may at least include decryption processing. The process of decrypting the second data packet using the second PDCP configuration information can refer to the relevant content recorded in the above embodiments and will not be elaborated here.

[0121] Further, the PDCP entity reorders the processed first data packet and the second data packet together, and after reordering, sends all the data packets to the upper layer protocol entity in the order of their numbers.

[0122] For example, the first PDCP configuration information configures the encryption configuration -1 and the header compression configuration -1 for the PDCP entity. The first data packets -2 / 4 are stored in the reordering window of the PDCP entity -1. These data packets have been decrypted using the encryption configuration -1, but the header has not been decompressed yet. The PDCP entity needs to wait until the second data packets -1 / 3 of the PDCP are received, then reorder the data packets -1 / 2 / 3 / 4 together, and then submit them to the upper layer protocol entity in the order of their numbers. Further, the target working mode configured for the PDCP is working mode B, and the second PDCP configuration information is provided. Among them, the second PDCP configuration information configures the encryption configuration -2 and the header compression configuration -2 for the PDCP entity. The PDCP entity decompresses the first data packets -2 / 4 using the header compression configuration -1 and stores them in the PDCP entity. The PDCP entity applies the encryption configuration -2 and the header compression configuration -2 configured in the second PDCP configuration information, decrypts the received second data packets -1 / 3 using the encryption configuration -2 and decompresses them using the header compression configuration -2. The PDCP entity submits all the data packets -1 / 2 / 3 / 4 to the upper layer protocol entity in the order of their numbers.

[0123] In the embodiment of the present application, when the target working mode of the PDCP entity is configured as working mode B, data transmission is performed based on working mode B. Working mode B has the function of supporting waiting for unsuccessfully received data packets, reducing the loss of data packets.

[0124] Figure 6 It is a schematic flowchart of another data transmission method provided in the embodiment of the present application. The execution subject of this data transmission method is the PDCP entity, and it is associated with the RLC entity of the UM.

[0125] S601, in response to the need to reconstruct the PDCP entity, determine the working mode adopted by the RLC entity associated with the PDCP entity.

[0126] In the embodiments of the present application, the target working mode of the PDCP entity can be determined by means of protocol agreement. The working modes adopted by the respective RLC entities associated with the PDCP entity often affect the working mode adopted by the PDCP entity. Therefore, in the protocol agreement, the target working mode of the PDCP entity can be agreed based on the working mode adopted by the RLC entity.

[0127] An indication to reconstruct the PDCP entity can be received. When this reconstruction indication is received, it triggers the determination of the working mode adopted by the RLC entity associated with the PDCP entity. The working mode adopted by the RLC entity can include: one of the working modes of AM, UM, and transparent mode, receiving data in multicast mode, and receiving data in unicast mode.

[0128] Optionally, whether the PDCP entity feeds back the data reception status also often affects the working mode of the PDCP entity.

[0129] S602, determine the target working mode of the PDCP entity based on at least one of the working mode adopted by the RLC entity and the data status feedback indication of the PDCP entity.

[0130] In response to the PDCP entity being only associated with a UM RLC entity, determine that the target working mode of the PDCP entity is working mode A, that is, one of the first working mode and the second working mode, namely working mode 1-1 and working mode 1-2. For example, the PDCP entity is an RLC entity associated with one or more UMs. When the PDCP entity is instructed to be reconstructed, the PDCP entity can adopt working mode A.

[0131] In response to at least one of the multiple RLC entities associated with the PDCP entity adopting the acknowledged mode AM, determine that the target working mode of the PDCP entity is the first working mode or the third working mode, that is, working mode 1-1 in working mode A or working mode B. For example, the PDCP entity is associated with 2 RLC entities, where RLC entity - 1 is configured as UM and RLC entity - 2 is configured as AM. When the PDCP entity is instructed to be reconstructed, the PDCP entity adopts working mode B.

[0132] In response to the PDCP entity needing to feedback the data reception status, determine that the target working mode of the PDCP entity is the first working mode or the third working mode, that is, working mode 1-1 in working mode A or working mode B. For example, the PDCP entity is associated with 2 RLC entities, where both RLC entity-1 and RLC entity-2 are configured with UM, but the PDCP entity needs to send the data reception status of the PDCP entity to the peer PDCP entity through RLC entity-2, that is, for example, a status report needs to be sent to the peer PDCP entity. When the PDCP entity is instructed to be reconstructed, the PDCP entity adopts working mode B.

[0133] In response to at least one of the multiple RLC entities associated with the PDCP entity receiving data through multicast, and at least one RLC entity receiving data through unicast, determine that the target working mode of the PDCP entity is the first working mode or the third working mode. That is, working mode 1-1 in working mode A or working mode B. For example, the PDCP entity is associated with 2 RLC entities, where RLC entity-1 is configured to receive data through point-to-multipoint (PTM), and RLC entity-2 is configured to receive data through point-to-point (PTP). When the PDCP entity is instructed to be reconstructed, the PDCP entity adopts working mode B.

[0134] For the specific introductions of working mode 1-1, working mode 1-2, and working mode B, reference can be made to the relevant content records in the above embodiments, which will not be elaborated here.

[0135] S603, send the data packets to the higher-layer protocol entity in sequential order based on the target working mode.

[0136] For step S603, any possible implementation manner in the embodiments of the present application can be adopted, which will not be elaborated here.

[0137] In the embodiments of the present application, different working modes can be configured for the PDCP entity based on different service scenarios, improving the flexibility of data transmission of the PDCP entity. Moreover, each working mode can perform reordering. Working mode A can more quickly deliver data packets to the application service, thereby reducing latency. Working mode B has the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

[0138] Figure 7 It is a schematic flowchart of another data transmission method provided in the embodiments of the present application. The execution subject of this data transmission method is the PDCP entity and is associated with RLC entities configured with UM.

[0139] S701, receive indication information, where the indication information carries identification information of a target working mode.

[0140] In the embodiments of the present application, each working mode can have an identification information, and thus the indication information can be configured, where the indication information is configured with the identification information of the target working mode to be selected. The PDCP entity can obtain the indication information and then extract the identification information of the target working mode.

[0141] S702, determine the target working mode of the PDCP entity based on the indication information.

[0142] For example, the identification information of the first working mode, i.e., working mode 1-1, can be A-1, the identification information of the second working mode, i.e., working mode 1-2, can be A-2, and the identification information of the third working mode, i.e., working mode B, can be B. For example, based on A-1 carried in reestablishPDCP, it can be indicated that the target working mode adopted by the PDCP entity is working mode 1-1; for another example, based on A-2 carried in reestablishPDCP, it can be indicated that the target working mode adopted by the PDCP entity is working mode 1-2; for another example, based on B carried in reestablishPDCP, it can be indicated that the target working mode adopted by the PDCP entity is working mode B.

[0143] S703, send the data packets to the higher layer protocol entity in sequential order based on the target working mode.

[0144] Regarding step S603, any possible implementation manner in the embodiments of the present application can be adopted, which will not be elaborated herein.

[0145] In the embodiments of the present application, different working modes can be configured for the PDCP entity based on different service scenarios, improving the flexibility of data transmission of the PDCP entity. Moreover, each working mode can be reordered. Working mode A can achieve more rapid delivery of data packets to the application service, thus reducing latency. Working mode B has the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

[0146] Corresponding to the data transmission methods provided in the above several embodiments, the present application further provides a data transmission device. Since the data transmission device provided in the embodiments of the present application corresponds to the Figures 1 - 7 data transmission methods provided in the above embodiments, the implementation manners of the data transmission methods are also applicable to the data transmission device provided in this embodiment and will not be described in detail in this embodiment.

[0147] Figure 8Schematic structural diagram of a data transmission device proposed in an embodiment of this application. The data transmission device is applicable to a PDCP entity, and the PDCP entity is associated with an RLC entity of UM. Optionally, at least one of the one or more RLC entities associated with the PDCP entity is configured as UM. Among them, the PDCP entity can be a PDCP entity in a UE or a network device. The PDCP entity in the UE and the PDCP entity in the network device are peer PDCP entities.

[0148] As Figure 8 shown, the data transmission device 800 includes: a mode determination module 81 and a transmission module 82.

[0149] Among them, the mode determination module 81 is configured to determine the target working mode of the PDCP entity;

[0150] The transmission module 82 is configured to send data packets to the higher-layer protocol entity in sequence based on the target working mode.

[0151] In the embodiment of this application, multiple working modes are configured for the PDCP entity. The target working mode can be determined for the PDCP entity from multiple working modes by means of protocol agreement or configuration indication information.

[0152] As a possible implementation manner, the target working mode of the PDCP entity can be determined by protocol agreement. Optionally, in response to the need to reconstruct the PDCP entity, the working modes adopted by each radio link control (RLC) entity associated with the PDCP entity are determined, and based on the working modes adopted by the RLC entities, the target working mode adopted by the PDCP entity is determined.

[0153] As a possible implementation manner, each working mode can have an identification information, and further, configuration indication information can be used. Among them, the identification information of the target working mode to be selected is configured in the indication information. The PDCP entity determines the target working mode to be used based on the indication information.

[0154] The working mode of the PDCP entity can be one of the following working modes:

[0155] Working mode A, which is a direct delivery mode for old protocol data unit (PDU) data packets stored in the PDCP entity. In some implementations, working mode A can include a first working mode and a second working mode. Optionally, the first working mode is marked as working mode 1-1, and the second working mode is marked as working mode 1-2. Here, this is only an example and cannot be used as a limitation condition of this application.

[0156] Optionally, in working mode 1-1, before receiving a new data packet, the PDCP entity reorders all the stored old data packets, for example, in ascending order of numbers, and then delivers them to the higher layer protocol entity in the order of numbers. Further, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers them to the higher layer protocol entity in the order of numbers.

[0157] Optionally, in working mode 1-2, before receiving a new data packet, the PDCP entity reorders all the stored old data packets, for example, in ascending order of numbers, then delivers them to the higher layer protocol entity in order, and initializes the relevant variables of the reordering window. Further, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers them to the higher layer protocol entity in the order of numbers.

[0158] It should be noted that working mode 1-1 does not initialize the reordering window compared with working mode 1-2, so that data can be continuously sent using the data packet numbers, thereby reducing the data transmission delay.

[0159] In working mode B, the old data packets stored in the PDCP entity wait until new data packets are received, and then are delivered in an overall reordering mode. Optionally, before receiving new data packets, the PDCP entity first processes all the stored old data packets. Further, the PDCP entity receives and processes new data packets. The PDCP entity performs an overall reordering on the processed old data packets and the processed new data, and delivers them to the higher layer protocol entity in the order of numbers. In the embodiments of the present application, working mode B can be referred to as the third working mode.

[0160] As a possible implementation, the timer for reordering can be stopped. In some implementations, a reordering timer (t-Reordering) is preconfigured for reordering, and timing starts from the beginning of reordering. In response to reaching the reordering timing value, the timer for reordering is stopped. For example, before delivering a data packet with a larger number received to the higher layer protocol entity, if a data packet with a smaller number has not been received, it waits within the timing duration of the reordering timer for the data packet with a smaller number to arrive. In response to the reordering timer timing out, it no longer waits for the data packet with a smaller number that has not been received, but directly delivers the data packet with a larger number to the higher layer protocol entity and stops the reordering timer. That is, when the timing duration of the reordering timer is reached, the PDCP entity no longer waits for the data packets with smaller numbers that have not been received, but directly delivers the received and sorted data packets to the higher layer protocol entity.

[0161] The PDCP entity adopts the reordering window mechanism and reorders packets according to the packet numbers (COUNT) of the data packets. The maximum number of PDCP COUNT numbers for which the PDCP entity can perform reordering is half of the maximum number of PDCP serial numbers (SN). That is to say, the size of the reordering window Window_Size = 2[pdcp - SN - Size DL] - 1, where "pdcp - SN - SizeDL" is the number of bits of the PDCP SN.

[0162] In the embodiments of the present application, different working modes can be configured for the PDCP entity based on different service scenarios, which improves the flexibility of data transmission of the PDCP entity. Moreover, reordering can be performed for each working mode. Working mode A can more quickly deliver data packets to the application service, thereby reducing latency. Working mode B has the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

[0163] Figure 9 The following is a schematic structural diagram of a data transmission device proposed in the embodiments of the present application. This data transmission device is applicable to the PDCP entity, and the PDCP entity is associated with the RLC entity of UM. Optionally, at least one of the one or more RLC entities associated with the PDCP entity is configured as UM. Among them, the PDCP entity can be a PDCP entity in a UE or a network device. The PDCP entity in the UE and the PDCP entity in the network device are peer PDCP entities.

[0164] As Figure 9 shown, the data transmission device 900 includes: a mode determination module 91 and a transmission module 92.

[0165] Among them, the mode determination module 91 is configured to determine the target working mode of the PDCP entity;

[0166] The transmission module 92 is configured to send data packets to the higher - layer protocol entity in numerical order based on the target working mode.

[0167] Optionally, the transmission module 92 includes: a first transmission unit 921 and a second transmission unit 922.

[0168] The first transmission unit 921 is configured to, in response to the target working mode being the first working mode, send the first data packets received from the first connection to the higher - layer protocol entity in numerical order before using the newly configured PDCP configuration information;

[0169] A second sending unit 922, configured to send the second data packets received from the second connection to a higher-layer protocol entity in sequential order after using the newly configured PDCP configuration information.

[0170] Optionally, the sending module 92 further includes: an initialization unit 923.

[0171] The initialization unit 913 is configured to initialize relevant variables of the reordering window after sending the first data packets to the higher-layer protocol entity in sequential order in response to the target operating mode being the second operating mode.

[0172] The second sending unit 922 is configured to process the second data packets using the newly configured PDCP configuration information based on the initialized reordering window.

[0173] Optionally, the sending module 92 is further configured to perform overall reordering on the first data packets and the second data packets according to their respective PDCP configuration information in response to the target operating mode being the third operating mode, and send them to the higher-layer protocol entity in sequential order;

[0174] wherein, the first data packets are the data packets received from the first connection, the first data packets correspond to the first PDCP configuration information, and the first PDCP configuration information is the previously configured PDCP configuration information;

[0175] The second data packets are the data packets received from the second connection, the second data packets correspond to the second PDCP configuration information, and the second PDCP configuration information is the newly configured PDCP configuration information.

[0176] Optionally, as Figure 9 shown, the data transmission device further includes: a timing stop module 93.

[0177] The timing stop module 93 is configured to stop the timer for reordering.

[0178] Optionally, the first data packets include at least one of the following:

[0179] PDU data packets cached in the PDCP entity;

[0180] PDU data packets received by the PDCP entity from the first connection before using the newly configured PDCP configuration information;

[0181] PDU data packets delivered to the PDCP entity during the reconstruction process of the underlying protocol entity.

[0182] Optionally, as Figure 9 shown, the data transmission device further includes: a processing module 94.

[0183] A processing module 94, configured to process a first data packet before sending it to a higher layer protocol entity according to first PDCP configuration information, and process a second data packet before sending it to the higher layer protocol entity according to second PDCP configuration information, where the second PDCP configuration information is newly configured PDCP configuration information.

[0184] Optionally, the first configuration information and the second PDCP configuration information each at least include: an encryption algorithm and an encryption key.

[0185] Optionally, the first configuration information and the second PDCP configuration information further include at least one of the following:

[0186] Packet header decompression / compression configuration;

[0187] Integrity protection algorithm and integrity protection key.

[0188] Optionally, the packet header decompression / compression configuration includes at least one of the following:

[0189] Robust Header Compression (ROHC) decompression / compression configuration;

[0190] Ethernet Header Compression (EHC) decompression / compression configuration.

[0191] Optionally, the second PDCP configuration information further includes indication information for indicating whether the packet header decompression / compression configuration context configured in the first PDCP configuration information continues to be used.

[0192] Optionally, the processing includes decryption processing and reordering.

[0193] Optionally, the processing further includes at least one of packet header decompression / compression processing and integrity verification processing.

[0194] Optionally, the processing module 94 is further configured to, in response to the first data packet being a decrypted data packet, not perform decryption processing on the first data packet.

[0195] Optionally, the processing module 94 is further configured to, in response to the PDCP configuration information configuring a packet header decompression / compression configuration, perform decompression / compression processing, and in response to the PDCP configuration information configuring an integrity protection algorithm and an integrity protection key, perform integrity verification processing.

[0196] Optionally, the first sending unit 921 is further configured to, in response to a missing packet number being generated for the first data packet in the reordering window, not wait for the packet corresponding to the missing packet number to be received.

[0197] Optionally, the second sending unit 922 is further configured to, in response to the peer PDCP entity numbering the second data packet using the newly configured PDCP configuration information, receive the second data packet with a number consecutive to that of the first data packet.

[0198] Optionally, the first sending unit 921 is configured to feedback the packet number information of the first data packet delivered to the upper layer protocol entity to the peer PDCP entity.

[0199] Optionally, the mode determination module 91 includes: a first determination unit 911 and a second determination unit 912.

[0200] The first determination unit 911 is configured to determine the working mode adopted by each radio link control (RLC) entity associated with the PDCP entity in response to the need to reconstruct the PDCP entity.

[0201] The second determination unit 912 is configured to determine the target working mode of the PDCP entity based on at least one of the working mode adopted by the RLC entity and the data status feedback indication of the PDCP entity.

[0202] Optionally, the second determination unit 912 is further configured to:

[0203] In response to the PDCP entity being only associated with RLC entities in UM mode, determine that the target working mode is the first working mode or the second working mode; or,

[0204] In response to at least one of the multiple RLC entities associated with the PDCP entity being in acknowledged mode (AM), determine that the target working mode is the first working mode or the third working mode; or,

[0205] In response to the PDCP entity needing to feedback the data reception status, determine that the target working mode is the first working mode or the third working mode; or,

[0206] In response to at least one of the multiple RLC entities associated with the PDCP entity receiving data through multicast and at least one RLC entity receiving data through unicast, determine that the target working mode is the first working mode or the third working mode.

[0207] Optionally, the mode determination module 91 is further configured to receive indication information, where the indication information carries the identification information of the target working mode, and determine the target working mode based on the indication information.

[0208] In the embodiments of the present application, different working modes can be configured for the PDCP entity based on different service scenarios, which improves the flexibility of data transmission of the PDCP entity. Moreover, reordering can be performed for each working mode. Working mode A can achieve faster delivery of data packets to the application service, thereby reducing latency. Working mode B has the function of supporting waiting for new data packets that have not been successfully received, which can reduce the loss of data packets.

[0209] According to the embodiments of the present application, the present application also provides a communication device and a readable storage medium.

[0210] As Figure 10 shown, the communication device includes: one or more processors 1100, a memory 1200, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. Each component is interconnected using different buses and can be mounted on a common motherboard or otherwise installed as required. The processor can process instructions executed within the communication device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In other embodiments, if necessary, multiple processors and / or multiple buses can be used in conjunction with multiple memories and multiple memories. Similarly, multiple communication devices can be connected, with each device providing some necessary operations (such as an array of servers, a set of blade servers, or a multi-processor system). Figure 10 In the example, one processor 1100 is taken.

[0211] The memory 1200 is the non-transitory computer-readable storage medium provided by the present application. Among them, the memory stores instructions executable by at least one processor, so that the at least one processor executes the data transmission method provided by the present application. The non-transitory computer-readable storage medium of the present application stores computer instructions, and the computer instructions are used to cause a computer to execute the data transmission method provided by the present application.

[0212] The memory 1200, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the data transmission method in the embodiments of the present application. The processor 1100 executes various functional applications and data processing of the server by running the non-transitory software programs, instructions, and modules stored in the memory 1200, that is, implements the data transmission method in the above method embodiments.

[0213] The memory 1200 may include a program storage area and a data storage area. The program storage area may store an operating system and application programs required for at least one function. The data storage area may store data created according to the use of the positioning communication device, etc. In addition, the memory 1200 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. Optionally, the memory 1200 may optionally include a memory remotely provided with respect to the processor 1100, and these remote memories may be connected to the positioning communication device through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0214] The communication device may further include: an input device 1300 and an output device 1400. The processor 1100, the memory 1200, the input device 1300, and the output device 1400 may be connected through a bus or other means. Figure 10 Taking the connection through the bus as an example.

[0215] The input device 1300 may receive input digital or character information, and generate key signal inputs related to the user settings and function controls of the positioning communication device, such as input devices like a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointing stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 1400 may include a display device, an auxiliary lighting device (e.g., an LED), and a haptic feedback device (e.g., a vibration motor), etc. The display device may include but is not limited to a liquid crystal display (LCD), a light-emitting diode (LED) display, and a plasma display. In some embodiments, the display device may be a touch screen.

[0216] Various embodiments of the systems and techniques described herein may be implemented in digital electronic circuit systems, integrated circuit systems, dedicated ASICs (application-specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and / or interpreted on a programmable system including at least one programmable processor, the programmable processor may be a dedicated or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0217] These computing procedures (also known as programs, software, software applications, or code) include machine instructions for a programmable processor and can implement these computing procedures using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0218] To provide for interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide for interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic, speech, or tactile input).

[0219] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0220] A computer system can include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0221] Those of ordinary skill in the art can understand that all or part of the steps carried out in implementing the above-mentioned embodiment methods can be completed by instructing relevant hardware through a program. The said program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0222] In addition, in each of the embodiments of the present invention, the functional units can be integrated in a processing module, or each unit can exist physically alone, or two or more units can be integrated in a module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0223] The above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disc, etc.

[0224] The above is only the preferred embodiment of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present invention.

Claims

1. A data transmission method, characterized in that, Applicable to a Packet Data Convergence Protocol (PDCP) entity, where the PDCP entity is associated with a Radio Link Control (RLC) entity in Unacknowledged Mode (UM). The method includes: Determine the target operating mode of the PDCP entity; Based on the target operating mode, send data packets to a higher layer protocol entity in sequential order by number; The method further includes: In response to the target operating mode being the first operating mode, before using the newly configured PDCP configuration information, send the first data packet received from the first connection to the higher layer protocol entity in sequential order by number; After using the newly configured PDCP configuration information, send the second data packet received from the second connection to the higher layer protocol entity in sequential order by number; In response to the target operating mode being the second operating mode, after sending the first data packet to the higher layer protocol entity in sequential order by number, initialize the relevant variables of the reordering window; Based on the initialized reordering window, process the second data packet using the newly configured PDCP configuration information.

2. The data transmission method according to claim 1, wherein It further includes: In response to the target operating mode being the third operating mode, perform overall reordering on the first data packet and the second data packet according to their respective PDCP configuration information, and send them to the higher layer protocol entity in sequential order by number; Wherein, the first data packet is a data packet received from the first connection, the first data packet corresponds to the first PDCP configuration information, and the first PDCP configuration information is the previously configured PDCP configuration information; The second data packet is a data packet received from the second connection, the second data packet corresponds to the second PDCP configuration information, and the second PDCP configuration information is the newly configured PDCP configuration information.

3. The data transmission method according to any one of claims 1-2, characterized in that, It further includes: Stop the timer for reordering.

4. The data transmission method according to any one of claims 1-2, characterized in that, The first data packet includes at least one of the following: PDU data packets cached within the PDCP entity; PDU data packets received by the PDCP entity from the first connection before using the newly configured PDCP configuration information; PDU data packets delivered to the PDCP entity during the reconstruction process of the underlying protocol entity.

5. The data transmission method according to any one of claims 1-2, characterized in that, It further includes: Process the first data packet according to the first PDCP configuration information before sending it to the higher layer protocol entity; Process the second data packet according to the second PDCP configuration information before sending it to the higher layer protocol entity, where the second PDCP configuration information is the newly configured PDCP configuration information.

6. The data transmission method according to claim 5, wherein The first PDCP configuration information and the second PDCP configuration information respectively include at least: an encryption algorithm and an encryption key.

7. The data transmission method according to claim 6, wherein The first PDCP configuration information and the second PDCP configuration information further include at least one of the following: Packet header decompression / compression configuration; Integrity protection algorithm and integrity protection key.

8. The data transmission method according to claim 7, wherein The packet header decompression / compression configuration includes at least one of the following: Robust Header Compression (ROHC) decompression / compression configuration; Ethernet Header Compression (EHC) decompression / compression configuration.

9. The data transmission method according to claim 7, wherein The second PDCP configuration information further includes indication information for indicating whether the packet header decompression / compression configuration context configured in the first PDCP configuration information continues to be used.

10. The data transmission method according to claim 5, characterized in that The processing includes decryption processing and reordering.

11. The data transmission method according to claim 10, characterized in that The processing further includes at least one of header decompression / compression processing and integrity verification processing.

12. The data transmission method according to claim 10, wherein It further includes: In response to the first data packet being a decrypted data packet, the decryption processing is not performed on the first data packet.

13. The data transmission method according to claim 11, wherein It further includes: In response to the PDCP configuration information configuring header decompression / compression configuration, the processing includes the decompression / compression processing; In response to the PDCP configuration information configuring an integrity protection algorithm and an integrity protection key, the processing includes integrity verification processing.

14. The data transmission method according to claim 1, wherein It further includes: In response to the first data packet generating a missing packet number in the reordering window, there is no need to wait for the data packet corresponding to the missing packet number to be received.

15. The data transmission method according to claim 1, wherein It further includes: In response to the peer PDCP entity numbering the second data packet using the newly configured PDCP configuration information, the number of the received second data packet is a consecutive number with the number of the first data packet.

16. The data transmission method according to claim 15, characterized in that, It further includes: The packet number information of the first data packet submitted to the higher layer protocol entity is fed back to the peer PDCP entity.

17. The data transmission method according to claim 1, wherein The determining the target working mode of the PDCP entity includes: In response to the need to reconstruct the PDCP entity, determining the working modes adopted by the respective radio link control (RLC) entities associated with the PDCP entity; Based on at least one of the working mode adopted by the RLC entity and the data status feedback indication of the PDCP entity, determining the target working mode of the PDCP entity.

18. The data transmission method according to claim 17, wherein The determining the target working mode of the PDCP entity based on at least one of the working mode adopted by the RLC entity and the data status feedback indication of the PDCP entity includes: In response to the PDCP entity being only associated with RLC entities in UM mode, determining the target working mode as the first working mode or the second working mode; or In response to at least one of the multiple RLC entities associated with the PDCP entity adopting the acknowledged mode (AM), determining the target working mode as the first working mode or the third working mode; or In response to the PDCP entity needing to feedback the data reception status, determining the target working mode as the first working mode or the third working mode; or In response to at least one of the multiple RLC entities associated with the PDCP entity receiving data through multicast and at least one RLC entity receiving data through unicast, determining the target working mode as the first working mode or the third working mode.

19. The data transmission method according to claim 18, wherein The determining the target working mode of the PDCP entity includes: Receiving indication information, where the indication information carries identification information of the target working mode; Based on the indication information, determining the target working mode.

20. A data transmission device, characterized in that, Applicable to a PDCP entity, the PDCP entity being associated with RLC entities in UM mode, the apparatus includes: A mode determination module configured to determine the target working mode of the PDCP entity; A sending module configured to send data packets to a higher layer protocol entity in sequential order based on the target working mode; The sending module is specifically configured as follows: In response to the target working mode being the first working mode, before using the newly configured PDCP configuration information, send the first data packet received from the first connection to the higher layer protocol entity in sequential order; After using the newly configured PDCP configuration information, send the second data packet received from the second connection to the higher layer protocol entity in sequential order; In response to the target working mode being the second working mode, after sending the first data packet to the higher layer protocol entity in sequential order, initialize the relevant variables of the reordering window; Based on the initialized reordering window, process the second data packet using the newly configured PDCP configuration information.

21. A communication device, characterized in that, Comprising: At least one processor; And A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method according to any one of claims 1 to 19.

22. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, and after being executed by a processor, the computer-executable instructions can implement the method according to any one of claims 1 to 19.

Images