Nothing Special   »   [go: up one dir, main page]

CN114902637B - Data transmission method and device - Google Patents

Data transmission method and device Download PDF

Info

Publication number
CN114902637B
CN114902637B CN201980103359.2A CN201980103359A CN114902637B CN 114902637 B CN114902637 B CN 114902637B CN 201980103359 A CN201980103359 A CN 201980103359A CN 114902637 B CN114902637 B CN 114902637B
Authority
CN
China
Prior art keywords
data packet
communication device
indication information
resource
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201980103359.2A
Other languages
Chinese (zh)
Other versions
CN114902637A (en
Inventor
黄曲芳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN114902637A publication Critical patent/CN114902637A/en
Application granted granted Critical
Publication of CN114902637B publication Critical patent/CN114902637B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

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, performs error delivery on the first data packet. By adopting the method, the data packet received by the receiving terminal equipment can be effectively utilized by performing error submission on the data packet, so that 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 various, 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 the time delay of the data is high.
However, how to perform data transmission to meet the transmission requirements of the above services still needs further research.
Disclosure of Invention
In view of this, the present application provides a data transmission method and apparatus for implementing error delivery of a data packet, so as to effectively utilize the data packet received by a receiving end device, thereby meeting the 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, where the communication device receives a first data packet, and if it is determined that the first data packet is transmitted in error, performs error delivery on the first data packet.
By adopting the method, the data packet received by the receiving terminal equipment can be effectively utilized by performing error submission on the data packet, so that the transmission requirement of the service is met.
In one possible design, the communication device determines a first packet transmission error, including: the communication device determines that the CRC of the first data packet fails; and/or the communication device determines that the first data packet has failed decoding.
In one possible design, the communication device may be a network device or a chip disposed within the network device.
In one possible design, the method further comprises: the communication device sends first indication information, wherein the first indication information is used for indicating data carried by a first resource to support error delivery; the first data packet is carried on the first resource.
In one possible design, the communication device sends first indication information including: the communication device sends an uplink grant, wherein the uplink grant is used for indicating the first resource, and the uplink grant carries first indication information; or the communication device sends first configuration information, wherein the first configuration information is used for configuring the first resource, and the first configuration information carries first indication information; or the communication device sends control information, wherein the control information is used for activating the first resource, and the control information carries first indication information.
By adopting the implementation manner, the network equipment can determine whether the transmission supports the error delivery by indicating whether the data carried by the first resource supports the error delivery, so that the flexibility of regulation and control of the network equipment is improved.
In one possible design, the method further comprises: the communication device receives second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.
By adopting the mode, the terminal equipment can indicate to the network equipment that the first data packet supports the error delivery, namely the terminal equipment can determine whether the transmission supports the error delivery or not, so that the network equipment does not need to indicate whether the data carried by the resources support the error delivery or not when the resources are allocated, and the processing burden of the network equipment is reduced.
In one possible design, the first data packet and the second indication information are carried on 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 not required to be sent by using additional resources, and the transmission resource can be effectively saved.
In one possible design, the communication device may be a terminal device or a chip arranged inside the terminal device.
In one possible design, the first data packet is carried on the second resource; the method further comprises the steps of: 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 a third indication information, including: the communication device receives first control information, wherein the first control information is used for scheduling second resources, and the first control information 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 the second control information carries third indication information; or the communication device receives second configuration information, wherein the second configuration information is used for configuring the 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 steps of: 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 second resources; the data supporting error submission of the resource bearer scheduled by the third control information of the preset control resource set and/or the preset search space bearer; or the communication device receives third control information in the 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 data of a resource carried by third control information scheduled by the physical downlink control channel supports error delivery.
By adopting the method, the data carried by the second resource is indicated to support error delivery in an implicit mode, so that the indication information is not required to be transmitted through additional resources, and the transmission resources can be effectively saved.
In one possible design, the method further comprises: the communication device receives third configuration information, and the third configuration information is used for configuring an error submitting 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, wherein the fourth indication information is used for indicating the transmission error of the first data packet.
In one possible design, the fourth indication information is used to indicate the 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 more clearly know the decoding condition of the first data packet, and 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 included: the HARQ entity of the communication device determines that the decoding accuracy of the first data packet is greater than a first threshold; the HARQ entity of the communication device determines that the retransmission times of the first data packet is larger than a second threshold value; the HARQ entity of the communication device determines that the timer corresponding to the first data packet is overtime.
In one possible design, the method further comprises: 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 the demultiplexing entity; further, the first data packet may be a new transmission data packet.
In one possible design, before the HARQ entity of the communication device submits the retransmission packet to the demultiplexing entity, the method further includes: the HARQ entity of the communication device determines that the retransmission packet transmission is correct.
In one possible design, the method further comprises: 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, the fifth indication information being for indicating a transmission error 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 logic channel identifier; the demultiplexing entity of the communication device analyzes the first data packet to obtain a logic channel identifier, and the logic channels corresponding to the logic channel identifier support error delivery; a demultiplexing entity of the communication device determines that the first data packet is not submitted 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.
In one possible design, the method further comprises: if the demultiplexing entity of the communication device determines that the first data packet includes the MAC CE, the demultiplexing entity applies the MAC CE.
In one possible design, before the demultiplexing entity of the communication device performs the act of MAC CE indication, at least one of the following is further included: a demultiplexing entity of the communication device analyzes the first data packet to obtain a logic channel identifier; the de-multiplexing entity of the communication device determines 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.
In one possible design, the method further comprises: the RLC layer entity of the communication device moves the window of the RLC SN if it determines that the first data packet was received for the first time. Similarly, the PDCP layer entity of the communication device moves a window of PDCP SNs 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, and if the first data packet is not received for the first time, the windows of the RLC SN and the PDCP SN can not be moved any more, so that the occurrence of errors caused by moving the windows for the same data packet for a plurality of 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, where the communication device composes a first data packet and transmits the first data packet; the first data packet supports error delivery.
By adopting the method, the first data packet supports error submission, so that the receiving end equipment can execute error submission on the first data packet after receiving the first data packet, the data packet received by the receiving end equipment is effectively utilized, and the transmission requirement of the service is met.
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 submission; the cell transmitting the first data packet supports error delivery; the first data packet includes data from at least one logical channel, and part or all of the at least one logical channel supports error delivery.
In one possible design, the communication device may be a terminal device or a chip arranged inside the terminal device.
In one possible design, the method further comprises: the communication device receives first indication information, wherein the first indication information is used for indicating first resource support 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 grant, wherein the uplink grant is used for indicating a first resource, and the uplink grant carries first indication information; or the communication device receives first configuration information, wherein the first configuration information is used for configuring first resources, and the first configuration information carries first indication information; or the communication device receives control information, wherein the control information is used for activating the first resource, and the control information carries first indication information.
In one possible design, the method further comprises: the communication device transmits second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.
After the terminal equipment builds the data packet, if the built data packet is determined to support error delivery, the data packet can be indicated to the network equipment to support error delivery, namely, the terminal equipment can determine whether the transmission supports error delivery or not, so that the network equipment does not need to indicate whether the data borne by the resource support error delivery or not when the network equipment allocates the resource, and the processing load of the network equipment is reduced.
In one possible design, the second indication information is used to indicate that the first data packet supports error delivery when the first data packet meets at least one of: 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; the timer corresponding to the first data packet times out.
In one possible design, the communication device sends a first data packet and second indication information, including: 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 a first data packet and second indication information on a first resource, including: the communication device punches the first data packet and sends the punched first data packet and second indication information on the first resource; or the communication device performs joint coding on the first data packet and the second indication information, and sends the joint coded information on the first resource.
In one possible design, the method further comprises: the communication device receives second configuration information indicating whether one or more logical channels support error delivery.
In one possible design, the communication device may be a network device or a chip disposed within the network device.
In one possible design, the first data packet is carried on the second resource; the method further comprises the steps of: the communication device transmits third indication information, wherein the third indication information is used for indicating the second resource to support error delivery.
In one possible design, the communication device is a DU, the method further comprising: fourth indication information is received from the CU, the fourth indication information being used to indicate whether one or more logical channels support error delivery.
In one possible design, the communication device sends a first data packet, including: the MAC layer entity of the communication device submits a first data packet and fifth indicating information to the physical layer entity, wherein the fifth indicating information is used for indicating the position of at least one of an SDAP head, a PDCP head, an RLC head and an MAC head of the first data packet in the first data packet; 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 position of the SDAP head, the PDCP head, the RLC head and the MAC head in the first data packet of the physical layer, namely, which bits in the first data packet are important, so that the physical layer can ensure the successful transmission of the bits in the position of the SDAP head, the PDCP head, the RLC head and the MAC head preferentially when transmitting the first data packet.
In one possible design, the first data packet may include one PDCP SDU or one PDCP SDU fragment.
By adopting the mode, after the physical layer receives the first data packet submitted by the MAC layer, the position of the SDAP head, the PDCP head, the RLC head and the MAC head in the first data packet (for example, the SDAP head, the PDCP head, the RLC head and the MAC head are distributed at the front part of the first data packet) can be known, so that when the first data packet is transmitted, the successful transmission of the bits of the position of the SDAP head, the PDCP head, the RLC head and the MAC head is preferentially ensured, namely, the correct transmission of the previous bits is preferentially ensured.
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 adapted to perform the method described in some of the possible designs of the first aspect or the second aspect.
In one possible design, the core network device is configured to send service information of one or more services to the network device; wherein the one or more services include a first service, and service information of the first service includes at least one of: a delay budget for the first service; an error delivery indication of a first service, the error delivery indication of the first service being used to indicate whether the first service supports error delivery; and the error delivery indication of the data stream is used for indicating whether the data stream supports error delivery or not.
In a fourth aspect, the present application provides a communication apparatus, which may be a terminal device (or a chip provided inside the terminal device) or a network device (or a chip provided inside the network device). The communication device has functions of implementing the first aspect or the second aspect, for example, the communication device includes modules or units or means (means) corresponding to the steps of implementing the first aspect or the second aspect, where the functions or units or means may be implemented by software, or implemented by hardware, or implemented by executing corresponding software by hardware.
In one possible design, the communication device includes a processing unit, a communication unit, where the communication unit may be configured to receive and transmit signals to enable 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, 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, where the transceiver is configured to receive signals, and where the processor executes program instructions to perform the method in any possible design or implementation of the first aspect or the second aspect. Wherein the communication device may further comprise one or more memories for coupling with the processor. The one or more memories may be integrated with the processor or may be separate from the processor, and the present application is not limited. The memory may hold the necessary computer programs or instructions to implement the functions referred to in the above-described first or second aspects. The processor may execute a computer program or instructions stored by the memory, which when executed, cause the communication device to implement the method in any of the possible designs or implementations of the first or second aspect described above.
In one possible design, the communication device includes a processor and a memory, where the memory may hold necessary computer programs or instructions to implement the functions referred to in the above first or second aspect. The processor may execute a computer program or instructions stored by the memory, which when executed, cause the communication device to implement the method in any of the possible designs or implementations of the first or second aspect described above.
In one possible design, the communication device includes at least one processor and an interface circuit, wherein the at least one processor is configured to communicate with other devices via the interface circuit and 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 stored therein computer readable instructions 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 application provides a computer program product which, when read and executed by a computer, causes the computer to carry out 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 to a memory for reading and executing a software program stored in the memory to implement the method of any one of the possible designs of the first or second aspects.
These and other aspects of the application will be more readily apparent from the following description of the embodiments.
Drawings
FIG. 1a is a schematic diagram of one possible system architecture to which embodiments of the present application are applicable;
FIG. 1b is a schematic diagram of another network architecture to which embodiments of the present application are applicable;
FIG. 1c is a schematic diagram of another network architecture to which embodiments of the present application are applicable;
Fig. 2a is a schematic diagram illustrating downlink data transmission between layers according to an embodiment of the present application;
Fig. 2b is a schematic diagram of data transmission between a transmitting device and a receiving device according to an embodiment of the present application;
Fig. 2c is a schematic diagram of decoding and HARQ feedback process of a receiving device according to an embodiment of the present application;
fig. 3 is a flow chart corresponding to a data transmission method according to a first 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 flow chart corresponding to a data transmission method according to a second embodiment of the present application;
FIG. 6 is a possible exemplary block diagram of an apparatus involved in an embodiment 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 following description of the technical solutions according to the embodiments of the present invention will be given with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, but not all embodiments.
First, some terms in the embodiments of the present application are explained for easy understanding by those skilled in the art.
(1) 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 capabilities, or other processing device connected to a wireless modem. The terminal device may communicate with one or more core networks or the internet via a radio access network (e.g., radio access network, RAN), and may be a mobile terminal device such as a mobile phone (or "cellular" phone), computer and data card, e.g., a portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile device that exchanges voice and/or data with the radio access network. Such as personal communication services (personal communication service, PCS) phones, cordless phones, session Initiation Protocol (SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal Digital Assistants (PDAs), tablet computers (Pad), computers with wireless transceiver capabilities, and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile Station (MS), remote station (remote station), access Point (AP), remote terminal device (remote terminal), access terminal device (ACCESS TERMINAL), user terminal device (user terminal), user agent (user agent), subscriber station (subscriber station, SS), user terminal device (customer premises equipment, CPE), terminal (terminal), user Equipment (UE), mobile Terminal (MT), etc. The terminal device may also be a wearable device as well as a next generation communication system, e.g. a terminal device in a 5G communication system or a terminal device in a future evolved public land mobile network (public land mobile network, PLMN), etc.
(2) Network equipment: may be a device in a wireless network, for example, a network device may be a radio access network (radio access network, RAN) node (or device), also referred to as a base station, that accesses a terminal to the wireless network. Currently, some examples of RAN equipment are: a new generation base station (generation Node B, gNodeB) in a 5G communication system, a transmission-reception point (transmission reception point, TRP), an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), a wireless fidelity (WIRELESS FIDELITY, wi-Fi) Access Point (AP), an access point in a roadside unit (road unit, RSU), a converged access backhaul (INTEGRATED ACCESS AND backhaul, IAB) system, a control Node and a terminal Node in a TSN network, and the like. In addition, in one network architecture, the network device may include a centralized unit (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 of providing wireless communication functionality for the terminal device, as other possibilities. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the network equipment. For convenience of description, in the 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 embodiments of the application may be used interchangeably. "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: cases where A alone, both A and B together, and B alone, where A and B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC.
And, unless otherwise specified, references to "first," "second," etc. ordinal words of embodiments of the present application are used for distinguishing between multiple objects and not for defining a sequence, timing, priority, or importance of the multiple objects. For example, the first terminal device and the second terminal device are only for distinguishing between different terminal devices, and are not indicative of the difference in priority or importance levels of the two terminal devices.
Fig. 1a is a schematic diagram of a network architecture to which an embodiment of the present application is applicable. 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 communicate with other devices through the wireless network, such as may communicate with other terminal devices. The wireless network includes a radio access network (radio access network, RAN) device 110 and a Core Network (CN) device 120, wherein the RAN device 110 is configured to access the terminal device 130 to the wireless network, and the CN device 120 is configured to manage the terminal device and provide a gateway for communication with an external network. It should be understood that the number of the respective devices in the communication system shown in fig. 1a is only illustrative, and the embodiment of the present application is not limited thereto, and more terminal devices 130, more RAN devices 110, and other devices may be further included in the communication system in practical applications.
A plurality of CN devices 120 may be included in the CN, and when the network architecture shown in fig. 1a is suitable for a 5G communication system, the CN devices 120 may be an access and mobility management function (ACCESS AND mobility management function, AMF) entity, a session management function (session management function, SMF) entity, or a user plane function (user plane function, UPF) entity, and in the embodiment of the present application, the CN devices 120 are taken as UPF entities as an example. Illustratively, the interface between terminal device 130 and RAN device 110 may be referred to as a Uu interface or a null 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 to which the embodiment of the present application is applicable. 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 may be implemented by multiple nodes, and the radio frequency device may be implemented independently from the baseband device, or may be integrated in the baseband device, or a part of the radio frequency device may be integrated in the baseband device. For example, in an LTE communication system, a RAN apparatus (eNB) includes a baseband device and a radio frequency device, where the radio frequency device may be remotely located relative to the baseband device, e.g., a remote radio unit (remote radio unit, RRU) is remotely located relative to the BBU. For another example, in an evolved architecture, a RAN device may include a CU and a DU, where multiple DUs may be centrally controlled by one CU, and the interface between the CU and the DU may be referred to as the F1-U interface.
Fig. 1c is a schematic diagram of another network architecture to which the embodiment of the present application is applicable. With respect to the network architecture shown in fig. 1b, the Control Plane (CP) and the User Plane (UP) of the CU may also be implemented in fig. 1c by separating the Control Plane (CP) CU entity (i.e. CU-CP entity) and the User Plane (UP) CU entity (i.e. CU-UP entity), respectively.
In the above network architecture, the signaling generated by the CU may be transmitted to the terminal device through the DU, or the signaling generated by the terminal device may be transmitted to the CU through the DU. The DU may be passed through to the terminal device or CU directly through protocol layer encapsulation without parsing the signaling. In the following embodiments, transmission or reception of signaling by a DU includes such a scenario if such signaling is involved in the transmission between the DU and the terminal device. For example, signaling of the radio resource control (radio resource control, RRC) layer or the packet data convergence layer protocol (PACKET DATA convergence protocol, PDCP) layer is eventually handled as physical layer signaling to the terminal device or converted from the received physical layer signaling. Under this architecture, the signaling of the RRC or PDCP layer can be considered as being sent either by the DU or by the DU and radio frequency loading.
The network architecture illustrated in fig. 1a, 1b or 1c may be applied to a communication system of various radio access technologies (radio access technology, RAT), for example, a 5G (or new radio, NR) communication system, and may be a future communication system. The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the communication network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is 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-DUs is employed, the network device may be a CU, or a DU, or a RAN device comprising a CU and a DU.
In the network architecture illustrated in fig. 1a, 1b or 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 an RRC layer, a PDCP layer, a radio link control (radio link control, RLC) layer, a medium access control (MEDIA ACCESS control, MAC) layer, and a physical layer (PHYSICAL LAYER, PHY) layer; the user plane protocol layer structure may include the functions of protocol layers such as PDCP layer, RLC layer, MAC layer, and physical layer; in one possible implementation, a service data adaptation (SERVICE DATA adaptation protocol, SDAP) layer may also be included above the PDCP layer. Illustratively, the network device may implement the functions of the protocol layers RRC, PDCP, RLC and MAC by one node, or may implement the functions of the protocol layers by a plurality of nodes. For example, if the network device includes a CU and a DU, the CU and the DU may be divided according to protocol layers of the wireless network, for example, functions of a PDCP layer and above are set at the CU, and functions of a protocol layer below the PDCP layer, for example, functions of an RLC layer and a MAC layer, etc., are set at the DU. The division of the protocol layer is merely an example, and other protocol layers may be divided, for example, division in the RLC layer, where functions of the RLC layer and above are set in the CU, and functions of the protocol layer below the RLC layer are set in the DU; or divided in a certain protocol layer, for example, a part of functions of the RLC layer and functions of protocol layers above the RLC layer are set at CU, and the remaining functions of the RLC layer and functions of protocol layers below the RLC layer are set at DU. In addition, the functions that require processing time to meet the latency requirement may be set in the DU and the functions that do not require processing time to meet the latency requirement may be set in the CU in other manners, such as time-lapse partitioning.
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, a MAC layer and a physical layer, wherein the SDAP layer, the PDCP layer, the RLC layer, the MAC layer and the physical layer can also be collectively called as an access layer. Each layer is divided into a transmitting part and a receiving part according to the transmission direction of data. For example, referring to fig. 2a, a schematic diagram of downlink data transmission between layers is shown, in fig. 2a, the downward arrow indicates data transmission, and the upward arrow indicates data reception. After the PDCP layer acquires data from the upper layer, the PDCP layer transfers the data to the RLC layer and the MAC layer, and the MAC layer generates Transport Blocks (TBs) and performs radio transmission through the physical layer. The data are correspondingly packaged in each layer, the data received from the upper layer of a certain layer are regarded as service data units (SERVICE DATA units, SDUs) of the layer, and the data are packaged into PDU (protocol data unit) by the layer and then transferred to the next layer. For example, data received from an upper layer by the PDCP layer is called PDCP SDU, and data transmitted to a lower layer by the PDCP layer is called PDCP PDU; the data received by the RLC layer from the upper layer is called RLC SDU, and the data transmitted by the RLC layer to the lower layer is called RLC PDU; the data received by the MAC layer from the upper layer is called a MAC SDU, the data transmitted by the MAC layer to the lower layer is called a MAC PDU, which may also be called a transport block. In the protocol, the connections between layers are mostly corresponding in a channel manner. 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 a physical channel (PHYSICAL CHANNEL) below the physical layer to correspond to the physical layer at the other end.
As can also be seen from fig. 2a, the terminal device 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 by the physical layer to the application layer, and then provided by the application layer to the application program; for another example, the application layer may obtain data generated by the application program (such as a video recorded by the user using the application program, etc.), and sequentially transmit the data to the physical layer, and send the data to other communication devices. The non-access stratum may be used to forward user data, such as forwarding uplink data received from the application stratum to the SDAP stratum or forwarding downlink data received from the SDAP stratum to the application stratum.
Referring to fig. 2b, one or more sub-functional entities or modules, such as a multiplexing or demultiplexing entity, a hybrid automatic repeat request (hybrid automatic repeat request, HARQ) entity, 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 (cyclic redundancy check, CRC) check module, may also be included in the physical layer. The above sub-functional entities or modules are described below in terms of a transmitting end device and a receiving end device, respectively. The sending end device may be a terminal device, and the receiving end device may be a network device; or the transmitting end device may be a network device, and the receiving end device may be a terminal device.
For the sender device, the MAC layer may include a multiplexing entity, a HARQ entity, and a coding entity. The multiplexing entity can be used for multiplexing the RLC PDU received from the RLC layer to obtain a MAC PDU and submitting the MAC PDU to the HARQ entity; one RLC layer entity corresponds to one logical channel, and RLC PDUs may also be called MAC SDUs. There are various ways of multiplexing, 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, namely RLC PDU segment 1 and RLC PDU segment 2, and further obtain MAC PDU1 according to RLC PDU segment 1 and MAC PDU2 according to RLC PDU segment 2. For another example, the multiplexing entity may concatenate RLC PDU1 received from logical channel 1 and RLC PDU2 received from logical channel 2, and further obtain a MAC PDU according to the concatenated RLC PDU1 and RLC PDU 2; RLC PDUs of different logical channels can be distinguished by logical channel identification (LCH ID) in the MAC PDU header. In fig. 2b, a cascade is illustrated as an example in a multiplexing manner. Further, the HARQ entity may submit the MAC PDU received from the multiplexing entity to the encoding entity, and then the encoding entity encodes the MAC PDU, and then transmits the encoded MAC PDU to the physical layer. Further, a CRC check module in the physical layer performs CRC check processing on the MAC PDU received from the MAC layer, and transmits the result to the receiving end device.
For the receiving end device, after receiving the data, the CRC check module in the physical layer may perform CRC check on the data, and if the data passes the check, the data may be delivered to the MAC layer. The MAC layer may include a demultiplexing entity, an HARQ entity, and a decoding entity, where after receiving the MAC PDU submitted by the physical layer, the decoding entity in the MAC layer may decode the MAC PDU, and if the decoding is correct, may submit the MAC PDU to the HARQ entity, and then be submitted to the demultiplexing entity by the HARQ entity, where the HARQ entity may also send HARQ feedback information. Further, after receiving the MAC PDU, the demultiplexing entity may demultiplex to obtain a 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 device will be described in detail with reference to fig. 2 c.
Fig. 2c is a schematic diagram of a possible flow of decoding and HARQ feedback of a receiving device, and referring to fig. 2c, the flow may include three parts, where the first part performs decoding operation for a decoding entity, the second part delivers data to an HARQ entity for the decoding entity, and the third part sends HARQ feedback information for the HARQ entity.
Step 201, determining whether the received data is new transmission data, if so, executing step 202, and if not (e.g. retransmission data), executing step 203.
Step 202, the data is decoded and step 205 is performed.
Step 203, determining whether the decoding has not been successful, if the decoding has not been successful, executing step 204, and if the decoding has been successful, not decoding.
Step 204, the data is combined with the previous data, and step 205 is performed.
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, determining whether the decoding has been successful, if so, executing step 208, and if not, executing step 207.
Step 207, update the data stored in the HARQ buffer, and execute step 211.
Step 208, it is determined whether broadcast data is available, if yes, step 210 is executed, and if no, step 209 is executed.
Step 209, determining whether the decoding is successful for the first time, if yes, executing step 210, and if not, executing step 211.
Step 210 submits the decoding result to the upper layer (i.e. the demultiplexing entity in fig. 2 b), and step 211 is performed.
Step 211, judging whether the feedback condition is met, if yes, executing step 213, and if not, executing step 212.
Wherein, the non-compliance with the feedback condition may mean compliance with at least one of: (1) The data is scheduled by a physical downlink control channel (physical downlink control channel, PDCCH) scrambled by a temporary cell-radio network temporary identifier (TC-RNTI) of a temporary cell radio network; (2) the data is broadcast data; (3) timing advance invalidation.
Illustratively, in the above (1), the TC-RNTI may be a temporary identifier allocated to the terminal device by the network device. In the above (2), the data is broadcast data, and it is understood that the data is data transmitted by a broadcast system. In the above (3), the network device may send a 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 may derive the timing advance based on the timing advance command. After the network device sends a timing advance command to the terminal device, a timing advance timer (TIME ADVANCE TIMER, TA timer) is started, the terminal device also starts the same TA timer after obtaining the timing advance, both the network device and the terminal device maintain the TA timer, and whether the timing advance is valid can be judged according to whether the TA timer is overtime. If the TA timer does not timeout, the timing advance is considered valid, otherwise, the timing advance is considered invalid.
In step 212, the HARQ entity does not inform the physical layer to send HARQ feedback information.
In step 213, the HARQ entity informs the physical layer to transmit HARQ feedback information.
From the foregoing, it can be seen that, since data may be erroneous during transmission, the transmitted data may be monitored by means of encoding and decoding, CRC check, and the like. For example, the transmitting end device may multiplex one or more service data into the same transport block, perform HARQ process processing, perform coding, increase CRC check, and then transmit the result to the receiving end device. After receiving the data, the receiver can perform CRC (cyclic redundancy check), and then perform decoding after the CRC 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 check fails or the decoding fails, the data transmission error is indicated, the data is not submitted to the upper layer, and after the retransmission data arrives, the merging decoding is carried out until the decoding is successful, and the data is not submitted to the upper layer. In the mode, the receiving end equipment 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 becoming more and more abundant and diverse, such as being capable of supporting more and more services such as 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 the data packet is transmitted in error, if the data packet is not submitted to the upper layer, but is discarded or waited for retransmission, on one hand, the resource waste can be caused because the data packet received by the receiving terminal device is not fully utilized, on the other hand, because the requirement on the time delay of the services is relatively high, the discarding or waited for retransmission of the data packet with the transmission error can possibly result in poor user experience, for example, the video clamping phenomenon can be caused when the user watches the video.
Based on this, even if the data packet is transmitted in error, it can be considered to continue to be submitted to the upper layer, in this case, although some mosaic phenomenon may still occur in the video due to the fact that the application layer cannot decode completely due to the data packet transmission error, compared with the video blocking caused by adopting the method, the method can not only effectively utilize the received data packet, but also improve the user experience. That is, for services like high-precision voice, high-definition video, etc., since the delay requirement of the data is high and the fault tolerance requirement is low, it is considered that the upper layer delivery, i.e., the error delivery, is performed after the packet transmission error. The high delay requirement 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; a low requirement for fault tolerance may be understood as a packet that is erroneous during transmission and is also useful to the receiving end device.
Furthermore, the embodiment of the application provides a data transmission method, which is used for realizing error submission of the data packet so as to effectively utilize the data packet received by the receiving end equipment and meet the transmission requirement of the service.
The data transmission method provided by the embodiment of the application can relate to interaction between two communication devices, for example, a first communication device and a second communication device, wherein the first communication device can be a transmitting end device, and the second communication device is a receiving end device; or the second communication apparatus may be a transmitting end device, and the first communication apparatus is a receiving end device. Further, the first communication means may be a network device or a communication means capable of supporting the functions required by the network device to implement the method, but may also be other communication means, such as a chip or a chip system. The second communication means may be a terminal device or a communication means capable of supporting the functions required by the terminal device to implement the method, but may of course also be other communication means, such as a chip or a chip system. For ease of description, hereinafter, the method is performed by the network device and the terminal device, that is, the first communication apparatus is the network device and the second communication apparatus is the terminal device.
When the first communication means is a network device and the second communication means is a terminal device, the communication between the terminal device and the network device may include uplink communication and downlink communication. In uplink communication, the terminal device may construct a data packet, the data supporting 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 downlink communications, the network device may construct a data packet, the data supporting 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 the error delivery. The following describes the case of uplink communication and downlink communication in detail 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 be other possible devices, for example, the first communication device is a first terminal device, the second communication device is a second terminal device, in which case, the first terminal device may construct a data packet, the data support error delivery, and send the data packet to the second terminal device, and if the data packet is transmitted in error, the second terminal device may perform error delivery; or the second terminal device may construct a data packet, the data supporting 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 the embodiment of the present 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 the licensed spectrum (licensed spectrum), communication may be performed through the unlicensed spectrum (unlicensed spectrum), and communication may also be performed through both the licensed spectrum and the unlicensed spectrum, which is not limited. The network device and the terminal device can communicate with each other through a frequency spectrum of less than 6 gigahertz (GHz), can also communicate through a frequency spectrum of greater than or equal to 6GHz, and can also communicate by using a frequency spectrum of less than 6GHz and a frequency spectrum of greater than or equal to 6GHz at the same time. Namely, the application is applicable to both low-frequency scenes (such as sub 6G) and high-frequency scenes (greater than or equal to 6G). The embodiment of the application does not limit the frequency spectrum resources used between the network equipment and the terminal equipment.
Example 1
In a first embodiment, some possible implementations will be described for the upstream communication case.
Fig. 3 is a flow chart corresponding to a data transmission method according to a first embodiment of the present application, as shown in fig. 3, including:
in 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 device support errors; whether one or more cells support error delivery; whether one or more logical channels support error delivery. Configuration information 1 is described in detail below in connection with example 1 and example 2.
Example 1
The terminal device may support one or more services, different services may have different requirements, e.g. some services require that the data packet must be transmitted correctly at the receiver before being submitted upwards, while some services may be tolerant of error submission. 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 to not support error delivery.
For example, the configuration information 1 may be configured in various manners whether one or more services support error delivery, for example, the configuration information 1 may be configured to implement whether one or more services support error delivery by configuring whether the 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 that the logical channel 1 supports error delivery, the logical channel 2 does not support error delivery, and then the terminal device may learn 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 for one or more services from the core network device; taking service a as an example, service information of service a includes at least one of: and the delay budget and the error delivery indication of the service A are used for indicating whether the service A indicates error delivery or not. If the service information of the service a includes an error delivery instruction, the network device may determine whether the service a indicates an error delivery according to the error delivery instruction; if the service information of the service a includes the delay budget of the service a, the network device may determine, according to the delay budget of the service a, whether the service a supports error delivery.
In this example, configuration information 1 may also be used to configure whether one or more cells support error delivery, see table 1 for a classification of support of traffic and cells for error delivery.
Table 1: support classification for error delivery by business and cell
As can be seen from table 1, if the configuration information 1 configures that the service a supports the error delivery, the service B does not support the error delivery, and further configures that the cell 1 supports the error delivery, the service a supports the error delivery in the cell 1, and the service B does not support the error delivery in the cell 1. For another example, if the configuration information 1 configures that the service a supports the error delivery, the service B does not support the error delivery, and the cell 1 does not support the error delivery, then the service a does not support the error delivery in the cell 1, and the service B does not support the error delivery in the 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, possible data flows support error delivery, and some data flows do 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 correspondence 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 stream A1 and data stream A2, where data stream A1 supports error delivery, data stream A2 does not support error delivery, data stream A1 corresponds to logical channel 1, and data stream 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 the service B may be mapped to the data stream B3 and the data stream B4, and neither the data stream B3 nor the data stream B4 supports error delivery, and the data stream B3 and the data stream B4 may correspond to the same logical channel, such as the logical channel 3, in which case the configuration information 1 may configure the logical channel 3 not to support error delivery.
There are a number of 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 for one or more services from the core network device; taking service a as an example, service information of service a includes error delivery indication of one or more data streams (such as data stream A1 and data stream A2) corresponding to service a, where the error delivery indication of data stream A1 is used to indicate whether data stream 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 be understood as a certain service, which is not specifically limited.
In step 303, the terminal device composes a first data packet, where the first data packet supports error delivery.
Here, the terminal device composes the first data packet, which may be understood as multiplexing the data received from at least one logical channel by a multiplexing entity in the MAC layer of the terminal device.
Illustratively, the terminal device may construct the data packet (e.g., the first data packet) according to the configuration information 1, for example, the terminal device may construct 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 is constructing a data packet, if the serving cell of the terminal device (which may also be understood as a cell transmitting the data packet constructed by the terminal device) supports error delivery, the terminal device may construct data in at least one logical channel supporting error delivery into the same data packet as much as possible, and construct data in at least one logical channel not supporting error delivery into the same data packet as much as possible; alternatively, the terminal device may not group data of the logical channel supporting the error delivery and data of the logical channel not supporting the error delivery into the same data packet as much as possible.
In the embodiment of the present application, the first data packet supports error delivery, which may include at least one of the following: the service to which the first data packet belongs supports error submission; the cell transmitting the first data packet supports error delivery; some or all of the at least one logical channel supports error delivery. For example, the service to which the first data packet belongs is service a, and if 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 if the at least one logical channel 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 if a portion of the at least one logical channel supports 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 if a portion of the at least one logical channel does not support error delivery, the first data packet may not support error delivery.
In 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 builds the first data packet, the location of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet may be recorded, and the physical layer may be notified, for example, the MAC layer may submit 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 the physical layer receives the first data packet and the indication information a, successful transmission of the bits where the SDAP header, the PDCP header, the RLC header and the MAC header are located can be preferentially ensured when the first data packet is transmitted.
Illustratively, the MAC layer informs the physical layer of the location of the SDAP header, PDCP header, RLC header, MAC header in the first data packet, it is understood that the MAC layer informs or tells the physical layer which bits in the first data packet are important. The physical layer is informed by the MAC layer, and in other possible implementations, rules may be preconfigured by the network device and sent to the terminal device. The rule may be used to characterize which bits in a packet of different sizes are important, e.g., if the size of the packet is a, the first X1 bits in the packet are important, and if the size of the packet is B, the first X2 bits in the packet are important. The terminal device can infer which bits are important for each size of data packet according to the rule, and can further construct 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, can determine which bits in the data packet are important according to the rule and the size of the data packet, so that successful decoding of the important bits is guaranteed preferentially.
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, in this case, the terminal device may determine that the first data packet to be transmitted needs to perform error delivery, then when the first transmission packet is configured, the first data packet may be configured in a segmented manner, and further may include a PDCP SDU or a PDCP SDU segment; or it may be described that one RLC SDU or one RLC SDU fragment is included in the first data packet; or it may be described that one MAC SDU or one MAC SDU fragment is included in the first data packet. In this case, after receiving the first data packet submitted by the MAC layer, the physical layer may learn 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), so that when the first data packet is transmitted, successful transmission of the bits where the SDAP header, the PDCP header, the RLC header, and the MAC header are located is preferentially ensured, that is, correct transmission of the previous bits is preferentially ensured. In this way, when the MAC layer submits the first data packet to the physical layer, it is unnecessary to submit the indication information a to indicate the positions of the SDAP header, the PDCP header, the RLC header, and the MAC header in the first data packet.
In the embodiment of the present application, the sending of the first data packet by the terminal device to the network device may be based on the scheduled data transmission, or may also be the data transmission of the scheduling-free grant (GRANT FREE, GF). The non-scheduling grant may also be referred to as a configuration grant (configured grant, CG), among others.
In the scheduling-based data transmission, the network device may send an Uplink (UL) grant to the terminal device, where the UL grant is used to indicate the first resource, and correspondingly, after the terminal device receives the uplink grant, the terminal device may send the first data packet on the first resource. The trigger factor of the network device for sending the uplink grant to the terminal device may be various, for example, if the terminal device determines that the first data packet needs to be sent, the terminal device may send a scheduling request (scheduling request, SR) to the network device on a physical uplink control channel (physical uplink control channel, PUCCH) first, and then the network device may send the uplink grant to the terminal device after receiving the SR.
In the data transmission without scheduling permission, the network device may pre-configure the periodic resource, and when the terminal device needs to send the first data packet, the first data packet may be sent through the pre-configured first resource. The network device pre-configures periodic resources can be divided into two types, wherein 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 the resources can be considered to occur periodically unless the terminal device receives a release command. Type 2 (Type 2) refers to that the network device configures the period and the start offset through configuration information 3, and then activates and indicates a specific resource (such as indicating a time domain location and a frequency domain location of the resource) through downlink control information (downlink control information, DCI) (for convenience of description, referred to as DCI-1), and unless the terminal device receives a deactivation command, the resource indicated by DCI-1 may be considered to occur periodically.
Some possible implementations of steps 303 to 305 are described below.
Implementation 1
The network device may indicate to the terminal device whether the data carried by the first resource supports error delivery. Accordingly, if the terminal device determines that the data carried by the first resource supports error delivery according to the indication of the network device, the terminal device may construct a first data packet supporting error delivery (step 303), and send the first data packet to the network device by carrying the first data packet onto the first resource (step 304). Further, the network device may receive a first data packet on a first resource (step 305). By adopting the implementation manner, the network equipment determines whether the transmission supports the error delivery by indicating whether the data carried by the first resource supports the error delivery, so that the flexibility of regulation and control of the network equipment is improved.
It should be noted that, in other possible embodiments, if the terminal device determines 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, description is given by taking data supporting error delivery carried by the first resource as an example.
There may be various ways in which the network device indicates 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 one example, the uplink grant 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, the data carried by the first resource supports error delivery; the value of the 1 bit is 0, which indicates that the data carried by the first resource does not support error delivery. In yet another example, if the uplink grant carries the indication information 1, it indicates that the data carried by the first resource supports error delivery, and if the uplink grant 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 uplink grant carries the indication information 1, the data carried by the first resource does not support error delivery, and if the uplink grant does not carry the indication information 1, 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 through the type 1 manner, in an example, the configuration information 2 may carry the indication information 1, where the indication information 1 may include 1 bit; for example, if the value of the 1 bit is 1, the data carried by the first resource supports error delivery; the value of the 1 bit is 0, which indicates that the data carried by the first resource does not support error delivery. In yet 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, 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, 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 the period 1, the start offset 1, the resource 1, the period 2, the start offset 2, and the resource 2, so that the resource 1 that periodically appears according to the period 1 and the start offset 1 may be understood as one set of resources, and the resource 2 that periodically appears according to the period 2 and the start offset 2 may be understood as another set of resources. When the configuration information 2 is used for configuring multiple sets of resources, whether the data carried by the multiple sets of resources support error delivery can be uniformly configured, namely, 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, the data carried by the multiple sets of resources support error delivery, and if the configuration information 2 does not carry the indication information 1, the data carried by the multiple sets of resources do not support error delivery. Or whether the data carried by each set of resources support error delivery can be configured independently, for example, the configuration information 2 configures two sets of resources, namely a first set of resources and a second set of resources, if the configuration information 2 carries the indication information 1a, the data carried by the first set of resources support error delivery, and if the configuration information 2 does not carry the indication information 1a, the data carried by the first set of resources do not support error delivery; the configuration information 2 carries the indication information 1b, which indicates that the data carried by the second set of resources support error delivery, and the configuration information 2 does not carry the indication information 1b, which indicates that the data carried by the second set of resources do not support error delivery.
(3) If the first resource is allocated to the terminal device by the network device through the type 2 manner, in an example, the DCI-1 may carry the indication information 1, where the indication information 1 may include 1 bit; for example, if the value of the 1 bit is 1, the data carried by the first resource supports error delivery; the value of the 1 bit is 0, which indicates that the data carried by the first resource does not support error delivery. In yet another example, if the DCI-1 carries the indication information 1, it indicates that the data carried by the first resource supports error delivery, and if the DCI-1 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 DCI-1 carries the indication information 1, the data carried by the first resource does not support error delivery, and if the DCI-1 does not carry the indication information 1, the data carried by the first resource supports error delivery.
Implementation 2
The terminal device composes a first data packet supporting error delivery (step 303), and may load the first data packet onto a first resource and send the first data packet to the network device, and may also indicate to the network device whether the first data packet supports error delivery (step 304). Further, the network device may receive a first data packet on a first resource (step 305). After the terminal equipment builds the data packet, if the built data packet is determined to support error delivery, the terminal equipment can be used for determining whether the transmission supports error delivery or not, so that the network equipment does not need to indicate whether the data carried by the resource supports error delivery or not when the resource is allocated, and the processing load of the network equipment is reduced.
There may be various ways in which the terminal device indicates to the network device whether the first data packet supports error delivery, for example, the terminal device may indicate whether the first data packet supports error delivery through indication information 2, and the indication information 2 may be uplink control information (uplink control information, UCI).
In one example, the terminal device may send indication information 2 to the network device, 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 yet another example, the terminal device indicates that the first data packet supports error delivery if the indication information 2 is sent to the network device, and indicates that the first data packet does not support error delivery if the indication information 2 is not sent to the network device.
There may be various ways in which the terminal device sends the indication information 2 to the network device, 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 encoded at the moment of joint transmission on the first resource by means of puncturing (puncture); for example, the terminal device may puncture the first data packet, and further transmit the punctured first data packet and the indication information 2 on the first resource. Or (2) jointly transmitting 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 will be appreciated that when the punching method is adopted, the indication information 2 described in the above two examples may be adopted to indicate whether or not error delivery is supported; when the joint coding scheme is employed, the indication information 2 described in the first example above may be employed to indicate whether or not error delivery is supported.
In step 306, the network device determines a first packet transmission error.
Illustratively, the network device determining the first data packet transmission error may include: the network device determines that the CRC 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 data 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 data packet, whether the CRC check is passed or not, and may further submit the first data packet to the MAC layer, and further indicate to the MAC layer whether the CRC check is passed or not. Further, the decoding entity of the MAC layer decodes the first data packet (wherein, whether the CRC check passes an input parameter when the decoding entity can perform decoding), and if the decoding fails (the CRC check may or may not pass at this time), determines that the first data packet has a transmission error; if the CRC check is passed and the decoding is successful, the first data packet can be determined to be correctly transmitted.
In yet 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 may submit the first data packet to the MAC layer (in this case, may not indicate whether the CRC check is passed any more), and the decoding entity of the MAC layer decodes the first data packet, and if the decoding fails, determines that the first data packet is transmitted 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 delivery, CRC check can be not performed 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 network device performing the error submission of the first data packet 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 submission on the first data packet; (3) The RLC layer entity of the network device 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 will be appreciated that the network device performing the error delivery on the first data packet may further comprise other layer entities performing the error delivery on the first data packet, such as the SDAP layer entity performing the error delivery on the first data packet. For example, each entity described above may notify the upper layer of the first packet transmission error when performing error delivery on the first packet.
The following describes the error delivery performed on the first data packet by the different entities.
(1) HARQ entity performs error submission on first data packet
The HARQ entity may submit the first data packet and indication information 3 to the demultiplexing entity, the indication information 3 being used to indicate a transmission error of the first data packet. 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 data packet and the indication information 3 to the demultiplexing entity upon determining that at least one of the following ①②③ is met. Wherein, ① 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. Illustratively, the first threshold, the second threshold, and the duration of the timer may be specified by a protocol; or may be determined by the network device, and further, the network device may further 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 the terminal device receives the data packet 1 (the data packet 1 is new transmission data), if it is determined that the decoding accuracy reaches 20% (less than the first threshold), the data in the HARQ buffer may not be submitted to the demultiplexing entity and updated to the data packet 1; after receiving the data packet 2 (the data packet 2 is the data packet retransmitted for the first time), the terminal equipment combines and decodes the data in the data packet 2 and the HARQ buffer, and if the decoding accuracy reaches 50% (less than the first threshold), the data in the HARQ buffer can be updated to the combined result of the data packet 2 and the data packet 1 without submitting the data to the demultiplexing entity; after receiving the data packet 3 (the data packet 2 is the 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 the first threshold (80%), the decoding result and the indication information 3 may be submitted to the demultiplexing entity, where the indication information 3 indicates that the decoding accuracy of the data packet 3 is 90%.
For another example, after the terminal device receives the data packet 1 (the data packet 1 is new transmission data), if it is determined that the decoding fails, the terminal device may not submit 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 the data packet retransmitted for the first time), the terminal equipment combines and decodes the data in the data packet 2 and the HARQ buffer, if the decoding fails, the terminal equipment does not need to submit to a demultiplexing entity, and updates the data in the HARQ buffer into the combined result of the data packet 2 and the data packet 1; after receiving the data packet 3 (the data packet 3 is the 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 decoding still fails, but the retransmission frequency is 2 and is greater than the second threshold, the decoding result and the indication information 3 can be submitted to the demultiplexing entity.
For another example, after receiving the data packet 1 (the data packet 1 is new transmission data), the terminal device starts a timer, if it is determined that decoding fails, the terminal device may not submit 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 the data packet retransmitted for the first time), the terminal equipment combines and decodes the data in the data packet 2 and the HARQ cache, the decoding fails, if the timer has not timed out yet, the data in the HARQ cache can not be submitted to a demultiplexing entity, and the data in the HARQ cache can be updated to be the combined result of the data packet 2 and the data packet 1; after receiving the data packet 3 (the data packet 3 is the 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 decoding result and the indication information 3 can be submitted to the demultiplexing entity.
It should be noted that: ① Optionally, after the HARQ entity submits the transmission error packet (such as the first packet) to the demultiplexing entity, if the retransmission packet of the first packet is received, the retransmission packet may not be submitted to the demultiplexing entity any more, as shown in (a) or (b) in fig. 4. In this case, when the delay requirement of the service is relatively high, the retransmitted data packet may not meet the delay requirement of the service, and thus, the retransmitted data packet may 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 (such as the first data packet) to the demultiplexing entity, if the transmission is determined to be correct after the HARQ entity receives the retransmitted data packet of the first data packet, the retransmitted data packet may be delivered to the demultiplexing entity, and if the transmission error is determined to be incorrect, the retransmitted data packet may not be delivered to the demultiplexing entity, as shown in (c) in fig. 4. Or after the HARQ entity delivers the transmission error data packet (such as the first data packet) to the demultiplexing entity, if the retransmission data packet of the first data packet is received, whether the transmission is correct or not may be delivered to the demultiplexing entity, as shown in (d) in fig. 4.
② Optionally, for data packets supporting error delivery (such as the first data packet), in one example, the HARQ entity may perform the corresponding feedback depending on whether the first data packet is delivered to the demultiplexing entity. For example, if the HARQ entity submits the first packet with the transmission error to the demultiplexing entity, the HARQ entity may not feed back an Acknowledgement (ACK) or a negative acknowledgement (negative acknowledgement, NACK) for the first packet, i.e. no feedback is performed. For another example, if the HARQ entity delivers the first packet with the transmission error to the demultiplexing entity, the ACK may be fed back for the first packet, and if not delivered, the NACK may be fed back for the first packet or the feedback may not be performed. For another example, if the HARQ entity delivers the first packet with the transmission error to the demultiplexing entity, no feedback is performed, and if not delivered, NACK may be fed back for the first packet. In yet another example, the HARQ entity may also perform the 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, the HARQ entity feeds back ACK, and if the HARQ entity determines that the first data packet is transmitted incorrectly, the HARQ entity feeds back NACK or does not perform feedback. For another example, if the HARQ entity determines that the first data packet is transmitted correctly, feedback is not performed, and if the HARQ entity determines that the first data packet is transmitted incorrectly, NACK is fed back.
(2) The demultiplexing entity performs error delivery for the first data packet.
The demultiplexing entity may submit the first data packet and indication information 4 to the RLC layer entity, the indication information 4 being used to indicate a transmission error of the first data packet. Here, if the first data packet is a MAC PDU submitted by the HARQ entity, after the demultiplexing entity receives the MAC PDU submitted by the HARQ entity, the MAC PDU may be demultiplexed into one or more MAC SDUs and submitted 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 the following ①②③④. Wherein ① the de-multiplexing entity obtains the logical channel identifier corresponding to the MAC SDU1; ② The de-multiplexing entity obtains a logic channel identifier corresponding to the MAC SDU1, and the logic channel corresponding to the logic channel identifier supports error delivery; ③ The de-multiplexing entity determines that the MAC SDU1 is not delivered to the RLC layer entity; ④ The demultiplexing entity determines that the decoding accuracy of the first data packet is greater than a third threshold. ⑤ The time period T1 has elapsed since the first time the erroneous packet of MAC SDU1 was received.
The demultiplexing entity may obtain the logical channel identifier corresponding to the MAC SDU1 in various manners, and in one possible implementation manner, the demultiplexing entity may parse the first data packet to obtain the logical channel identifier corresponding to the MAC SDU1, for example, the demultiplexing entity parses the first data packet from the MAC subheader to obtain the logical channel identifier corresponding to the MAC SDU 1. In yet another possible implementation, 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, the manner in which the demultiplexing entity obtains the logical channel identifier is not limited, and the description will be given below taking the logical channel identifier obtained by parsing the MAC subheader of the first data packet by the demultiplexing entity as an example. The third threshold may be agreed upon by the protocol or may be determined by the network device, and further the network device may send the third threshold to the terminal device. The value of the duration T1 may be agreed by a protocol, or may be determined by a network device, and further, the network device may send the value of T1 to a terminal device.
The following describes in detail examples 1 to 5.
Example 1: if the de-multiplexing entity analyzes one or more logic channel identifiers from the MAC subheader of the first data packet, the de-multiplexing entity submits one or more de-multiplexed MAC SDUs to one or more RLC layer entities, otherwise, the de-multiplexing 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 the logical channel 1 and the identifier of the logical channel 2, and then submits the MAC SDU1 to the RLC layer entity 1 through the logical channel 1 and the MAC SDU2 to the RLC layer entity 2 through the logical channel 2. If the demultiplexing entity does not parse the identifier of the logical channel 1 and the identifier of the logical channel 2, the demultiplexing entity may not submit any more.
Example 2: the demultiplexing entity analyzes one or more logic channel identifiers from the MAC sub-head of the first data packet, and part or all of the logic channels in the one or more logic channels support error delivery, so that the demultiplexed MAC SDU can be delivered to the RLC layer entity through the logic channels supporting the error delivery, and the MAC SDU can not be delivered for the logic channels not supporting the error delivery.
For example, the first 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 analyzes the identifier of the logical channel 1 and the identifier of the logical channel 2 from the MAC subheader of the first data packet, the demultiplexing entity may submit the MAC SDU1 to the RLC layer entity 1 through the logical channel 1 and may submit the MAC SDU2 to the RLC layer entity 2 through the logical channel 2.
For another example, the first 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 de-multiplexing entity analyzes the identifier of the logical channel 1 and the identifier of the logical channel 2 from the MAC sub-header of the first data packet, the de-multiplexing entity can submit the MAC SDU1 to the RLC layer entity 1 through the logical channel 1, and can also indicate the transmission error of the MAC SDU 1; for MAC SDU2, retransmission may be waited, and after receiving the MAC SDU2 that is retransmitted and successfully decoded by combining, the MAC SDU2 may be delivered to the RLC layer entity 2 through the logical channel 2.
It will be appreciated that in this example, logical channel 1 supports error delivery, indicating that the latency requirement for data in logical channel 1 may be relatively high, logical channel 2 does not support error delivery, indicating that the latency requirement for data in logical channel 2 may be relatively low. In one possible scenario, if the transmitting end device only has resources supporting error delivery when transmitting data, the transmitting end device may multiplex the data in logical channel 1 and the data in logical channel 2 into the same data packet (i.e., the first data packet) for transmission. Accordingly, after determining that the first data packet is transmitted in error, the demultiplexing entity of the receiving end device may submit the MAC SDU1 to the upper layer before waiting for retransmission. After receiving the retransmitted first data packet, if the merging 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, where the demultiplexing entity may again submit the MAC SDU1 to the RLC layer entity 1 through the logical channel 1 (may also notify the RLC layer entity 1 that the MAC SDU1 submitted at this time is submitted for the second time, and/or may also notify the RLC layer entity 1 that the transmission of the MAC SDU1 submitted at this time is correct), or may also not submit the MAC SDU1.
Example 3: the demultiplexing entity analyzes one or more logic channel identifiers from the MAC sub-head of the first data packet, the one or more logic channels comprise logic channels (such as logic channel 1) supporting error delivery, and the demultiplexing entity does not deliver the MAC SDU to the upper layer through the logic channel 1 yet, otherwise, does not deliver the MAC SDU to the upper layer.
For example, the first 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 analyzes the identifier of the logical channel 1 and the identifier of the logical channel 2 from the MAC subheader of the first data packet, it determines whether the MAC SDU1 has been submitted to the RLC layer entity 1 through the logical channel 1, if the MAC SDU1 has been submitted 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, the demultiplexing entity has submitted 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 submitted any more, or the MAC SDU1 may be submitted to the RLC layer entity 1 through the logical channel 1 again, further, the RLC layer entity 1 may be notified, and the RLC layer entity 1 may be notified that the MAC SDU1 is submitted for the nth time (for example, the second time or the third time), and/or the RLC layer entity 1 may be notified that the transmission of the MAC SDU1 is wrong (or transmission is correct); if the MAC SDU1 has not been delivered to the RLC layer entity 1 through the logical channel 1, the MAC SDU1 may be delivered to the RLC layer entity 1 through the logical channel 1. For MAC SDU2, retransmission may be waited, and after receiving the MAC SDU2 that is retransmitted and successfully decoded by combining, the MAC SDU2 may be delivered to the RLC layer entity 2 through the logical channel 2.
Example 4: the demultiplexing entity analyzes one or more logic channel identifiers from the MAC sub-head of the first data packet, the one or more logic channels comprise logic channels (such as logic channel 1) supporting error delivery, and the HARQ indicates that the decoding accuracy of the first data packet is greater than a third threshold, and the MAC SDU can be delivered to an upper layer through the logic channel 1, otherwise, the MAC SDU is not delivered to the upper layer.
For example, the first 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 de-multiplexing entity analyzes the identifier of the logical channel 1 and the identifier of the logical channel 2 from the MAC subheader of the first data packet, it can 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 de-multiplexing entity can submit the MAC SDU1 to the upper layer through the logical channel 1, and the de-multiplexing entity can wait for retransmission for the MAC SDU2, and after receiving the retransmitted and combined successfully decoded MAC SDU2, the de-multiplexing entity can submit the MAC SDU2 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 one or more logical channel identifiers from the MAC subheader of the first data packet, where the one or more logical channels include a logical channel (e.g., logical channel 1) that supports error delivery. If the demultiplexing entity determines that the time length T1 has elapsed since the first time the error data packet of the MAC SDU1 is received, the demultiplexing entity can submit the MAC SDU1 to the upper layer through the logic channel 1, otherwise, the demultiplexing entity does not submit the MAC SDU1 to the upper layer.
For example, the demultiplexing entity receives packet 1, packet 1 including MAC SDU1 from logical channel 1 and MAC SDU2 from logical channel 2, logical channel 1 supporting error delivery, logical channel 2 not supporting error delivery. If the demultiplexing entity determines that the data packet 1 is the error data packet of the MAC SDU1 received for the first time, the demultiplexing entity may not submit the MAC SDU1 and the MAC SDU2, and starts a timer, where the duration of the timer is T1. The demultiplexing entity receives the repeated data packet of the data packet 1 (called data packet 2), and the data packet 2 is transmitted in error, but when the timer is overtime, the demultiplexing entity can submit the MAC SDU1 to the upper layer through the logical channel 1. For MAC SDU2, retransmission may be waited, and after receiving the MAC SDU2 that is retransmitted and successfully decoded by combining, the MAC SDU2 may be delivered to the RLC layer entity 2 through the logical channel 2.
It will be appreciated that examples 1 to 5 above are merely illustrative of some exemplary situations, and other possible situations may be included in the embodiments of the present application, for example, the demultiplexing entity may also submit a MAC SDU to an upper layer when a plurality of conditions are satisfied at the same time; for example, the first data packet includes the MAC SDU1, and the demultiplexing entity may submit the MAC SDU1 to the upper layer, specifically not listed, if it is determined that the MAC SDU1 is not submitted to the RLC layer entity and the decoding accuracy of the first data packet is greater than the third threshold.
It should be noted that, if the demultiplexing entity determines that the first packet includes a MAC CE, the demultiplexing entity may apply (apply) the MAC CE. In one example, the demultiplexing entity may apply the MAC CE included in the first data packet after determining that the first data packet is transmitted correctly. In yet another example, the demultiplexing entity may perform the act of MAC CE indication after meeting at least one of the following ①②③. The ① de-multiplexing entity analyzes the first data packet to obtain a logic channel identifier; ② The de-multiplexing entity determines that the first data packet is received for the first time; ③ The demultiplexing entity determines that the decoding accuracy of the first data packet is greater than a fourth threshold. 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.
By way of example, there may be a variety of specific implementations of the application MAC CE, such as performing the actions indicated by the MAC CE. Some possible implementations of the application MAC CE are described in detail below, to name a few. For example, the MAC CE reports (buffer status report, BSR) the MAC CE for the buffer, the network device may schedule the terminal device according to the BSR. For example, if the MAC CE is a power headroom report (power headroom report, PHR) MAC CE, the network device may schedule the terminal device according to the PHR, for example, if the terminal device reports that its own power headroom is smaller, and the uplink subband width used by the terminal device when the network device discovers that the reporting PHR is 4MHz, which indicates that the power of the terminal device is insufficient to support subband transmission greater than 4MHz, so that it may be avoided to allocate subband width greater than 4MHz to the terminal device at a time.
(3) The RLC layer entity and PDCP layer entity perform error delivery on the first data packet
For example, when the RLC layer entity or PDCP layer entity receives a MAC SDU (such as MAC SDU 1) from the MAC layer and the MAC layer indicates that the MAC SDU1 is a transmission error packet, the RLC layer entity or PDCP layer entity may move a window of the respective layer, i.e., the RLC layer entity may move a window of RLC SN and the PDCP layer entity may move a window of PDCP SN, according to an RLC Sequence Number (SN) and PDCP SN.
In one example, when the RLC layer entity or 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 one transmission error, the RLC layer entity or PDCP layer entity may move the window of the respective layer according to the RLC Sequence Number (SN) and PDCP SN if it is determined that the MAC SDU1 is received for the first time, and may not move the window of the respective layer according to the RLC SN and PDCP SN if it is determined that the MAC SDU1 is not received for the first time (e.g., may be received for the second or third time), thereby avoiding the occurrence of errors caused by moving the window for the same MAC SDU multiple times. For example, even if the MAC SDU1 received the second or third time is properly transmitted, the RLC layer entity or PDCP layer entity may not move the window of the respective layer according to the RLC SN and PDCP SN any more.
In addition, for performing error delivery on the first data packet, it is also required to be explained that:
(1) When the RLC layer entity receives a MAC SDU (e.g., MAC SDU 1) 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, and the specific implementation may be determined by the network device, and further, the network device may also configure this specific implementation for the terminal device, for example, the network device may configure this specific implementation for the terminal device through RRC signaling.
(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 can be submitted to the PDCP layer entity for N times before, and then the MAC SDU is not submitted any more, the value of N can be determined by network equipment, and further, the network equipment can also indicate the value of N to terminal equipment; or the RLC layer entity may submit the MAC SDU to the PDCP layer entity when receiving that the MAC layer indicates that the decoding success rate is greater than a certain threshold (the threshold may be agreed by a protocol, or may be determined by a network device, further, the network device may also send the value of the threshold to the terminal device); or the RLC layer entity may submit the MAC SDU to the PDCP layer entity when a time period T2 has elapsed since the first time the erroneous data packet of the MAC SDU is received, where the time period T2 may be agreed by a protocol, or may be determined by a network device, and further, the network device may also 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 (such as an application layer), the upper layer may indicate that the delivered packet is a transmission error packet. As can be appreciated, since both the network device and the terminal device may be the receiving end device of the data packet, when the network device is 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 transmission error data packet; when the terminal device is used as the receiving end device, the PDCP layer entity (or the SDAP layer entity) of the terminal device may submit a data packet to the application layer of the terminal device, and instruct the submitted data packet to be a data packet with a transmission error, so that the application layer of the terminal device may count a packet error rate (packet error rate, PER), and then feed back 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 errors, the core network device can not participate in traffic statistics and does not charge the data packet, or can calculate traffic or charge according to a preset proportion, for example, the data packet comprises 100 bytes, and can calculate according to 40 bytes when traffic statistics is performed. The embodiment of the application does not limit the preset proportion.
Example two
In the second embodiment, some possible implementations will be described for the downlink communication case.
Fig. 5 is a flow chart corresponding to a data transmission method according to a second embodiment of the present application, as shown in fig. 5, including:
in step 501, the network device sends configuration information 4 to the terminal device, where the configuration information 4 is used to configure 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 delivery, if the terminal device supports error delivery, the network device may send the configuration information 4 to the terminal device, and if the terminal device does not support error delivery, the network device may not send the configuration information 4 to the terminal device any more. The method that the terminal device reports whether the terminal device supports the error delivery to the network device may be various, 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 the error delivery.
In one example, after receiving a data packet, if it is determined that the data packet needs to be submitted to an error, the terminal device configured with the error-submitting function may not perform CRC check on the data packet at the physical layer and submit 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 be submitted to an error, the terminal device configured with the error submitting function may perform CRC check on the data packet at the physical layer, and may submit 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 the CRC needs to be performed (or whether the CRC is turned off) for the packet supporting the error delivery, and a second parameter for indicating that the packet supporting the error delivery is also delivered to an upper layer when decoding the error. The first parameter and the second parameter may be the same parameter, or may be two different parameters, which is not limited in particular.
In step 503, the network device composes a second data packet, the second data packet supporting error delivery.
Here, the network device composes the second data packet, which may be understood as multiplexing the data received from the at least one logical channel by a multiplexing entity in the MAC layer of the network device. 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; some or all of the at least one logical channel supports error delivery. For specific implementation, reference may be made to the description of the first packet supporting error delivery in the first embodiment.
For example, if the network device includes a CU and a DU, the data packet (e.g., the second data packet) may be composed of 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 above embodiment one, 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 packet according to the notification information. For example, if the notification information is used to notify whether one or more logical channels of the DU support error delivery, the DU may multiplex data in logical channels supporting error delivery into the same data packet as much as possible and multiplex data in logical channels not supporting error delivery into the same data packet as much as possible when constructing the data packet according to the notification information.
In step 504, the network device sends a second data packet to the terminal device.
Accordingly, in step 505, the terminal device receives a second data packet from the network device.
For example, 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 may be a dynamically scheduled resource; for example, the network device sends DCI-2 to the terminal device, where DCI-2 is used to schedule the second resource, or DCI-2 is used to indicate the second resource; accordingly, after receiving DCI-2, the terminal device may receive the second data packet on the second resource. Or the second resource may also be a semi-statically scheduled resource; for example, the network device configures a period (such as a period configured by an RRC message) for the terminal device in advance, and then activates the terminal device by using DCI-3, where the DCI-3 may indicate a time domain location and a frequency domain location of a block of resources, and then the terminal device considers that each period later, the network device transmits data on the block of resources.
It should be noted that, whether the network device supports the data packet to the terminal device or not supports the error delivery may be understood that the network device indicates whether the MAC PDU supports the error delivery or not. If the MAC PDU supports error delivery and one or some MAC SDUs in the MAC PDU does not support error delivery, the terminal equipment can deliver the MAC SDUs supporting error delivery to an upper layer after decoding failure; for the MAC SDUs that do not support error delivery, the MAC SDUs may not be delivered to the upper layer, and may be delivered to the upper layer after waiting for successful retransmission.
There are a number of ways in which the network device may 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: the DCI-2 may carry indication information 5, where the indication information 5 is used to indicate whether the data carried by the second resource supports error delivery. Illustratively, the indication information 5 may include 1 bit; for example, if the value of the 1 bit is 1, the data carried by the second resource supports error delivery; the value of the 1 bit is 0, which indicates that the data carried by the second resource does not support error delivery. It may be appreciated that the indication information 5 may be carried in one or more fields of DCI-2, such as one or more of a HARQ process number (HARQ process number) indication field, a modulation and coding scheme (modulation and coding scheme, MCS) indication field, a frequency domain resource allocation (frequency domain resource assignment) indication field, a time domain resource allocation (time domain resource assignment) indication field, a reserved field carried in DCI-2. Taking the MCS indication field of the indication information 5 carrying DCI-2 as an example, for example, the MCS indication field includes 5 bits, and a total of 32 (2 5) code points, where 25 code points have specified their specific meanings, and the remaining 7 code points are reserved code points, so that two code points in 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, the data carried by the second resource supports the error delivery, and if the DCI-2 does not carry the indication information 5, the data carried by the second resource does not support the error delivery. Or if the DCI-2 carries the indication information 5, the data carried by the second resource does not support error delivery, and if the DCI-2 does not carry the indication information 5, the data carried by the second resource supports error delivery.
Example 3: if the terminal device is DCI-2 received according to a preset control-resource set (CORESET) and/or a preset search space (SEARCH SPACE), it may be determined that the data carried by the second resource scheduled by DCI-2 supports error delivery, and if the data carried by the second resource scheduled by DCI-2 is not DCI-2 received according to the preset control resource set and not according to the preset search space, it may be determined that the data carried by the second resource scheduled by DCI-2 does not support error delivery. The data of the resource bearer scheduled by the DCI of the preset control resource set and/or the preset search space bearer supports error submission. The preset control resource set and/or the preset search space may be configured for the network device to be a terminal device.
Example 4: if the terminal equipment is DCI-2 received by the PDCCH scrambled by the preset RNTI, the data carried by the second resource of the DCI-2 scheduling can be determined to support error delivery, and if the data carried by the second resource of the DCI-2 scheduling is not the DCI-2 received by the PDCCH scrambled by the RNTI, the data carried by the second resource of the DCI-2 scheduling can be determined not to support error delivery. The preset RNTI may be a newly defined RNTI, which is used to indicate data supporting error delivery of the resource bearer scheduled by DCI-2. The preset RNTI may be configured for the network device for the terminal device.
Example 5: if the terminal device is DCI-2 received on a preset bandwidth part (BWP), it may be determined that the data carried by the second resource scheduled by DCI-2 supports error delivery, or else, it may be determined that the data carried by the second resource scheduled by DCI-2 does not support error delivery. Illustratively, the network device may configure one or more BWP for the terminal device, e.g., the network device may select at least one BWP from the one or more BWP as a preset BWP after configuring the one or more BWP, and indicate the preset BWP to the terminal device; for another example, the network device may also indicate that it is a preset BWP while configuring the terminal device with a certain BWP or BWPs.
Example 6: if the terminal equipment is DCI-2 received on the preset time-frequency resource, determining that the data carried by the second resource scheduled by the DCI-2 supports error delivery, otherwise, determining that the data carried by the second resource scheduled by the DCI-2 does not support error delivery. The preset time-frequency resources may be determined by the network device and indicative of the terminal device, for example.
It will be appreciated that the above examples 1 and 2 can be understood as whether the network device explicitly indicates that the data carried by the second resource supports error delivery, and examples 3 to 6 can be understood as whether the network device implicitly indicates that the data carried by the second resource supports error delivery.
(2) Semi-static 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, the data carried by the second resource supports error delivery; the value of the 1 bit is 0, which indicates that the data carried by the second resource does not support error delivery.
In yet another example, if the DCI-3 carries the indication information 5, it indicates that the data carried by the second resource supports error delivery, and if the DCI-3 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-3 carries the indication information 5, the data carried by the second resource does not support error delivery, and if the DCI-3 does not carry the indication information 5, the data carried by the second resource supports error delivery.
It should be noted that, for semi-persistent scheduling, the foregoing description is given by taking, as an example, whether the data of the resource bearer of the semi-persistent scheduling is indicated by DCI-3 to support error delivery, and in other possible embodiments, whether the data of the resource bearer of the semi-persistent scheduling supports error delivery may also be indicated by an RRC message for a configuration period.
Illustratively, the terminal device may be configured with up to 8 sets of semi-statically scheduled resources on one BWP. When the RRC message indicates whether the data of the semi-statically scheduled resource bearer supports error delivery, it may be that whether the data of each set of semi-statically scheduled resource bearers supports error delivery is separately indicated, for example, if the data of a certain set of semi-statically scheduled resource bearers is indicated in the RRC message to support error delivery, no indication may be required in 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, whether the data carried by all the semi-static scheduling resources support error delivery or not can be configured uniformly, for example, if the error delivery is indicated in the RRC message, the indication is not needed in DCI of the semi-static scheduling resources, and as long as any set of semi-static scheduling resources are activated, all the data transmitted on the set of semi-static resources support error delivery.
In step 506, the terminal device determines a second packet transmission error.
In step 507, the terminal device performs error delivery on the second data packet.
Here, step 506 and step 507 may refer to step 306 and step 307 in the above embodiment adaptively, 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 each implementation of performing error delivery by the respective entities may refer to implementation of performing error delivery by the HARQ entity, the demultiplexing entity, the RLC layer entity, the PDCP layer entity, and the SDAP layer entity in the network device.
For the 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 the embodiment of the present application, taking the first resource as an example, the data carried by the first resource may support error delivery, which may also be described as first resource support error delivery. The logical channel supports error delivery, and may also be described as data carried by the logical channel supports error delivery. The service support error delivery may also be described as data support error delivery belonging to the service. The data stream may also be described as supporting error delivery.
(3) The configuration information (such as configuration information 1, configuration information 2, configuration information 3, or configuration information 4) in the embodiment of the present application may be sent to the terminal device in various manners, for example, through RRC signaling, which is not limited in particular.
(4) The step numbers of the flowcharts (e.g., fig. 3 and 5) described in the embodiments of the present application are only an example of the execution flow, and do not limit the execution sequence of the steps, and in the embodiments of the present application, there is no strict execution sequence between the steps that have no time sequence dependency relationship with each other. For example, in fig. 5, step 501 may be performed prior to step 503, or may be performed concurrently with step 503.
The scheme provided by the embodiment of the application is mainly introduced from the perspective of equipment interaction. It will be appreciated that, in order to implement the above-described functions, the network device or terminal device may include corresponding hardware structures and/or software modules that perform the respective functions. 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 implemented as hardware or computer software driven 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.
The embodiment of the application can divide the functional units of the terminal equipment and the network equipment according to the method example, for example, each functional unit can be divided corresponding to each function, and two or more functions can be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
In case of integrated units, fig. 6 shows a possible exemplary block diagram of the apparatus involved in an embodiment of the 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 the operations of the apparatus 600. The communication unit 603 is used to support communication of the apparatus 600 with other devices. Alternatively, the communication unit 603, also referred to as a transceiver unit, 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 a terminal device) in any of the above embodiments, for example, a 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 examples of the methods above; or the processing unit 602 mainly performs internal actions of the terminal device in the method example, the communication unit 603 may support communication between the apparatus 600 and other devices (such as network devices). Or the apparatus 600 may be a network device (or a chip disposed in a network device) in any of the above embodiments, for example, a network 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 network device in the method examples above; or the processing unit 602 mainly performs internal actions of the network device in the method example, 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: if the first data packet is determined to be transmitted in error, error delivery is performed on the first data packet.
In one possible design, processing unit 602 determines a first packet transmission error, including: processing unit 602 determines that the CRC of the first data packet fails; and/or the processing unit 602 determines that the first packet decoding failed.
In one possible design, the communication unit 603 is further configured to: transmitting first indication information, wherein the first indication information is used for indicating that data carried by a 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 grant, wherein the uplink grant is used for indicating the first resource, and the uplink grant carries first indication information; or sending first configuration information, wherein the first configuration information is used for configuring the first resource, and the first configuration information carries first indication information; or sending control information, wherein the control information is used for activating the first resource, and the control information carries first indication information.
In one possible design, the 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 on 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 the first control information carries third indication information; or receiving second control information, wherein the second control information is used for activating a second resource, and the second control information carries third indication information; or receiving second configuration information, where the second configuration information is used to configure the 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 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 supporting error submission of the resource bearer scheduled by the third control information of the preset control resource set and/or the preset search space bearer; or receiving third control information in the 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 data of a resource carried by third control information scheduled by the physical downlink control channel supports error delivery.
In one possible design, the communication unit 603 is further configured to: and receiving third configuration information, wherein the third configuration information is used for configuring an error submitting function for the communication device.
In one possible design, the processing unit 602 is further configured to: the HARQ entity is controlled to deliver 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, the fourth indication information is used to indicate the decoding accuracy of the first data packet.
In one possible design, before the processing unit 602 controls the HARQ entity to submit the first data packet and the fourth indication information to the demultiplexing entity, at least one of the following is 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 the processing unit 602 determines that the HARQ entity receives the retransmission packet of the first packet, the processing unit submits the retransmission packet to the demultiplexing entity; further, the first data packet may be a new transmission data packet.
In one possible design, before the processing unit 602 controls the HARQ entity to forward the retransmission packet to the demultiplexing entity, it is further configured to: and determining that the retransmission data packet is correctly transmitted.
In one possible design, the processing unit 602 is further configured to: the controlling HARQ entity feeds back an acknowledgement ACK for the first data packet.
In one possible design, the processing unit 602 is further configured to: the demultiplexing entity is controlled to submit the first data packet and fifth indication information to the RLC layer entity, the fifth indication information being for indicating a transmission error of the first data packet.
In one possible design, the processing unit 602 may further include at least one of the following before controlling the demultiplexing entity to submit the first data packet to the RLC layer entity: analyzing the first data packet to obtain a logic channel identifier; analyzing the first data packet to obtain a logic channel identifier, wherein the logic channels corresponding to the logic channel identifier support error delivery; determining that the first data packet is not submitted to the RLC layer entity; and determining that the decoding accuracy of the first data packet is greater than a third threshold.
In one possible design, the processing unit 602 is further configured to: and if the first data packet comprises the MAC CE, applying the MAC CE.
In one possible design, before the processing unit 602 performs the act of MAC CE indication, at least one of the following is further included: analyzing the first data packet to obtain a logic 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.
In one possible design, the processing unit 602 is further configured to: and if the first data packet is determined to be received for the first time, controlling the RLC layer entity to move a window of the RLC SN.
In yet another embodiment, the processing unit 602 is configured to: constructing a first data packet, wherein the first data packet supports error submission; the communication unit 603 is configured to: and sending the first data packet.
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 submission; the cell transmitting the first data packet supports error delivery; the first data packet includes data from at least one logical channel, and part or all of the at least one logical channel supports error delivery.
In one possible design, the communication unit 603 is further configured to: receiving first indication information, wherein the first indication information is used for indicating data carried by a first resource to support error delivery; and transmitting the first data packet on the first resource.
In one possible design, the communication unit 603 is further configured to: receiving an uplink grant, wherein the uplink grant is used for indicating a first resource, and the uplink grant carries first indication information; or receiving first configuration information, wherein the first configuration information is used for configuring first resources, and the first configuration information carries first indication information; or receiving control information, wherein the control information is used for activating the first resource, and the control information carries first indication information.
In one possible design, the 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 second indication information is used to indicate that the first data packet supports error delivery when the first data packet meets at least one of: 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; the timer corresponding to the first data packet times out.
In one possible design, the communication unit 603 sends the first data packet and the second indication information, including: and sending the first data packet and the second indication information on the first resource.
In one possible design, the processing unit 602 is further configured to: punching the first data packet; the communication unit 603 is further configured to: transmitting the first data packet and the second indication information after punching on the first resource; or the processing unit 602 is further configured to: performing joint coding on the first data packet and the second indication information; the communication unit 603 is further configured to: and transmitting the jointly coded information on the first resource.
In one possible design, the communication unit 603 is further configured to: second configuration information is received, the second configuration information being used to indicate 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: fourth indication information is received from the CU, the fourth indication information being used to indicate whether one or more logical channels support error delivery.
In one possible design, the processing unit 602 is further configured to: the MAC layer entity is controlled to submit the first data packet and fifth indicating information to the physical layer entity, wherein the fifth indicating information is used for indicating the position of at least one of an SDAP head, a PDCP head, an RLC head and an MAC head of the first data packet in the first data packet; and the control physical layer entity sends the first data packet according to the fifth indication information.
In one possible design, the first data packet may include one PDCP SDU or one PDCP SDU fragment.
It should be understood that the division of the units in the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated when actually implemented. And the units in the device can be all realized in the form of software calls through the processing element; or can be realized in hardware; it is also possible that part of the units are implemented in the form of software, which is called by the processing element, and part of the units are implemented in the form of hardware. For example, each unit may be a processing element that is set up separately, may be implemented as integrated in a certain chip of the apparatus, or may be stored in a memory in the form of a program, and the functions of the unit may be called and executed by a certain processing element of the apparatus. Furthermore, all or part of these units may be integrated together or may be implemented independently. The processing element described herein may in turn be a processor, which may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in a processor element or in the form of software called by a processing element.
In one example, the unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, for example: one or more Application SPECIFIC INTEGRATED Circuits (ASIC), or one or more microprocessors (DIGITAL SINGNAL processors, DSP), or one or more field programmable gate arrays (field programmable GATE ARRAY, FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the units in the apparatus may be implemented in the form of a scheduler of processing elements, the processing elements may be processors, such as a general purpose central processing unit (central processing unit, CPU), or other processor that may invoke a program. For another example, the 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 device for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit of the chip for receiving signals from other chips or devices. The above unit for transmitting is an interface circuit of the apparatus for transmitting signals to other apparatuses. For example, when the device is implemented in the form of a chip, the transmitting unit is an interface circuit of the chip for transmitting signals to other chips or devices.
Fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application. Which 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 part 720, a signal processing part 730. The antenna 710 is connected to the radio frequency part 720. In the downlink direction, the radio frequency part 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 part 730 for processing. In the uplink direction, the signal processing part 730 processes information of the terminal device and transmits the processed information to the radio frequency part 720, and the radio frequency part 720 processes information of the terminal device and transmits the processed information to the network device through the antenna 710.
The signal processing part 730 may include a modem subsystem for implementing processing of the data communication protocol layers; the system also comprises a central processing subsystem for realizing the processing of the terminal equipment operating system and the application layer; in addition, other subsystems, such as a multimedia subsystem for implementing control of a terminal device camera, screen display, etc., a peripheral subsystem for implementing connection with other devices, etc., may be included. The modem subsystem may be a separately provided chip.
The modem subsystem may include one or more processing elements 731, including, for example, a host CPU and other integrated circuits. In addition, the modulation and demodulation subsystem may also include a storage element 732 and an interface circuit 733. The storage element 732 is used for storing 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 in a memory outside the modulation and demodulation subsystem, which is loaded for use when in use. The interface circuit 733 is used to communicate with other subsystems.
The modulation and demodulation 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 above terminal device and an interface circuit for communicating with other devices. In one implementation, the unit of the terminal device implementing each step in the above method may be implemented in the form of a processing element scheduler, for example, the apparatus for a terminal device includes a processing element and a storage element, and the processing element invokes the program stored in the storage element to perform the method performed by the terminal device in the above method embodiment. The memory element may be a memory element where the processing element is on the same chip, i.e. an on-chip memory element.
In another implementation, the program for executing the method executed by the terminal device in the above method may be a storage element on a different chip than the processing element, i.e. an off-chip storage element. At this time, the processing element calls or loads a program from the off-chip storage element on 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 implementing the steps of the above method may be configured as one or more processing elements, which are 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.
The units of the terminal device for implementing the steps in the method can be integrated together and implemented in the form of an SOC chip for implementing the method. At least one processing element and a storage element can be integrated in the chip, and the processing element invokes the stored program of the storage element to implement the method executed by the terminal device; or at least one integrated circuit may be integrated in the chip for implementing the method performed by the above terminal device; or may be combined with the above implementation, the functions of part of the units are implemented in the form of processing element calling programs, and the functions of part of the units are implemented in the form of integrated circuits.
It will be 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 adapted to perform any of the methods performed by the terminal device provided by the above method embodiments. The processing element may be configured in a first manner: that is, a part or all of the steps executed by the terminal device are executed in a manner of calling the program stored in the storage element; the second way is also possible: i.e. by means of integrated logic circuitry of hardware in the processor element in combination with instructions to perform part or all of the steps performed by the terminal device; of course, it is also possible to perform part or all of the steps performed by the terminal device in combination with the first and second modes.
The processing elements herein are as described above and 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 microprocessor DSPs, 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 memory element may be one memory or may be a collective term for a plurality of memories.
The terminal device shown in fig. 7 is capable of carrying out the respective procedures involving the terminal device in the method embodiment illustrated in fig. 3 or fig. 5. The operations and/or functions of the respective modules in the terminal device shown in fig. 7 are respectively for implementing the corresponding flows in the above-described method embodiment. Reference is specifically made to the description of the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid redundancy.
Fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application. Which may be a network device (such as a DU) in the above embodiments, for implementing the operations of the network device in the above embodiments. As shown in fig. 8, the network device includes: an antenna 801, a radio frequency device 802, and a baseband device 803. The antenna 801 is connected to a radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information transmitted from the terminal device via the antenna 801, and transmits the information transmitted from the terminal device to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes information of the terminal device and sends the processed information to the radio frequency device 802, and the radio frequency device 802 processes information of the terminal device and sends the processed information to the terminal device through the antenna 801.
The baseband apparatus 803 may include one or more processing elements 8031, including, for example, a master 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 for storing programs and data; the interface 8033 is used to interact with the radio frequency device 802, such as a common public radio interface (common public radio interface, CPRI). The above means for network device may be located in the baseband means 803, e.g. the above means for network device may be a chip on the baseband means 803 comprising at least one processing element for performing the steps of any one of the methods performed by the above network device and interface circuitry for communicating with other means. In one implementation, the units of the network device implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for a network device includes a processing element and a storage element, where the processing element invokes the program stored in the storage element to perform the method performed by the network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing elements, i.e., on-chip memory elements, or may be memory elements on a different chip than the processing elements, i.e., off-chip memory elements.
In another implementation, the units of the network device 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), e.g. the baseband device comprises 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 processing element invokes the stored program of the storage element to implement the method executed by the above network device; or at least one integrated circuit may be integrated within the chip for implementing the method performed by the above network device; or may be combined with the above implementation, the functions of part of the units are implemented in the form of processing element calling programs, and the functions of part of the units are implemented in the form of integrated circuits.
It will be 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 adapted to perform any of the methods performed by the network device provided by the above method embodiments. The processing element may be configured in a first manner: that is, a part or all of the steps executed by the network device are executed in a manner of calling the program stored in the storage element; the second way is also possible: i.e. by means of integrated logic circuitry of hardware in the processor element in combination with instructions to perform part or all of the steps performed by the network device; of course, some or all of the steps performed by the above network device may also be performed in combination with the first and second modes.
The processing elements herein are as described above and 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 microprocessor DSPs, 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 memory element may be one memory or may be a collective term for a plurality of memories.
The network device shown in fig. 8 is capable of implementing the 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 embodiment. Reference is specifically made to the description of the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid redundancy.
Fig. 9 is a schematic structural diagram of another network device according to an embodiment of the present application. Which may be a network device (e.g., 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: processor 910, memory 920, and interface 930, processor 910, memory 920, and interface 930 are in signal connection.
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 various elements above may be implemented by one or more integrated circuits configured to implement the methods above. For example: one or more ASICs, or one or more microprocessor DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or may be combined with the above implementations.
It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (44)

1. A method of data transmission, the method comprising:
The communication device receives a first data packet;
the communication device determines that the first data packet fails to be decoded in a Media Access Control (MAC) layer, and the communication device does not execute Cyclic Redundancy Check (CRC) on the first data packet;
the communication device performs error delivery on the first data packet.
2. The method of claim 1, wherein the communication device is located at a network appliance.
3. The method according to claim 2, wherein the method further comprises:
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 on the first resource.
4. A method according to claim 3, wherein the communication means transmitting the first indication information comprises:
The communication device sends an uplink grant, wherein the uplink grant is used for indicating the first resource, and the uplink grant carries the first indication information; or alternatively
The communication device sends first configuration information, wherein the first configuration information is used for configuring the first resource, and the first configuration information carries the first indication information; or alternatively
The communication device sends control information, wherein the control information is used for activating the first resource, and the control information carries the first indication information.
5. The method according to claim 2, wherein the method further comprises:
The communication device receives second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.
6. The method of claim 5, wherein the first data packet and the second indication information are carried on a first resource allocated by the communication device.
7. The method of claim 1, wherein the communication device is located at a terminal equipment.
8. The method of claim 7, wherein the first data packet is carried on a second resource;
the method further comprises the steps of: 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.
9. The method of claim 8, wherein the communication device receiving the third indication information comprises:
The communication device receives first control information, wherein the first control information is used for scheduling the second resource, and the first control information carries the third indication information; or alternatively
The communication device receives second control information, wherein the second control information is used for activating the second resource, and the second control information carries the third indication information; or alternatively
The communication device receives second configuration information, wherein the second configuration information is used for configuring the second resource, and the second configuration information carries the third indication information.
10. The method of claim 7, wherein the first data packet is carried on a second resource;
The method further comprises the steps of:
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 of the resource bearer scheduled by the third control information carried by the preset control resource set and/or the preset search space support error submission; or alternatively
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 data of a resource bearer scheduled by the third control information borne by the physical downlink control channel supports error delivery.
11. The method according to any one of claims 7 to 10, further comprising:
The communication device receives third configuration information, which is used for configuring an error submitting function for the communication device.
12. The method according to any one of claims 1 to 11, wherein the communication device performs error delivery on the first data packet, comprising:
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.
13. The method of claim 12, wherein the fourth indication information is used to indicate a decoding accuracy of the first data packet.
14. The method according to claim 12 or 13, characterized in that before the HARQ entity of the communication device delivers the first data packet and the fourth indication information to a demultiplexing entity, it further comprises at least one of:
the HARQ entity of the communication device determines that the decoding accuracy of the first data packet is greater than a first threshold;
the HARQ entity of the communication device determines that the retransmission times of the first data packet is larger than a second threshold value;
and the HARQ entity of the communication device determines that the timer corresponding to the first data packet is overtime.
15. The method according to any one of claims 12 to 14, 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.
16. The method of claim 15, wherein the HARQ entity of the communication device further comprises, prior to submitting the retransmission packet to the demultiplexing entity:
the HARQ entity of the communication device determines that the retransmission packet transmission is correct.
17. The method according to any one of claims 12 to 16, further comprising:
the HARQ entity of the communication device feeds back an acknowledgement ACK for the first data packet.
18. The method according to any one of claims 1 to 17, wherein the communication device performs error delivery on the first data packet, comprising:
The demultiplexing entity of the communication device submits the first data packet and fifth indication information to a radio link control RLC layer entity, the fifth indication information being for indicating a transmission error of the first data packet.
19. The method of claim 18, wherein the demultiplexing entity of the communications device further comprises at least one of:
the demultiplexing entity of the communication device analyzes the first data packet to obtain a logic channel identifier;
The demultiplexing entity of the communication device analyzes the first data packet to obtain a logic channel identifier, and the logic channels corresponding to the logic channel identifier support error delivery;
a demultiplexing entity of the communication device determining that the first data packet is not submitted to the RLC layer entity;
a demultiplexing entity of the communication device determines that a decoding accuracy of the first data packet is greater than a third threshold.
20. The method according to any one of claims 1 to 19, further comprising:
and if the demultiplexing entity of the communication device determines that the first data packet comprises the Media Access Control (MAC) Control Element (CE), the MAC CE is applied.
21. The method of claim 20, wherein the demultiplexing entity of the communications apparatus, prior to performing the act of MAC CE indication, further comprises at least one of:
the demultiplexing entity of the communication device analyzes the first data packet to obtain a logic channel identifier;
the de-multiplexing entity of the communication device determining that the first data packet was received for the first time;
A demultiplexing entity of the communication device determines that a decoding accuracy of the first data packet is greater than a fourth threshold.
22. The method according to any one of claims 18 to 21, 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 a window of an RLC sequence number SN.
23. A method of data transmission, the method comprising:
The communication device builds a first data packet, wherein the first data packet supports error delivery, and the data packet supporting error delivery does not need to execute CRC check;
The communication device sends the first data packet;
Wherein the first data packet supports error delivery, comprising: the first data packet supports error delivery when decoding fails at the MAC layer.
24. The method of claim 23, wherein the first data packet supports error delivery, comprising at least one of:
the service to which the first data packet belongs supports error submission;
the cell transmitting the first data packet supports error submission;
The first data packet includes data from at least one logical channel, and part or all of the at least one logical channel supports error delivery.
25. A method according to claim 23 or 24, characterized in that the communication means are located at a terminal device.
26. The method of claim 25, wherein the method further comprises: the communication device receives first indication information, wherein the first indication information is used for indicating that data carried by a first resource supports error delivery;
The communication device transmits a first data packet, including: the communication device transmits the first data packet on the first resource.
27. The method of claim 26, wherein the communication device receiving the first indication information comprises:
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; or alternatively
The communication device receives first configuration information, wherein the first configuration information is used for configuring the first resource, and the first configuration information carries the first indication information; or alternatively
The communication device receives control information, wherein the control information is used for activating the first resource, and the control information carries the first indication information.
28. The method of claim 25, wherein the method further comprises:
The communication device sends second indication information, wherein the second indication information is used for indicating that the first data packet supports error delivery.
29. The method of claim 28, wherein the second indication information is used to indicate that the first data packet supports error delivery, comprising:
the second indication information is used for indicating that the first data packet supports error delivery when the first data packet accords with at least one of the following:
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.
30. The method of claim 28 or 29, wherein the communication device transmitting the first data packet and the second indication information comprises:
the communication device transmits the first data packet and the second indication information on a first resource.
31. The method of claim 30, wherein the communication device transmitting the first data packet and the second indication information on a first resource comprises:
The communication device punches the first data packet and sends the punched first data packet and the second indication information on the first resource; or alternatively
The communication device performs joint coding on the first data packet and the second indication information, and sends the joint coded information on the first resource.
32. The method according to any one of claims 25 to 31, further comprising:
The communication device receives second configuration information indicating whether one or more logical channels support error delivery.
33. A method according to claim 23 or 24, wherein the communication means is located at a network device.
34. The method of claim 33, wherein the first data packet is carried on a second resource;
The method further comprises the steps of:
And the communication device sends third indication information, wherein the third indication information is used for indicating that the data carried by the second resource supports error delivery.
35. The method according to claim 33 or 34, characterized in that the method further comprises:
Fourth indication information is received from the concentration unit CU, the fourth indication information being used to indicate whether one or more logical channels support error delivery.
36. The method according to any one of claims 23 to 35, wherein the communication device transmitting the first data packet comprises:
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 a service data adaptation SDAP header, a packet data convergence layer protocol PDCP header, an RLC header and an 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.
37. The method according to any of claims 23 to 36, wherein the first data packet comprises one PDCP service data unit, SDU, or one PDCP SDU fragment.
38. A communication system comprising 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 6, 12 to 24, 33 to 37.
39. The communication system according to claim 38, wherein the core network device is configured to send service information of one or more services to the network device;
Wherein the one or more services include a first service, and service information of the first service includes at least one of the following:
A delay budget for the first service;
An error delivery indication of a first service, the error delivery indication of the first service being used to indicate whether the first service supports error delivery;
And the error delivery indication of one or more data streams corresponding to the first service is used for indicating whether the data streams support error delivery or not.
40. A communication device comprising means for performing the steps of the method of any of claims 1 to 37.
41. A communication 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 of claims 1 to 37.
42. A communications device comprising a processor for invoking a program stored in memory to perform the method of any of claims 1 to 37.
43. A computer readable storage medium comprising a program which, when executed by a processor, performs the method of any of claims 1 to 37.
44. A computer program product, characterized in that the computer program product, when read and executed by a computer, causes the method according to any one of claims 1 to 37 to be performed.
CN201980103359.2A 2019-12-31 2019-12-31 Data transmission method and device Active CN114902637B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/130917 WO2021134680A1 (en) 2019-12-31 2019-12-31 Data transmission method and apparatus

Publications (2)

Publication Number Publication Date
CN114902637A CN114902637A (en) 2022-08-12
CN114902637B true CN114902637B (en) 2024-05-17

Family

ID=76686145

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980103359.2A Active CN114902637B (en) 2019-12-31 2019-12-31 Data transmission method and device

Country Status (2)

Country Link
CN (1) CN114902637B (en)
WO (1) WO2021134680A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116456477A (en) * 2023-03-30 2023-07-18 华为技术有限公司 Communication method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761687B2 (en) * 2007-06-26 2010-07-20 International Business Machines Corporation Ultrascalable petaflop parallel supercomputer
CN102655448A (en) * 2011-03-03 2012-09-05 工业和信息化部电信传输研究所 Data transmission method for medium access control layer of long-term evolution system
CN108260222A (en) * 2016-12-29 2018-07-06 大唐移动通信设备有限公司 A kind of method and apparatus of ascending resource scheduling
CN109756468A (en) * 2017-11-07 2019-05-14 中兴通讯股份有限公司 A kind of restorative procedure of data packet, base station and computer readable storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064665B (en) * 2006-04-27 2010-06-23 上海无线通信研究中心 Service quality based HARQ method
CN108307519B (en) * 2016-09-30 2021-05-11 华为技术有限公司 Message transmission method, device and system
CN110234124B (en) * 2019-04-19 2022-04-01 维沃移动通信(深圳)有限公司 Information transmission method and terminal equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761687B2 (en) * 2007-06-26 2010-07-20 International Business Machines Corporation Ultrascalable petaflop parallel supercomputer
CN102655448A (en) * 2011-03-03 2012-09-05 工业和信息化部电信传输研究所 Data transmission method for medium access control layer of long-term evolution system
CN108260222A (en) * 2016-12-29 2018-07-06 大唐移动通信设备有限公司 A kind of method and apparatus of ascending resource scheduling
CN109756468A (en) * 2017-11-07 2019-05-14 中兴通讯股份有限公司 A kind of restorative procedure of data packet, base station and computer readable storage medium

Also Published As

Publication number Publication date
WO2021134680A1 (en) 2021-07-08
CN114902637A (en) 2022-08-12

Similar Documents

Publication Publication Date Title
CN106992846B (en) Data sending method, data receiving method and device
WO2018028269A1 (en) Resource scheduling method and device
CN110621075B (en) Method and device for transmitting data
CN111865508B (en) Communication method and communication device
CN118316581A (en) User equipment and system for performing transmitting and receiving operations
US20210399846A1 (en) Apparatus, method and computer program for packet duplication
WO2013017096A1 (en) Method, base station and user equipment for transmitting scheduling information
WO2021065153A1 (en) Terminal and communication method
WO2021170136A1 (en) Communication method and apparatus
CN110870373B (en) Method and equipment for configuring resources
CN114342535B (en) Method and device for transmitting and receiving uplink signals
CN114041314A (en) User equipment and scheduling node
US20220377781A1 (en) Method, apparatus, computer program product and computer program
KR20090016419A (en) Method for controlling a harq operation in a dynamic radio resource allocation
CN111757507A (en) Communication method and device
CN114902637B (en) Data transmission method and device
WO2021146868A1 (en) Communication method and apparatus
CN108702649B (en) Transmission device and method for status indication and communication system
WO2022077511A1 (en) Communication method and apparatus
WO2021065154A1 (en) Terminal and communication method
CN113939019A (en) Communication method and communication device
CN115119224A (en) Data transmission method and device
WO2023216986A1 (en) Buffer status report (bsr) indication method, and apparatus
US20240356684A1 (en) Data transmission method and apparatus
WO2024165436A1 (en) Methods, communications devices, and infrastructure equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant