Data transmission method and device

Abstract

The present application provides a data transmission method and device applied to a PDCP entity, where the PDCP entity is associated with an RLC entity of a UM, and the method includes the steps of determining a target operation mode of the PDCP entity, and transmitting the data packets to an upper layer protocol entity in numerical order based on the target operation mode. In the present application, different operation modes can be set for the PDCP entity based on different service scenarios, thereby improving the flexibility of data transmission of the PDCP entity. Furthermore, each operation mode can be reordered. Furthermore, each operation mode can be pari-ordered, and some operation modes can pass data packets to the application service more quickly, thereby reducing delay. Some operation modes support a function of waiting for new data packets that have failed to be received, which can reduce data packet loss.

Description

[Technical field]

[0001] The present application relates to the field of mobile communications, and in particular to a data transmission method and device. [Background technology]

[0002] A Multimedia Broadcast and Multicast Service (MBMS) or a Broadcast and Multicast Service (MBS) can be transmitted over a specific MRB radio bearer. The MBS service can include a normal MBS bearer and a split MBS bearer. Here, the normal MBS bearer includes one Packet Data Convergence Protocol (PDCP) entity associating with one Radio Link Control (RLC) entity. The split MBS bearer includes one PDCP associating with two RLC entities.

[0003] The RLC entity can use one of the following three working modes, depending on the network configuration: Transparent Mode (TM): Data received from the Media Access Control (MAC) layer is transmitted transparently directly to the PDCP entity. Unacknowledged Mode (UM): Data group data packets received from the MAC layer are transmitted to the PDCP entity, but the RLC entity does not support feedback to the peer RLC entity on whether the RLC data packets were successfully received or not. Acknowledged Mode (AM): When a data group data packet received from the MAC layer is transmitted to a PDCP entity, and the RLC entity supports feedback to the other RLC entity about whether the RLC data packet was successfully received or not, the RLC entity can retransmit unreceived data packets based on the feedback message.

[0004] In the related art, a PDCP entity associated with an RLC entity using UM often passes data packets received during a switch directly to a higher layer protocol entity. Summary of the Invention

[0005] The data transmission method, device, communication device and storage medium provided in the present application are used to solve the problem that in the related art, the PDCP entity often passes the received data packet directly to the upper layer protocol entity.

[0006] An embodiment of a first aspect of the present application provides a data transmission method applied to a PDCP entity, the PDCP entity being associated with an RLC entity of a UM, the method comprising the steps of determining a target operation mode of the PDCP entity, and transmitting data packets in numerical order to an upper layer protocol entity based on the target operation mode.

[0007] An embodiment of a second aspect of the present application provides a data transmission apparatus applied to a PDCP entity, the PDCP entity being associated with an RLC entity of a UM, the apparatus including: a mode determination module configured to determine a target operation mode of the PDCP entity; and a transmission module configured to transmit data packets to an upper layer protocol entity in numerical order based on the target operation mode.

[0008] An embodiment of a third aspect of the present application provides a communications device, comprising at least one processor and a memory in communication with the at least one processor, the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor such that the at least one processor is capable of performing a data transmission method according to an embodiment of the first aspect of the present application or a data transmission method according to an embodiment of the second aspect of the present application.

[0009] An embodiment of a fourth aspect of the present application provides a computer storage medium having computer-executable instructions stored thereon, for implementing the data transmission method described in the embodiment of the first aspect of the present application or the data transmission method described in the embodiment of the second aspect of the present application. [Brief description of the drawings]

[0010] The above and / or additional aspects and advantages of the present application will become apparent and will be readily understood from the following detailed description of the embodiments taken in conjunction with the accompanying drawings. [Figure 1] FIG. 2 is a schematic diagram of a data transmission method provided by an embodiment of the present application; [Diagram 2] FIG. 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application; [Diagram 3] FIG. 2 is a schematic diagram of a reordering window provided by an embodiment of the present application; [Figure 4] FIG. 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application; [Diagram 5] FIG. 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application; [Figure 6] FIG. 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application; [Figure 7] FIG. 2 is a schematic diagram of another data transmission method provided by an embodiment of the present application; [Figure 8] FIG. 2 is a schematic diagram of a data transmission device provided by an embodiment of the present application; [Figure 9]FIG. 2 is a schematic diagram of another data transmission device provided by an embodiment of the present application; [Figure 10] 1 is a schematic diagram of a communication device provided by an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The embodiments of the present application will be described in detail below. An example of the embodiments is shown in the drawings. Here, the same or similar reference numerals throughout indicate the same or similar elements, or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are illustrative and are for explaining the present application, and should not be understood as limitations of the present application.

[0012] FIG. 1 is a schematic flow chart of a data transmission method provided by an embodiment of the present application. The data transmission method is performed by a PDCP entity and associated with an RLC entity of UM. Optionally, at least one RLC entity among one or more RLC entities associated with the PDCP entity is configured as UM. Here, the PDCP entity may 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.

[0013] As shown in FIG. 1, the data transmission method includes the following steps S101-S102.

[0014] S101, determining a target operation mode of a PDCP entity.

[0015] In an embodiment of the present application, to set multiple operation modes for a PDCP entity, a target operation mode can be determined for the PDCP entity from the multiple operation modes by protocol agreement or setting of indication information.

[0016] As a possible implementation, determining the target operation mode of the PDCP entity may be determined by a protocol agreement, and optionally, in response to a need to reconstruct the PDCP entity, determining the operation mode used by each Radio Link Control (RLC) entity associated with the PDCP entity, and determining the target operation mode to be used by that PDCP entity based on the operation mode used by the RLC entities.

[0017] In a possible implementation, an identification may be set for each operation mode, and then an indication may be set, where the identification of the target operation mode to be selected is set in the indication, and the PDCP entity determines the target operation mode to be used based on the indication.

[0018] S102, sending the data packets to an upper layer protocol entity in numerical order based on a target operation mode.

[0019] The operation mode of the PDCP entity may be one of the following operation modes:

[0020] The operation mode A is a mode for directly passing old protocol data unit (PDU) data packets stored in the PDCP entity. In some embodiments, the operation mode A can include a first operation mode and a second operation mode. Optionally, the first operation mode is denoted as operation mode 1-1, and the second operation mode is denoted as operation mode 1-2, which is an example and cannot be a limiting condition of the present application.

[0021] Alternatively, the operation mode 1-1 may be such that, before receiving a new data packet, the PDCP entity reorders all stored old data packets, for example in ascending numerical order, and then passes the packets to the upper layer protocol entity in numerical order. Furthermore, the PDCP entity continues to receive new data packets, reorders the new data packets, and then passes the packets to the upper layer protocol entity in numerical order.

[0022] Alternatively, in the operation mode 1-2, before receiving a new data packet, the PDCP entity may reorder all stored old data packets, for example, in ascending order, before passing the packets to the upper layer protocol entity in order and initialize the associated variables of the reordering window. Furthermore, the PDCP entity may continue to receive new data packets, reorder the new data packets, and then pass the packets to the upper layer protocol entity in order.

[0023] In addition, since the operation mode 1-1 does not initialize the reordering window for the operation mode 1-2, it is possible to continue transmitting data using the data packet number, and thus it is possible to reduce the data transmission delay.

[0024] The operation mode B is a mode in which old data packets stored in the PDCP entity are entirely reordered and passed on after a new data packet is received. Optionally, before receiving a new data packet, the PDCP entity first processes all the old data packets stored therein. Furthermore, the PDCP entity receives and processes a new data packet. The PDCP entity entirely reorders the processed old data packets together with the processed new data packets, and passes them to an upper layer protocol entity in numerical order. In the embodiment of the present application, the operation mode B can be referred to as a third operation mode.

[0025] As a possible implementation, the timer for reordering can be stopped. In some embodiments, a reordering timer (t-Reordering) for reordering is preset, counted when reordering is started, and the timer for reordering is stopped in response to reaching a reordering timing value. For example, if a data packet with a lower number has not been received before a received data packet with a higher number is passed to an upper layer protocol entity, the timer waits for the data packet with the lower number to arrive within the timing time of the reordering timer. In response to the reordering timing out, the data packet with the higher number is passed directly to the upper layer protocol entity without waiting for the data packet with the lower number, and the reordering timer is stopped. That is, when the timing time of the reordering timer has elapsed, the PDCP entity passes the existing received, sorted data packet directly to the upper layer protocol entity without waiting for the unreceived data packet with a lower number.

[0026] The PDCP entity uses a reordering window mechanism to perform reordering based on the data packet number (COUNT) of the data packets. The maximum number of PDCP COUNT numbers that the PDCP entity can reorder is half the maximum number of PDCP serial numbers (SN), that is, the size of the reordering window Window_Size = 2 [pdcp-SN-Size DL]-1 "pdcp-SN-SizeDL" is the number of bits of PDCP SN.

[0027] In the embodiment of the present application, different operation modes can be set for the PDCP entity according to different service scenarios, thereby improving the flexibility of data transmission of the PDCP entity. In addition, each operation mode can be reordered. Operation mode A can quickly deliver data packets to the application service, reducing delay. Operation mode B supports the function of waiting for new data packets that have failed to be received, reducing data packet loss.

[0028] The data transmission process of the PDCP entity will be described below by taking as an example the target operation mode set in the PDCP entity as operation mode 1-1 of operation mode A, i.e., the first operation mode. Figure 2 is a schematic flow chart of another data transmission method provided in an embodiment of the present application. The data transmission method is performed by a PDCP entity and is associated with an RLC entity using UM.

[0029] S201, determining a target operation mode of a PDCP entity.

[0030] As for step S201, any feasible method in each embodiment of the present application can be used, so the description thereof will be omitted here.

[0031] S202, in response to the target operation mode being the first operation mode, sending a first data packet received from the first connection to an upper layer protocol entity in numerical order before using the newly configured PDCP configuration information.

[0032] In order to distinguish between the newly set PDCP setting information and the previously set PDCP setting information, in the embodiments of the present application, the previously set PDCP setting information is called the first PDCP setting information and the newly set PDCP setting information is called the second PDCP setting information. In other words, the first PDCP setting information is the PDCP setting information used by a PDCP entity before it uses the second PDCP setting information.

[0033] For example, the network side may instruct the PDCP entity to use operation mode 1-1, thereby making the old settings used by the PDCP entity before receiving the setting instruction the first PDCP setting information, and simultaneously with or after instructing the PDCP entity to use operation mode 1-1, the network side may selectively instruct the PDCP entity to use new settings, and the new settings used by the PDCP entity are the second PDCP setting information.

[0034] In the following embodiments, the first PDCP setting information and the second PDCP setting information are both used to describe the data transmission method provided by the present application.

[0035] Before using the second PDCP setting information, a first data packet received from the first connection is processed based on the first PDCP setting information before being transmitted to an upper layer protocol entity, and the processed first data packet is transmitted to the upper layer protocol entity in numerical order.

[0036] For example, the first connection may be a source connection in a switching process, and the first data packet may be a data packet that an RLC entity associated with the source connection passes to a PDCP entity.

[0037] In the embodiment of the present application, a data packet received before the PDCP entity uses the second PDCP configuration information is called a first data packet, and the first data packet is old data stored in the PDCP entity.

[0038] Optionally, the first data packet comprises: PDU data packets cached in the PDCP entity; PDU data packets received from the first connection before using the second PDCP configuration information; and at least one of the PDU data packets passed to the PDCP entity during the re-establishment of the lower protocol entity before using the second PDCP configuration information; For example, the PDCP entity may be a UE-side entity, and the received PDU data packet may be a PDU data packet received by the UE from a source cell during a handover process; For example, in the process of reconstructing the RLC entity, data packets stored in the RLC entity are passed to the PDCP entity.

[0039] For the first PDCP setting information and the second PDCP setting information, optionally, the PDCP setting information includes at least an encryption algorithm and an encryption key.

[0040] Optionally, the PDCP configuration information further comprises: a header decompression / compression configuration, the header decompression / compression configuration including at least one of a Robust Header Compression (ROHC) configuration and an Ethernet Header Compression (EHC) configuration, optionally, the ROHC configuration including a ROH decompression / compression configuration and the EHC configuration including an EHC decompression / compression configuration; The encryption key includes at least one of an integrity protection algorithm and an integrity protection key.

[0041] Optionally, the second PDCP configuration information further includes indication information for indicating whether the header decompression / compression configuration context configured in the first PDCP configuration information is to be continued to be used or not.

[0042] For example, when a ROHC configuration is set, the second PDCP configuration information may also indicate whether the ROHC compression context set by the first PDCP configuration information continues to be used or not; in an implementation, the second PDCP configuration information may carry drb-ContinueROHC indication information, which may indicate whether the ROHC compression context set by the first PDCP configuration information continues to be used or not.

[0043] When an EHC configuration is set, the second PDCP configuration information may also indicate whether the EHC compression context set by the first PDCP configuration information continues to be used or not; in an implementation, the second PDCP configuration information may carry drb-ContinueEHC indication information, which may indicate whether the EHC compression context set by the first PDCP configuration information continues to be used or not.

[0044] 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 is continuously usable. The PDCP entity decompresses the header compression of the second data packet using the header decompression / compression configured in the second PDCP configuration information. For example, if "drb-ContinueROHC" is not indicated for ROHC or "drb-ContinueEHC" is not indicated for EHC, i.e., if it is not indicated that the header decompression / compression context configured in the first PDCP configuration information is continuously usable, the PDCP entity cannot use the header decompression / compression configuration configured in the first PDCP configuration information when applying the header decompression / compression configuration configured in the second PDCP configuration information.

[0045] Optionally, if the second PDCP configuration information indicates that header decompression / compression is configured and that the header decompression / compression context configured by the first PDCP configuration information is still usable, the PDCP entity decompresses the header of the second data packet using the header decompression / compression configured in the first PDCP configuration information. For example, if "drb-ContinueROHC" is indicated for ROHC or "drb-ContinueEHC" is indicated for EHC, i.e., if it is indicated that the header decompression / compression context configured in the first PDCP configuration information is still usable, the PDCP entity decompresses / compresses the header of the second data packet using the header decompression / compression configuration configured in the first PDCP configuration information.

