RU2807322C1 - Method and device for data transmission - Google Patents

Abstract

FIELD: communications.

SUBSTANCE: invention relates to data transmission in a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in an unacknowledged mode (UM). To do this, the method includes determining the target operating mode of the PDCP entity and, based on the target operating mode, transmitting data packets to the upper layer protocol entity in numbering order. According to the present application, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode, and through some operating modes, data packets can be delivered to the application service faster, and thus latency is reduced. Some operating modes support the ability to wait for new data packets that are not successfully received, which may result in reduced data packet loss.

EFFECT: increased flexibility when transmitting PDCP object data.

22 cl, 10 dwg

Description

TECHNICAL FIELD

[001] The present invention relates to the field of mobile communications and, in particular, to a method and apparatus for transmitting data.

PREREQUISITES FOR CREATION OF THE INVENTION

[002] An MBMS (Multimedia Broadcast and Multicast Service) or a Multicast Broadcast Service (MBS) may be provided over a specific MBS radio bearer (MRB). The MBS may include a common MBS channel and a separate MBS channel. The MBS common channel includes a Packet Data Convergence Protocol (PDCP) entity associated with a Radio Link Control (RLC) entity. A separate MBS channel includes PDCP associated with two RLC entities.

[003] The RLC object, depending on the configuration of the network side, can represent any of the following modes: transparent mode (TM, Transparent Mode), unacknowledged mode (UM, Unacknowledged Mode) and confirmed mode (AM, Acknowledged Mode).

[004] In TM, data received from the Media Access Control (MAC) address layer is directly transmitted transparently to the PDCP entity.

[005] In UM, the data packet received from the MAC layer is sent back to the PDCP entity, but the RLC entity does not maintain feedback whether the RLC data packet was successfully received to the peer RLC entity; And

[006] in AM, packet data received from the MAC layer is sent back to the PDCP entity, and the RLC entity maintains feedback whether the RLC data packet was successfully received with the peer RLC entity. The RLC entity may retransmit the not received data packet in accordance with the feedback message.

[007] In the current state of the art, the PDCP entity associated with the RLC entity in UM mode often directly delivers the received data packet to the upper layer protocol entity in a handover process.

SUMMARY OF THE INVENTION

[008] A method and apparatus for transmitting data, a communication apparatus, and a storage medium provided within the scope of the disclosure of the present invention are used to solve the problem that a Packet Data Convergence Protocol (PDCP) entity often directly delivers a received data packet to a protocol entity top level.

[009] According to a first aspect of embodiments of the present invention, a data transmission method applicable to a PDCP entity is provided. The PDCP entity is associated with the radio link control (RLC) entity in unacknowledged mode (UM). The method includes determining a target operating mode of a PDCP entity and transmitting a data packet to an upper layer protocol entity in a numbering order based on the target operating mode.

[0010] In accordance with a second aspect of embodiments of the present invention, there is provided a data transmission device usable in a PDCP entity. The PDCP entity is associated with the RLC entity in UM mode. The device comprises a determination module configured to determine a target operating mode of a PDCP entity; and a transmission module configured to transmit the data packet to the upper-layer protocol entity in a numbering order based on the target operating mode.

[0011] In accordance with a third aspect of embodiments of the present invention, a communication device is provided. The communication device contains: at least one processor and a memory connected for communication with at least one processor. The memory stores instructions executed by at least one processor. When the instructions are executed by the at least one processor, the processor executes a data communication method in accordance with the first aspect of the present disclosure or a data communication method in accordance with the second aspect of the present invention.

[0012] In accordance with a fourth aspect of embodiments of the present invention, there is provided a computer-readable medium on which computer-readable instructions are stored. When the computer-readable instructions are executed by the processor, a data transmission method in accordance with the first aspect of the present disclosure or a data transmission method in accordance with the second aspect of the present invention is implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and/or additional aspects and advantages of the disclosure of the present invention will become apparent and clear from the following description of the embodiments with reference to the accompanying drawings.

[0014] In FIG. 1 is a flowchart illustrating an implementation of a data transmission method in accordance with an embodiment of the present invention;

[0015] In FIG. 2 is a flowchart illustrating implementation of another data transmission method in accordance with an embodiment of the present invention;

[0016] In FIG. 3 is a block diagram illustrating a reorder window in accordance with an embodiment of the present invention;

[0017] In FIG. 4 is a flowchart illustrating implementation of another data transmission method in accordance with an embodiment of the present invention;

[0018] In FIG. 5 is a flowchart illustrating implementation of another data transmission method in accordance with an embodiment of the present invention;

[0019] In FIG. 6 is a flowchart illustrating implementation of another data transmission method in accordance with an embodiment of the present invention;

[0020] In FIG. 7 is a flowchart illustrating implementation of another data transmission method in accordance with an embodiment of the present invention;

[0021] In FIG. 8 is a block diagram illustrating a data transmission apparatus according to an embodiment of the present invention;

[0022] In FIG. 9 is a block diagram illustrating another data transmission device in accordance with an embodiment of the present invention;

[0023] In FIG. 10 is a block diagram illustrating a communication device in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0024] Embodiments of the present invention are described in detail below. Examples of embodiments of the invention are shown in the accompanying drawings, in which the same or similar numerals indicate the same or similar components or components performing the same or similar functions. The embodiments of the invention described below with reference to the accompanying drawings are illustrative and are used to explain the disclosure of the present invention, but are not intended to limit the disclosure.

[0025] In FIG. 1 shows a flowchart of a data transmission method according to an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM). Additionally, at least one of one or more RLC entities associated with the PDCP is configured in the UM. The PDCP object may be a PDCP object in a user equipment (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 shown in FIG. 1, the data transmission method includes the following steps.

[0027] In step S101, the target operating mode of the PDCP entity is determined.

[0028] According to embodiments of the present invention, a plurality of operating modes are configured for a PDCP entity. The target operating mode may be determined based on a plurality of operating modes for the PDCP entity through protocol convention or configuration indication information.

[0029] As an exemplary implementation, the target operating mode of a PDCP entity may be determined using a protocol convention. Additionally, if recovery of a PDCP entity is required, the operating mode used by each RLC entity associated with the PDCP entity is determined, and the target operating mode used by the PDCP entity is determined based on the operating mode used by each RLC entity.

[0030] As a possible implementation, each operating mode may be associated with one piece of identification information, so that the indication information can be further configured. The indication information is configured using 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] In step S102, the data packet is transmitted to the upper-layer protocol entity in numbering order based on the target operating mode.

[0032] The operating mode of the PDCP entity may be operating mode A or operating mode B.

[0033] In operating mode A, the old Protocol Data Unit (PDU) data packet stored in the PDCP object is delivered directly. In some implementations, operating mode A may include a first operating mode and a second operating mode. Additionally, the first operating mode is referred to as operating mode 1-1, and the second operating mode is referred to as operating mode 1-2, which are merely examples and cannot be used to limit the disclosure of the present invention.

[0034] Additionally, in operating mode 1-1, the PDCP entity may reorder all stored old data packets (e.g., old data packets may be reordered in numerical order from lowest value to highest value) before receiving a new data packet, and deliver the reordered old packets data into the top-level protocol object in numerical order. In addition, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers the reordered new data packets to the upper layer protocol entity in numbered order.

[0035] Additionally, in operating mode 1-2, the PDCP entity may reorder all stored old data packets (e.g., old data packets may be reordered in numerical order from lowest value to highest value) before receiving new data packets, delivering the reordered data packets to the top-level protocol object in numerical order and initialize the variable associated with the reorder window. In addition, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers the reordered data packets to the upper layer protocol entity in numbered order.

[0036] It should be noted that in the 1-1 operating mode, the reordering window is not initialized as in the 1-2 operating mode, so data can be transmitted by continuously using the data packet counter, and the delay in data transmission can also be reduced.

[0037] In runtime mode, old data packets stored in the PDCP entity wait for new data packets to be received, and all data packets in the PDCP entity are reordered before delivery. Additionally, the PDCP entity first processes all old data packets stored before receiving new data packets. The PDCP entity then accepts new data packets for processing. The PDCP entity performs a general reordering of processed old data packets and processed new data packets, and delivers the reordered old data packets and reordered new data packets to the upper layer protocol entity in numbered order. In accordance with embodiments of the present invention, operating mode B may be referred to as third operating mode.

[0038] As a possible implementation, the reorder timer may be stopped. According to some implementations, the reordering timer (ie, t-Reordering) is pre-configured for reordering. The reorder timer counts down when reordering begins and stops when the reorder time value is reached. For example, before a data packet with a higher counter is delivered to an upper layer protocol entity, if a data packet with a lower counter is not received, then a data packet with a lower counter is expected to arrive within the reordering timer. When the reordering timer expires, the data packet with the lower counter is no longer expected, while the data packet with the higher counter is directly delivered to the upper-layer protocol entity and the reordering timer is stopped. That is, when the reordering timer expires, the PDCP entity does not wait for a data packet with a lower counter that has not yet been received, and directly passes the existing received ordered data packet to the upper-layer protocol entity.

[0039] The PDCP entity performs data packet reordering based on the data packet counter (COUNT) using a reordering window mechanism. The maximum counter value for PDCP COUNT that a PDCP object can use for reordering is half the maximum value of the PDCP Serial Number, that is, the reordering window size Window_Size=2 ^{[pdcp-SN-Size DL]-1} where "pdcp-SN-SizeDL" is the number of PDCP SN bits.

[0040] According to embodiments of the present invention, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode. In operating mode A, the data packet can be delivered to the application service faster, resulting in reduced latency. In operating mode B, there is a function that supports waiting for new data packets that are not received successfully, which can result in reduced data packet loss.

[0041] For example, the target operating mode configured for the PDCP entity is operating mode 1-1 in operating mode A, that is, the first operating mode, the data transmission process of the PDCP entity is described next. In fig. 2 shows a flowchart for another data transmission method in accordance with an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM).

[0042] In step S201, the target operating mode of the PDCP entity is determined.

[0043] Step S201 may be implemented in accordance with any possible embodiment of the disclosure, and these embodiments will not be described again.

[0044] In step S202, if the target operating mode is the first operating mode, before using the newly configured PDCP configuration information, the first data packet received on the first link is transmitted to the upper layer protocol entity in number order.

[0045] It should be noted that in order to distinguish the newly configured PDCP configuration information from the previous configured PDCP configuration information, according to embodiments of the present invention, the previous configured PDCP configuration information is called the first PDCP configuration information, and the newly configured PDCP configuration information is called the second PDCP configuration information. That is, the first PDCP configuration information is the PDCP configuration information used before the PDCP entity applies the second PDCP configuration information.

[0046] For example, the network side allows the PDCP entity to be in operating mode 1-1 through a configuration indication, and before the configuration indication is received, the old configuration used by the PDCP entity is the first PDCP configuration information. At the same time or later, the network side performs configuration and indicates that the PDCP entity is in operating mode 1-1. Additionally, the network side indicates a new configuration of the PDCP entity, and the new configuration used by the PDCP entity is the second PDCP configuration information.

[0047] In the following embodiments, a data transmission method according to the present disclosure implemented by first PDCP configuration information and second PDCP configuration information is described.

[0048] Before using the second PDCP configuration information, a first data packet received on the first link is processed before being transmitted to an upper-layer protocol entity based on the first configuration information, and the processed first data packet is transmitted to the upper-layer protocol entity in numbering order.

[0049] For example, the first link may be the original link in the handover process, and the first data packet may be a data packet delivered to the PDCP entity from an RLC entity associated with the original link.

[0050] According to embodiments of the present invention, 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 contains old data stored in the PDCP entity.

[0051] Additionally, the first data packet may contain at least one of the following:

[0052] a protocol data unit (PDU) data packet cached in the PDCP object;

[0053] a PDU data packet received on the first link before using the second PDCP configuration information, for example, the PDCP entity is an entity on the UE side, and the received PDU data packet may be a PDU data packet received from the source cell in the UE handover process; or

[0054] A PDU data packet delivered to a PDCP entity in a lower layer protocol entity recovery process before using the second PDCP configuration information, for example, a data packet stored in an RLC entity is delivered to a PDCP entity in a RLC entity recovery process.

[0055] Additionally, both the first PDCP configuration information and the second PDCP configuration information include at least an encryption algorithm and an encryption key.

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

[0057] packet header compression/decompression configuration or data integrity protection algorithm and data integrity protection key.

[0058] The packet header compression/decompression configuration includes a Robust Header Compression (ROHC) configuration and/or an Ethernet Header Compression (EHC) configuration. Additionally, the ROHC configuration includes an ROH compression/decompression configuration; and the EHC configuration includes the EHC compression/decompression configuration.

[0059] Additionally, the second PDCP configuration information also includes indication information for indicating whether the packet header compression/decompression configuration context configured in the first PDCP configuration information should continue to be used.

[0060] For example, in case an ROHC configuration is configured, the second PDCP configuration information may also indicate whether the ROHC compression context configured in the first PDCP configuration information can continue to be used. According to the implementation, the second PDCP configuration information may carry drb-ContinueROHC indication information that indicates whether the ROHC compression context configured in the first PDCP configuration information can continue to be used.

[0061] In case the EHC configuration is configured, the second PDCP configuration information may also indicate whether the EHC compression context configured in the first PDCP configuration information can continue to be used. According to the implementation, the second PDCP configuration information may carry drb-ContinueEHC indication information that indicates whether the EHC compression context configured in the first PDCP configuration information can continue to be used.

[0062] Additionally, the second PDCP configuration information configures packet header compression/decompression and does not indicate whether the header compression/decompression context configured in the first PDCP configuration information can continue to be used, and the PDCP entity performs packet header decompression for the second data packet using compression/decompression. decompressions configured in the second PDCP configuration information. For example, in the case where there is no "drb-ContinueROHC" indication for ROHC or no "drb-ContinueEHC" indication for EHC, there is no indication that the packet header compression/decompression context configured in the first PDCP configuration information can continue to be used. In this case, if the PDCP entity applies the packet header compression/decompression configuration configured in the second PDCP configuration information, then the packet header compression/decompression configuration configured in the first PDCP configuration information is not available.

[0063] Additionally, the second PDCP configuration information configures packet header compression/decompression and indicates that the packet header compression/decompression context configured in the first PDCP configuration information can continue to be used, and the PDCP entity performs packet header decompression for the second data packet using compression/decompression. decompressing the packet header configured in the first PDCP configuration information. For example, in case there is a "drb-ContinueROHC" indication for ROHC or a "drb-ContinueEHC" indication for EHC, then there is an indication that the packet header compression/decompression context configured in the first PDCP configuration information can continue to be used. At the same time, the PDCP entity performs packet header compression/decompression for the second data packet using the packet header compression/decompression configuration configured in the first PDCP configuration information.

