CN114902637A

CN114902637A - Data transmission method and device

Info

Publication number: CN114902637A
Application number: CN201980103359.2A
Authority: CN
Inventors: 黄曲芳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2022-08-12
Anticipated expiration: 2039-12-31
Also published as: WO2021134680A1

Abstract

The application discloses a data transmission method and device. The method comprises the following steps: the communication device receives the first data packet, and if the first data packet is determined to be transmitted in error, error delivery is performed on the first data packet. By adopting the method, the data packet which is already received by the receiving end equipment can be effectively utilized by executing error submission on the data packet, and the transmission requirement of the service is met.

Description

Data transmission method and device

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a data transmission method and apparatus.

Background

With the development of wireless communication networks, services supported by terminal devices are more and more abundant and diverse, for example, the terminal devices can support more and more services such as high-precision voice, high-definition video and the like, the data volume of the services is large, and the requirement on data delay is higher.

However, how to perform data transmission to meet the transmission requirement of the above services still needs to be further studied.

Disclosure of Invention

In view of this, the present application provides a data transmission method and apparatus, so as to implement error delivery of a data packet, so as to effectively utilize the data packet that has been received by a receiving end device, and meet a transmission requirement of a service.

In a first aspect, an embodiment of the present application provides a data transmission method, which may be applied to a communication device, in which the communication device receives a first data packet, and performs error delivery on the first data packet if it is determined that the first data packet is transmitted in error.

By adopting the method, the data packet which is already received by the receiving end equipment can be effectively utilized by executing error submission on the data packet, and the transmission requirement of the service is met.

In one possible design, the communication device determining the first packet transmission error includes: the communication device determines that the CRC check of the first packet failed; and/or the communication device determines that the first packet decoding failed.

In one possible embodiment, the communication device may be a network device or a chip disposed inside the network device.

In one possible design, the method further includes: the communication device sends first indication information, wherein the first indication information is used for indicating that the data carried by the first resource supports error delivery; the first data packet is carried on the first resource.

In one possible design, the communication device sends the first indication information, including: the communication device sends an uplink authorization, wherein the uplink authorization is used for indicating a first resource and carries first indication information; or the communication device sends first configuration information, wherein the first configuration information is used for configuring a first resource and carries first indication information; or, the communication device sends control information, where the control information is used to activate the first resource, and the control information carries the first indication information.

By adopting the implementation mode, the network equipment can determine whether the transmission supports the error delivery or not by indicating whether the data carried by the first resource supports the error delivery or not, so that the regulation and control flexibility of the network equipment is improved.

In one possible design, the method further includes: the communication device receives second indication information indicating that the first data packet supports error delivery.

By adopting the method, the terminal device can indicate the first data packet to the network device to support the error delivery, that is, the terminal device can determine whether the transmission supports the error delivery, so that when the network device allocates resources, the network device does not need to indicate whether the data carried by the resources support the error delivery, and the processing burden of the network device is reduced.

In one possible design, the first data packet and the second indication information are carried in a first resource allocated by the communication device.

By adopting the mode, the first data packet and the second indication information are both borne on the first resource, so that the second indication information is sent without using extra resources, and transmission resources can be effectively saved.

In one possible embodiment, the communication device may be a terminal or a chip arranged inside the terminal.

In one possible design, the first data packet is carried on the second resource; the method further comprises the following steps: the communication device receives third indication information, wherein the third indication information is used for indicating that the data carried by the second resource supports error delivery.

In one possible design, the communication device receives third indication information, including: the communication device receives first control information, wherein the first control information is used for scheduling second resources and carries third indication information; or the communication device receives second control information, wherein the second control information is used for activating a second resource and carries third indication information; or, the communication device receives second configuration information, where the second configuration information is used to configure a second resource, and the second configuration information carries third indication information.

In one possible design, the first data packet is carried on the second resource; the method further comprises the following steps: the communication device receives third control information according to the preset control resource set and/or the preset search space, wherein the third control information is used for scheduling the second resource; the data loaded by the resource scheduled by the third control information loaded by the preset control resource set and/or the preset search space supports error submission; or, the communication device receives third control information on a physical downlink control channel, where the third control information is used to schedule the second resource; the physical downlink control channel is scrambled through a preset RNTI (radio network temporary identifier), and the preset RNTI indicates that the data supported by the resource scheduled by the third control information supported by the physical downlink control channel supports error delivery.

By adopting the mode, the data loaded by the second resource is indicated to support error submission in an implicit mode, so that the indication information does not need to be transmitted through extra resources, and the transmission resources can be effectively saved.

In one possible design, the method further includes: the communication device receives third configuration information, the third configuration information being used for configuring an error delivery function for the communication device.

In one possible design, the communication device performs error delivery on the first data packet, including: the HARQ entity of the communication device delivers the first data packet and fourth indication information to the demultiplexing entity, the fourth indication information being indicative of a transmission error of the first data packet.

In one possible design, the fourth indication information is used to indicate a decoding accuracy of the first data packet.

By adopting the mode, the decoding accuracy of the first data packet is indicated, so that the upper layer can be more clear of the decoding condition of the first data packet, and the corresponding operation can be conveniently executed according to the decoding condition of the first data packet.

In one possible design, before the HARQ entity of the communication device delivers the first data packet and the fourth indication information to the demultiplexing entity, at least one of the following is further included: the HARQ entity of the communication device determines that the decoding accuracy of the first data packet is greater than a first threshold; determining, by an HARQ entity of the communication device, that a number of retransmissions of the first data packet is greater than a second threshold; the HARQ entity of the communication device determines that the timer corresponding to the first data packet has expired.

In one possible design, the method further includes: if the HARQ entity of the communication device receives the retransmission data packet of the first data packet, the HARQ entity submits the retransmission data packet to a demultiplexing entity; further, the first packet may be a newly transmitted packet.

In one possible design, before the HARQ entity of the communication device delivers the retransmission packet to the demultiplexing entity, the method further includes: the HARQ entity of the communication device determines that the retransmitted data packet is transmitted correctly.

In one possible design, the method further includes: the HARQ entity of the communication device feeds back an acknowledgement ACK for the first data packet.

In one possible design, the communication device performs error delivery on the first data packet, including: the demultiplexing entity of the communication device delivers the first data packet and fifth indication information to the RLC layer entity, and the fifth indication information is used for indicating transmission errors of the first data packet.

In one possible design, before the demultiplexing entity of the communication device delivers the first data packet to the RLC layer entity, at least one of: a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier; a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier, and the logical channels corresponding to the logical channel identifier all support error submission; a demultiplexing entity of the communication device determines that a first data packet is not delivered to an RLC layer entity; the demultiplexing entity of the communication device determines that the decoding correctness rate of the first data packet is greater than a third threshold.

In one possible design, the method further includes: and if the demultiplexing entity of the communication device determines that the first data packet comprises the MAC CE, applying the MAC CE.

In one possible design, before the demultiplexing entity of the communication apparatus performs the MAC CE indicated action, at least one of the following is further included: a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier; a demultiplexing entity of the communication device determines that a first data packet is received for the first time; the demultiplexing entity of the communication device determines that the decoding correctness rate of the first data packet is greater than the fourth threshold.

In one possible design, the method further includes: if the RLC layer entity of the communication device determines that the first data packet is received for the first time, the RLC SN window is moved. Similarly, the PDCP layer entity of the communication device moves the window of the PDCP SN if it determines that the first data packet is received for the first time.

By adopting the method, when the first data packet is received for the first time, the windows of the RLC SN and the PDCP SN are moved, if the first data packet is not received for the first time, the windows of the RLC SN and the PDCP SN are not moved any more, so that the error caused by moving the windows for the same data packet for many times is avoided.

In a second aspect, an embodiment of the present application provides a data transmission method, which may be applied to a communication device, in which the communication device creates a first data packet and transmits the first data packet; the first packet supports error delivery.

By adopting the method, the first data packet supports error delivery, so that the receiving end equipment can execute the error delivery on the first data packet after receiving the first data packet, thereby effectively utilizing the data packet already received by the receiving end equipment and meeting the transmission requirement of the service.

In one possible design, the first data packet supports error delivery, including at least one of: the service to which the first data packet belongs supports error delivery; the cell transmitting the first data packet supports error delivery; the first data packet includes data from at least one logical channel, and the at least one logical channel partially or completely supports error delivery.

In one possible design, the method further includes: the communication device receives first indication information, wherein the first indication information is used for indicating that the first resource supports error delivery; the communication device transmits a first data packet, comprising: the communication device transmits a first data packet on a first resource.

In one possible design, the communication device receives first indication information, including: the communication device receives an uplink authorization, wherein the uplink authorization is used for indicating a first resource and carries first indication information; or the communication device receives first configuration information, wherein the first configuration information is used for configuring a first resource and carries first indication information; or, the communication device receives control information, where the control information is used to activate the first resource, and the control information carries the first indication information.

In one possible design, the method further includes: the communication device sends second indication information for indicating that the first data packet supports error delivery.

By adopting the mode, after the terminal equipment constructs the data packet, if the constructed data packet is determined to support the error submission, the terminal equipment can indicate the data packet to support the error submission to the network equipment, namely, the terminal equipment can determine whether the transmission supports the error submission, so that when the network equipment allocates resources, the network equipment does not need to indicate whether the data carried by the resources support the error submission, and the processing burden of the network equipment is reduced.

In one possible design, the second indication information is used to indicate that the first packet supports error delivery when the first packet conforms to at least one of the following: the decoding accuracy of the first data packet is greater than a first threshold value; the retransmission times of the first data packet are larger than a second threshold value; the timer corresponding to the first data packet is expired.

In one possible design, the communication device sends the first data packet and the second indication information, and includes: the communication device transmits the first data packet and the second indication information on the first resource.

In one possible design, the communication device sends the first data packet and the second indication information on the first resource, including: the communication device punches the first data packet and sends the punched first data packet and the second indication information on the first resource; alternatively, the communication device jointly encodes the first packet and the second indication information and transmits the jointly encoded information on the first resource.

In one possible design, the method further includes: the communication device receives second configuration information indicating whether the one or more logical channels support error delivery.

In one possible design, the first data packet is carried on the second resource; the method further comprises the following steps: the communication device transmits third indication information, wherein the third indication information is used for indicating that the second resource supports error delivery.

In one possible design, the communication device is a DU, and the method further includes: and receiving fourth indication information from the CU, wherein the fourth indication information is used for indicating whether the one or more logical channels support error delivery.

In one possible design, the communication device transmits a first data packet, including: the MAC layer entity of the communication device delivers the first data packet and fifth indication information to the physical layer entity, wherein the fifth indication information is used for indicating the position of at least one of an SDAP (data base protocol access protocol) head, a PDCP (packet data convergence protocol) head, an RLC (radio link control) head and an MAC (media access control) head of the first data packet in the first data packet; and the physical layer entity of the communication device sends the first data packet according to the fifth indication information.

By adopting the mode, the MAC layer informs the physical layer of the positions of the SDAP header, the PDCP header, the RLC header and the MAC header in the first data packet, namely, which bits in the first data packet are more important, so that the successful transmission of the bits at the positions of the SDAP header, the PDCP header, the RLC header and the MAC header is preferentially ensured when the physical layer transmits the first data packet.

In one possible design, the first data packet includes one PDCP SDU or one PDCP SDU fragment.

By adopting the method, after receiving the first data packet submitted by the MAC layer, the physical layer can know the positions of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet (for example, the SDAP header, the PDCP header, the RLC header, and the MAC header are distributed at the front part of the first data packet), and thus when transmitting the first data packet, the successful transmission of bits at the positions of the SDAP header, the PDCP header, the RLC header, and the MAC header is preferentially ensured, that is, the previous bits are preferentially ensured to be correctly transmitted.

In a third aspect, an embodiment of the present application provides a communication system, where the communication system includes a network device and a core network device; wherein the network device is configured to perform the method as described in some possible designs of the first or second aspects above.

In one possible design, the core network device is configured to send service information of one or more services to the network device; the one or more services include a first service, and the service information of the first service includes at least one of the following: a delay budget for the first service; the error submission instruction of the first service is used for indicating whether the first service supports the error submission; and indicating the error delivery of one or more data flows corresponding to the first service, wherein the error delivery indication of the data flows is used for indicating whether the data flows support the error delivery.

In a fourth aspect, the present application provides a communication apparatus, which may be a terminal device (or a chip disposed inside the terminal device) or a network device (or a chip disposed inside the network device). The communication device has a function of implementing the first aspect or the second aspect, for example, the communication device includes a module or a unit or means (means) corresponding to the step of executing the first aspect or the second aspect, and the function or the unit or the means may be implemented by software, or implemented by hardware executing corresponding software.

In one possible design, the communication device includes a processing unit, a communication unit, wherein the communication unit may be used for transceiving signals to realize communication between the communication device and other devices; the processing unit may be adapted to perform some internal operations of the communication device. The functions performed by the processing unit and the communication unit may correspond to the steps referred to in the first aspect or the second aspect.

In one possible design, the communication device includes a processor, and may further include a transceiver for transceiving signals, and the processor executes program instructions to implement the method in any possible design or implementation manner of the first aspect or the second aspect. Wherein the communications apparatus can further include one or more memories for coupling with the processor. The one or more memories may be integrated with the processor or separate from the processor, which is not limited in this application. The memory may hold the necessary computer programs or instructions to implement the functions referred to in the first or second aspect above. The processor may execute a computer program or instructions stored by the memory that, when executed, causes the communication device to implement the method of any possible design or implementation of the first or second aspects described above.

In one possible design, the communication device includes a processor and a memory, and the memory can hold necessary computer programs or instructions to implement the functions referred to in the first or second aspect. The processor may execute a computer program or instructions stored by the memory that, when executed, causes the communication device to implement the method of any possible design or implementation of the first or second aspects described above.

In one possible design, the communication device includes at least one processor and an interface circuit, where the at least one processor is configured to communicate with other devices through the interface circuit and to perform the method of any possible design or implementation of the first aspect or the second aspect.

In a fifth aspect, the present application provides a computer-readable storage medium having computer-readable instructions stored thereon which, when read and executed by a computer, cause the computer to perform the method of any one of the possible designs of the first or second aspects described above.

In a sixth aspect, the present application provides a computer program product which, when read and executed by a computer, causes the computer to perform the method of any one of the possible designs of the first or second aspects described above.