[0046] In the present example, the processing for the first data packet includes at least a decoding process and a reordering process.

[0047] Prior to using the second PDCP configuration information, the PDCP entity reorders the received first data packets in numerical order based on the first PDCP configuration information. In some embodiments, the PDCP entity decodes and processes the first data packets based on the first PDCP configuration information and reorders the decoded and processed first data packets in numerical order.

[0048] Optionally, the processing on the first data packet further includes at least one of a header decompression / compression process and an integrity verification process.

[0049] In response to the header decompression / compression setting being set in the first PDCP setting information, the process for the first data packet may include a header decompression / compression process, where the header decompression may be performed in the order of the data packet numbers, for example, in ascending order of numbers.

[0050] In response to an integrity protection algorithm and an integrity protection key being set in the first PDCP setting information, the processing on the first data packet can include an integrity verification process.

[0051] In a possible implementation, in response to the first data packet being a processed data packet, the PDCP entity does not perform the above-mentioned processing steps, such as the decryption processing, the header decompression / compression processing and / or the integrity verification processing, on the first data packet using the first PDCP configuration information. That is, if the PDCP entity performed the above-mentioned processing steps on the first data packet using the first PDCP configuration information before the target operation mode used by the PDCP entity was determined, the PDCP entity does not perform the processing using the first PDCP configuration information. For example, the PDCP entity usually decrypts and processes the first data packet using the first PDCP configuration information immediately after receiving the first data packet, and does not reorder the first data packet in data packet number order before decoding. In an embodiment of the present application, when receiving the operation mode instruction, if the first data packet is a decrypted data packet, the PDCP entity does not perform the decoding process on the stored first data packet.

[0052] Furthermore, the PDCP entity may reorder the first processed data packets in the order of data packet numbers, for example, in ascending order of data packet numbers.

[0053] The PDCP entity uses a reordering window mechanism to reorder data packets. Figure 3 is a schematic diagram of the reordering window. As shown in Figure 3, the variable of the lower boundary of the reordering window is "RX_DELIV", which identifies the data packet number of the first PDU data packet that has not been passed to the upper layer protocol entity. The PDCP entity updates the variable of the lower boundary of the reordering window, "RX_DELIV", based on the data packet number of the PDU data packet that has been passed to the upper layer protocol entity. When waiting to receive a PDU data packet, the PDCP entity starts a reordering timer, and when the reordering times out, the PDCP entity ignores the "number of the PDU data packet waiting to be received" and updates the lower boundary of the reordering window. If the PDCP entity receives a data packet outside the reordering window, the PDCP entity discards the data packet. The variable "RX_REORD" represents the data packet number that starts the reordering timer. Here, "RX_NEXT" indicates the data packet number of the next PDU data packet to be received. As shown in Figure 3, the initial values ​​of "RX_DELIV" and "RX_NEXT" of the PDCP entity are "0". If a PDU data packet with number "1" is received, it indicates that a PDU data packet with number "0" has not been received. The PDCP entity updates "RX_NEXT" to "2" and sets "RX_REORD" to "2" in response to starting the reordering timer. If a PDU data packet with number "2" is received, it updates "RX_NEXT" to "3".

[0054] In the embodiment of the present application, when the PDCP entity uses the operation mode 1-1, it directly passes the first data packet passed in numerical order, and does not need to wait for the reception of subsequent data packets.

[0055] When the PDCP entity reorders the first data packet, an empty data packet number occurs in the reordering window, and in the embodiment of the present application, the PDCP can pass the first data packet to the upper layer protocol entity in numerical order without waiting for the reception of the data packet corresponding to the empty number. For example, the PDCP entity uses the first PDCP configuration information to process the PDU data packet-1 / 3 and then passes it to the upper layer protocol entity. Because the reordering window is not initialized, the PDCP entity continues to inherit the previous number, and receives the PDU data packet-0 / 2 / 4, and the PDU data packet-1 / 3 creates an empty space in the reordering window. The PDCP entity can ignore the reception of the PDU data packet-1 / 3 corresponding to the empty number. For example, the reordering timer does not need to be started.

[0056] S203, after using the second PDCP configuration information, sending second data packets received from the second connection to an upper layer protocol entity in numerical order.

[0057] In some embodiments, the PDCP entity processes second data packets received from a second connection based on the second PDCP configuration information and reorders the processed second data packets according to data packet numbers. For example, the second connection may be a target connection of a switch. The second data packets are data packets that an RLC entity associated with the target connection passes to the PDCP entity.

[0058] In the present example, the processing for the second data packet includes at least a decoding process and a reordering process.

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

[0060] In response to the header decompression / compression setting being set in the second PDCP setting information, the processing on the second data packet may include a header decompression / compression process.

[0061] In response to an integrity protection algorithm and an integrity protection key being set in the second PDCP setting information, the processing on the second data packet may include an integrity verification process.

[0062] Furthermore, the PDCP entity may reorder the processed second data packets in the order of data packet numbers, for example, in ascending order of data packet numbers.

[0063] In the embodiment of the present application, since the PDCP entity does not initialize the variables related to the reordering window, when the other PDCP entity uses the second PDCP configuration information to number the new data packet, the second data packet, the number of the second data packet is the number following the number of the first data packet. Accordingly, the number of the second data packet received by the PDCP entity is consecutive with the number of the first data packet and is the number following the number of the first data packet. For example, after the PDCP entity processes the PDU data packet-1 / 3 using the first PDCP configuration information and passes it to the upper layer protocol entity, the operation mode 1?1 does not initialize the reordering window, so the number of the transmission data of the PDCP entity to the other PDCP entity starts from 4, and the other PDCP entity transmits the PDU data packet-4 / 5 to the PDCP entity.

[0064] Furthermore, the PDCP entity passes the second data packet to the upper layer protocol entity in the reordered number order.

[0065] When the target operation mode setting is described as operation mode 1-1, before receiving a new data packet or before using the second setting information, the PDCP entity processes the first stored data packet based on the first PDCP setting information, and after processing, reorders the data packet in order of data packet number, for example, from smallest to largest, and passes the data packet to the upper layer protocol entity in that order. For example, the encryption setting-1 and header compression setting-1 of the PDCP entity are set in the first PDCP setting information. The reordering window of the PDCP entity stores PDCP data packet-2 and PDCP data packet-4, which are the first data packets received by the PDCP entity. If PDCP data packet-2 / 4 has been decrypted with encryption setting-1 but has not been header-compressed, it is necessary to decompress PDCP data packet-2 / 4 with header compression setting-1 and pass the data packet to the upper layer protocol entity in order of data packet number. In other words, the PDCP entity passes PDCP data packets-1, 2, 3, and 4 in order to the upper layer protocol entity without waiting for reception of PDCP data packet-1 and PDCP data packet-3.

