Communication method and communication apparatus

By obtaining the data delay expiration time, updating the PDCP window state variable, and delivering the data in a timely manner, the problem of data not being delivered due to timeout on the receiving side was solved, improving data reliability and user experience.

WO2026067749A1PCT designated stage Publication Date: 2026-04-02HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-09-29
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

In existing technologies, the problem of data not being delivered due to timeout or being delivered after timeout on the receiving side causes data to be unable to be delivered in a timely manner according to the time delay requirements, affecting data reliability and user experience.

Method used

By obtaining the data's expiration time, the Packet Data Convergence Layer Protocol (PDCP) window state variable is updated, and the data is delivered in a timely manner according to the expiration time, including starting or stopping the reordering timer, to ensure that the data is delivered in time before the expiration time.

Benefits of technology

It enables timely data delivery, avoids data delays, improves data reliability and user experience, and meets latency requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025125161_02042026_PF_FP_ABST
    Figure CN2025125161_02042026_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method and a communication apparatus, which are applied to the technical field of communications. The communication method comprises: acquiring first information, the first information comprising information of the delay expiration time of first data; and then, on the basis of the delay expiration time of the first data, updating a state variable and / or submitting at least one piece of data. The method helps to prevent data submission from overrunning.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication apparatus

[0001] This application claims priority to the Chinese Patent Application No. 202411400180.2, filed on September 30, 2024, entitled “Communication method and communication apparatus”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a communication method and a communication apparatus. BACKGROUND

[0003] Generally, after receiving data, the receiving side submits the data to the upper layer in order based on the count value of the data. Since the receiving side does not necessarily receive the data in the order of increasing count value, for example, there may be a hole in the receiving window of the receiving side, and the count value of the data received in the receiving window is greater than the count value of the data not received. Therefore, generally, the receiving side is required to submit the data to the upper layer only when a condition is met, for example, the condition can include a reordering timer timeout.

[0004] Generally, if there is a hole in the receiving window of the receiving side, a reordering timer is started. For example, if the receiving side does not receive data with a count value of 2, but receives data with a count value of 3, and the reordering timer is not running, the receiving side will start the reordering timer. If the receiving side receives data with a count value of 2 before the reordering timer times out, the receiving side can submit data with a count value greater than 2 and continuous count values, and the receiving side can stop the reordering timer. If the reordering timer times out, the receiving side can submit data with a count value greater than 2 and continuous count values without waiting for data with a count value of 2.

[0005] However, submitting data to the upper layer according to the reordering timer can cause the data to exceed its delay requirement but still not be submitted to the upper layer. Therefore, how to avoid data from not being submitted before it times out (or, how to avoid data from timing out or being submitted after timing out, or how to ensure that data is submitted in time before / when it times out), is a technical problem that needs to be solved. SUMMARY

[0006] The present application provides a communication method and a communication apparatus, which are beneficial to avoid data from not being submitted before it times out.

[0007] In a first aspect, a communication method is provided. The method can be performed by a terminal device itself, or by a processor, module, chip, or chip system in the terminal device, which is not limited in the present application. Alternatively, the method can be performed by a network device itself, or by a processor, module, chip, or chip system in the network device, which is not limited in the present application. Without causing ambiguity in context, the method is applied to a first device, which can be a terminal device or a network device. The method comprises: obtaining first information, the first information comprising information of a time delay expiration time of first data; and performing state variable updating and / or submitting at least one data according to the time delay expiration time of the first data.

[0008] Based on the method described in the first aspect, the first device performs state variable updating according to the time delay expiration time of the first data, which is beneficial to updating packet data convergence protocol (PDCP) window / state variable in time, and further beneficial to submitting data in time. The first device submits at least one data according to the time delay expiration time of the first data, which is beneficial to submitting data in time. Submitting data in time is beneficial to avoiding data not being submitted before the data expires, and is beneficial to avoiding submitting data after the data expires. The method ensures / substantially guarantees that data is submitted in time before the data expires, which is beneficial to decoding at a receiving end, beneficial to guaranteeing a time delay requirement of data, and can improve reliability of data, which is beneficial to service / user experience.

[0009] In a possible implementation, obtaining the first information can be further implemented as: obtaining the first data, and the first data carrying the first information.

[0010] In a possible implementation, performing state variable updating according to the time delay expiration time of the first data can be further implemented as: if the first data expires, performing at least one of the following:

[0011] updating the first state variable to a first count value, the first count value being greater than a second count value; or

[0012] if a reordering timer is running, and the first state variable is greater than or equal to a second state variable, the first device stops the reordering timer; or

[0013] if the reordering timer is not running, and the first state variable is less than a third state variable, the first device starts the reordering timer.

[0014] The second count value is a count value of the first data; the first state variable is used to indicate a count value of a first data which the first device waits to submit; the second state variable is used to indicate a count value of data which triggers the reordering timer plus 1; and the third state variable is used to indicate a count value of next data which the first device expects to receive.

[0015] According to the implementation, the first device updates the state variables when the first data is not submitted and the time delay of the first data expires, so that the first device can submit the data in the receiving window which meets the submission condition in time, and the data is not submitted due to time delay is avoided.

[0016] In a possible implementation, the data corresponding to the first count value is the first unreceived data with a count value greater than the second count value; or, the data corresponding to the first count value is the first unreceived data with a count value greater than the second count value except for discarded data.

[0017] In a possible implementation, the at least one data is submitted according to the time delay expiration time of the first data, and the implementation can be further configured as: if the time delay of the first data expires, the at least one data is submitted. According to the implementation, the data is not submitted due to time delay is avoided.

[0018] In a possible implementation, the at least one data includes at least one second data and / or at least one third data; the second data corresponds to a count value less than the second count value; the third data corresponds to a count value greater than or equal to the second count value; and the second count value is a count value of the first data.

[0019] In a possible implementation, the count values of the at least one third data are continuous, or the count values of the at least one third data and the discarded data are continuous.

[0020] In a possible implementation, the information of the time delay expiration time of the first data includes information of a time unit in which the time delay expiration time of the first data is located, and the time unit includes at least one of a frame, a subframe, a slot or a symbol.

[0021] In a possible implementation, the second information is carried in the first data, and the second information is used to indicate that the first information is carried in the first data.

[0022] In a possible implementation, the method further includes: obtaining first indication information, and the first indication information is used to indicate that information of a time delay expiration time of data is carried in data associated with a first radio bearer (RB) or a first PDCP entity.

[0023] In a possible implementation, the first data is a PDCP protocol data unit (PDU).

[0024] In a second aspect, a communication method is provided. The method can be performed by a terminal device itself, or can be performed by a processor, a module, a chip, or a chip system in the terminal device, which is not limited in the application. Alternatively, the method can be performed by a network device itself, or can be performed by a processor, a module, a chip, or a chip system in the network device, which is not limited in the application. Without causing ambiguity in the context, the method is applied to a second device, which can be a terminal device or a network device, and the method comprises:

[0025] The beneficial effects of the second aspect can be referred to the description in the first aspect, which will not be repeated here.

[0026] In a possible implementation, the information of the time delay expiration time of the first data comprises information of a time unit in which the time delay expiration time of the first data is located, and the time unit comprises at least one of a frame, a subframe, a slot, or a symbol.

[0027] In a possible implementation, the second information is carried in the first data, and the second information is used to indicate that the first information is carried in the first data.

[0028] In a possible implementation, the method further comprises: sending first indication information, and the first indication information is used to indicate that the information of the time delay expiration time of the data is carried in the data associated with the first RB or the first PDCP entity.

[0029] In a possible implementation, the first data is a PDCP PDU.

[0030] In a third aspect, an embodiment of the present application provides a communication device for executing the method in any possible implementation manner of the first aspect or the second aspect. The communication device comprises a module for executing the method in any possible implementation manner of the first aspect or the second aspect.

[0031] In a fourth aspect, an embodiment of the present application provides a communication device comprising a processing circuit for executing the method in any possible implementation manner of the first aspect or the second aspect. The processing circuit is used to execute a program, and when the program is executed, the method in any possible implementation manner of the first aspect or the second aspect is executed.

[0032] In a possible implementation, the communication device further comprises a memory for storing the program.

[0033] In a possible implementation, the memory is located outside the communication device.

[0034] In a possible implementation, the memory is located in the communication apparatus.

[0035] In a possible implementation, the processing circuitry and the memory can be integrated in one device, i.e., the processing circuitry and the memory can be integrated together. For example, the communication apparatus can be a chip.

[0036] In a possible implementation, the communication apparatus further comprises a transceiver circuit, which is configured to receive information (or input information) or send information (or output information).

[0037] In a fifth aspect, an embodiment of the present application provides a communication apparatus, which comprises a processing circuitry and a transceiver circuit, the processing circuitry can be a logic circuit, and the transceiver circuit can be an interface circuit, the logic circuit and the interface circuit are coupled; the interface circuit is configured to input and / or output information, and the logic circuit is configured to execute the method in any possible implementation of the first aspect or the second aspect.

[0038] In a sixth aspect, the present application provides a communication system, which comprises a communication apparatus for executing the method in the first aspect and a communication apparatus for executing the method in the second aspect.

[0039] In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, which is configured to store a computer program, when the computer program is executed on a computer, the method in any possible implementation of the first aspect or the second aspect is executed.

[0040] In an eighth aspect, an embodiment of the present application provides a computer program product, when the computer program product is executed on a computer, the method in any possible implementation of the first aspect or the second aspect is executed. BRIEF DESCRIPTION OF DRAWINGS

[0041] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0042] FIG. 2 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0043] FIG. 3 is a schematic diagram of a network architecture according to an embodiment of the present application;

[0044] FIG. 4 is a schematic diagram of a network architecture according to an embodiment of the present application;

[0045] FIG. 5 is a schematic diagram of a protocol stack according to an embodiment of the present application;

[0046] FIG. 6 is a schematic diagram of a relationship between a PDU and an SDU of a protocol layer according to an embodiment of the present application;

[0047] FIG. 7 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0048] FIG. 8 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0049] FIG. 9 is a schematic diagram of a COUNT according to an embodiment of the present application;

[0050] FIG. 10 is a schematic diagram of data transmission according to an embodiment of the present application;

[0051] FIG. 11 is a schematic diagram of a communication method according to an embodiment of the present application;

[0052] FIG. 12 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0053] FIG. 13 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0054] FIG. 14 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0055] FIG. 15 is a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present application;

[0056] FIG. 16 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0057] FIG. 17 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0058] FIG. 18 is a schematic diagram of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the technical solution of the present application more comprehensible, the present application will be further described below with reference to the accompanying drawings.

[0060] The terms "first" and "second" and the like in the specification of the present application, claims, and drawings are only used to distinguish different objects, and are not used to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus, and the like including a series of steps or units is not limited to the listed steps or units, but can optionally include other steps or units not listed or inherent to the process, method, product, or apparatus.

[0061] Reference to an "embodiment" herein means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive of one another. Those skilled in the art will appreciate from the present disclosure that embodiments described herein can be combined with other embodiments in various ways.

[0062] In this application, "at least one" means one or more, "multiple" means two or more, "at least two" means two or three and three or more, and / or is used to describe the relationship between associated objects, which means that there can be three relationships, for example, "A and / or B" can mean: only A, only B, and A and B exist at the same time, where A and B can be singular or plural. "Or" means that there can be two relationships, such as only A, only B; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A, only B, and A and B exist at the same time. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one" or similar expressions mean any combination of these items. For example, at least one of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c". "When" and "if" both mean that under certain objective circumstances, the corresponding processing will be done, not limited to time, and does not require a judgment action when implemented, nor does it mean that there are other limitations.

[0063] In this application, "send" and "receive" represent the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct transmission through the air interface, or indirect transmission through other units or modules through the air interface. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct reception from YY through the air interface, or indirect reception from YY through other units or modules through the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules or hardware modules within a device through a bus, wire or interface.

[0064] In the embodiments of the present application, the words "exemplary" and "for example" are used to mean serving as an example, instance, or illustration, at 99 least with respect to the matters described at that point in the disclosure. The absence of the words "exemplary" and "for example" should not necessarily be taken to mean that the disclosure is in any way not exhaustive of other embodiments or scenarios. The words "exemplary" and "for example" are simply intended to highlight or emphasize that the referenced embodiments or scenarios are examples, and should not be viewed as limiting in any way. Indeed, the embodiments and scenarios set forth herein are intended to be illustrative only and not restrictive.

[0065] In the present application, "indication" can include direct indication, or indirect indication, or explicit indication, or implicit indication.

[0066] In the present application, "include" can include direct inclusion, or indirect inclusion, or explicit inclusion, or implicit inclusion.

[0067] It should be understood that the prior art can change as the technical solutions evolve, and the technical solutions provided in the present application are not limited to the provided prior art.