[0064] According to embodiments of the present invention, processing of the first data packet includes decryption and reordering processing.

[0065] Before using the second PDCP configuration information, the PDCP entity reorders the received first data packet in number order based on the first PDCP configuration information. In some implementations, the PDCP entity performs decryption processing for the first data packet based on the first PDCP configuration information and reorders the decrypted first data packet in numbering order.

[0066] Additionally, the processing for the first data packet may also include packet header compression/decompression processing and/or data integrity checking processing.

[0067] It should be noted that if the first PDCP configuration information is configured using a packet header compression/decompression configuration, then processing of the first data packet may include packet header compression/decompression processing. Packet header decompression can be performed in the numbering order of the data packet. For example, unpacking can be performed sequentially in numerical order, from smallest value to largest value.

[0068] In case the first PDCP configuration information is configured using a data integrity protection algorithm and a data integrity protection key, the processing for the first data packet may include data integrity checking processing.

[0069] As a possible implementation, if the first data packet is a processed data packet, the PDCP entity no longer performs the above processing of the first data packet using the first PDCP configuration information, such as decryption processing, packet header compression/decompression processing, and/or processing data integrity checks. That is, before determining the target operating mode used by the PDCP entity, if it is determined that the PDCP entity has performed the specified processing for the first data packet using the first PDCP configuration information, the PDCP entity no longer performs the above processing using the first PDCP configuration information. For example, a PDCP entity typically may perform decryption processing of the first data packet using the first PDCP configuration information immediately after receiving the first data packet, without waiting for the data packet to be reordered in numbering order and then perform decryption. According to embodiments of the present invention, if the first data packet is a decrypted data packet in the case of receiving an operating mode indication, the PDCP entity does not perform a decryption process of the stored first data packet.

[0070] In addition, the PDCP entity reorders the processed first data packet in the data packet numbering order. For example, reordering may be performed in order of the data packet numbering from smallest value to largest value.

[0071] The PDCP entity reorders the data packet using a reorder window mechanism. In fig. 3 is a block diagram illustrating a reordering window. As shown in FIG. 3, the reorder window lower boundary variable is "RX_DELIV". "RX_DELIV" indicates the count of the PDU data packet that was not delivered to the upper layer protocol entity. The PDCP entity updates the reorder window lower bound variable "RX_DELIV" based on the count of the PDU data packet delivered to the upper layer protocol entity. While waiting to receive a PDU, the PDCP entity may start a reordering timer, and when the reordering timer expires, the PDCP entity ignores the "PDU Pending Counter" and updates the lower bound of the reordering window. If PDCP receives a data packet outside the reordering window, the PDCP entity may discard the data packet. The variable "RX_REORD" specifies the data packet counter when the reorder timer starts. "RX_NEXT" indicates the counter of the next PDU to be received. As shown in FIG. 3, the initial values of the PDCP object variables "RX_DELIV" and "RX_NEXT" are "0". If a PDU with a count of "1" is received, this indicates that a PDU with a count of "0" has not been received. The PDCP entity updates "RX_NEXT" to a value of "2" if it needs to start the reorder timer , the value of "RX_REOR" is set to "2". If a PDU whose count is "2" is received, the value of "RX_NEXT" is updated to "3".

[0072] According to embodiments of the present invention, if the PDCP entity is in operating mode 1-1, the first data packet is directly delivered in numerical order without waiting for the subsequent data packet to be received.

[0073] The PDCP entity may generate a vacancy counter in the reordering window when reordering the first data packet. According to embodiments of the present invention, the PDCP stops waiting for the reception of a data packet corresponding to the vacancy counter, and can directly deliver the first data packet to the upper layer protocol entity in numbering order. For example, a PDCP entity processes 1/3 PDU data packets and delivers the processed 1/3 PDU data packets to an upper layer protocol entity using the first PDCP configuration information. Since the reordering window is not initialized, the PDCP entity may continue to use the previous counter and receive 0/2/4 data PDUs, and 1/3 data PDUs may create a vacancy in the reordering window. The PDCP entity may ignore receiving 1/3 data packets corresponding to the vacancy counter. For example, the reorder timer may not start.

[0074] In step S203, the second data packet received on the second link is transmitted to the upper layer protocol entity in number order after using the second PDCP configuration information.

[0075] According to some implementations, the PDCP entity processes the second data packet received on the second link based on the second PDCP configuration information and reorders the processed second data packet based on the data packet counter. For example, the second link may be a target link in a handover process. The second data packet may be a data packet delivered from an RLC entity associated with a PDCP entity.

[0076] According to embodiments of the present invention, processing of the second data packet includes decryption and reordering processing.

[0077] Additionally, the processing for the second data packet may also include: packet header compression/decompression processing and/or data integrity checking processing.

[0078] It should be noted that if the second PDCP configuration information is configured using a packet header compression/decompression configuration, then processing the second data packet may include packet header compression/decompression processing.

[0079] In case the second PDCP configuration information is configured using a data integrity protection algorithm and a data integrity protection key, the processing for the second data packet may include data integrity checking processing.

[0080] In addition, the PDCP entity reorders the processed second data packet in data packet counter order. For example, reordering can be done in the order of the data packet counter from lowest value to highest value.

[0081] According to embodiments of the present invention, since the PDCP entity does not initialize variables associated with the reorder window, if the peer PDCP entity numbers a new data packet (i.e., a second data packet) using the second PDCP configuration information, the second data packet counter continues to count counter readings of the first data packet. Accordingly, the counter of the second data packet received by the PDCP entity and the counter of the first data packet are sequential counters, and the counter of the second data packet continues to count after the counter of the first data packet. For example, if a PDCP entity delivers processed PDU data packets to an upper layer protocol entity after processing 1/3 PDU data packets using the first PDCP configuration information, since the reordering window is not initialized in operating mode 1-1, the initial value of the peer PDCP entity's transmit data counter with respect to the PDCP entity is set to 4, and the peer PDCP entity transmits 4/5 data packets to the PDCP entity.

[0082] In addition, the PDCP entity delivers the second data packet to the upper layer protocol entity in reordered numbering order.

[0083] For example, let the target operating mode be configured as 1-1, before receiving a new data packet or using the second configuration information, the PDCP entity processes the stored first data packet based on the first PDCP configuration information, reorders the processed first data packet in the order of the data packet counters ( for example, from the smallest value to the largest) and sequentially delivers the processed data packet to the upper-level protocol object. For example, in the first PDCP configuration information, encryption configuration 1 and packet header compression configuration 1 for the PDCP entity are configured. PDCP Data Packet 2 and PDCP Data Packet 4 are stored in the PDCP entity reorder window, and these packets are the first data packets received by the PDCP entity. If 2/4 data packets have been decrypted using encryption configuration 1 and have not been decompressed so far, PDCP data 2/4 packets need to be decompressed using packet header compression configuration 1, and then these packets are delivered to the upper layer protocol entity in counter order data packets. That is, the PDCP entity does not need to wait to receive PDCP Data Packet 1 and PDCP Data Packet 3 before delivering Data Packets 1/2/3/4 sequentially to the upper layer protocol entity.

[0084] In some embodiments, the method may also include the following steps.

[0085] In step S204, the data packet counter information for the first data packet delivered to the upper layer protocol entity is returned to the peer PDCP entity.

[0086] The counter information includes at least one of the following:

[0087] a maximum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity;

[0088] the maximum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity, plus 1;

[0089] the maximum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity, minus 1;

[0090] a minimum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity;

[0091] the minimum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity, plus 1;

[0092] the minimum counter of the first data packet processed by the first PDCP configuration information and delivered to the upper layer protocol entity, minus 1; or

[0093] the total data amount of the first data packet processed by the first configuration information and delivered to the upper-layer protocol entity.

[0094] According to embodiments of the present invention, in the case of a PDCP entity recovery indication, the target operating mode is configured as operating mode 1-1. In this case, the PDCP entity can obtain the second PDCP configuration information, and the encryption configuration 2 and the packet header compression configuration 2 are configured in the second PDCP configuration information. The PDCP entity receives a new data packet (ie, a second data packet) based on the second PDCP configuration information and processes the second data packet. That is, the PDCP entity decrypts PDCP data 2/4 packets using encryption configuration 2 and delivers the decompressed PDCP data 2/4 packets to the upper layer protocol entity in the order of data packet numbering after decompression using packet header compression configuration 2.

[0095] According to embodiments of the present invention, if the target operating mode of a PDCP entity is configured as operating mode 1-1, data transmission is performed based on operating mode 1-1. Since waiting for vacant data packets to be received is stopped, the data packet can be delivered to the application service faster, resulting in reduced latency. In addition, in the 1-1 operating mode, the reordering window is not initialized, so data can be transmitted by continuously using the data packet counter, and the delay of data transmission can also be reduced.

[0096] For example, the target operating mode configured for the PDCP entity is operating mode 1-2 in operating mode A (that is, the second operating mode), the data transmission process of the PDCP entity is described next. In fig. 4 shows a flowchart for another data transmission method in accordance with an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM).

[0097] In step S401, the target operating mode of the PDCP entity is determined.

[0098] In step S402, in case the target operating mode is the second operating mode, before using the second PDCP configuration information, the first data packet received on the first link is transmitted to the upper layer protocol entity in number order.

[0099] Steps S401 and S402 may be implemented in accordance with any possible embodiments of the present invention, which are not further described again.

[00100] In step S403, a variable associated with the reordering window is initialized.

[00101] As shown in FIG. 3, according to an embodiment of the present invention, setting the initial value of a variable associated with a reorder window includes at least one of the following operations:

[00102] setting the initial value of the "variable for indicating the next data packet to be received", for example, the initial value of the variable "RX_NEXT" may be set to "0"; or

[00103] Setting the initial value of the "variable for indicating the lower boundary of the reordering window", for example, the initial value of the variable "RX_DELIV" may be set to "0".

[00104] In step S404, the second data packet received on the second link is processed using the second PDCP configuration information based on the post-initialization reordering window.

[00105] If the reorder window is initialized, a variable associated with the reorder window may start counting from the initial value. Moreover, according to an embodiment of the present invention, processing of the second data packet includes decryption and reordering processing. Additionally, the processing for the second data packet may also include packet header compression/decompression processing and/or data integrity checking processing.

[00106] It should be noted that if the second PDCP configuration information is configured using a packet header compression/decompression configuration, then processing of the second data packet may include packet header compression/decompression processing. In case the second PDCP configuration information is configured using a data integrity protection algorithm and a data integrity protection key, the processing for the second data packet may include data integrity checking processing.

[00107] If the PDCP entity delivers processed PDU data packets to the upper layer protocol entity after processing 1/3 PDU data packets using the first PDCP configuration information, since the reordering window may be initialized in operating mode 1-2, the peer PDCP entity may renumber the counters 2/4 PDU data packets that have not yet been transmitted, that is, the PDCP peer starts transmitting PDU data packets with an initial value set to 0 and may, within the reordering window, not generate 1/3 vacancy counters as in the 1-1 operating mode.

[00108] At step 405, the second data packet is transmitted to the upper layer protocol entity in numerical order.

[00109] In addition, the PDCP entity reorders the processed second data packet in data packet numbering order and transmits the second data packet to the upper layer protocol entity in numbering order. For example, reordering can be done in the order of data packet counters from lowest value to highest value.

[00110] Descriptions of the first PDCP configuration information and the second PDCP configuration information can be found above in the respective embodiment sections and therefore are not repeated.

[00111] Descriptions of the processing process of the first data packet based on the first PDCP configuration information and the processing process of the second data packet based on the second PDCP configuration information can be found above in the respective embodiment sections and therefore are not repeated.

[00112] According to embodiments of the present invention, if the target operating mode of a PDCP entity is configured as operating mode 1-2, data transmission is performed based on operating mode 1-2. Since the reordering window is initialized, vacancy counters may not appear and waiting for vacant data packets to be received is stopped, as a result of which the delay caused by reordering is reduced and the data packet can be delivered to the application service faster.

[00113] For example, the target operating mode configured for the PDCP entity is operating mode B (that is, the third operating mode), the data transmission process of the PDCP entity is described next. In fig. 5 shows a flowchart for another data transmission method in accordance with an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM).

[00114] In step S501, the target operating mode of the PDCP entity is determined.

[00115] Step S501 may be implemented in accordance with any possible embodiment of the present invention, and these embodiments will not be further described again.

[00116] In step S502, in the case where the target operating mode is the third operating mode, general reordering of the first data packet and the second data packet is performed based on the corresponding PDCP configuration information, and the reordered first data packet and the reordered second data packet are transmitted to the upper protocol entity. levels in numerical order.

[00117] It should be noted that the first data packet is a data packet received on the first communication link, the first data packet corresponds to the first PDCP configuration information, and the first PDCP configuration information is the previous configured PDCP configuration information. Additionally, the first link may be the original link in the handover process, and the first data packet may be a data packet delivered to the PDCP entity from an RLC entity associated with the original link.

[00118] The second data packet is a data packet received on a second link, the second data packet corresponds to second PDCP configuration information, and the second PDCP configuration information is newly configured PDCP configuration information. Additionally, the second link may be a target link in the handover process, and the second data packet may be a data packet delivered to a PDCP entity from an RLC entity associated with the target link.

[00119] The PDCP entity processes the first data packet using the first PDCP configuration information before using the second PDCP configuration information. The processing may include at least decryption processing. A description of the process of decrypting the first data packet using the first PDCP configuration information can be found above in the respective embodiment sections and is therefore not repeated.

[00120] The PDCP entity processes the second data packet using the second PDCP configuration information. The processing may include at least decryption processing. A description of the process of decrypting the second data packet using the second PDCP configuration information can be found above in the respective embodiment sections and is therefore not repeated.

[00121] In addition, the PDCP entity reorders the processed first data packet and the second data packet and transmits all reordered data packets to the upper layer protocol entity in numerical order.

[00122] For example, in the first PDCP configuration information, encryption configuration 1 and packet header compression configuration 1 for the PDCP entity are configured. The first 2/4 data packets are stored in the PDCP entity 1 reorder window. These data packets are decrypted using encryption configuration 1 and are not decompressed. The PDCP entity may need to wait for 1/3 data packets to be received, reorder all 1/2/3/4 data packets, and deliver the reordered data packets to the upper layer protocol entity in numbered order. In addition, the target operating mode configured for PDCP is operating mode B, and second PDCP configuration information is provided. In the second PDCP configuration information, an encryption configuration 2 and a packet header compression configuration 2 for the PDCP entity are configured. The first 2/4 data packets are decompressed by the PDCP entity using packet header compression configuration 1 and stored in the PDCP entity. The PDCP entity applies the encryption configuration 2 and the packet header compression configuration 2 configured in the second PDCP configuration information, decrypts the second 1/3 data packets using the encryption configuration 2, and decompresses the decrypted 1/3 data packets using the packet header compression configuration 2. The PDCP entity delivers all 1/2/3/4 data packets sequentially to the upper layer protocol entity in numbered order.

[00123] According to embodiments of the present invention, if the target operating mode of a PDCP entity is configured as operating mode B, data transmission is performed based on operating mode B. Operating mode B performs a function that supports waiting for data packets not received successfully, thereby reducing losses data packets.

[00124] In FIG. 6 shows a flowchart for another data transmission method in accordance with an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM).

[00125] In step S601, the operating mode used by each RLC entity associated with the PDCP entity is determined if recovery of the PDCP entity is required.

[00126] According to embodiments of the present invention, the target operating mode of a PDCP entity is determined using a protocol convention. The operating mode used by each RLC entity associated with the PDCP entity often influences the operating mode used by the PDCP entity. Thus, the protocol agreement may specify that the target operating mode of the PDCP entity is based on the operating mode used by the RLC entity.

[00127] Additionally, an indication of PDCP object recovery may be received. If the recovery indication is received, then a determination of the operating mode used by the RLC entity associated with the PDCP entity is initialized. The operating mode used by the RLC entity may be one of the following modes: AM, UM, transparent mode, multicast mode for receiving data, or unicast mode for receiving data.

[00128] Additionally, the operating mode of a PDCP entity is often influenced by whether the PDCP entity returns a receiving state.

[00129] In step S602, the target operating mode of the PDCP entity is determined based on the operating mode used by the RLC entity and/or the data status feedback indication of the PDCP entity.

[00130] If only the RLC entity in UM mode is associated with the PDCP entity, then it is determined that the target operating mode of the PDCP entity is operating mode A, that is, the first operating mode or the second operating mode, namely operating mode 1-1 or operating mode 1-2. For example, a PDCP entity is associated with one or more RLC entities in the UM. If it is indicated that the PDCP entity should be restored, then the PDCP entity may be in operating mode A.

[00131] If at least one of the plurality of RLC entities associated with the PDCP entity is in AM mode, then the target operating mode of the PDCP entity is determined to be the first operating mode or the third operating mode (i.e., operating mode 1-1 in operating mode A or operating mode B). For example, a PDCP entity is associated with two RLC entities, with RLC entity 1 configured in the UM and RLC entity 2 configured in the AM. If it is indicated that the PDCP entity should be restored, then the PDCP entity may be in operating mode B.

[00132] If the PDCP entity needs to return a data reception state, then the target operating mode of the PDCP entity is determined to be the first operating mode or the third operating mode (ie, operating mode 1-1 in operating mode A or operating mode B). For example, a PDCP entity is associated with two RLC entities, with RLC entity 1 and RLC entity 2 configured in the UM. However, the PDCP entity needs to convey the data reception status of the PDCP entity to the peer PDCP entity via the RLC entity 2, that is, for example, it is required to report the status to the peer PDCP entity. If it is indicated that the PDCP entity should be restored, then the PDCP entity may be in operating mode B.

[00133] If at least one of a plurality of RLC entities associated with a PDCP entity receives data in a multicast mode, and at least one of a plurality of RLC entities receives data in a unicast mode, then the target operating mode of the PDCP entity is determined to be the first operating mode or a third operating mode, that is, operating mode 1-1 in operating mode A or operating mode B. For example, a PDCP entity is associated with two RLC entities, with RLC entity 1 configured to receive point-to-multipoint data (PTM, Point To Multipoint), and the RLC object 2 is configured to receive data in point-to-point mode (PTP, Point To Point). If it is indicated that the PDCP entity should be restored, then the PDCP entity may be in operating mode B.

[00134] Descriptions of operating mode 1-1, operating mode 1-2, and operating mode B can be found above in the respective embodiment sections and are therefore not repeated.

[00135] In step S603, the data packet is transmitted to the upper-layer protocol entity in numbering order based on the target operating mode.

[00136] Step S603 may be implemented in accordance with any possible embodiment of the present invention, which will not be described again.

[00137] According to embodiments of the present invention, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode. In operating mode A, data packets can be delivered to the application service faster, resulting in reduced latency. In operating mode B, there is a function that supports waiting for new data packets that are not received successfully, which can result in reduced data packet loss.

[00138] In FIG. 7 shows a flowchart for another data transmission method in accordance with an embodiment of the present invention. The main component of the data transmission method is a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in unacknowledged mode (UM).

[00139] In step S701, indication information is received. The indication information carries identification information of the target operating mode.

[00140] According to embodiments of the present invention, each operating mode may contain one piece of identification information, so that the indication information can be further configured. The indication information is configured using identification information of the target operating mode to be selected. The PDCP entity can receive the indication information and further retrieve the identification information in the target operating mode.

[00141] In step S702, the target operating mode of the PDCP entity is determined based on the indication information.

[00142] For example, the identification information of the first operating mode (i.e., operating mode 1-1) may be A-1, the identification information of the second operating mode (i.e., operating mode 1-2) may be A-2, and the identification information the third operating mode (ie, operating mode B) may be B. For example, based on A-1 carried in the PDCP recovery process, it may be indicated that the target operating mode used by the PDCP entity is operating mode 1-1. In another example, based on A-2 carried in the PDCP recovery process, it may be indicated that the target operating mode used by the PDCP entity is operating mode 1-2. In another example, based on the B carried during the PDCP recovery process, it may be indicated that the target operating mode used by the PDCP entity is operating mode B.

[00143] In step S703, the data packet is transmitted to the upper-layer protocol entity in numbering order based on the target operating mode.

[00144] Step S703 may be implemented in accordance with any possible embodiment of the present invention, which will not be described again.

[00145] According to embodiments of the present invention, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode. In operating mode A, data packets can be delivered to the application service faster, resulting in reduced latency. In operating mode B, there is a function that supports waiting for new data packets that are not received successfully, which can result in reduced data packet loss.

[00146] According to a data transmission method according to embodiments of the disclosure, a data transmission device is also provided within the scope of the disclosure of the present invention. Since the data transmission apparatus according to the disclosure of the present invention is consistent with the data transmission method, embodiments of which are shown in FIGS. 1-7, the implementation of the data transmission method is also applicable to the data transmission device and is not described in the subsequent embodiments of the device disclosure.

[00147] In FIG. 8 is a block diagram illustrating a data transmission apparatus in accordance with an embodiment of the present invention. The data communication device is applicable in a PDCP entity associated with an RLC entity in UM mode. Additionally, at least one of one or more RLC entities associated with the PDCP is configured in the UM. The PDCP entity may be a PDCP entity in a user equipment (UE) or a network device. The PDCP entity in the UE and the PDCP entity in the network device are peer PDCP entities.

[00148] As shown in FIG. 8, the data transmission device 800 may include a mode determination module 81 and a transmission module 82.

[00149] The mode determination module 81 is configured to determine the target operating mode of the PDCP entity.

[00150] The transmission module 82 is configured to transmit the data packet to the upper layer protocol entity in numbering order based on the target operating mode.

[00151] According to embodiments of the present invention, a plurality of operating modes are configured for a PDCP entity. The target operating mode may be determined based on a plurality of operating modes for the PDCP entity through protocol convention or configuration indication information.

[00152] As a possible implementation, the target operating mode of a PDCP entity may be determined using a protocol convention. Additionally, if recovery of a PDCP entity is required, the operating mode used by each RLC entity associated with the PDCP entity is determined, and the target operating mode used by the PDCP entity is determined based on the operating mode used by the RLC entity.

[00153] As a possible implementation, each operating mode may be associated with one piece of identification information, so that the indication information can be further configured. The indication information is configured using 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.

[00154] The operating mode of the PDCP entity may be operating mode A or operating mode B.

[00155] In operating mode A, the old protocol data unit (PDU) data packet stored in the PDCP object is delivered directly. In some implementations, operating mode A may include a first operating mode and a second operating mode. Additionally, the first operating mode is referred to as operating mode 1-1, and the second operating mode is referred to as operating mode 1-2, which are merely examples and cannot be used to limit the disclosure of the present invention.

[00156] Additionally, in operating mode 1-1, the PDCP entity may reorder all stored old data packets (e.g., old data packets may be reordered in numerical order from lowest value to highest value) before receiving a new data packet, and deliver the reordered old packets data into the top-level protocol object in numerical order. In addition, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers the reordered data packets to the upper layer protocol entity in numbered order.

[00157] Additionally, in operating mode 1-2, the PDCP entity may reorder all stored old data packets (e.g., old data packets may be reordered in numerical order from lowest to highest value) before receiving new data packets and deliver the reordered data packets to the protocol entity top level in numerical order, and also initialize the variable associated with the reorder window. In addition, the PDCP entity continues to receive new data packets, reorders the new data packets, and delivers the reordered data packets to the upper layer protocol entity in numbered order.

[00158] It should be noted that in the 1-1 operating mode, the reordering window is not initialized as in the 1-2 operating mode, so data can be transmitted by continuously using the data packet counter, and the delay in data transmission can also be reduced.

[00159] In runtime mode, old data packets stored in the PDCP object wait for new data packets to be received, and all data packets in the PDCP object are reordered before delivery. Additionally, the PDCP entity first processes all old data packets stored before receiving new data packets. The PDCP entity then accepts new data packets for processing. The PDCP entity performs a general reordering of processed old data packets and processed new data packets, and delivers the reordered old data packets and reordered new data packets to the upper layer protocol entity in numbered order. In accordance with embodiments of the present invention, operating mode B may be referred to as third operating mode.

[00160] As a possible implementation, the timer for reordering may be stopped. According to some implementations, the reordering timer (ie, t-Reordering) is pre-configured for reordering. The reorder timer counts down when reordering begins and stops when the reorder time value is reached. For example, before a data packet with a higher counter is delivered to an upper layer protocol entity, if a data packet with a lower counter is not received, then a data packet with a lower counter is expected to arrive within the reordering timer. When the reordering timer expires, the data packet with the lower counter is no longer expected, while the data packet with the higher counter is directly delivered to the upper-layer protocol entity and the reordering timer is stopped. That is, when the reorder timer expires, the PDCP entity no longer waits for a data packet with a lower counter that has not yet been received, and directly forwards the existing received reordered data packet to the upper layer protocol entity.

[00161] The PDCP entity performs reordering of data packets based on the data packet counter (COUNT) using a reordering window mechanism. The maximum number of counters for PDCP COUNT that a PDCP entity can use for reordering is half the maximum PDCP Serial Number, that is, the reordering window size Window_Size=2 ^{[pdcp-SN-Size DL]-1} where "pdcp-SN-SizeDL" is the number of PDCP SN bits.

[00162] According to embodiments of the present invention, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode. In operating mode A, data packets can be delivered to the application service faster, resulting in reduced latency. In operating mode B, there is a function that supports waiting for new data packets that are not received successfully, which can result in reduced data packet loss.

[00163] In FIG. 9 is a block diagram illustrating the structure of a data transmission apparatus according to an embodiment of the present invention. The data communication device is applicable in a PDCP entity associated with an RLC entity in UM mode. Additionally, at least one of one or more RLC entities associated with the PDCP is configured in the UM. The PDCP entity may be a PDCP entity in a user equipment (UE) or a network device. The PDCP entity in the UE and the PDCP entity in the network device are peer PDCP entities.

[00164] As shown in FIG. 9, the data transmission device 900 may include a mode determination module 91 and a transmission module 92.

[00165] The mode determination module 91 is configured to determine the target operating mode of the PDCP entity.

[00166] The transmission module 92 is configured to transmit the data packet to the upper layer protocol entity in numbering order based on the target operating mode.

[00167] Additionally, the transmission module 92 includes a first transmission block 921 and a second transmission block 922.

[00168] The first transmission unit 921 is configured to transmit, in number order, the first data packet received on the first link to an upper layer protocol entity in case the target operating mode is the first operating mode, before using the newly configured PDCP configuration information.

[00169] The second transmission unit 922 is configured to transmit the second data packet received on the second link to an upper layer protocol entity in number order after using the newly configured PDCP configuration information.

[00170] Additionally, the transmission module 92 also includes an initialization block 923.

[00171] The initialization unit 923 is configured to initialize a variable associated with the reordering window, in case the target operating mode is the second operating mode, after transmitting the first packet to the upper-layer protocol entity in numbering order.

[00172] Transmission unit 922 is configured to process the second data packet using the newly configured PDCP configuration information based on the post-initialization reordering window.

[00173] Additionally, the transmission module 92 is configured, if the target operating mode is the third operating mode, to perform a general reordering of the first data packet and the second data packet based on the corresponding PDCP configuration information and transmitting the reordered first data packet and the reordered second data packet to an upper protocol entity. levels in numerical order.

[00174] The first data packet is a data packet received on the first communication link, the first data packet corresponds to the first PDCP configuration information, and the first PDCP configuration information is the previous configured PDCP configuration information.

[00175] The second data packet is a data packet received on a second link, the second data packet corresponds to second PDCP configuration information, and the second PDCP configuration information is newly configured PDCP configuration information.

[00176] Additionally, as shown in FIG. 9, the data transmission device also includes a timer stop unit 93.

[00177] The timer stop module 93 is configured to stop the reorder timer.

[00178] Additionally, the first data packet includes at least one of the following:

[00179] a protocol data unit (PDU) data packet cached in the PDCP object;

[00180] a PDU data packet received by the PDCP entity on the first link before using the newly configured PDCP configuration information; or

[00181] A PDU data packet delivered to a PDCP entity during the recovery process of a lower layer protocol entity.

[00182] Additionally, as shown in FIG. 9, the data transmission device also includes a processing unit 94.

[00183] The processing unit 94 is configured to process a first data packet based on the first PDCP configuration information before transmitting the first data packet to an upper-layer protocol entity, and process a second data packet based on the second PDCP configuration information before transmitting the second data packet to an upper-layer protocol entity. The second PDCP configuration information is newly configured PDCP configuration information.

[00184] Additionally, both the first configuration information and the second PDCP configuration information include at least an encryption algorithm and an encryption key.