In a seventh aspect, the present application provides a chip comprising a processor, coupled with a memory, for reading and executing a software program stored in the memory to implement the method in any one of the possible designs of the first or second aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

FIG. 1a is a schematic diagram of a possible system architecture suitable for use in embodiments of the present application;

FIG. 1b is a schematic diagram of another network architecture suitable for use in the embodiments of the present application;

FIG. 1c is a schematic diagram of another network architecture suitable for use in the embodiments of the present application;

fig. 2a is a schematic diagram illustrating transmission of downlink data between layers according to an embodiment of the present application;

fig. 2b is a schematic diagram of data transmission between a sending end device and a receiving end device according to an embodiment of the present application;

fig. 2c is a schematic diagram of a decoding and HARQ feedback process of a receiving end device according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating a data transmission method according to an embodiment of the present application;

fig. 4 is a schematic diagram of error delivery of an HARQ entity according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a data transmission method according to a second embodiment of the present application;

FIG. 6 is a possible exemplary block diagram of the devices involved in the embodiments of the present application;

fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments.

First, some terms in the embodiments of the present application are explained so as to be easily understood by those skilled in the art.

(1) The terminal equipment: may be a wireless terminal device capable of receiving network device scheduling and indication information, which may be a device providing voice and/or data connectivity to a user, or a handheld device having wireless connection capability, or other processing device connected to a wireless modem. The terminal devices, which may be mobile terminal devices such as mobile telephones (or "cellular" telephones), computers, and data cards, for example, mobile devices that may be portable, pocket, hand-held, computer-included, or vehicle-mounted, may communicate with one or more core networks or the internet via a radio access network (e.g., a RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), tablet computers (pads), and computers with wireless transceiving functions. A wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a Mobile Station (MS), a remote station (remote station), an Access Point (AP), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), a Subscriber Station (SS), a user terminal device (CPE), a terminal (terminal), a User Equipment (UE), a Mobile Terminal (MT), etc. The terminal device may also be a wearable device and a next generation communication system, for example, a terminal device in a 5G communication system or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, etc.

(2) A network device: may be a device in a wireless network, for example, a network device may be a Radio Access Network (RAN) node (or device) that accesses a terminal to the wireless network, which may also be referred to as a base station. Currently, some examples of RAN equipment are: a new generation base station (gbodeb), a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved NodeB or HNB), a Base Band Unit (BBU), a wireless fidelity (Wi-Fi) access point (access point, AP), a roadside unit (iau), a converged access backhaul (tsap), a control Node in a terminal network, and the like in a 5G communication system. In addition, in one network configuration, the network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node. Furthermore, the network device may be other means for providing wireless communication functionality for the terminal device, where possible. The embodiments of the present application do not limit the specific technologies and the specific device forms used by the network devices. For convenience of description, in this embodiment of the present application, a device that provides a wireless communication function for a terminal device is referred to as a network device.

(3) The terms "system" and "network" in the embodiments of the present application may be used interchangeably. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a alone, A and B together, and B alone, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC.

And, unless otherwise specified, the embodiments of the present application refer to the ordinal numbers such as "first", "second", etc., for distinguishing between a plurality of objects, and do not limit the sequence, timing, priority or importance of the plurality of objects. For example, the first terminal device and the second terminal device are only used for distinguishing different terminal devices, and do not indicate the difference of the priority or importance of the two terminal devices.

Fig. 1a is a schematic diagram of a network architecture applicable to the embodiment of the present application. As shown in fig. 1a, the terminal device 130 may access a wireless network to obtain services of an external network (e.g., the internet) through the wireless network, or may communicate with other devices through the wireless network, such as may communicate with other terminal devices. The wireless network includes a Radio Access Network (RAN) device 110 and a Core Network (CN) device 120, where the RAN device 110 is configured to access a terminal device 130 to the wireless network, and the CN device 120 is configured to manage the terminal device and provide a gateway for communicating with an external network. It should be understood that the number of each device in the communication system shown in fig. 1a is only an illustration, and the embodiment of the present application is not limited thereto, and in practical applications, more terminal devices 130, more RAN devices 110, and other devices may also be included in the communication system.

The CN may include a plurality of CN devices 120, and when the network architecture shown in fig. 1a is applicable to a 5G communication system, the CN devices 120 may be access and mobility management function (AMF) entities, Session Management Function (SMF) entities, User Plane Function (UPF) entities, or the like, and in this embodiment, the CN devices 120 are used as UPF entities. Illustratively, the interface between terminal device 130 and RAN device 110 may be referred to as a Uu interface or air interface, and the interface between RAN device 110 and the UPF entity may be referred to as an N3 interface.

Fig. 1b is a schematic diagram of another network architecture applicable to the embodiment of the present application. As shown in fig. 1b, the network architecture includes CN devices, RAN devices, and terminal devices. The RAN device includes a baseband device and a radio frequency device, where the baseband device may be implemented by one node or by multiple nodes, and the radio frequency device may be implemented independently by being pulled away from the baseband device, may also be integrated in the baseband device, or may be partially pulled away and partially integrated in the baseband device. For example, in an LTE communication system, a RAN equipment (eNB) includes a baseband device and a radio frequency device, where the radio frequency device may be remotely located with respect to the baseband device, e.g., a Remote Radio Unit (RRU) is remotely located with respect to a BBU. Also for example, in an evolved structure, a RAN device may include a CU and a DU, a plurality of DUs may be centrally controlled by one CU, and an interface between the CU and the DU may be referred to as an F1-U interface.

Fig. 1c is a schematic diagram of another network architecture applicable to the embodiment of the present application. With respect to the network architecture shown in fig. 1b, fig. 1c may also be implemented by separating a Control Plane (CP) and a User Plane (UP) of a CU into different entities, namely, a Control Plane (CP) CU entity (i.e., a CU-CP entity) and a User Plane (UP) CU entity (i.e., a CU-UP entity).

In the above network architecture, the signaling generated by the CU may be sent to the terminal device through the DU, or the signaling generated by the terminal device may be sent to the CU through the DU. The DU may pass through the protocol layer encapsulation directly to the terminal device or CU without parsing the signaling. In the following embodiments, if transmission of such signaling between the DU and the terminal device is involved, in this case, the transmission or reception of the signaling by the DU includes such a scenario. For example, the signaling of a Radio Resource Control (RRC) layer or a Packet Data Convergence Protocol (PDCP) layer is finally processed into the signaling of a physical layer and sent to the terminal device, or is converted from the received signaling of the physical layer. Under this architecture, the signaling of the RRC or PDCP layer can also be considered as being sent by the DU, or sent by the DU and the radio bearer.

The network architecture illustrated in fig. 1a, 1b or 1c may be applied to communication systems of various Radio Access Technologies (RATs), such as a 5G (or new radio, NR) communication system, and may also be a future communication system. The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the communication network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The apparatus in the following embodiments of the present application may be located in a terminal device or a network device according to the functions implemented by the apparatus. When the above structure of CU-DU is adopted, the network device may be a CU, or a DU, or a RAN device including a CU and a DU.

In the network architecture illustrated in fig. 1a, fig. 1b or fig. 1c, the communication between the network device and the terminal device may follow a certain protocol layer structure, for example, the control plane protocol layer structure may include functions of protocol layers such as an RRC layer, a PDCP layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer and a physical layer (PHY); the user plane protocol layer structure can comprise functions of protocol layers such as a PDCP layer, an RLC layer, an MAC layer, a physical layer and the like; in a possible implementation, a Service Data Adaptation (SDAP) layer may be further included above the PDCP layer. Illustratively, the network device may implement the functions of the protocol layers of RRC, PDCP, RLC, and MAC by one node, or may implement the functions of these protocol layers by a plurality of nodes. For example, if the network device includes CU and DU, the CU and DU may be divided according to protocol layers of the wireless network, for example, functions of PDCP layer and above protocol layers are set in the CU, and functions of protocol layers below the PDCP layer, for example, RLC layer and MAC layer, are set in the DU. This division of the protocol layers is only an example, and it is also possible to divide the protocol layers at other protocol layers, for example, at the RLC layer, and the functions of the RLC layer and the protocol layers above are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; alternatively, the functions may be divided into some protocol layers, for example, a partial function of the RLC layer and a function of a protocol layer above the RLC layer may be provided in the CU, and the remaining function of the RLC layer and a function of a protocol layer below the RLC layer may be provided in the DU. In addition, the processing time may be divided in other manners, for example, by time delay, a function that needs to satisfy the time delay requirement for processing is provided in the DU, and a function that does not need to satisfy the time delay requirement is provided in the CU.

Taking data transmission between a network device and a terminal device as an example, the data transmission needs to pass through a user plane protocol layer, such as an SDAP layer, a PDCP layer, an RLC layer, an MAC layer, and a physical layer, wherein the SDAP layer, the PDCP layer, the RLC layer, the MAC layer, and the physical layer may also be collectively referred to as an access layer. The data transmission method is divided into transmission and reception according to the data transmission direction, and each layer is divided into a transmission part and a reception part. For the following data transmission as an example, referring to fig. 2a, a schematic diagram of downlink data transmission between layers is shown, where a downward arrow in fig. 2a indicates data transmission, and an upward arrow indicates data reception. After the PDCP layer obtains data from an upper layer, the PDCP layer transmits the data to the RLC layer and the MAC layer, and the MAC layer generates a Transport Block (TB), and performs wireless transmission through a physical layer. Data is correspondingly encapsulated in each layer, data received by a layer from an upper layer of the layer is regarded as a Service Data Unit (SDU) of the layer, and the PDU is formed after layer encapsulation and then transmitted to a next layer. For example, data received by the PDCP layer from an upper layer is called PDCP SDU, and data transmitted by the PDCP layer to a lower layer is called PDCP PDU; data received by the RLC layer from an upper layer is called RLC SDU, and data sent by the RLC layer to a lower layer is called RLC PDU; data received by the MAC layer from an upper layer is referred to as MAC SDU, data transmitted by the MAC layer to a lower layer is referred to as MAC PDU, which may also be referred to as transport block. In the protocol, the inter-layer relation is mostly corresponded in a channel mode. The RLC layer corresponds to the MAC layer through a Logical Channel (LCH), the MAC layer corresponds to the physical layer through a transport channel (transport channel), and the physical layer is referred to as a physical channel (physical channel) below the MAC layer and corresponds to the other physical layer.

Exemplarily, according to fig. 2a, it can also be seen that the terminal device further has an application layer and a non-access layer; the application layer may be configured to provide services to an application program installed in the terminal device, for example, downlink data received by the terminal device may be sequentially transmitted to the application layer by the physical layer, and then provided to the application program by the application layer; for another example, the application layer may obtain data generated by the application (e.g., a video recorded by a user using the application), and sequentially transmit the data to the physical layer for transmission to other communication devices. The non-access stratum may be used to forward user data, such as to forward uplink data received from the application layer to the SDAP layer or to forward downlink data received from the SDAP layer to the application layer.

Referring to fig. 2b, one or more sub-functional entities or modules, such as a multiplexing or demultiplexing entity, a hybrid automatic repeat request (HARQ) entity, and an encoding or decoding entity, may be included in the MAC layer. One or more sub-functional entities or modules, such as a Cyclic Redundancy Check (CRC) check module, may also be included in the physical layer. The sub-functional entities or modules are introduced from the perspective of the sending end device and the receiving end device, respectively. The sending end device can be a terminal device, and the receiving end device can be a network device; alternatively, the sending end device may be a network device, and the receiving end device may be a terminal device.

For the sending end device, the MAC layer may include a multiplexing entity, an HARQ entity, and a coding entity. The multiplexing entity can be used for multiplexing the RLC PDU received from the RLC layer to obtain an MAC PDU and submitting the MAC PDU to the HARQ entity; one RLC layer entity corresponds to one logical channel, and an RLC PDU may also be referred to as a MAC SDU. The multiplexing may be performed in various ways, such as segmentation and concatenation. For example, the multiplexing entity may segment the RLC PDU received from the logical channel 1, for example, into two RLC PDU segments, that is, RLC PDU segment 1 and RLC PDU segment 2, and further obtain MAC PDU1 according to RLC PDU segment 1 and obtain MAC PDU2 according to RLC PDU segment 2. For another example, the multiplexing entity may cascade the RLC PDU1 received from the logical channel 1 and the RLC PDU2 received from the logical channel 2, and further obtain an MAC PDU according to the cascaded RLC PDU1 and RLC PDU 2; RLC PDUs of different logical channels can be distinguished by a logical channel identification (LCH ID) in the MAC PDU header. Fig. 2b illustrates an example of cascade connection in a multiplexing manner. Further, the HARQ entity may submit the MAC PDU received from the multiplexing entity to the coding entity, and then the coding entity performs coding, and then transmits the coded MAC PDU to the physical layer. Furthermore, the CRC check module in the physical layer performs CRC check processing on the MAC PDU received from the MAC layer, and transmits the MAC PDU to the receiving end device.

For the receiving end device, after receiving the data, the CRC module in the physical layer may perform CRC check on the data, and if the check is passed, the data may be delivered to the MAC layer. The MAC layer may include a demultiplexing entity, an HARQ entity, and a decoding entity, and the decoding entity in the MAC layer may decode the MAC PDU after receiving the MAC PDU submitted by the physical layer, and if the decoding is correct, the MAC PDU may be submitted to the HARQ entity, and then the HARQ entity submits to the demultiplexing entity, and the HARQ entity may also send HARQ feedback information. Further, after receiving the MAC PDU, the demultiplexing entity may demultiplex to obtain MAC SDU, and deliver the MAC SDU to the RLC layer through a corresponding logical channel.

The decoding and HARQ feedback process of the receiving end device will be described in detail with reference to fig. 2 c.

Fig. 2c is a schematic diagram of a possible decoding and HARQ feedback process of a receiving end device, and as shown in fig. 2c, the process may include three parts, where a first part is a decoding entity performing a decoding operation, a second part is a decoding entity submitting data to an HARQ entity, and a third part is the HARQ entity sending HARQ feedback information.

Step 201, determining whether the received data is newly transmitted data, if so, executing step 202, and if not, executing step 203.

Step 202, decode the data and execute step 205.

Step 203, determining whether the decoding is not successful, if the decoding is not successful, executing step 204, and if the decoding is successful, the decoding can be stopped.

Step 204, merging and decoding the data and the previous data, and executing step 205.