[0068] It should be noted that different embodiments or parts of steps (for example, any one or more steps) in different embodiments in the present application can be combined with each other to form new embodiments. It should be noted that the parts of steps or any one or more steps in different embodiments can include optional steps in a certain embodiment, or can include mandatory steps in a certain embodiment, or can include optional steps and mandatory steps in a certain embodiment, which is not limited in the present application.

[0069] It should be noted that the terms and / or descriptions of different embodiments are consistent and can be mutually referred to each other if there is no special description and logical conflict.

[0070] It should be noted that the present application does not limit the order of the steps in the embodiments of the present application.

[0071] It should be noted that the present application does not limit the order of the conditions in the embodiments of the present application.

[0072] It should be noted that the "after" and "time" in the present application are not strictly limited to the time point.

[0073] It should be noted that the terms, names and the like involved in the present application are only examples, which can also be other names, and the present application is not limited.

[0074] The following introduces a communication system related to the embodiments of the present application.

[0075] The technical solutions provided in the present application can be applied to various communication systems, for example, a 5th generation (5G) or new radio (NR) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a wireless local area network (WLAN) system, a satellite communication system, a future communication system, or a fusion system of multiple systems, and the like. The technical solutions provided in the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and internet of things (IoT) communication system or other communication systems.

[0076] The method provided in the embodiments of the present application can be applied to two entities in a communication system, for example, one of the two entities can send information to the other entity, or receive information sent by the other entity. In a wireless communication system, communication devices are included, and the communication devices can perform wireless communication by using air interface resources. The air interface resources can include at least one of time domain resources, frequency domain resources, code resources, and space resources, which are not limited in the present application. For example, the two entities can include a network device and a terminal device, or a chip that can be placed in the network device, and a chip that can be placed in the terminal device, and the like. Of course, with the development of standards, other types of entities can also appear in the future, which are not limited in the embodiments of the present application.

[0077] FIG. 1 is a schematic diagram of an architecture of a communication system provided in the embodiments of the present application. As shown in FIG. 1, the communication system can include at least one network device and at least one terminal device, such as terminal device 1 to terminal device 4 in FIG. 1. The terminal device and the network device can communicate through an air interface Uu link or an NTN link, and the like. For example, the terminal device 3 and the terminal device 4 can communicate through a D2D or sidelink, and the like. The form of the terminal device shown in FIG. 1 is only an example, and in specific implementation, the terminal device can also include a vehicle-mounted device or a vehicle-mounted terminal in a vehicle network, and the like. The embodiments of the present application do not limit the specific form of the terminal device when it is applied to a vehicle network or the Internet.

[0078] FIG. 2 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application. As shown in FIG. 2, the scenario of the communication system can include at least one of the following: point-to-point single connection between a network device and a terminal device, point-to-point dual connectivity (DC) between a network device and a terminal device, multi-hop single connection between a network device and a terminal device, or multi-hop dual connectivity between a network device and a terminal device.

[0079] FIG. 1 exemplarily shows one network device and multiple terminal devices, and FIG. 2 exemplarily shows single connection and dual connectivity. In a specific implementation, the communication system can further include a larger number of network devices, and each network device can include a larger or smaller number of terminal devices within its coverage, which is not limited in the embodiments of the present application. The architectures shown in FIG. 1 and FIG. 2 are only examples, and do not limit the network architecture applicable to the present application, as long as any network-side device in a cellular network communicates or senses other devices, which is a network architecture applicable to the present application.

[0080] The terminal device and the network device are described in detail below.

[0081] A terminal device is a device with wireless transceiving function. The terminal device can communicate with an access network device (or also referred to as an access device or a network device shown below) in a radio access network (RAN). The terminal device can also be referred to as a user equipment (UE), an access terminal, a terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a user agent, or a user apparatus, etc. In a possible implementation, the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; or can be deployed on water, including a ship; or can be deployed in the air, such as an airplane, a balloon or a satellite, etc. In another possible implementation, the terminal device can be a handheld device, a vehicle-mounted device, a wearable device, a sensor, a terminal in Internet of Things, a terminal in Internet of Vehicles, a drone, a terminal device in 5G network or future network, etc., which is not limited in the embodiments of the present application. In yet another possible implementation, the terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote medical treatment, a wireless terminal in smart power grid, a wireless terminal in smart city, or a wireless terminal in smart home, etc.

[0082] In embodiments of the present application, the apparatus for implementing the function of the terminal device can be a terminal device; it can also be an apparatus capable of supporting the terminal device to implement the function, such as a chip system. The apparatus can be installed in the terminal device or used in matching with the terminal device. In embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices. For ease of description, the apparatus for implementing the function of the terminal device is taken as an example of UE to describe the technical solutions provided in embodiments of the present application.

[0083] The network device can be an apparatus deployed in a wireless access network to provide wireless communication services for terminal devices. The network device can also be referred to as an access network device, an access device, or a RAN device, etc. For example, the network device can be a next generation node B (gNB), a next generation evolved node B (ng-eNB), or a network device in future communication, etc. The network device can be any kind of device with wireless transceiver function, including but not limited to the above-mentioned base stations (including base stations deployed on satellites). The network device can also be an apparatus with base station function in future communication systems. As an example, the network device can be an access node, a wireless relay node, a wireless backhaul node, etc. in a wireless fidelity (Wi-Fi) system. As another example, the network device can be a wireless controller in a cloud radio access network (CRAN) scenario. As yet another example, the network device can be a wearable device or a vehicle-mounted device, etc. that can provide wireless communication services. As yet another example, the network device can also be a small station, a transmission reception point (TRP) (or also referred to as a transmission point), etc. In different wireless access technology systems, the names of apparatuses with network device functions can be different, and embodiments of the present application will not be listed one by one.

[0084] The network device can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, the helicopter or the drone can be configured to act as a device that communicates with another network device.

[0085] FIG. 3 is a schematic diagram of a network architecture applicable to embodiments of the present application. As shown in FIG. 3, the network architecture includes a core network device, a network device, and a terminal device. The network device includes a baseband device and a radio frequency device, wherein the baseband device can be implemented by one node or by multiple nodes, and the radio frequency device can be independently implemented by pulling away from the baseband device or integrated in the baseband device, or partially independently integrated and partially integrated in the baseband device. For example, in an LTE communication system, the RAN device (eNB) includes a baseband device and a radio frequency device, wherein the radio frequency device can be arranged remotely relative to the baseband device, such as a remote radio unit (RRU) arranged remotely relative to a BBU.

[0086] The communication between the network device and the terminal device follows a certain protocol layer structure. For example, the control plane protocol layer structure can include the functions of the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer. The user plane protocol layer structure can include the functions of the PDCP layer, the RLC layer, the MAC layer, and the physical layer. In one possible implementation, the PDCP layer can further include a service data adaptation (SDAP) layer.

[0087] The network device can implement the functions of the RRC, PDCP, RLC, and MAC protocol layers by one node or by multiple nodes. For example, in one evolution structure, the network device can include a CU and a DU, and multiple DUs can be centrally controlled by one CU. As shown in FIG. 3, the CU and the DU can be divided according to the protocol layers of the wireless network, such as the functions of the PDCP layer and above protocol layers being arranged in the CU, and the functions of the PDCP layer below, such as the RLC layer and the MAC layer, being arranged in the DU.

[0088] The division of the protocol layers is only an example, and other protocol layer divisions are also possible, such as a division at the RLC layer, with the functions of the RLC layer and the protocol layers above the RLC layer being arranged in the CU, and the functions of the protocol layers below the RLC layer being arranged in the DU; or a division in a certain protocol layer, such as a division in which part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are arranged in the DU. In addition, other divisions are also possible, such as a division according to a delay requirement, with the functions that need to meet the delay requirement being arranged in the DU, and the functions that do not need to meet the delay requirement being arranged in the CU.

[0089] In addition, the radio frequency device can be independently integrated, and is not necessarily arranged in the DU, or can be integrated in the DU, or part of the radio frequency device is integrated in the DU and part of the radio frequency device is pulled away, and no limitation is made herein.

[0090] FIG. 4 is a schematic diagram of another network architecture to which the embodiments of the present application are applicable. In the network architecture shown in FIG. 4, the control plane (CP) and the user plane (UP) of the CU can be separated and implemented by different entities, namely, a control plane (CP) CU entity (namely, a CU-CP entity) and a user plane (UP) CU entity (namely, a CU-UP entity).

[0091] In the above network architecture, the signaling generated by the CU can be transmitted to the terminal device through the DU, or the signaling generated by the terminal device can be transmitted to the CU through the DU. The DU can directly transmit the signaling to the terminal device or the CU through protocol layer encapsulation without analyzing the signaling. In the following embodiments, if the transmission of the signaling between the DU and the terminal device is involved, the transmission or reception of the signaling by the DU includes this scenario. For example, the signaling of the RRC or PDCP layer is finally processed as the signaling of the PHY layer and transmitted to the terminal device, or is converted from the received signaling of the PHY layer. In this architecture, the signaling of the RRC or PDCP layer can also be considered as being transmitted by the DU, or being transmitted by the DU and the radio frequency device.

[0092] In yet some deployments of the network device, the network device can also be an open radio access network (ORAN) architecture. When the network device is an ORAN architecture, the network device can be a functional entity or module, etc. in the ORAN. For example, the network device can be a combination of one or more of a CU, a DU, or a RU. In the ORAN system, the CU can also be referred to as an open (O)-CU, the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, etc. The deployment manners of the network device listed herein are only examples, and as the standard technology evolves, there can be other deployment forms of the network device, which are not limited by the embodiments of the present application.

[0093] In some deployments, wireless access can be assisted by a plurality of RAN nodes to assist terminals, and different RAN nodes respectively implement part of the functions of the access network. For example, the RAN node can be a CU, a DU, a CU-CP, a CU-UP, or a RU, etc. The CU and the DU can be separately arranged, or can also be included in the same network element, such as an indoor base band unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0094] The RAN node can support one or more types of fronthaul interfaces, different fronthaul interfaces respectively corresponding to DUs and RUs having different functions. If the fronthaul interface between the DU and the RU is a common public radio interface (CPRI), the DU is configured to implement one or more of the baseband functions, and the RU is configured to implement one or more of the radio frequency functions. If the fronthaul interface between the DU and the RU is another interface, relative to the CPRI, one or more of the partial baseband functions of the downlink and / or uplink, such as, for the downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / adding cyclic prefix (CP), is moved from the DU to the RU for implementation, and for the uplink, one or more of digital beamforming, or one or more of fast Fourier transform (FFT) / removing cyclic prefix (CP) is moved from the DU to the RU for implementation. In a possible implementation, the interface can be an enhanced common public radio interface (eCPRI). Under the eCPRI architecture, the splitting manner between the DU and the RU is different, corresponding to different categories (Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, F.

[0095] Taking the eCPRI Cat A as an example, for downlink transmission, the splitting is layer mapping, the DU is configured to implement one or more of the functions before the layer mapping (i.e., one or more of encoding, rate matching, scrambling, modulation, and layer mapping), and other functions after the layer mapping (e.g., one or more of resource element (RE) mapping, digital beamforming, or IFFT / adding CP) are moved to the RU for implementation. For uplink transmission, the splitting is RE demapping, the DU is configured to implement one or more of the functions before the demapping (i.e., one or more of decoding, de-rate matching, de-scrambling, de-modulation, inverse discrete Fourier transform (IDFT), channel equalization, and RE demapping), and other functions after the demapping (e.g., one or more of digital BF or FFT / removing CP) are moved to the RU for implementation. It can be understood that the function description of the DU and the RU corresponding to various types of eCPRI can refer to the eCPRI protocol, and will not be described here.

[0096] In a possible design, a processing unit in the BBU for implementing baseband functions is referred to as a base band high (BBH) unit, and a processing unit in the RRU / AAU / RRH for implementing baseband functions is referred to as a base band low (BBL) unit.

[0097] In different systems, the CU (or CU-CP and CU-UP), DU, or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0098] The network device and / or the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed on aircraft, balloons, and satellites in the air. The scenario in which the network device and the terminal device are located is not limited in the embodiments of this application. In addition, the terminal device and the network device can be hardware devices, or software functions running on special-purpose hardware, general-purpose hardware, such as virtualized functions instantiated on a platform (for example, a cloud platform), or entities including special-purpose or general-purpose hardware devices and software functions. The specific form of the terminal device and the network device is not limited in this application.

[0099] In the embodiments of this application, the apparatus for implementing the function of the network device can be a network device, or an apparatus capable of supporting the network device to implement the function, such as a chip system. The apparatus can be installed in the network device or used in matching with the network device. For ease of description, the apparatus for implementing the function of the network device is taken as a base station to describe the technical solutions provided in the embodiments of this application when some specific examples are involved.

[0100] The professional terms involved in the embodiments of this application are explained as follows:

[0101] 1. New radio (NR) protocol architecture:

[0102] The NR protocol architecture involved in the embodiments of this application can be divided into a user plane protocol stack and a control plane protocol stack. The two protocol stacks will be described in detail below in combination with FIG. 5. FIG. 5 is described by taking the interaction between a terminal device and a base station as an example. (a) of FIG. 5 shows the user plane protocol stack, and (b) of FIG. 5 shows the control plane protocol stack.

[0103] User plane protocol stack: protocol cluster adopted by user data transmission. As shown in (a) of FIG. 5, the user plane protocol stack can include five layers of PHY layer, MAC layer, RLC layer, PDCP layer and SDAP layer.

[0104] Control plane protocol stack architecture: protocol cluster adopted by control signaling transmission of the system. As shown in (b) of FIG. 5, the control plane protocol stack can include non-access-stratum (NAS), RRC, PDCP, RLC, MAC, PHY layers.

[0105] For example, the PHY layer can be responsible for one or more of coding and decoding, modulation and demodulation, multi-antenna mapping and other physical layer functions. For example, the MAC layer can be responsible for one or more of hybrid automatic repeat request (HARQ), uplink scheduling, downlink scheduling, discontinuous reception (DRX), packet grouping, logical channel prioritization (LCP), multiplexing and assembly, etc. For example, the RLC layer can be responsible for one or more of segmentation, reassembly and retransmission processing, etc. For example, the PDCP layer can be responsible for one or more of header compression / decompression, security (encryption function, integrity protection function), retransmission and in-sequence delivery, etc. For example, the RRC layer can be responsible for one or more of broadcast, paging, RRC connection management, radio bearer control, mobility management, terminal device measurement reporting and control, etc. For example, the NAS layer can be responsible for one or more of identity authentication, mobility management, security control, etc.

[0106] Compared with the long term evolution (LTE) protocol stack, the NR protocol stack has an additional SDAP layer for the user plane protocol stack. The NR protocol stack is similar to the LTE protocol stack for the control plane protocol stack.

[0107] Optionally, in the embodiments of the present application, each layer in the protocol stack can also be replaced by an entity. For example, the PDCP layer can be replaced by a PDCP entity, and the SDAP layer can be replaced by an SDAP entity. A unified description is made here and will not be repeated later.

[0108] 2、Protocol data unit (PDU) and service data unit (SDU):

[0109] In each protocol layer (e.g., any one or more of SDAP, RRC, PDCP, RLC, MAC), the SDU of the Nth layer and the PDU of the last layer (e.g., the (N+1)th layer) are corresponding. For example, N is a positive integer. In other words, the PDU of the current layer is the SDU of the lower layer, and the SDU of the current layer is the PDU of the upper layer.

[0110] The relationship between the PDU and the SDU will be described in detail below in conjunction with FIG. 6 taking the interaction between the terminal device and the network device as an example.

[0111] FIG. 6 is a schematic diagram of the relationship between the PDU and the SDU of the protocol layer provided by the embodiments of the present application. As shown in FIG. 6, for the sending end, after the RRC layer generates the signaling (e.g., RRC message or RRC PDU) to be transmitted, or after the SDAP layer obtains the data to be transmitted, the signaling or the data can be submitted to the corresponding PDCP layer. For the convenience of description, the signaling is referred to as / alternatively replaced by the data in the following; for the data (e.g., PDCP SDU) received from the RRC layer or the SDAP layer, the PDCP layer can obtain the PDCP PDU after a certain processing or without processing, and then submit the PDCP PDU to the RLC layer corresponding to the PDCP layer; for the data (e.g., RLC SDU) received from the PDCP layer, the RLC layer can obtain the RLC PDU after a certain processing or without processing, and then submit the RLC PDU to the corresponding MAC layer; for the data (e.g., MAC SDU) received from the RLC layer, the MAC layer can obtain the MAC PDU after a certain processing or without processing, and then submit the MAC PDU to the PHY layer; the PHY layer can perform air interface transmission after a certain processing or without processing.

[0112] Correspondingly, for the receiving end, after the PHY layer receives data (e.g., a transport block (TB)), the data is delivered to the MAC layer; for the data (e.g., a TB or a MAC PDU) received from the PHY, the MAC layer can obtain a MAC SDU after certain processing or without processing, and then deliver the MAC SDU to the corresponding RLC layer; for the data (e.g., an RLC PDU) received from the MAC layer, the RLC layer can obtain an RLC SDU after certain processing or without processing, and then deliver the RLC SDU to the corresponding PDCP layer; for the data (e.g., a PDCP PDU) received from the RLC layer, the PDCP layer can obtain a PDCP SDU after certain processing or without processing, and then deliver the PDCP SDU to the RRC layer or the SDAP layer; for the data (e.g., an RRC message or an RRC PDU) received from the PDCP layer, which can also be referred to as signaling, the RRC layer performs RRC decoding or ASN.1 decoding to determine the meaning of the received data; or, for the data (e.g., an SDAP PDU) received from the PDCP layer, the SDAP layer can obtain an SDAP SDU after certain processing or without processing, and then deliver the SDAP PDU to an upper layer (e.g., an application (APP) layer or an internet protocol (IP) layer).

[0113] For transmission and reception of data (or signaling), data can be encapsulated / processed or transparently passed in various layers. For example, for a transmitting end, data received from an upper layer of a certain layer is referred to as a SDU, and data delivered to a lower layer of the certain layer is referred to as a PDU, and the data received from the upper layer and the data delivered to the lower layer can be the same (e.g., transparently passed) or different (e.g., the data received from the upper layer is encapsulated / processed by the certain layer to obtain the data delivered to the lower layer). For example, data received by a PDCP layer from an upper layer is referred to as a PDCP SDU, and data transmitted by the PDCP layer to a lower layer is referred to as a PDCP PDU; data received by an RLC layer from an upper layer is referred to as an RLC SDU, and data transmitted by the RLC layer to a lower layer is referred to as an RLC PDU; data received by a MAC layer from an upper layer is referred to as a MAC SDU, and data transmitted by the MAC layer to a lower layer is referred to as a MAC PDU or TB. For example, for a receiving end, data received from a lower layer of a certain layer is referred to as a PDU, and data delivered to an upper layer of the certain layer is referred to as a SDU, and the data received from the lower layer and the data delivered to the upper layer can be the same (e.g., transparently passed) or different (e.g., the data received from the lower layer is processed by the certain layer to obtain the data delivered to the upper layer). For example, data received by a PDCP layer from a lower layer is referred to as a PDCP PDU, and data transmitted by the PDCP layer to an upper layer is referred to as a PDCP SDU; data received by an RLC layer from a lower layer is referred to as an RLC PDU, and data transmitted by the RLC layer to an upper layer is referred to as an RLC SDU; data received by a MAC layer from a lower layer is referred to as a MAC PDU or TB, and data transmitted by the MAC layer to an upper layer is referred to as a MAC SDU.

[0114] In the embodiments of the present application, the upper layer and the lower layer are a relative concept. For example, for an RRC layer, an RLC layer can be a lower layer of the RRC layer, but for a MAC layer, the RLC layer can be an upper layer of the MAC layer. For another example, a lower layer of a PDCP layer can include any one or more of the following: a PHY layer, a MAC layer, an RLC layer. For another example, an upper layer of the PDCP layer can include any one or more of the following: an RRC layer, an SDAP layer, an IP layer, an APP layer.

[0115] For the PDCP layer, a PDU can be classified into two types: data PDU and control PDU. The PDCP data PDU can carry control plane data and / or user plane data. The PDCP control PDU can mainly carry any one or more of robust header compression (ROHC) feedback, ethernet header compression (EHC) feedback, PDCP status report, and PDCP SN gap report.

[0116] For example, FIG. 7 and FIG. 8 are schematic diagrams of structures of PDCP PDUs according to embodiments of the present application.

[0117] (a) of FIG. 7 shows a PDCP data PDU format of a signaling radio bearer (SRB). (b) of FIG. 7 shows a PDCP data PDU format of a data radio bearer (DRB) with 12 bits PDCP SN. (c) of FIG. 7 shows a PDCP data PDU format of a DRB with 18 bits PDCP SN.

[0118] For a transmitting end, for data (e.g., PDCP SDU) received from a SDAP layer or a RRC layer, the PDCP layer can process (e.g., any one or more of header compression, ciphering, integrity protection, adding a PDCP PDU header) or not process the data to obtain a PDCP PDU.

[0119] For example, a PDCP PDU can include at least one of the following information (or, field): SN, reserved bit R, D / C, data, message authentication code for integrity (MAC-I).

[0120] For example, the SN field can be used to indicate information of a SN of a PDCP PDU or a PDCP SDU. For example, the SN field can have a bit number (or, a number of bits occupied) of 12 bits, or 18 bits.

[0121] For example, the R field is a reserved bit.

[0122] For example, the D / C field can be used to indicate whether the PDCP PDU is a PDCP data PDU or a PDCP control PDU. For example, the number of bits (or, the number of bits occupied) of the D / C field can be 1 bit. For example, the D / C field has a first value to indicate that the PDCP PDU is a PDCP data PDU, and the D / C field has a second value to indicate that the PDCP PDU is a PDCP control PDU. For example, the first value is 1, and the second value is 0; or, the first value is 0, and the second value is 1.

[0123] For example, the data field can include any one or more of the following: a PDCP service data unit (SDU), a compressed PDCP SDU, and an uncompressed PDCP SDU. For example, the data can be denoted as Data. For example, the data field can be denoted as a Data field. It should be noted that the data in the data field can be encrypted or not encrypted. For example, any one or more of the PDCP SDU, the compressed PDCP SDU, and the uncompressed PDCP SDU can include user plane data and / or control plane data. For example, the number of bits (or, the number of bits occupied) of the data field can be variable. For example, the number of bits (or, the number of bits occupied) of the data field can be X bytes, or 8 times Y bits, where X and / or Y can be a positive integer.

[0124] For example, the MAC-I field can be used for integrity protection. For example, the number of bits (or, the number of bits occupied) of the MAC-I field can be 32 bits.

[0125] A PDCP control PDU format for a PDCP SN gap report is shown in FIG. 8.

[0126] For example, the control PDU can include at least one of the following information (or, field): D / C, a reserved bit R, a PDU type (Type), a FDC, or a discard bitmap.

[0127] For example, the D / C field can be used to indicate whether the PDCP PDU is a PDCP data PDU or a PDCP control PDU. For example, the number of bits (or, the number of bits occupied) of the D / C field can be 1 bit. For example, the D / C field has a first value to indicate that the PDCP PDU is a PDCP data PDU, and the D / C field has a second value to indicate that the PDCP PDU is a PDCP control PDU. For example, the first value is 1, and the second value is 0; or, the first value is 0, and the second value is 1.

[0128] For example, the R field is a reserved bit.

[0129] For example, the PDU Type field can be used to indicate the type of control information in the PDCP control PDU. For example, the PDU Type field can have a bit number (or, a number of bits occupied) of 3 bits. For example, when the PDU Type field has a value / bit of “100”, it indicates that the type of control information in the PDCP control PDU is a PDCP SN gap report or that the PDCP control PDU is for the PDCP SN gap report.

[0130] For example, the FDC field can be used to indicate the minimum value in the COUNT values related to the discarded PDCP SDUs or PDCP PDUs. For example, the first discarded COUNT is indicated. For example, the FDC field can have a bit number (or, a number of bits occupied) of 32 bits.

[0131] For example, the discard bitmap field indicates which SDUs or PDUs in the sending PDCP entity are discarded and which SDUs or PDUs are not discarded. For example, the discard bitmap field can have a variable bit number (or, a number of bits occupied). For example, the discard bitmap field can have a bit number (or, a number of bits occupied) of 0.

[0132] 3. PDCP Related Content:

[0133] For example, the COUNT can be used for one or more of the following functions: integrity protection and integrity check, ciphering and deciphering, header compression and decompression, in-sequence delivery, duplicate discard. For example, the sending end uses the COUNT to encrypt a data packet, and then sends the encrypted data packet to the receiving end, which needs to decrypt the data packet according to the COUNT. It should be understood that, in general, one PDCP PDU is associated with one COUNT. For example, the COUNT can have a bit number of 32 bits. As shown in FIG. 9, the COUNT can include two parts: a high-bit hyper frame number (HFN) and a low-bit PDCP sequence number (SN). The bit number of the PDCP SN is configured by an upper layer (for example, an RRC layer) or a network device, and the bit number of the HFN changes with the bit number of the PDCP SN. For example, the bit number of the PDCP SN can be 12 bits or 18 bits, and accordingly, the bit number of the HFN can be (32-PDCP SN size) bits, where the PDCP SN size is the bit number of the PDCP SN. For example, if the PDCP SN size is 12 bits, the bit number of the HFN is (32-12) bits, i.e., 20 bits.

[0134] To avoid air interface overhead, the complete COUNT is not included in the PDCP PDU, only the lower bit of the COUNT (i.e. the SN) is included.

[0135] For example, RCVD_HFN: HFN of the received PDCP data PDU calculated by the receiving PDCP entity.

[0136] For example, RCVD_SN: PDCP SN of the received PDCP data PDU, included in the PDU header.