[0066] In some embodiments, the method of any of the embodiments of the present application further comprises: The method may further include the step S204 of feeding back data packet number information of the first data packet passed to the upper layer protocol entity to the other PDCP entity; Here, the number information is the highest number of the first data packet that is processed by the first PDCP configuration information and passed to a higher layer protocol entity; incrementing by one the highest number of a first data packet that is processed according to the first PDCP configuration information and passed to an upper layer protocol entity; subtracting one from the highest number of a first data packet that is processed according to the first PDCP configuration information and passed to an upper layer protocol entity; the smallest number of the first data packet that is processed by the first PDCP configuration information and passed to a higher layer protocol entity; incrementing by one the lowest number of a first data packet that is processed according to the first PDCP configuration information and passed to an upper layer protocol entity; subtracting one from the lowest number of a first data packet that is processed by the first PDCP configuration information and passed to an upper layer protocol entity; and The first data packet includes at least one of a total amount of data of the first data packet that is processed according to the first PDCP configuration information and passed to an upper layer protocol entity.

[0067] In the embodiment of the present application, in response to the reconfiguration instruction of the PDCP entity, the target operation mode is set to be the operation mode 1-1. In this case, the PDCP entity can obtain second PDCP configuration information in which the ciphering setting-2 and the header compression setting-2 are set. The PDCP entity receives a new data packet, i.e., the second data packet, based on the second PDCP configuration information and processes the second data packet. That is, the PDCP entity decrypts the PDCP data packet-2 / 4 with the ciphering setting-2, decompresses it with the header compression setting-2, and then passes it to the upper layer protocol entity in the order of the data packet number.

[0068] In the embodiment of the present application, when the target operation mode of the PDCP entity is set to operation mode 1-1, data transmission is performed based on operation mode 1-1, and there is no need to wait for missing data packets, so that data packets can be delivered to the application service more quickly and delays can be reduced. Furthermore, since operation mode 1-1 does not initialize the reordering window, data can continue to be sent using data packet numbers, and data transmission delays can be reduced.

[0069] The data transmission process of the PDCP entity will be described below by taking as an example the target operation mode set in the PDCP entity as operation mode 1-2 of operation mode A, i.e., the second operation mode. Figure 4 is a schematic flow chart of another data transmission method provided in an embodiment of the present application. The data transmission method is performed by a PDCP entity and is associated with an RLC entity using UM.

[0070] S401, determining a target operation mode of a PDCP entity.

[0071] S402, in response to the target operation mode being the second operation mode, sending a first data packet received from the first connection to an upper layer protocol entity in numerical order before using the second PDCP configuration information.

[0072] As for steps S401 to S402, any feasible method in each embodiment of the present application can be used, and therefore a description thereof will be omitted here.

[0073] S403, initialize variables related to the reordering window.

[0074] Continuing to refer to FIG. 3, in an embodiment of the present application, the step of setting the relevant variables of the reordering window to initial values ​​includes: A step of setting a "variable for indicating a data packet to be received next" to an initial value, for example, a step of setting "RX_NEXT" to an initial value of "0"; The method includes at least one of a step of setting a "variable for expressing a lower boundary of a reordering window" to an initial value, for example, a step of setting "RX_DELIV" to an initial value "0".

[0075] S404, processing a second data packet received from a second connection using the second PDCP configuration information based on the initialized reordering window.

[0076] When the reordering window is initialized, the associated variable of the reordering window is counted from the initial value. Furthermore, in the example of the present application, the processing for the second data packet includes at least a decryption processing and a reordering. Optionally, the processing for the second data packet can further include at least one of a header decompression / compression processing and an integrity verification processing.

[0077] If the second PDCP setting information includes a header decompression / compression setting timing, the process for the second data packet may include a header decompression / compression process. If the second PDCP setting information includes an integrity protection algorithm and an integrity protection key, the process for the second data packet may include an integrity verification process.

[0078] After the PDCP entity processes PDU data packet-1 / 3 using the first PDCP setting information and passes it to the upper layer protocol entity, the operation mode 1-2 initializes the reordering window, so that the other PDCP entity renumbers the untransmitted PDU data packet-2 / 4, i.e., transmits it from the initial number 0, and thus no free number 1 / 3 is generated in the reordering window as in the operation mode 1-1.

[0079] S405, sending the second data packets to an upper layer protocol entity in numerical order.

[0080] Furthermore, the PDCP entity reorders the processed second data packets in numerical order of the data packets and transmits the second data packets to the upper layer protocol entity in numerical order. For example, the reordering can be performed in ascending order of the data packet numbers.

[0081] The first PDCP setting information and the second PDCP setting information can be explained by referring to the relevant descriptions in the above embodiments, and therefore the explanation will be omitted here.

[0082] For the process of processing a first data packet based on the first PDCP setting information, and the process of processing a second data packet based on the second PDCP setting information, reference can be made to the relevant descriptions in the above embodiments, and therefore a description thereof will be omitted here.

[0083] In an embodiment of the present application, when the target operation mode of the PDCP entity is set to operation mode 1-2, data transmission is performed based on operation mode 1-2, and the reordering window is initialized, so that free numbers are not generated, there is no need to wait for missing data packets, the reordering delay is reduced, and data packets can be delivered to the application service more quickly.

[0084] The data transmission process of the PDCP entity will be described below by taking the target operation mode set in the PDCP entity as operation mode B, i.e., the third operation mode, as an example. Figure 5 is a schematic flowchart of another data transmission method provided in an embodiment of the present application. The data transmission method is performed by the PDCP entity and is associated with the RLC entity of the UM.

[0085] S501, determining a target operation mode of a PDCP entity.

[0086] As for step S501, any feasible method in each embodiment of the present application can be used, so the description will be omitted here.

[0087] S502, in response to the target operation mode being a third operation mode, globally reorder the first data packet and the second data packet based on their respective PDCP setting information, and send them to an upper layer protocol entity in numerical order.

[0088] Wherein, the first data packet is a data packet received from a 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 may be a source connection in a switching process, and the first data packet may be a data packet sent by an RLC entity associated with the source connection to a PDCP entity.

[0089] The second data packet is a data packet received from a second connection, the second data packet corresponds to second PDCP configuration information, and the second PDCP configuration information is newly configured PDCP configuration information. Optionally, the second connection may be a target connection in a switching process, and the second data packet may be a data packet sent by an RLC entity associated with the target connection to a PDCP entity.

[0090] Before using the second PDCP setting information, the PDCP entity processes the first data packet using the first PDCP setting information, where the processing process may include at least a decoding process. The process of decoding and processing the first data packet using the first PDCP setting information may refer to the description of the relevant content in the above embodiment, so the description will be omitted.

[0091] The PDCP entity processes the second data packet using the second PDCP setting information, where the processing process may include at least a decoding process. The process of decoding and processing the second data packet using the second PDCP setting information may refer to the description of the relevant content in the above embodiment, so the description is omitted.

[0092] Furthermore, the PDCP entity reorders the processed first data packet and second data packet together, and transmits all the data packets after the reordering to the upper layer protocol entity in numerical order.

