Data processing method and apparatus, and device and storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are a data processing method and apparatus, and a device and a storage medium. The data processing method in the embodiments of the present application comprises: a terminal receiving at least two PDCP SDUs from a high layer, wherein there is a synchronization requirement between the at least two PDCP SDUs; the terminal respectively starting discard timers respectively corresponding to the at least two PDCP SDUs; and on the basis of whether the synchronization requirement is met, the terminal executing a synchronization operation on the basis of the discard timers.

Description

Data processing method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202410388907.3 filed on April 1, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data processing method, apparatus, device and storage medium. Background Art

[0004] When the acquisition end of multimodal data (i.e., data of multimodal services) collects multiple types of data, in order for the other end to be able to present the corresponding scene based on the provided multimodal data, the multimodal data needs to be transmitted synchronously to the other end. For example, when a real-time application is provided based on multimodal data, the multimodal data needs to be transmitted synchronously to the other end. For uplink applications based on multimodal data, first, the multimodal data must be transmitted synchronously on the air interface between the base station and the terminal. If synchronous transmission is not achieved on the air interface, the different modal data will lose synchronization, and this out-of-synchronization state will be transmitted to the other end after the data is transmitted, which reduces the service quality of the other end. Therefore, how to ensure the synchronous transmission of business data remains to be solved. Summary of the Invention

[0005] The embodiments of the present application provide a data processing method, apparatus, device, and storage medium, which can solve the problem of how to ensure synchronous transmission of business data.

[0006] In a first aspect, a data processing method is provided, the method comprising: a terminal receiving at least two Packet Data Convergence Protocol (PDCP) service data units (SDUs) from a higher layer; wherein there is a synchronization requirement between the at least two PDCP SDUs; the terminal respectively starts a discard timer corresponding to each of the at least two PDCP SDUs; and according to whether the synchronization requirement is met, the terminal performs a synchronization operation based on the discard timer.

[0007] In a second aspect, a data processing method is provided, which includes: a network side device receives at least two PDCP SDUs from a higher layer; wherein, there is a synchronization requirement between the at least two PDCP SDUs; the network side device respectively starts the discard timers corresponding to the at least two PDCP SDUs; and according to whether the synchronization requirement is met, the network side device performs a synchronization operation based on the discard timer.

[0008] According to a third aspect, a data processing device is provided, comprising: a receiving module, a starting module, and an execution module. The receiving module is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization requirements are met between the at least two PDCP SDUs. The starting module is configured to start a discard timer corresponding to each of the at least two PDCP SDUs. The execution module is configured to perform synchronization operations based on the discard timers according to whether the synchronization requirements are met.

[0009] In a fourth aspect, a data processing device is provided, comprising: a receiving module, a starting module, and an execution module. The receiving module is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization requirements are met between the at least two PDCP SDUs. The starting module is configured to start a discard timer corresponding to each of the at least two PDCP SDUs. The execution module is configured to perform synchronization operations based on the discard timers according to whether the synchronization requirements are met.

[0010] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0011] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization is required between the at least two PDCP SDUs; and the processor is configured to start a discard timer corresponding to each of the at least two PDCP SDUs; and perform synchronization based on the discard timer according to whether the synchronization requirement is met.

[0012] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0013] In an eighth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization is required between the at least two PDCP SDUs; and wherein the processor is configured to start a discard timer corresponding to each of the at least two PDCP SDUs; and perform synchronization based on the discard timer according to whether the synchronization requirement is met.

[0014] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0015] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0016] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0017] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data processing method described in the first aspect, or to implement the steps of the data processing method described in the second aspect.

[0018] In an embodiment of the present application, a terminal receives at least two PDCP SDUs from a higher layer, wherein synchronization requirements are met between the at least two PDCP SDUs, and respectively starts corresponding discard timers for the at least two PDCP SDUs, so as to perform synchronization operations based on the discard timers according to whether the synchronization requirements are met. In this solution, since synchronization requirements are met between the at least two PDCP SDUs, the terminal can perform corresponding synchronization operations based on the synchronization requirements between the at least two PDCP SDUs and the corresponding discard timers for the at least two PDCP SDUs, thereby ensuring synchronous transmission between the PDCP SDUs. This ensures that the transmission of service data on the air interface meets the synchronization requirements, thereby improving the transmission performance of the service data. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0020] FIG2 is a flow chart of a data processing method according to an embodiment of the present application;

[0021] FIG3 is a second flowchart of a data processing method provided in an embodiment of the present application;

[0022] FIG4 is a third flowchart of a data processing method provided in an embodiment of the present application;

[0023] FIG5 is a fourth flowchart of a data processing method provided in an embodiment of the present application;

[0024] FIG6 is a structural diagram of a data processing device according to an embodiment of the present application;

[0025] FIG7 is a second structural diagram of a data processing device provided in an embodiment of the present application;

[0026] FIG8 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

[0027] FIG9 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0028] FIG10 is a schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0030] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0031] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0032] The terms "at least one" and "at least one of" in this application refer to any one, any two, or a combination of more than two of the objects included. For example, at least one of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two" means two or more, and its meaning is similar to "at least one".

[0033] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0034] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0035] The following explains some concepts and / or terms involved in the data processing method, apparatus, device and storage medium provided in the embodiments of the present application.

[0036] 1. eXtended Reality (XR)

[0037] XR refers to all combined real and virtual environments and human-computer interactions generated by computer technology and wearable devices. It includes representative forms such as augmented reality (AR), mixed reality (MR), virtual reality (VR), and their intersections. The levels of virtual worlds range from partial sensory input to fully immersive virtual reality. A key aspect of XR is the expansion of human experience, especially those related to presence (represented by VR) and cognitive learning (represented by AR).

[0038] For VR services, the uplink is mainly based on the transmission of relatively dense small data packets. These small data packets can carry information such as gestures and controls, and serve as input and reference for downlink presentation data. The downlink is mainly based on the transmission of multimedia data such as video and audio. The timely reception and presentation of these multimedia data provide users with an immersive experience. Taking downlink video data as an example, video data can be modeled as video frames based on the frame rate (Frame Per Second, FPS), with a typical FPS value of 60 or 120. These video frames arrive periodically or quasi-periodically based on the period determined by the FPS (1 / FPS second), and the size of the video frame changes dynamically. Each video frame is generally required to be successfully transmitted within 10ms on the air interface, and the transmission success rate is required to be no less than 99% or even 99.9%. In addition, downlink video data generally requires a very high data rate, generally up to tens or even hundreds of Mbps (typical values ​​are 30 / 45Mbps).

[0039] For AR services, in addition to the above-mentioned dense transmission of small data packets, uplink may also transmit multimedia data such as video, audio, and scene images. Its service characteristics are similar to those of downlink. The data rate is usually relatively low, for example, at most tens of Mbps (typically 10 / 20 Mbps). The time limit for air interface transmission can also be relaxed. For example, each video frame is generally required to be successfully transmitted within 30ms. The downlink data transmission characteristics are basically the same as those of VR services.

[0040] 2. Protocol Data Unit (PDU) set

[0041] Currently, in the relevant discussions of 3GPP, XR business data is modeled as a PDU set. A PDU set includes a group of PDUs so that the quality of service (QoS) of the data is managed according to the PDU set when it is transmitted in the wireless network. According to the different video data transmission methods mentioned above, a PDU set can correspond to an image frame, for example, a complete P frame or B frame, or an XR business data slice; another image frame can contain several PDU sets. For example, when the image frame is transmitted according to the left and right eye lines of sight, the left eye image data of an image frame corresponds to a PDU set, and the right eye image data corresponds to another PDU set; in addition, when the image is transmitted in the direction of the visual axis and the direction of the non-visual axis, the image data in the direction of the visual axis corresponds to a PDU set, and the image data in the direction of the non-visual axis corresponds to another PDU set. The above is only an example to illustrate the modeling of the PDU set. There may be other forms of modeling of the PDU set, which does not constitute a limitation on the implementation of this patent.

[0042] 3. Transmission of XR Services in NR Networks

[0043] According to the current 3GPP protocol, when an uplink XR packet from a terminal arrives at the Packet Data Convergence Protocol (PDCP) layer buffer from the application layer, a PDCP discard timer is started according to the initial value preconfigured by the base station. During the PDCP discard timer, the base station can schedule the terminal to transmit the packet to the base station. If the corresponding PDCP discard timer expires and the data is still not successfully transmitted, the packet is discarded.

[0044] 4. Packet Delay Budget (PDB)

[0045] Different services have different QoS management requirements. In 3GPP networks, QoS parameters include service data rate requirements, service data transmission delay requirements, and service data transmission reliability requirements (such as packet loss rate). The network can set different QoS parameters based on the user experience objectives of different services.

[0046] For latency-sensitive services, end-to-end latency requirements are generally stringent. Based on these end-to-end latency requirements, the latency budget for each segment of the data transmission path is determined. When latency-sensitive service data is transmitted over the 3GPP air interface, the network determines the corresponding air interface latency budget and schedules resources to ensure data transmission within the given latency budget.

[0047] According to the current protocol, the PDB or PDU Set Delay Budget (PSDB) window of a data packet can be understood as the operating time window of the corresponding PDCP discard timer, that is, PDCP

[0048] The time window between the start of the discard timer and the expiration of the PDCP discard timer. If the corresponding data packet has not been successfully transmitted when the PDCP discard timer times out, the PDCP entity will discard the untransmitted PDCP Service Data Unit (SDU), PDCP PDU or corresponding Radio Link Control (RLC) PDU.

[0049] When transmitting XR image data, the network can configure data transmission based on PDU sets. In this case, the network can configure the air interface transmission delay budget of the PDU set, PDU set Delay Budget (PSDB). The data packets contained in a PDU set correspond to the transmission window determined by the PSDB. Based on the current conclusions, the network can configure the corresponding PDCP discard timer of the UE based on the PSDB to determine the transmission window of the PDU set or the data packets belonging to the PDU set.

[0050] 5. Latency status reporting and uplink latency emergency data

[0051] Delay Status Report (DSR): In R18, the protocol supports reporting delay status by logical channel group (LCG). When the remaining delay budget of the data with the minimum remaining delay budget of an LCG is lower than the preconfigured threshold (remainingTimeThreshold), the delay status report of the LCG can be triggered. The data with the remaining delay budget of an LCG lower than the preset threshold is called delay-critical data. In the delay status report of an LCG, the terminal indicates the remaining delay budget of the data with the minimum remaining delay budget of an LCG and the amount of cached data with the remaining delay budget lower than the preset threshold. The network performs uplink resource scheduling based on the remaining time information of each LCG reported by the terminal.

[0052] In the PDCP protocol, a PDCP entity corresponding to a logical channel (LCH) determines the remaining delay budget of a data packet based on the remaining time of a discardTimer of the data packet.

[0053] In Release 19, an uplink scheduling method based on delay / remaining time information will be introduced. That is, the terminal will refer to the delay / remaining time information when allocating uplink resources to each LCH.

[0054] 6. Multimodal XR services

[0055] XR services include a wide range of services, including video conferencing, video gaming, video calling, and video-assisted remote work. A multimodal XR service is based on a combination of multiple data sources, including sound, touch, vision, kinesthetic sense, pain, pressure, airflow, and temperature. After the data acquisition endpoint of a multimodal XR service collects multiple data sources, it must synchronously transmit the data to the peer endpoint so that the peer endpoint can realistically present the scene corresponding to the data based on the provided multimodal data.

[0056] For uplink multimodal XR services, the terminal collects multimodal data. Based on base station scheduling, the terminal transmits the multimodal data to the base station, which then transmits the multimodal data to the other end. The other end constructs and plays the established scene based on the received multimodal data at a given time interval.

[0057] The data processing method, apparatus, device and storage medium provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0058] The present invention provides a data processing method, and Figure 2 shows a flow chart of the data processing method provided by the present invention. As shown in Figure 2, the data processing method provided by the present invention may include the following steps 201 to 203.

[0059] Step 201: The terminal receives at least two PDCP SDUs from a higher layer.

[0060] In the embodiment of the present application, there is a synchronization requirement between the at least two PDCP SDUs.

[0061] It should be noted that the synchronization requirement described in the embodiment of the present application refers to the synchronization requirement between the transmission time (for example, the timeout moment) of at least two PDCP SDUs. For example, meeting the synchronization requirement means that the difference between the timeout moments of at least two PDCP SDUs is less than a threshold (for example, P milliseconds).

[0062] Optionally, in an embodiment of the present application, the at least two PDCP SDUs may include multimodal data, such as multimodal XR service data.

[0063] Optionally, in an embodiment of the present application, the terminal receives the at least two PDCP SDUs at different times.

[0064] Optionally, in an embodiment of the present application, the terminal receives the at least two PDCP SDUs from a high layer or upper layer, and the upper layer may be a Service Data Adaptation Protocol (SDAP) layer, etc.

[0065] Exemplarily, the terminal receives a PDCP SDU from the SDAP layer, such as a PDCP SDU associated with at least two DRBs, or a PDCP SDU of at least two PDCPs, or a PDCP SDU associated with at least two QoS flows.

[0066] Optionally, the data processing method provided in the embodiment of the present application may further include the following steps 201a and 201b.

[0067] Step 201a: The network-side device sends first synchronization information to the terminal.

[0068] Step 201b: The terminal receives first synchronization information configured by the network side device.

[0069] In the embodiment of the present application, the first synchronization information is used to determine the synchronization requirement between at least two PDCP SDUs.

[0070] Optionally, in the embodiment of the present application, the data processing method provided in the embodiment of the present application may further include the following step 201c.

[0071] Step 201c: The terminal determines a synchronization requirement between the at least two PDCP SDUs according to the first information corresponding to the at least two PDCP SDUs.

[0072] In an embodiment of the present application, the above-mentioned first information includes at least one of the following: QoS flow, data radio bearer (DRB), LCG, and LCH.

[0073] In the embodiment of the present application, the first synchronization information is associated with at least two first information. It is understood that when the first synchronization information is associated with multiple first information, the terminal can determine the synchronization requirements between different service data (i.e., the first synchronization information) based on the synchronization requirements between different first information.

[0074] Optionally, in an embodiment of the present application, the above-mentioned different service data may include any one of the following: service data associated with different QoS flows, service data sent by different DRBs, service data sent by different PDCP entities, service data of different LCGs, and service data of different LCHs.

[0075] For example, the first synchronization information associates two DRBs, namely DRB1 and DRB2. The terminal can determine the synchronization requirements between different service data based on the synchronization requirements between DRB1 and DRB2. The different service data can be service data sent by different DRBs, or service data sent by different PDCP entities.

[0076] Optionally, in an embodiment of the present application, the first synchronization information is a first synchronization requirement, and the first synchronization requirement is a synchronization requirement between business data.

[0077] Optionally, in an embodiment of the present application, the first synchronization information is a value of a synchronization timer, the value of the synchronization timer is a synchronization requirement between service data, and the synchronization timer is used to determine the remaining transmission time of the PDCP SDU.

[0078] It should be noted that the synchronization timer can ensure the synchronous transmission of PDCP SDUs. The terminal can determine the remaining transmission time of the PDCP SDU based on the synchronization timer, thereby ensuring the synchronous transmission of the PDCP SDUs. That is, the synchronization timer ensures that the timeout moments of PDCP SDUs of different services meet the synchronization requirements.

[0079] Step 202: The terminal starts the discard timers corresponding to at least two PDCP SDUs respectively.

[0080] In the embodiment of the present application, the discard timer (discardTimer) is used to trigger the discard of the PDCP SDU, that is, after the discard timer times out, the corresponding PDCP SDU is discarded.

[0081] It is understood that each time a terminal receives a PDCP SDU from a higher layer, it starts a discard timer corresponding to the PDCP SDU. For example, when the terminal receives PDCP SDU1 from a higher layer at time 1, it starts a discard timer A corresponding to PDCP SDU1. When the terminal receives PDCP SDU2 from a higher layer at time 2, it starts a discard timer B corresponding to PDCP SDU2.

[0082] Step 203: Depending on whether the synchronization requirement is met, the terminal performs a synchronization operation based on the discard timer.

[0083] In the embodiment of the present application, when the terminal receives at least two PDCP SDUs, it can perform a synchronization operation according to whether the synchronization requirement is met and according to the timeout time of the at least two PDCP SDUs.

[0084] In the embodiment of the present application, the timeout moment of each PDCP SDU refers to the timeout moment of a discard timer corresponding to or associated with each PDCP SDU.

[0085] Optionally, in an embodiment of the present application, the timeout moment of each PDCP SDU is the sum of the first moment corresponding to each PDCP SDU and the value of the discard timer associated with each PDCP SDU (i.e., the duration of the discard timer). The first moment corresponding to each PDCP SDU is the reception moment of each PDCP SDU, or the start moment of the discard timer associated with each PDCP SDU.

[0086] It should be noted that the value of the timer described in the embodiments of the present application refers to the maximum value of the timer. The timeout time of the timer refers to the sum of the timer start time and the timer value.

[0087] It can be understood that when the terminal receives a PDCP SDU at time 1, the terminal starts the discard timer associated with the PDCP SDU, and the timeout moment of the PDCP SDU is the sum of the value of the discard timer associated with the PDCP SDU and time 1; when the terminal receives another PDCP SDU at time 2, the terminal starts the discard timer associated with the other PDCP SDU, and the timeout moment of the other PDCP SDU is the sum of the value of the discard timer associated with the other PDCP SDU and time 2; and so on, the timeout moments of the above-mentioned at least two PDCP SDUs are obtained.

[0088] For example, assume that a terminal receives PDCP SDU X associated with DRB1 at time 1. The terminal controls the PDCP entity corresponding to DRB1 to start discard timer A associated with PDCP SDU X at time 1 (e.g., 0 ms), with a value of 40 ms. The terminal receives PDCP SDU Y associated with DRB2 at time 2 (e.g., 5 ms), and the terminal controls the PDCP entity corresponding to DRB2 to start discard timer B associated with PDCP SDU Y at time 2, with a value of 60 ms. Therefore, the timeout time of PDCP SDU X is the sum of time 1 (0 ms) and the value of discard timer A (40 ms), i.e., 40 ms. That is, discard timer A associated with PDCP SDU X times out at 40 ms. The timeout time of PDCP SDU Y is the sum of time 2 (5 ms) and the value of discard timer B (60 ms), i.e., 65 ms. That is, discard timer B associated with PDCP SDU Y times out at 65 ms.

[0089] It should be noted that the examples of the embodiments of the present application are illustrated by taking the case where synchronization requirements exist for PDCP SDUs transmitted by two DRBs (for example, PDCP SDU X associated with DRB1 and PDCP SDU Y associated with DRB2). This solution is applicable to the case where synchronization requirements exist for PDCP SDUs transmitted by multiple DRBs, PDCP SDUs transmitted by multiple PDCP entities, PDCP SDUs of multiple LCHs, or PDCP SDUs associated with multiple QoS flows.

[0090] Optionally, in the embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 3 , the above step 203 may be specifically implemented through the following step 203a.

[0091] Step 203a: If the difference between the remaining time of the discard timers corresponding to the at least two PDCP SDUs until their respective timeouts does not meet the synchronization requirement, the terminal adjusts the duration of the discard timer corresponding to at least one of the at least two PDCP SDUs.

[0092] It should be noted that the difference between the remaining time from the discard timers corresponding to at least two PDCP SDUs to their respective timeouts does not meet the synchronization requirement means that the difference between the remaining time from the discard timers corresponding to at least two PDCP SDUs to their respective timeouts is greater than the synchronization requirement.

[0093] In an embodiment of the present application, the remaining time from the discard timers corresponding to the at least two PDCP SDUs to their respective timeouts refers to: the remaining time from the current moment of the discard timers corresponding to the at least two PDCP SDUs to their respective timeout moments, that is, each remaining time is the difference between the timeout moment of the discard timer corresponding to each PDCP SDU and the current moment.

[0094] Exemplarily, if the difference between the timeout moment of discard timer A corresponding to the first PDCP SDU in at least two PDCP SDUs and the current moment is value a, that is, the remaining time from discard timer A to the timeout of discard timer A is value a; the difference between the timeout moment of discard timer B corresponding to the second PDCP SDU in at least two PDCP SDUs and the current moment is value b, that is, the remaining time from discard timer B to the timeout of discard timer B is value b; then if the difference between value a and value b does not meet the synchronization requirements, the terminal adjusts the duration of the discard timer corresponding to the first PDCP SDU or the second PDCP SDU (that is, the value of the discard timer).

[0095] It can be understood that when the difference between the remaining time of the discard timers corresponding to at least two PDCP SDUs and their respective timeouts does not meet the synchronization requirements, the scheduling of at least one PDCP SDU can be accelerated or slowed down by adjusting the value of the discard timer associated with at least one PDCP SDU, thereby ensuring that the synchronization requirements are met between the PDCP SDUs.

[0096] For example, assuming the synchronization requirement is 20 ms, if the timeout time of the discard timer corresponding to PDCP SDU X is 40 ms and the timeout time of the discard timer corresponding to PDCP SDU Y is 65 ms, then the difference between the timeout time of 40 ms of the discard timer corresponding to PDCP SDU X and the current time (e.g., the start time of 5 ms of discard timer B corresponding to PDCP SDU Y) is 35 ms, i.e., the remaining time from discard timer A to the timeout of discard timer A is 35 ms. The difference between the timeout time of 65 ms of the discard timer B corresponding to PDCP SDU Y and the current time (e.g., the start time of 5 ms of discard timer B corresponding to PDCP SDU Y) is 60 ms, i.e., the remaining time from discard timer B to the timeout of discard timer B is 60 ms. Then, the difference between the remaining time until the discard timers corresponding to the two PDCP SDUs expire is the remaining time of 60 ms minus the remaining time of 35 ms, which is equal to 25 ms. That is, the difference between the remaining time until the discard timers corresponding to the two PDCP SDUs (i.e., PDCP SDU X and PDCP SDU Y) expires, which is 25 ms, is greater than the synchronization requirement of 20 ms. In this case, the terminal adjusts the duration of the discard timer corresponding to PDCP SDU X or PDCP SDU Y (i.e., the value of the discard timer).

[0097] Optionally, in the embodiment of the present application, "the terminal adjusts the duration of the discard timer of at least one of the at least two PDCP SDUs" in the above step 203a can be specifically implemented through the following step 203a1 or step 203a2.

[0098] Step 203a1: The terminal extends the duration of the discard timer corresponding to the first PDCP SDU in the at least two PDCP SDUs to a first duration.

[0099] In an embodiment of the present application, the above-mentioned first duration is determined based on the timeout moment of the discard timer corresponding to the second PDCP SDU in at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU includes M PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the second PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0100] Step 203a2: The terminal shortens the duration of the discard timer corresponding to the fourth PDCP SDU in the at least two PDCP SDUs to the second duration.

[0101] In an embodiment of the present application, the above-mentioned second duration is determined based on the timeout moment of the discard timer corresponding to the third PDCP SDU among the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes the N PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the fourth PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0102] Optionally, in an embodiment of the present application, the value range of the above-mentioned first duration is [the timeout moment of the discard timer corresponding to the second PDCP SDU - the synchronization requirement - the start moment of the discard timer corresponding to the first PDCP SDU, the remaining time of the discard timer corresponding to the second PDCP SDU until the timeout + the synchronization requirement - the start moment of the discard timer corresponding to the first PDCP SDU].

[0103] Optionally, in an embodiment of the present application, the value range of the above-mentioned second duration is [the timeout moment of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, the timeout moment of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

[0104] For example, if the difference between the remaining time between the discard timers corresponding to PDCP SDU X and PDCP SDU Y and their respective timeouts (e.g., 25 ms) is greater than the synchronization requirement (e.g., 20 ms), the terminal adjusts the duration of the discard timer corresponding to PDCP SDU X or PDCP SDU Y (i.e., the value of the discard timer), including:

[0105] In one solution, the terminal may extend the duration of the discard timer A corresponding to PDCP SDU X to a first duration. The first duration is a value within a value range A. The lower limit of the value range A is 45 ms, which is the timeout time of the discard timer B corresponding to PDCP SDU Y (65 ms) minus the synchronization requirement of 20 ms, minus the start time of the discard timer A corresponding to PDCP SDU X (0 ms). The upper limit of the value range A is 85 ms, which is the sum of the timeout time of the discard timer B corresponding to PDCP SDU Y (65 ms) and the synchronization requirement of 20 ms, minus the start time of the discard timer A corresponding to PDCP SDU X (0 ms). Therefore, the value range of the first duration is [45, 85]. Therefore, the first duration can be any value between 45 ms and 85 ms.

[0106] In this way, by slowing down the scheduling of PDCP SDU X, the synchronization requirement between PDCP SDU X and PDCP SDU Y is met. That is, at this time, the remaining time from the time when discard timer A corresponding to PDCP SDU X expires is 45 - 5 ms at the current time = 40 ms, and the remaining time from the time when discard timer B corresponding to PDCP SDU Y expires is 65 - 5 ms at the current time = 60 ms. Therefore, the difference between the remaining time until each PDCP SDU X and PDCP SDU Y expires is 60 ms minus 40 ms, which equals 20 ms. This satisfies the synchronization requirement of 20 ms between PDCP SDU X and PDCP SDU Y. Alternatively, at this time, the remaining time from the discard timer A corresponding to the PDCP SDU X to the timeout of the discard timer A is 85 - 5 ms at the current time = 80 ms, and the remaining time from the discard timer B corresponding to the PDCP SDU Y to the timeout of the discard timer B is 65 ms - 5 ms at the current time = 60 ms. Therefore, the difference between the remaining time of PDCP SDU X and PDCP SDU Y until their respective timeouts is 80 ms minus 60 ms, which is equal to 20 ms. This satisfies the synchronization requirement of 20 ms between PDCP SDU X and PDCP SDU Y.

[0107] Another solution: The terminal may shorten the duration of the discard timer A corresponding to PDCP SDU Y to a second duration. This second duration is within a value range B. The lower limit of this value range B is the timeout time of the discard timer A corresponding to PDCP SDU X (40 ms) minus the synchronization requirement of 20 ms, minus the start time of the discard timer B corresponding to PDCP SDU Y (5 ms). That is, the lower limit of this value range B is 15 ms. The upper limit of this value range B is the sum of the timeout time of the discard timer A corresponding to PDCP SDU X (40 ms) and the synchronization requirement of 20 ms, minus the start time of the discard timer B corresponding to PDCP SDU Y (5 ms). That is, the upper limit of this value range B is 55 ms. The value range of the second duration is [15, 55]. Therefore, the second duration can be any value between 15 ms and 55 ms.

[0108] In this way, by accelerating the scheduling of PDCP SDU Y, the synchronization requirement between PDCP SDU X and PDCP SDU Y is met. Specifically, the remaining time from the time when discard timer A corresponding to PDCP SDU X expires is 40 ms minus the current time (5 ms) = 35 ms. The remaining time from the time when discard timer B corresponding to PDCP SDU Y expires is the time when discard timer B corresponding to PDCP SDU Y expires (i.e., the value of discard timer B (15 ms) + the start time of discard timer B (5 ms) = 20 ms) minus the current time (5 ms) = 15 ms. Therefore, the difference between the remaining time until each of PDCP SDU X and PDCP SDU Y expires is 35 ms minus 15 ms, which equals 20 ms. This satisfies the synchronization requirement of 20 ms between PDCP SDU X and PDCP SDU Y. Alternatively, in this case, the remaining time from the discard timer A corresponding to the PDCP SDU X to the timeout of the discard timer A is 40 ms minus the current time of 5 ms = 35 ms, and the remaining time from the discard timer B corresponding to the PDCP SDU Y to the timeout of the discard timer B is the timeout time of the discard timer B corresponding to the PDCP SDU Y (i.e., the value of the discard timer B is 55 ms + the start time of the discard timer B is 5 ms = 60 ms) minus the current time of 5 ms = 55 ms. Therefore, the difference between the remaining time of the PDCP SDU X and the PDCP SDU Y to their respective timeouts is 55 ms minus 35 ms, which is equal to 20 ms, satisfying the synchronization requirement of 20 ms between the PDCP SDU X and the PDCP SDU Y.

[0109] Optionally, in an embodiment of the present application, if the timeout moment of the first PDCP SDU is less than the timeout moment of the second PDCP SDU, the terminal adjusts the value of the discard timer associated with the second PDCP SDU to the first value, or the terminal adjusts the value of the discard timer associated with the first PDCP SDU to the second value.

[0110] Optionally, in an embodiment of the present application, if the timeout moment of the second PDCP SDU is less than the timeout moment of the first PDCP SDU, the terminal adjusts the value of the discard timer associated with the first PDCP SDU to the second value, or the terminal adjusts the value of the discard timer associated with the second PDCP SDU to the first value.

[0111] In the embodiment of the present application, the first value is within a first value range, and the second value is within a second value range.

[0112] The lower limit of the first value range is the timeout moment of the first PDCP SDU minus the first synchronization information, minus the start time of the discard timer associated with the second PDCP SDU. The upper limit of the first value range is the sum of the timeout moment of the first PDCP SDU and the first synchronization information, minus the start time of the discard timer associated with the second PDCP SDU.

[0113] The lower limit of the second value range is the timeout moment of the second PDCP SDU minus the first synchronization information, minus the start time of the discard timer associated with the first PDCP SDU. The upper limit of the second value range is the sum of the timeout moment of the second PDCP SDU and the first synchronization information, minus the start time of the discard timer associated with the first PDCP SDU.

[0114] It can be understood that the terminal adjusts the value of the discard timer associated with the second PDCP SDU to the first value or it can be: the terminal adjusts the timeout moment of the second PDCP SDU to a third value, the third value is a value within the third value range, the lower limit of the third value range is the difference between the timeout moment of the first PDCP SDU and the first synchronization information, and the upper limit of the third value range is the sum of the timeout moment of the first PDCP SDU and the first synchronization information.

[0115] The terminal adjusts the value of the discard timer associated with the first PDCP SDU to the second value, or it may be: the terminal adjusts the timeout moment of the first PDCP SDU to a fourth value, the fourth value is a value within the fourth value range, the lower limit of the fourth value range is the difference between the timeout moment of the second PDCP SDU and the first synchronization information, and the upper limit of the fourth value range is the sum of the timeout moment of the second PDCP SDU and the first synchronization information.

[0116] For example, if the timeout of PDCP SDU X is 40 ms, the timeout of PDCP SDU Y is 65 ms, and the difference between the timeout of PDCP SDU X and the timeout of PDCP SDU Y is 25 ms, which is greater than the first synchronization requirement of 20 ms, then:

[0117] One solution: The terminal may adjust the timeout time of the PDCP SDU Y to a third value, where the third value is within a third value range. The lower limit of the third value range is the difference between the timeout time of the PDCP SDU X (40 ms) and the timeout time of the first synchronization information (20 ms) (i.e., 20 ms), and the upper limit of the third value range is the sum of the timeout time of the PDCP SDU X (40 ms) and the timeout time of the first synchronization information (20 ms) (i.e., 60 ms). Therefore, the third value may be any value between 20 ms and 60 ms.

[0118] This solution can also be understood as adjusting the value of the discard timer B associated with PDCP SDU Y to a first value within a first value range. The lower limit of the first value range is the timeout time of PDCP SDU X (40 ms) minus the first synchronization information (20 ms), minus the start time of the discard timer B associated with PDCP SDU Y (5 ms), i.e., the lower limit of the first value range is 15 ms. The upper limit of the first value range is the sum of the timeout time of PDCP SDU X (40 ms) and the first synchronization information (20 ms), minus the start time of the discard timer B associated with PDCP SDU Y (5 ms), i.e., the upper limit of the first value range is 55 ms. Therefore, the first value can be any value between 15 ms and 55 ms.

[0119] In this way, by accelerating the scheduling of PDCP SDU Y, the synchronization requirement between PDCP SDU X and PDCP SDU Y is met. That is, at this time, the difference between the timeout time of 20 ms of PDCP SDU Y and the timeout time of 40 ms of PDCP SDU X is 20 ms, or the difference between the timeout time of 60 ms of PDCP SDU Y and the timeout time of 40 ms of PDCP SDU X is 20 ms, thereby meeting the synchronization requirement of 20 ms between PDCP SDU X and PDCP SDU Y.

[0120] Another solution: The terminal may adjust the timeout time of the PDCP SDU X to a fourth value, where the fourth value is within a fourth value range. The lower limit of the fourth value range is the difference between the timeout time of PDCP SDU Y (65 ms) and the first synchronization information (20 ms) (i.e., 45 ms), and the upper limit of the fourth value range is the sum of the timeout time of PDCP SDU Y (65 ms) and the first synchronization information (20 ms) (i.e., 85 ms). Therefore, the fourth value may be any value between 45 ms and 85 ms.

[0121] This solution can also be understood as adjusting the value of the discard timer A associated with PDCP SDU X to a second value within a second value range. The lower limit of the second value range is 65 ms, the timeout time of PDCP SDU Y minus 20 ms of the first synchronization information, minus 0 ms, the start time of the discard timer A associated with PDCP SDU X. That is, the lower limit of the second value range is 45 ms. The upper limit of the second value range is 85 ms, the sum of 65 ms, the timeout time of PDCP SDU Y, and 20 ms of the first synchronization information, minus 0 ms, the start time of the discard timer A associated with PDCP SDU X. Therefore, the second value can be any value between 45 ms and 85 ms.

[0122] In this way, by slowing down the scheduling of PDCP SDU X, the synchronization requirement between PDCP SDU X and PDCP SDU Y is met. That is, at this time, the difference between the timeout instant 45 ms of PDCP SDU X and the timeout instant 65 ms of PDCP SDU Y is 20 ms, or the difference between the timeout instant 85 ms of PDCP SDU X and the timeout instant 65 ms of PDCP SDU Y is 20 ms, thus meeting the synchronization requirement of 20 ms between PDCP SDU X and PDCP SDU Y.

[0123] In the embodiment of the present application, the terminal may determine the remaining transmission time of the PDCP SDU corresponding to the discard timer according to the adjusted value of the discard timer.

[0124] In the embodiment of the present application, the terminal can calculate the timeout moment of the third timer based on the value of the adjusted third timer, and the timeout moment is the sum of the start moment of the third timer and the value of the adjusted third timer; then the terminal can calculate the difference between the timeout moment of the third timer and the current moment (for example, the reception moment of the PDCP SDU corresponding to the third timer), and determine the difference as the remaining transmission time of the PDCP SDU corresponding to the third timer, so that the PDCP SDU corresponding to the third timer is transmitted within the remaining transmission time, and is lost after exceeding the remaining transmission time, so as to ensure that the synchronization requirement between the first PDCP SDU and the second PDCP SDU is met. It can be understood that after the third timer times out, the terminal discards the PDCP SDU corresponding to the third timer.

[0125] For example, assuming that the third timer is discard timer B associated with PDCP SDU Y. If the terminal adjusts the value of discard timer B associated with PDCP SDU Y to a first value of 55 ms, and the reception time of the PDCP SDU corresponding to discard timer B (i.e., the start time of discard timer B) is 5 ms, then the timeout time of discard timer B associated with PDCP SDU Y is 60 ms. The remaining transmission time of the PDCP SDU corresponding to discard timer B (i.e., PDCP SDU Y) is 60 ms, and the remaining transmission time of the PDCP SDU corresponding to discard timer B (i.e., PDCP SDU Y) is 55 ms, which is the timeout time of discard timer B (60 ms) minus the current time (e.g., the reception time of PDCP SDU Y (5 ms)). Therefore, the remaining transmission time is 55 ms. After 55 ms of transmission of PDCP SDU Y, the terminal discards PDCP SDU Y. At this point, PDCP SDU X is completely transmitted; or PDCP SDU X is not completely transmitted, but the discard timer A associated with PDCP SDU X times out at 40 ms, causing PDCP SDU X to be discarded.

[0126] For another example, assume that the third timer is discard timer A associated with PDCP SDU X. If the terminal adjusts the value of discard timer A associated with PDCP SDU X to the second value of 45 ms, and the reception time of the PDCP SDU corresponding to discard timer A (i.e., the start time of discard timer A) is 0 ms, then the timeout time of discard timer A associated with PDCP SDU X is 45 ms, and the remaining transmission time of the PDCP SDU corresponding to discard timer A (i.e., PDCP SDU X) is the timeout time of discard timer A (45 ms) minus the current time (e.g., the reception time of PDCP SDU Y (5 ms), resulting in a remaining transmission time of 40 ms. Therefore, after PDCP SDU X is transmitted for 40 ms, the terminal discards PDCP SDU X, at which point the transmission of PDCP SDU Y is completed; or PDCP SDU Y continues to be transmitted without completing transmission until discard timer B associated with PDCP SDU Y times out at 65 ms, at which point PDCP SDU Y is discarded.

[0127] In an embodiment of the present application, the terminal adjusts the value of the associated discard timer (discard timer) of the PDCP SDU according to the synchronization requirements, that is, adjusts the packet loss time to affect the uplink resource scheduling, so that the transmission of service data on the air interface meets the synchronization requirements, thereby ensuring the synchronous transmission of service data.

[0128] Optionally, in the embodiment of the present application, the above step 203 can be specifically implemented through the following step 203b.

[0129] Step 203b: If there is a PDCP SDU that has been completely transmitted among the at least two PDCP SDUs, and a discard timer corresponding to at least one PDCP SDU is still running, the terminal starts a synchronization timer.

[0130] The duration of the synchronization timer is less than or equal to the duration required to meet the synchronization requirement.

[0131] Optionally, in the embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 4 , the above step 203 may be specifically implemented through the following step 203 c.

[0132] Step 203c: If there is a PDCP SDU whose transmission is completed among the at least two PDCP SDUs, and the discard timer corresponding to at least one PDCP SDU is still running, the terminal determines whether to start the synchronization timer.

[0133] In an embodiment of the present application, the duration of the above-mentioned synchronization timer is less than or equal to the duration that meets the synchronization requirements.

[0134] Optionally, in the embodiment of the present application, the "terminal determines whether to start the synchronization timer" in the above step 203c can be specifically implemented through the following step 203c1 or step 203c2.

[0135] Step 203c1: If the remaining time of each of the running discard timers before their respective expiration times does not meet the synchronization requirement, the terminal determines to start the synchronization timer.

[0136] It should be noted that the remaining time until each of the running discard timers expires does not meet the synchronization requirement means that the remaining time until each of the running discard timers expires is greater than the synchronization requirement.

[0137] Step 203c2: If the remaining time of each of the running discard timers before their respective timeouts meets the synchronization requirement, the terminal determines not to start the synchronization timer.

[0138] Exemplarily, when the terminal receives at least two PDCP SDUs, if the fifth PDCP SDU in the at least two PDCP SDUs is transmitted, and the discard timer associated with the sixth PDCP SDU has not timed out and the sixth PDCP SDU has not been transmitted, the synchronization timer associated with the sixth PDCP SDU is started.

[0139] In the embodiment of the present application, each PDCP SDU data is associated with a synchronization timer.

[0140] It should be noted that the transmission completion described in the embodiment of the present application means that the upper layer (such as the PDCP layer) receives the indication information provided by the lower layer, and the indication information is used to indicate that the PDCP SDU is successfully sent or received.

[0141] For example, assuming that the fifth PDCP SDU is PDCP SDU X and the sixth PDCP SDU is PDCP SDU Y, the reception time of PDCP SDU X is 0 ms, the value of the discard timer A associated with PDCP SDU X is 40 ms, the reception time of PDCP SDU Y is 5 ms, and the value of the discard timer B associated with PDCP SDU Y is 60 ms. If PDCP SDU X is completely transmitted at 40 ms, the discard timer B associated with PDCP SDU Y (the timeout time of discard timer B is 65 ms) has not timed out, and PDCP SDU Y has not been completely transmitted, the terminal may start the synchronization timer associated with PDCP SDU Y, that is, start the synchronization timer associated with PDCP SDU Y at 40 ms.

[0142] In the embodiment of the present application, the terminal may determine the remaining transmission time of the sixth PDCP SDU according to the remaining time of the synchronization timer associated with the sixth PDCP SDU and the remaining time of the associated discard timer.

[0143] In an embodiment of the present application, the remaining time of the above-mentioned synchronization timer is obtained according to the value of the synchronization timer, and the remaining time of the discard timer is obtained according to the value of the discard timer.

[0144] In the embodiment of the present application, the terminal may determine the smallest remaining time between the remaining time of the synchronization timer associated with the sixth PDCP SDU and the remaining time of the associated discard timer as the remaining transmission time of the sixth PDCP SDU.

[0145] In this embodiment of the present application, the remaining time of the synchronization timer associated with the sixth PDCP SDU is the difference between the timeout moment of the synchronization timer associated with the sixth PDCP SDU and the current moment (e.g., the start moment of the synchronization timer associated with the sixth PDCP SDU). The remaining time of the discard timer associated with the sixth PDCP SDU is the difference between the timeout moment of the discard timer associated with the sixth PDCP SDU and the current moment (e.g., the start moment of the synchronization timer associated with the sixth PDCP SDU).

[0146] For example, if the synchronization timer associated with the sixth PDCP SDU (PDCP SDU Y) is started at 40ms, the value of the synchronization timer associated with PDCP SDU Y is 20ms, and the timeout time of the discard timer B associated with PDCP SDU Y is 65ms, then the timeout time of the synchronization timer associated with PDCP SDU Y is the sum of the start time 40ms of the synchronization timer associated with PDCP SDU Y and the value 20ms of the synchronization timer associated with PDCP SDU Y (i.e., 60ms), the remaining time of the synchronization timer associated with PDCP SDU Y is the difference between the timeout time 60ms of the synchronization timer associated with PDCP SDU Y and the current time (e.g., the start time 40ms of the synchronization timer associated with PDCP SDU Y) (i.e., 20ms), and the remaining time of the discard timer B associated with PDCP SDU Y is the difference between the timeout time 65ms of the discard timer B associated with PDCP SDU Y and the current time (e.g., the start time 40ms of the synchronization timer associated with PDCP SDU Y) (i.e., 25ms). In this way, If the remaining time of the synchronization timer associated with Y, 20 ms, is less than the remaining time of the discard timer B associated with PDCP SDU Y, 25 ms, then 20 ms is the remaining transmission time of PDCP SDU Y.

[0147] Optionally, in an embodiment of the present application, if the difference between the timeout moment of the discard timer associated with the sixth PDCP SDU and the transmission completion moment of the fifth PDCP SDU is greater than the first synchronization information, the terminal starts the synchronization timer associated with the sixth PDCP SDU.

[0148] It can be understood that when the difference between the timeout moment of the discard timer associated with the sixth PDCP SDU and the transmission completion moment of the fifth PDCP SDU is greater than the first synchronization information, it is considered that the synchronization requirements are not met between the sixth PDCP SDU and the fifth PDCP SDU. Then, the remaining transmission time of the sixth PDCP SDU can be calculated by starting the synchronization timer associated with the sixth PDCP SDU, so that the sixth PDCP SDU is transmitted within the remaining transmission time, and the packet is lost after exceeding the remaining transmission time, thereby ensuring that the synchronization requirements are met between the sixth PDCP SDU and the fifth PDCP SDU.

[0149] Optionally, in an embodiment of the present application, after the above step 203c, the data processing method provided in the embodiment of the present application further includes the following step 204.

[0150] Step 204: After the synchronization timer times out, the terminal discards the PDCP SDU corresponding to the synchronization timer.

[0151] Exemplarily, after the terminal starts the synchronization timer associated with the sixth PDCP SDU, if the synchronization timer associated with the sixth PDCP SDU times out, the terminal discards the PDCP SDU corresponding to the sixth synchronization timer.

[0152] Optionally, the data processing method provided in the embodiment of the present application further includes the following step 205.

[0153] Step 205: After the discard timer times out, the terminal discards the PDCP SDU corresponding to the discard timer.

[0154] Optionally, in an embodiment of the present application, after the network side device activates synchronous transmission related operations based on synchronization requirements through RRC configuration, the terminal can execute the steps of the data processing method of the embodiment of the present application and its related schemes.

[0155] Optionally, in an embodiment of the present application, after the network side device activates synchronous transmission related operations based on synchronization requirements through the Medium Access Control Control Element (MAC CE), the terminal can execute the steps of the data processing method of the embodiment of the present application and its related schemes.

[0156] An embodiment of the present application provides a data processing method, in which a terminal receives at least two PDCP SDUs from a higher layer, wherein the at least two PDCP SDUs have a synchronization requirement, and respectively starts a corresponding discard timer for each of the at least two PDCP SDUs, so as to perform a synchronization operation based on the discard timer according to whether the synchronization requirement is met. In this solution, the at least two PDCP SDUs have a synchronization requirement, and the terminal can perform a corresponding synchronization operation based on the synchronization requirement between the at least two PDCP SDUs and the corresponding discard timer for each of the at least two PDCP SDUs, thereby ensuring synchronous transmission between the PDCP SDUs, thereby ensuring that the transmission of service data on the air interface meets the synchronization requirement, thereby improving the transmission performance of the service data.

[0157] The present invention provides a data processing method, and Figure 5 shows a flow chart of the data processing method provided by the present invention. As shown in Figure 5, the data processing method provided by the present invention may include the following steps 301 to 303.

[0158] Step 301: A network-side device receives at least two PDCP SDUs from a higher layer.

[0159] In the embodiment of the present application, there is a synchronization requirement between the at least two PDCP SDUs.

[0160] Optionally, the data processing method provided in the embodiment of the present application may further include the following steps 301a and 301b.

[0161] Step 301a: The network-side device sends first synchronization information to the terminal.

[0162] Step 301b: The terminal receives first synchronization information configured by the network side device.

[0163] In the embodiment of the present application, the first synchronization information is used to determine the synchronization requirement between at least two PDCP SDUs.

[0164] Optionally, in the embodiment of the present application, the data processing method provided in the embodiment of the present application may further include the following step 301c.

[0165] Step 301c: The network-side device determines a synchronization requirement between the at least two PDCP SDUs according to the first information corresponding to the at least two PDCP SDUs.

[0166] In an embodiment of the present application, the above-mentioned first information includes at least one of the following: QoS flow, data radio bearer (DRB), LCG, and LCH.

[0167] Step 302: The network-side device starts the discard timers corresponding to at least two PDCP SDUs respectively.

[0168] Step 303: Depending on whether the synchronization requirement is met, the network side device performs a synchronization operation based on the discard timer.

[0169] Optionally, in the embodiment of the present application, the above step 303 can be specifically implemented through the following step 303a.

[0170] Step 303a: If the difference between the remaining time of the discard timers corresponding to the at least two PDCP SDUs until their respective timeouts does not meet the synchronization requirement, the network side device adjusts the length of the discard timer corresponding to at least one of the at least two PDCP SDUs.

[0171] Optionally, in the embodiment of the present application, the “network-side device adjusts the duration of the discard timer of at least one of the at least two PDCP SDUs” in the above step 303a can be specifically implemented through the following step 303a1 or step 303a2.

[0172] Step 303a1: The network-side device extends the duration of the discard timer corresponding to the first PDCP SDU in the at least two PDCP SDUs to a first duration.

[0173] In an embodiment of the present application, the above-mentioned first duration is determined based on the timeout moment of the discard timer corresponding to the second PDCP SDU in at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU includes M PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the second PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0174] Step 303a2: The network-side device shortens the duration of the discard timer corresponding to the fourth PDCP SDU in the at least two PDCP SDUs to the second duration.

[0175] In an embodiment of the present application, the above-mentioned second duration is determined based on the timeout moment of the discard timer corresponding to the third PDCP SDU among the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes the N PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the fourth PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0176] Optionally, in an embodiment of the present application, the value range of the above-mentioned first duration is [the timeout moment of the discard timer corresponding to the second PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the first PDCP SDU, the timeout moment of the discard timer corresponding to the second PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the first PDCP SDU].