[0137] For example, RCVD_COUNT: COUNT value of the received PDCP data PDU = [RCVD_HFN, RCVD_SN].

[0138] For example, reordering window can include / replace: receiving window, or, PDCP window, or, PDCP receiving window.

[0139] For example, RX_DELIV is a state variable indicating the COUNT value of the first PDCP SDU not delivered to upper layers but still pending. For example, the initial value of RX_DELIV can be 0. For example, RX_DELIV can also be understood as the lower limit of the reordering window.

[0140] For example, RX_NEXT is a state variable indicating the COUNT value of the next PDCP SDU expected to be received. For example, the initial value of RX_NEXT is 0.

[0141] For example, RX_REORD is a state variable indicating the COUNT value following the COUNT value associated with the PDCP data PDU that triggered t-Reordering.

[0142] For example, t-Reordering: also called reordering timer, used to detect loss of PDCP data PDUs. For example, t-Reordering should not be started in addition if t-Reordering is already running. One receiving PDCP entity cannot start multiple t-Reordering at the same time; or, at a given time, one receiving PDCP entity only runs one t-Reordering. Optionally, the length of t-Reordering is configured by RRC layer or network equipment.

[0143] 3.1, Operation after receiving a PDCP data PDU:

[0144] The receiving end (e.g., the receiving PDCP entity) needs to calculate the HFN after receiving the PDCP data PDU to obtain the COUNT. For example, the method for the receiving end (e.g., the receiving PDCP entity) to calculate the HFN can include any one or more of the following:

[0145] (1) If the PDCP SN of the PDCP data PDU < (the SN part of RX_DELIV - the size of the reordering window), the HFN of the PDCP data PDU = the HFN part of RX_DELIV + 1; or,

[0146] (2) If the PDCP SN of the PDCP data PDU >= (the SN part of RX_DELIV + the size of the reordering window), or, if the PDCP SN of the PDCP data PDU >= (the SN part of RX_DELIV - the size of the reordering window) and the PDCP SN of the PDCP data PDU >= (the SN part of RX_DELIV + the size of the reordering window), the HFN of the PDCP data PDU = the HFN part of RX_DELIV - 1; or,

[0147] (3) If the PDCP SN of the PDCP data PDU >= (the SN part of RX_DELIV - the size of the reordering window) and / or, the PDCP SN of the PDCP data PDU < (the SN part of RX_DELIV + the size of the reordering window), the HFN of the PDCP data PDU = the HFN part of RX_DELIV.

[0148] For example, the size of the reordering window is equal to 2 (X-1) , X represents the number of bits corresponding to the SN. For example, RX_DELIV indicates the COUNT of the first PDCP SDU that has not been delivered to the upper layer but is still waiting. For example, the initial value of RX_DELIV is 0. In addition, ">=" means greater than or equal to.

[0149] The receiving end (e.g., the receiving PDCP entity) determines the COUNT of the PDCP data PDU according to the calculated PDCP HFN of the PDCP data PDU and the PDCP SN of the PDCP data PDU, which can be referred to as RCVD_COUNT.

[0150] For example, after the receiving end (e.g., the receiving PDCP entity) determines the COUNT of the PDCP data PDU, any one or more of the following can be performed:

[0151] (1) Perform decryption and integrity verification of the PDCP data PDU using COUNT = RCVD_COUNT; if the integrity verification fails: indicate the integrity verification failure to the upper layer (e.g., the RRC layer), and / or, discard the PDCP data PDU; or,

[0152] (2) If RCVD_COUNT < RX_DELIV; or, if a PDCP Data PDU with COUNT = RCVD_COUNT has been received before: discard the PDCP Data PDU.

[0153] If the received PDCP Data PDU with COUNT = RCVD_COUNT is not discarded after the above judgment, the receiving end (e.g., the receiving PDCP entity) can perform one or more of the following operations:

[0154] Operation (2.1) stores the resulting PDCP SDU in the receiving buffer; or,

[0155] Operation (2.2) if RCVD_COUNT >= RX_NEXT, updates RX_NEXT to RCVD_COUNT + 1; or,

[0156] Operation (2.3) if RCVD_COUNT = RX_DELIV, delivers all stored PDCP SDUs with consecutive associated COUNT values starting from COUNT = RX_DELIV to upper layers in ascending order of COUNT values (optionally, after performing header decompression if not decompressed before); and / or; updates RX_DELIV to the COUNT value of the first PDCP SDU that has not been delivered to upper layers, and the COUNT value of the first PDCP SDU > RX_DELIV; or,

[0157] Operation (2.4) if t-Reordering is running, and RX_DELIV >= RX_REORD, stops (or, stops and resets) t-Reordering; or,

[0158] Operation (2.5) if t-Reordering is not running (including the case where t-Reordering is stopped due to operation (2.4) above), and RX_DELIV < RX_NEXT, updates RX_REORD to RX_NEXT, and starts t-Reordering.

[0159] For example, referring to the above operations (2.1) to (2.5), it can be seen that the storing of the received PDCP PDU in the buffer by the receiving end in operation (2.1) has an impact on the in-sequence delivery and / or RX_DELIV update in operation (2.3).

[0160] 3.2, Operation of t-Reordering Timeout:

[0161] If t-Reordering expires, the receiving side (e.g., receiving PDCP entity) can perform one or more of the following operations:

[0162] Operation (1) If header decompression has not been performed before, after performing header decompression, deliver to upper layers the following PDCP SDUs in ascending order of COUNT of PDCP SDUs in the buffer: all stored PDCP SDUs with associated COUNT < RX_REORD, and / or all stored PDCP SDUs with consecutive associated COUNTs starting from RX_REORD; or,

[0163] Operation (2) Update RX_DELIV to the COUNT of the first PDCP SDU not yet delivered to upper layers, and the COUNT of the first PDCP SDU >= RX_REORD; or,

[0164] Operation (3) If RX_DELIV < RX_NEXT, update RX_REORD to RX_NEXT and start t-Reordering.

[0165] For example, after the receiving side (e.g., receiving PDCP entity) receives a PDCP PDU, the receiving side (e.g., receiving PDCP entity) first determines the COUNT of the PDCP PDU, and determines whether to discard the PDCP PDU according to the COUNT of the PDCP PDU. If the receiving side (e.g., receiving PDCP entity) determines not to discard the PDCP PDU, the receiving side (e.g., receiving PDCP entity) further performs reordering process according to the relationship between the COUNT of the PDCP PDU and the state variables (e.g., RX_NEXT and / or RX_DELIV). In the reordering process, the state variables can be updated and / or data can be delivered.

[0166] 3.3 Operation upon receiving a PDCP SN gap report (or a PDCP control PDU for PDCP SN gap report):

[0167] If the receiving side (e.g., receiving PDCP entity) receives a PDCP SN gap report from the transmitting side (e.g., transmitting PDCP entity), the receiving side (e.g., receiving PDCP entity) can perform one or more of the following operations:

[0168] Operation (1) Consider the PDCP SDUs or COUNT values with bit positions of "1" in each discard bitmap in the PDCP SN gap report as discarded.

[0169] Operation (2) If RX_DELIV is less than or equal to the maximum COUNT value associated with the discarded PDCP SDUs (e.g., the maximum COUNT value associated with the discarded PDCP SDUs refers to the maximum COUNT value among COUNT values of the discarded one or more PDCP SDUs), perform at least one of the following:

[0170] Operation (2.1) If RX_NEXT <= the COUNT value associated with the last discarded PDCP SDU indicated in the PDCP SN gap report (or, if RX_NEXT <= the maximum COUNT value associated with the discarded PDCP SDUs), update RX_NEXT to the maximum COUNT value associated with the discarded PDCP SDUs + 1. In addition, "<=" means less than or equal to.

[0171] Operation (2.2) If RX_DELIV is equal to the COUNT value of one PDCP SDU among the discarded one or more PDCP SDUs, deliver to upper layers in ascending order of associated COUNT values after performing header decompression (if not decompressed before): all stored one or more PDCP SDUs with consecutive associated COUNT values starting from COUNT = RX_DELIV + 1, wherein the consecutive associated COUNT values include COUNT values of the stored PDCP SDUs and the PDCP SDU regarded as discarded; and, update RX_DELIV to the COUNT value of the first PDCP SDU not delivered to upper layers and not regarded as discarded, and COUNT value > RX_DELIV.

[0172] Operation (2.3) If t-Reordering is running, and RX_DELIV >= RX_REORD, stop (or, stop and reset) t-Reordering.

[0173] Operation (2.4) If t-Reordering is not running (including the case that t-Reordering is stopped due to operation (2.3) above), and RX_DELIV < RX_NEXT, update RX_REORD to RX_NEXT, and start t-Reordering.

[0174] It should be noted that the PDCP related content can refer to 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) protocol specification", which will not be repeated here.

[0175] For example, the time length of the reordering timer can be matched (or, equivalent) with the time delay requirement of the data, for example, the time length of the reordering timer is equal to (or, approximately equal to) the time delay requirement of the data (for example, 10 milliseconds). For example, in some cases, the time when the reordering timer starts can be later than the start time of the time delay statistics of the data, which can cause the situation that the data has exceeded its time delay requirement but has not been submitted to the upper layer if the data is submitted to the upper layer according to the reordering timer. Therefore, how to avoid the situation that the data is not submitted before the time delay expires (or, how to avoid the situation that the data is submitted after the time delay expires, or, how to ensure that the data is submitted before / when the time delay expires) is a technical problem to be solved. For example, the start time of the time delay statistics of the data can be the data generation time. Since the data is generated, it cannot be immediately sent to the receiving end, for example, it can need to be retransmitted by HARQ to reach the receiving end. Therefore, the time when the reordering timer starts will be later than the start time of the time delay statistics of the data, and the time delay expiration time of the data will be before the retransmission timer expires, thereby causing the situation that the data expires but has not been submitted to the upper layer.

[0176] For example, as shown in FIG. 10, at T1, RX_DELIV of the receiving end is 1, RX_NEXT is 1, the sending end generates data 1 and data 2 at T1, the count value of data 1 is 1, and the count value of data 2 is 2. Then, the sending end sends data 1 at T2 and sends data 2 at T3. After one or more times of HARQ retransmission, the receiving end receives data 2 at T4, but has not received data 1. After receiving data 2, the receiving end updates RX_NEXT to 3 (i.e., the count value 2 of data 2+1), and RX_DELIV is still equal to 1. In this case, the reordering timer is not running, and RX_DELIV is less than RX_NEXT. Therefore, the receiving end starts the reordering timer. The receiving end has not received data 1, and the reordering timer expires at T5. The time length of the reordering timer is time length 1, which is the time length between T4 and T5. If the time delay requirement of the data (for example, data 1 and / or data 2) is equal to the time length of the reordering timer (time length 1), but the start time of the time delay statistics of data 2 is from T1, the time delay expiration time of data 2 is before T5 (or, before T5, the time delay of data 2 has expired). If data 2 is submitted at T5 (or, after the reordering timer expires, or, after the time delay of the data has expired), it will affect the service reliability and the service / user experience.

[0177] For example, in the present application, PDCP can include / replace: the first layer, or the first protocol layer.

[0178] For example, in the present application, PDCP layer can include / replace: the first layer, or the first protocol layer.

[0179] For example, in this application, a PDCP entity can include / replace a first layer entity, or a first protocol layer entity.

[0180] For example, in this application, a PDCP PDU can include / replace a first layer PDU, or a first protocol layer PDU.

[0181] For example, in this application, a PDCP SDU can include / replace a first layer SDU, or a first protocol layer SDU.

[0182] For example, in this application, a PDCP data PDU can include / replace a first layer data PDU, or a first protocol layer data PDU.

[0183] For example, in this application, a PDCP header can include / replace a first layer header, or a first protocol layer header.

[0184] For example, in this application, a PDCP header can include / replace a first layer header, or a first protocol layer header.

[0185] For example, in this application, a PDCP SN can include / replace a first layer SN, or a first protocol layer SN.

[0186] For example, in this application, a PDCP window can include / replace a first layer window, or a first protocol layer window.

[0187] For example, in this application, a PDCP receive window can include / replace a first layer receive window, or a first protocol layer receive window.

[0188] For example, in this application, a PDCP control PDU can include / replace a first layer control PDU, or a first protocol layer control PDU.

[0189] For example, in this application, a PDCP HFN can include / replace a first layer HFN, or a first protocol layer HFN.

[0190] For example, in this application, a PDCP status variable can include / replace a first layer status variable, or a first protocol layer status variable.

[0191] For example, in this application, a PDCP status report can include / replace a first layer status report, or a first protocol layer status report.

[0192] For example, in this application, a PDCP SN gap report can include / replace a first layer SN gap report, or a first protocol layer SN gap report.

[0193] For example, in this application, the COUNT value can include / replace: SN, or, sequence number, or, number, or, index.

[0194] For example, in this application, the COUNT value can include / replace: SN, or, sequence number, or, number, or, index.

[0195] For example, the first layer or the first protocol layer can be / include / replace: RLC layer, or, new protocol layer, or other, without limiting the name.

[0196] For example, the first layer or the first protocol layer can be responsible for (or have functions including) one or more of: segmentation, re-segmentation, recombination, retransmission (e.g., ARQ retransmission), compression / decompression (e.g., header compression / decompression), security (e.g., encryption / decryption functions and / or integrity protection / integrity check functions), retransmission (e.g., handover retransmission), data recovery, dual connectivity, carrier aggregation, data discard (e.g., SDU discard), reordering, or in-sequence delivery, etc.

[0197] In order to avoid data timeout without delivery (or, to avoid data timeout or delivery after timeout, or, to ensure that data is delivered in time before / when the delay timeout), an embodiment of the present application proposes a communication method, as shown in FIG. 11, which includes steps 1101-1102. The method is illustrated by taking the first device and the second device as an example. Of course, the subject performing the action of the first device in the method can also be a device / module in the first device, such as a chip, processor, or processing unit in the first device, and the subject performing the action of the second device in the method can also be a device / module in the second device, such as a chip, processor, or processing unit in the second device, and the embodiment of the present application does not limit the subject performing the communication method. For example, the first device can be a terminal device or a network device. For example, the second device can be a terminal device or a network device.

[0198] For example, in an embodiment of the present application, the first device can include / replace: the first equipment, which is uniformly described here and will not be described again in the following.

[0199] For example, in an embodiment of the present application, the second device can include / replace: the second equipment, which is uniformly described here and will not be described again in the following.

[0200] 1101, the first device acquires first information.

[0201] For example, the first information includes information of the time delay expiration time of the first data.

[0202] For example, the time delay expiration time can include / replace: time 1.

[0203] For example, the time delay expiration time of the first data can comprise / replace: time 1 of the first data, or, time 1.

[0204] Optionally, the time 1 or the time 1 of the first data or the data time 1 is associated with performing state variable updating and / or submitting the at least one data.

[0205] Optionally, the first device obtaining the first information can comprise / replace: the first device obtaining the first data. Optionally, the first information is carried / comprised in the first data.

[0206] For example, the obtaining can comprise / replace: receiving.

[0207] For example, the first device obtaining the first data can comprise / replace: the first device obtaining the first data from the second device, or, the first device obtaining the first data from a lower layer.

[0208] For example, the lower layer can comprise / replace: a lower layer of the first device, or, a lower layer of a PDCP layer of the first device, or, an RLC layer, or, a MAC layer, or, a PHY layer.

[0209] Optionally, the first data is sent by the second device. For example, the second device is a sending end, and the first device is a receiving end. Or, for example, the first device is a receiving PDCP entity, and the second device is a sending PDCP entity.

[0210] For example, the first device is a terminal device, and the second device is a network device. Or, for example, the first device is a network device, and the second device is a terminal device. Or, for example, the first device is a terminal device, and the second device is a terminal device. Or, for example, the first device is a network device, and the second device is a network device.

[0211] Optionally, the first data can comprise / replace: a PDCP PDU, or a PDCP data PDU, or, a PDCP SDU.

[0212] For example, the first data carrying / comprising the first information can comprise / replace: the first data carrying / comprising the first information in a header of the first data. For example, the header can comprise / replace: a PDCP header, or, a PDCP header.

[0213] Optionally, the first information can be carried in a first field. For example, the first information can be carried in a first field in the first data. For example, the embodiments of the present application do not limit the name of the first field.

[0214] For example, the first field comprises / is used to indicate information of a time delay expiration time of the first information / data.

[0215] For example, the time delay expiration time of the data can comprise / replace: a time 1 of the data, or a time 1.

[0216] For example, the format of the first data can be as shown in FIG. 12, where (a) of FIG. 12 shows a PDCP PDU format of 12 bits PDCP SN, and (b) of FIG. 12 shows a PDCP PDU format of 18 bits PDCP SN. For example, the PDCP PDU comprises a first field. For example, the first field occupies 8 bits. Other fields comprised in the PDCP PDU can refer to the foregoing description, and will not be described herein. It should be understood that FIG. 12 is only an example, and the embodiments of the present application do not limit the number of bits occupied by the first field, the position of the first field in the PDCP PDU, and the order of the fields in the PDCP PDU.

[0217] In some other examples, the first information can also be carried on a message other than the first data, or sent by another device, for example, a network device. The embodiments of the present application do not limit the message carrying the first information, and the device sending the first information.

[0218] Optionally, the first information comprising the time delay expiration time of the first data can comprise / replace: the first information is the time delay expiration time of the first data, or the first information comprises information used to determine the time delay expiration time of the first data. For example, the first information comprises / is the information of the generation time of the first data, and the first device can determine the time delay expiration time of the first data according to the information of the generation time of the first data, or the first device can determine the time delay expiration time of the first data according to the information of the generation time of the first data and the information of the time delay requirement of the first data.

[0219] Optionally, the information of the time delay expiration time of the first data can comprise / replace: information of a time unit in which the time delay expiration time of the first data is located.

[0220] Optionally, the time delay expiration time of the first data can comprise / replace: a time unit in which the time delay expiration time of the first data is located.

[0221] Optionally, the information of the generation time of the first data can comprise / replace: information of a time unit in which the generation time of the first data is located.

[0222] Optionally, the generation time of the first data can comprise / replace: a time unit in which the generation time of the first data is located.

[0223] For example, the time unit can include / replace at least one of: a superframe, a frame, a subframe, a time slot, a mini-slot, or a symbol.

[0224] For example, the location can include / replace: a belonging, or an association.

[0225] For example, the first field can include / replace one or more fields. For example, the first field can include / replace: an SFN field and / or a subframe field. For example, the names of the SFN field and the subframe field can be replaced by others, such as field 1, field 2, etc., without limitation.

[0226] For example, the SFN field is used to represent information of a system frame number (SFN) in which a time delay expiration time of the first data (or a generation time of the first data) is located.

[0227] For example, the subframe field is used to represent information of a subframe in which the time delay expiration time of the first data (or the generation time of the first data) is located.

[0228] For example, taking the first data as a PDCP PDU as an example, the format of the first data can be as shown in FIG. 13. (a) of FIG. 13 shows a PDCP PDU format of a 12-bit PDCP SN. (b) of FIG. 13 shows a PDCP PDU format of an 18-bit PDCP SN. For example, the PDCP PDU includes an SFN field, a subframe field. For example, the SFN field occupies 10 bits, and the subframe field occupies 4 bits. For other fields included in the PDCP PDU, refer to the foregoing description, which is not repeated here. It should be understood that FIG. 13 is only an example, and the embodiments of the present application do not limit the number of bits occupied by the SFN field and the subframe field, the positions of the SFN field and the subframe field in the PDCP PDU, and the order of the fields in the PDCP PDU.

[0229] For example, the generation time can include / replace: time 2.

[0230] For example, the generation time of the first data can include / replace: time 2 of the first data, or time 2.

[0231] Optionally, time 2 or time 2 of the first data or data time 2 is associated with performing state variable updating and / or submitting at least one data.

[0232] For example, the time can be understood as: a time point, or a time, or a time period, without limitation.

[0233] For example, the time delay expiration time of the first data can comprise / replace: a time delay expiration time associated with the first data (e.g., a time delay expiration time associated with the first data set of the first data).

[0234] Optionally, the time delay expiration time of the first data set associated with the first data can comprise / replace: a time delay expiration time of one or more data (e.g., the first data, or one or more data in the first data set other than the first data) in the first data set; or, a time delay expiration time of the first data in the first data set. Optionally, the first data is the first data in the first data set, or the first data is not the first data in the first data set (e.g., the count value of the first data is greater than or equal to the count value of the first data in the first data set). For example, the application does not limit the time delay expiration time of the first data to be the time delay expiration time of the first data itself.

[0235] For example, the generation time of the first data can comprise / replace: a generation time associated with the first data (e.g., a generation time associated with the first data set of the first data).

[0236] Optionally, the generation time of the first data set associated with the first data can comprise / replace: a generation time of one or more data (e.g., the first data, or one or more data in the first data set other than the first data) in the first data set; or, a generation time of the first data in the first data set. Optionally, the first data is the first data in the first data set, or the first data is not the first data in the first data set (e.g., the count value of the first data is greater than or equal to the count value of the first data in the first data set). For example, the application does not limit the generation time of the first data to be the generation time of the first data itself.

[0237] For example, the time delay requirement of the first data can comprise / replace: a time delay requirement associated with the first data (e.g., a time delay requirement associated with the first data set of the first data); or, a time delay requirement associated with the first PDCP entity, or a time delay requirement associated with the first RB, or a time delay requirement of the first service. For example, the first service is associated with the first data.

[0238] Optionally, the time delay requirement of the first data set of the first data association can comprise / replace: the time delay requirement of one or more data (e.g., the first data, or one or more data in the first data set other than the first data) in the first data set; or, the time delay requirement of the first data in the first data set. Optionally, the first data is the first data in the first data set, or the first data is not the first data in the first data set (e.g., the count value of the first data is greater than or equal to the count value of the first data in the first data set).

[0239] For example, the first data set of the first data association can comprise / replace: the first data in the first data set of the first data association.

[0240] For example, the data set can comprise / replace: a PDU set, or a data burst.

[0241] For example, the generation time can be understood as the time obtained by the second device, or the time obtained by the PDCP layer of the second device, or the time of arrival at the second device, or the time of arrival at the PDCP layer of the second device.

[0242] For example, the generation time of the first data can comprise / replace: the time obtained by the second device for the first data, or the time obtained by the PDCP layer of the second device for the first data, or the time of arrival of the first data at the second device, or the time of arrival of the first data at the PDCP layer of the second device.

[0243] For example, the generation time of the first data set can comprise / replace: the time obtained by the second device for the first data set (or the first data in the first data set), or the time obtained by the PDCP layer of the second device for the first data set (or the first data in the first data set), or the time of arrival of the first data set (or the first data in the first data set) at the second device, or the time of arrival of the first data set (or the first data in the first data set) at the PDCP layer of the second device.

[0244] Optionally, the second information is carried / contained in the first data.

[0245] For example, the second information is used to indicate the information of the time delay expiration time of the first information / data carried / contained in the first data (or data); or, the second information is used to indicate that the data format of the first data (or data) is the first format; or, the second information is used to indicate the existence of the first field.

[0246] For example, if the data format of the first data is the first format, the first information or the first field is carried / contained in the first data.

[0247] For example, the first information / data in the first format carries / includes information of the time delay expiration time, or the first format of the data has the first field.

[0248] Optionally, the embodiments of the present application can further include that the first device acquires second data. Optionally, the second data carries / includes third information.

[0249] For example, the first device acquiring the second data can include / replace the first device acquiring the second data from the second device, or the first device acquiring the second data from a lower layer.

[0250] For example, the third information is used to indicate that the second data (or the data) does not carry / include information of the time delay expiration time of the information / data of the time delay expiration time of the second data; or the third information is used to indicate that the data format of the second data (or the data) is the second format; or the third information is used to indicate that the first field does not exist.

[0251] For example, if the data format of the second data is the second format, the second data does not carry / include information of the time delay expiration time of the information / data of the time delay expiration time of the second data or the first field does not exist.

[0252] For example, the second format of the data does not carry / include information of the time delay expiration time of the data, or the second format of the data does not have the first field.

[0253] For example, the first device receives / acquires multiple data, a part of the multiple data (such as the first data) carries / includes the second information, and another part of the multiple data (such as the second data) carries / includes the third information.

[0254] Optionally, the data can include / replace the PDCP PDU, or the PDCP data PDU, or the PDCP SDU.

[0255] Optionally, the second information and / or the third information can be carried on a second field in the data (for example, the first data or the second data). For example, the embodiments of the present application do not limit the name of the second field.

[0256] For example, the second field includes / is used to indicate that the data carries / includes information of the time delay expiration time of the data, or the data does not carry / include information of the time delay expiration time of the data; or the second field includes / is used to indicate whether the data carries / includes information of the time delay expiration time of the data; or the second field is used to indicate that the data format of the data is the first format or the second format; or the second field is used to indicate the data format of the data; or the second field is used to indicate that the first field exists, or the first field does not exist; or the second field is used to indicate whether the first field exists.

[0257] For example, if the data format of the data is the first format, the data carries / includes the information of the time delay expiration time of the data or the first field exists.

[0258] For example, if the data format of the data is the second format, the data does not carry / include the information of the time delay expiration time of the data or the first field does not exist.

[0259] For example, the first field includes / is used to indicate the information of the time delay expiration time of the first information / data.