[0093] For example, the first PDCP setting information sets the ciphering setting-1 and the header compression setting-1 in the PDCP entity. The first data packet-2 / 4 is stored in the reordering window of the PDCP entity-1, and these data packets are decrypted by the ciphering setting-1 but the header compression is not decompressed. The PDCP entity must wait for the reception of the second PDCP data packet-1 / 3, and then reorder the data packets-1 / 2 / 3 / 4 together and pass them to the upper layer protocol entity in numerical order. Furthermore, the target operation mode set in the PDCP is the operation mode B, and second PDCP setting information is provided, where the second PDCP setting information sets the ciphering setting-2 and the header compression setting-2 in the PDCP entity. The PDCP entity decompresses the first data packet-2 / 4 by the header compression setting-1 and stores it in the PDCP entity. The PDCP entity applies encryption setting-2 and header compression setting-2 set in the second PDCP setting information, decrypts the received second data packet-1 / 3 using encryption setting-2 and decompresses it using header compression setting-2, and the PDCP entity passes all data packets-1 / 2 / 3 / 4 to the upper layer protocol entity in numerical order.

[0094] In an embodiment of the present application, when the target operation mode of a PDCP entity is set to operation mode B, data transmission is performed based on operation mode B, and operation mode B supports a function of waiting for data packets that have failed to be received, thereby reducing data packet loss.

[0095] 6 is a schematic flow chart of another data transmission method provided in an embodiment of the present application, the data transmission method is performed by a PDCP entity and is associated with an RLC entity of a UM.

[0096] S601, in response to a need to reconstruct a PDCP entity, determines an operation mode to be used by an RLC entity associated with the PDCP entity.

[0097] In an embodiment of the present application, a target operation mode of a PDCP entity can be determined by a protocol agreement. Since the operation modes used by each RLC entity associated with a PDCP entity often affect the operation mode used by the PDCP entity, the protocol agreement can negotiate a target operation mode of the PDCP entity based on the operation mode used by the RLC entity.

[0098] An indication may be received to reconstruct the PDCP entity, and when the indication to reconstruct is received, a determination of an operation mode to be used by an RLC entity associated with the PDCP entity may be triggered. The operation mode to be used by the RLC entity may include one of the following operation modes: AM, UM and transparent mode, receiving data in a multicast manner, and receiving data in a unicast manner.

[0099] Optionally, whether a PDCP entity feeds back data reception status often also affects the operation mode of the PDCP entity.

[0100] S602, determining a target operation mode of the PDCP entity based on at least one of an operation mode used by the RLC entity and a data status feedback indication of the PDCP entity.

[0101] In response to the PDCP entity being associated only with the RLC entity of the UM, determine a target operation mode of the PDCP entity to be operation mode A, i.e., one of the first operation mode and the second operation mode, i.e., operation mode 1-1 and operation mode 1-2. For example, the PDCP entity is an RLC entity associated with one or more UMs. When a reconfiguration of the PDCP entity is indicated, the PDCP entity can use operation mode A.

[0102] In response to at least one RLC entity among the multiple RLC entities associated with the PDCP entity using acknowledged mode AM, the target operation mode of the PDCP entity is determined to be the first operation mode or the third operation mode, i.e., operation mode 1-1 of operation mode A or operation mode B. For example, a PDCP entity is associated with two RLC entities, RLC entity-1 is configured as UM and RLC entity-2 is configured as AM. When reconfiguration of the PDCP entity is indicated, the PDCP entity uses operation mode B.

[0103] In response to the need for the PDCP entity to feed back the data reception status, the target operation mode of the PDCP entity is determined to be the first operation mode or the third operation mode, i.e., operation mode 1-1 of operation mode A or operation mode B. For example, a PDCP entity is associated with two RLC entities, and RLC entity-1 and RLC entity-2 are both configured as UM, but the PDCP entity needs to transmit the data reception status of the PDCP entity to the other PDCP entity through RLC entity-2, i.e., to transmit a Status Report to the other PDCP entity. When re-establishment of the PDCP entity is instructed, the PDCP entity uses operation mode B.

[0104] In response to at least one RLC entity of the multiple RLC entities associated with the PDCP entity receiving data in a multicast manner and at least one RLC entity receiving data in a unicast manner, the PDCP entity determines a target operation mode to be the first operation mode or the third operation mode, i.e., operation mode 1-1 of operation mode A or operation mode B. For example, the PDCP entity is associated with two RLC entities, where RLC is configured to receive data in a Point To Multipoint (PTM) manner and RLC entity-2 is configured to receive data in a Point To Point (PTP) manner. When reconfiguration of the PDCP entity is indicated, the PDCP entity uses operation mode B.

[0105] For specific explanations of the operation mode 1-1, the operation mode 1-2, and the operation mode B, the relevant contents in the above embodiment can be referred to, and therefore the explanations will be omitted here.

[0106] S603, sending the data packets to an upper layer protocol entity in numerical order based on the target operation mode.

[0107] As for step S603, any feasible method in each embodiment of the present application can be used, so the description will be omitted here.

[0108] In the embodiment of the present application, different operation modes can be set for the PDCP entity according to different service scenarios, so that the flexibility of data transmission of the PDCP entity is improved. In addition, each operation mode can be reordered. Operation mode A can quickly deliver data packets to the application service, and delays are reduced. Operation mode B supports the function of waiting for new data packets that have failed to be received, and can reduce data packet loss.

[0109] 7 is a schematic flow chart of another data transmission method provided in an embodiment of the present application, the data transmission method is performed by a PDCP entity and is associated with an RLC entity of a UM.

[0110] S701, receiving instruction information, where the instruction information carries identification information of a target operation mode.

[0111] In the embodiment of the present application, an identification information may be set for each operation mode, and then an indication information may be set, where the identification information of the target operation mode to be selected is set in the indication information, and the PDCP entity can obtain the indication information and then extract the identification information of the target operation mode.

[0112] S702, determining a target operation mode of the PDCP entity based on the indication information.

[0113] For example, the identification information of the first operation mode, operation mode 1-1, may be A-1, the identification information of the second operation mode, operation mode 1-2, may be A-2, and the identification information of the third operation mode, operation mode B, may be B. For example, based on A-1 carried in the reestablishPDCP, it may be indicated that the target operation mode to be used by the PDCP entity is operation mode 1-1, and for example, based on A-2 carried in the reestablishPDCP, it may be indicated that the target operation mode to be used by the PDCP entity is operation mode 1-2, and for example, based on B carried in the reestablishPDCP, it may be indicated that the target operation mode to be used by the PDCP entity is operation mode B.

[0114] S703, sending the data packets to an upper layer protocol entity in numerical order based on the target operation mode.

[0115] As for step S603, any feasible method in each embodiment of the present application can be used, so the description will be omitted here.

[0116] In the embodiment of the present application, different operation modes can be set for the PDCP entity according to different service scenarios, thereby improving the flexibility of data transmission of the PDCP entity. In addition, each operation mode can be reordered. Operation mode A can quickly deliver data packets to the application service, reducing delay. Operation mode B supports the function of waiting for new data packets that have failed to be received, reducing data packet loss.

[0117] Corresponding to the data transmission methods provided by some of the above embodiments, the present application further provides a data transmission device, and since the data transmission device provided by the embodiments of the present application corresponds to the data transmission methods provided by the embodiments of Figures 1 to 7 above, the embodiments of the data transmission method are also applied to the data transmission device provided by the present embodiments, but detailed descriptions are omitted in this embodiment.