[0177] Optionally, in an embodiment of the present application, the value range of the above-mentioned second duration is [the timeout moment of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, the timeout moment of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

[0178] Optionally, in the embodiment of the present application, the above step 303 can be specifically implemented through the following step 303b.

[0179] Step 303b: If there is a PDCP SDU that has been completely transmitted among the at least two PDCP SDUs, and the discard timer corresponding to at least one PDCP SDU is still running, the network side device starts a synchronization timer.

[0180] The duration of the synchronization timer is less than or equal to the duration required to meet the synchronization requirement.

[0181] Optionally, in the embodiment of the present application, the above step 303 can be specifically implemented through the following step 303c.

[0182] Step 303c: If there is a PDCP SDU that has been completely transmitted among the at least two PDCP SDUs, and the discard timer corresponding to at least one PDCP SDU is still running, the network-side device determines whether to start the synchronization timer.

[0183] In an embodiment of the present application, the duration of the above-mentioned synchronization timer is less than or equal to the duration that meets the synchronization requirements.

[0184] Optionally, in the embodiment of the present application, the “network-side device determines whether to start the synchronization timer” in the above step 303c can be specifically implemented through the following step 303c1 or step 303c2.

[0185] Step 303c1: If the remaining time of the running discard timers before their respective timeouts does not meet the synchronization requirement, the network side device determines to start the synchronization timer.

[0186] Step 303c2: If the remaining time of the running discard timers before their respective timeouts meets the synchronization requirement, the network side device determines not to start the synchronization timer.

[0187] Optionally, in an embodiment of the present application, after the above step 303c, the data processing method provided in the embodiment of the present application further includes the following step 304.

[0188] Step 304: After the synchronization timer times out, the network side device discards the PDCP SDU corresponding to the synchronization timer.

[0189] Optionally, the data processing method provided in the embodiment of the present application further includes the following step 305.

[0190] Step 305: After the discard timer times out, the network side device discards the PDCP SDU corresponding to the discard timer.

[0191] An embodiment of the present application provides a data processing method, in which a network-side device receives at least two PDCP SDUs from a higher layer, wherein the at least two PDCP SDUs have a synchronization requirement, and respectively starts a discard timer corresponding to each of the at least two PDCP SDUs, so as to perform a synchronization operation based on the discard timer according to whether the synchronization requirement is met. In this solution, there is a synchronization requirement between the at least two PDCP SDUs, and the network-side device can perform a corresponding synchronization operation based on the synchronization requirement between the at least two PDCP SDUs and the discard timer corresponding to the at least two PDCP SDUs, thereby ensuring synchronous transmission between the PDCP SDUs, thereby ensuring that the transmission of service data on the air interface meets the synchronization requirement, thereby improving the transmission performance of the service data.

[0192] Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment, can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation can be determined according to actual usage requirements, and the embodiments of this application do not limit this.

[0193] The data processing method provided in the embodiment of the present application can be executed by a data processing device. In the embodiment of the present application, the data processing device provided in the embodiment of the present application is described by taking the data processing method executed by the data processing device as an example.

[0194] FIG6 shows a possible structural diagram of a data processing device involved in an embodiment of the present application. As shown in FIG6 , the data processing device 40 may include: a first receiving module 41 , a first starting module 42 and a first executing module 43 .

[0195] The first receiving module 41 is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization is required between the at least two PDCP SDUs.

[0196] The first starting module 42 is configured to start the discard timers corresponding to at least two PDCP SDUs respectively.

[0197] The first execution module 43 is configured to execute a synchronization operation based on a discarding timer according to whether a synchronization requirement is met.

[0198] In a possible implementation, the first receiving module 41 is further configured to receive first synchronization information configured by a network-side device, where the first synchronization information is used to determine a synchronization requirement between at least two PDCP SDUs.

[0199] Alternatively, the data processing device 40 provided in the embodiment of the present application further includes: a determination module. The determination module is configured to determine a synchronization requirement between at least two PDCP SDUs based on first information corresponding to the at least two PDCP SDUs, where the first information includes at least one of the following: QoS flow, DRB, LCG, and LCH.

[0200] In one possible implementation, the first execution module 43 is specifically configured to adjust the duration of the discard timer corresponding to at least one of the at least two PDCP SDUs if the difference between the remaining time between the discard timers corresponding to the at least two PDCP SDUs and their respective timeouts does not meet the synchronization requirement.

[0201] In a possible implementation, the first execution module 43 is specifically configured to:

[0202] Extending a duration of a discard timer corresponding to a first PDCP SDU among the at least two PDCP SDUs to a first duration, wherein the first duration is determined based on a timeout moment of a discard timer corresponding to a second PDCP SDU among the at least two PDCP SDUs, a synchronization requirement, and a start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU including M PDCP SDUs among the at least two PDCP SDUs having the shortest remaining time until the corresponding discard timer expires, and the second PDCP SDU being a PDCP SDU among the at least two PDCP SDUs having the longest remaining time until the corresponding discard timer expires;

[0203] or,

[0204] Shorten the duration of the discard timer corresponding to the fourth PDCP SDU in the at least two PDCP SDUs to a second duration, wherein the second duration is determined according to the timeout moment of the discard timer corresponding to the third PDCP SDU in the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes N PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the fourth PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0205] In one possible implementation, a value range of the first duration is [timeout time of the discard timer corresponding to the second PDCP SDU - synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU, timeout time of the discard timer corresponding to the second PDCP SDU + synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU];