Step 205, determine whether the decoding is successful, if the decoding is failed, execute step 206, if the decoding is successful, execute step 207.

Step 206, determine whether the decoding was successful, if yes, go to step 208, otherwise go to step 207.

Step 207, updating the data stored in the HARQ buffer, and executing step 211.

In step 208, it is determined whether the broadcast data is broadcast data, if so, step 210 is executed, and if not, step 209 is executed.

Step 209 determines whether the decoding is successful for the first time, if so, step 210 is executed, and if not, step 211 is executed.

In step 210, the decoding result is submitted to the upper layer (i.e. the demultiplexing entity in fig. 2 b), and step 211 is executed.

In step 211, it is determined whether the feedback condition is satisfied, if yes, step 213 is executed, and if not, step 212 is executed.

Wherein, not meeting the feedback condition may mean meeting at least one of the following: (1) the data is data scheduled by a Physical Downlink Control Channel (PDCCH) scrambled by a temporary cell-radio network temporary identifier (TC-RNTI); (2) the data is broadcast data; (3) timing advance is invalid.

For example, in (1) above, the TC-RNTI may be a temporary identifier allocated by the network device for the terminal device. In the above (2), the data is broadcast data, and it can be understood that the data is data transmitted by a broadcast method. In the above (3), the network device may send the timing advance command to the terminal device, for example, the network device may estimate the timing advance of the terminal device according to the random access preamble sent by the terminal device, and then send the timing advance command to the terminal device; accordingly, the terminal device can obtain the timing advance according to the timing advance command. The network device starts a timing advance timer (TA timer) after sending a timing advance command to the terminal device, the terminal device also starts a same TA timer after obtaining the timing advance, the network device and the terminal device both maintain the TA timer, and whether the timing advance is effective can be judged according to whether the TA timer is overtime. If the TA timer does not time out, the timing advance is considered to be valid, otherwise, the timing advance is considered to be invalid.

In step 212, the HARQ entity does not inform the physical layer to send HARQ feedback information.

In step 213, the HARQ entity notifies the physical layer to send HARQ feedback information.

According to the above, since the data may have errors during the transmission process, the transmitted data may be monitored by encoding and decoding, CRC check, and the like. For example, the sending end device may multiplex data of one or more services into the same transport block, perform HARQ process processing, perform coding, add CRC check, and then send the data to the receiving end device. After receiving the data, the receiver can perform CRC check, decode the data after the CRC check is successful, if the decoding is successful, the data transmission is correct, and the data can be submitted to an upper layer; if the CRC does not pass or the decoding fails, the data transmission is wrong, the data is not submitted to the upper layer, and after the retransmitted data arrives, the combined decoding is carried out until the decoding is successful, and the data is not submitted to the upper layer. In this way, the receiving end device can submit the data block to the upper layer under the condition of determining that the data transmission is correct, so that the requirement of the service with higher fault tolerance requirement can be effectively met.

However, with the development of wireless communication networks, applications that can be supported are more and more abundant and diverse, such as services that can support more and more high-precision voice, high-definition video, and the like. The data volume of these services is very large, the requirement on the time delay of the data is high, after a data packet transmission error occurs, if the data packet is not delivered to an upper layer but is discarded or waits for retransmission, on one hand, the data packet already received by a receiving end device is not fully utilized, which may result in resource waste, and on the other hand, because the time delay requirement of the service is relatively high, discarding the data packet with the transmission error or waiting for retransmission may result in poor user experience, for example, in the case of a high definition video service, a video pause phenomenon may occur when a user watches a video.

Therefore, even if the data packet is transmitted incorrectly, the data packet can be considered to be continuously submitted to the upper layer, in this case, although some mosaic phenomenon may still occur on the video due to the fact that the application layer cannot be completely and correctly decoded due to the data packet transmission error, compared with the video jamming caused by the method, the received data packet can be effectively utilized, and the user experience can be improved. That is, for services similar to high-precision voice, high-definition video, and the like, since the delay requirement of the data is high and the fault tolerance requirement is low, it may be considered that the data packet is still submitted to the upper layer after the transmission error, that is, the error submission is executed. The high requirement on the time delay can be understood as that if the data packet arrives within a certain time, the data packet is useful for the receiving end device, otherwise, the data packet is not useful; the data packet with low fault tolerance requirement, which can be understood as an error in the transmission process, is also useful for the receiving end equipment.

Further, an embodiment of the present application provides a data transmission method, which is used to implement error delivery of a data packet, so as to effectively utilize the data packet that has been received by a receiving end device, and meet a transmission requirement of a service.

The data transmission method provided by the embodiment of the application may relate to interaction between two communication devices, for example, a first communication device and a second communication device, where the first communication device may be a sending end device, and the second communication device is a receiving end device; alternatively, the second communication apparatus may be a sending end device, and the first communication apparatus is a receiving end device. Further, the first communication device may be a network device or a communication device capable of supporting the network device to implement the functions required by the method, but may also be other communication devices, such as a chip or a system of chips. The second communication means may be a terminal device or a communication means capable of supporting the terminal device to implement the functions required by the method, but may of course also be other communication means, such as a chip or a system of chips. For convenience of introduction, in the following, the method is taken as an example executed by a network device and a terminal device, that is, the first communication apparatus is taken as a network device, and the second communication apparatus is taken as a terminal device.

When the first communication device is a network device and the second communication device is a terminal device, the communication between the terminal device and the network device may include uplink communication and downlink communication. In the uplink communication, the terminal device may create a data packet, the data packet supports error delivery, and send the data packet to the network device, and if the data packet is transmitted in error, the network device may perform error delivery. In the downlink communication, the network device may create a data packet, the data packet supports error delivery, and send the data packet to the terminal device, and if the data packet is transmitted in error, the terminal device may perform error delivery. The following describes in detail the case of uplink communication and downlink communication with reference to the first embodiment and the second embodiment, respectively.

It should be noted that: (1) in other possible embodiments, the first communication device and the second communication device may also be other possible devices, for example, the first communication device is a first terminal device, and the second communication device is a second terminal device, in this case, the first terminal device may create a data packet, the data supports error delivery, and send the data packet to the second terminal device, and if the data packet is transmitted incorrectly, the second terminal device may perform error delivery; or, the second terminal device may create a data packet, where the data packet supports error delivery, and send the data packet to the first terminal device, and if the data packet is transmitted in error, the first terminal device may perform error delivery.

(2) In this embodiment of the application, communication between the network device and the terminal device (or between the first terminal device and the second terminal device) may be performed through a licensed spectrum (licensed spectrum), may also be performed through an unlicensed spectrum (unlicensed spectrum), and may also be performed through both the licensed spectrum and the unlicensed spectrum, which is not limited herein. The network device and the terminal device can communicate through a frequency spectrum smaller than 6 gigahertz (GHz), or through a frequency spectrum larger than or equal to 6GHz, or simultaneously use the frequency spectrum smaller than 6GHz and the frequency spectrum larger than or equal to 6 GHz. That is, the present application is applicable to both low frequency scenarios (e.g., sub 6G) and high frequency scenarios (greater than or equal to 6G). The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

Example one

In embodiment one, some possible implementations will be described for the uplink communication scenario.

Fig. 3 is a schematic flowchart corresponding to a data transmission method provided in an embodiment of the present application, and as shown in fig. 3, the method includes:

step 301, the network device sends configuration information 1 to the terminal device.

Accordingly, in step 302, the terminal device receives configuration information 1 from the network device.

Illustratively, configuration information 1 may be used to configure at least one of: whether one or more services supported by the terminal equipment support errors; whether one or more cells support false deliveries; whether one or more logical channels support error delivery. The configuration information 1 is described in detail below with reference to example 1 and example 2.

Example 1

The terminal device may support one or more services, and different services may have different requirements, for example, some services may require that data packets must be transmitted correctly at the receiving end for onward delivery, and some services may tolerate erroneous delivery. Thus, configuration information 1 may be used to configure whether one or more services support error delivery. For example, configuration information 1 is used to configure service a to support error delivery and service B not to support error delivery.

For example, the configuration information 1 may configure whether the one or more services support error delivery in various ways, for example, the configuration information 1 may configure whether the one or more services support error delivery by configuring whether logical channels corresponding to the one or more services support error delivery. For example, the service a corresponds to the logical channel 1, the service B corresponds to the logical channel 2, the configuration information 1 may configure the logical channel 1 to support error delivery, and the logical channel 2 does not support error delivery, and then the terminal device may know whether the service supports error delivery according to whether the logical channel corresponding to the service supports error delivery. For example, the logical channel 1 corresponding to the service a supports error delivery, and then the service a supports error delivery; the logical channel 2 corresponding to the service B does not support error delivery, and further the service B does not support error delivery.

There may be various ways in which the network device determines whether one or more services support error delivery. In one possible implementation, the network device receives service information of one or more services from the core network device; taking the service a as an example, the service information of the service a includes at least one of the following items: the service A comprises a delay budget and an error delivery indication of the service A, wherein the error delivery indication is used for indicating whether the service A indicates error delivery. If the service information of the service a includes the error delivery indication, the network device may determine whether the service a indicates the error delivery according to the error delivery indication; if the service information of the service a includes the delay budget of the service a, the network device may determine whether the service a supports the error delivery according to the delay budget of the service a.

In this example, configuration information 1 may also be used to configure whether one or more cells support error delivery, and see table 1 for the support classification of error delivery by service and cell.

Table 1: service and cell support classification for error delivery

As can be seen from table 1, if configuration information 1 configures that service a supports error delivery, service B does not support error delivery, and also configures that cell 1 supports error delivery, service a supports error delivery in cell 1, and service B does not support error delivery in cell 1. For another example, if configuration information 1 configures that service a does not support error delivery, service B does not support error delivery, and also configures that cell 1 does not support error delivery, service a does not support error delivery in cell 1, and service B does not support error delivery in cell 1.

Example 2

The terminal device may support one or more services, and data of each service may be mapped into one or more data flows (flows), and for the same service, some data flows may support error delivery and some data flows may not support error delivery. In this case, the configuration information 1 may be used to configure whether one or more data streams support error delivery, and further, since there is a corresponding relationship between the data streams and the logical channels, it may also be understood that the configuration information 1 is used to configure whether one or more logical channels support error delivery. For example, data of service a may be mapped to data flow a1 and data flow a2, data flow a1 supports error delivery, data flow a2 does not support error delivery, data flow a1 corresponds to logical channel 1, and data flow a2 corresponds to logical channel 2, in which case, configuration information 1 may configure logical channel 1 to support error delivery and logical channel 2 does not support error delivery. For another example, the data packet in service B may be mapped to data flow B3 and data flow B4, neither data flow B3 nor data flow B4 may support error delivery, and data flow B3 and data flow B4 may correspond to the same logical channel, for example, logical channel 3, in this case, configuration information 1 may configure logical channel 3 not to support error delivery.

There may be various ways in which the network device determines whether one or more data streams support error delivery. In one possible implementation, the network device receives service information of one or more services from the core network device; taking the service a as an example, the service information of the service a includes an error delivery indication of one or more data flows (such as the data flow a1 and the data flow a2) corresponding to the service a, for example, the error delivery indication of the data flow a1 is used to indicate whether the data flow a1 supports error delivery.

It should be noted that the service a or the service B may be understood as a service of the same service type, or may also be understood as a certain service, and is not limited specifically.

Step 303, the terminal device builds a first data packet, and the first data packet supports error delivery.

Here, the terminal device constructs the first data packet, and it is understood that the multiplexing entity in the MAC layer of the terminal device multiplexes the data received from the at least one logical channel to obtain the first data packet.

Illustratively, the terminal device may compose a data packet (e.g., a first data packet) according to the configuration information 1, for example, the terminal device may compose the data packet according to at least one of whether the service supports error delivery, whether the cell supports error delivery, and whether the logical channel supports error delivery. For example, when the configuration information 1 is the configuration information 1 described in the above example 2, when the terminal device constructs a data packet, if a serving cell of the terminal device (which may also be understood as a cell for transmitting the data packet constructed by the terminal device) supports error delivery, the terminal device may try to construct data in at least one logical channel that supports error delivery into the same data packet, and try to construct data in at least one logical channel that does not support error delivery into the same data packet; or, the terminal device may try not to group the data of the logical channel that supports the error delivery and the data of the logical channel that does not support the error delivery into the same data packet.

In an embodiment of the present application, the first data packet supports error delivery, and may include at least one of the following: the service to which the first data packet belongs supports error delivery; the cell transmitting the first data packet supports error delivery; at least one logical channel supports error delivery, partially or fully. For example, the service to which the first data packet belongs is service a, and if the service a supports error delivery, the first data packet supports error delivery. For another example, the service to which the first data packet belongs is service a, and if service a supports error delivery and the cell transmitting the first data packet supports error delivery, the first data packet supports error delivery. For another example, the first data packet includes data from at least one logical channel, and the first data packet supports error delivery if all of the at least one logical channel supports error delivery. For another example, the first data packet includes data from at least one logical channel, and if a part of the logical channels of the at least one logical channel support error delivery, the first data packet supports error delivery. In other possible examples, the first data packet includes data from at least one logical channel, and the first data packet may not support error delivery if a portion of the at least one logical channel does not support error delivery.

Step 304, the terminal device sends a first data packet to the network device.

Accordingly, in step 305, the network device receives a first data packet from the terminal device.

Here, after the MAC layer of the terminal device creates the first data packet, the MAC layer may record the location of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet, and notify the physical layer, for example, the MAC layer may deliver the first data packet and indication information a to the physical layer, where the indication information a is used to indicate the location of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet. Accordingly, after receiving the first data packet and the indication information a, the physical layer may preferentially ensure successful transmission of bits at positions where the SDAP header, the PDCP header, the RLC header, and the MAC header are located when transmitting the first data packet.

Illustratively, the MAC layer informs the physical layer of the location of the SDAP header, PDCP header, RLC header, MAC header in the first packet, it being understood that the MAC layer informs or tells the physical layer which bits in the first packet are important. It is described here that the MAC layer informs the physical layer, and in other possible implementations, the rules may be configured in advance by the network device and sent to the terminal device. The rule may be used to characterize which bits in packets of different sizes are important, for example, if the size of a packet is a, the first X1 bits in the packet are important, and if the size of a packet is B, the first X2 bits in the packet are important. The terminal equipment can deduce which bits are important for each size of data packet according to the rule, and then can build the data packet according to the rule. The subsequent network device receives the data packet from the terminal device, and before decoding the data packet, the subsequent network device can determine which bits in the data packet are more important according to the rule and the size of the data packet, so that the successful decoding of the more important bits is preferentially ensured.