[0118] 8 is a schematic diagram of a data transmission device provided by an embodiment of the present application. The data transmission device is applied to a PDCP entity, and the PDCP entity is associated with an RLC entity of UM, and optionally, at least one RLC entity among one or more RLC entities associated with the PDCP entity is configured as UM. Here, the PDCP entity may 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.

[0119] As shown in FIG. 8, the data transmission device 800 includes a mode determination module 81 and a sending module 82. Wherein the mode determination module 81 is configured to determine a target operation mode of the PDCP entity; The transmitting module 82 is configured to transmit the data packets in numerical order to an upper layer protocol entity based on the target operating mode.

[0120] In an embodiment of the present application, to set multiple operation modes for a PDCP entity, a target operation mode can be determined for the PDCP entity from the multiple operation modes by protocol agreement or setting of indication information.

[0121] Determining the target operation mode of the PDCP entity may be determined by a protocol agreement, and optionally, in response to a need to reconstruct the PDCP entity, determining the operation mode used by each Radio Link Control (RLC) entity associated with the PDCP entity, and determining the target operation mode to be used by that PDCP entity based on the operation mode used by the RLC entities.

[0122] In a possible implementation, an identification may be set for each operation mode, and then an indication may be set, where the identification of the target operation mode to be selected is set in the indication, and the PDCP entity determines the target operation mode to be used based on the indication.

[0123] The operation mode of the PDCP entity may be one of the following operation modes:

[0124] Operation mode A is a mode for directly passing old protocol data unit (PDU) data packets stored in the PDCP entity. In some embodiments, operation mode A can include a first operation mode and a second operation mode. Optionally, the first operation mode is denoted as operation mode 1-1, and the second operation mode is denoted as operation mode 1-2, which is merely an example and cannot be a limiting condition of the present application.

[0125] Alternatively, the operation mode 1-1 may be such that, before receiving a new data packet, the PDCP entity reorders all stored old data packets, for example in ascending numerical order, and then passes the packets to the upper layer protocol entity in numerical order. Furthermore, the PDCP entity continues to receive new data packets, reorders the new data packets, and then passes the packets to the upper layer protocol entity in numerical order.

[0126] Alternatively, in the operation mode 1-2, before receiving a new data packet, the PDCP entity may reorder all stored old data packets, for example, in ascending order, before passing the packets to the upper layer protocol entity in order and initialize the associated variables of the reordering window. Furthermore, the PDCP entity may continue to receive new data packets, reorder the new data packets, and then pass the packets to the upper layer protocol entity in order.

[0127] In addition, since the operation mode 1-1 does not initialize the reordering window for the operation mode 1-2, it is possible to continue transmitting data using the data packet number, and thus it is possible to reduce the data transmission delay.

[0128] The operation mode B is a mode in which old data packets stored in the PDCP entity are entirely reordered and passed on after a new data packet is received. Optionally, before receiving a new data packet, the PDCP entity first processes all the old data packets stored therein. Furthermore, the PDCP entity receives and processes a new data packet. The PDCP entity entirely reorders the processed old data packets together with the processed new data packets, and passes them to an upper layer protocol entity in numerical order. In the embodiment of the present application, the operation mode B can be referred to as a third operation mode.

[0129] As a possible implementation, the timer for reordering can be stopped. In some embodiments, a reordering timer (t-Reordering) for reordering is preset, counted when reordering is started, and the timer for reordering is stopped in response to reaching a reordering timing value. For example, if a data packet with a lower number has not been received before a received data packet with a higher number is passed to an upper layer protocol entity, the timer waits for the data packet with the lower number to arrive within the timing time of the reordering timer. In response to the reordering timing out, the data packet with the higher number is passed directly to the upper layer protocol entity without waiting for the data packet with the lower number, and the reordering timer is stopped. That is, when the timing time of the reordering timer has elapsed, the PDCP entity passes the existing received, sorted data packet directly to the upper layer protocol entity without waiting for the unreceived data packet with a lower number.

[0130] The PDCP entity uses a reordering window mechanism to perform reordering based on the data packet number (COUNT) of the data packets. The maximum number of PDCP COUNT numbers that the PDCP entity can reorder is half the maximum number of PDCP serial numbers (SN), that is, the size of the reordering window Window_Size = 2 [pdcp-SN-Size DL]-1 , "pdcp-SN-SizeDL" is the number of bits of PDCP SN.

[0131] In the embodiment of the present application, different operation modes can be set for the PDCP entity according to different service scenarios, thereby improving the flexibility of data transmission of the PDCP entity. In addition, each operation mode can be reordered. Operation mode A can quickly deliver data packets to the application service, reducing delay. Operation mode B supports the function of waiting for new data packets that have failed to be received, reducing data packet loss.

[0132] 9 is a schematic diagram of a data transmission device provided by an embodiment of the present application. The data transmission device is applied to a PDCP entity, and the PDCP entity is associated with an RLC entity of UM, and optionally, at least one RLC entity among one or more RLC entities associated with the PDCP entity is configured as UM. Here, the PDCP entity may 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.

[0133] As shown in FIG. 9, the data transmission device 900 includes a mode determination module 91 and a sending module 92; Wherein the mode determination module 91 is configured to determine a target operation mode of the PDCP entity; The transmitting module 92 is configured to transmit the data packets in numerical order to an upper layer protocol entity based on the target operating mode.

[0134] Optionally, the sending module 92 includes a first sending unit 921 and a second sending unit 922; the first sending unit 921 is configured to, in response to the target operation mode being the first operation mode, send a first data packet received from the first connection to an upper layer protocol entity in numerical order before using the newly configured PDCP configuration information; The second sending unit 922, after using the newly configured PDCP configuration information, sends the second data packets received from the second connection to the upper layer protocol entity in numerical order.

[0135] Optionally, the sending module 92 further includes an initialization unit 923; The initialization unit 913 is configured to initialize a related variable of the reordering window after transmitting the first data packet in numerical order to the upper layer protocol entity in response to the target operating mode being the second operating mode. The second sending unit 922 is configured to process the second data packet using the newly set PDCP setting information based on the initialized reordering window.

[0136] Optionally, the transmitting module 92 is further configured, in response to the target operating mode being a third operating mode, to globally reorder the first data packet and the second data packet based on the respective PDCP configuration information and transmit the first data packet and the second data packet to the upper layer protocol entity in numerical order; Wherein the first data packet is a data packet received from a first connection, the first data packet corresponds to first PDCP setting information, and the first PDCP setting information is previously configured PDCP setting information; The second data packet is a data packet received from the second connection, the second data packet corresponds to the second PDCP setting information, and the second PDCP setting information is newly configured PDCP setting information.

[0137] Optionally, as shown in FIG. 9, the data transmission device further includes a timing stop module 93; The timing stop module 93 is configured to stop the timer for the reordering.

[0138] Optionally, the first data packet comprises: PDU data packets cached in the PDCP entity, Before using the newly configured PDCP configuration information, the PDCP entity shall It includes at least one of the PDU data packets passed to the PDCP entity during the re-establishment of the lower protocol entity.

[0139] Optionally, as shown in FIG. 9, the data transmission device further includes a processing module 94; The processing module 94 processes the first data packet based on the first PDCP setting information before transmitting the first data packet to the upper layer protocol entity, and processes the second data packet based on the second PDCP setting information before transmitting the second data packet to the upper layer protocol entity, where the second PDCP setting information is configured to be newly configured PDCP setting information.