[0206] The value range of the above-mentioned second duration is [the timeout time of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, the timeout time of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

[0207] In one possible implementation, the first execution module 43 is specifically configured to start a synchronization timer if there is a PDCP SDU that has completed transmission among at least two PDCP SDUs and there is at least one PDCP SDU corresponding to a discard timer that is still running, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirements.

[0208] In one possible implementation, the first execution module 43 is specifically configured to determine whether to start a synchronization timer if there is a PDCP SDU that has completed transmission among at least two PDCP SDUs and a discard timer corresponding to at least one PDCP SDU is still running, and the duration of the synchronization timer is less than or equal to the duration for meeting the synchronization requirements.

[0209] In a possible implementation, the first execution module 43 is specifically configured to:

[0210] If the remaining time of the running discard timers before their respective timeouts does not meet the synchronization requirement, it is determined to start the synchronization timer;

[0211] or,

[0212] If the remaining time of the running discard timers before their respective expiration times meets the synchronization requirement, it is determined not to start the synchronization timer.

[0213] In a possible implementation, the first execution module 43 is further configured to, after determining to start the synchronization timer, discard the PDCP SDU corresponding to the synchronization timer after the synchronization timer times out.

[0214] In a possible implementation, the first execution module 43 is further configured to discard the PDCP SDU corresponding to the discard timer after the discard timer expires.

[0215] An embodiment of the present application provides a data processing device, wherein there is a synchronization requirement between at least two PDCP SDUs. The data processing device can perform corresponding synchronization operations in combination with the synchronization requirement between the at least two PDCP SDUs and the discard timers corresponding to the at least two PDCP SDUs, thereby ensuring synchronous transmission between the PDCP SDUs, thereby ensuring that the transmission of service data on the air interface meets the synchronization requirement and improves the transmission performance of the service data.

[0216] The data processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0217] The data processing device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned data processing method embodiment and achieve the same technical effect. To avoid repetition, it will not be described here.

[0218] FIG7 shows a possible structural diagram of a data processing device involved in an embodiment of the present application. As shown in FIG7 , a data processing device 50 may include: a second receiving module 51 , a second starting module 52 , and a second executing module 53 .

[0219] The second receiving module 51 is configured to receive at least two PDCP SDUs from a higher layer; wherein synchronization is required between the at least two PDCP SDUs.

[0220] The second starting module 52 is configured to start the discard timers corresponding to at least two PDCP SDUs respectively.

[0221] The second execution module 53 is configured to execute a synchronization operation based on a discarding timer according to whether the synchronization requirement is met.

[0222] In a possible implementation, the second receiving module 51 is further configured to send first synchronization information to the terminal, where the first synchronization information is used to determine a synchronization requirement between at least two PDCP SDUs.

[0223] In one possible implementation, the second execution module 53 is specifically configured to adjust the duration of the discard timer corresponding to at least one of the at least two PDCP SDUs if the difference between the remaining time between the discard timers corresponding to the at least two PDCP SDUs and their respective timeouts does not meet the synchronization requirement.

[0224] In a possible implementation, the second execution module 53 is specifically configured to:

[0225] Extending a duration of a discard timer corresponding to a first PDCP SDU among the at least two PDCP SDUs to a first duration, wherein the first duration is determined based on a timeout moment of a discard timer corresponding to a second PDCP SDU among the at least two PDCP SDUs, a synchronization requirement, and a start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU including M PDCP SDUs among the at least two PDCP SDUs having the shortest remaining time until the corresponding discard timer expires, and the second PDCP SDU being a PDCP SDU among the at least two PDCP SDUs having the longest remaining time until the corresponding discard timer expires;

[0226] or,

[0227] Shorten the duration of the discard timer corresponding to the fourth PDCP SDU in the at least two PDCP SDUs to a second duration, wherein the second duration is determined according to the timeout moment of the discard timer corresponding to the third PDCP SDU in the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes N PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the fourth PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs.

[0228] In one possible implementation, a value range of the first duration is [timeout time of the discard timer corresponding to the second PDCP SDU - synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU, timeout time of the discard timer corresponding to the second PDCP SDU + synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU];

[0229] The value range of the above-mentioned second duration is [the timeout time of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, the timeout time of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

[0230] In one possible implementation, the second execution module 53 is specifically configured to start a synchronization timer if there is a PDCP SDU that has completed transmission among at least two PDCP SDUs and there is at least one PDCP SDU whose corresponding discard timer is still running, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirements.

[0231] In one possible implementation, the second execution module 53 is specifically configured to determine whether to start a synchronization timer if there is a PDCP SDU that has completed transmission among at least two PDCP SDUs and there is at least one PDCP SDU corresponding to a discard timer that is still running, and the duration of the synchronization timer is less than or equal to the duration for meeting the synchronization requirements.

[0232] In a possible implementation, the second execution module 53 is specifically configured to:

[0233] If the remaining time of the running discard timers before their respective timeouts does not meet the synchronization requirement, it is determined to start the synchronization timer;

[0234] or,

[0235] If the remaining time of the running discard timers before their respective expiration times meets the synchronization requirement, it is determined not to start the synchronization timer.

[0236] In a possible implementation, the second execution module 53 is further configured to, after determining to start the synchronization timer, discard the PDCP SDU corresponding to the synchronization timer after the synchronization timer expires.

[0237] In a possible implementation, the second execution module 53 is further configured to discard the PDCP SDU corresponding to the discard timer after the discard timer expires.

[0238] An embodiment of the present application provides a data processing device, wherein there is a synchronization requirement between at least two PDCP SDUs. The data processing device can perform corresponding synchronization operations in combination with the synchronization requirement between the at least two PDCP SDUs and the discard timers corresponding to the at least two PDCP SDUs, thereby ensuring synchronous transmission between the PDCP SDUs, thereby ensuring that the transmission of service data on the air interface meets the synchronization requirement and improves the transmission performance of the service data.

[0239] The data processing device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned data processing method embodiment and achieve the same technical effect. To avoid repetition, it will not be described here.

[0240] As shown in Figure 8, an embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002, wherein the memory 5002 stores a program or instruction that can be run on the processor 5001. For example, when the communication device 5000 is a terminal, the program or instruction, when executed by the processor 5001, implements the various steps of the above-mentioned terminal-side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 5000 is a network-side device, the program or instruction, when executed by the processor 5001, implements the various steps of the above-mentioned network-side device method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0241] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the above-described data processing method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and each implementation process and implementation method of the above-described method embodiment can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0242] The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of the processor 7010.

[0243] Those skilled in the art will appreciate that the terminal 7000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 7010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0244] It should be understood that in an embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0245] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 7001 may transmit the data to the processor 7010 for processing. Furthermore, the RF unit 7001 may send uplink data to the network-side device. Typically, the RF unit 7001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0246] The memory 7009 can be used to store software programs or instructions and various data. The memory 7009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 7009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 7009 in the embodiment of the present application includes, but is not limited to, these and any other suitable types of memory.

[0247] The processor 7010 may include one or more processing units. Optionally, the processor 7010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into the processor 7010.

[0248] The terminal provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned data processing method embodiment. To avoid repetition, it will not be repeated here.

[0249] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the above-mentioned data processing method embodiment. This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0250] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 10, the network-side device 600 includes an antenna 61, a radio frequency device 62, a baseband device 63, a processor 64, and a memory 65. Antenna 61 is connected to radio frequency device 62. In the uplink direction, radio frequency device 62 receives information via antenna 61 and sends the received information to baseband device 63 for processing. In the downlink direction, baseband device 63 processes the information to be transmitted and sends it to radio frequency device 62. Radio frequency device 62 processes the received information and then sends it through antenna 61.

[0251] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 63 , which includes a baseband processor.

[0252] The baseband device 63 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 65 through a bus interface to call the program in the memory 65 and execute the network side device operations shown in the above method embodiment.

[0253] The network side device may further include a network interface 66, which is, for example, a Common Public Radio Interface (CPRI).

[0254] Specifically, the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 65 and can be run on the processor 64. The processor 64 calls the instructions or programs in the memory 65 to execute the methods executed by the modules shown in the above-mentioned data processing device and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0255] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data processing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0256] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0257] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0258] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0259] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0260] An embodiment of the present application further provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the above-mentioned data processing method, and the network-side device can be used to execute the steps of the above-mentioned data processing method.