It should be noted that, if the terminal device determines that the first data packet to be transmitted needs to perform error delivery (for example, the network device schedules the first resource to the terminal device and indicates that the first resource supports error delivery, and the terminal device constructs the first data packet to be transmitted on the first resource, in this case, the terminal device may determine that the first data packet to be transmitted needs to perform error delivery), the terminal device may perform the construction in a segmentation manner when constructing the first transmission packet, and further, the first data packet may include one PDCP SDU or one PDCP SDU fragment; or that the first data packet may include one RLC SDU or one RLC SDU fragment; or that one MAC SDU or one MAC SDU fragment can be included in the first data packet. Under the situation, after receiving the first data packet delivered by the MAC layer, the physical layer can obtain the positions of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet (for example, the SDAP header, the PDCP header, the RLC header, and the MAC header are distributed at the front of the first data packet), and thus when transmitting the first data packet, the physical layer preferentially ensures the successful transmission of bits at the positions of the SDAP header, the PDCP header, the RLC header, and the MAC header, that is, preferentially ensures the correct transmission of the previous bits. By adopting the mode, when the MAC layer submits the first data packet to the physical layer, the position of the SDAP header, the PDCP header, the RLC header and the MAC header in the first data packet can be indicated without submitting the indication information a.

In this embodiment, the sending of the first data packet by the terminal device to the network device may be data transmission based on scheduling, or may also be data transmission without scheduling Grant (GF). Among them, the exempt scheduling grant may also be referred to as a Configured Grant (CG).

In the data transmission based on the scheduling, the network device may send an Uplink (UL) grant to the terminal device, where the uplink grant is used to indicate the first resource, and accordingly, after receiving the uplink grant, the terminal device may send the first data packet on the first resource. For example, if the terminal device determines that the first data packet needs to be sent, the terminal device may send a Scheduling Request (SR) to the network device on a Physical Uplink Control Channel (PUCCH), and then the network device may send an uplink grant to the terminal device after receiving the SR.

In the data transmission without scheduling permission, the network device may pre-configure a periodic resource, and when the terminal device needs to send the first data packet, the terminal device may send the first data packet through the pre-configured first resource. The network device pre-configures periodic resources into two types, where Type 1(Type 1) refers to that the network device configures a period and a start offset through configuration information 2 and indicates a specific resource location, and unless the terminal device receives a release command, the resource may be considered to appear periodically. Type 2(Type 2) means that the network device configures a period and a start offset through configuration information 3, and then activates and indicates a specific resource (for example, indicates a time domain position and a frequency domain position of the resource) through Downlink Control Information (DCI) (referred to as DCI-1 for convenience of description), and unless the terminal device receives a deactivation command, it may consider that the resource indicated by DCI-1 appears periodically.

Some possible implementations of steps 303 to 305 are described below.

Implementation mode 1

The network device may indicate to the terminal device whether the data carried by the first resource supports error delivery. Correspondingly, according to the indication of the network device, if it is determined that the data carried by the first resource supports error delivery, the terminal device may construct a first data packet supporting error delivery (step 303), and carry the first data packet to the first resource and send the first data packet to the network device (step 304). In turn, the network device may receive a first data packet on a first resource (step 305). By adopting the implementation mode, the network equipment determines whether the transmission supports the error delivery or not by indicating whether the data carried by the first resource supports the error delivery or not, thereby increasing the regulation and control flexibility of the network equipment.

It should be noted that, in other possible embodiments, if it is determined that the data carried by the first resource does not support error delivery, the terminal device may also construct a data packet that does not support error delivery, and carry the data packet to the first resource and send the data packet to the network device. In the embodiment of the present application, a description is given by taking an example that data carried by a first resource supports error delivery.

There are various ways for the network device to indicate to the terminal device whether the data carried by the first resource supports error delivery. For example, (1) if the first resource is allocated to the terminal device by the network device through the uplink grant, in an example, the uplink grant may carry indication information 1, and the indication information 1 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the data carried by the first resource supports error delivery; if the value of the 1 bit is 0, it indicates that the data carried by the first resource does not support error delivery. In another example, if the uplink grant carries indication information 1, it indicates that the data carried by the first resource supports error delivery, and if the uplink grant does not carry indication information 1, it indicates that the data carried by the first resource does not support error delivery. Or, if the uplink grant carries the indication information 1, it indicates that the data carried by the first resource does not support error delivery, and if the uplink grant does not carry the indication information 1, it indicates that the data carried by the first resource supports error delivery.

(2) If the first resource is allocated to the terminal device by the network device in the type 1 manner, in an example, the configuration information 2 may carry indication information 1, and the indication information 1 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the data carried by the first resource supports error delivery; if the value of the 1 bit is 0, it indicates that the data carried by the first resource does not support error delivery. In another example, if the configuration information 2 carries the indication information 1, it indicates that the data carried by the first resource supports error delivery, and if the configuration information 2 does not carry the indication information 1, it indicates that the data carried by the first resource does not support error delivery. Or, if the configuration information 2 carries the indication information 1, it indicates that the data carried by the first resource does not support error delivery, and if the configuration information 2 does not carry the indication information 1, it indicates that the data carried by the first resource supports error delivery.

It should be noted that the configuration information 2 may be used to configure one set of resources or multiple sets of resources, for example, the configuration information 2 configures a period 1, a starting offset 1, a resource 1, a period 2, a starting offset 2, and a resource 2, so that the resource 1 that periodically appears according to the period 1 and the starting offset 1 may be understood as one set of resources, and the resource 2 that periodically appears according to the period 2 and the starting offset 2 may be understood as another set of resources. When the configuration information 2 is used for configuring multiple sets of resources, whether data carried by the multiple sets of resources support error delivery or not can be configured uniformly, that is, the data carried by the multiple sets of resources can all support error delivery or all do not support error delivery; for example, if the configuration information 2 carries the indication information 1, it indicates that the data carried by the multiple sets of resources all support error delivery, and if the configuration information 2 does not carry the indication information 1, it indicates that the data carried by the multiple sets of resources all support error delivery. Or, it may also be separately configured whether the data carried by each set of resources supports error delivery, for example, if the configuration information 2 configures two sets of resources, which are the first set of resources and the second set of resources respectively, the configuration information 2 carries the indication information 1a, which indicates that the data carried by the first set of resources supports error delivery, and the configuration information 2 does not carry the indication information 1a, which indicates that the data carried by the first set of resources does not support error delivery; if the configuration information 2 carries the indication information 1b, it indicates that the data carried by the second set of resources all support error delivery, and if the configuration information 2 does not carry the indication information 1b, it indicates that the data carried by the second set of resources all support error delivery.

(3) If the first resource is allocated to the terminal device by the network device in the type 2 manner, in an example, DCI-1 may carry indication information 1, where the indication information 1 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the data carried by the first resource supports error delivery; if the value of the 1 bit is 0, it indicates that the data carried by the first resource does not support error delivery. In another example, if indication information 1 is carried in DCI-1, it indicates that data of the first resource bearer supports error delivery, and if indication information 1 is not carried in DCI-1, it indicates that data of the first resource bearer does not support error delivery. Or, if the DCI-1 carries the indication information 1, it indicates that the data carried by the first resource does not support error delivery, and if the DCI-1 does not carry the indication information 1, it indicates that the data carried by the first resource supports error delivery.

Implementation mode 2

The terminal device creates a first data packet supporting error delivery (step 303), may bear the first data packet on the first resource and send the first data packet to the network device, and may further indicate to the network device whether the first data packet supports error delivery (step 304). In turn, the network device may receive a first data packet on a first resource (step 305). By adopting the implementation mode, after the terminal equipment builds the data packet, if the built data packet is determined to support the error submission, the terminal equipment can indicate the data packet to support the error submission to the network equipment, namely, the terminal equipment can determine whether the transmission supports the error submission, so that when the network equipment allocates resources, the network equipment does not need to indicate whether the data carried by the resources support the error submission, and the processing burden of the network equipment is reduced.

The manner of indicating, by the terminal device, whether the first data packet supports error delivery to the network device may be multiple, for example, the terminal device may indicate whether the first data packet supports error delivery through the indication information 2, and the indication information 2 may be Uplink Control Information (UCI).

In one example, the terminal device may transmit indication information 2 to the network device, and the indication information 2 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the first data packet supports error delivery; the value of the 1 bit is 0, which indicates that the first data packet does not support error delivery. In another example, if the terminal device sends the indication information 2 to the network device, it indicates that the first data packet supports error delivery, and if the indication information 2 is not sent to the network device, it indicates that the first data packet does not support error delivery.

For example, the terminal device may send the indication information 2 to the network device on the first resource, that is, the first data packet and the indication information 2 may be jointly transmitted on the first resource. The first data packet and the indication information 2 are jointly transmitted on the first resource, which can be understood as: (1) the first data packet and the indication information 2 can be independently coded at the moment by means of joint transmission on the first resource in a puncturing (puncturing) mode; for example, the terminal device may puncture the first data packet, and then transmit the punctured first data packet and the indication information 2 on the first resource. Or, (2) jointly transmit on the first resource by means of joint coding, for example, the terminal device may jointly code the first data packet and the indication information 2, and send the jointly coded information on the first resource. It is to be understood that when the puncturing manner is adopted, the indication information 2 described in the above two examples may be adopted to indicate whether error delivery is supported; when the joint coding is adopted, the indication information 2 described in the first example above may be adopted to indicate whether or not to support error delivery.

In step 306, the network device determines that the first data packet transmission is erroneous.

Illustratively, the network device determining the first packet transmission error may include: the network device determines that the CRC check of the first data packet fails and/or the network device determines that the decoding of the first data packet fails.

In one example, if the network device determines that the first packet supports error delivery or needs to perform error delivery, the physical layer of the network device may perform CRC check after receiving the first packet, and may deliver the CRC check to the MAC layer regardless of whether the CRC check passes, and further, may indicate whether the CRC check passes to the MAC layer. Decoding the first data packet by a decoding entity of the MAC layer (wherein, whether the CRC check passes may be used as an input parameter when the decoding entity performs decoding), and if the decoding fails (at this time, the CRC check may pass or may not pass), determining that the first data packet is in error transmission; if the CRC check passes and the decoding is successful, it can be determined that the first data packet was transmitted correctly.

In another example, if the network device determines that the first data packet supports error delivery or needs to perform error delivery, the physical layer of the network device may not perform CRC check after receiving the first data packet, and deliver the first data packet to the MAC layer (in this case, it may not indicate whether the CRC check passes or not), and a decoding entity of the MAC layer decodes the first data packet, and if the decoding fails, it determines that the first data packet is in error; if the decoding is successful, it can be determined that the first data packet is transmitted correctly. By adopting the mode, when the first data packet supports error submission, CRC (cyclic redundancy check) can not be carried out on the first data packet any more, so that the processing burden can be effectively saved.

In step 307, the network device performs error delivery on the first data packet.

Illustratively, the error delivery of the first data packet by the network device may include at least one of: (1) the HARQ entity of the network equipment executes error submission on the first data packet; (2) a demultiplexing entity of the network device performs error delivery on the first data packet; (3) the RLC layer entity of the network equipment performs error delivery on the first data packet; (4) the PDCP layer entity of the network device performs error delivery on the first data packet. It is to be appreciated that the error delivery of the first data packet by the network device may also include other layer entities performing the error delivery of the first data packet, such as the SDAP layer entity performing the error delivery of the first data packet. For example, when each of the above-described entities performs error delivery on the first packet, the upper layer may be notified of the transmission error of the first packet.

The different entities described above perform error delivery on the first packet in the following detailed description.

(1) The HARQ entity performs error delivery on the first data packet

The HARQ entity may deliver the first data packet and indication information 3 to the demultiplexing entity, the indication information 3 being used to indicate that the first data packet was transmitted with errors. In one example, the indication information 3 is used to indicate the decoding accuracy of the first data packet, for example, the decoding accuracy is 30% or 50%.

In one example, the HARQ entity may submit the first packet and the indication information 3 to the demultiplexing entity after determining that at least one of (c) below is met. The decoding accuracy of the first data packet is greater than a first threshold; the retransmission times of the first data packet is greater than a second threshold value; and the timer corresponding to the first data packet is overtime. For example, the first threshold, the second threshold, and the duration of the timer may be specified by a protocol; or, the determination may also be made by the network device, and further, the network device may also send the first threshold, the second threshold, and the duration of the timer to the terminal device.

For example, the first threshold may be 80%, and after receiving the data packet 1 (the data packet 1 is newly transmitted data), if it is determined that the decoding accuracy reaches 20% (smaller than the first threshold), the terminal device may not submit the data to the demultiplexing entity, and update the data in the HARQ buffer to the data packet 1; after receiving the data packet 2 (the data packet 2 is a data packet retransmitted for the first time), the terminal equipment merges and decodes the data packet 2 and the data in the HARQ buffer, if the decoding accuracy reaches 50% (smaller than a first threshold), the terminal equipment does not submit the data to the demultiplexing entity, and updates the data in the HARQ buffer into a merging result of the data packet 2 and the data packet 1; after receiving the data packet 3 (the data packet 2 is a data packet retransmitted for the second time), the terminal device merges and decodes the data packet 3 and the data in the HARQ buffer, and if the decoding accuracy reaches 90% and exceeds a first threshold (80%), the terminal device may submit the decoding result and the indication information 3 to the demultiplexing entity, and the indication information 3 indicates that the decoding accuracy of the data packet 3 is 90%.

For another example, the second threshold is 1, after receiving the data packet 1 (the data packet 1 is newly transmitted data), if it is determined that the decoding fails, the terminal device may not submit the data to the demultiplexing entity, and update the data in the HARQ buffer to the data packet 1; after receiving the data packet 2 (the data packet 2 is a data packet retransmitted for the first time), the terminal equipment merges and decodes the data packet 2 and the data in the HARQ cache, if the decoding fails, the terminal equipment does not submit the data to the demultiplexing entity, and updates the data in the HARQ cache into a merging result of the data packet 2 and the data packet 1; after receiving the data packet 3 (the data packet 3 is a data packet retransmitted for the second time), the terminal device merges and decodes the data packet 3 and the data in the HARQ buffer, and if the decoding still fails, but the retransmission number is 2 and is greater than the second threshold, the terminal device may submit the decoding result and the indication information 3 to the demultiplexing entity.

For another example, after receiving the data packet 1 (the data packet 1 is newly transmitted data), the terminal device starts a timer, and if it is determined that the decoding fails, the terminal device may not submit the data to the demultiplexing entity, and update the data in the HARQ buffer to the data packet 1; after receiving the data packet 2 (the data packet 2 is a data packet retransmitted for the first time), the terminal equipment merges and decodes the data packet 2 and the data in the HARQ cache, the decoding fails, if the timer is not overtime, the terminal equipment does not submit the data to the demultiplexing entity, and updates the data in the HARQ cache into a merging result of the data packet 2 and the data packet 1; after receiving the data packet 3 (the data packet 3 is a data packet retransmitted for the second time), the terminal device merges and decodes the data packet 3 and the data in the HARQ buffer, and still fails in decoding, and if the timer is overtime, the terminal device may submit the decoding result and the indication information 3 to the demultiplexing entity.

It should be noted that: optionally, after the HARQ entity delivers the data packet with the transmission error (for example, the first data packet) to the demultiplexing entity, if the retransmission data packet of the first data packet is received, the retransmission data packet may not be delivered to the demultiplexing entity any more, as shown in (a) or (b) in fig. 4. Under the condition, when the delay requirement of the service is relatively high, the retransmitted data packet may not meet the delay requirement of the service, and the retransmitted data packet does not need to be delivered to the demultiplexing entity, so as to save the processing burden of an upper layer. Or, after the HARQ entity delivers the data packet with the transmission error (for example, the first data packet) to the demultiplexing entity, after the HARQ entity receives the retransmission data packet of the first data packet, if it is determined that the transmission is correct, the HARQ entity may deliver the retransmission data packet to the demultiplexing entity, and if it is determined that the transmission is erroneous, the HARQ entity may not deliver the retransmission data packet to the demultiplexing entity, as shown in (c) in fig. 4. Alternatively, after the HARQ entity delivers the data packet with the transmission error (for example, the first data packet) to the demultiplexing entity, if the retransmission data packet of the first data packet is received, the data packet may be delivered to the demultiplexing entity regardless of whether the transmission is correct, as shown in (d) in fig. 4.

Optionally, for a data packet (such as the first data packet) supporting error delivery, in one example, the HARQ entity may perform corresponding feedback according to whether the first data packet is delivered to the demultiplexing entity. For example, if the HARQ entity delivers the first data packet with the transmission error to the demultiplexing entity, no Acknowledgement (ACK) or Negative Acknowledgement (NACK) may be fed back for the first data packet, that is, no feedback is performed. For another example, if the HARQ entity delivers the first data packet with the transmission error to the demultiplexing entity, ACK may be fed back for the first data packet, and if not, NACK may be fed back or feedback may not be performed for the first data packet. For another example, if the HARQ entity delivers the first data packet with the transmission error to the demultiplexing entity, the HARQ entity does not perform feedback, and if the HARQ entity is not delivered, the HARQ entity may feed back NACK for the first data packet. In yet another example, the HARQ entity may also perform corresponding feedback depending on whether the first data packet is transmitted correctly. For example, if the HARQ entity determines that the first data packet is transmitted correctly, an ACK is fed back, and if the HARQ entity determines that the first data packet is transmitted incorrectly, a NACK is fed back or no feedback is performed. For another example, if the HARQ entity determines that the first data packet is transmitted correctly, the HARQ entity does not perform feedback, and if the HARQ entity determines that the first data packet is transmitted incorrectly, the HARQ entity feeds back NACK.

(2) The de-multiplexing entity performs error delivery on the first data packet.

The demultiplexing entity may deliver the first data packet and indication information 4 to the RLC layer entity, the indication information 4 being used to indicate that the first data packet was transmitted in error. Here, if the first data packet is a MAC PDU submitted by the HARQ entity, the demultiplexing entity may demultiplex the MAC PDU into one or more MAC SDUs after receiving the MAC PDU submitted by the HARQ entity, and submit the MAC SDU to the RLC layer entity.

Illustratively, taking the example that the first data packet includes MAC SDU1, the demultiplexing entity may submit MAC SDU1 to the RLC layer entity after conforming to at least one of (r) to (r). The demultiplexing entity acquires a logical channel identifier corresponding to the MAC SDU 1; acquiring a logical channel identifier corresponding to the MAC SDU1 by the demultiplexing entity, wherein the logical channel corresponding to the logical channel identifier supports error delivery; thirdly, the demultiplexing entity determines that MAC SDU1 is not submitted to the RLC layer entity; and fourthly, the demultiplexing entity determines that the decoding accuracy of the first data packet is greater than a third threshold value. Time duration T1 has elapsed since the first receipt of an erroneous packet of MAC SDU 1.

In a possible implementation manner, the demultiplexing entity may analyze the first data packet to obtain the logical channel identifier corresponding to the MAC SDU1, for example, the demultiplexing entity analyzes the MAC subheader of the first data packet to obtain the logical channel identifier corresponding to the MAC SDU 1. In yet another possible implementation manner, the demultiplexing entity may obtain the logical channel identifier corresponding to the MAC SDU1 from the DCI or obtain the logical channel identifier corresponding to the MAC SDU1 from the upper layer configuration message. In the embodiment of the present application, a manner for the demultiplexing entity to obtain the logical channel identifier is not limited, and the following description takes an example in which the demultiplexing entity obtains the logical channel identifier by parsing from the MAC subheader of the first data packet. The third threshold may be determined by the network device, or may be determined by the protocol. The value of the duration T1 may be agreed by a protocol, or may also be determined by the network device, and further, the network device may also send the value of T1 to the terminal device.

The following is a detailed description with reference to examples 1 to 5.

Example 1: if the demultiplexing entity obtains one or more logical channel identifiers from the MAC subheader of the first data packet by analysis, the demultiplexing entity submits one or more MAC SDUs after demultiplexing to one or more RLC layer entities, otherwise, the demultiplexing entity does not submit to an upper layer.

For example, the first packet includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2. The demultiplexing entity obtains the identifier of logical channel 1 and the identifier of logical channel 2, and then may submit MAC SDU1 to RLC layer entity 1 through logical channel 1, and submit MAC SDU2 to RLC layer entity 2 through logical channel 2. If the demultiplexing entity does not obtain the identifier of the logical channel 1 and the identifier of the logical channel 2 through analysis, the demultiplexing entity can not submit any more.

Example 2: the demultiplexing entity analyzes the MAC subheader of the first data packet to obtain one or more logical channel identifiers, and if some or all of the logical channels in the one or more logical channels support error delivery, the demultiplexed MAC SDU may be delivered to the RLC layer entity through the logical channel that supports error delivery, and if the logical channel that does not support error delivery is used, the MAC SDU may not be delivered.

For example, the first data packet includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, and both logical channel 1 and logical channel 2 support error delivery. If the demultiplexing entity parses the identifier of logical channel 1 and the identifier of logical channel 2 from the MAC subheader of the first packet, MAC SDU1 may be delivered to RLC layer entity 1 through logical channel 1, and MAC SDU2 may be delivered to RLC layer entity 2 through logical channel 2.

For another example, the first data packet includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, where logical channel 1 supports error delivery and logical channel 2 does not support error delivery. If the demultiplexing entity obtains the identifier of the logical channel 1 and the identifier of the logical channel 2 from the MAC subheader of the first data packet by parsing, the demultiplexing entity may submit MAC SDU1 to the RLC layer entity 1 through the logical channel 1, and may also indicate that the transmission of MAC SDU1 is erroneous; for MAC SDU2, retransmission may be waited for, and after receiving retransmitted and successfully decoded MAC SDU2 combined, MAC SDU2 may be delivered to RLC layer entity 2 over logical channel 2.

It is to be understood that in this example, logical channel 1 supports error delivery, which means that the latency requirement of data in logical channel 1 may be relatively high, and logical channel 2 does not support error delivery, which means that the latency requirement of data in logical channel 2 may be relatively low. In a possible scenario, if the sending end device only supports resources for error delivery when sending data, the sending end device may multiplex the data in the logical channel 1 and the data in the logical channel 2 into the same data packet (i.e., a first data packet) for sending. Accordingly, the demultiplexing entity of the receiving device may deliver the MAC SDU1 to the upper layer after determining that the first packet transmission error occurs, and then wait for retransmission. After receiving the retransmitted first data packet, if the combining and decoding are successful, the HARQ entity of the receiving end device may submit the retransmitted first data packet to the demultiplexing entity, and then the demultiplexing entity may submit the MAC SDU2 to the RLC layer entity 2 through the logical channel 2, in this case, the demultiplexing entity may submit the MAC SDU1 to the RLC layer entity 1 through the logical channel 1 again (the RLC layer entity 1 may also be notified, the MAC SDU1 submitted this time is submitted for the second time, and/or the RLC layer entity 1 may also be notified, the MAC SDU1 submitted this time is correctly transmitted), or the MAC SDU1 may not be submitted any more.

Example 3: the demultiplexing entity parses the MAC subheader of the first data packet to obtain one or more logical channel identifiers, where the one or more logical channels include a logical channel (for example, logical channel 1) supporting error delivery, and the demultiplexing entity does not deliver MAC SDUs to the upper layer through the logical channel 1, and otherwise does not deliver MAC SDUs to the upper layer.

For example, the first data packet includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, where logical channel 1 supports error delivery and logical channel 2 does not support error delivery. If the demultiplexing entity parses the identifier of logical channel 1 and the identifier of logical channel 2 from the MAC subheader of the first packet, it is determined whether the MAC SDU1 has been delivered to the RLC layer entity 1 through the logical channel 1, and if the MAC SDU1 has been delivered to the RLC layer entity 1 through the logical channel 1 (for example, the first data packet is a retransmission data packet of the data packet 1, and the demultiplexing entity has delivered the MAC SDU1 in the data packet 1 to the RLC layer entity 1 through the logical channel 1), the MAC SDU1 may not be delivered any more, or, the MAC SDU1 may be delivered to the RLC layer entity 1 again through the logical channel 1, and further, the RLC layer entity 1 may be notified that the MAC SDU1 is delivered for the nth (e.g., second or third) delivery of the MAC SDU1, and/or, the RLC layer entity 1 may also be notified that the delivery of the MAC SDU1 at this time is erroneous (or correct) in transmission; if the MAC SDU1 has not been delivered to the RLC layer entity 1 over logical channel 1, then the MAC SDU1 may be delivered to the RLC layer entity 1 over logical channel 1. For MAC SDU2, retransmission may be waited for, and after receiving retransmitted and successfully decoded MAC SDU2 combined, MAC SDU2 may be delivered to RLC layer entity 2 over logical channel 2.

Example 4: the demultiplexing entity parses the MAC subheader of the first data packet to obtain one or more logical channel identifiers, where the one or more logical channels include a logical channel (for example, logical channel 1) supporting error delivery, and the HARQ indicates that the decoding accuracy of the first data packet is greater than a third threshold, then the MAC SDU may be delivered to the upper layer through the logical channel 1, otherwise, the MAC SDU is not delivered to the upper layer.

For example, the first data packet includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, where logical channel 1 supports error delivery and logical channel 2 does not support error delivery. If the demultiplexing entity obtains the identifier of the logical channel 1 and the identifier of the logical channel 2 by parsing from the MAC subheader of the first data packet, it may determine whether the decoding accuracy of the first data packet is greater than a third threshold according to the indication information 3, if the decoding accuracy of the first data packet is greater than the third threshold, the MAC SDU1 may be delivered to an upper layer through the logical channel 1, and for the MAC SDU2, the MAC SDU2 may be waited for retransmission, and after receiving the MAC SDU2 that is retransmitted and decoded successfully, the MAC SDU2 may be delivered to the RLC layer entity 2 through the logical channel 2; if the decoding accuracy of the first data packet is less than or equal to the third threshold, the MAC SDU1 is not delivered.

Example 5: the demultiplexing entity parses the MAC subheader of the first data packet to obtain one or more logical channel identifiers, where the one or more logical channels include a logical channel (e.g., logical channel 1) supporting error delivery. If the demultiplexing entity determines that a time period T1 has elapsed since the first reception of an erroneous packet of MAC SDU1, the MAC SDU1 may be delivered to the upper layer over logical channel 1, otherwise it is not delivered to the upper layer.

For example, the demultiplexing entity receives data packet 1, where data packet 1 includes MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, logical channel 1 supports error delivery, and logical channel 2 does not support error delivery. If the demultiplexing entity determines that the data packet 1 is an error data packet of the MAC SDU1 received for the first time, the MAC SDU1 and the MAC SDU2 may not be submitted, and a timer is started, where the duration of the timer is T1. The de-multiplexing entity receives the duplicate packet of packet 1 (referred to as packet 2), where packet 2 is transmitted in error, but the timer is expired, and the de-multiplexing entity may deliver MAC SDU1 to the upper layer through logical channel 1. For MAC SDU2, retransmission may be waited for, and after receiving retransmitted and successfully decoded MAC SDU2 combined, MAC SDU2 may be delivered to RLC layer entity 2 over logical channel 2.

It can be understood that the above examples 1 to 5 only describe some exemplary situations, and other possible situations may also be included in the embodiments of the present application, for example, the demultiplexing entity may also deliver the MAC SDU to the upper layer when multiple conditions are simultaneously satisfied; for example, the first data packet includes MAC SDU1, and the demultiplexing entity may deliver MAC SDU1 to the upper layer in case it is determined that MAC SDU1 has not been delivered to the RLC layer entity and the decoding accuracy of the first data packet is greater than the third threshold, which is not specifically listed again.

It should be noted that, if the demultiplexing entity determines that the first packet includes the MAC CE, the MAC CE may be applied (application). In one example, the demultiplexing entity may apply the MAC CE included in the first packet after determining that the first packet is transmitted correctly. In yet another example, the demultiplexing entity may perform the behavior indicated by the MAC CE after complying with at least one of (c) below. The demultiplexing entity analyzes the first data packet to obtain a logical channel identifier; determining that the first data packet is received for the first time by the demultiplexing entity; and thirdly, the demultiplexing entity determines that the decoding accuracy of the first data packet is greater than a fourth threshold value. The fourth threshold may be determined by the network device, and further, the network device may further send the fourth threshold to the terminal device.