[0260] For example, if the value of the second field is the first value, the second field is used to indicate that the data carries / includes the information of the time delay expiration time of the data, or is used to indicate that the data format of the data is the first format, or is used to indicate that the first field exists. For example, if the value of the second field is the second value, the second field is used to indicate that the data does not carry / include the information of the time delay expiration time of the data, or is used to indicate that the data format of the data is the second format, or is used to indicate that the first field does not exist. For example, the second field includes / occupies 1 bit. For example, the first value is 1 and the second value is 0, or the first value is 0 and the second value is 1.

[0261] For example, taking the data as a PDCP PDU, the first format can be as shown in FIG. 14. FIG. 14(a) shows a 12-bit PDCP SN PDCP PDU format. FIG. 14(b) shows an 18-bit PDCP SN PDCP PDU format. For example, the PDCP PDU format includes the second field and the first field, the value of the second field is the first value, and the second field is used to indicate that the PDCP PDU carries / includes the information of the time delay expiration time of the data, or is used to indicate that the format of the PDCP PDU is the first format, or is used to indicate that the first field exists. The other fields included in the PDCP PDU can refer to the foregoing description and will not be described here. For example, the second field occupies 1 bit, and the first field occupies 8 bits. It should be understood that FIG. 14 is only an example, and the embodiments of the present application do not limit the number of bits occupied by the second field, the position of the second field in the PDCP PDU, the number of bits occupied by the first field, the position of the first field in the PDCP PDU, and the order of the fields in the PDCP PDU.

[0262] For example, for a data-carrying PDCP PDU, the second format can be as shown in FIG. 15. FIG. 15(a) shows a PDCP PDU format with a 12-bit PDCP SN. FIG. 15(b) shows a PDCP PDU format with an 18-bit PDCP SN. For example, the second field is included in the PDCP PDU format, the second field has a second value, and the second field is used to indicate information of a time delay expiration time of data carried / included in the PDCP PDU, or used to indicate that the format of the PDCP PDU is the second format, or used to indicate that the first field does not exist. Other fields included in the PDCP PDU can be referred to the foregoing description, and will not be described herein. For example, the second field occupies 1 bit. It should be understood that FIG. 15 is only an example, and the embodiments of the present application do not limit the number of bits occupied by the second field, the position of the second field in the PDCP PDU, and the order of the fields in the PDCP PDU.

[0263] Optionally, the second device transmits M data carrying / including the second information after transmitting N data carrying / including the third information, or transmits N data carrying / including the third information after transmitting M data carrying / including the second information when transmitting the plurality of data. For example, M and N are positive integers. For example, the data carrying / including the second information is referred to as first format data, and the data carrying / including the third information is referred to as second format data. The second device transmits M first format data after transmitting N second format data, or transmits N second format data after transmitting M first format data when transmitting the plurality of data.

[0264] Optionally, at least one data (for example, at least the first data) in a PDU set or a data burst carries / includes the information of the time delay expiration time of data and / or the second information.

[0265] Optionally, at least the first (at least the first X) data in a PDU set or a data burst carries / includes the information of the time delay expiration time of data and / or the second information. For example, X is a positive integer.

[0266] For example, by at least one of the second field, the second information, the third information, the partial data can not carry / included the information of the time delay expiration time of the data, and resource overhead of the information of the time delay expiration time of the data can be reduced.

[0267] Optionally, the embodiments of the present application can further include that the first device determines, based on the second information / third information / second field, that the first data (or data) carries / included the information of the time delay expiration time of the first information / data or the data format of the first data (or data) is the first format or the first field exists, or determines that the second data (or data) does not carry / included the information of the time delay expiration time of the second data or the information of the time delay expiration time of the data or the data format of the second data (or data) is the second format or the first field does not exist, or determines whether the data carries / included the information of the time delay expiration time of the data or the data format of the data is the first format or the second format or the data format of the data or the first field exists.

[0268] It should be noted that the first device obtaining the second data (or the first device obtaining the first data) can be an independent embodiment, which is independent of other steps (for example, steps 1101 and / or steps 1102), and can also be combined with other steps (for example, the first device determines, based on the second information / third information / second field, that the first data (or data) carries / included the information of the time delay expiration time of the first information / data or the data format of the first data (or data) is the first format or the first field exists, or determines that the second data (or data) does not carry / included the information of the time delay expiration time of the second data or the information of the time delay expiration time of the data or the data format of the second data (or data) is the second format or the first field does not exist, or determines whether the data carries / included the information of the time delay expiration time of the data or the data format of the data is the first format or the second format or the data format of the data or the first field exists) to form a new embodiment.

[0269] 1102、The first device performs state variable update and / or submits at least one data according to the time delay expiration time of the first data.

[0270] Optionally, the first device performs state variable update and / or submits at least one data according to the time delay expiration time of the first data can include / replaced by: when the first condition is met, the first device performs state variable update and / or submits at least one data according to the time delay expiration time of the first data.

[0271] Optionally, the embodiments of the present application can further include that when the first condition is met, the first device performs state variable update and / or submits at least one data according to the time delay expiration time of the first data.

[0272] For example, the first condition can comprise at least one of: the first data is not submitted to the upper layer; or, the second COUNT value is greater than or equal to the first state variable; or, the first timer is not stopped.

[0273] For example, not submitted can comprise / replaced by: not yet submitted.

[0274] For example, submitted to can comprise / replaced by: submitted to, or, submitted to.

[0275] For example, the first data is not submitted to the upper layer can comprise / replaced by at least one of: the first device or the PDCP layer of the first device does not submit the first data to the upper layer; the first data is stored in a buffer; or, the first device stores the first data in a buffer.

[0276] For example, the upper layer can comprise / replaced by: the upper layer of the first device, or, the upper layer of the PDCP layer of the first device, or, the SDAP layer, or, the RRC layer, or, the IP layer, or, the APP layer.

[0277] For example, the buffer can comprise / replaced by: buffer, or, receiving buffer, or, receiving buffer of the PDCP layer, or, buffer of the first device, or, buffer of the first device, or, receiving buffer of the first device, or, receiving buffer of the PDCP layer of the first device.

[0278] For example, the second COUNT value is the COUNT value of the first data. Or, the COUNT value of the first data can also be referred to as the second COUNT. Or, other names, which are not limited in the present application.

[0279] For example, not stopped can comprise / replaced by: not stopped, or, not stopped before, or, not stopped before, or, not stopped before, or, not stopped before, or, not stopped before, or, not stopped before.

[0280] For example, the first timer is not stopped can comprise / replaced by at least one of: the first device does not stop the first timer.

[0281] Optionally, the first timer is associated with the first data or the second COUNT value.

[0282] Optionally, when / acquiring the first data (or, if the first device acquires the first data), the first device starts the first timer.

[0283] Optionally, when / acquiring the first data (or, if the first device acquires the first data), if the first data carries / contains information / second information / first field of the time delay expiration time of the first information / data, the first device starts the first timer.

[0284] Optionally, the time length of the first timer can be: a time interval between the starting time of the first timer and the time delay expiration time of the first data, or, a time interval between the starting time of the first timer and the first time, or, a difference between the time delay requirement of the first data and the first time interval (e.g., the time delay requirement of the first data - the first time interval), or, a difference between the time delay requirement of the first data and the first time interval and the second time interval (e.g., the time delay requirement of the first data - the first time interval - the second time interval).

[0285] For example, the starting time of the first timer can include / replace: a time when the first device obtains the first data.

[0286] For example, the time interval can include / replace: the time length.

[0287] For example, the first time is: a time before the time delay expiration time of the first data.

[0288] Optionally, the second time interval is a time interval between the first time and the time delay expiration time of the first data. For example, the second time interval can be negotiated / agreed by the first device and the second device (e.g., indicated by the first device to the second device, or, indicated by the second device to the first device, or, the specific value of the time interval is agreed by the first device and the second device), or, can be configured by the network device (e.g., configured by the network device to the second device, or, configured by the network device to the first device), or, can be specified by the communication protocol, or, can be predefined, which is not limited in the application itself.

[0289] For example, the network device can include / replace: an access network device.

[0290] For example, the second time interval is 1 subframe, or, 1 slot, or, 1 symbol. For example, the second time interval can include / replace: the first threshold.

[0291] For example, the first time interval is a time interval between the starting time of the first timer and the generation time of the first data.

[0292] For example, the time delay requirement of the first data can include / replace: the time delay requirement of the first service, or, the time delay requirement of the service associated with the first PDCP entity. For example, the first data is associated with the first service or the first PDCP entity.

[0293] For example, the time interval between the generation time of the first data and the time delay expiration time of the first data is the time delay requirement of the first data. For example, starting from the generation time of the first data, after a time length corresponding to the time delay requirement of the first data, the time delay expiration time of the first data is reached.

[0294] Optionally, the first data is submitted to the upper layer (or, if the first data is submitted to the upper layer), or, the first status variable is greater than the second count value (or, if the first status variable is greater than the second count value), the first device stops the first timer.

[0295] Optionally, the first data is submitted to the upper layer (or, if the first data is submitted to the upper layer), or, the first status variable is greater than the second count value (or, if the first status variable is greater than the second count value), the first device stops the first timer if the first timer is running.

[0296] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0297] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0298] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0299] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0300] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0301] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0302] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0303] For example, the first data is submitted to the upper layer can include / replace at least one of: the first device or the PDCP layer of the first device submits the first data to the upper layer; or, the first data is not stored in the buffer.

[0304] For example, the interval between the first time and the time delay expiration time of the first data is less than or equal to the second time interval.

[0305] For example, the first device performing the state variable updating can include / replace: the first device performing at least one of operation 1-3.

[0306] For example, the first device submitting the at least one data can include / replace: the first device performing operation 4.

[0307] Optionally, the first device performing the state variable updating according to the time delay expiration time of the first data can include / replace: when the second condition is met, the first device performing at least one of operation 1-3.

[0308] Operation 1: the first device updates the first state variable to the first count value.

[0309] For example, the first count value is greater than the second count value.

[0310] For example, the first state variable is used to indicate the count value of the first data waiting to be submitted by the first device, or the count value of the first data not submitted and waiting to be submitted by the first device, or the count value of the first data waiting to be received by the first device, or the count value of the first data not received and waiting to be received by the first device, or the count value of the first data not received and waiting to be submitted by the first device, or the count value of the first data waiting to be submitted, or the count value of the first data not submitted and waiting to be submitted, or the count value of the first data waiting to be received, or the count value of the first data not received and waiting to be received, or the count value of the first data not received and waiting to be submitted.

[0311] For example, the first state variable can include RX_DELIV. For example, the first state variable is RX_DELIV.

[0312] For example, RX_DELIV can indicate the COUNT of the first PDCP PDU not submitted to the upper layer and still waiting.

[0313] For example, RX_DELIV can be understood as the lower limit of the reordering window.

[0314] For example, the reordering window can also include / replace: the receiving window, or the PDCP window, or the PDCP receiving window.

[0315] Optionally, the first count value corresponds to data not received by the first device, or the first count value corresponds to data not received by the first device.

[0316] Optionally, the data corresponding to the first count value is not submitted to the upper layer, or the first device does not submit the data corresponding to the first count value to the upper layer.

[0317] Optionally, the data corresponding to the first count value does not include / is not: discarded data.

[0318] For example, the discarded data can include / replaced by: data considered to have been received by the first device, or data considered to be discarded, or data considered to be discarded by the first device, or data considered to be received, or data considered to be received by the first device.

[0319] For example, the data corresponding to the first count value is the first unreceived data with a count value greater than the second count value; or, the data corresponding to the first count value is the first unreceived data with a count value greater than the second count value, except for discarded data.

[0320] For example, the first unreceived data can include / replaced by: the first unsubmitted data.

[0321] For example, the submission can include / replaced by: submission to the upper layer or the upper layer of the first device.

[0322] For example, except for discarded data, it can include / replaced by: data that is not discarded.

[0323] For example, the data corresponding to the first count value is the first unreceived data with a count value greater than the second count value can include / replaced by any one or more of the following: the data corresponding to the first count value is data with a count value greater than the second count value, the data corresponding to the first count value has not been submitted to the upper layer, the data corresponding to the first count value does not exist / is not stored in the cache.

[0324] For example, the data corresponding to the first count value can include / replaced by the PDCP SDU or PDCP PDU corresponding to the first count value.

[0325] For example, the first unreceived data with a count value greater than the second count value, except for discarded data, can include / replaced by any one or more of the following: the first data with a count value greater than the second count value, except for discarded data, that has not been submitted to the upper layer; or, the first data with a count value greater than the second count value, except for discarded data, that does not exist / is not stored in the cache.

[0326] For example, the first device updates the first status variable to the COUNT of the first data (e.g., PDCP SDU) that has not been submitted to the upper layer, and the COUNT of the first data is greater than the second COUNT value. For example, the first device updates the first status variable to the first hole after the second COUNT value. For example, the first device updates the first status variable to the first hole after the second COUNT value, except for the discarded data.