[0140] Optionally, each of the first configuration information and the second PDCP configuration information includes at least an encryption algorithm and an encryption key.

[0141] Optionally, the first configuration information and the second PDCP configuration information are Header decompression / compression settings, The encryption / decryption method further includes at least one of an integrity protection algorithm and an integrity protection key.

[0142] Optionally, the header decompression / compression settings can be Robust Head Compression (ROHC) decompression / compression settings, and Contains at least one of the Ethernet Header Compression (EHC) decompression / compression settings.

[0143] Optionally, the second PDCP configuration information further includes indication information for indicating whether the header decompression / compression configuration context configured in the first PDCP configuration information is to be continued to be used or not.

[0144] Optionally, the processing includes a decoding process and a reordering process.

[0145] Optionally, the processing includes at least one of a header decompression / compression processing and an integrity verification processing.

[0146] Optionally, the processing module 94 is further configured to, in response to the first data packet being a decoded data packet, not perform a decoding process on the first data packet.

[0147] Optionally, the processing module 94 is further configured to perform a decompression / compression process in response to a header decompression / compression setting being set in the PDCP setting information, and to perform an integrity verification process in response to an integrity protection algorithm and an integrity protection key being set in the PDCP setting information.

[0148] Optionally, the first sending unit 921 is further configured, in response to the first data packet generating a free data packet number in the reordering window, to not need to wait for reception of the data packet corresponding to the free data packet number.

[0149] Optionally, the second transmitting unit 922 is configured such that, in response to the other PDCP entity numbering the second data packets using the newly configured PDCP configuration information, the numbers of the received second data packets are consecutive with the numbers of the first data packets.

[0150] Optionally, the first sending unit 921 is configured to feed back the data packet number information of the first data packet passed to the upper layer protocol entity to the peer PDCP entity.

[0151] Optionally, the mode determination module 91 includes a first determination unit 911 and a second determination unit 912; The first determining unit 911 is configured to, in response to a need to reconstruct the PDCP entity, determine an operation mode to be used by each radio link control (RLC) entity associated with the PDCP entity. The second determining unit 912 is configured to determine a target operation mode of the PDCP entity based on at least one of the operation mode used by the RLC entity and the data status feedback indication of the PDCP entity.

[0152] Optionally, the second determining unit 912 is In response to the PDCP entity being associated only with the UM RLC entity, the target operation mode is determined to be the first operation mode or the second operation mode; or determining that the target operation mode is the first operation mode or the third operation mode in response to at least one RLC entity of the plurality of RLC entities associated with the PDCP entity using the acknowledged mode AM; or In response to the PDCP entity needing to feed back a data reception status, the target operation mode is determined to be the first operation mode or the third operation mode; or The target operation mode is further configured to be determined to be the first operation mode or the third operation mode in response to at least one RLC entity of the multiple RLC entities associated with the PDCP entity receiving data in a multicast manner and at least one RLC entity receiving data in a unicast manner.

[0153] Optionally, the mode determination module 91 is further configured to receive instruction information, where the instruction information carries an identification of a target operational mode, and to determine the target operational mode based on the instruction information.

[0154] In the embodiment of the present application, different operation modes can be set for the PDCP entity according to different service scenarios, thereby improving the flexibility of data transmission of the PDCP entity. In addition, each operation mode can be reordered. Operation mode A can quickly deliver data packets to the application service, reducing delay. Operation mode B supports the function of waiting for new data packets that have failed to be received, reducing data packet loss.

[0155] According to an embodiment of the present application, the present application further provides a communication device and a readable storage medium.

[0156] As shown in FIG. 10, the electronic device includes one or more processors 110, memory 1200, and interfaces for connecting each component, including high-speed and low-speed interfaces. Each component can be connected to each other by different buses and mounted on a common motherboard, or mounted in other manners as needed. The processor can process instructions executed in the electronic device, including instructions stored in the memory for displaying graphical information of a GUI on an external input / output device (such as a display device coupled to the interface). In other embodiments, multiple processors and / or multiple buses can be used, along with multiple memories and multiple memories, if necessary. Similarly, multiple electronic devices can be connected, and each electronic device can provide a portion of the required operations (e.g., a server array, a blade server, or a multi-processor system). In FIG. 10, one processor 1100 is taken as an example.

[0157] The memory 1200 is a non-transitory computer-readable storage medium provided by the present application, where the memory stores instructions that are executed by at least one processor to cause the at least one processor to perform the data transmission method provided by the present application. The non-transitory computer-readable storage medium of the present application stores computer instructions that cause a computer to perform the data transmission method provided by the present application.

[0158] The memory 1200 is a non-transitory computer-readable storage medium used to store non-transitory software programs, non-transitory computer-executable programs and modules, such as program instructions / modules corresponding to the data transmission method in the embodiments of the present application. The processor 1100 executes the non-transitory software programs, instructions and modules stored in the memory 1200 to perform various functional applications and data processing of the server, i.e., to realize the data transmission method in the above embodiment of the method.

[0159] The memory 1200 may include a program storage area and a data storage area, where the program storage area may store an operating system, an application program required for at least one function, and the data storage area may store data generated by the use of the positioning communication device, etc. The memory 1200 may also include a high-speed random storage memory, and may further include a non-transient memory, such as at least one disk storage device, flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 1200 may optionally include a memory located remotely to the processor 501, and these remote memories may be connected to the electronic device of the three-dimensional reconstruction method via a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0160] 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 via a bus or other methods, and FIG. 10 illustrates a bus connection as an example.

[0161] The input device 1300 can receive input digital or textual information and generate key signal inputs related to user settings and function control of the positioning communication device, such as a touch screen, a keypad, a mouse, a track pad, a touchpad, a pointing stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 1400 can include a display device, an auxiliary lighting device (e.g., LED), a haptic feedback device (e.g., vibration motor), etc. The display device can 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 can be a touch screen.

[0162] Various embodiments of the systems and techniques described herein may be realized in digital electronic circuitry systems, integrated circuit systems, application specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include being embodied in one or more computer programs that can be executed and / or interpreted by a programmable system that includes at least one programmable processor, which may be a special purpose or general purpose programmable processor, and that can receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device.

[0163] These computing programs (also referred to as programs, software, software applications, or code) may include machine instructions for a programmable processor and may include implementing these computing programs in high-level process 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., magnetic disks, optical disks, memories, programmable logic devices (PLDs)) used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions that are machine-readable signals. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0164] To provide 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 a user, and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other types of devices can also be used to provide interaction with a user, for example, feedback provided to the user can be any form of sensing feedback (e.g., visual feedback, auditory feedback, or haptic feedback) and can receive input from the user in any form (including acoustic input, speech input, and haptic input).

[0165] The systems and techniques described herein may be implemented in a computing system including a back-end component (e.g., a data server), or a computing system including a middleware component (e.g., an application server), or a computing system including a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user interacts with an embodiment of the systems and techniques described herein), or any combination of the back-end, middleware, and front-end components. The components of the system may 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.