Illustratively, the specific implementation of the MAC CE may be various, such as performing the behavior indicated by the MAC CE. Some possible implementations of applying MAC CE are detailed below by way of a few examples. For example, if the MAC CE is a Buffer Status Report (BSR) MAC CE, the network device may schedule the terminal device according to the BSR. For example, if the MAC CE is a Power Headroom Report (PHR) MAC CE, the network device may schedule the terminal device according to the PHR, for example, if the power headroom reported by the terminal device is small, and the network device finds that the uplink sub-frequency bandwidth used by the terminal device when reporting the PHR is 4MHz, it indicates that the power of the terminal device is not sufficient to support the sub-frequency bandwidth transmission greater than 4MHz, and thus, the allocation of the sub-frequency bandwidth greater than 4MHz to the terminal device at one time may be avoided.

(3) The RLC layer entity and the PDCP layer entity perform error delivery on the first data packet

Illustratively, when the RLC layer entity or the PDCP layer entity receives a MAC SDU (e.g., MAC SDU1) from the MAC layer and the MAC layer indicates that the MAC SDU1 is a data packet with transmission error, the RLC layer entity or the PDCP layer entity may move the window of the respective layers according to the RLC Sequence Number (SN) and the PDCP SN, i.e., the RLC layer entity may move the window of the RLC SN and the PDCP layer entity may move the window of the PDCP SN.

In one example, when the RLC layer entity or the PDCP layer entity receives the MAC SDU1 from the MAC layer and the MAC layer indicates that the MAC SDU1 is a data packet with transmission errors, if the RLC layer entity or the PDCP layer entity determines that the MAC SDU1 is received for the first time, the window of each layer may be shifted according to the RLC Sequence Number (SN) and the PDCP SN, and if the MAC SDU1 is determined not to be received for the first time (for example, the MAC SDU1 may be received for the second time or the third time), the window of each layer may not be shifted according to the RLC SN and the PDCP SN any more, so as to avoid the occurrence of erroneous SDUs due to shifting the window multiple times for the same MAC SDU. Illustratively, even if the MAC SDU1 received for the second or third time is transmitted correctly, the RLC layer entity or PDCP layer entity may no longer move the window of the respective layer according to the RLC SN and PDCP SN.

In addition, for performing error delivery on the first data packet, it should be further explained that:

(1) when the RLC layer entity receives a MAC SDU (e.g., MAC SDU1) from the MAC layer and the MAC layer indicates that the MAC SDU1 is a data packet with a transmission error (or decoding failure), the RLC layer entity may submit the data packet to the PDCP layer entity of the upper layer, or may not submit the data packet to the PDCP layer entity of the upper layer.

(2) If the RLC layer entity receives the same MAC SDU from the MAC layer multiple times and the MAC layer indicates a transmission error (or decoding failure) each time, the RLC layer entity may submit the MAC SDU to the PDCP layer entity each time; or, the MAC SDU may be submitted to the PDCP layer entity N times before, and then is not submitted any more, the value of N may be determined by the network device, and further, the network device may also indicate the value of N to the terminal device; or, the RLC layer entity may submit the MAC SDU to the PDCP layer entity when receiving that the MAC layer indication decoding success rate is greater than a certain threshold (the threshold may be agreed by a protocol or determined by the network device, and further, the network device may also send a value of the threshold to the terminal device); still alternatively, the RLC layer entity may deliver the MAC SDU to the PDCP layer entity when a time length T2 has elapsed since the first time the error packet of the MAC SDU is received, where the time length T2 may be agreed by a protocol or determined by the network device, and further, the network device may further send the value of T2 to the terminal device.

(3) When the PDCP layer entity (or the SDAP layer entity) delivers to an upper layer (e.g., an application layer), it may indicate to the upper layer that the delivered packet is a packet with a transmission error. It can be understood that, since the network device and the terminal device may both serve as a receiving end device for the data packet, when the network device serves as the receiving end device, the PDCP layer entity (or the SDAP layer entity) of the network device may submit the data packet to the application layer of the application server, and indicate that the submitted data packet is a data packet with a transmission error; when the terminal device serves as a receiving end device, the PDCP layer entity (or the SDAP layer entity) of the terminal device may deliver a data packet to the application layer of the terminal device, and indicate that the delivered data packet is a data packet with an error in transmission, so that the application layer of the terminal device may count a Packet Error Rate (PER) and subsequently feed back the Packet Error Rate (PER) to the application layer of the application server. By adopting the above manner, the core network device can charge the data packet according to the transmission condition of the data packet, for example, when the core network device knows that the data packet is a data packet with transmission error, the core network device may not participate in traffic statistics and does not charge for the data packet, or may calculate traffic or charge according to a preset proportion, for example, when the data packet includes 100 bytes, the core network device may calculate according to 40 bytes when performing traffic statistics. The preset proportion is not limited in the embodiment of the application.

Example two

In embodiment two, some possible implementations will be described for the downlink communication scenario.

Fig. 5 is a schematic flowchart of a data transmission method according to a second embodiment of the present application, and as shown in fig. 5, the method includes:

step 501, the network device sends configuration information 4 to the terminal device, and the configuration information 4 is used for configuring an error delivery function for the terminal device.

Accordingly, in step 502, the terminal device receives configuration information 4.

As an example, the terminal device may report to the network device whether the terminal device supports error submission, and if the terminal device supports error submission, the network device may send the configuration information 4 to the terminal device, and if the terminal device does not support error submission, the network device may no longer send the configuration information 4 to the terminal device. For example, the terminal device may report capability information of the terminal device to the network device, where the capability information is used to indicate whether the terminal device supports error delivery.

In one example, after receiving a data packet, if it is determined that the data packet needs to perform error delivery, the terminal device configured with an error delivery function may not perform CRC check on the data packet any more in the physical layer and deliver the data packet to the MAC layer.

In yet another example, after receiving a data packet, if it is determined that the data packet needs to perform error delivery, a terminal device configured with an error delivery function may perform CRC check on the data packet at the physical layer, and may deliver the data packet to the MAC layer regardless of whether the check is passed.

Illustratively, the configuration information 4 may include a first parameter for indicating whether CRC check needs to be performed (or whether CRC is turned off) for the data packet supporting error delivery, and a second parameter for indicating that the data packet supporting error delivery is also to be delivered to an upper layer when decoding errors. The first parameter and the second parameter may be the same parameter, or may also be two different parameters, which is not limited specifically.

Step 503, the network device builds a second data packet, and the second data packet supports error delivery.

Here, the network device constructs the second data packet, and it is understood that the multiplexing entity in the MAC layer of the network device multiplexes the data received from the at least one logical channel to obtain the second data packet. Wherein the second data packet supports error delivery, and may include at least one of: the service to which the second data packet belongs supports error delivery; the cell transmitting the second data packet supports error delivery; at least one logical channel supports error delivery, partially or fully. For specific implementation, reference may be made to the description related to the first data packet supporting error delivery in embodiment one.

Illustratively, if the network device includes a CU and a DU, a data packet (e.g., a second data packet) may be composed from the DU. In one example, the CU may send notification information to the DU through the F1-U interface, where the notification information may refer to the related description of configuration information 1 in the first embodiment, for example, the notification information may be used to notify whether one or more services of the DU support error delivery, or the notification information may be used to notify whether one or more logical channels of the DU support error delivery. Accordingly, the DU may construct a data packet according to the notification information. For example, if the notification information is used to notify the DU whether one or more logical channels support error delivery, when the DU creates a data packet according to the notification information, the DU may multiplex data in the logical channels that support error delivery into the same data packet as much as possible, and multiplex data in the logical channels that do not support error delivery into the same data packet as much as possible.

In step 504, the network device sends the second data packet to the terminal device.

Accordingly, in step 505, the terminal device receives a second data packet from the network device.

Illustratively, the network device may send a second data packet to the terminal device on the second resource and indicate whether the second data packet supports error delivery. In some possible examples, the data packets received by the terminal device may be predefined or preconfigured to each support error delivery, and the network device may no longer indicate to the terminal device whether the second data packet supports error delivery. Wherein, the second resource can be a dynamically scheduled resource; for example, the network device sends DCI-2 to the terminal device, where the DCI-2 is used to schedule the second resource, or the DCI-2 is used to indicate the second resource; accordingly, the terminal device may receive the second data packet on the second resource after receiving the DCI-2. Alternatively, the second resource may also be a semi-statically scheduled resource; for example, the network device configures a period for the terminal device in advance (for example, configures the period through an RRC message), and then activates through DCI-3, the DCI-3 may indicate a time domain position and a frequency domain position of a block of resources, and further the terminal device may consider that in each subsequent period, the network device transmits data on the block of resources.

It should be noted that, whether the network device supports error delivery for the terminal device, may be understood as whether the network device indicates that the MAC PDU supports error delivery. If the MAC PDU supports error delivery and one or some MAC SDUs in the MAC PDU do not support error delivery, the terminal equipment can deliver the MAC SDUs supporting the error delivery to an upper layer after decoding fails; for the MAC SDU which does not support error delivery, the MAC SDU can not be delivered to the upper layer, and the MAC SDU is delivered to the upper layer after the retransmission is successful.

There are various ways for the network device to indicate whether the second data packet supports error delivery, and several possible implementations are described below for dynamic scheduling and semi-static scheduling, respectively.

(1) Dynamic scheduling

Example 1: indication information 5 may be carried in the DCI-2, where the indication information 5 is used to indicate whether data carried by the second resource supports error delivery. Exemplarily, the indication information 5 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the data carried by the second resource supports error delivery; the value of the 1 bit is 0, which means thatThe data carried by the second resource does not support error delivery. It is understood that the indication information 5 may be carried in one or more fields of the DCI-2, such as one or more of a HARQ process number (HARQ process number) indication field carried in the DCI-2, a Modulation and Coding Scheme (MCS) indication field, a frequency domain resource allocation (frequency domain resource allocation) indication field, a time domain resource allocation (time domain resource allocation) indication field, and a reserved field. Take the MCS indication field with indication information 5 carrying DCI-2 as an example, for example, the MCS indication field includes 5 bits and has a total of 32 (2) ⁵ ) And 25 code points of which the specific meanings have been specified, and the remaining 7 code points are reserved code points, and then two of the remaining 7 code points can be used to indicate whether the data carried by the second resource supports error delivery.

Example 2: if the DCI-2 carries the indication information 5, it indicates that the data carried by the second resource supports error delivery, and if the DCI-2 does not carry the indication information 5, it indicates that the data carried by the second resource does not support error delivery. Or, if the DCI-2 carries the indication information 5, it indicates that the data carried by the second resource does not support error delivery, and if the DCI-2 does not carry the indication information 5, it indicates that the data carried by the second resource supports error delivery.

Example 3: if the terminal device receives DCI-2 according to a preset control-resource set (core set) and/or a preset search space (search space), it may be determined that data carried by a second resource scheduled by the DCI-2 supports error delivery, and if the terminal device does not receive the DCI-2 according to the preset control-resource set and the preset search space, it may be determined that the data carried by the second resource scheduled by the DCI-2 does not support error delivery. Wherein, the data of the resource load-bearing scheduled by the DCI loaded by the preset control resource set and/or the preset search space supports error delivery. The preset control resource set and/or the preset search space may be configured for the network device to the terminal device.

Example 4: if the terminal equipment receives the DCI-2 through the PDCCH scrambled by the preset RNTI, the data borne by the second resource scheduled by the DCI-2 can be determined to support error delivery, and if the terminal equipment does not receive the DCI-2 through the PDCCH scrambled by the RNTI, the data borne by the second resource scheduled by the DCI-2 can be determined not to support error delivery. The preset RNTI may be a newly defined RNTI for indicating that the data carried by the resource scheduled by the DCI-2 supports error delivery. The preset RNTI may be configured for the terminal device by the network device.

Example 5: if the terminal device receives the DCI-2 on the preset bandwidth part (BWP), it may be determined that the data carried by the second resource scheduled by the DCI-2 supports error delivery, otherwise, it may be determined that the data carried by the second resource scheduled by the DCI-2 does not support error delivery. Illustratively, the network device may configure one or more BWPs for the terminal device, for example, the network device may select at least one BWP from the one or more BWPs as a preset BWP after configuring the one or more BWPs, and indicate the preset BWP to the terminal device; for another example, the network device may also indicate that the terminal device is a preset BWP while configuring a certain BWP or BWPs.

Example 6: if the terminal device receives the DCI-2 on the preset time frequency resource, the data carried by the second resource scheduled by the DCI-2 can be determined to support error delivery, otherwise, the data carried by the second resource scheduled by the DCI-2 can be determined to not support error delivery. The preset time-frequency resource may be determined by the network device and may indicate the terminal device.

It is to be appreciated that examples 1 and 2 above can be understood as the network device indicating whether the data carried by the second resource supports error delivery in an explicit manner, and examples 3 to 6 can be understood as the network device indicating whether the data carried by the second resource supports error delivery in an implicit manner.

(2) Semi-persistent scheduling

In one example, indication information 5 may be carried in DCI-3, and indication information 5 may include 1 bit; for example, if the value of the 1 bit is 1, it indicates that the data carried by the second resource supports error delivery; if the value of the 1 bit is 0, it indicates that the data carried by the second resource does not support error delivery.

In another example, if indication information 5 is carried in DCI-3, it indicates that the data of the second resource bearer supports error delivery, and if indication information 5 is not carried in DCI-3, it indicates that the data of the second resource bearer does not support error delivery. Or, if the DCI-3 carries the indication information 5, it indicates that the data carried by the second resource does not support error delivery, and if the DCI-3 does not carry the indication information 5, it indicates that the data carried by the second resource supports error delivery.

It should be noted that, for semi-persistent scheduling, the above is described by taking an example of indicating whether data of a semi-persistent scheduled resource bearer supports error delivery through DCI-3, and in other possible embodiments, it may also be indicated whether data of a semi-persistent scheduled resource bearer supports error delivery through an RRC message for a configuration period.