[00185] Additionally, the first configuration information and the second configuration information may also comprise:

[00186] packet header compression/decompression configuration and/or

[00187] a data integrity protection algorithm and a data integrity protection key.

[00188] Additionally, the compression/decompression configuration includes:

[00189] noise-resistant header compression (ROHC)/decompression configuration and/or

[00190] Ethernet Header Compression/Decompression Configuration (ENC).

[00191] Additionally, the second PDCP configuration information also includes indication information for indicating whether to continue to use the packet header compression/decompression configuration context configured in the first PDCP configuration information.

[00192] Additionally, said processing includes decryption and reordering processing.

[00193] Additionally, said processing also includes packet header compression/decompression processing and/or data integrity checking processing.

[00194] Additionally, the processing unit 94 is also configured to stop performing decryption processing of the first data packet if the first data packet is a decrypted data packet.

[00195] Additionally, the processing unit 94 is also configured to perform compression/decompression processing if a packet header compression/decompression configuration is configured in the PDCP configuration information; and performing data integrity checking processing if a data integrity protection algorithm and a data integrity protection key are configured in the PDCP configuration information.

[00196] Additionally, the first transmission unit 921 is also configured to stop waiting for receiving a data packet corresponding to a vacant data packet counter in the event that the first data packet generates a vacant data packet counter in the reordering window.

[00197] Additionally, the second transmit block 922 is also configured, if the PDCP peer entity numbers the second data packet using the newly configured PDCP configuration information, to include the received second data packet counter and the first data packet counter as sequential counters.

[00198] Additionally, the first transmit block 921 is configured to return to the peer PDCP entity data packet counter information for the first data packet delivered to the upper layer protocol entity.

[00199] Additionally, the determination module 91 includes a first determination block 911 and a second determination block 912.

[00200] The first determination block 911 is configured to determine the operating mode used by each RLC entity associated with the PDCP entity if recovery of the PDCP entity is required.

[00201] The second determination unit 912 is configured to determine a target operating mode of the PDCP entity based on the operating mode used by the RLC entity and/or the data status feedback indication of the PDCP entity.

[00202] Additionally, the second determination unit 912 is also configured to

[00203] determining that the target operating mode is the first operating mode or the second operating mode if only the RLC entity in UM mode is associated with the PDCP entity, or

[00204] determining that the target operating mode is the first operating mode or the third operating mode if at least one of the plurality of RLC entities associated with the PDCP entity is in a confirmable mode; or

[00205] determining that the target operating mode is the first operating mode or the third operating mode if the PDCP entity needs to return a data reception state; or

[00206] determining that the target operating mode is the first operating mode or the third operating mode if at least one of the plurality of RLC entities associated with the PDCP entity receives data in a multicast mode, and at least one of the plurality of RLC entities receives data in unicast mode.

[00207] Additionally, the determination module 91 is configured to receive indication information and determine a target operating mode based on the indication information. The indication information carries identification information of the target operating mode.

[00208] According to embodiments of the present invention, a PDCP entity can be configured with different operating modes based on different service scenarios, thereby increasing flexibility in transmitting PDCP entity data. In addition, reordering can be performed in each operating mode. In operating mode A, data packets can be delivered to the application service faster, resulting in reduced latency. In operating mode B, there is a function that supports waiting for new data packets that are not received successfully, which can result in reduced data packet loss.

[00209] In accordance with embodiments of the present invention, a communication device and a computer-readable storage medium are also provided.

[00210] As shown in FIG. 10, the communication device includes one or more processors 1100, a memory 1200, and an interface configured to connect various components, including a high speed interface and a low speed interface. The different components are connected to each other using different buses and can be mounted on a common motherboard or in any other desired manner. The processor may process instructions executed in a communications device, including instructions stored in memory, to display GUI graphical information on an external input/output device (such as a display associated with an interface). In other implementations, multiple processors and/or multiple buses may be shared with multiple memory components as needed. Multiple communication devices can be connected in this manner, with each device performing part of the required operations (eg, in the form of an array of servers, a group of mesh servers, or a multiprocessor system). In fig. Figure 10 shows an example with one processor.

[00211] Memory 1200 is a computer-readable storage medium consistent with the disclosure of the present invention. The memory stores instructions executable by the at least one processor such that the at least one processor performs the data transfer method described within the scope of the disclosure of the present invention. The computer readable storage medium according to the disclosure of the present invention stores computer instructions. The computer instructions are configured to carry out a data communication method according to the disclosure of the present invention.

[00212] Like computer-readable media, memory 1200 may be configured to store computer-executable programs and modules, such as instructions/modules consistent with the data transfer method described within the disclosure of the present invention. The processor 1100 executes various functional applications and processes data on the server by running the program, instruction and module stored in the memory 1200, that is, carries out the data transfer method according to the above-described embodiment.

[00213] The memory 1200 may include a program storage area and a data storage area, wherein the program storage area may store operating systems and application programs required to perform at least one function; and in the data storage area, data generated based on the use of the positioning communication device, etc. can be stored. In addition, memory 1200 may include high-speed random access memory as well as read-only memory, such as at least one of magnetic disk, flash memory, or other read-only solid-state storage devices. In some embodiments, memory 1200 further includes memory located remotely to processor 1100 that can be coupled to a communication device over a network. Examples of such networks include, but are not limited to, the Internet, an enterprise Intranet, a local area network, a mobile phone network, and combinations thereof.

[00214] The communication device may also include an input device 1300 and an output device 1400. The processor 1100, memory 1200, input device 1300, and output device 1400 may be connected via a bus or other means. In fig. 10 shows an example of a bus connection.

[00215] The input device 1300 may receive digital or character input and generate an input control signal associated with user settings and functional control of the position communication device, and may be, for example, a touch pad, a keyboard, a mouse, a touch pad, a touch keyboard, a pointing stylus, one or more mouse buttons, a trackball, a joystick, and other input devices. The output device 1400 may include a display, an auxiliary lighting device (eg, an LED), and a haptic feedback device (eg, a vibration motor), etc. The display may include, but is not limited to, an LCD (Liquid Crystal Display), an LED (Light Emitting Diode), and a plasma display. In some implementations, the display may be a touch screen.

[00216] The various modes of implementation of the systems and technologies described above may be based on the use of digital electronic circuits, integrated circuits, application specific integrated circuits (ASIC), computer hardware, firmware, software and/or combinations thereof . The various implementation modes include implementation in one or more computer programs, and the one or more computer programs may be executed and/or interpreted on a programmable system, including at least one programmable processor. A programmable processor may be a special-purpose or general-purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to a storage system, at least one input device and at least one output device.

[00217] Computer programs (also called programs, software, software applications or code) contain machine instructions for a programmable processor and can be implemented using high-level procedural and/or object-oriented programming languages, and/or using assembly/machine language language. As used herein, the term "machine-readable medium" refers to any computer program product, device and/or equipment (such as a magnetic disk, optical disk, memory, programmable logic device (PLD)) configured to provide machine instructions and/or data to a programmable processor, including a computer-readable medium that receives the machine instructions in the form of computer-readable signals. The term "machine-readable signal" refers to any signal configured to provide machine instructions and/or data to a programmable processor.