[0327] As an example, the first status variable RX_DELIV is 3, and it is assumed that the data received and stored by the first device includes data #1, data #2, and data #3. The COUNT of data #1 is 4, the COUNT of data #2 is 5, and the COUNT of data #3 is 7. If the time delay of data #1 expires, the first device submits data #1 and data #2 to the upper layer, the first device determines the COUNT of the first data that has not been submitted to the upper layer is 6, and the first device updates the first status variable RX_DELIV to 6.

[0328] As an example, the first status variable RX_DELIV is 3, and it is assumed that the data received and stored by the first device includes data #1, data #2, and data #3. The COUNT of data #1 is 4, the COUNT of data #2 is 5, and the COUNT of data #3 is 7. If the time delay of data #1 expires, the COUNT of the discarded data (or, considered as the data that has been received by the first device) is 6, the first device updates the first status variable RX_DELIV to 8, and the first device submits data #1, data #2, and data #3 to the upper layer.

[0329] As an example, the first status variable RX_DELIV is 3, and it is assumed that the data received and stored by the first device includes data #1, data #2, and data #3. The COUNT of data #1 is 4, the COUNT of data #2 is 5, and the COUNT of data #3 is 6. If the time delay of data #1 expires, the COUNT of the discarded data (or, considered as the data that has been received by the first device) is 7. The first device updates the first status variable RX_DELIV to 8, and the first device submits data #1, data #2, and data #3 to the upper layer.

[0330] Operation 2: If the reordering timer is running, and the first status variable is greater than or equal to the second status variable, the first device stops the reordering timer.

[0331] For example, if the reordering timer is running can include / replaced by: when the reordering timer is running.

[0332] For example, stopping can include: stopping and resetting.

[0333] For example, the reordering timer is used to detect loss of data. For example, the reordering timer can be t-Reordering.

[0334] For example, the second status variable is used to indicate the COUNT value of the data triggering the reordering timer plus 1, or, is used to indicate the COUNT value after the COUNT value of the data triggering the reordering timer. For example, the second status variable can include RX_REORD. For example, the second status variable is RX_REORD.

[0335] As an example, assuming the first status variable = 4, the second status variable = 2, the first status variable is greater than the second status variable, indicating that the first device has received or no longer needs to receive / await data before the first status variable or the second status variable, the first device stops the reordering timer.

[0336] Operation 3: If the reordering timer is not running, and the first status variable is less than the third status variable, the first device starts the reordering timer.

[0337] For example, the third status variable is used to indicate the COUNT value of the next data expected to be received. For example, the third status variable can include RX_NEXT. For example, the second status variable is RX_NEXT.

[0338] For example, RX_NEXT can indicate the COUNT of the next PDCP PDU expected to be received.

[0339] For example, RX_NEXT can be understood as the COUNT value of the data with the largest COUNT value among the received data and / or discarded data plus 1.

[0340] For example, if the reordering timer is not running, it can include / replaced by: when the reordering timer is not running.

[0341] As an example, when the reordering timer is not running, assuming the first status variable = 4, the third status variable = 7, indicating that the first device has received data with a COUNT value of 6, the first device has not received data before the data with a COUNT value of 6, or can be referred to as there is a hole, the first device starts the reordering timer.

[0342] It can be understood that the first device updates the status variable according to the delay expiration time of the first data, which is beneficial to timely update the PDCP window / status variable, is beneficial to timely delivery of data, avoids data not being delivered before the delay expires, avoids data being delivered after the delay expires, guarantees / benefits timely delivery of data before / when the delay expires, is beneficial to decoding at the receiving end, is beneficial to guaranteeing the delay requirement of data, can improve the reliability of data, and is beneficial to service / user experience.

[0343] Optionally, the first device submitting the at least one data according to the time delay expiration time of the first data can comprise / replaced by: the first device performing operation 4 under the second condition.

[0344] Operation 4: The first device submits the at least one data.

[0345] For example, the submitting can comprise / replaced by: submitting to an upper layer.

[0346] For example, the at least one data can comprise at least one second data and / or at least one third data.

[0347] For example, the second data corresponds to a count value less than or equal to a second count value.

[0348] For example, the third data corresponds to a count value greater than or equal to the second count value.

[0349] Optionally, the second data can comprise / replaced by: a PDCP PDU, or a PDCP data PDU, or a PDCP SDU.

[0350] Optionally, the third data can comprise / replaced by: a PDCP PDU, or a PDCP data PDU, or a PDCP SDU.

[0351] For example, the at least one second data can comprise one or more of: data received by the first device or a PDCP layer of the first device and having a count value less than or equal to the second count value, data not submitted by the first device or the PDCP layer of the first device and having a count value less than or equal to the second count value, data existing / stored in a buffer and having a count value less than or equal to the second count value.

[0352] For example, the count value of the at least one second data can be continuous or discontinuous.

[0353] For example, the at least one second data does not comprise / is not: discarded data.

[0354] For example, the at least one third data comprises one or more of: data received by the first device or the PDCP layer of the first device and having a count value greater than or equal to the second count value, data not submitted by the first device or the PDCP layer of the first device and having a count value greater than or equal to the second count value, data existing / stored in a buffer and having a count value greater than or equal to the second count value.

[0355] For example, the count value of the at least one third data can be continuous.

[0356] For example, the at least one third data can not comprise: discarded data.

[0357] For example, the COUNT value of the at least one third data is consecutive to the COUNT value of the discarded data.

[0358] For example, the at least one third data can include any one or more of the following:

[0359] data whose COUNT value is greater than or equal to the second COUNT value and which has been received and not submitted;

[0360] data whose COUNT value is greater than or equal to the second COUNT value and which exists / stored in the buffer;

[0361] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / consecutively stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1);

[0362] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / in-sequence stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1);

[0363] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / consecutively stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1);

[0364] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / in-sequence stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1);

[0365] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / in-sequence stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1);

[0366] data whose COUNT value is greater than or equal to the second COUNT value and which is consecutively received (or deemed to be received) / in-sequence stored (or deemed to be stored) after the second COUNT value (or, the second COUNT value + 1).

[0367] It should be noted that the "consecutively received data" does not mean that the first device receives the data consecutively in sequence, but only means that the COUNT values of the data are consecutive. Alternatively, the consecutively received data means that the COUNT values of the data are consecutive, and does not mean that the first device or the PDCP layer of the first device receives the data consecutively.

[0368] As an example, it is assumed that the data received and stored by the first device includes data #1, data #2 and data #3, the COUNT of data #1 is 4, the COUNT of data #2 is 5, and the COUNT of data #3 is 6. The COUNTs of data #1, data #2 and data #3 are consecutive, and if the delay of data #1 expires, data #1, data #2 and data #3 can be submitted.

[0369] As an example, assume that the first device receives and stores data #1, data #2, data #3, the COUNT of data #1 is 4, the COUNT of data #2 is 5, and the COUNT of data #3 is 7. The COUNT of discarded data is 6. The COUNTs of data #1, data #2, data #3, and discarded data are consecutive. If the time delay of data #1 expires, data #1, data #2, and data #3 can be submitted.

[0370] It can be understood that the first device submits at least one data according to the time delay expiration time of the first data, which is beneficial to timely submission of data, avoids submission of data before the time delay expires, avoids submission of data after the time delay expires, ensures timely submission of data before the time delay expires, is beneficial to decoding of the receiving end, is beneficial to ensuring the time delay requirement of data, can improve the reliability of data, and is beneficial to service / user experience.

[0371] For example, performing state variable updating and / or submitting at least one data can include / replaced by: performing reordering, or performing a reordering operation / process. For example, performing can include / replaced by: performing.

[0372] Optionally, the application can further include (or, step 1102 can be replaced by): the first device discards at least one second data according to the time delay expiration time of the first data.

[0373] Optionally, the first device discarding at least one second data according to the time delay expiration time of the first data can include / replaced by: satisfying a second condition, and the first device performing operation 5.

[0374] Operation 5: The first device submits the discarded at least one second data.

[0375] For example, the application does not limit the execution order of operation 1, operation 2, operation 3, operation 4, and operation 5. For example, operation 2 is performed before operation 3. For example, operation 4 is performed before at least one of operation 1, operation 2, and operation 3.

[0376] Optionally, the application can further include / need to satisfy: the first device obtains first indication information.

[0377] For example, the first indication information is used to indicate information / first field / second field / second information / third information / first information carrying / included in data, which is the time delay expiration time of data.

[0378] Optionally, the first indication information is used to indicate information / first field / second field / second information / third information / first information carrying / included in data associated with the first radio bearer (radio bearer, RB) or the first PDCP entity, which is the time delay expiration time of data.

[0379] For example, the first data is associated with the first RB or the first PDCP entity.

[0380] For example, the first data is carried in the first RB, or the first PDCP entity obtains the first data.

[0381] Optionally, the first device can include / replace the first PDCP entity.

[0382] Optionally, the first indication information is from the network device (or the second device). Alternatively, the network device (or the second device) sends the first indication information, and correspondingly, the first device obtains the first indication information, and further can be implemented as: the first device receives the first indication information from the network device (or the second device).

[0383] For example, the network device is the second device, and the first indication information is sent by the second device.

[0384] For example, if the first device obtains the first indication information, the first device only performs the content related to step 1101 and / or step 1102 (or at least one of operation 1, operation 2, operation 3, operation 4 and operation 5).

[0385] It should be noted that step 1101 can be an independent embodiment and does not depend on step 1102. Step 1101 can also be combined with other steps to form a new embodiment.

[0386] It should be noted that step 1102 can be an independent embodiment and does not depend on step 1101. Step 1102 can also be combined with other steps to form a new embodiment.

[0387] The communication device provided by the embodiment of the present application will be introduced below.

[0388] The present application divides the function modules of the communication device according to the above-mentioned method embodiments. For example, each function module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of software function module. It should be noted that the division of the modules in the present application is illustrative, and is only a logical function division. In actual implementation, another division mode can be used. The communication device of the embodiment of the present application will be described in detail below with reference to FIGS. 16-18.

[0389] FIG. 16 is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application. As shown in FIG. 16, the communication apparatus includes a processing module 1601 and a transceiver module 1602. The transceiver module 1602 can implement corresponding communication functions, and the processing module 1601 is configured to implement corresponding processing functions. The transceiver module 1602 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0390] In the embodiment of the present application, the communication apparatus can be configured to perform the actions performed by the first device in the method embodiments. At this time, the first device can be the first device itself or a chip or a functional module configured in the first device, etc. The transceiver module 1602 is configured to perform the operations related to the transceiving of the first device in the method embodiments, and the processing module 1601 is configured to perform the operations related to the processing of the first device in the method embodiments.

[0391] For example, the transceiver module 1602 can be configured to obtain first information, and the first information includes information of a time delay expiration time of first data; and the processing module 1601 can be configured to perform state variable updating and / or submitting at least one data according to the time delay expiration time of the first data.

[0392] Optionally, in each of the above embodiments, the communication apparatus can further include a storage module, which can be configured to store instructions and / or data, and the processing module 1601 can read the instructions and / or data in the storage module, so that the communication apparatus implements the method embodiments.

[0393] The specific description of the transceiver module and the processing module in each of the above embodiments is only an example. For the specific functions or executed steps of the transceiver module and the processing module, reference can be made to the method embodiments, which will not be described in detail here.

[0394] Referring to FIG. 16, in an embodiment of the present application, the communication apparatus can be configured to perform the actions performed by the second device in the method embodiments. At this time, the second device can be the second device itself or a chip or a functional module configured in the second device, etc. The transceiver module 1602 is configured to perform the operations related to the transceiving of the second device in the method embodiments, and the processing module 1601 is configured to perform the operations related to the processing of the second device in the method embodiments.

[0395] For example, the processing module 1601 can be configured to generate first data; and the transceiver module 1602 can be configured to send the first data, and the first data carries first information, and the first information includes information of a time delay expiration time of the first data.

[0396] Optionally, in each of the above embodiments, the communication apparatus can further include a storage module, which can be configured to store instructions and / or data, and the processing module 1601 can read the instructions and / or data in the storage module to enable the communication apparatus to implement the foregoing method embodiments.

[0397] The specific descriptions of the transceiver module and the processing module in each of the above embodiments are merely examples. For the specific functions or executed steps of the transceiver module and the processing module, reference can be made to the above method embodiments, which will not be described in detail here.

[0398] The communication apparatus of the embodiments of the present application is introduced above, and possible product forms of the communication apparatus are introduced below. Any product form that has the functions of the communication apparatus described in FIG. 16 falls within the protection scope of the embodiments of the present application. The following introduction is merely an example, and does not limit the product form of the communication apparatus of the embodiments of the present application.