Illustratively, a terminal device may be configured with up to 8 sets of semi-statically scheduled resources on one BWP. When whether the data of the semi-statically scheduled resource bearers support error delivery is indicated by the RRC message, whether the data of each set of semi-statically scheduled resource bearers supports error delivery may be separately indicated, for example, if it is indicated in the RRC message that the data of a certain set of semi-statically scheduled resource bearers supports error delivery, it may not be required to indicate in the DCI activating the set of semi-statically scheduled resources, and as long as the set of semi-statically scheduled resources is activated, all the data transmitted on the set of semi-statically scheduled resources support error delivery. Or, it may be configured to uniformly configure whether data carried by all semi-statically scheduled resources supports error delivery, for example, if it is indicated in the RRC message that the semi-statically scheduled resources support error delivery, it may not be required to indicate in the DCI activating the semi-statically scheduled resources, and as long as any set of semi-statically scheduled resources is activated, all data transmitted on the set of semi-statically scheduled resources support error delivery.

In step 506, the terminal device determines that the second data packet transmission is erroneous.

And step 507, the terminal equipment delivers the second data packet in an error mode.

Here, step 506 and step 507 may refer to step 306 and step 307 in the first embodiment, for example, the terminal device may include an HARQ entity, a demultiplexing entity, an RLC layer entity, a PDCP layer entity, and an SDAP layer entity, and the implementation that each entity performs error delivery may refer to the HARQ entity, the demultiplexing entity, the RLC layer entity, the PDCP layer entity, and the SDAP layer entity in the network device to perform error delivery.

For the above first and second embodiments, it should be noted that: (1) the first and second embodiments may be implemented individually or in combination. That is, the network device in the first embodiment and the network device in the second embodiment may be different network devices, and the terminal device in the first embodiment and the terminal device in the second embodiment may be different terminal devices; or, the network device in the first embodiment and the network device in the second embodiment may be the same network device, and the terminal device in the first embodiment and the terminal device in the second embodiment may be the same terminal device.

(2) In this embodiment, taking the first resource as an example, the data carried by the first resource supports error delivery, which may also be described as the first resource supporting error delivery. The logical channel supports error delivery, which can also be described as data carried by the logical channel supporting error delivery. A service supports error delivery, which may also be described as data belonging to the service supporting error delivery. The data stream supports error delivery, which can also be described as data in the data stream supporting error delivery.

(3) The configuration information (for example, configuration information 1, configuration information 2, configuration information 3, or configuration information 4) referred to in the embodiments of the present application may be sent to the terminal device in a variety of ways, for example, through RRC signaling, which is not limited specifically.

(4) The step numbers of the flowcharts (such as fig. 3 and fig. 5) described in the embodiment of the present application are only an example of an execution flow, and do not limit the execution sequence of the steps, and there is no strict execution sequence between the steps that have no time sequence dependency relationship with each other in the embodiment of the present application. For example, in fig. 5, step 501 may be performed before step 503, or may be performed simultaneously with step 503.

The above-mentioned scheme provided by the embodiments of the present application is introduced mainly from the perspective of device interaction. It is understood that, in order to implement the above functions, the network device or the terminal device may include a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the terminal device and the network device may be divided into the functional units according to the above method examples, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

In case of integrated units, fig. 6 shows a possible exemplary block diagram of the apparatus involved in the embodiments of the present application. As shown in fig. 6, the apparatus 600 may include: a processing unit 602 and a communication unit 603. The processing unit 602 is configured to control and manage operations of the apparatus 600. The communication unit 603 is used to support communication of the apparatus 600 with other devices. Optionally, the communication unit 603 is also referred to as a transceiving unit and may comprise a receiving unit and/or a transmitting unit for performing receiving and transmitting operations, respectively. The apparatus 600 may further comprise a storage unit 601 for storing program code and/or data of the apparatus 600.

The apparatus 600 may be a terminal device (or a chip disposed in the terminal device) in any of the above embodiments, such as the terminal device in the first embodiment or the second embodiment; wherein, the processing unit 602 may support the apparatus 600 to perform the actions of the terminal device in the above method examples; alternatively, the processing unit 602 mainly performs internal actions of the terminal device in the method example, and the communication unit 603 may support communication between the apparatus 600 and other devices (such as network devices). Alternatively, the apparatus 600 may be a network device (or a chip disposed in a network device) in any of the above embodiments, such as the network device in embodiment one or embodiment two; wherein the processing unit 602 may enable the apparatus 600 to perform the actions of the network device in the above method examples; alternatively, the processing unit 602 mainly performs internal actions of the network device in the method example, and the communication unit 603 may support communication between the apparatus 600 and other devices (such as terminal devices).

In one embodiment, the communication unit 603 is configured to: receiving a first data packet; the processing unit 602 is configured to: and if the first data packet is determined to be transmitted in error, performing error submission on the first data packet.

In one possible design, the processing unit 602 determines that the first packet transmission error includes: the processing unit 602 determines that the CRC check of the first packet fails; and/or the processing unit 602 determines that the decoding of the first packet fails.

In one possible design, communication unit 603 is further configured to: sending first indication information, wherein the first indication information is used for indicating that the data carried by the first resource supports error delivery; the first data packet is carried on the first resource.

In one possible design, the communication unit 603 is further configured to: the communication device sends an uplink authorization, wherein the uplink authorization is used for indicating a first resource and carries first indication information; or sending first configuration information, wherein the first configuration information is used for configuring a first resource and carries first indication information; or sending control information, wherein the control information is used for activating the first resource and carries the first indication information.

In one possible design, communication unit 603 is further configured to: and receiving second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.

In one possible design, the first data packet and the second indication information are carried in the first resource.

In one possible design, the first data packet is carried on the second resource; the communication unit 603 is further configured to: and receiving third indication information, wherein the third indication information is used for indicating that the data carried by the second resource supports error delivery.

In one possible design, the communication unit 603 is specifically configured to: receiving first control information, wherein the first control information is used for scheduling second resources and carries third indication information; or receiving second control information, wherein the second control information is used for activating a second resource and carries third indication information; or receiving second configuration information, where the second configuration information is used to configure a second resource, and the second configuration information carries third indication information.

In one possible design, the first data packet is carried on the second resource; the communication unit 603 is further configured to: receiving third control information according to the preset control resource set and/or the preset search space, wherein the third control information is used for scheduling the second resource; the data loaded by the resource scheduled by the third control information loaded by the preset control resource set and/or the preset search space supports error submission; or receiving third control information on a physical downlink control channel, wherein the third control information is used for scheduling the second resource; the physical downlink control channel is scrambled through a preset RNTI, and the preset RNTI indicates that the data supported by the resource scheduled by the third control information carried by the physical downlink control channel supports error delivery.

In one possible design, communication unit 603 is further configured to: third configuration information is received, the third configuration information being used to configure an error delivery function for the communication device.

In one possible design, processing unit 602 is further configured to: and controlling the HARQ entity to submit the first data packet and fourth indication information to the demultiplexing entity, wherein the fourth indication information is used for indicating the transmission error of the first data packet.

In one possible design, before the processing unit 602 controls the HARQ entity to deliver the first data packet and the fourth indication information to the demultiplexing entity, at least one of the following is further included: determining that the decoding accuracy of the first data packet is greater than a first threshold; determining that the retransmission times of the first data packet is greater than a second threshold; and determining that the timer corresponding to the first data packet is overtime.

In one possible design, if it is determined that the HARQ entity receives the retransmission data packet of the first data packet, the processing unit 602 delivers the retransmission data packet to the demultiplexing entity; further, the first packet may be a newly transmitted packet.

In one possible design, before the processing unit 602 controls the HARQ entity to deliver the retransmission packet to the demultiplexing entity, the processing unit is further configured to: and determining that the retransmission data packet is transmitted correctly.

In one possible design, processing unit 602 may further be configured to: and controlling the HARQ entity to feed back an acknowledgement ACK for the first data packet.

In one possible design, processing unit 602 is further configured to: and controlling the demultiplexing entity to deliver the first data packet and fifth indication information to the RLC layer entity, wherein the fifth indication information is used for indicating the transmission error of the first data packet.

In one possible design, before the processing unit 602 controls the demultiplexing entity to deliver the first data packet to the RLC layer entity, at least one of the following is further included: analyzing the first data packet to obtain a logical channel identifier; analyzing from the first data packet to obtain a logical channel identifier, wherein logical channels corresponding to the logical channel identifier all support error submission; determining that a first data packet is not submitted to an RLC layer entity; and determining that the decoding accuracy of the first data packet is greater than a third threshold value.

In one possible design, processing unit 602 is further configured to: and if the first data packet is determined to contain the MAC CE, applying the MAC CE.

In one possible design, before the processing unit 602 performs the MAC CE indicated action, at least one of the following is further included: analyzing the first data packet to obtain a logical channel identifier; determining that the first data packet is received for the first time; and determining that the decoding accuracy of the first data packet is greater than a fourth threshold value.

In one possible design, processing unit 602 may further be configured to: and if the first data packet is determined to be received for the first time, controlling the RLC layer entity to move the RLC SN window.

In yet another embodiment, the processing unit 602 is configured to: establishing a first data packet, wherein the first data packet supports error delivery; the communication unit 603 is configured to: the first data packet is transmitted.

In one possible design, communication unit 603 is further configured to: receiving first indication information, wherein the first indication information is used for indicating that data carried by a first resource supports error delivery; and transmitting the first data packet on the first resource.

In one possible design, communication unit 603 is further configured to: receiving an uplink authorization, wherein the uplink authorization is used for indicating a first resource and carries first indication information; or receiving first configuration information, wherein the first configuration information is used for configuring a first resource and carries first indication information; or receiving control information, wherein the control information is used for activating the first resource and carries first indication information.

In one possible design, communication unit 603 is further configured to: and sending second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.

In one possible design, the communication unit 603 sends the first data packet and the second indication information, and includes: and sending the first data packet and the second indication information on the first resource.

In one possible design, processing unit 602 is further configured to: puncturing the first data packet; the communication unit 603 is further configured to: sending the first data packet and the second indication information after the punching on the first resource; alternatively, the processing unit 602 is further configured to: jointly encoding the first data packet and the second indication information; the communication unit 603 is further configured to: the jointly encoded information is transmitted on a first resource.

In one possible design, communication unit 603 is further configured to: second configuration information is received, the second configuration information indicating whether one or more logical channels support error delivery.

In one possible design, the first data packet is carried on the second resource; the communication unit 603 is further configured to: and sending third indication information, wherein the third indication information is used for indicating that the data carried by the second resource supports error delivery.

In one possible design, the communication unit 603 is further configured to: and receiving fourth indication information from the CU, wherein the fourth indication information is used for indicating whether the one or more logical channels support error delivery.

In one possible design, processing unit 602 is further configured to: the MAC layer entity is controlled to deliver the first data packet and fifth indication information to the physical layer entity, and the fifth indication information is used for indicating the position of at least one item of an SDAP (data base protocol access protocol) head, a PDCP (packet data convergence protocol) head, an RLC (radio link control) head and an MAC (media access control) head of the first data packet in the first data packet; and controlling the physical layer entity to send the first data packet according to the fifth indication information.

It should be understood that the division of the units in the above apparatus is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity or may be physically separated. And the units in the device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; part of the units can also be realized in the form of software called by a processing element, and part of the units can be realized in the form of hardware. For example, each unit may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory in the form of a program, and a function of the unit may be called and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together or can be independently realized. The processing element described herein may in turn be a processor, which may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the units above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.

In one example, the units in any of the above apparatus may be one or more integrated circuits configured to implement the above method, for example: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when a unit in a device may be implemented in the form of a processing element scheduler, the processing element may be a processor, such as a Central Processing Unit (CPU), or other processor capable of invoking a program. As another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above unit for receiving is an interface circuit of the apparatus for receiving signals from other apparatuses. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The above unit for transmitting is an interface circuit of the apparatus for transmitting a signal to other apparatuses. For example, when the device is implemented in the form of a chip, the transmission unit is an interface circuit for the chip to transmit a signal to other chips or devices.

Please refer to fig. 7, which is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure. It may be the terminal device in the above embodiment, for implementing the operation of the terminal device in the above embodiment. As shown in fig. 7, the terminal device includes: an antenna 710, a radio frequency section 720, a signal processing section 730. The antenna 710 is connected to the radio frequency part 720. In the downlink direction, the rf section 720 receives information transmitted by the network device through the antenna 710, and transmits the information transmitted by the network device to the signal processing section 730 for processing. In the uplink direction, the signal processing portion 730 processes the information of the terminal device and sends the information to the radio frequency portion 720, and the radio frequency portion 720 processes the information of the terminal device and sends the information to the network device through the antenna 710.

The signal processing portion 730 may include a modem subsystem for implementing processing of various communication protocol layers of data; the system also comprises a central processing subsystem used for realizing the processing of the operating system and the application layer of the terminal equipment; in addition, other subsystems, such as a multimedia subsystem for controlling a camera, a screen display and the like of the terminal device, a peripheral subsystem for connecting with other devices, and the like can be included. The modem subsystem may be a separately provided chip.

The modem subsystem may include one or more processing elements 731, for example, including a master CPU and other integrated circuits. The modem subsystem may also include a storage element 732 and an interface circuit 733. The storage element 732 is used to store data and programs, but the programs for executing the methods executed by the terminal device in the above methods may not be stored in the storage element 732, but may be stored in a memory outside the modem subsystem, and the modem subsystem is loaded for use when used. The interface circuit 733 is used to communicate with other subsystems.

The modem subsystem may be implemented by a chip comprising at least one processing element for performing the steps of any of the methods performed by the terminal equipment above, and interface circuitry for communicating with other devices. In one implementation, the unit for the terminal device to implement each step in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the terminal device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the terminal device in the above method embodiment. The memory elements may be memory elements with the processing elements on the same chip, i.e. on-chip memory elements.

In another implementation, the program for performing the method performed by the terminal device in the above method may be a memory element on a different chip than the processing element, i.e. an off-chip memory element. At this time, the processing element calls or loads a program from the off-chip storage element onto the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiment.

In yet another implementation, the unit of the terminal device for implementing the steps of the above method may be configured as one or more processing elements disposed on the modem subsystem, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

Units of the terminal equipment for realizing the steps of the method can be integrated together and realized in the form of SOC, and the SOC chip is used for realizing the method. At least one processing element and a storage element can be integrated in the chip, and the processing element calls the stored program of the storage element to realize the method executed by the terminal equipment; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above terminal device; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.