[00218] To provide user interaction, the systems and technologies described above may be implemented on a computer equipped with a display that displays information to the user (for example, a CRT (Cathode Ray Tube) or LCD monitor); and a keyboard and pointing device (such as a mouse or trackball) that allows the user to enter data into the computer. In addition, other types of devices may be used to interact with the user, for example, the feedback provided to the user may be any type of sensory feedback (for example, visual feedback, auditory feedback, or haptic feedback), and input from the user can be received in any form (including acoustic, speech or tactile input).

[00219] The systems and technologies described above may be implemented in a computer system including server components (e.g., a data server), or in a computer system that includes intermediate components (e.g., an application server), or in a computer system that includes client components (e.g., a user computer equipped with a graphical user interface or web browser through which the user can interact with the system implementation mode and technology described above), or in a computing system including any combination of such server, middleware, or client components. System components may be connected to each other by any means or digital media (eg, a network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), a network based on blockchain technology, and the Internet.

[00220] A computer system may include a client and a server. The client and server are usually separated from each other and communicate through a communication network. Communication between the client and the server is usually carried out through computer programs running on the corresponding computer and having a client-server relationship.

[00221] Those skilled in the art will appreciate that all or some of the steps, including one step or a combination of method steps, in the embodiments described above may be implemented by a program that controls associated hardware, and the program may be stored on a machine-readable storage medium.

[00222] In addition, functional blocks in various embodiments of the present invention may be integrated into a processing module or physically installed separately, or two or more blocks may be integrated into a single module. The above integrated module may be implemented as a hardware or software function module. The integrated module may be stored on a computer-readable storage medium if implemented as a software function module, and sold or used as an independent product.

[00223] The above storage device may be a read-only memory, a magnetic disk or a compact disk, etc.

[00224] The above description contains preferred embodiments of the present invention. It should be noted that certain improvements and modifications can be made by those skilled in the art without departing from the teachings of the present invention, and these improvements and modifications should also be considered to be within the spirit of the present invention.

Claims (54)

1. A data transmission method performed by a packet data convergence protocol (PDCP) entity associated with a radio link control (RLC) entity in an unacknowledged mode (UM), the method including: determining (S101, S201, S401, S501) the target operating mode of the PDCP entity and transmitting (S102, S603, S703) the data packet to the upper layer protocol entity in numbering order based on the target operating mode. 2. The method according to claim 1, also including: in case the target operating mode is the first operating mode, before using the newly configured PDCP configuration information, transmitting (S202) the first data packet received on the first link to the upper layer protocol entity in number order; And, after using the newly configured PDCP configuration information, transmitting (S203) the second data packet received on the second link to the upper layer protocol entity in number order. 3. The method according to claim 2, also including: in case the target operating mode is the second operating mode, after transmitting the first data packet to the upper-layer protocol object in number order, initializing (S403) a variable associated with the reordering window; And processing (S404) the second data packet using the newly configured PDCP configuration information based on the reordering window after initialization. 4. The method according to claim 1, also including: in case the target operating mode is the third operating mode, performing (S502) general reordering of the first data packet and the second data packet based on the corresponding PDCP configuration information, and transmitting the reordered first data packet and the reordered second data packet to the upper layer protocol entity in number order; wherein the first data packet is a data packet received on the first communication link, the first data packet corresponds to the first PDCP configuration information, and the first PDCP configuration information is the previous configured PDCP configuration information; And the second data packet is a data packet received on the second link, the second data packet corresponds to second PDCP configuration information, and the second PDCP configuration information is newly configured PDCP configuration information. 5. The method according to claim 1, also including stopping the reordering timer. 6. The method of claim 2, wherein the first data packet contains at least one of the following: a protocol data unit (PDU) data packet cached in the PDCP object; a PDU data packet received by the PDCP entity on the first link before using the newly configured PDCP configuration information; or a PDU data packet delivered to a PDCP entity during the recovery process of a lower-layer protocol entity. 7. The method according to claim 2, also including: processing the first data packet based on the first PDCP configuration information before transmitting the first data packet to the upper layer protocol entity; and processing the second data packet based on the second PDCP configuration information before transmitting the second data packet to the upper layer protocol entity, wherein the second PDCP configuration information is the newly configured PDCP configuration information. 8. The method of claim 7, wherein both the first PDCP configuration information and the second PDCP configuration information include at least an encryption algorithm and an encryption key. 9. The method of claim 8, wherein the first PDCP configuration information and the second PDCP configuration information also comprise: packet header compression/decompression configuration and/or data integrity protection algorithm and data integrity protection key. 10. The method according to claim 9, in which the packet header compression/decompression configuration contains: a noise-resistant header compression (ROHC)/decompression configuration and/or an Ethernet header compression/decompression configuration (ENC). 11. The method of claim 9, wherein the second PDCP configuration information also includes indication information for indicating whether to continue to use the packet header compression/decompression configuration context configured in the first PDCP configuration information. 12. The method of claim 7, wherein the processing includes decryption processing and reordering. 13. The method of claim 12, wherein the processing also includes packet header compression/decompression processing and/or data integrity checking processing. 14. The method according to claim 12, also including: in case the first data packet is a decrypted data packet, stopping the execution of decryption processing of the first data packet. 15. The method according to claim 13, also including: in case the packet header compression/decompression configuration is configured in the PDCP configuration information, the processing includes compression/decompression processing; And in case the data integrity protection algorithm and the data integrity protection key are configured in the PDCP configuration information, the processing includes data integrity checking processing. 16. The method according to claim 2, also including: if the first data packet generates a vacant data packet counter in the reordering window, stopping waiting for the reception of a data packet corresponding to the vacant data packet counter. 17. The method according to claim 2, also including: in case the PDCP peer entity numbers the second data packet using the newly configured PDCP configuration information, including the received second data packet counter and the first data packet counter as sequential counters. 18. The method according to claim 2, also including: Return to the peer PDCP entity the data packet counter information for the first data packet delivered to the upper layer protocol entity. 19. The method of claim 1, wherein determining the target operating mode of the PDCP entity includes: in case recovery of a PDCP entity is required, determining (S601) the operating mode used by each RLC entity associated with the PDCP entity, and determining (S602) a target operating mode of the PDCP entity based on the operating mode used by the RLC entity and/or the data status feedback indication of the PDCP entity. 20. The method of claim 19, wherein determining a target operating mode of the PDCP entity based on the operating mode used by the RLC entity and/or a data status feedback indication of the PDCP entity comprises one of the following: in case only the RLC entity in UM mode is associated with the PDCP entity, determining that the target operating mode is the first operating mode or the second operating mode, in case at least one of the plurality of RLC entities associated with the PDCP entity is in a confirmable mode, determining that the target operating mode is a first operating mode or a third operating mode; in case the PDCP entity needs to provide data reception status feedback, determining that the target operating mode is the first operating mode or the third operating mode; or in case at least one of the plurality of RLC entities associated with the PDCP entity receives data in a multicast mode and at least one of the plurality of RLC entities receives data in a unicast mode, determining that the target operating mode is the first operating mode or the third working mode. 21. The method of claim 20, wherein determining the target operating mode of the PDCP entity includes: receiving (S701) indication information, wherein the indication information carries target operating mode identification information; And determining (S702) a target operating mode based on the indication information. 22. A communication device comprising: at least one processor and a memory coupled in communication with at least one processor and storing instructions executable by the at least one processor, in this case, when instructions are executed by at least one processor, at least one processor is provided with the execution of the method according to any one of claims. 1-21.