[0166] A computer system may include clients and servers that are generally remote from each other and typically interact through a communication network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship to each other.

[0167] Those skilled in the art will understand that all or part of the steps carried out to implement the method of the above examples can be instructed to complete the associated hardware by a program that can be stored in a computer-readable storage medium that, when executed, includes one or a combination of the steps of the method embodiments.

[0168] Furthermore, each functional unit in each embodiment of the present invention may be integrated into one processing module, each unit may exist physically alone, or two or more units may be integrated into one module. The integrated module may be realized in the form of hardware or in the form of a software functional module. When the integrated module is implemented as a software functional module and sold or used as an independent product, it may be stored in a computer-readable storage medium.

[0169] The above mentioned storage medium may be a read-only memory, a magnetic disk, an optical disk, or the like.

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

Claims

1. A data transmission method applied to a Packet Data Convergence Protocol (PDCP) entity, comprising: The PDCP entity is associated with an unacknowledged mode (UM) Radio Link Control (RLC) entity, and the method comprises: determining a target operational mode of the PDCP entity; transmitting data packets to an upper layer protocol entity in numerical order based on the target mode of operation; in response to the target operation mode being a first operation mode, transmitting a first data packet received from a first connection to the upper layer protocol entity in numerical order before using newly configured PDCP configuration information; and after using the newly configured PDCP configuration information, transmitting second data packets received from a second connection to the higher layer protocol entity in numerical order.

2. A data transmission method comprising:

2. in response to the target operating mode being a second operating mode, initializing a variable associated with a reordering window after transmitting the first data packet to the upper layer protocol entity in numerical order; and processing the second data packet using the newly configured PDCP configuration information based on the initialized reordering window.

2. The data transmission method according to claim 1 .

3. responsive to the target operation mode being a third operation mode, globally reordering the first data packet and the second data packet based on respective PDCP configuration information and transmitting the first data packet and the second data packet to an upper layer protocol entity in numerical order; the first data packet is a data packet received from a first connection, the first data packet corresponds to first PDCP configuration information, the first PDCP configuration information is previously configured PDCP configuration information; the second data packet is a data packet received from a second connection, the second data packet corresponds to second PDCP configuration information, and the second PDCP configuration information is newly configured PDCP configuration information; 2. The data transmission method according to claim 1 .

4. stopping a timer for the reordering; 2. The data transmission method according to claim 1 .

5. The first data packet comprises: PDU data packets cached in the PDCP entity; Before using the newly configured PDCP configuration information, the PDCP entity performs a PDU data packet received from the first connection, and At least one of the PDU data packets is delivered to the PDCP entity during re-establishment of the lower protocol entity.

2. The data transmission method according to claim 1 .

6. processing the first data packet based on first PDCP configuration information before transmitting the first data packet to the higher layer protocol entity; and processing the second data packet before transmitting the second data packet to the higher layer protocol entity based on second PDCP configuration information, the second PDCP configuration information being the newly configured PDCP configuration information.

2. The data transmission method according to claim 1 .

7. The first PDCP setting information and the second PDCP setting information each include at least an encryption algorithm and an encryption key.

7. The data transmission method according to claim 6.

8. The first PDCP setting information and the second PDCP setting information, Header decompression / compression settings, further comprising at least one of an integrity protection algorithm and an integrity protection key; 8. The data transmission method according to claim 7.

9. The header decompression / compression settings are: Robust Head Compression (ROHC) decompression / compression settings, and at least one of Ethernet Header Compression (EHC) decompression / compression settings; 9. The data transmission method according to claim 8.

10. The second PDCP configuration information further includes indication information for indicating whether a header decompression / compression configuration context configured in the first PDCP configuration information is to be continued to be used.

9. The data transmission method according to claim 8.

11. The process includes a decoding process and a reordering process.

7. The data transmission method according to claim 6.

12. the processing includes at least one of a header decompression / compression processing and an integrity verification processing; 12. The data transmission method according to claim 11.

13. and in response to the first data packet being a decoded data packet, not performing a decoding process on the first data packet.

12. The data transmission method according to claim 11.

14. In response to a header decompression / compression setting being set in the PDCP configuration information, the processing includes the header decompression / compression processing; In response to an integrity protection algorithm and an integrity protection key being set in the PDCP setting information, the process further includes a step of including an integrity verification process.

13. The data transmission method according to claim 12.

15. and in response to the first data packet generating a free data packet number in a reordering window, not waiting for receipt of the data packet corresponding to the free data packet number.

2. The data transmission method according to claim 1 .

16. In response to the other PDCP entity numbering the second data packets using the newly configured PDCP configuration information, the number of the received second data packets is consecutive to the number of the first data packets.

2. The data transmission method according to claim 1 .

17. and feeding back data packet number information of the first data packet passed to the higher layer protocol entity to the peer PDCP entity.

17. The data transmission method according to claim 16.

18. The step of determining a target operation mode of the PDCP entity comprises: in response to a need to reconstruct a PDCP entity, determining an operation mode to be used by each Radio Link Control (RLC) entity associated with said PDCP entity; determining the target operation mode of the PDCP entity based on at least one of an operation mode used by the RLC entity and a data status feedback indication of the PDCP entity.

2. The data transmission method according to claim 1 .

19. determining the target operation mode of the PDCP entity based on at least one of an operation mode used by the RLC entity and a data status feedback indication of the PDCP entity, determining, in response to the PDCP entity being associated only with a UM RLC entity, that the target mode of operation is a first mode of operation or a second mode of operation; or determining that the target mode of operation is a first mode of operation or a third mode of operation in response to at least one RLC entity of a plurality of RLC entities associated with the PDCP entity using acknowledged mode AM; or determining, in response to the PDCP entity needing to feed back a data reception status, that the target operation mode is a first operation mode or a third operation mode; or determining that the target operation mode is a first operation mode or a third operation mode in response to at least one RLC entity of a plurality of RLC entities associated with the PDCP entity receiving data in a multicast manner and at least one RLC entity receiving data in a unicast manner; 20. The data transmission method according to claim 18.

20. The step of determining a target operation mode of the PDCP entity comprises: receiving an indication carrying an identification of the target operational mode; determining the target operational mode based on the instruction information.

20. The data transmission method according to claim 19.

21. A data transmission device applied to a PDCP entity, comprising: The PDCP entity is associated with a UM RLC entity, and the device: a mode determination module configured to determine a target operational mode of the PDCP entity; a transmission module configured to transmit data packets to an upper layer protocol entity in numerical order based on the target operating mode; The transmission module further comprises: in response to the target operation mode being a first operation mode, transmitting a first data packet received from a first connection to the upper layer protocol entity in numerical order before using newly configured PDCP configuration information; sending second data packets received from a second connection to the upper layer protocol entity in numerical order after using the newly configured PDCP configuration information; A data transmission device comprising:

22. At least one processor; a memory in communication with the at least one processor; The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor such that the at least one processor can perform the data transmission method according to any one of claims 1 to 20. A communication device comprising:

23. A computer storage medium having computer-executable instructions stored thereon, comprising: The computer-executable instructions, when executed by a processor, implement a data transmission method according to any one of claims 1 to 20. A computer storage medium comprising:

Images