[0399] In a possible implementation, in the communication apparatus shown in FIG. 16, the processing module 1601 can be one or more processing circuits, and the transceiver module 1602 can be a transceiver circuit, or the transceiver module 1602 can also be a sending module and a receiving module, the sending module can be a sending circuit, and the receiving module can be a receiving circuit, which are integrated in one device, such as a transceiver circuit. In the embodiments of the present application, the processing circuit and the transceiver circuit can be coupled, and the connection manner of the processing circuit and the transceiver circuit is not limited in the embodiments of the present application. In the process of executing the above method, the process of sending information in the above method can be the process of outputting the above information by the processing circuit. When the above information is outputted, the processing circuit outputs the above information to the transceiver circuit, so as to be transmitted (or outputted) by the transceiver circuit. After the above information is outputted by the processing circuit, it can also need to be processed further, and then reaches the transceiver circuit. Similarly, the process of receiving information in the above method can be the process of receiving inputted above information by the processing circuit. When the processing circuit receives the inputted information, the transceiver circuit receives the above information and inputs it to the processing circuit. Furthermore, after the transceiver circuit receives the above information, the above information can need to be processed further, and then inputted to the processing circuit.

[0400] FIG. 17 is a structural schematic diagram of a communication apparatus provided by the embodiments of the present application. As shown in FIG. 17, the communication apparatus 170 includes one or more processing circuits 1720 and a transceiver circuit 1710.

[0401] In some embodiments of the application, the communication device can be configured to perform the steps or methods or functions performed by the first apparatus as described above, e.g., the processing circuitry 1720 can be configured to perform the functions or steps implemented by the processing module 1601 as illustrated in FIG. 16, and the transceiver circuitry 1710 can be configured to perform the functions or steps implemented by the transceiving module 1602 as illustrated in FIG. 16. More details about the processing circuitry 1720 and the transceiver circuitry 1710 can be referred to the description of the method embodiments illustrated above or FIG. 16, and will not be repeated here.

[0402] In some embodiments of the application, the communication device can be configured to perform the steps or methods or functions performed by the first apparatus as described above, e.g., the processing circuitry 1720 can be configured to perform the functions or steps implemented by the processing module 1601 as illustrated in FIG. 16, and the transceiver circuitry 1710 can be configured to perform the functions or steps implemented by the transceiving module 1602 as illustrated in FIG. 16. More details about the processing circuitry 1720 and the transceiver circuitry 1710 can be referred to the description of the method embodiments illustrated above or FIG. 16, and will not be repeated here.

[0403] By way of example, the processing circuitry can be one or more processors, or all or part of one or more processors. The transceiver circuitry can be a transceiver, or input / output circuitry, or interface circuitry, etc.

[0404] By way of example, in each of the various implementations of the communication device illustrated in FIG. 17, the transceiver circuitry can include a receiver configured to perform the functions (or operations) of receiving, and a transmitter configured to perform the functions (or operations) of transmitting. The transceiver circuitry is configured to communicate with other devices / apparatuses via a transmission medium.

[0405] Optionally, the communication device 170 can further include one or more memories 1730 configured to store program instructions and / or data. The memory 1730 is coupled to the processing circuitry 1720. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other form, for information interaction between devices, units, or modules. The processing circuitry 1720 can operate in cooperation with the memory 1730. The processing circuitry 1720 can execute program instructions stored in the memory 1730. Optionally, at least one of the one or more memories can be included in the processing circuitry.

[0406] The specific connection medium between the transceiver circuit 1710, the processing circuit 1720 and the memory 1730 in the embodiments of the present application is not limited. In FIG. 17, the memory 1730, the processing circuit 1720 and the transceiver circuit 1710 are connected through a bus 1740, which is represented by a thick line in FIG. 17, and the connection mode between other components is only illustrative and is not limited. The bus can be divided into an address bus, a data bus, a control bus and the like. For convenience of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or only one type of bus.

[0407] In the embodiments of the present application, the processing circuit can be a general-purpose processing circuit, a digital signal processing circuit, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can implement or execute the methods, steps and logic block diagrams in the embodiments of the present application. The general-purpose processing circuit can be a micro-processing circuit or any conventional processing circuit, etc. The steps of the method in combination with the embodiments of the present application can be directly embodied as execution completed by a hardware processing circuit, or executed by a combination of hardware and software modules in the processing circuit, etc.

[0408] In the embodiments of the present application, the memory can include, but is not limited to, a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable ROM (EPROM), a read-only memory (ROM) or a compact disc read-only memory (CD-ROM), etc. The memory is any storage medium that can be used to carry or store program codes in the form of instructions or data structures and can be read and / or written by a computer (such as the communication device shown in the present application, etc.), but is not limited thereto. The memory in the embodiments of the present application can also be a circuit or any other device capable of realizing a storage function, used for storing program instructions and / or data.

[0409] The processing circuit 1720 is mainly configured to process communication protocols and communication data, control the whole device, execute software programs, and process data of the software programs. The memory 1730 is mainly configured to store software programs and data. The transceiver circuit 1710 can include a control circuit and an antenna, where the control circuit is mainly configured to convert baseband signals and radio frequency signals and process the radio frequency signals. The antenna is mainly configured to transceive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, and the like, are mainly configured to receive user input data and output data to users.

[0410] When the device is powered on, the processing circuit 1720 can read software programs in the memory 1730, interpret and execute instructions of the software programs, and process data of the software programs. When data needs to be transmitted wirelessly, the processing circuit 1720 performs baseband processing on the data to be transmitted, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit converts the baseband signal into a radio frequency signal, and transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is transmitted to the device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processing circuit 1720. The processing circuit 1720 converts the baseband signal into data and processes the data.

[0411] In another implementation, the radio frequency circuit and the antenna can be arranged independently of the processing circuit that performs baseband processing, for example, in a distributed scenario, the radio frequency circuit and the antenna can be arranged remotely from the device.

[0412] The communication device shown in the embodiments of the present application can also have more components and the like than those shown in FIG. 17, which are not limited in the embodiments of the present application. The methods performed by the processing circuit and the transceiver circuit shown above are only examples, and the specific steps performed by the processing circuit and the transceiver circuit can refer to the methods introduced above.

[0413] In another possible implementation, in the communication device shown in FIG. 16, the processing module 1601 can be one or more logic circuits, and the transceiver module 1602 can be an input and output interface, also referred to as a communication interface, or an interface circuit, or an interface, and the like. Alternatively, the transceiver module 1602 can also be a sending module and a receiving module, where the sending module can be an output interface, and the receiving module can be an input interface. The sending module and the receiving module are integrated into one module, such as an input and output interface.

[0414] FIG. 18 is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application. As shown in FIG. 18, the communication apparatus shown in FIG. 18 includes a logic circuit 1801 and an interface circuit 1802. That is, the processing module 1601 can be implemented by the logic circuit 1801, and the transceiver module 1602 can be implemented by the interface circuit 1802. The logic circuit 1801 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, and the interface circuit 1802 can be a communication interface, an input / output interface, a pin, etc. For example, FIG. 18 is a chip in which the communication apparatus is taken as an example, and the chip includes the logic circuit 1801 and the interface circuit 1802.

[0415] In an embodiment of the present application, the logic circuit and the interface can also be coupled to each other. The specific connection mode of the logic circuit and the interface is not limited in the embodiments of the present application. For example, the logic circuit 1801 can be used to execute the functions or steps implemented by the processing module 1601 shown in FIG. 16, and the interface circuit 1802 can be used to execute the functions or steps implemented by the transceiver module 1602 shown in FIG. 16. The specific description of the logic circuit 1801 and the interface circuit 1802 can be referred to the method embodiments shown in FIG. 16 or the above description, which will not be described here in detail.

[0416] The communication apparatus shown in the embodiments of the present application can be used to implement the method provided in the embodiments of the present application in the form of hardware, or can be used to implement the method provided in the embodiments of the present application in the form of software, etc., and the embodiments of the present application do not limit this.

[0417] The embodiments of the present application further provide a communication system, which includes a first apparatus and a second apparatus, and the first apparatus and the second apparatus can be used to execute the method in any of the foregoing embodiments.

[0418] In addition, the present application further provides a computer program, which is used to implement the operations and / or processes executed by each communication apparatus in the method provided in the present application.

[0419] The present application further provides a computer readable storage medium, which stores computer code, and when the computer code is run on a computer, the computer code makes the computer execute the operations and / or processes executed by each communication apparatus in the method provided in the present application.

[0420] The present application further provides a computer program product, which includes computer code or a computer program, and when the computer code or the computer program is run on a computer, the operations and / or processes executed by each communication apparatus in the method provided in the present application are executed.

[0421] In several embodiments provided in the present application, it should be understood that the disclosed system, communication device and method can be implemented in other manners. For example, the division of the above-described communication device embodiments is merely a logical function division, and there can be another division manner for the actual implementation, for example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, communication devices or modules, and can be electric, mechanical or in other forms.

[0422] The modules illustrated as separated components can or can not be physically separated, and the components illustrated as modules can or can not be physical modules, i.e., can be located in one place or distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0423] In addition, the functional modules in each of the embodiments of the present application can be integrated into one processing module, or each module can be physically present alone, or two or more modules can be integrated into one module. The above integrated module can be realized in the form of hardware or in the form of a software functional module.

[0424] The integrated module, if realized in the form of a software functional module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art that contributes to the technical solutions, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a readable storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned readable storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0425] The above is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method applied to a first device comprises: obtaining first information, wherein the first information comprises information of a time delay expiration time of first data; updating a state variable according to the time delay expiration time of the first data and / or submitting at least one data.

2. The method of claim 1, wherein, The obtaining of the first information comprises: obtaining the first data, wherein the first data carries the first information.

3. The method according to claim 1 or 2, characterized in that, The updating of the state variable according to the time delay expiration time of the first data comprises: if the time delay expiration time of the first data expires, performing at least one of the following: updating a first state variable to a first count value, wherein the first count value is greater than a second count value; or if a reordering timer is running and the first state variable is greater than or equal to a second state variable, stopping the reordering timer by the first device; or if the reordering timer is not running and the first state variable is less than a third state variable, starting the reordering timer by the first device; wherein the second count value is a count value of the first data; the first state variable is used to indicate a count value of a first data which the first device waits to submit; the second state variable is used to indicate a count value of data which triggers the reordering timer plus 1; the third state variable is used to indicate a count value of next data which the first device expects to receive.

4. The method of claim 3, wherein, the data corresponding to the first count value is a first unreceived data whose count value is greater than the second count value; or the data corresponding to the first count value is a first unreceived data whose count value is greater than the second count value except for discarded data.

5. The method according to any one of claims 1 to 4, characterized in that, The submitting of at least one data according to the time delay expiration time of the first data comprises: if the time delay expiration time of the first data expires, submitting at least one data.

6. The method according to any one of claims 1 to 5, characterized in that, The at least one data comprises at least one second data and / or at least one third data; the second data corresponds to a count value less than a second count value; the third data corresponds to a count value greater than or equal to the second count value; and the second count value is a count value of the first data.

7. The method of claim 6, wherein, The count value of the at least one third data is continuous, or the count value of the at least one third data is continuous with that of discarded data.

8. The method according to any one of claims 1 to 7, characterized in that, The information of the time delay expiration time of the first data comprises information of a time unit in which the time delay expiration time of the first data is located, and the time unit comprises at least one of a frame, a subframe, a slot and a symbol.

9. The method according to any one of claims 1 to 8, characterized in that, The first data carries second information, wherein the second information is used to indicate that the first data carries the first information.

10. The method according to any one of claims 1 to 9, characterized in that, The method further comprises: obtaining first indication information, wherein the first indication information is used to indicate that data in data associated with a first radio bearer (RB) or a first packet data convergence protocol (PDCP) entity carries information of a time delay expiration time of the data.

11. The method according to any one of claims 1 to 10, characterized in that, The first data is a PDCP protocol data unit (PDU).

12. A communication method characterized by comprising: The method applied to a second device comprises: sending first data, wherein the first data carries first information, and the first information comprises information of a time delay expiration time of the first data.

13. The method of claim 12, wherein, The information of the time delay expiration time of the first data comprises information of a time unit in which the time delay expiration time of the first data is located, and the time unit comprises at least one of a frame, a subframe, a time slot, and a symbol.

14. The method according to claim 12 or 13, characterized in that, The first data carries second information, and the second information is used for indicating that the first data carries the first information.

15. The method according to any one of claims 12 to 14, characterized in that, The method further comprises: sending first indication information, wherein the first indication information is used for indicating information of a time delay expiration time carried in data associated with a first radio bearer (RB) or a first packet data convergence protocol (PDCP) entity.

16. The method according to any one of claims 12 to 15, characterized in that, The first data is a PDCP protocol data unit (PDU).

17. A communications device, characterized by The apparatus comprises a module or unit for performing the method in any of claims 1-11, or the apparatus comprises a module or unit for performing the method in any of claims 12-16.

18. A communications device, characterized by The apparatus comprises a processor for enabling the apparatus to perform the method in any of claims 1-11, or the processor is configured to enable the apparatus to perform the method in any of claims 12-16.

19. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, and when the computer program or instructions are executed by the apparatus, the method in any of claims 1-11 is executed, or the method in any of claims 12-16 is executed.

Citation Information

Patent Citations

  • Data packet transmission method and communication device

    CN112153691A