[0261] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0262] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0263] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data processing method, comprising: The terminal receives at least two Packet Data Convergence Protocol (PDCP) service data units (SDUs) from a higher layer; wherein synchronization requirements are required between the at least two PDCP SDUs; The terminal starts a discard timer corresponding to each of the at least two PDCP SDUs; According to whether the synchronization requirement is met, the terminal performs a synchronization operation based on the discard timer.

2. The method according to claim 1, wherein Also includes: The terminal receives first synchronization information configured by a network-side device, where the first synchronization information is used to determine a synchronization requirement between the at least two PDCP SDUs; or, The terminal determines the synchronization requirement between the at least two PDCP SDUs according to first information corresponding to the at least two PDCP SDUs, where the first information includes at least one of the following: quality of service QoS flow, data radio bearer DRB, logical channel group LCG, and logical channel LCH.

3. The method according to claim 1 or 2, wherein: The terminal performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If the difference between the remaining time between the discard timers corresponding to the at least two PDCP SDUs and their respective timeouts does not meet the synchronization requirement, the terminal adjusts the duration of the discard timer corresponding to at least one of the at least two PDCP SDUs.

4. The method according to claim 3, wherein: Adjusting, by the terminal, a duration of a discard timer of at least one of the at least two PDCP SDUs, including: The terminal extends, by the terminal, a duration of a discard timer corresponding to a first PDCP SDU among the at least two PDCP SDUs to a first duration, wherein the first duration is determined according to a timeout moment of a discard timer corresponding to a second PDCP SDU among the at least two PDCP SDUs, the synchronization requirement, and a start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU including M PDCP SDUs among the at least two PDCP SDUs having the shortest remaining time until the corresponding discard timer times out, and the second PDCP SDU being a PDCP SDU among the at least two PDCP SDUs having the longest remaining time until the corresponding discard timer times out; or, The terminal shortens the duration of the discard timer corresponding to the fourth PDCP SDU among the at least two PDCP SDUs to a second duration, wherein the second duration is determined according to the timeout moment of the discard timer corresponding to the third PDCP SDU among the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes N PDCP SDUs among the at least two PDCP SDUs with the shortest remaining time until the corresponding discard timer times out, and the fourth PDCP SDU is the PDCP SDU among the at least two PDCP SDUs with the longest remaining time until the corresponding discard timer times out.

5. The method according to claim 4, wherein The first duration has a value range of [timeout time of the discard timer corresponding to the second PDCP SDU - synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU, timeout time of the discard timer corresponding to the second PDCP SDU + synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU]; The value range of the second duration is [the timeout time of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, or the timeout time of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

6. The method according to claim 1 or 2, wherein: The terminal performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If there is a PDCP SDU whose transmission is completed among the at least two PDCP SDUs, and there is at least one PDCP SDU whose corresponding discard timer is still running, the terminal starts a synchronization timer, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirement.

7. The method according to claim 1 or 2, wherein: The terminal performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If there is a PDCP SDU whose transmission is completed among the at least two PDCP SDUs, and there is at least one PDCP SDU whose corresponding discard timer is still running, the terminal determines whether to start a synchronization timer, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirement.

8. The method according to claim 7, wherein: The terminal determines whether to start a synchronization timer, including: If the remaining time of the running discard timers to their respective timeouts does not meet the synchronization requirement, the terminal determines to start the synchronization timer; or, If the remaining time of the running discard timers until their respective timeouts meet the synchronization requirement, the terminal determines not to start the synchronization timer.

9. The method according to claim 8, wherein After the terminal determines to start the synchronization timer, the further step includes: After the synchronization timer expires, the PDCP SDU corresponding to the synchronization timer is discarded.

10. The method according to any one of claims 1 to 9, wherein: The method further comprises: After the discard timer times out, the terminal discards the PDCP SDU corresponding to the discard timer.

11. A data processing method, comprising: The network side device receives at least two Packet Data Convergence Protocol (PDCP) service data units (SDUs) from a higher layer; wherein synchronization requirements are required between the at least two PDCP SDUs; The network side device starts the discard timer corresponding to each of the at least two PDCP SDUs respectively; According to whether the synchronization requirement is met, the network side device performs a synchronization operation based on the discard timer.

12. The method according to claim 11, wherein Also includes: The network-side device sends first synchronization information to the terminal, where the first synchronization information is used to determine a synchronization requirement between the at least two PDCP SDUs.

13. The method according to claim 11 or 12, wherein: The network-side device performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If the difference between the remaining time between the discard timers corresponding to the at least two PDCP SDUs and their respective timeouts does not meet the synchronization requirement, the network side device adjusts the duration of the discard timer corresponding to at least one of the at least two PDCP SDUs.

14. The method according to claim 13, wherein: Adjusting, by the network side device, a duration of a discard timer of at least one of the at least two PDCP SDUs, includes: The network-side device extends the duration of a discard timer corresponding to a first PDCP SDU in the at least two PDCP SDUs to a first duration, wherein the first duration is determined according to the timeout moment of the discard timer corresponding to a second PDCP SDU in the at least two PDCP SDUs, the synchronization requirement, and the start moment of the discard timer corresponding to the first PDCP SDU, the first PDCP SDU including M PDCP SDUs with the shortest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs, and the second PDCP SDU is the PDCP SDU with the longest remaining time until the corresponding discard timer times out among the at least two PDCP SDUs; or, The network side device shortens the duration of the discard timer corresponding to the fourth PDCP SDU among the at least two PDCP SDUs to a second duration, wherein the second duration is determined according to the timeout moment of the discard timer corresponding to the third PDCP SDU among the at least two PDCP SDUs, the synchronization requirement and the start moment of the discard timer corresponding to the fourth PDCP SDU, the third PDCP SDU includes N PDCP SDUs among the at least two PDCP SDUs with the shortest remaining time until the corresponding discard timer times out, and the fourth PDCP SDU is the PDCP SDU among the at least two PDCP SDUs with the longest remaining time until the corresponding discard timer times out.

15. The method according to claim 14, wherein The first duration has a value range of [timeout time of the discard timer corresponding to the second PDCP SDU - synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU, timeout time of the discard timer corresponding to the second PDCP SDU + synchronization requirement - start time of the discard timer corresponding to the first PDCP SDU]; The value range of the second duration is [the timeout time of the discard timer corresponding to the third PDCP SDU - the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU, or the timeout time of the discard timer corresponding to the third PDCP SDU + the synchronization requirement - the start time of the discard timer corresponding to the fourth PDCP SDU].

16. The method according to claim 11 or 12, wherein: The network-side device performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If there is a PDCP SDU that has been transmitted among the at least two PDCP SDUs, and there is at least one PDCP SDU whose corresponding discard timer is still running, the network side device starts a synchronization timer, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirement.

17. The method according to claim 11 or 12, wherein: The network-side device performing a synchronization operation based on the discard timer according to whether the synchronization requirement is met includes: If there is a PDCP SDU that has completed transmission among the at least two PDCP SDUs, and there is at least one PDCP SDU whose corresponding discard timer is still running, the network side device determines whether to start the synchronization timer, and the duration of the synchronization timer is less than or equal to the duration that meets the synchronization requirement.

18. The method according to claim 17, wherein The network side device determines whether to start a synchronization timer, including: If the remaining time of the running discard timers before their respective expiration does not meet the synchronization requirement, the network side device determines to start the synchronization timer; or, If the remaining time of the running discard timers until their respective timeouts meets the synchronization requirement, the network side device determines not to start the synchronization timer.

19. The method according to claim 18, wherein After the network side device determines to start the synchronization timer, the method further includes: After the synchronization timer expires, the PDCP SDU corresponding to the synchronization timer is discarded.

20. The method according to any one of claims 11 to 19, wherein: The method further comprises: After the discard timer times out, the network side device discards the PDCP SDU corresponding to the discard timer.

21. A data processing device comprising: a first receiving module, a first starting module and a first executing module; The first receiving module is configured to receive at least two Packet Data Convergence Protocol (PDCP) service data units (SDUs) from a higher layer; wherein the at least two PDCP SDUs have synchronization requirements; The first starting module is configured to start a discard timer corresponding to each of the at least two PDCP SDUs; The first execution module is configured to enable the terminal to perform a synchronization operation based on the discard timer according to whether the synchronization requirement is met.

22. A data processing device comprising: a second receiving module, a second starting module and a second executing module; The second receiving module is configured to receive at least two Packet Data Convergence Protocol (PDCP) service data units (SDUs) from a higher layer; wherein the at least two PDCP SDUs have synchronization requirements; The second starting module is configured to start a discard timer corresponding to each of the at least two PDCP SDUs; The second execution module is configured to enable the terminal to perform a synchronization operation based on the discard timer according to whether the synchronization requirement is met.

23. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data processing method according to any one of claims 1 to 10 are implemented.

24. A network-side device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the data processing method according to any one of claims 11 to 20 are implemented.

25. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the data processing method according to any one of claims 1 to 10, or implements the steps of the data processing method according to any one of claims 11 to 20.

Images