It is seen that the above apparatus for a terminal device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the terminal devices provided by the above method embodiments. The processing element may: namely, the method calls the program stored in the storage element to execute part or all of the steps executed by the terminal equipment; it is also possible to: that is, some or all of the steps performed by the terminal device are performed by integrated logic circuits of hardware in the processor element in combination with the instructions; of course, some or all of the steps performed by the terminal device may be performed in combination with the first manner and the second manner.

The processing elements herein, like those described above, may be implemented by a processor, and the functions of the processing elements may be the same as those of the processing unit described in fig. 6. Illustratively, the processing element may be a general-purpose processor, such as a CPU, and may also be one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. The memory element may be implemented by a memory, and the function of the memory element may be the same as that of the memory cell described in fig. 6. The storage element may be a single memory or a combination of memories.

The terminal device shown in fig. 7 can implement the processes related to the terminal device in the method embodiments illustrated in fig. 3 or fig. 5. The operations and/or functions of the modules in the terminal device shown in fig. 7 are respectively for implementing the corresponding flows in the above method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

Please refer to fig. 8, which is a schematic structural diagram of a network device according to an embodiment of the present disclosure. Which may be the network device (such as DU) in the above embodiments, for implementing the operation of the network device in the above embodiments. As shown in fig. 8, the network device includes: antenna 801, radio frequency device 802, baseband device 803. The antenna 801 is connected to a radio frequency device 802. In the uplink direction, the radio frequency apparatus 802 receives information transmitted by the terminal device through the antenna 801, and transmits the information transmitted by the terminal device to the baseband apparatus 803 for processing. In the downlink direction, the baseband device 803 processes the information of the terminal device and sends the information to the radio frequency device 802, and the radio frequency device 802 processes the information of the terminal device and sends the information to the terminal device through the antenna 801.

The baseband device 803 may include one or more processing elements 8031, including, for example, a host CPU and other integrated circuits. In addition, the baseband device 803 may further include a storage element 8032 and an interface 8033, the storage element 8032 being used to store programs and data; the interface 8033 is used for exchanging information with the radio frequency device 802, and is, for example, a Common Public Radio Interface (CPRI). The above means for network devices may be located at the baseband means 803, for example, the above means for network devices may be a chip on the baseband means 803, the chip comprising at least one processing element and interface circuitry, wherein the processing element is configured to perform the steps of any of the methods performed by the above network devices, and the interface circuitry is configured to communicate with other devices. In one implementation, the unit of the network device for implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the network device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing element, i.e. on-chip memory elements, or may be memory elements on a different chip than the processing element, i.e. off-chip memory elements.

In another implementation, the unit of the network device for implementing the steps of the above method may be configured as one or more processing elements, which are disposed on the baseband apparatus, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

The units of the network device implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC), for example, a baseband device including the SOC chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the method executed by the network equipment is realized in the form that the processing element calls the stored program of the storage element; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above network device; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.

It is seen that the above apparatus for a network device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the network devices provided by the above method embodiments. The processing element may: namely, calling the program stored in the storage element to execute part or all of the steps executed by the network equipment; it is also possible to: that is, some or all of the steps performed by the network device are performed by integrated logic circuitry of hardware in the processor element in combination with the instructions; of course, some or all of the steps performed by the above network device may also be performed in combination with the first manner and the second manner.

The processing elements described herein, like those described above, may be implemented by a processor, and the functionality of the processing elements may be the same as that of the processing unit described in fig. 6. Illustratively, the processing element may be a general-purpose processor, such as a CPU, and may also be one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. The memory element may be implemented by a memory, and the function of the memory element may be the same as that of the memory cell described in fig. 6. The storage element may be a single memory or a combination of memories.

The network device shown in fig. 8 is capable of implementing various processes involving the network device in the method embodiments illustrated in fig. 3 or 5. The operations and/or functions of the respective modules in the network device shown in fig. 8 are respectively for implementing the corresponding flows in the above-described method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

Please refer to fig. 9, which is a schematic structural diagram of another network device according to an embodiment of the present application. Which may be a network device (such as a CU) in the above embodiments for implementing the operations of the network device in the above embodiments.

As shown in fig. 9, the network device includes: a processor 910, a memory 920, and an interface 930, the processor 910, the memory 920, and the interface 930 being in signal communication.

The apparatus illustrated in fig. 6 above may be located in the network device, and the functions of the respective units may be implemented by the processor 910 calling a program stored in the memory 920. That is, the apparatus illustrated in fig. 6 above includes a memory for storing a program that is called by the processor to perform the method in the above method embodiment, and a processor. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. Or the functions of the above respective units may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

A method of data transmission, the method comprising:

the communication device receives a first data packet;

the communication device determining that the first data packet transmission error;

the communication device performs error delivery on the first data packet.
The method of claim 1, wherein the communication device determining the first packet transmission error comprises:

the communication device determining that a cyclic redundancy check, CRC, check of the first data packet failed; and/or the presence of a gas in the gas,

the communication device determines that the first packet coding failed.
The method according to claim 1 or 2, wherein the communication device is located in a network device.
The method of claim 3, further comprising:

the communication device sends first indication information, wherein the first indication information is used for indicating that data carried by a first resource supports error delivery;

wherein the first data packet is carried in the first resource.
The method of claim 4, wherein the communication device sends the first indication information, comprising:

the communication device sends an uplink grant, wherein the uplink grant is used for indicating the first resource and carries the first indication information; alternatively, the first and second electrodes may be,

the communication device sends first configuration information, wherein the first configuration information is used for configuring the first resource and carries the first indication information; alternatively, the first and second electrodes may be,

the communication device sends control information, the control information is used for activating the first resource, and the control information carries the first indication information.
The method of claim 3, further comprising:

the communication device receives second indication information indicating that the first data packet supports error delivery.
The method of claim 6, wherein the first data packet and the second indication information are carried in a first resource allocated by the communication device.
The method according to claim 1 or 2, wherein the communication means is located at a terminal device.
The method of claim 8, wherein the first packet is carried on a second resource;

the method further comprises the following steps: the communication device receives third indication information, where the third indication information is used to indicate that data carried by the second resource supports error delivery.
The method of claim 9, wherein the communication device receives a third indication information, comprising:

the communication device receives first control information, wherein the first control information is used for scheduling the second resource and carries the third indication information; alternatively, the first and second electrodes may be,

the communication device receives second control information, wherein the second control information is used for activating the second resource and carries the third indication information; alternatively, the first and second electrodes may be,

the communication device receives second configuration information, where the second configuration information is used to configure the second resource, and the second configuration information carries the third indication information.
The method of claim 8, wherein the first packet is carried on a second resource;

the method further comprises the following steps:

the communication device receives third control information according to a preset control resource set and/or a preset search space, wherein the third control information is used for scheduling the second resource; the data loaded by the resource scheduled by the third control information loaded by the preset control resource set and/or the preset search space supports error submission; alternatively, the first and second electrodes may be,

the communication device receives third control information on a physical downlink control channel, wherein the third control information is used for scheduling the second resource; the physical downlink control channel is scrambled through a preset Radio Network Temporary Identifier (RNTI), and the preset RNTI indicates that the data loaded by the resource scheduled by the third control information loaded by the physical downlink control channel supports error delivery.
The method according to any one of claims 8 to 11, further comprising:

the communication device receives third configuration information, wherein the third configuration information is used for configuring an error delivery function for the communication device.
The method of any of claims 1 to 12, wherein the communication device performs error delivery on the first data packet, comprising:

and the hybrid automatic repeat request HARQ entity of the communication device submits the first data packet and fourth indication information to a demultiplexing entity, wherein the fourth indication information is used for indicating the transmission error of the first data packet.
The method of claim 13, wherein the fourth indication information is used to indicate a coding accuracy of the first data packet.
The method according to claim 13 or 14, wherein before the HARQ entity of the communication device delivers the first data packet and the fourth indication information to the demultiplexing entity, further comprising at least one of:

determining, by an HARQ entity of the communication device, that a decoding accuracy of the first data packet is greater than a first threshold;

determining, by an HARQ entity of the communication device, that a number of retransmissions of the first data packet is greater than a second threshold;

and the HARQ entity of the communication device determines that the timer corresponding to the first data packet is overtime.
The method according to any one of claims 13 to 15, further comprising:

and if the HARQ entity of the communication device receives the retransmission data packet of the first data packet, submitting the retransmission data packet to the demultiplexing entity.
The method of claim 16, wherein before the HARQ entity of the communication device delivers the retransmission packet to the demultiplexing entity, further comprising:

the HARQ entity of the communication device determines that the retransmission data packet is transmitted correctly.
The method according to any one of claims 13 to 17, further comprising:

and the HARQ entity of the communication device feeds back an acknowledgement ACK for the first data packet.
The method of any of claims 1 to 18, wherein the communication device performing error delivery on the first data packet comprises:

and the demultiplexing entity of the communication device delivers the first data packet and fifth indication information to a Radio Link Control (RLC) layer entity, wherein the fifth indication information is used for indicating the transmission error of the first data packet.
The method of claim 19, wherein before the demultiplexing entity of the communication device delivers the first data packet to the RLC layer entity, at least one of:

a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier;

a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier, and the logical channels corresponding to the logical channel identifier all support error delivery;

a demultiplexing entity of the communication device determines that the first data packet has not been delivered to the RLC layer entity;

the demultiplexing entity of the communication device determines that the decoding accuracy of the first data packet is greater than a third threshold.
The method according to any one of claims 1 to 20, further comprising:

and if the demultiplexing entity of the communication device determines that the first data packet comprises a Media Access Control (MAC) Control Element (CE), applying the MAC CE.
The method of claim 21, wherein before the performing the MAC CE indicated action by the demultiplexing entity of the communication apparatus, further comprising at least one of:

a demultiplexing entity of the communication device analyzes the first data packet to obtain a logical channel identifier;

determining, by a de-multiplexing entity of the communication device, that the first data packet is received for the first time;

the demultiplexing entity of the communication device determines that the decoding accuracy of the first data packet is greater than a fourth threshold.
The method according to any one of claims 19 to 22, further comprising:

and if the RLC layer entity of the communication device determines that the first data packet is received for the first time, moving the window of the RLC sequence number SN.
A method of data transmission, the method comprising:

a communication device establishes a first data packet, wherein the first data packet supports error delivery;

the communication device transmits a first data packet.
The method of claim 24, wherein the first data packet supports error delivery, comprising at least one of:

the service to which the first data packet belongs supports error delivery;

the cell transmitting the first data packet supports error delivery;

the first data packet includes data from at least one logical channel, and the at least one logical channel partially or completely supports error delivery.
The method according to claim 24 or 25, wherein the communication means is located in a terminal device.
The method of claim 26, further comprising: the communication device receives first indication information, wherein the first indication information is used for indicating that data carried by the first resource supports error delivery;

the communication device transmits a first data packet, comprising: the communication device transmits the first data packet on the first resource.
The method of claim 27, wherein the communication device receives a first indication comprising:

the communication device receives an uplink grant, wherein the uplink grant is used for indicating the first resource, and the uplink grant carries the first indication information; alternatively, the first and second electrodes may be,

the communication device receives first configuration information, wherein the first configuration information is used for configuring the first resource and carries the first indication information; alternatively, the first and second electrodes may be,

the communication device receives control information, wherein the control information is used for activating the first resource and carries the first indication information.
The method of claim 26, further comprising:

the communication device sends second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.
The method of claim 29, wherein the second indication information is used for indicating that the first data packet supports error delivery, and comprises:

the second indication information is used for indicating that the first data packet supports error delivery when the first data packet conforms to at least one of the following items:

the decoding accuracy of the first data packet is greater than a first threshold;

the retransmission times of the first data packet are larger than a second threshold value;

and the timer corresponding to the first data packet is overtime.
The method according to claim 29 or 30, wherein the communication device transmits the first data packet and the second indication information, comprising:

the communication device transmits the first data packet and the second indication information on a first resource.
The method of claim 31, wherein the communication device transmits the first packet and the second indication information on a first resource, comprising:

the communication device punches the first data packet and sends the punched first data packet and the second indication information on the first resource; alternatively, the first and second electrodes may be,

the communication device jointly encodes the first data packet and the second indication information and transmits the jointly encoded information on the first resource.
The method of any one of claims 26 to 32, further comprising:

the communication device receives second configuration information indicating whether one or more logical channels support error delivery.
The method according to claim 24 or 25, wherein the communication device is located in a network device.
The method of claim 34, wherein the first packet is carried on a second resource;

the method further comprises the following steps:

the communication device sends third indication information, where the third indication information is used to indicate that the data carried by the second resource supports error delivery.
The method of claim 34 or 35, further comprising:

receiving fourth indication information from the concentration unit CU, the fourth indication information indicating whether one or more logical channels support error delivery.
The method of any one of claims 24 to 36, wherein the communication device transmits a first data packet comprising:

the MAC layer entity of the communication device submits the first data packet and fifth indication information to a physical layer entity, wherein the fifth indication information is used for indicating the position of at least one of Service Data Adaptation (SDAP) header, packet data convergence layer protocol (PDCP) header, Radio Link Control (RLC) header and MAC header of the first data packet in the first data packet;

and the physical layer entity of the communication device sends the first data packet according to the fifth indication information.
The method according to any of claims 24 to 37, wherein the first data packet comprises one PDCP service data unit, SDU, or one PDCP SDU fragment.
A communication system, characterized in that the communication system comprises a network device and a core network device, wherein the network device is configured to perform the method of any of the preceding claims 1 to 7, 13 to 25, 34 to 38.
The communication system according to claim 39, wherein the core network device is configured to send service information of one or more services to a network device;

wherein the one or more services include a first service, and the service information of the first service includes at least one of:

a delay budget for the first service;

the error submission indication of the first service is used for indicating whether the first service supports error submission;

and indicating error delivery of one or more data flows corresponding to the first service, wherein the error delivery indication of the data flows is used for indicating whether the data flows support error delivery.
A communications apparatus, comprising means for performing the steps of the method of any one of claims 1 to 38.
A communications device comprising at least one processor and interface circuitry, wherein the at least one processor is configured to communicate with other devices via the interface circuitry and to perform the method of any one of claims 1 to 38.
A communications device comprising a processor for invoking a program stored in memory to perform the method of any one of claims 1 to 38.
A computer-readable storage medium, characterized by comprising a program which, when executed by a processor, performs the method of any of claims 1 to 38.