WO2024001831A1 - 通信方法、终端设备、网络设备及通信系统 - Google Patents

通信方法、终端设备、网络设备及通信系统 Download PDF

Info

Publication number
WO2024001831A1
WO2024001831A1 PCT/CN2023/100756 CN2023100756W WO2024001831A1 WO 2024001831 A1 WO2024001831 A1 WO 2024001831A1 CN 2023100756 W CN2023100756 W CN 2023100756W WO 2024001831 A1 WO2024001831 A1 WO 2024001831A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu set
pdu
terminal device
network device
indication information
Prior art date
Application number
PCT/CN2023/100756
Other languages
English (en)
French (fr)
Inventor
胡少领
徐海博
薛丽霞
Original Assignee
华为技术有限公司
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
Priority claimed from CN202210872898.6A external-priority patent/CN117375775A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024001831A1 publication Critical patent/WO2024001831A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end

Definitions

  • Embodiments of this application relate to the field of communications, specifically to communication methods, terminal equipment, network equipment and communication systems.
  • the upstream scheduling of the terminal device by the network device is based on the scheduling request (SR) and buffer status report (BSR) sent by the terminal device.
  • SR scheduling request
  • BSR buffer status report
  • the network device can learn that the terminal device has uplink data that needs to be transmitted based on the SR, and the amount of data cached in the cache of the terminal device can be learned based on the BSR.
  • the network device After receiving the uplink scheduling request, the network device schedules uplink data through downlink control information (DCI). After receiving the scheduled DCI, the terminal device uploads uplink data on the designated time and frequency resources. After receiving the uplink data, the network device will not immediately reply with an acknowledgment message (ACK) or negative acknowledgment (NACK) through the HARQ of the MAC layer to indicate whether the uplink data was successfully received. Therefore, the terminal device cannot immediately determine whether the upload of the uplink data is successful, resulting in the terminal device being unable to determine the processing method of the data related to the uplink data, resulting in insufficient utilization of uplink resources, resulting in a waste of uplink resources.
  • DCI downlink control information
  • the terminal device defaults that the uplink data #1 is uploaded successfully. In fact, the uplink data #1 was not uploaded successfully, and the number of retransmissions of the uplink data #1 reached the upper limit, so the network device did not instruct the retransmission of the uplink data #1. By default, the terminal device uploads uplink data #1 successfully, so the terminal device can continue to upload uplink data #2 related to the uplink data #1 (for example, the decoding of uplink data #2 needs to depend on uplink data #1). In this case, the terminal device uploading uplink data #2 will cause a waste of uplink resources.
  • this application provides a communication method so that the terminal device can determine whether the upload of uplink data is successful and avoid the waste of uplink resources caused by uploading data without uploading data.
  • a communication method is provided. This method can be executed by the terminal device or by a component (such as a chip or circuit) of the terminal device, which is not limited in this application.
  • a component such as a chip or circuit
  • the following description takes terminal device execution as an example.
  • the communication method includes: the terminal device reports first indication information to the network device, and the first indication information indicates the second PDU set referenced (also called dependent) by the first protocol data unit set (Protocol Data Unit set, PDU set) ;
  • the terminal device determines whether the second PDU set is successfully uploaded based on at least one of the timeout condition of the timer of the terminal device and the feedback condition of the network device to the first indication information.
  • the first PDU set includes the PDU set to be sent by the terminal device
  • the second PDU set includes the PDU set that the terminal device has sent.
  • the first PDU set refers to the second PDU set to indicate: the successful decoding of the first PDU set is based on the second PDU set.
  • the successful decoding of set is a prerequisite.
  • the terminal device reports indication information indicating that the first PDU set to be sent refers to the second PDU set that has been sent, and after sending the first indication information, according to the timeout situation of the started timer (such as , timing length, whether it has timed out, etc.) and at least one of the feedback situation of the network device for the received first indication information (such as sending information in response to the first indication information), determine whether the second PDU set is uploaded successfully. That is to say, through this technical solution, the terminal device can determine whether the second PDU set is successfully uploaded.
  • the terminal device can determine the processing of the first PDU set based on the determined result of whether the second PDU set is successfully uploaded. For example, if the second PDU set is not successfully uploaded, the terminal device determines that the first PDU set does not need to be uploaded. Because the successful decoding of the first PDU set is predicated on the successful decoding of the second PDU set, when the second PDU set is not successfully uploaded, that is Even if the first PDU set is uploaded, it cannot be decoded correctly.
  • the terminal device can determine the processing method of the first PDU set based on the judgment result, thereby avoiding the waste of uplink resources caused by uploading the first PDU set without uploading the first PDU set.
  • the first indication information includes a media access control layer control element (MAC CE), and the MAC CE includes a logical channel identifier LCID and an identifier of the second PDU set.
  • the LCID indicates the logical channel corresponding to the MAC CE, and the logical channel is used to transmit the identification of the second PDU set referenced by the first PDU set.
  • the signaling format of the first indication information reported by the terminal device can be MAC CE, following the signaling format already defined in the existing protocol (such as the MAC CE format defined in 3GPP TS 38.321), to avoid passing the The newly defined signaling format realizes the function of the above-mentioned first indication information and simplifies the solution.
  • the method when it is determined that the second PDU set is not successfully uploaded, the method further includes: the terminal device discards the first PDU set.
  • the terminal device determines that the second PDU set has not been successfully uploaded, it can determine that even if the first PDU set is uploaded, the first PDU set cannot be correctly parsed, so there is no need to upload the first PDU set. Further, in order to save cache space, the first PDU set can be discarded or deleted from the cache.
  • the terminal device discards the first PDU set, including: after the first timer expires or when the first timer expires, if the first PDU is cached in the cache of the terminal device set, the first PDU set in the cache will be discarded.
  • the first timer is a discard timer set by the terminal device for the first PDU set, and the starting time of the first timer is when the packet data convergence protocol (PDCP) entity of the terminal device receives the
  • the first PDU sets the moment of the last bit of the last PDU (also called time point), and the timing length of the first timer is less than the frame arrival period.
  • the frame arrival period indicates the arrival of two adjacent frames in the buffer. interval.
  • the PDCP entity of the terminal device can be understood as the transmission entity of the PDCP layer of the terminal device (also called transmitting PDCP entity).
  • the terminal device expires after the first timer expires (where the expiration may also be called timeout, expire) or when the first timer expires (which may also be called a time point). , time point), the first PDU set is cached in the cache of the terminal device, indicating that the second PDU set was not successfully uploaded.
  • the method when it is determined that the second PDU set is successfully uploaded, the method further includes: the terminal device discards some of the PDUs in the first PDU set; or, the terminal device sends the first PDU set.
  • the terminal device when the terminal device determines that the second PDU set is successfully uploaded, the terminal device can indirectly learn that the PDUs included in the first PDU set can be uploaded, but the specific upload situation needs to be based on the scheduling of the network equipment. For example, the network device may successfully schedule only a portion of the PDUs in the first PDU set. For another example, the network device successfully schedules all PDUs in the first PDU set. In summary, when the terminal device determines that the second PDU set is successfully uploaded, the subsequent processing of the first PDU set may be partially or completely successfully sent.
  • the terminal device discards part of the PDUs in the first PDU set, including: within the expiration of the first timer, if part of the PDUs in the first PDU set is cached in the cache of the terminal device, then Some PDUs in the first PDU set in the cache are discarded.
  • the first timer is a discard timer set by the terminal device for the first PDU set, and the starting time of the first timer is when the PDCP entity of the terminal device receives the last bit of the last PDU of the first PDU set. moment.
  • the cache of the terminal device includes a cache of a radio link control (RLC) layer of the terminal device or a packet data convergence protocol (PDCP) of the terminal device layer cache.
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the cache of the terminal device can be the cache of different protocol layers, which improves the flexibility of the solution.
  • the terminal device determines that the second PDU set has not been successfully uploaded based on the network device's feedback on the first indication information, including: the terminal device receives the second indication information from the network device, and the second The indication information is used to indicate that the second PDU set was not successfully uploaded.
  • the second indication information is used to indicate that the second PDU set has not been successfully uploaded, including: the second indication information indicates that some or all of the PDUs included in the second PDU set have not been successfully uploaded; or, The second indication information indicates that the number of successfully uploaded PDUs in the second PDU set is less than or equal to the first threshold.
  • the terminal device determines the second PDU set based on the timeout of the timer of the terminal device. Unsuccessful uploading includes: the terminal device starts the second timer when sending the first instruction information. If the second timer times out and the terminal device does not receive the scheduling information from the network device, the terminal device determines the second PDU set Upload not successful.
  • the method before the terminal device sends the first indication information, the method further includes: the terminal device sends a second PDU set to the network device, the second PDU set includes the third indication information, and the third indication The information is used by the network device to determine whether all PDUs of the second PDU set or a specified number of PDUs have been successfully received.
  • the third indication information includes at least one of the following: identification of the first and last PDU included in the second PDU set; or, the total number of PDUs included in the second PDU set; or , the number of PDUs that need to be successfully transmitted for the second PDU set to be successfully decoded; or, the ratio of the number of PDUs that need to be successfully transmitted for the second PDU set to be successfully decoded and the total number of PDUs included in the second PDU set; or, the second PDU Identification of the PDU contained in the set belonging to the second PDU set; or, the sequence number of the PDU contained in the second PDU set in the second PDU set.
  • the method further includes: when (when) or after (after) the protocol layer entity of the terminal device receives the first PDU set generated by the application layer of the terminal device,
  • the first PDU set performs header detection to determine the identity of the first PDU set and the identity of at least one PDU set referenced by the first PDU set.
  • the protocol layer of the terminal device encapsulates the identifier of the first PDU set and the identifier of at least one PDU set in the header of the protocol layer of the first PDU set.
  • the first PDU set generated by the application layer includes the identifier of the first PDU set and the identifier of the reference at least one PDU set.
  • the first PDU or each PDU of the first PDU set includes the identifier of the first PDU set and the identifier of the first PDU set.
  • the second PDU set is one of at least one PDU set.
  • the terminal device can learn the identity of a certain PDU set and the identity of another PDU set referenced by the PDU set through header detection, so that the terminal device can learn the reference relationship between different PDU sets.
  • the protocol layer includes at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, non-access layer (Non-Access Stratum, NAS) or wireless Resource control (radio resource control, RRC) layer.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • N-Access Stratum Non-Access Stratum
  • RRC wireless Resource control
  • the second aspect provides a communication method.
  • the method may be executed by a network device, or may be executed by a component (such as a chip or circuit) of the network device, which is not limited in this application.
  • a component such as a chip or circuit
  • the following takes network device execution as an example.
  • the communication method includes: the network device receives first indication information from the terminal device, and the first indication information is used to indicate the second PDU set referenced by the first protocol data unit group PDU set.
  • the network device determines not to schedule the first PDU set.
  • the first PDU set includes the PDU set to be sent by the terminal device
  • the second PDU set includes the PDU set referenced by the first PDU set that the terminal device has sent
  • the first PDU set refers to the second PDU set to represent: the first PDU set
  • the successful decoding of is predicated on the successful decoding of the second PDU set.
  • the network device when the network device determines that the second PDU set is successfully received, the network device schedules the first PDU set.
  • the network device determines that all the PDUs required for successful decoding of the second PDU set have not been successfully received, including: the network device determines that the network device does not save the identification of the second PDU set.
  • the method further includes: the network device receives a second PDU set from the terminal device, and the second PDU set includes third indication information.
  • the network device determines whether to save the identity of the second PDU set based on the three indication information.
  • the third indication information For the description of the third indication information, reference may be made to the description of the third indication information in the first aspect, which will not be described again here.
  • the method further includes: the network device sends second indication information to the terminal device, and the second indication information is used to indicate that the network device is unsuccessful. Receive all PDUs required for successful decoding of the second PDU set.
  • the method before the network device sends the second indication information to the terminal device, the method further includes: the network device determines that the timing duration of the first timer is greater than the frame arrival period.
  • the first timer is a discard timer set by the terminal device for the first PDU set.
  • the starting time of the first timer is the moment when the PDCP entity of the terminal device receives the first PDU set.
  • the frame arrival period indicates The interval between two adjacent frames arriving at the terminal device buffer.
  • the second indication information is used to indicate that the network device has not successfully received all PDUs required for successful decoding of the second PDU set including: the second indication information includes an identification of at least one PDU set, Indicates that at least one PDU set is not Successfully uploaded, the second PDU set is one of at least one PDU set.
  • the third aspect provides a communication method.
  • the method may be executed by a network device, or may be executed by a component (such as a chip or circuit) of the network device, which is not limited in this application.
  • a component such as a chip or circuit
  • the following takes network device execution as an example.
  • the communication method includes: the network device determines that the first condition is met; the network device sends fourth indication information to the terminal device, where the fourth indication information is used to indicate PDUs successfully received by the network device and/or PDUs received unsuccessfully.
  • the first condition includes at least one of the following: on the premise that the fourth instruction information is sent periodically, the moment when the fourth instruction information is sent, the network device determines whether the third PDU set is successfully received, or the network device receives a message from the terminal device. trigger information. The trigger information is used to trigger the network device to determine the fourth indication information.
  • the network device can notify the terminal device of successfully received PDUs and/or unsuccessfully received PDUs through the fourth indication information, so that the terminal device can determine whether the uplink data is successfully uploaded.
  • the network device determines whether the third PDU set is successfully received, including: the network device determines whether all PDUs included in the third PDU set are successfully received, and/or the network device successfully receives Whether the number of PDUs exceeds the first threshold, the received PDUs successfully received by the network device are PDUs included in the third PDU set.
  • the first threshold is predefined.
  • the method further includes: the network device receives the third PDU set from the terminal device, and the third The PDU set includes fifth indication information. The network device determines whether all PDUs required for successful decoding of the third PDU set are successfully received according to the fifth indication information.
  • the terminal device when the terminal device sends the third uplink PDU set, it can carry the fifth indication information in the third PDU set, so that the network device can determine whether the third PDU set included in the third PDU set has been successfully received based on the fifth indication information. All PDUs.
  • the five indication information includes at least one of the following: the identification of the first and last PDU included in the third PDU set; or, the total number of PDUs included in the third PDU set; or, The number of successfully transmitted PDUs required for the third PDU set to be successfully decoded; or the ratio of the number of successfully transmitted PDUs required for the third PDU set to be successfully decoded and the total number of PDUs included in the third PDU set; or the number of PDUs included in the third PDU set The identification of the PDU belonging to the third PDU set; or the sequence number of the PDU contained in the third PDU set in the third PDU set.
  • the network device determines whether all PDUs included in the third PDU set have been successfully received according to the fifth indication information, including: the network device determines whether it has received all the PDUs included in the third PDU set according to the fifth indication information. partial PDU, all PDUs included in the third PDU set were not successfully received; the method also includes: the network device deletes or discards some PDUs in the third PDU set.
  • the network device when the network device determines that it has not successfully received all PDUs included in the third PDU set, but has received some PDUs included in the third PDU set, the network device can discard some of the received PDUs.
  • the fourth aspect provides a communication method.
  • the method may be executed by the terminal device, or may be executed by a component (such as a chip or circuit) of the terminal device, which is not limited in this application.
  • a component such as a chip or circuit
  • the following description takes terminal device execution as an example.
  • the communication method includes: the terminal device receives fourth indication information from the network device, and the fourth indication information is used to indicate PDUs successfully received and/or PDUs unsuccessfully received by the network device.
  • the terminal device determines to delete the first PDU based on the PDU that has not been successfully received.
  • the unsuccessfully received PDU is a PDU in the third PDU set, and the first PDU includes at least one of the following: a PDU included in the fourth PDU set, an untransmitted PDU in the third PDU set, or a PDU included in the fifth PDU set.
  • the fourth PDU set is the PDU set that refers to the third PDU set
  • the fifth PDU set is the PDU set that refers to the third PDU set and/or the fourth PDU set
  • the fourth PDU set refers to the third PDU set, which means: fourth
  • the successful decoding of the PDU set is based on the successful decoding of the third PDU set.
  • the fifth PDU set refers to the third PDU set and/or the fourth PDU set.
  • the successful decoding of the fifth PDU set is based on the third PDU set and/or the fourth PDU set.
  • the successful decoding of the four PDU set is a prerequisite.
  • the terminal device can determine that some PDUs are not successfully transmitted based on the received fourth indication information. For example, the terminal device determines that PDU #1 is not successfully transmitted, and PDU #1 is a PDU in PDU set #1. This ensures that the terminal device determines that the PDU set that refers to PDU set #1 does not need to be uploaded, or that other PDUs in PDU set #1 do not need to be uploaded, so that the terminal device can discard the PDU set or PDU that does not need to be uploaded, saving the cache and uplink of the terminal device. resource.
  • the method before the terminal device receives the third indication information from the network device, the method further includes Including: the terminal device sends a third PDU set to the network device, the third PDU set includes fifth indication information, and the fifth indication information is provided to the network device so as to serve as a basis for the network device to determine whether to successfully receive the third PDU set.
  • the fifth instruction information reference may be made to the description of the fifth instruction information in the third aspect, which will not be described again here.
  • the method further includes: before or when the third PDU set is cached in the cache, the terminal device performs header detection on the third PDU set generated by the application layer to determine the third PDU set The identifier and the identifier of at least one PDU set referenced by the third PDU set.
  • the terminal device encapsulates the identifier of the third PDU set and the identifier of at least one PDU set in the header of the protocol layer of the third PDU set.
  • the third PDU set generated by the application layer includes the identifier of the third PDU set and the identifier of at least one PDU set.
  • the first PDU or each PDU of the third PDU set includes the identifier of the third PDU set and the identifier of at least one PDU set.
  • the successful decoding of the third PDU set is predicated on the successful decoding of at least one PDU set.
  • the terminal device can learn the identity of a certain PDU set and the identity of another PDU set referenced by the PDU set through header detection, so that the terminal device can learn the reference relationship between different PDU sets.
  • a fifth aspect provides a terminal device.
  • the terminal device is used to execute the method provided by the first aspect and any one of its implementations, the fourth aspect and any of its implementations.
  • the terminal device includes a processor and a memory, and the memory is used to store a computer program; the processor is used to call and run the computer program from the memory, so that the terminal device executes the above-mentioned first aspect and any one of its implementations, Or the method provided by the fourth aspect and any one of its implementations.
  • a sixth aspect provides a network device.
  • the network device is used to execute the method provided in the second or third aspect above.
  • the network device includes a processor and a memory, and the memory is used to store a computer program; the processor is used to call and run the computer program from the memory, so that the network device executes the above second aspect and any one of its implementations or The method provided by the third aspect and any one of its implementations.
  • a communication device is provided.
  • the communication device is used to perform the method provided by the above-mentioned first aspect and any one of its implementations or the fourth aspect and any one of its implementations.
  • the communication device may include units and/or modules (such as a processing unit, a transceiver unit) for performing the method provided by the first aspect and any one of its implementations or the fourth aspect and any one of its implementations. .
  • the communication device is a terminal device.
  • the transceiver unit may be a transceiver, or an input/output interface.
  • the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the communication device may be a chip, a chip system or a circuit in a terminal device.
  • the transceiver unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit etc.
  • a communication device is provided.
  • the communication device is used to perform the method provided by the above-mentioned second aspect and any one of its implementations or the third aspect and any one of its implementations.
  • the communication device may include units and/or modules for executing the method provided by the second aspect and any one of its implementations or the third aspect and any of its implementations, such as a processing unit and a transceiver unit.
  • the communication device is a network device.
  • the transceiver unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the transceiver unit may be an input/output interface, interface circuit, output circuit or input circuit on the chip, chip system or circuit. , pins or related circuits, etc.; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • this application provides a processor for executing the methods provided in the above aspects.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium stores a computer program.
  • the communication device causes the communication device to execute the method of any one of the above-mentioned first to fourth aspects.
  • a computer program product containing instructions is provided.
  • the computer program product is run on a computer, the computer is caused to execute the method provided by any one of the above implementations of the first to fourth aspects.
  • a chip in a twelfth aspect, includes a processor and a communication interface.
  • the processor reads instructions stored in the memory through the communication interface and executes the method provided by any one of the above-mentioned implementations of the first to fourth aspects.
  • the chip also includes a memory, the memory stores computer programs or instructions, and the processor is used to execute the computer program or instructions stored on the memory.
  • the processor is used to execute the above.
  • a thirteenth aspect provides a communication system, including the terminal device of the fifth aspect and the network device of the sixth aspect.
  • Figure 1 is a schematic diagram of a communication system applicable to this application.
  • Figure 2 is a schematic diagram of the protocol layer structure between network equipment and terminal equipment.
  • Figure 3 is a schematic flow chart of a communication method provided by this application.
  • FIG. 4 are schematic diagrams of the terminal device provided by the embodiment of the present application to determine whether the second PDU set is successfully uploaded.
  • Figure 5 is a schematic flow chart of another communication method provided by this application.
  • Figure 6 is a schematic diagram of a communication device provided by this application.
  • Figure 7 is a schematic structural diagram of the terminal equipment of the present application.
  • FIG 8 is a schematic diagram of another communication device provided by this application.
  • Figure 9 is a schematic structural diagram of the network device of the present application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems.
  • fifth generation (5G) system or new radio (NR) long term evolution (LTE) system
  • LTE frequency division duplex (FDD) system LTE time division duplex Work (time division duplex, TDD), etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solutions of the embodiments of this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, and machine-to-machine (M2M) communication.
  • Type communication machine type communication, MTC
  • Internet of things Internet of things, IoT
  • Terminal equipment in the embodiments of this application may refer to access terminal, user unit, user station, mobile station, mobile station, relay station, remote station, remote terminal, mobile device, user terminal (user terminal), user equipment (user equipment, UE), terminal, wireless communication equipment, user agent or user device.
  • the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a device with wireless communications Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminals in future evolved public land mobile communications networks (PLMN) Equipment or terminal equipment in future Internet of Vehicles, etc., the embodiments of this application are not limited to this.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile communications networks
  • a wearable device may also be called a wearable smart device, which is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices.
  • wearable devices are portable devices that are worn directly on the body or are integrated into the user's clothing or accessories.
  • Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured devices that can achieve complete or partial functions without relying on smartphones.
  • it can also be a portable device that only focuses on a certain type of application function and needs to be used in conjunction with other devices such as smartphones.
  • smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-computer interconnection and object interconnection.
  • IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.
  • NB narrowband
  • the terminal device may also include a sensor, whose main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and sending electromagnetic waves to transmit uplink data to the network device.
  • the network device in the embodiment of the present application may be any communication device with wireless transceiver functions used to communicate with terminal devices.
  • the equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (Node B, NB), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point in the wireless fidelity (wireless fidelity, WIFI) system (transmission point, TP) or transmission and reception point (TRP), etc.
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • NB home base station
  • baseband unit baseBand unit, BBU
  • AP access point
  • wireless relay node wireless backhaul node
  • transmission point in the wireless fidelity (wireless fidelity, WIFI) system transmission point, TP) or transmission and reception point (TRP), etc.
  • Network equipment and terminal equipment can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, the scenarios in which network devices and terminal devices are located are not limited.
  • the terminal device or network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • This hardware layer includes hardware such as central processing unit (CPU), memory management unit (MMU) and memory (also called main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, for example, operating system, operating system, operating system, operating system or operating system, etc.
  • This application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • various aspects or features of the present application may be implemented as methods, apparatus, or articles of manufacture using standard programming and/or engineering techniques.
  • article of manufacture encompasses a computer program accessible from any computer-readable device, carrier or medium.
  • computer-readable media include but are not limited to: magnetic storage devices (such as hard disks, floppy disks or tapes, etc.), optical disks (such as compact discs (CD), digital versatile discs (DVD), etc.) , smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable storage medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • the communication system 100 may include at least one network device 101 and at least one terminal device 102 to 107 .
  • the terminal devices 102 to 107 can be mobile or fixed.
  • Network device 101 and one or more of terminal devices 102 to 107 may each communicate via wireless links.
  • Each network device can provide communication coverage for a specific geographical area and can communicate with end devices located within that coverage area.
  • terminal devices can communicate directly with each other.
  • D2D device to device
  • terminal devices can communicate directly with terminal devices.
  • D2D technology can be used to achieve direct communication between terminal devices.
  • D2D technology can be used to communicate directly between terminal devices 105 and 106, and between terminal devices 105 and 107.
  • Terminal device 106 and terminal device 107 may communicate with terminal device 105 individually or simultaneously.
  • the terminal devices 105 to 107 can also communicate with the network device 101 respectively.
  • the terminal devices 105 and 106 in the figure can directly communicate with the network device 101. It may also communicate with the network device 101 indirectly, for example, the terminal device 107 in FIG. 1 communicates with the network device 101 via the terminal device 105.
  • Each communication device can be configured with multiple antennas.
  • the configured plurality of antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. Therefore, communication devices in the communication system 100 can communicate through multi-antenna technology.
  • the interface between the network device and the terminal device may be a Uu interface (or air interface).
  • Uu interface or air interface
  • the names of these interfaces may remain unchanged or may be replaced by other names, which is not limited by this application.
  • communication between network equipment and terminal equipment follows a certain protocol layer structure.
  • Network layering is to send, forward, package or unpack data of network nodes (such as network equipment and terminal equipment), and control information. Work such as loading or unloading is completed by different hardware and software modules. This simplifies the complex issues of communication and network interconnection.
  • the protocol layer structure between the network device and the terminal device involved in the embodiment of the present application is briefly described with reference to FIG. 2 .
  • the network layers of network equipment and terminal equipment include: application layer, RRC layer, SDAP layer, PDCP layer, RLC layer, and MAC layer.
  • the main function of the application layer is to provide many services for application software, such as file servers, database services, email and other network software services;
  • the RRC layer implementation functions include establishing, maintaining and releasing RRC connections, allocating or Reconfigure the radio resources used for RRC connections;
  • one of the functions of the SDAP layer is to map between the Quality of Service flow and the data radio bear (DRB);
  • the PDCP layer is responsible for compressing the IP header and Decompress and maintain the PDCP layer sequence number, encryption and decryption, etc.;
  • the RLC layer mainly provides wireless link control functions, providing services such as segmentation, retransmission control, and on-demand transmission for the upper layer;
  • the functions of the MAC layer include logical channels and transmission channels Mapping between devices to select the appropriate transmission format for each transmission channel.
  • FIG. 1 is only a simplified schematic diagram for ease of understanding, and the communication system 100 may also include other network devices or other terminal devices (not shown in FIG. 1 ).
  • the communication system 100 may also include core network equipment.
  • the access network equipment provides wireless access connections for terminal equipment, and can send data to or receive data sent by the terminal equipment; on the other hand, the access network equipment is also connected to the core network equipment and can receive data from the terminal equipment. The data is forwarded to the core network, or data that needs to be sent to the terminal device is received from the core network.
  • Extended Reality eXtended Reality, one.
  • XR applications provide users with a virtual immersive world by providing audio and video signals. Among them, the transmission of video frames is divided into I-frame transmission and P-frames transmission.
  • I frame and P frame I frame can be called an intra-frame coded frame. It is an independent frame that carries all its own information and can be decoded independently without referring to other images.
  • the P frame can be called a predictive coding frame. When encoding continuous dynamic images, the P frame is predicted from the P frame or I frame before it. It compares the difference information with the P frame or I frame before it or Data, that is, inter-frame compression is performed taking into account the characteristics of motion.
  • Protocol Data Unit A specific data frame format, which refers to a hierarchical network structure. A PDU will be established at each layer of the transmission system. The PDU contains information from the upper layer and the current layer. With additional information about the entity, this PDU will be transmitted to the next lower layer.
  • Protocol Data Unit set A PDU set consists of one or more PDUs. It is a unit of information generated by the application layer. This unit of information can refer to a unit in the XR media service. A frame or a slice.
  • the application layer needs to receive all PDUs in a PDU set in order to use the information of one unit. In some other applications, the application layer only needs to receive a part of a PDU set to recover part or all of the unit information.
  • all PDUs within a PDU set are processed as a whole. For example, a frame within a group of pictures (GoP) can only be decoded normally after all its dependent frames have been received and decoded. If this dependency between PDU sets is not considered, the randomly lost data packets of 5GS will affect the normal decoding of subsequent transmission data packets, resulting in the transmission of invalid data packets and wireless waste.
  • GoP group of pictures
  • PDU set sequence number PS-SN
  • RPS-SN reference PDU set sequence number
  • the referenced PDU set can be called a reference PDU set, and the PDU set that refers to the reference PDU set is called a dependent PDU set.
  • New data indicator new data indicator, NDI field and number of hybrid automatic repeat request (HARQ) processes: 1 bit in the DCI (for example, DCI format 0_0, 0_1 or 0_2) used to schedule upstream data
  • the NDI field and the 4-bit HARQ process number are used to indicate whether the network device is scheduling retransmission of data or scheduling new transmission of data.
  • NDI combined with HARQ process number is used to indicate whether the uploaded data is newly transmitted or retransmitted. For the same HARQ process number, if the NDI indication value is the same as the previous scheduling, then this scheduling is a retransmission of the previous scheduling data. If the NDI indication value is the same as the previous scheduling, If the schedule is different (0 the previous time, 1 this time, or vice versa), then this schedule is a new transmission. After receiving the new NDI instruction transmission, the terminal device will use the untransmitted data to refresh the buffer of the associated HARQ process; if it receives the NDI instruction retransmission, it will cache the data in the buffer corresponding to the HARQ process and re-upload it.
  • Uplink scheduling The network device schedules the uplink data of the terminal device based on the SR and BSR signaling sent by the terminal device.
  • SR is physical layer signaling.
  • the terminal device uploads SR to the network device and can use a dedicated and periodic physical layer uplink control channel (PUCCH) channel.
  • PUCCH physical layer uplink control channel
  • the network device After receiving the SR signal sent by the terminal device, the network device knows that the terminal device has uplink data that needs to be transmitted, and can allocate uplink resources to the terminal device.
  • the network device cannot determine how much data the terminal device needs to transmit, nor how many uplink resources should be allocated to the terminal device. Therefore, the subsequent terminal device still needs to send a BSR signal to the network device to report how much data is cached in the buffer on the terminal device side in order to apply for uplink resources.
  • the network device After receiving the uplink scheduling application, the network device uses DCI (for example, DCI format 0_0, 0_1 or 0_2) to schedule uplink data.
  • DCI for example, DCI format 0_0, 0_1 or 0_2
  • the terminal device After receiving the scheduled DCI, the terminal device will upload data in the designated time-frequency resource block. After the network device receives the uploaded data, it does not feedback ACK ⁇ NACK signals to the terminal device, unlike the downlink transmission. If a certain data is not uploaded successfully, the network device decides whether to retransmit the data. The network device will directly send the DCI of the scheduling retransmission signal to the terminal device to schedule the data that needs to be retransmitted; if the unsuccessfully uploaded data does not need to be retransmitted, the network device will directly schedule the newly transmitted data and no longer schedule the unsuccessful data. upload data.
  • DCI for example, DCI format 0_0, 0_1 or 0_2
  • Unacknowledgement mode In the WCDMA system, the RLC layer is located above the MAC layer and is part of L2, providing segmentation and retransmission services for user and control data.
  • Each RLC entity is configured by RRC and has three modes according to the service type: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM).
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledged mode
  • non-confirmation mode the sending entity adds necessary control protocol overhead to the high-level PDU, and then transmits it but does not guarantee delivery to the peer entity, and does not use a retransmission protocol.
  • the receiving entity marks the received error data as an error and then submits it, or directly discards it and reports it to the higher level. Since the RLC PDU contains a sequence number, the integrity of the higher-level PDU can be detected.
  • for indicating may include direct indicating and indirect indicating.
  • indication information When describing certain indication information as indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.
  • the information indicated by the indication information is called information to be indicated, and during the specific implementation process, there are many ways to indicate the information to be indicated.
  • the information to be instructed can be sent together as a whole, or can be divided into multiple sub-information and sent separately, and the sending period and/or sending timing of these sub-information can be the same or different.
  • the specific sending method is not limited in this application.
  • the sending period and/or sending timing of these sub-information may be predefined, for example, according to a protocol, or may be configured by the transmitting device by sending configuration information to the receiving device.
  • the configuration information may include, for example but not limited to, one or a combination of at least two of radio resource control signaling, MAC layer signaling and physical layer signaling.
  • the radio resource control signaling includes, for example, RRC signaling; the MAC layer signaling, for example, includes a MAC control element (CE); and the physical layer signaling, for example, includes DCI.
  • the “save” involved in the embodiments of this application may refer to saving in one or more memories.
  • the one or more memories may be provided separately, or may be integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partially provided separately and partially integrated in the decoder, processor, or communication device.
  • the type of memory can be any form of storage medium, and this application is not limited thereto.
  • the "protocol” involved in the embodiments of this application may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.
  • control channel may include PDCCH, enhanced physical downlink control channel (EPDCCH) and other physical layer control channels.
  • PDCCH enhanced physical downlink control channel
  • EPDCCH enhanced physical downlink control channel
  • the embodiment of the present application takes the downlink control channel as the physical downlink control channel PDCCH as an example for explanation, but this does not limit the embodiment of the present application.
  • the downlink control channel may also be defined as other terms or concepts.
  • the technical solutions of the embodiments of this application are all applicable.
  • the downlink control channel and the PDCCH may be used interchangeably, and the PDCCH can be considered to be an example description of the uplink control channel.
  • DCI downlink control information
  • MAC-CE media access control control element
  • RRC radio resource control
  • the term "and/or" in this article is just an association relationship that describes related objects, indicating that there can be three relationships.
  • a and/or B can mean: A alone exists, and A and B exist simultaneously. , there are three situations of B alone.
  • the character "/" in this article generally indicates that the related objects are an "or" relationship.
  • the network device When the network device schedules uplink data, it will not immediately feedback ACK/NACK signals to the terminal device. The terminal device cannot immediately confirm whether the currently uploaded data is successfully uploaded. What the terminal device can confirm through the HARQ process is that the network device no longer schedules the previously uploaded data. This may be because the network device successfully received the data, or it may be because the maximum number of retransmissions has been reached and the network device no longer schedules retransmissions. Therefore, the terminal device cannot confirm whether the uploaded data is successfully uploaded.
  • this application provides a communication method to determine whether the uplink data is uploaded successfully and avoid the waste of uplink resources caused by scheduling invalid frames.
  • the communication method provided by the embodiment of the present application can be applied to a system that communicates through multi-antenna technology, such as the communication system 100 shown in FIG. 1 .
  • the communication system may include at least one network device and at least one terminal device. Network equipment and terminal equipment can communicate through multi-antenna technology.
  • the embodiments shown below do not specifically limit the specific structure of the execution body of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run according to the present application. It is sufficient to communicate using the method provided in the application embodiment.
  • the execution subject of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call a program and execute the program.
  • FIG. 3 is a schematic flow chart of a communication method provided by this application. Includes the following steps:
  • the terminal device sends the first instruction information to the network device, or the network device receives the first instruction information from the terminal device.
  • the first indication information is used to indicate the second PDU set that the first PDU set refers to (can also be called dependent on).
  • the first PDU set refers to (can also be called dependent on) the second PDU set, which can be understood as the successful decoding of the first PDU set is predicated on the successful decoding of the second PDU set.
  • the first PDU set can be decoded successfully only if the second PDU set is successfully decoded (or in other words, the second PDU set is successfully uploaded).
  • the above-mentioned first PDU set is a PDU set to be sent by the terminal device, such as cached in the cache of the terminal device (e.g., cached in the cache of the RLC layer of the terminal device and/or the cache of the PDCP layer of the terminal device) PDU set).
  • the terminal device such as cached in the cache of the terminal device (e.g., cached in the cache of the RLC layer of the terminal device and/or the cache of the PDCP layer of the terminal device) PDU set).
  • the terminal device is triggered to send the first indication information to the network device.
  • the first indication information can indicate the second PDU set.
  • the first indication information includes information that can be used to indicate the second PDU set.
  • the first indication information includes the identification of the second PDU set (for example, the sequence number of the second PDU set).
  • the terminal device can learn the identity of the second PDU set through the following process:
  • the protocol layer of the terminal device can learn the first PDU set through header detection (such as deep packet inspection, packet filtering, etc.) The identifier and the identifier of the second PDU set referenced by the first PDU set.
  • the application layer of the terminal device packages the data of the first PDU set
  • the data packet header of the PDU belonging to the first PDU set (for example, it can be in the data packet header of each PDU belonging to the first PDU set, or it can Only when the packet header of the first PDU of the first PDU set carries the identifier of the first PDU set and the identifier of at least one PDU set referenced by the first PDU set, and the application layer of the terminal device generates the first PDU set, enter At the access stratum (AS) layer, header detection is performed at a certain protocol layer of the AS layer (such as the SDAP layer or PDCP layer or NAS layer or RRC layer) to obtain the identity of the first PDU set and the first PDU set reference.
  • the identifier of at least one PDU set, and the above-mentioned second PDU set is one of the at least one PDU set.
  • the above-mentioned second PDU set is the PDU set that has been sent by the terminal device.
  • the PDU set referenced by the first PDU set has not been sent or is being sent (for example, cached in the RLC layer cache of the terminal device or PDCP of the terminal device)
  • the PDU set referenced by the first PDU set in the cache of the layer does not need to be indicated by the first indication information.
  • the PDU set referenced by the first PDU set includes PDU set #1, PDU set #2 and PDU set #3. If PDU set#1 is a PDU set that has been sent by the terminal device, PDU set#2 and PDU set#3 are PDU sets that have not been sent by the terminal device, or PDU set#2 and PDU set#3 are currently being sent by the terminal device. PDU set, then the first indication information only needs to indicate PDU set#1, and there is no need to indicate PDU set#2 and PDU set#3. The reason is: the purpose of sending the first indication information is for the network device to determine whether the sent PDU set#1 has been successfully received.
  • the terminal device knows that PDU set#2 and PDU set#3 have not been successfully sent, then the terminal device has Knowing that the network device has not successfully received PDU set#2 and PDU set#3, there is no need to indicate PDU set#2 and PDU set#3 through the first indication information, in order for the network device to determine whether it has successfully received PDU set#2 and PDU set#3.
  • the sent PDU set referenced by the first PDU set may also include other PDU sets except the second PDU set.
  • the first indication information may also be used to indicate the first PDU set.
  • the PDU set referenced by the first PDU set is the second PDU set. That is to say, no matter how many PDU sets the first PDU set refers to that have been sent, Each one can be called the second PDU set.
  • the terminal device can report information indicating the sent PDU set referenced by multiple PDU sets at one time. That is to say, the terminal device can indicate the PDU set referenced by multiple PDU sets in the cache at one time through one indication message.
  • the above-mentioned first PDU set includes the first PDU set #1, the first PDU set #2 and the first PDU set #3, and the second PDU set #1 and the second PDU set #1 referenced by the first PDU set #1 set#2 has been sent, the second PDU set#3 and the second PDU set#4 referenced by the first PDU set#2 have been sent, the second PDU set#5 and the second PDU referenced by the first PDU set#3 set#6 has been sent.
  • the first indication information may be used to indicate the second PDU set #1, the second PDU set #2, the second PDU set #3, the second PDU set #4, the second PDU set #5 and the second PDU set #6.
  • the first indication information may use the currently existing signaling format.
  • the first indication information is MAC CE
  • MAC CE includes a logical channel identifier LCID and an identifier of the second PDU set, where the LCID indicates the logical channel corresponding to the MAC CE, and the logical channel is used to transmit the PDU set referenced by the first PDU set.
  • logo It can be understood that the LCID is used to indicate the type of MAC CE to indicate the MAC CE of the PDU set referenced by the first PDU set.
  • the identifier of the second PDU set is used to identify the second PDU set.
  • MAC CE can be called dependency MAC CE.
  • the signaling format of the Dependency MAC CE is as shown in Table 1 below:
  • the identifier of the second PDU set #1 can be the sequence number of the second PDU set #1, or other information that can identify the second PDU set #1; similarly, the identifier of the second PDU set #2 can be the second PDU set #1. The sequence number of PDU set#2, or other information that can identify the second PDU set#2.
  • this embodiment mainly considers the situation of the second PDU set that the first PDU set refers to.
  • PDU set belonging to an independent frame for example, a certain PDU set does not refer to other PDU sets, it can be called Standalone PDU set
  • PDU set without reference That is, the PDU set without reference needs to be reported through the first indication information.
  • the first indication information may not be sent, or the first indication information may be sent, and the field indicating the referenced PDU set in the first indication information is set to 0.
  • the field of the dependent PDU set SN included in the Dependency MAC C is set to 0.
  • the terminal device when the first indication information is MAC CE, after the terminal device triggers MAC CE, if the MAC layer of the terminal device has uplink resources, it can communicate with the buffer status report (BSR) MAC CE is sent to the network device together.
  • BSR buffer status report
  • the terminal device may request to allocate uplink resources for transmitting the first indication information.
  • the terminal device sends the first indication information to the network device.
  • the network device can compare the identifier of the second PDU set with the identifier of at least one locally saved PDU set, and determine whether the first PDU set needs to be scheduled according to the comparison result. PDU set.
  • the method flow shown in Figure 3 also includes:
  • S320 The network device determines whether to schedule the first PDU set.
  • the network device determines not to schedule the first PDU set.
  • the PDU set successfully received by the network device includes PDU set #1 and PDU set #3, and the network device locally stores the identifiers "#1" and "#3" of PDU set #1 and PDU set #3.
  • the network device receives the first indication information and learns that the identifier of the second PDU set is "#2" and determines that the network device does not locally store the identifier "#2"
  • the network device determines that the second PDU set has not been successfully received.
  • the successful decoding of the first PDU set is premised on the successful decoding of the second PDU set. If the network device determines that the second PDU set has not been successfully received, and through information indicating the function of the first indication information (such as the first indication information (LCID in ) determines that the first indication information indicates the second PDU set referenced by the first PDU set, then the network device determines that the second PDU set has not been successfully received, and the first PDU set does not need to be scheduled. Therefore, in this implementation manner, the network device determines not to schedule the first PDU set.
  • information indicating the function of the first indication information such as the first indication information (LCID in ) determines that the first indication information indicates the second PDU set referenced by the first PDU set
  • the network device determines that the second PDU set is successfully received, the network device determines to schedule the first PDU set.
  • the PDU set successfully received by the network device includes PDU set #2 and PDU set #3, and the network device locally saves the identifiers "#2" and "#3" of PDU set #1 and PDU set #3.
  • the device learns that the identifier of the second PDU set is "#2" and determines that the network device locally stores the identifier "#2". Then the network device determines that the second PDU set has been successfully received, and the network device determines the scheduling. The first PDU set.
  • the network device can send scheduling information (such as DCI signaling) to the terminal device through the PDCCH channel.
  • scheduling information such as DCI signaling
  • step S320 the network device determines whether it needs to schedule the first PDU set by determining whether the second PDU set is successfully received.
  • the method flow shown in Figure 3 also includes:
  • the terminal device sends the second PDU set to the network device, or the network device receives the second PDU set from the terminal device.
  • the second PDU set includes third indication information
  • the third indication information is provided to the network device so that the network device determines whether to successfully receive the second PDU set based on the third indication information.
  • the third indication information may be called integrity indication information.
  • the third indication information includes at least one of the following: the identification of the first and last PDU included in the second PDU set; or, the total number of PDUs included in the second PDU set; or, the second PDU set is successfully decoded.
  • the function of the third indication information can be implemented in different ways.
  • the second PDU set includes the third indication information for integrity detection.
  • the following is a brief description of how the terminal device generates the second PDU set including the third indication information:
  • the data packet header of the PDU belonging to the second PDU set (for example, it can be in the data packet header of each PDU belonging to the second PDU set, or it can be only in the data packet header of the second PDU set).
  • the packet header of the first PDU of the second PDU set carries the following data:
  • the application layer of the terminal device generates the second PDU set, and the first PDU of the second PDU set or each PDU includes the identifier of the second PDU set and the identifier of at least one PDU set referenced by the second PDU set.
  • the application layer of the terminal device generates other PDU sets in a manner similar to the way of generating the second PDU set (or the first PDU set). If a certain PDU set refers to multiple PDU sets, the terminal device The application layer should carry the identifiers of all PDU sets referenced by the PDU set in the packet header of the PDU set (for example, the first PDU of the PDU set, or each PDU of the PDU set). If a PDU set is an independent PDU set, the terminal device can set the field in the packet header of the independent PDU set that carries the identifier of the PDU set referenced by the independent PDU set to zero.
  • the terminal device application layer After the terminal device application layer generates the second PDU set, it enters the AS layer, performs header detection on a certain protocol layer of the AS layer (such as the SDAP layer or PDCP layer), and obtains the identifier of the second PDU set and the second PDU set The identifier of the referenced second PDU set, and reprint these two types of identifiers into the header of the SDAP layer or PDCP layer of the second PDU set.
  • a certain protocol layer of the AS layer such as the SDAP layer or PDCP layer
  • the terminal device in order to facilitate the network device to perform PDU set integrity detection, can carry the third indication information for integrity detection in the second PDU set.
  • the terminal device marks the first PDU and the last PDU of the second PDU set, indicating respectively as the first and last PDU of the second PDU set.
  • the terminal device adds the identification of the PDU in the second PDU set to each PDU belonging to the second PDU set. For example, add the PDU sequence number of the PDU in the second PDU set to each PDU.
  • the third indication information can be understood as including: the identification information of the first and last PDU of the second PDU set, and the PDU sequence number of the PDU contained in the second PDU set in the second PDU set.
  • the terminal device provides the total number of PDUs contained in the second PDU set, and the identification that the PDUs contained in the second PDU set belong to the second PDU set.
  • the third indication information can be understood as including: the total number of PDUs contained in the second PDU set, and the identification that the PDUs contained in the second PDU set belong to the second PDU set.
  • the terminal device provides the minimum number of PDUs required to successfully transmit the second PDU set, and an identification that the PDUs contained in the second PDU set belong to the second PDU set.
  • the third indication information can be understood as including: the number of PDUs required for successful transmission of the second PDU set, and an identification that the PDUs contained in the second PDU set belong to the second PDU set.
  • the above only takes the generation of the second PDU set including the third indication information as an example to illustrate how the terminal device generates the PDU set including the integrity detection information in this embodiment, and does not constitute any limitation on the protection scope of the present application.
  • the process of the terminal device generating the PDU set can refer to the process of the terminal device generating the second PDU set, which will not be described again here.
  • the network device After receiving the PDU included in the second PDU set, the network device can determine whether to completely receive the second PDU set based on the third indication information in the second PDU set, and determine whether to save the identifier of the second PDU set based on the judgment result.
  • the method flow shown in Figure 3 also includes:
  • S312 The network device determines whether to save the identifier of the second PDU set.
  • the network device after the network device receives the data sent by the terminal device, it needs to detect the integrity of the PDU set on the received data and record the SN of the complete received PDU set.
  • the network device performs integrity testing on the second PDU set as an example. For other PDU sets, the process of the network device performing integrity testing is similar and will not be repeated.
  • the process of the network device performing integrity check on the second PDU set is as follows:
  • the identifier of the detected second PDU set and the identifier of the PDU set referenced by the second PDU set are reprinted to the third
  • the second PDU sets the header of the data packet related to the protocol layer.
  • the network device receives the data from the terminal device, it also performs the integrity check of the PDU set at the corresponding protocol layer.
  • the network device performs integrity testing on the second PDU set at the SDAP layer.
  • the network device performs integrity testing on the second PDU set at the PDCP layer.
  • the second PDU set may be checked at the PDCP layer. After the set is reordered, the integrity of the second PDU set is checked when submitting the data packet for the second PDU set to the upper layer. The detection is used to determine whether all PDUs included in the second PDU set are successfully received, or the detection is used to determine whether the number of PDUs successfully received in the second PDU set exceeds the first threshold.
  • the network device determines the first and last PDU belonging to the second PDU set at the aforementioned protocol layer (such as SDAP or PDCP, etc.), and Determine whether the second PDU set has been completely received through the continuity of the PDU identifier in the second PDU set.
  • the protocol layer such as SDAP or PDCP, etc.
  • the third indication information indicates that the first and last PDUs of the second PDU set are PDU#1 and PDU#/6 respectively, and the identifiers of the PDUs in the second PDU set are PDU#1, PDU#2, and PDU #3, PDU#4, PDU#5, PDU#6.
  • the network device successfully receives PDU#1 and PDU#/6, and the identifiers of the received PDUs in the second PDU set are consistent, it is determined that the second PDU set has been completely received, otherwise it is determined that the second PDU set has not been completely received. .
  • the network device confirms whether the second PDU set has been completely received by determining the total number of data packets belonging to the second PDU set and the identification of the PDU belonging to the second PDU set.
  • the third indication information indicates that the identities of the PDUs in the second PDU set are PDU#1, PDU#2, PDU#3, PDU#4, PDU#5, and PDU#6, and the total number of PDUs included in the second PDU set. is 6.
  • the network device receives 6 PDUs, and the PDU identifiers are PDU#1, PDU#2, PDU#3, PDU#4, PDU#5, and PDU#6, it is determined that the second PDU set is completely received, otherwise It is determined that the second PDU set has not been completely received.
  • the network device determines whether the total number of successfully received data packets belonging to the second PDU set reaches a threshold value to determine whether the second PDU set has been completely received.
  • the third indication information indicates that the total number of successfully received data packets belonging to the second PDU set is 3, and the identifiers of the PDUs in the second PDU set are PDU#1, PDU#2, PDU#3, PDU#4, and PDU# 5.
  • PDU#6 When the network device receives 3 or more PDUs, and the identifiers of at least 3 PDUs are 3 of PDU#1, PDU#2, PDU#3, PDU#4, PDU#5, and PDU#6 , determine that the second PDU set is completely received, otherwise determine that the second PDU set is not completely received.
  • the network device determines that the second PDU set has been completely received, the network device saves the identifier of the second PDU set. Otherwise, the network device does not save the identifier of the second PDU set.
  • the identifier of the second PDU set is "#2".
  • the network device determines that the second PDU set has been completely received, the network device saves "#2"; otherwise, the network device does not save "#2".
  • the network device can automatically clear the identification of the PDU set saved before the time T or before the identification of N PDU sets.
  • the T value and N value are set so that the identifier of the cleared PDU set will no longer refer to the identifier of the PDU set referenced by the subsequently transmitted PDU set.
  • the network device determines whether the second PDU set referenced by the first PDU set in step S320 has been successfully uploaded through the saved identification of the PDU set. If the identifier of the second PDU set reported in the first indication information is one of the identifiers of the PDU set saved by the network device, it indicates that the corresponding second PDU set was successfully uploaded; otherwise, it indicates that the second PDU set was not successfully uploaded.
  • the terminal device can determine whether the second PDU set is successfully uploaded based on at least one of the timeout condition of the timer of the terminal device and the feedback condition of the network device to the first indication information.
  • the method flow shown in Figure 3 also includes:
  • S330 The terminal device determines whether the second PDU set is successfully uploaded.
  • the terminal device determines whether the second PDU set is successfully uploaded based on the timeout of the local first timer.
  • the first timer is a discard timer set by the terminal device for the first PDU set.
  • the starting time of the first timer is the moment when the PDCP entity of the terminal device receives the first PDU set, and in the In an implementation manner, the timing duration of the first timer is less than the frame arrival period.
  • the frame arrival period in this embodiment indicates the interval between two adjacent frames arriving at the buffer of the terminal device.
  • the PDCP entity of the terminal device can be understood as the transmission entity (such as transmitting PDCP entity) of the PDCP layer of the terminal device.
  • the starting time of the first timer is the time when the PDCP entity of the terminal device receives the first PDU set, which can also be understood as the PDCP layer of the terminal device passing the first PDU set to the RLC layer of the terminal device. moment, it can also be understood as the first The time at which a PDU set is cached in the cache.
  • the timeout situation of the existing timer is multiplexed and the first timer is judged. 2. Whether the PDU set is successfully uploaded.
  • the network device can learn information related to the first timer and the periodic frame arrival period. It can be understood that in this embodiment, the network device can learn that the first timer expiration time (or termination time) is earlier than the second frame arriving at the terminal. At the time of the device's cache, the second frame is the next frame to the first frame, and the first frame includes the first PDU set.
  • the first timer is configured by the network device, and the network device can determine the information related to the first timer (such as timing duration, starting time, etc.); the information related to the periodic frame arrival period is reported to the network device by the terminal device. of.
  • the terminal device determines that the second PDU set has not been successfully uploaded based on the timeout of the local first timer, including: after the first timer expires or when the first timer expires, the terminal device does not After receiving the scheduling information of the network device, the terminal device determines that the second PDU set was not successfully uploaded; or,
  • the terminal device determines that the second PDU set is successfully uploaded based on the timeout of the local first timer, including: before the first timer expires, the terminal device receives the scheduling information of the network device.
  • the terminal device uploads the first PDU set according to the scheduling information. It should be understood that the scheduling information of the network device may schedule some PDUs in the first PDU set. After the first timer expires or when the first timer expires, if part of the PDU in the first PDU set is still cached in the cache of the terminal device, the terminal device discards the part of the PDU that has not been uploaded.
  • the PDU set to be sent by the terminal device is PDU set #1 (that is, the first PDU set mentioned above).
  • This PDU set #1 is a PDU set included in frame #1.
  • PDU set#1 enters the buffer of the RLC layer of the terminal device.
  • the terminal device starts the first timer (for example, starts the discard timer (discard Timer)). The first timer is used to indicate that in the first If the DCI for scheduled PDU set#1 is not received before the timer expires, the PDU set#1 is discarded.
  • the terminal device before the terminal device submits PDU set #1 to the MAC layer for packaging, it triggers the reporting of Dependency MAC CE (for example, reporting the first indication information at time t2 after time t1).
  • the Dependency MAC CE indicates that PDU set #1 depends on
  • the PDU set #0 (that is, the second PDU set mentioned above) is a PDU set that has been reported.
  • the PDU set #0 is a PDU set included in frame #0.
  • the network device determines that PDU set #0 was not successfully uploaded (for example, the network device determines that the PDU set in frame #0 was not successfully uploaded), then the network device determines not to schedule PDU set #1 in the buffer of the terminal device, but the network device does not Display notification that the terminal device PDU set#0 has not been successfully received.
  • the terminal device has not received the scheduling information of the network device until the first timer expires.
  • the default PDU set#0 has not been successfully received. Clear the PDU set in the buffer. #1.
  • the network device determines that PDU set #0 is successfully uploaded (for example, the network device determines that the PDU set in frame #0 has been successfully uploaded), then the network device determines to schedule PDU set #1 in the buffer of the terminal device, and the network device issues the schedule Information (e.g., DCI) schedules PDU set#1. If after the first timer expires, some PDUs of PDU set#1 are still cached in the terminal device's cache, clear some of the PDUs in the buffer.
  • schedule Information e.g., DCI
  • the timing length of the first timer is less than or equal to the frame arrival period, that is to say, the PDU set included in the next frame enters the cache of the RLC/PDCP layer of the terminal device (such as (a) in Figure 4 The first timer expires before the t3 time shown).
  • the network device determines that PDU set#0 has not been successfully uploaded, the network device does not need to display a notification to the terminal device that PDU set#0 has not been successfully received.
  • the terminal device can determine the timeout of the timer of the terminal device (for example, the When a certain timer times out and the timing length of the first timer is less than the frame arrival period, it is determined that PDU set#0 has not been successfully received, thus determining that PDU set#1 does not need to be uploaded. In order to save local cache space, the PDU set#1 is discarded.
  • the terminal device determines whether the second PDU set is successfully uploaded based on the timeout of the local second timer.
  • the second timer is a timer started when the terminal device sends the first indication information
  • the starting time of the second timer is the time when the terminal device sends the first indication information (or in other words, the terminal device finishes sending the first indication information). a time of indication information).
  • the expiration time of the second timer is before the second frame reaches the buffer of the terminal device.
  • the second frame is the next frame of the first frame, and the first frame includes the first PDU set.
  • the terminal device determines that the second PDU set has not been successfully uploaded based on the timeout of the local second timer, including: before the second timer times out (or during the running period of the second timer), the terminal device The scheduling information of the network device is not received, and the terminal device determines that the second PDU set was not successfully uploaded; or,
  • the terminal device determines that the second PDU set is successfully uploaded based on the timeout of the local second timer, including: before the second timer times out (or during the running period of the second timer), the terminal device receives the scheduling information of the network device , the terminal device determines that the second PDU set is successfully uploaded.
  • the PDU set to be sent by the terminal device is PDU set#1.
  • This PDU set#1 is a PDU set included in frame #1.
  • PDU set#1 enters the terminal device.
  • RLC layer cache buffer
  • the terminal device starts the first timer (for example, starts the discard timer (discard Timer)). The first timer is used to indicate if no reception is received before the first timer expires. Schedule the DCI of PDU set#1 and discard the PDU set#1.
  • the terminal device before submitting PDU set #1 to the MAC layer packet, the terminal device triggers reporting of Dependency MAC CE (for example, reporting the first indication information at time t2 after time t1), and starts the second time at the time of reporting Dependency MAC CE.
  • Two timers such as dropping packet timer (droppingPacketTimer)
  • the Dependency MAC CE indicates the PDU set #0 on which PDU set #1 depends.
  • the PDU set #0 is a PDU set that has been reported, and the PDU set #0 is a PDU set included in frame #0.
  • the droppingPacketTimer will be terminated. For example, if the network device determines that PDU set#0 is successfully uploaded, PDU set#1 can be scheduled through DCI, and the terminal device determines that PDU set#0 is successfully uploaded and terminates the droppingPacketTimer.
  • the terminal device If the terminal device receives the DCI scheduled for Dependency MAC CE retransmission sent by the network device while the droppingPacketTimer is running, the terminal device restarts the droppingPacketTimer after resending the Dependency MAC CE. For example, if the network device fails to successfully receive the Dependency MAC CE, it can instruct the terminal device to retransmit the Dependency MAC CE.
  • the processing of the retransmission of the Dependency MAC CE is similar to the above-mentioned initial transmission of the Dependency MAC CE and will not be described again.
  • the terminal device determines that PDU set #0 has not been successfully uploaded, and the network The device does not schedule PDU set#1 in the buffer, and the terminal device can clear PDU set#1 in the buffer.
  • the timing duration of the first timer is longer than the frame arrival period, that is to say, the PDU set included in the next frame enters the cache of the RLC/PDCP layer of the terminal device (for example, as shown in (b) of Figure 4 After time t3), the first timer expires.
  • the terminal device does not send a scheduling request (SR) and first indication information (such as Dependency MAC CE for the new PDU set) about the new PDU set.
  • SR scheduling request
  • first indication information such as Dependency MAC CE for the new PDU set
  • the terminal device determines whether the second PDU set is successfully uploaded based on the feedback of the first indication information from the network device.
  • the feedback situation of the network device for the first indication information may be whether the network device sends the second indication information for the first indication information, indicating that the second PDU set has not been successfully uploaded.
  • the terminal device determines whether the second PDU set is successfully uploaded based on the network device's feedback on the first indication information, including: the terminal device receives the second indication information from the network device, and the second indication information is used to indicate The second PDU set was not successfully uploaded.
  • the second indication information indicates that the second PDU set has not been successfully uploaded, including: the second indication information indicates that some or all of the PDUs included in the second PDU set have not been successfully uploaded; or, the second indication information indicates that the second PDU set has not been successfully uploaded; The number of successfully uploaded PDUs is less than the first threshold.
  • the second indication information indicates that the second PDU set is not successfully uploaded, and does not constitute any limitation on the protection scope of this application.
  • Other ways that can be used to indicate that the second PDU set is not successfully uploaded are also available. It is within the protection scope of this application and will not be described again here.
  • the timing duration of the first timer is longer than the frame arrival period, in order to prevent the UE from waiting until the discard Timer of frame #1 expires, and then discarding the PDU set #1 of frame #1, it will cause When scheduling the PDU set of frame #2, the PDU set #1 of frame #1 must be scheduled first, resulting in a waste of resources.
  • frame #2 has no dependency on frame #1.
  • the network device receives the Dependency MAC CE for the PDU set included in frame #2. Afterwards, the PDU set included in frame #2 can be scheduled.
  • the network device schedules the PDU set included in frame #2, if the UE's cache also caches PDU set #1 of frame #1, the terminal device will send the PDU through the uplink resource of the PDU set included in the transmission frame #2. set#1, causing a waste of resources. Therefore, in this implementation mode, the network device needs to send the second instruction information to instruct the terminal device to discard PDU set #1 of frame #1.
  • the network device detects that some of the dependent PDU sets reported by the Dependency MAC CE have been successfully uploaded and the other part has not been successfully uploaded, and the network device issues a second instruction message to indicate to the terminal device that the PDU set has not been successfully uploaded.
  • the terminal device network device determines that the second PDU set has not been successfully uploaded in response to the feedback of the first indication information in detail with reference to (d) in Figure 4.
  • the PDU set to be sent by the terminal device is PDU set#1.
  • This PDU set#1 is a PDU set included in frame #1.
  • PDU set#1 enters the terminal device.
  • the terminal device starts the first timer (for example, starts the discard timer (discard Timer)).
  • the first timer is used to indicate if no reception is received before the first timer expires. Schedule the DCI of PDU set#1 and discard the PDU set#1.
  • the terminal device before submitting PDU set #1 to the MAC layer packet, the terminal device triggers the reporting of Dependency MAC CE (for example, reporting the first indication information at time t2 after time t1).
  • the Dependency MAC CE indicates PDU set #0 that PDU set #1 depends on.
  • This PDU set #0 is a PDU set that has been reported.
  • This PDU set #0 is a PDU set included in frame #0.
  • the network device determines that PDU set #0 is not successfully uploaded (for example, the PDU set in frame #0 is not successfully uploaded), then the network device determines not to schedule PDU set #1 in the buffer of the terminal device, and the network device determines the first timing The timing duration of the controller is longer than the frame arrival period, that is to say, after the PDU set included in the next frame enters the cache of the RLC/PDCP layer of the terminal device (for example, the t3 moment shown in (d) in Figure 4), the first timing The device has just expired.
  • the network device determines not to schedule PDU set #1, and notifies the terminal device to discard PDU set #1 in the buffer through the second indication information (for example, the second indication information is sent at t5 as shown in (d) of Figure 4).
  • the terminal device before submitting PDU set#1 to the MAC layer packet, the terminal device triggers reporting of Dependency MAC CE (for example, reporting the first indication information at time t2 after time t1).
  • Dependency MAC CE indicates that PDU set#1 depends on PDU set#0 and PDU set#0_1, DU set#0 and PDU set#0_1 are the reported PDU set, and the PDU set#0 and PDU set#0_1 are frame #0 PDU set included in .
  • the network device determines that PDU set #0 was not successfully uploaded (e.g., the PDU set in frame #0 was not successfully uploaded) and PDU set #0_1 was successfully uploaded, and the network device passes the second indication information (e.g., (d in Figure 4 The second indication information is sent at t5 as shown in ) to notify the terminal device that PDU set#0 has not been successfully uploaded.
  • the terminal device determines that PDU set#0 has not been successfully uploaded, and at the same time determines that PDU set#1 Depending on PDU set#0, PDU set#1 will be deleted from the buffer.
  • the example shown in (d) of Figure 4 is similar to the example shown in (a) of Figure 4, except that frame #2 has no dependency on frame #1 and the network device can schedule frame #2 PDU set. If the UE waits until the discardTimer of frame #1 expires and then discards the PDU set #1 of frame #1, then when scheduling the PDU set of frame #2, the PDU set of frame #1 will be scheduled first, resulting in a waste of resources. Therefore, the network device in the example shown in (d) of Figure 4 needs to additionally issue second instruction information to instruct the UE to discard PDU set #1 of frame #1.
  • the second indication information can be MAC CE, PDCP report or SDAP report, and the format and protocol layer of the second indication information are not limited.
  • the uplink data is a PDU set as an example for explanation, and the embodiment of this application is also applicable to other uplink data with dependencies.
  • the terminal device may also notify the network device through the first indication information that the first uplink data depends on the second uplink data before sending the first uplink data.
  • Uplink data when it is determined that the second uplink data is not uploaded successfully, there is no need to schedule the first uplink data.
  • the first PDU set in the above embodiment can be replaced with the general description "first uplink data”
  • the second PDU set set can be replaced by the general description "second upstream data”
  • the dependence between upstream data can be understood as a strong correlation between the first upstream data and the second upstream data. If the second upstream data is not uploaded successfully, even if the second upstream data is not uploaded successfully, It is meaningless once the uplink data is uploaded successfully.
  • the terminal device reports indication information indicating that the first PDU set to be sent refers to the second PDU set that has been sent, and after sending the first indication information, according to the started timer Determine the second PDU set based on at least one of a timeout situation (such as timing duration, whether it has timed out, etc.) and a feedback situation of the network device to the received first indication information (such as sending information in response to the first indication information). Whether the upload was successful. That is to say, in this technical solution, the terminal device can learn whether the second PDU set is successfully uploaded.
  • a timeout situation such as timing duration, whether it has timed out, etc.
  • the terminal device can determine the processing of the first PDU set based on whether the second PDU set is successfully uploaded. For example, if the second PDU set is not successfully uploaded, the terminal device determines that the first PDU set There is no need to upload, because the successful decoding of the first PDU set is predicated on the successful decoding of the second PDU set. If the second PDU set is not successfully uploaded, even if the first PDU set is uploaded, it cannot be decoded correctly. The terminal device can Discard the first PDU set.
  • This application also provides a communication method.
  • the network device sends fourth indication information to indicate whether a certain PDU is successfully received, so that the terminal device can determine whether the uplink data is successfully uploaded.
  • This communication method will be introduced in detail below in conjunction with Figure 5.
  • FIG. 5 is a schematic flow chart of another communication method provided by this application. Includes the following steps:
  • S510 The network device determines that the first condition is met.
  • S520 The network device sends fourth instruction information to the terminal device, or the terminal device receives the fourth instruction information from the network device.
  • the fourth indication information is used to indicate the PDU successfully received by the network device and/or the PDU received unsuccessfully.
  • the first condition includes at least one of the following:
  • the fourth indication information is information sent periodically, and at the moment when the fourth indication information is sent, the network device determines whether the third PDU set is successfully received, or the network device receives trigger information from the terminal device, where the trigger information is used Trigger the network device to determine fourth indication information.
  • the network device determines whether it successfully receives the third PDU set including: the network device determines whether it successfully receives all PDUs included in the third PDU set, and/or the network device successfully receives the PDU data of the third PDU set. Whether the first threshold is exceeded, where the first threshold is predefined.
  • the fourth indication information may be called PDCP status report.
  • the PDCP status report is triggered, it is submitted to the RLC and/or MAC layer of the network device and transmitted to the terminal device.
  • the network device when the first condition is that the fourth indication information is information sent periodically and the time for sending the fourth indication information is reached, the network device periodically sends the fourth indication information.
  • the network device detects uplink PDUs, records successfully received PDUs and unsuccessfully received PDUs, and periodically notifies the terminal device of successfully received PDUs and/or unsuccessfully received PDUs through the fourth indication information.
  • the period size of the periodic sending of the fourth indication information is preset (for example, the fourth indication information is sent every 10 minutes, and the starting time of the periodic sending may be the time when the first PDU is received).
  • the network device when the first condition is that the network device receives trigger information from the terminal device, the network device receives the trigger information from the terminal device, and the trigger information is used to indicate that the network device has successfully issued the instruction.
  • the fourth indication information of the received PDU and/or the unsuccessfully received PDU is used to indicate that the network device has successfully issued the instruction.
  • the network device receives the trigger information from the terminal device, determines the successfully received PDUs and the unsuccessfully received PDUs before receiving the trigger information, and notifies the terminal device of the successfully received PDUs and/or unsuccessfully received PDUs through the fourth indication information. Successfully received PDU.
  • the network device when the first condition is that the network device determines whether the third PDU set is successfully received, the network device receives the third PDU set from the terminal device, and the third PDU set includes fifth indication information. , the fifth indication information is used by the network device to determine whether the third PDU set is successfully received.
  • the fifth indication information may be called integrity indication information.
  • the network device determines whether the third PDU set is successfully received according to the fifth indication information. For example, the network device determines whether all PDUs included in the third PDU set are successfully received according to the fifth instruction information, or, for example, the network device determines whether the number of PDUs of the third PDU set successfully received exceeds the number of the third PDU set according to the fifth instruction information. a threshold.
  • the fifth indication information includes at least one of the following: the identification of the first and last PDU included in the third PDU set; or, the total number of PDUs included in the third PDU set; or, the success required for successful decoding of the third PDU set The number of transmitted PDUs; or, the ratio of the number of successfully transmitted PDUs required for successful decoding of the third PDU set to the total number of PDUs included in the third PDU set; or, the PDUs contained in the third PDU set belong to the third PDU set The identifier; or, the sequence number of the PDU contained in the third PDU set in the third PDU set.
  • the terminal device may carry fifth indication information for integrity detection in the third PDU set.
  • the process of the terminal device generating the third PDU set may refer to the description of the process of the terminal device generating the second PDU set in the embodiment shown in FIG. 3 , which will not be described again here.
  • the difference is that the network device does not need to determine the PDU set referenced by the third PDU set.
  • the terminal device After a certain protocol layer of the AS of the terminal device (such as SDAP or PDCP, etc.) performs header detection, it learns the identity of the detected third PDU set and the identity of the PDU set referenced by the third PDU set.
  • the terminal device can determine the PDU set referenced by the third PDU set based on the identification of the third PDU set and the identification of the PDU set referenced by the third PDU set, and combine the identification of the third PDU set and the PDU referenced by the third PDU set.
  • the identifier of the set is reproduced in the header of the data packet of the third PDU set-related protocol layer.
  • the network device After receiving the third PDU set, the network device does not need to know the PDU set referenced by the third PDU set.
  • the third PDU set sent by the terminal device carries information for integrity detection, and may not carry information indicating the PDU set referenced by the third PDU set.
  • the network device After receiving the third PDU set uploaded by the terminal device, the network device performs an integrity check on the third PDU set.
  • the network device performs an integrity check on the third PDU set.
  • the network device performs an integrity check on the second PDU set. The process of integrity testing will not be described again here.
  • the integrity check of the third PDU set is performed after the PDCP layer completes reordering. After the PDCP layer completes the reordering, if it is found that the integrity of the third PDU set is lacking (for example, the network device determines that the total number of PDUs belonging to the third PDU set successfully received does not exceed the threshold value, or the network device By confirming that not all PDUs belonging to the third PDU set are successfully received (to confirm the integrity of the transmission of the third PDU set), the network device is triggered to generate a PDCP status report.
  • the network device determines that the integrity of the third PDU set is lacking, that is, when the PDCP layer submits it to the SDAP layer, or the SDAP layer submits it to a higher layer, it is found that not all data packets or data packet fragments of the third PDU set have been completely received. (For example, the first packet is missing, the tail packet is missing, or the middle part of the data packet is missing).
  • the network device is triggered to generate a PDCP status report. If such a situation occurs and the third PDU set cannot be submitted upward completely, the network device can choose to directly delete the third PDU set without submitting it upward.
  • the terminal device can determine the data packets that have been successfully transmitted and the data packets that have failed to be transmitted according to the fourth instruction information, and can determine between the PDU set to which the PDU that failed to be transmitted belongs and other PDU sets. dependencies, discard the first PDU.
  • the method flow shown in Figure 5 also includes:
  • S530 The terminal device discards the first PDU.
  • the terminal device determines to discard the first PDU based on the PDU that has not been successfully received, and the PDU that has not been successfully received is the PDU in the third PDU set.
  • the first PDU includes at least one of the following: PDUs included in the fourth PDU set, PDUs not transmitted in the third PDU set, or PDUs included in the fifth PDU set, where the fourth PDU set is a PDU set that refers to the third PDU set , the fifth PDU set is the PDU set that refers to the third PDU set and/or the fourth PDU set, and the fourth PDU set refers to the third PDU set, which means: the successful decoding of the fourth PDU set is based on the successful decoding of the third PDU set. , the fifth PDU set refers to the third PDU set and/or the fourth PDU set, indicating that the successful decoding of the fifth PDU set is predicated on the successful decoding of the third PDU set and/or the fourth PDU set.
  • the terminal device If the terminal device confirms that all or part of the transmitted data packets of the third PDU set have not been successfully transmitted, and the terminal device finds based on the header detection results of the subsequently arriving fourth PDU set that the fourth PDU set depends on the third PDU set, Then the terminal device deletes the fourth PDU set from the buffer and no longer allocates uplink resources for uploading the fourth PDU set.
  • the terminal device If the terminal device confirms that some of the data packets of the third PDU set that have been transmitted have not been successfully transmitted, and the network device no longer schedules this part of the data packets, there is another part of the data packets of the third PDU set that has not been transmitted in the RLC buffer.
  • the terminal device deletes this part of the data packets from the RLC buffer; if some data packets in the third PDU set are in the HARQ buffer, they are still transmitted.
  • devices in the existing network architecture are mainly used as examples for illustrative explanations (such as network devices, terminal devices, etc.). It should be understood that the specific form of the device implemented in this application Examples are not limited. For example, devices that can achieve the same functions in the future are applicable to the embodiments of this application.
  • the methods and operations implemented by devices can also be implemented by components of the devices (such as chips or circuits).
  • network equipment and terminal equipment include corresponding hardware structures and/or software modules for performing each function.
  • the communication device provided by the present application will be described in detail below with reference to FIGS. 6 to 9 . It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for content that is not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be described again.
  • Embodiments of the present application can divide the transmitting end device or the receiving end device into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. middle.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods. The following is an example of dividing each functional module according to each function.
  • FIG. 6 is a schematic diagram of a communication device provided by this application.
  • the device 600 includes a receiving unit 610 , a sending unit 620 and a processing unit 630 .
  • the sending unit 620 is configured to report first indication information to the network device, where the first indication information indicates the second PDU set referenced by the first protocol data unit group PDU set.
  • the processing unit 630 is configured to determine whether the second PDU set is successfully uploaded based on at least one of the timeout of the timer of the terminal device and the feedback of the network device to the first indication information.
  • the receiving unit 610 is configured to receive fourth indication information from the network device, where the fourth indication information is used to indicate PDUs successfully received by the network device and/or PDUs received unsuccessfully.
  • the processing unit 630 is configured to, when the fourth indication information is used to indicate a PDU that has not been successfully received by the network device, the terminal device determines to delete the first PDU based on the PDU that has not been successfully received.
  • the device 600 corresponds to the terminal device in the method embodiment.
  • the device 600 may be a terminal device in the method embodiment, or a chip or functional module inside the terminal device in the method embodiment.
  • the corresponding units of the device 600 are used to perform corresponding steps performed by the terminal device in the method embodiments shown in FIG. 3 and FIG. 5 .
  • the processing unit 630 in the device 600 is used to execute steps related to processing of the terminal device in the method embodiment. For example, step S330 in FIG. 3 is executed, or step S530 in FIG. 5 is executed.
  • the receiving unit 610 in the device 600 is used to perform the terminal device receiving step in the method embodiment. For example, step S520 in FIG. 5 is executed.
  • the sending unit 620 in the device 600 is used to perform the steps of sending by the terminal device in the method embodiment. For example, steps S311 and S310 in Figure 3 are executed.
  • the processing unit 630 may be at least one processor.
  • the sending unit 620 may be a transmitter or an interface circuit
  • the receiving unit 610 may be a receiver or an interface circuit.
  • the receiver and transmitter can be integrated together to form a transceiver or interface circuit.
  • the device 600 may further include a storage unit for storing data and/or signaling.
  • the processing unit 630, the sending unit 620, and the receiving unit 610 may interact or be coupled with the storage unit, such as reading or calling data and/or signaling in the storage unit, so that the methods of the above embodiments are executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • FIG. 7 is a schematic structural diagram of the terminal device of the present application.
  • the terminal device 700 can be applied in the system shown in FIG. 1 .
  • FIG. 7 shows only the main components of the terminal device.
  • the terminal device 700 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is used to control the antenna and the input and output device to send and receive signals
  • the memory is used to store the computer program
  • the processor is used to call and run the computer program from the memory to execute the corresponding process executed by the terminal device in the communication method proposed in this application and/ or operation. No further details will be given here.
  • FIG. 8 is a schematic diagram of another communication device provided by this application.
  • the device 800 includes a receiving unit 810 , a sending unit 820 and a processing unit 830 .
  • the receiving unit 810 is configured to receive first indication information from the terminal device, and the first indication information is used to indicate the second PDU set referenced by the first protocol data unit group PDU set.
  • the processing unit 830 is configured to determine that when the second PDU set is not successfully received, the network device determines not to schedule the first PDU set.
  • the receiving unit 810 and the processing unit 830 are used to determine fourth indication information, and the fourth indication information is used to indicate PDUs successfully received by the network device and/or PDUs unsuccessfully received.
  • the sending unit 820 is configured to send the fourth instruction information to the terminal device when the first condition is met.
  • the device 800 corresponds to the network device in the method embodiment.
  • the apparatus 800 may be a network device in the method embodiment, or a chip or functional module inside the network device in the method embodiment.
  • the corresponding units of the device 800 are used to perform corresponding steps performed by the network device in the method embodiments shown in FIG. 3 and FIG. 5 .
  • the processing unit 830 in the device 800 is used to perform steps corresponding to processing within the network device in the method embodiment. For example, steps S312 and S320 in FIG. 3 are executed, or step S510 in FIG. 5 is executed.
  • the sending unit 820 in the device 800 is used to perform steps related to network device sending. For example, step S520 in Figure 5.
  • the receiving unit 810 in the device 800 is used to perform the receiving step of the network device in the method embodiment. For example, steps S311 and S310 of FIG. 3 are executed.
  • the receiving unit 810 and the sending unit 820 may form a transceiver unit and have the functions of receiving and sending at the same time.
  • the processing unit 830 may be at least one processor.
  • the sending unit can be a transmitter or an interface circuit.
  • the receiving unit may be a receiver or an interface circuit.
  • the receiver and transmitter can be integrated together to form a transceiver or interface circuit.
  • the device 800 may further include a storage unit for storing data and/or signaling.
  • the processing unit 830, the sending unit 820, and the receiving unit 810 may interact or be coupled with the storage unit, such as reading or calling data and/or signaling in the storage unit, so that the methods of the above embodiments are executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • Figure 9 is a schematic structural diagram of the network device of the present application, which can be used to implement the functions of the network device in the above communication method.
  • the network device 900 may include a centralized unit (central unit, CU), a distributed unit (DU), and an active antenna unit (active antenna unit,AAU).
  • CU central unit
  • DU distributed unit
  • AAU active antenna unit
  • CU central unit
  • DU distributed unit
  • AAU active antenna unit
  • RRU remote radio frequency unit
  • BBU baseband unit
  • the non-real-time part of the BBU will be separated and redefined as CU; it is responsible for processing non-real-time protocols and services.
  • Some of the physical layer processing functions of the BBU will be merged with the original RRU and passive antenna into AAU.
  • BBU BBU
  • DU BBU
  • CU and DU are distinguished by the real-time nature of processing content
  • AAU is a combination of RRU and antenna.
  • CU, DU, and AAU can be separated or combined, so there will be a variety of network deployment forms.
  • One possible deployment form is consistent with traditional 4G access network equipment, with CU and DU deployed on the same hardware. It should be understood that Figure 9 is only an example and does not limit the scope of protection of the present application.
  • the deployment form can also be DU deployed in the 5G BBU computer room, CU centralized deployment or DU centralized deployment, CU higher-level centralized deployment, etc.
  • AAU 901 can implement transceiver functions and is called a transceiver unit.
  • the transceiver unit may also be called a transceiver, a transceiver circuit, a transceiver, etc., and may include at least one antenna 909 and a radio frequency unit 9010.
  • the transceiver unit may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (also referred to as a receiver, a receiving circuit), and the transmitting unit may correspond to a transmitter (also referred to as a transmitter, a transmitting circuit). ).
  • CU and DU 902 can implement internal processing functions called processing units.
  • the processing unit can control the access network equipment, etc., and can be called a controller.
  • AAU 901, CU and DU 902 can be physically set together or physically separated.
  • the access network equipment is not limited to the form shown in Figure 9, and may also be in other forms.
  • it includes BBU and ARU, or it includes BBU and AAU; it can also be CPE, or it can be in other forms, which is not limited by this application.
  • the network device 900 shown in Figure 9 can implement the network devices involved in the method embodiments of Figures 5 and 7.
  • the operations and/or functions of each unit in the network device 900 are respectively intended to implement the corresponding processes executed by the network device in the method embodiments of this application. No further details will be given here.
  • the structure of the network device illustrated in Figure 9 is only one possible form, and should not constitute any limitation on the embodiment of the present application. This application does not exclude the possibility of other forms of network equipment structures that may appear in the future.
  • An embodiment of the present application also provides a communication system, which includes the aforementioned terminal device and network device.
  • This application also provides a computer-readable storage medium, which stores instructions.
  • the instructions When the instructions are run on a computer, the computer executes the terminal device in the method shown in Figure 3 and Figure 5. or individual steps performed by network equipment.
  • This application also provides a computer program product containing instructions.
  • the computer program product When the computer program product is run on a computer, it causes the computer to perform various steps performed by the terminal device or the network device in the methods shown in Figures 3 and 5.
  • This application also provides a chip including a processor.
  • the processor is used to read and run the computer program stored in the memory to perform corresponding operations and/or processes performed by the terminal device or network device in the communication method provided by this application.
  • the above-mentioned chips can also be replaced Switching to a chip system, I won’t go into details here.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not used. implement.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units may be selected according to actual conditions to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .
  • a and/or B means: A alone, A and B together, and B alone.
  • the character / in this article means or.
  • at least one means one and more than two (including two).

Landscapes

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

Abstract

本申请提供了一种通信方法、终端设备、网络设备及通信系统。该方法包括：终端设备向网络设备上报第一指示信息，第一指示信息指示待发送的第一协议数据单元组PDU set所参考的已经发送的第二PDU set，并根据终端设备的定时器的超时情况和网络设备对第一指示信息的反馈情况的至少之一，确定第二PDU set是否成功上传。通过上报指示信息指示待发送的第一PDU set所参考的第二PDU set，在发送指示信息之后，终端设备根据定时器的超时情况和/或网络设备对第一指示信息的反馈情况获知第二PDU set是否上传成功，以便于终端设备确定上传或者丢弃第一PDU set。

Description

通信方法、终端设备、网络设备及通信系统
本申请要求于2022年06月27日提交国家知识产权局、申请号为202210745443.8、发明名称为“一种数据传输方法、终端设备、网络设备”和于2022年07月21日提交国家知识产权局、申请号为202210872898.6、发明名称为“通信方法、终端设备、网络设备及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，具体涉及通信方法、终端设备、网络设备及通信系统。
背景技术
网络设备对终端设备的上行调度是基于终端设备发送的调度请求(scheduling request，SR)和缓存状态报告(buffer status report，BSR)。其中，网络设备基于SR可以获知终端设备有上行数据需要传输，基于BSR可以获知终端设备的缓存中缓存的数据量。
发明内容
网络设备接收到上行调度请求后，通过下行控制信息(downlink control information，DCI)调度上行数据。终端设备在接收到调度DCI后，在指定的时频资源上上传上行数据。网络设备接收到上行数据之后并不会通过MAC层的HARQ立即回复应答消息(acknowledgment，ACK)或否定应答(negative acknowledgment，NACK)指示是否成功接收到上行数据。因此终端设备无法即时确定上行数据的上传是否成功，从而导致终端设备无法确定与该上行数据相关的数据的处理方式，从而使得上行资源的利用不充分，导致上行资源的浪费。例如，在网络设备未指示终端设备重传上行数据#1的前提下，终端设备默认上行数据#1上传成功。而实际上上行数据#1未上传成功，且上行数据#1的重传次数到达上限，网络设备才没有指示重传该上行数据#1。而终端设备默认上行数据#1上传成功，从而终端设备可以继续上传与该上行数据#1相关的上行数据#2(如，上行数据#2的解码需要依赖于上行数据#1)。在这种情况下，终端设备上传上行数据#2会导致上行资源的浪费。
为了解决上述的技术问题，本申请提供一种通信方法，以期终端设备能够确定上行数据的上传是否成功，避免在无需上传数据的情况下上传数据而导致上行资源的浪费。
第一方面，提供了一种通信方法。该方法可以由终端设备执行，也可以由终端设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以终端设备执行为例进行说明。
该通信方法包括：终端设备向网络设备上报第一指示信息，第一指示信息指示第一协议数据单元组(Protocol Data Unit set，PDU set)所参考(也可称为依赖)的第二PDU set；终端设备根据终端设备的定时器的超时情况和网络设备对第一指示信息的反馈情况的至少之一，确定第二PDU set是否成功上传。其中，第一PDU set包括终端设备待发送的PDU set，第二PDU set包括终端设备已经发送的PDU set，第一PDU set参考第二PDU set表示：第一PDU set的成功解码以第二PDU set的成功解码为前提。
基于上述技术方案，终端设备上报指示待发送的第一PDU set所参考的已经发送过的第二PDU set的指示信息，并且在发送第一指示信息之后，根据启动的定时器的超时情况(如，定时时长、是否超时等)和网络设备对于接收到的第一指示信息的反馈情况(如，下发响应于第一指示信息的信息)的至少之一，确定第二PDU set是否上传成功。也就是说通过该技术方案，终端设备可以确定第二PDU set是否成功上传。
另外，在该技术方案中，终端设备可以根据确定的第二PDU set是否成功上传的结果，来确定对第一PDU set的处理。例如，第二PDU set未成功上传，终端设备确定第一PDU set也无需上传。因为第一PDU set的成功解码以第二PDU set的成功解码为前提，在第二PDU set未成功上传的情况下，即 使第一PDU set上传了也无法正确解码。因此，第一PDU set无需上传，从而终端设备可以根据判断结果确定第一PDU set的处理方式，避免在不需要上传第一PDU set的情况下上传第一PDU set，而导致上行资源的浪费。
在第一方面的某些实现方式中，第一指示信息包括媒体接入控制层控制元素(media access control control element，MAC CE)，MAC CE包括逻辑信道标识LCID和第二PDU set的标识。其中，LCID指示MAC CE对应的逻辑信道，逻辑信道用于传输第一PDU set所参考的第二PDU set的标识。
基于上述技术方案，终端设备上报的第一指示信息的信令格式可以是MAC CE，沿用现有协议中已经定义的信令格式(如，3GPP TS 38.321中定义的MAC CE的格式)，避免通过新定义信令格式实现上述第一指示信息的功能，简化方案。
在第一方面的某些实现方式中，在确定第二PDU set未成功上传的情况下，该方法还包括：终端设备丢弃第一PDU set。
基于上述技术方案，终端设备在确定第二PDU set未成功上传的情况下，能够确定即使上传第一PDU set，第一PDU set也无法正确解析，因此无需上传第一PDU set。进一步地，为了节省缓存空间，第一PDU set可以从缓存中丢弃或删除。
在第一方面的某些实现方式中，终端设备丢弃第一PDU set，包括：在第一定时器到期后或者在第一定时器到期时，若终端设备的缓存中缓存有第一PDU set，则将缓存中的第一PDU set丢弃。其中，第一定时器为终端设备针对该第一PDU set设置的丢弃定时器，第一定时器的启动时刻为终端设备的分组数据汇聚层协议(packet data convergence protocol，PDCP)实体接收到所述第一PDU set最后一个PDU的最后一个比特的时刻(也可称为时间点，time point)，且第一定时器的定时时长小于帧到达周期，帧到达周期指示相邻两个帧到达缓存的间隔。其中，终端设备的PDCP实体可以理解为终端设备的PDCP层的传输实体(也可称为transmitting PDCP entity)。
在第一方面的某些实现方式中，终端设备在第一定时器到期(其中，到期也可称为超时，expire)后或者在第一定时器到期时(也可称为时间点，time point)，终端设备的缓存中缓存有第一PDU set，表明第二PDU set未成功上传。
在第一方面的某些实现方式中，在确定第二PDU set成功上传的情况下，该方法还包括：终端设备丢弃第一PDU set中部分PDU；或者，终端设备发送第一PDU set。
基于上述技术方案，终端设备在确定第二PDU set成功上传的情况下，终端设备能够间接获知第一PDU set中包括的PDU可以上传，但是具体上传情况需要根据网络设备的调度。例如，网络设备可能仅成功调度第一PDU set中部分的PDU。再例如，网络设备成功调度第一PDU set中所有的PDU。综上，终端设备在确定第二PDU set成功上传的情况下，后续对第一PDU set的处理可能是部分成功发送或全部成功发送。
在第一方面的某些实现方式中，终端设备丢弃第一PDU set中部分PDU，包括：在第一定时器超时内，若终端设备的缓存中缓存有第一PDU set中部分PDU，则将缓存中的第一PDU set中部分PDU丢弃。其中，第一定时器为终端设备针对该第一PDU set设置的丢弃定时器，第一定时器的启动时刻为该终端设备的PDCP实体接收到所述第一PDU set最后一个PDU的最后一个比特的时刻。
在第一方面的某些实现方式中，终端设备的缓存包括终端设备的无线链路控制(radio link control，RLC)层的缓存或终端设备的分组数据汇聚层协议(packet data convergence protocol，PDCP)层的缓存。其中，当终端设备的缓存为RLC层的缓存的情况下，第一定时器到期后或到期时，终端设备的PDCP层通过通知消息通知终端设备的RLC层丢弃RLC层的缓存中的PDU set和/或PDU。
基于上述技术方案，终端设备的缓存可以是不同协议层的缓存，提高方案的灵活性。
在第一方面的某些实现方式中，终端设备根据网络设备对第一指示信息的反馈情况，确定第二PDU set未成功上传，包括：终端设备接收来自网络设备的第二指示信息，第二指示信息用于指示第二PDU set未成功上传。
在第一方面的某些实现方式中，第二指示信息用于指示第二PDU set未成功上传，包括：第二指示信息指示第二PDU set包括的部分或者全部PDU未成功上传；或者，第二指示信息指示第二PDU set中成功上传的PDU数量小于或者等于第一阈值。
在第一方面的某些实现方式中，终端设备根据终端设备的定时器的超时情况，确定第二PDU set 未成功上传，包括：终端设备在发送第一指示信息之时，启动第二定时器，若第二定时器超时，且终端设备未接收到来自网络设备的调度信息，终端设备确定第二PDU set未成功上传。
在第一方面的某些实现方式中，在终端设备发送第一指示信息之前，该方法还包括：终端设备向网络设备发送第二PDU set，第二PDU set包括第三指示信息，第三指示信息用于网络设备确定是否成功接收第二PDU set的所有PDU或达到指定数量的PDU。
在第一方面的某些实现方式中，第三指示信息包括以下至少一种：第二PDU set包括的第一个和最后一个PDU的标识；或者，第二PDU set包括的PDU的总数；或者，第二PDU set成功解码所需要成功传输的PDU的数量；或者，第二PDU set成功解码所需要成功传输的PDU的数量和第二PDU set包括的PDU的总数的比值；或者，第二PDU set所含PDU属于第二PDU set的标识；或者，第二PDU set所含PDU在第二PDU set中的序列号。
在第一方面的某些实现方式中，该方法还包括：终端设备的协议层实体在接收到该终端设备的应用层产生的第一PDU set之时(when)或之后(after)，对该第一PDU set进行报头检测，确定第一PDU set的标识和第一PDU set参考的至少一个PDU set的标识。终端设备的协议层将第一PDU set的标识和至少一个PDU set的标识封装在第一PDU set的该协议层的报头中。其中，应用层产生的第一PDU set包括第一PDU set的标识和参考至少一个PDU set的标识，具体地，第一PDU set的第一个PDU或者每个PDU包括第一PDU set的标识和参考至少一个PDU set的标识，第二PDU set为至少一个PDU set中的一个。
基于上述技术方案，终端设备可以通过报头检测获知某个PDU set的标识，以及该PDU set所参考的另一PDU set的标识，以便终端设备获知不同PDU set之间的参考关系。
在第一方面的某些实现方式中，协议层包括以下至少一项：业务数据适配(service data adaptation protocol，SDAP)层、PDCP层、非接入层(Non-Access Stratum，NAS)或无线资源控制(radio resource control，RRC)层。
第二方面，提供了一种通信方法。该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以网络设备执行为例进行说明。
该通信方法包括：网络设备接收来自终端设备的第一指示信息，第一指示信息用于指示第一协议数据单元组PDU set所参考的第二PDU set。在网络设备确定第二PDU set成功解码所需的PDU未全部成功接收的情况下，网络设备确定不调度第一PDU set。其中，第一PDU set包括终端设备待发送的PDU set，第二PDU set包括终端设备已经发送的第一PDU set所参考的PDU set，第一PDU set参考第二PDU set表示：第一PDU set的成功解码以第二PDU set的成功解码为前提。其中，第一指示信息的描述可以参考第一方面中对于第一指示信息的描述，此处不再赘述。
在第二方面的某些实现方式中，在网络设备确定第二PDU set成功接收的情况下，网络设备调度第一PDU set。
在第二方面的某些实现方式中，网络设备确定第二PDU set成功解码所需的PDU未全部成功接收，包括：网络设备确定网络设备未保存有第二PDU set的标识。
在第二方面的某些实现方式中，该方法还包括：网络设备接收来自终端设备的第二PDU set，第二PDU set包括第三指示信息。网络设备根据三指示信息确定是否保存第二PDU set的标识。其中，第三指示信息的描述可以参考第一方面中对于第三指示信息的描述，此处不再赘述。
在第二方面的某些实现方式中，在网络设备确定不调度第一PDU set之后，该方法还包括：网络设备向终端设备发送第二指示信息，第二指示信息用于指示网络设备未成功接收第二PDU set成功解码所需的全部PDU。
在第二方面的某些实现方式中，在网络设备向终端设备发送第二指示信息之前，方法还包括：网络设备确定第一定时器的定时时长大于帧到达周期。其中，第一定时器为终端设备针对该第一PDU set设置的丢弃定时器，第一定时器的启动时刻为该终端设备的PDCP实体接收到所述第一PDU set的时刻，帧到达周期指示相邻两个帧到达终端设备缓存的间隔。
在第二方面的某些实现方式中，第二指示信息用于指示网络设备未成功接收所述第二PDU set成功解码所需的全部PDU包括：第二指示信息包括至少一个PDU set的标识，指示至少一个PDU set未 成功上传，第二PDU set为至少一个PDU set中的一个。
以上第二方面及其可能的设计所示方法的技术效果可参照第一方面及其可能的设计中的技术效果。
第三方面，提供了一种通信方法。该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以网络设备执行为例进行说明。
该通信方法包括：网络设备确定满足第一条件；网络设备向终端设备发送第四指示信息，第四指示信息用于指示网络设备成功接收到的PDU和/或未成功接收到的PDU。第一条件包括以下至少一项：在第四指示信息为周期发送的前提下，到达发送第四指示信息的时刻、网络设备确定是否成功接收到第三PDU set、或网络设备接收到来自终端设备的触发信息。其中，触发信息用于触发网络设备确定第四指示信息。
基于上述技术方案，网络设备可以在满足第一条件的情况下，通过第四指示信息通知终端设备成功接收到的PDU和/或未成功接收到的PDU，以便于终端设备确定上行数据是否上传成功。
在第三方面的某些实现方式中，网络设备确定是否成功接收到第三PDU set，包括：网络设备确定是否成功接收到第三PDU set包括的所有PDU，和/或，网络设备成功接收到的PDU的数量是否超过第一阈值，网络设备成功接收到的接收到的PDU为第三PDU set包括的PDU。其中，第一阈值为预定义的。
在第三方面的某些实现方式中，在第一条件为网络设备确定是否成功接收到第三PDU set的情况下，该方法还包括：网络设备接收来自终端设备的第三PDU set，第三PDU set包括第五指示信息。网络设备根据第五指示信息确定是否成功接收到第三PDU set成功解码所需的所有PDU。
基于上述技术方案，终端设备在发送上行的第三PDU set时，可以在第三PDU set中携带第五指示信息，以便于网络设备根据第五指示信息确定是否成功接收到第三PDU set包括的所有PDU。
在第三方面的某些实现方式中，五指示信息包括以下至少一种：第三PDU set包括的第一个和最后一个PDU的标识；或者，第三PDU set包括的PDU的总数；或者，第三PDU set成功解码所需成功传输的PDU的数量；或者第三PDU set成功解码所需成功传输的PDU的数量和第三PDU set包括的PDU的总数的比值；或者第三PDU set所含PDU属于第三PDU set的标识；或者第三PDU set所含PDU在第三PDU set中的序列号。
在第三方面的某些实现方式中，网络设备根据第五指示信息确定是否成功接收到第三PDU set包括的所有PDU，包括：网络设备根据第五指示信息确定接收到第三PDU set中的部分PDU，未成功接收到第三PDU set包括的所有PDU；该方法还包括：网络设备删除或丢弃第三PDU set中的部分PDU。
基于上述技术方案，网络设备在确定未成功接收到第三PDU set包括的所有PDU，而是接收到第三PDU set包括的部分PDU的情况下，网络设备可以将接收到的部分PDU丢弃。
第四方面，提供了一种通信方法。该方法可以由终端设备执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以终端设备执行为例进行说明。
该通信方法包括：终端设备接收来自网络设备的第四指示信息，第四指示信息用于指示网络设备成功接收到的PDU和/或未成功接收到的PDU。在第四指示信息用于指示网络设备未成功接收到的PDU的情况下，终端设备根据未成功接收到的PDU，确定删除第一PDU。未成功接收到的PDU为第三PDU set中的PDU，第一PDU包括以下至少一项：第四PDU set包括的PDU、第三PDU set中未传输的PDU或第五PDU set包括的PDU。其中，第四PDU set为参考第三PDU set的PDU set，第五PDU set为参考第三PDU set和/或第四PDU set的PDU set，第四PDU set参考第三PDU set表示：第四PDU set的成功解码以第三PDU set的成功解码为前提，第五PDU set参考第三PDU set和/或第四PDU sett表示：第五PDU set的成功解码以第三PDU set和/或第四PDU set的成功解码为前提。
基于上述技术方案，终端设备可以基于接收到的第四指示信息确定某些PDU未成功传输，例如，终端设备确定PDU#1未成功传输，PDU#1为PDU set#1中的PDU。从而确定终端设备确定参考PDU set#1的PDU set可以无需上传，或者PDU set#1中的其他PDU可以无需上传，以便于终端设备丢弃无需上传的PDU set或PDU，节约终端设备的缓存和上行资源。
在第四方面的某些实现方式中，在终端设备接收来自网络设备的第三指示信息之前，该方法还包 括：终端设备向网络设备发送第三PDU set，第三PDU set包括第五指示信息，第五指示信息提供给网络设备，以便于作为网络设备确定是否成功接收第三PDU set的依据。其中，第五指示信息的描述可以参考第三方面中对于第五指示信息的描述，此处不再赘述。
在第四方面的某些实现方式中，该方法还包括：在第三PDU set缓存至缓存中之前或之时，终端设备对应用层产生的第三PDU set进行报头检测，确定第三PDU set的标识和第三PDU set参考的至少一个PDU set的标识。终端设备将第三PDU set的标识和至少一个PDU set的标识封装在第三PDU set的协议层的报头中。其中，应用层产生的第三PDU set包括第三PDU set的标识和至少一个PDU set的标识。具体地，第三PDU set的第一个PDU或者每个PDU包括第三PDU set的标识和至少一个PDU set的标识，第三PDU set的成功解码以至少一个PDU set的成功解码为前提。
基于上述技术方案，终端设备可以通过报头检测获知某个PDU set的标识，以及该PDU set所参考的另一PDU set的标识，以便终端设备获知不同PDU set之间的参考关系。
第五方面，提供了一种终端设备。终端设备用于执行上述第一方面及其任意一种实施方式、第四方面及其任意一种实施方式提供的方法。具体地，终端设备包括处理器和存储器，该存储器用于存储计算机程序；该处理器用于从存储器中调用并运行该计算机程序，使得该终端设备执行上述第一方面及其任意一种实施方式、或第四方面及其任意一种实施方式提供的方法。
第六方面，提供了一种网络设备。网络设备用于执行上述第二方面或第三方面提供的方法。具体地，网络设备包括处理器和存储器，该存储器用于存储计算机程序；该处理器用于从存储器中调用并运行该计算机程序，使得该网络设备执行上述第二方面及其任意一种实施方式或第三方面及其任意一种实施方式提供的方法。
第七方面，提供了一种通信装置。该通信装置用于执行上述第一方面及其任意一种实施方式或第四方面及其任意一种实施方式提供的方法。具体地，该通信装置可包括用于执行第一方面及其任意一种实施方式或第四方面及其任意一种实施方式提供的方法的单元和/或模块(如，处理单元，收发单元)。
在一种实现方式中，该通信装置为终端设备。当该通信装置为终端设备时，收发单元可以是收发器，或，输入/输出接口。处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该通信装置可以为终端设备中的芯片、芯片系统或电路。此时，收发单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第八方面，提供了一种通信装置。该通信装置用于执行上述第二方面及其任意一种实施方式或第三方面及其任意一种实施方式提供的方法。具体地，该通信装置可以包括用于执行第二方面及其任意一种实施方式或第三方面及其任意一种实施方式提供的方法的单元和/或模块，如处理单元和收发单元。
在一种实现方式中，该通信装置为网络设备。当该通信装置为网络设备时，收发单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该通信装置为网络设备中的芯片、芯片系统或电路时，收发单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第九方面，本申请提供一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十方面，提供一种计算机可读存储介质。该计算机可读存储介质存储有计算机程序，当计算机程序在通信装置上运行时，使得通信装置执行上述第一方面至第四方面的任意一种实现方式的方法。
第十一方面，提供一种包含指令的计算机程序产品。当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第四方面的任意一种实现方式提供的方法。
第十二方面，提供一种芯片，芯片包括处理器与通信接口，处理器通过通信接口读取存储器上存储的指令，执行上述第一方面至第四方面的任意一种实现方式提供的方法。
可选地，作为一种实现方式，芯片还包括存储器，存储器存储有计算机程序或指令，处理器用于执行存储器上存储的计算机程序或指令，当计算机程序或指令被执行时，处理器用于执行上述第一方面至第四方面的任意一种实现方式提供的方法。
第十三方面，提供一种通信系统，包括第五方面的终端设备和第六方面的网络设备。
附图说明
图1是本申请适用的通信系统示意图。
图2是网络设备和终端设备之间的协议层结构的示意图。
图3是本申请提供的一种通信方法的示意性流程图。
图4中的(a)至(d)是本申请实施例提供的终端设备确定是否成功上传第二PDU set的示意图。
图5是本申请提供的另一种通信方法的示意性流程图。
图6是本申请提供的一种通信装置的示意图。
图7是本申请的终端设备的结构示意图。
图8是本申请提供的另一种通信装置的示意图。
图9是本申请的网络设备的结构示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行具体描述。
本申请实施例的技术方案可以应用于各种通信系统。例如：第五代(5th generation，5G)系统或新空口(new radio，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请实施例的技术方案还可以应用于设备到设备(device to device，D2D)通信，车辆外联(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
为便于理解本申请实施例，示例性地，首先结合图1来介绍本申请适用的通信系统。本申请实施例中的终端设备(terminal equipment)可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、用户设备(user equipment，UE)、终端(terminal)、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备或者未来车联网中的终端设备等，本申请实施例对此并不限定。
示例性地，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称。如眼镜、手套、手表、服饰及鞋等。可穿戴设备是直接穿在身上，或是整合到用户的衣服或配件的便携式设备。可穿戴设备不仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、可不依赖智能手机实现完整或者部分的功能。例如：智能手表或智能眼镜等。另外，还可以为只专注于某一类应用功能，需要和其它设备如智能手机配合使用的便携式设备。如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备。IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，在本申请实施例中，终端设备还可以包括传感器，主要功能包括收集数据(部分终端设备)、接收网络设备的控制信息与下行数据，并发送电磁波，向网络设备传输上行数据。
本申请实施例中的网络设备可以是用于与终端设备通信的任意一种具有无线收发功能的通信设备。该设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G系统，如NR系统中的gNB，或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或分布式单元(distributed unit，DU)等。
网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对网络设备和终端设备所处的场景不做限定。
在本申请实施例中，终端设备或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，操作系统、操作系统、操作系统、操作系统或操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质包括但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读存储介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
为便于理解本申请实施例，首先以图1中示出的通信系统为例详细说明适用于本申请实施例的通信系统。如图1所示，通信系统100可以包括至少一个网络设备101和至少一个终端设备102至107。其中，终端设备102至107可以是移动的或固定的。网络设备101和终端设备102至107中的一个或多个均可以通过无线链路通信。每个网络设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
可选地，终端设备之间可以直接通信。例如可以利用设备到设备(device to device，D2D)技术等实现终端设备之间的直接通信。如图1中所示，终端设备105与106之间、终端设备105与107之间，可以利用D2D技术直接通信。终端设备106和终端设备107可以单独或同时与终端设备105通信。
终端设备105至107也可以分别与网络设备101通信。例如可以直接与网络设备101通信如图中的终端设备105和106可以直接与网络设备101通信。也可以间接地与网络设备101通信，如图1中的终端设备107经由终端设备105与网络设备101通信。
各通信设备均可以配置多个天线。对于通信系统100中的每一个通信设备而言，所配置的多个天线可以包括至少一个用于发送信号的发射天线和至少一个用于接收信号的接收天线。因此，通信系统100中的各通信设备之间，可通过多天线技术通信。
网络设备与终端设备之间的接口可以为Uu接口(或称为空口)。当然，在未来通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。示例性地，网络设备和终端设备之间的通信遵循一定的协议层结构，网络分层就是将网络节点(如，网络设备和终端设备)的数据发送、转发、打包或拆包，控制信息的加载或拆出等工作，分别由不同的硬件和软件模块去完成。这样可以将往来通信和网络互连这一复杂的问题变得较为简单。为了便于理解，结合图2简单说明本申请实施例中涉及的网络设备和终端设备之间的协议层结构。
从图2中可看出网络设备和终端设备的网络层次划分包括：应用层、RRC层、SDAP层、PDCP层、RLC层、MAC层。其中，应用层主要功能是为应用软件提供很多服务，例如文件服务器、数据库服务、电子邮件与其他网络软件服务；RRC层实现功能包括建立、维持以及释放RRC连接，分配或者 重配置用于RRC连接的无线资源；SDAP层的功能之一就是对服务质量(Quality of Service)流与数据无线承载(data radio bear，DRB)之间进行映射；PDCP层负责将IP头压缩和解压、并维护PDCP层序列号，加密和解密等等；RLC层主要提供无线链路控制功能，为上层提供分割、重传控制以及按需发送等服务；MAC层的功能包括逻辑信道和传输信道间的映射，为每个传输信道选择适当的传输格式。
需要说明的是，本申请实施例中对于终端设备和网络设备的网络层次划分不做限制，图2仅为示例，对本申请的保护范围不构成任何的限定。
应理解，图1仅为便于理解而示例的简化示意图，通信系统100中还可以包括其他网络设备或者还可以包括其他终端设备(图1未示出)。例如，通信系统100还可以包括核心网设备。接入网设备一方面为终端设备提供无线接入连接，可以向终端设备发送数据或者接收终端设备发送的数据；另一方面接入网设备和核心网设备也有连接，可以将从终端设备接收的数据转发至核心网，或者从核心网接收需要发送给终端设备的数据。
为便于理解本申请实施例，对本申请涉及的一些基本概念做简要说明。应理解，下文所介绍的基本概念是以NR协议中规定的基本概念为例进行说明，但并不限定本申请实施例只能够应用于NR系统。因此，以NR系统为例描述时出现的标准名称，都是功能性描述，具体名称并不限定，仅表示设备的功能，可以对应扩展到未来的其它系统。
1、扩展现实(eXtended Reality，XR)：包含虚拟现实(Virtual Reality，VR)、增强现实(Augmented Reality，AR)和混合现实(Mixed Reality，MR)等，是未来5G网络最具吸引力的应用之一。XR应用通过提供音视频信号，为用户提供虚拟的沉浸世界。其中，对于视频帧的传输来说分为I帧(I-frame)传输和P帧(P-frames)传输。
2、I帧和P帧：I帧可以称为帧内编码帧，是一种自带全部信息的独立帧，无需参考其它图像便可独立进行解码。P帧可以称为预测编码帧，在针对连续动态图像编码时，P帧由在它前面的P帧或者I帧预测而来，它比较与它前面的P帧或者I帧之间的差异信息或数据，也即考虑运动的特性进行帧间压缩。
3、协议数据单元(Protocol Data Unit，PDU)：一种特定的数据帧格式，是指在分层网络结构，在传输系统的每一层都将建立PDU，PDU包含来自上层的信息和当前层的实体附加的信息，这个PDU会被传送到下一较低的层。
4、协议数据单元组(Protocol Data Unit set，PDU set)：一个PDU set由一个或者多个PDU组成，是应用层产生的一个单位的信息，该一个单位的信息可以指XR媒体服务中的一个帧(frame)或一个切片(slice)。
在一些应用中，应用层需要接收一个PDU set内的所有PDU，才能使用所述一个单位的信息。在其他的一些应用中，应用层只需要接收一个PDU set的一部分，就能恢复部分或全部的所述的单位信息。
在应用层，一个PDU set内的所有PDU是作为一个整体处理的。例如，一个图片组(group of pictures，GoP)内的某一个frame只有在其依赖的frame全被接收和解码之后，才能被正常解码。若是不考虑这种PDU set间的依赖性，5GS的随机丢掉的数据包会影响后续传输数据包的正常解码，从而导致无效数据包的传输和无线的浪费。
5、PDU set序列号(PDU set sequence number，PS-SN)和参考PDU set序列号(reference PDU set sequence number，RPS-SN)：为指示PDU set之间的参考(或者说依赖)关系，PDU set可以携带两个序列号：PS-SN和RPS-SN。若是参考PDU set未成功传输，则后续依赖该参考PDU set的PDU set可不必传输以节约无线资源。
为了便于描述，可以将被参考的PDU set称为参考PDU set，将参考该参考PDU set的PDU set称为依赖PDU set。
6、新数据指示(new data indicator，NDI)字段和混合自动请求重传(hybrid automatic repeat request，HARQ)进程数量：用于调度上行数据的DCI(如，DCI format 0_0，0_1或0_2)中1bit的NDI字段和4bits的HARQ process number用于指示网络设备是在调度重传数据，还是在调度新传数据。
NDI结合HARQ process number用于指示上传数据是新传还是重传。对于同一个HARQ process number，若NDI指示值与前一次调度相同，则此次调度为前一次调度数据的重传，若NDI指示值与前 一次调度不同(前一次为0，此次为1，或相反)，则此次调度为新传。终端设备在收到NDI指示新传后，便会利用未传输过的数据来刷新关联的HARQ process的buffer；若是收到NDI指示重传，则将缓存对应HARQ process的buffer中的数据重新上传。
7、上行调度：网络设备对终端设备上行数据的调度，基于终端设备发出的SR和BSR信令。其中，SR为物理层信令，终端设备向网络设备上传SR，可使用专有的、周期性的物理层上行控制信道(physical uplink control channel，PUCCH)信道。网络设备在收到终端设备发送的SR信号后，便知道终端设备有上行数据需要传输，可为终端设备分配上行资源。但是，通过SR信号，网络设备并不能确定终端设备有多少数据需要传输，不能确定应该给终端设备分配多少上行资源。因此，后续终端设备仍需向网络设备发送BSR信号，来汇报终端设侧的buffer中缓存有多少数据，以便申请上行资源。
网络设备收到上行调度的申请后，使用DCI(如，DCI format 0_0，0_1或0_2)来调度上行数据。终端设备在收到调度DCI后会在指定的时频资源块上传数据。网络设备接收上传数据后，与下行传输不同，并不向终端设备反馈ACK\NACK信号。若是某一数据上传不成功，则由网络设备决定是否重传这一数据。网络设备会直接向终端设备发送调度重传信号的DCI来调度需要重传的数据；若是未成功上传的数据不需重传，则网络设备直接调度新传的数据，而不再调度该未成功上传数据。
8、非确认模式(unacknowledgement mode，UM)：在WCDMA系统中，RLC层位于MAC层之上，属于L2的一部分，为用户和控制数据提供分段和重传业务。每个RLC实体由RRC配置，并且根据业务类型有三种模式：透明模式(transparent mode，TM)、非确认模式(UM)、确认模式(acknowledged mode，AM)。其中，非确认模式：发送实体在高层PDU上添加必要的控制协议开销，然后进行传送但并不保证传递到对等实体，且没有使用重传协议。接收实体对所接收到的错误数据标记为错误后递交，或者直接丢弃并向高层报告。由于RLC PDU包含有顺序号，因此能够检测高层PDU的完整性。
此外，为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一指示信息用于指示A时，可以包括该指示信息直接指示A或间接指示A，而并不代表该指示信息中一定包括有A。
将指示信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种。待指示信息可以作为一个整体一起发送，也可以分成多个子信息分开发送，而且这些子信息的发送周期和/或发送时机可以相同，也可以不同。具体发送方法本申请不进行限定。其中，这些子信息的发送周期和/或发送时机可以是预先定义的，例如根据协议预先定义的，也可以是发射端设备通过向接收端设备发送配置信息来配置的。其中，该配置信息可以例如但不限于包括无线资源控制信令、MAC层信令和物理层信令中的一种或者至少两种的组合。其中，无线资源控制信令例如包RRC信令；MAC层信令例如包括MAC控制元素(control element，CE)；物理层信令例如包括DCI。
第二，在本申请中示出的“至少一个”是指一个或者多个，“多个”是指两个或两个以上。另外，在本申请的实施例中，“第一”、“第二”以及各种数字编号(例如，“#1”、“#2”等)只是为了描述方便进行的区分，并不用来限制本申请实施例的范围。下文各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定，应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。此外，在本申请实施例中，“510”、“610”、“810”等字样仅为了描述方便作出的标识，并不是对执行步骤的次序进行限定。
第三，在本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
第四，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第五，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第六，在本申请实施例中，控制信道可以包括PDCCH、增强物理下行控制信道(enhanced physical downlink control channel，EPDCCH)等其它物理层控制信道，但为了描述方便，下面的术语或概念仅以PDCCH为例进行说明，但本申请实施例并不限于此。
应理解，本申请实施例中是以下行控制信道为物理下行控制信道PDCCH为例进行说明，但并不对本申请实施例构成限定，事实上，下行控制信道也可能定义为其他的术语或概念，均适用本申请实施例的技术方案。在本申请实施例中，下行控制信道和PDCCH可能会交替使用，可以认为PDCCH是上行控制信道的一种示例描述。
第七，在本申请实施例中，各术语及英文缩略语，如下行控制信息(DCI)、媒体接入控制控制元素(MAC-CE)、无线资源控制(RRC)等，均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
第八，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
上文结合图1简单介绍了本申请实施例提供的通信方法能够应用的场景，以及介绍了本申请实施例中可能涉及到的基本概念，并在基本概念中介绍了目前上行调度的方式，由上述可知目前上行调度的方式存在以下问题：
1)网络设备在调度上行数据时，并不会即时给终端设备反馈ACK/NACK信号。终端设备不能即时确认当前上传数据是否上传成功。终端设备通过HARQ process所能确认的是网络设备不再调度之前上传的数据了。这既有可能是因为网络设备成功接收了所述数据，也有可能是因为达到了最大重传次数，网络设备不再调度重传了。因此，终端设备不能确认上传的数据是否上传成功了。
2)XR业务中视频帧的压缩编码有相互依赖关系，若PDU set#2依赖于PDU set#1，但PDU set#1未成功上传，即便PDU set#2成功上传，PDU set#2也不能在应用层成功解码。因为终端设备不能确认PDU set#1是否成功上传，所以即使在PDU set#1上传失败的情况下，终端也不能主动放弃PDU set#2的上传，也就是说网络设备调度的PDU set#2为无效帧，便造成了上行资源的浪费。
为了解决目前上行调度存在的问题，本申请提供一种通信方法，确定上行的数据是否上传成功，避免调度无效帧而导致的上行资源的浪费。
应理解，本申请实施例提供的通信方法可以应用于通过多天线技术通信的系统，例如，图1中所示的通信系统100。该通信系统可以包括至少一个网络设备和至少一个终端设备。网络设备和终端设备之间可通过多天线技术通信。
还应理解，下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
以下，以网络设备与终端设备之间的交互为例详细说明本申请实施例提供的通信方法。
图3是本申请提供的一种通信方法的示意性流程图。包括以下步骤：
S310，终端设备向网络设备发送第一指示信息，或者说网络设备接收来自终端设备的第一指示信息。
第一指示信息用于指示第一PDU set所参考(也可称为所依赖)的第二PDU set。第一PDU set参考(也可称为依赖)第二PDU set可以理解为，第一PDU set的成功解码以第二PDU set的成功解码为前提。也就是说，在第二PDU set成功解码的前提下(或者说在第二PDU set成功上传的前提下)，第一PDU set才有可能成功解码。
具体地，上述的第一PDU set为终端设备待发送的PDU set，如缓存在终端设备的缓存中(如，缓存在终端设备的RLC层的缓存和/或终端设备的PDCP层的缓存中的PDU set)。
例如，第一PDU set进入终端设备的RLC层的buffer之后，递交终端设备的MAC层组包前，终端设备的触发向网络设备发送第一指示信息。
由上述可知，第一指示信息能够指示第二PDU set。例如，第一指示信息中包括能够用于指示第二PDU set的信息。可选地，第一指示信息中包括第二PDU set的标识(如，第二PDU set的序列号)。
示例性地，该实施例中，终端设备可以通过如下流程获知第二PDU set的标识：
终端设备的协议层在接收到所述终端设备的应用层产生的所述第一PDU set之时或之后，能够通过报头检测(如，深度包检测、包过滤等方法)，获知第一PDU set的标识以及第一PDU set所参考的第二PDU set的标识。具体地，终端设备的应用层在打包第一PDU set的数据时，在属于第一PDU set的PDU的数据包报头(如，可在属于第一PDU set每个PDU的数据包报头，也可仅在第一PDU set的第一个PDU的数据包报头)携带第一PDU set的标识和第一PDU set参考的至少一个PDU set的标识，终端设备的应用层产生第一PDU set之后，进入接入层(access stratum，AS)层，在AS层某个协议层(如，SDAP层或PDCP层或NAS层或RRC层)进行报头检测，获得第一PDU set的标识和第一PDU set参考的至少一个PDU set的标识，上述的第二PDU set为该至少一个PDU set中的一个。
上述的第二PDU set为终端设备已经发送过的PDU set，第一PDU set所参考的PDU set未被发送的或正在发送的(如，缓存在终端设备的RLC层的缓存或终端设备的PDCP层的缓存中的第一PDU set所参考的PDU set)无需通过第一指示信息指示。
例如，第一PDU set所参考的PDU set包括PDU set#1、PDU set#2和PDU set#3。若PDU set#1为终端设备已经发送过的PDU set，PDU set#2和PDU set#3为未被终端设备发送的PDU set，或者PDU set#2和PDU set#3为终端设备正在发送的PDU set，则第一指示信息指示PDU set#1即可，无需指示PDU set#2和PDU set#3。原因在于：发送第一指示信息的目的是为了网络设备判断已经发送的PDU set#1是否成功接收到，如果终端设备已知PDU set#2和PDU set#3还未成功发送，那么终端设备已经获知网络设备未成功接收到PDU set#2和PDU set#3，没有必要再通过第一指示信息指示PDU set#2和PDU set#3，以期网络设备确定是否成功接收到PDU set#2和PDU set#3。
应理解，第一PDU set所参考的已经发送的PDU set还可以包括除第二PDU set之外的其他PDU set，在该情况下，第一指示信息中还可以用于指示第一PDU set所参考的其他PDU set，为了便于描述，该实施例中以第一PDU set所参考的PDU set为第二PDU set进行说明，也就是说不管第一PDU set所参考的已经发送的PDU set有多少个，都可以称之为第二PDU set。
另外，终端设备可以一次上报指示多个PDU set所参考的已发送的PDU set的信息。也就是说，终端设备可以通过一个指示信息一次指示缓存中的多个PDU set分别参考的PDU set。
例如，上述的第一PDU set包括第一PDU set#1、第一PDU set#2和第一PDU set#3，且第一PDU set#1所参考的第二PDU set#1和第二PDU set#2已经发送，第一PDU set#2所参考的第二PDU set#3和第二PDU set#4已经发送，第一PDU set#3所参考的第二PDU set#5和第二PDU set#6已经发送。第一指示信息可以用于指示第二PDU set#1、第二PDU set#2、第二PDU set#3、第二PDU set#4、第二PDU set#5和第二PDU set#6。
示例性地，为了简化方案，第一指示信息可以沿用目前已有的信令格式。例如，第一指示信息为MAC CE，MAC CE包括逻辑信道标识LCID和第二PDU set的标识，其中，LCID指示MAC CE对应的逻辑信道，逻辑信道用于传输第一PDU set所参考的PDU set的标识。可以理解为，LCID用于指示MAC CE的类型为指示第一PDU set所参考的PDU set的MAC CE。第二PDU set的标识用于标识第二PDU set。
例如，MAC CE可以称为依赖(Dependency)MAC CE，该Dependency MAC CE的信令格式如下表1所示：
其中，第二PDU set#1的标识可以为第二PDU set#1的序列号，或者其他可以标识第二PDU set#1的信息；同理，第二PDU set#2的标识可以为第二PDU set#2的序列号，或者其他可以标识第二PDU set#2的信息。
需要说明的是，该实施例中主要考虑第一PDU set有所参考的第二PDU set的情况，对于属于独立帧的PDU set(如，某个PDU set未参考其他的PDU set，可以称为独立PDU set)没有参考的PDU set， 也就没有参考的PDU set需要通过第一指示信息上报。
示例性地，对于没有参考的PDU set的独立PDU set可以不发送第一指示信息，或者，发送第一指示信息，而第一指示信息中指示所参考的PDU set的字段设置为0。
例如，针对某个独立帧的PDU set触发的Dependency MAC CE，该Dependency MAC C中包括的所依赖的PDU set SN的字段设置为0。
作为一种可能的实现方式，在第一指示信息为MAC CE的情况下，终端设备触发MAC CE之后，若终端设备的MAC层有上行资源，便可以与缓存状态报告(buffer status report，BSR)MAC CE一起发送给网络设备。
作为另一种可能的实现方式，终端设备可以请求分配用于传输第一指示信息的上行资源。
该实施例中对于终端设备如何向网络设备发送第一指示信息不做限定。
进一步地，该实施例中，网络设备接收到上述的第一指示信息之后，可以比较第二PDU set的标识和本地保存的至少一个PDU set的标识，并根据比较结果，确定是否需要调度第一PDU set。图3所示的方法流程还包括：
S320，网络设备确定是否调度第一PDU set。
作为一种可能的实现方式，在网络设备确定第二PDU set未成功接收的情况下，网络设备确定不调度第一PDU set。
例如，网络设备成功接收到的PDU set包括PDU set#1和PDU set#3，并且网络设备本地保存有PDU set#1和PDU set#3的标识“#1”和“#3”。在网络设备接收到第一指示信息之后，获知第二PDU set的标识为“#2”，确定网络设备本地未保存标识“#2”，则网络设备确定第二PDU set未成功接收。
由上述可知第一PDU set的成功解码以第二PDU set的成功解码为前提，若网络设备确定第二PDU set未成功接收，且通过指示第一指示信息功能的信息(如，第一指示信息中的LCID)确定第一指示信息指示的是第一PDU set所参考的第二PDU set，则网络设备确定第二PDU set未成功接收，第一PDU set也就无需调度了。从而在该实现方式下，网络设备确定不调度第一PDU set。
作为另一种可能的实现方式，在网络设备确定第二PDU set成功接收的情况下，网络设备确定调度第一PDU set。
例如，网络设备成功接收到的PDU set包括PDU set#2和PDU set#3，并且网络设备本地保存有PDU set#1和PDU set#3的标识“#2”和“#3”，在网络设备接收到第一指示信息之后，获知第二PDU set的标识为“#2”，确定网络设备本地保存有标识“#2”，则网络设备确定第二PDU set成功接收，从而网络设备确定调度第一PDU set。
示例性地，网络设备若是决定调度第一PDU set，可以通过PDCCH信道向终端设备发送调度信息(如，DCI信令)。
由上述的步骤S320可知，网络设备是通过确定是否成功接收到第二PDU set，判断是否需要调度第一PDU set，则图3所示的方法流程还包括：
S311，终端设备向网络设备发送第二PDU set，或者说网络设备接收来自终端设备的第二PDU set。
具体地，第二PDU set包括第三指示信息，第三指示信息提供给网络设备，以便于网络设备基于该第三指示信息确定是否成功接收第二PDU set。可选地，该第三指示信息可以称为完整性指示信息。
示例性地，第三指示信息包括以下至少一种：第二PDU set包括的第一个和最后一个PDU的标识；或者，第二PDU set包括的PDU的总数；或者，第二PDU set成功解码所需成功传输的PDU的数量；或者第二PDU set成功解码所需成功传输的PDU的数量和第二PDU set包括的PDU的总数的比值；或者第二PDU set所含PDU属于第二PDU set的标识；或者，第二PDU set所含PDU在第二PDU set中的序列号。
该实施例中，第三指示信息的功能可以通过不同的方式实现。
由上述可知，第二PDU set中包括用于完整性检测的第三指示信息，为了便于理解，下面简单说明终端设备如何生成包括第三指示信息的第二PDU set：
终端设备的应用层在打包第二PDU set的数据时，在属于该第二PDU set的PDU的数据包报头(如，可在属于该第二PDU set每个PDU数据包报头，也可仅在该第二PDU set的首个PDU的数据包报头)携带如下数据：
第二PDU set的序列号(sequence number，SN)以及第二PDU set所依赖的PDU set的序列号。
例如，终端设备的应用层生成第二PDU set，第二PDU set的第一个PDU或者每个PDU中包括第二PDU set的标识和第二PDU set所参考的至少一个PDU set的标识。
应理解，终端设备的应用层生成其他的PDU set的方式和生成第二PDU set(或第一PDU set)的方式类似，若某个一PDU set所参考的PDU set为多个，则终端设备应用层应在该PDU set的数据包报头(如，该PDU set的第一个PDU，或者PDU set的每个PDU)中携带所有该PDU set所参考的PDU set的标识。若某个一PDU set为独立PDU set，终端设备可以将独立PDU set的数据包报头中携带独立PDU set所参考的PDU set的标识的字段置零。
进一步地，终端设备应用层产生第二PDU set后，进入AS层，在AS层某个协议层(如，SDAP层或PDCP层)进行报头检测，获得第二PDU set的标识和第二PDU set所参考的第二PDU set的标识，并将这两类标识转载至第二PDU set的SDAP层或PDCP层的报头中。
该实施例中，为便于网络设备做PDU set完整性检测，终端设备可以在第二PDU set中携带用于完整性检测的第三指示信息。
作为一种可能的实现方式，终端设备在第二PDU set的第一个PDU和最后一个PDU做标识，分别指示为第二PDU set的第一个和最后一个PDU。
另外，终端设备在属于第二PDU set的每个PDU中加入PDU在第二PDU set中的标识。如，在每个PDU中加入PDU在第二PDU set中的PDU序列号。
在该实现方式下，第三指示信息可以理解为包括：第二PDU set的第一个和最后一个PDU的标识信息，以及第二PDU set所含PDU在第二PDU set中的PDU序列号。
作为另一种可能的实现方式，终端设备提供第二PDU set中所含PDU的总数，以及第二PDU set所含PDU属于第二PDU set的标识。
在该实现方式下，第三指示信息可以理解为包括：第二PDU set中所含PDU的总数，以及第二PDU set所含PDU属于第二PDU set的标识。
作为又一种可能的实现方式，终端设备提供成功传输第二PDU set所需的PDU的数量的最小值，以及第二PDU set所含PDU属于第二PDU set的标识。
在该实现方式下，第三指示信息可以理解为包括：第二PDU set成功传输所需的PDU的数量，以及第二PDU set所含PDU属于第二PDU set的标识。
应理解，上述只是以生成包括第三指示信息的第二PDU set为例，说明该实施例中终端设备如何生成包括用于完整性检测信息的PDU set，对本申请的保护范围不构成任何的限定。例如，对于除第二PDU set之外的其他PDU set，终端设备生成PDU set的过程可以参考终端设备生成第二PDU set的流程，此处不再赘述。
网络设备在接收到第二PDU set包括的PDU之后，可以基于第二PDU set中的第三指示信息确定是否完整接收该第二PDU set，并基于判断结果确定是否保存第二PDU set的标识，图3所示的方法流程还包括：
S312，网络设备确定是否保存第二PDU set的标识。
具体地，该实施例中网络设备接收到终端设备发送的数据后，需对接收的数据做PDU set完整性的检测，并记录完整接收的PDU set的SN。为了便于描述，以网络设备对第二PDU set做完整性检测为例进行说明，对于其他的PDU set，网络设备做完整性检测的流程类似，不再重复说明。
示例性地，网络设备对第二PDU set做完整性检测的过程如下：
如上所述，终端设备的AS某个协议层(如，SDAP或PDCP等)进行报头检测后，将被检测的第二PDU set的标识和第二PDU set所参考的PDU set的标识转载到第二PDU set相关协议层的数据包的报头。相应地，网络设备接收终端设备的数据后，也在对应的协议层做PDU set的完整性检测。
若被检测的第二PDU set的标识和第二PDU set所参考的PDU set的标识被加载在第二PDU set的SDAP层，则网络设备在SDAP层对第二PDU set进行完整性检测。
若被检测的第二PDU set的标识和第二PDU set所参考的PDU set的标识被加载在第二PDU set的PDCP层，则网络设备在PDCP层对第二PDU set进行完整性检测。
示例性地，若网络设备是在PDCP层对第二PDU set进行完整性检测，可以在PDCP层对第二PDU  set做完重排序后，向上层递交对第二PDU set的数据包之时对第二PDU set进行完整性检测。该检测用于确定第二PDU set包括的所有PDU是否被成功接收，或者该检测用于确定第二PDU set中被成功接收的PDU数量是否超过第一阈值。
作为一种可能的实现方式，网络设备在接收到终端设备上传的数据包后，在前述协议层(如，SDAP或PDCP等)，确定属于第二PDU set的第一个和最后一个PDU，并通过PDU在第二PDU set中的标识的连贯性，确定第二PDU set是否被完整接收。
例如，第三指示信息指示第二PDU set的第一个和最后一个PDU分别为PDU#1和PDU#/6，以及PDU在第二PDU set中的标识为PDU#1、PDU#2、PDU#3、PDU#4、PDU#5、PDU#6。当网络设备成功接收到PDU#1和PDU#/6，且接收到的PDU在第二PDU set中的标识连贯时，确定第二PDU set被完整接收，否则确定第二PDU set未被完整接收。
作为另一种可能的实现方式，网络设备通过确定属于第二PDU set的数据包数量总数和PDU属于第二PDU set的标识来确认第二PDU set是否被完整接收。
例如，第三指示信息指示PDU在第二PDU set中的标识为PDU#1、PDU#2、PDU#3、PDU#4、PDU#5、PDU#6，以及第二PDU set包括的PDU总数为6。当网络设备接收到6个PDU，且PDU的标识分别为PDU#1、PDU#2、PDU#3、PDU#4、PDU#5、PDU#6时，确定第二PDU set被完整接收，否则确定第二PDU set未被完整接收。
作为又一种可能的实现方式，网络设备通过确定成功接收的属于第二PDU set的数据包总数是否达到门限值，来判断第二PDU set是否被完整接收。
例如，第三指示信息指示成功接收的属于第二PDU set的数据包总数为3，PDU在第二PDU set中的标识为PDU#1、PDU#2、PDU#3、PDU#4、PDU#5、PDU#6。当网络设备接收到3个或3个以上的PDU，且至少3个PDU的标识为PDU#1、PDU#2、PDU#3、PDU#4、PDU#5、PDU#6中的3个时，确定第二PDU set被完整接收，否则确定第二PDU set未被完整接收。
应理解，上述只是举例说明网络设备对第二PDU set进行完整性检测可能的方式，对本申请的保护范围不构成任何的限定，其他能够实现对数据包进行完整性检测的方法也在本申请的保护范围之内，此处不再赘述。
若网络设备判断第二PDU set被完整接收，则网络设备保存第二PDU set的标识，否则，网络设备不保存第二PDU set的标识。
例如，第二PDU set的标识为“#2”，当网络设备判断第二PDU set被完整接收，则网络设备保存“#2”；否则，网络设备不保存“#2”。
示例性地，网络设备可以自动清空时间T之前或间隔N个PDU set的标识之前保存的PDU set的标识。其中，T值和N值的设定，满足被清除的PDU set的标识不会再指代后续传输的PDU set所参考的PDU set的标识。
由上述可知，网络设备通过保存的PDU set的标识，来确定步骤S320中第一PDU set所参考的第二PDU set是否被成功上传。若第一指示信息上报的第二PDU set的标识为网络设备保存的PDU set的标识中的一个，则表明对应的第二PDU set成功上传，否则表明第二PDU set未成功上传。
进一步地，该实施例中终端设备在发送第一指示信息之后可以根据终端设备的定时器的超时情况和网络设备对第一指示信息的反馈情况的至少之一，确定第二PDU set是否成功上传。图3所示的方法流程还包括：
S330，终端设备确定第二PDU set是否成功上传。
作为一种可能的实现方式，终端设备根据本地的第一定时器的超时情况确定第二PDU set是否成功上传。
具体地，第一定时器为终端设备针对该第一PDU set设置的丢弃定时器，第一定时器的启动时刻为该终端设备的PDCP实体接收到所述第一PDU set的时刻，且在该实现方式下，该第一定时器的定时时长小于帧到达周期，该实施例中的帧到达周期指示相邻两个帧到达终端设备的缓存的间隔。其中，终端设备的PDCP实体可以理解为终端设备的PDCP层的传输实体(如，transmitting PDCP entity)。
示例性地，第一定时器的启动时刻为该终端设备的PDCP实体接收到所述第一PDU set的时刻，还可以理解为终端设备的PDCP层将第一PDU set传递给终端设备的RLC层的时刻，还可以理解为第 一PDU set缓存至缓存中的时刻。
应理解，该实施例中对于第一定时器和帧到达周期的设置不做任何的限定，可以参考目前相关技术中的描述，该实施例中复用已有的定时器的超时情况，判断第二PDU set是否成功上传。
另外，网络设备能够获知第一定时器和周期帧到达周期相关的信息，可以理解为该实施例中网络设备能够获知第一定时器到期时刻(或者说终止时刻)早于第二帧到达终端设备的缓存的时刻，第二帧为第一帧的下一帧，第一帧包括第一PDU set。
例如，第一定时器为网络设备配置的，网络设备能够确定第一定时器相关的信息(如，定时时长、起始时刻等信息)；周期帧到达周期相关的信息为终端设备上报给网络设备的。
在该实现方式下，终端设备根据本地的第一定时器的超时情况确定第二PDU set未成功上传，包括：在第一定时器到期后或者在第一定时器到期时，终端设备未接收到网络设备的调度信息，终端设备确定第二PDU set未成功上传；或者，
终端设备根据本地的第一定时器的超时情况确定第二PDU set成功上传，包括：在第一定时器到期前，终端设备接收到网络设备的调度信息。终端设备根据调度信息上传第一PDU set。应理解，网络设备的调度信息可能调度第一PDU set中的部分PDU。在第一定时器到期后或者在第一定时器到期时，若终端设备的缓存中还缓存有第一PDU set中的部分PDU，终端设备丢弃未上传的部分PDU。
为了便于理解，结合图4中的(a)详细说明终端设备如何根据第一定时器的超时情况确定第二PDU set是否成功上传。
如图4中的(a)所示，终端设备待发送的PDU set为PDU set#1(即上述的第一PDU set)，该PDU set#1为帧#1中包括的一个PDU set，在t1时刻PDU set#1进入终端设备RLC层的缓存(buffer)，在t1时刻终端设备启动第一定时器(如，启动丢弃定时器(discard Timer))，该第一定时器用于指示在第一定时器到期之前如果没有接收到调度PDU set#1的DCI，丢弃该PDU set#1。
该实施例中终端设备将PDU set#1递交MAC层组包之前，触发上报Dependency MAC CE(如，在t1时刻之后的t2时刻上报第一指示信息)，该Dependency MAC CE指示PDU set#1依赖的PDU set#0(即上述的第二PDU set)，该PDU set#0为已上报的一个PDU set，如，该PDU set#0为帧#0中包括的一个PDU set。
例如，网络设备确定PDU set#0未成功上传(如，网络设备确定帧#0中的PDU set未成功上传)，则网络设备确定不调度终端设备buffer中的PDU set#1，但是网络设备不显示通知终端设备PDU set#0未成功接收，终端设备等到第一定时器到期后，终端设备仍未接收到网络设备的调度信息，默认PDU set#0未成功接收，清除buffer中的PDU set#1。
还例如，网络设备确定PDU set#0成功上传(如，网络设备确定帧#0中的PDU set已经成功上传)，则网络设备确定调度终端设备buffer中的PDU set#1，网络设备下发调度信息(如，DCI)调度PDU set#1。若第一定时器到期后，终端设备的缓存中还缓存有PDU set#1的部分PDU，清除buffer中的部分PDU。
该实施例中，第一定时器的定时时长小于或者等于帧到达周期，也就是说在下一个帧中包括的PDU set进入终端设备RLC/PDCP层的缓存(如，图4中的(a)所示的t3时刻)之前，第一定时器到期。
由上述可知，在网络设备确定PDU set#0未成功上传的情况下，网络设备无需显示通知终端设备PDU set#0未成功接收，终端设备可以根据终端设备的定时器的超时情况(如，第一定时器超时、第一定时器的定时时长小于帧到达周期)确定PDU set#0未成功接收，从而确定PDU set#1也无需上传，为了节约本地的缓存空间，丢弃该PDU set#1。
作为另一种可能的实现方式，终端设备根据本地的第二定时器的超时情况确定第二PDU set是否成功上传。
具体地，第二定时器为终端设备在发送第一指示信息之时启动的定时器，该第二定时器的起始时刻为终端设备发送第一指示信息的时刻(或者说终端设备发送完第一指示信息的时刻)。
作为一种可能的实现方式，该第二定时器的终止时刻在第二帧到达终端设备的缓存之前，第二帧为第一帧的下一帧，第一帧包括第一PDU set。
在该实现方式下，终端设备根据本地的第二定时器的超时情况确定第二PDU set未成功上传，包括：在第二定时器未超时(或者说第二定时器运行期间内)，终端设备未接收到网络设备的调度信息，终端设备确定第二PDU set未成功上传；或者，
终端设备根据本地的第二定时器的超时情况确定第二PDU set成功上传，包括：在第二定时器未超时(或者说第二定时器运行期间内)，终端设备接收到网络设备的调度信息，终端设备确定第二PDU set成功上传。
为了便于理解，结合图4中的(b)详细说明终端设备如何根据第二定时器的超时情况确定第二PDU set未成功上传。
如图4中的(b)所示，终端设备待发送的PDU set为PDU set#1，该PDU set#1为帧#1中包括的一个PDU set，在t1时刻PDU set#1进入终端设备RLC层的缓存(buffer)，在t1时刻终端设备启动第一定时器(如，启动丢弃定时器(discard Timer))，该第一定时器用于指示在第一定时器到期之前如果没有接收到调度PDU set#1的DCI，丢弃该PDU set#1。
该实施例中终端设备将PDU set#1递交MAC层组包之前，触发上报Dependency MAC CE(如，在t1时刻之后的t2时刻上报第一指示信息)，并且在上报Dependency MAC CE的时刻启动第二定时器(如，丢包定时器(droppingPacketTimer))。具体地，该Dependency MAC CE指示PDU set#1依赖的PDU set#0，该PDU set#0为已上报的一个PDU set，该PDU set#0为帧#0中包括的一个PDU set。
若终端设备在droppingPacketTimer运行期间，收到了网络设备发送的调度上行数据的DCI，则终止droppingPacketTimer运行。例如，网络设备确定PDU set#0成功上传，可以通过DCI调度PDU set#1，终端设备确定PDU set#0成功上传终止droppingPacketTimer。
若终端设备在droppingPacketTimer运行期间，收到网络设备发送的调度Dependency MAC CE重传的DCI，则终端设备在重发Dependency MAC CE之后，重新启动droppingPacketTimer。例如，网络设备未成功接收到Dependency MAC CE，可以指示终端设备重传Dependency MAC CE，针对重传Dependency MAC CE的处理与上述的初传Dependency MAC CE类似，不再赘述。
若终端设备在droppingPacketTimer运行期间，没有收到调度上行数据的DCI(如，上述的调度上行数据的DCI以及调度Dependency MAC CE重传的DCI)，则终端设备确定PDU set#0未成功上传，网络设备不调度buffer中的PDU set#1，终端设备可以清除buffer中的PDU set#1。
该实施例中，第一定时器的定时时长大于帧到达周期，也就是说在下一个帧中包括的PDU set进入终端设备RLC/PDCP层的缓存(如，图4中的(b)所示的t3时刻)之后，第一定时器到期。
需要说明的是，如果第二定时器的终止时刻在第二帧到达终端设备的缓存之后，在第二定时器的运行期间内，若有新的PDU set(如，帧#2的PDU set)到达buffer，则终端设备不发送关于该新的PDU set的调度请求(scheduling request，SR)和第一指示信息(如，针对新的PDU set的Dependency MAC CE)。如图4中的(c)所示，在第二定时器到期之后(如图4中的(c)中的t4)，发送关于新的PDU set的SR和第一指示信息。
作为又一种可能的实现方式，终端设备根据网络设备针对第一指示信息的反馈情况确定第二PDU set是否成功上传。
具体地，网络设备针对第一指示信息的反馈情况可以是网络设备是否针对第一指示信息下发第二指示信息，指示第二PDU set未成功上传。
在该实现方式下，终端设备根据网络设备针对第一指示信息的反馈情况确定第二PDU set是否成功上传，包括：终端设备接收到来自网络设备的第二指示信息，第二指示信息用于指示第二PDU set未成功上传。
示例性地，第二指示信息指示第二PDU set未成功上传，包括：第二指示信息指示第二PDU set包括的部分或者全部PDU未成功上传；或者，第二指示信息指示第二PDU set中成功上传的PDU数量小于第一阈值。
应理解，上述只是举例说明第二指示信息指示第二PDU set未成功上传的可能方式，对本申请的保护范围不构成任何的限定，其他能够用于指示第二PDU set未成功上传的方式也在本申请的保护范围之内，此处不再赘述。
作为一种可能的实现方式，在第一定时器的定时时长大于帧到达周期的情况下，为了避免UE等到帧#1的discard Timer到期，再将帧#1的PDU set#1抛弃会导致在调度帧#2的PDU set时，必然先调度帧#1的PDU set#1，造成资源浪费。
例如，帧#2对帧#1没有依赖，网络设备在接收到针对帧#2包括的PDU set的Dependency MAC CE 之后，可以调度帧#2包括的PDU set。而当网络设备调度帧#2包括的PDU set的情况下，如果UE的缓存中还缓存有帧#1的PDU set#1，终端设备会通过传输帧#2包括的PDU set的上行资源发送PDU set#1，造成资源浪费。因此，该实现方式下需要网络设备下发第二指示信息，指示终端设备将帧#1的PDU set#1丢弃。
作为另一种可能的实现方式，网络设备检测到Dependency MAC CE上报的所依赖PDU set中，有部分已成功上传，另一部分没有成功上传，则网络设备下发第二指示信息向终端设备指示未上传成功的PDU set的标识，其中，未上传成功的PDU set包括上述的PDU set#0。
为了便于理解，结合图4中的(d)详细说明终端设备网络设备针对第一指示信息的反馈情况确定第二PDU set未成功上传。
如图4中的(d)所示，终端设备待发送的PDU set为PDU set#1，该PDU set#1为帧#1中包括的一个PDU set，在t1时刻PDU set#1进入终端设备PDCP层的缓存(buffer)，在t1时刻终端设备启动第一定时器(如，启动丢弃定时器(discard Timer))，该第一定时器用于指示在第一定时器到期之前如果没有接收到调度PDU set#1的DCI，丢弃该PDU set#1。
作为一种可能的实现方式，该实施例中终端设备将PDU set#1递交MAC层组包之前，触发上报Dependency MAC CE(如，在t1时刻之后的t2时刻上报第一指示信息)，该Dependency MAC CE指示PDU set#1依赖的PDU set#0，该PDU set#0为已上报的一个PDU set，该PDU set#0为帧#0中包括的一个PDU set。
例如，网络设备确定PDU set#0未成功上传(如，帧#0中的PDU set未成功上传)，则网络设备确定不调度终端设备buffer中的PDU set#1，且网络设备确定第一定时器的定时时长大于帧到达周期，也就是说在下一个帧中包括的PDU set进入终端设备RLC/PDCP层的缓存(如，图4中的(d)所示的t3时刻)之后，第一定时器才到期。网络设备确定不调度PDU set#1，通过第二指示信息通知终端设备丢弃buffer中PDU set#1(如，图4中的(d)中所示的t5时刻发送第二指示信息)。
作为另一种可能的实现方式，该实施例中终端设备将PDU set#1递交MAC层组包之前，触发上报Dependency MAC CE(如，在t1时刻之后的t2时刻上报第一指示信息)，该Dependency MAC CE指示PDU set#1依赖的PDU set#0和PDU set#0_1，DU set#0和PDU set#0_1为已上报的PDU set，该PDU set#0和PDU set#0_1为帧#0中包括的PDU set。
例如，网络设备确定PDU set#0未成功上传(如，帧#0中的PDU set未成功上传)和PDU set#0_1成功上传，网络设备通过第二指示信息(如，图4中的(d)中所示的t5时刻发送第二指示信息)通知终端设备PDU set#0未成功上传，终端设备接收到该第二指示信息后，确定PDU set#0未成功上传，同时确定PDU set#1赖于PDU set#0，则将PDU set#1从buffer中删除。
图4中的(d)中所示的示例与图4中的(a)中所示的示例类似，不同之处在于，帧#2对帧#1没有依赖，网络设备可以调度帧#2的PDU set。若UE等到帧#1的discardTimer到期，再将帧#1的PDU set#1抛弃，则在调度帧#2的PDU set时，会先调度帧#1的PDU set，造成资源浪费。因此，需要图4中的(d)中所示的示例中网络设备额外下发第二指示信息，指示UE将帧#1的PDU set#1丢弃。第二指示信息可为MAC CE、PDCP report或SDAP report，不限定第二指示信息的格式和协议层。
应理解，图3所示的实施例中以上行数据为PDU set为例进行说明，针对其他的具有依赖关系的上行数据本申请实施例也适用。例如，在第一上行数据和第二上行数据之间具有依赖关系的情况下，终端设备在发送第一上行数据之前，也可以通过第一指示信息通知网络设备该第一上行数据依赖于第二上行数据，在确定第二上行数据未上传成功的情况下，无需调度第一上行数据，也就是说上述实施例中第一PDU set可以替换为通用的描述“第一上行数据”，第二PDU set可以替换为通用的描述“第二上行数据”，而上行数据之间的依赖关系可以理解为第一上行数据和第二上行数据之间强相关，如果第二上行数据未上传成功，即使第一上行数据上传成功了也没有意义。
图3所示的实施例中，终端设备上报指示待发送的第一PDU set所参考的已经发送过的第二PDU set的指示信息，并且在发送第一指示信息之后，根据启动的定时器的超时情况(如，定时时长、是否超时等)和网络设备对于接收到的第一指示信息的反馈情况(如，下发响应于第一指示信息的信息)的至少之一，确定第二PDU set是否上传成功。也就是说该技术方案中，终端设备可以获知第二PDU set是否成功上传。
另外，图3所示的实施例中，终端设备可以基于第二PDU set是否成功上传的结果确定对第一PDU set的处理，例如，第二PDU set未成功上传，终端设备确定第一PDU set也无需上传，因为第一PDU set的成功解码以第二PDU set的成功解码为前提，在第二PDU set未成功上传的情况下，即使第一PDU set上传了也无法正确解码，终端设备可以丢弃第一PDU set。
本申请还提供一种通信方法，网络设备在满足一定的条件的情况下下发第四指示信息指示某个PDU是否成功接收到，以便于终端设备确定上行数据是否上传成功。下面结合图5详细介绍该通信方法。
图5是本申请提供的另一种通信方法的示意性流程图。包括以下步骤：
S510，网络设备确定满足第一条件。
S520，网络设备向终端设备发送第四指示信息，或者说终端设备接收来自网络设备的第四指示信息。
第四指示信息用于指示网络设备成功接收到的PDU和/或未成功接收到的PDU。
该第一条件包括以下至少一项：
第四指示信息为周期发送的信息，且到达发送第四指示信息的时刻、网络设备确定是否成功接收到第三PDU set、或网络设备接收到来自终端设备的触发信息，其中，触发信息用于触发网络设备确定第四指示信息。
其中，网络设备确定是否成功接收到第三PDU set包括：该网络设备确定是否成功接收到第三PDU set包括的所有PDU，和/或，该网络设备成功接收到的第三PDU set的PDU数据是否超过第一阈值，其中，第一阈值为预定义的。
示例性地，第四指示信息可以称为PDCP status report，PDCP status report被触发后，递交给网络设备的RLC和/或MAC层传输给终端设备。
作为一种可能的实现方式，在第一条件为第四指示信息为周期发送的信息，且到达发送第四指示信息的时刻的情况下，网络设备周期性地发送第四指示信息。
例如，网络设备对上行PDU进行检测，记录成功接收到的PDU和未成功接收到的PDU，并周期性地通过第四指示信息通知终端设备成功接收到的PDU和/或未成功接收到的PDU。可选地，周期发送第四指示信息的周期大小为预设的(如，每隔10min下发一次第四指示信息，周期发送的起始时刻可以为接收到第一个PDU的时刻)。
作为另一种可能的实现方式，在第一条件为网络设备接收到来自终端设备的触发信息的情况下，网络设备接收来自终端设备的触发信息，该触发信息用于指示网络设备下发指示成功接收到的PDU和/或未成功接收到的PDU的第四指示信息。
例如，网络设备接收到终端设备的触发信息，确定接收到该触发信息之前成功接收到的PDU和未成功接收到的PDU，并通过第四指示信息通知终端设备成功接收到的PDU和/或未成功接收到的PDU。
作为又一种可能的实现方式，在第一条件为网络设备确定是否成功接收到第三PDU set的情况下，网络设备接收来自终端设备的第三PDU set，第三PDU set包括第五指示信息，第五指示信息用于网络设备确定是否成功接收第三PDU set。
可选地，第五指示信息可以称为完整性指示信息。
网络设备根据第五指示信息确定是否成功接收到第三PDU set。例如，网络设备根据第五指示信息确定是否成功接收到第三PDU set包括的所有PDU，或者，还例如，网络设备根据第五指示信息确定成功接收到的第三PDU set的PDU数量是否超过第一阈值。
第五指示信息包括以下至少一种：第三PDU set包括的第一个和最后一个PDU的标识；或者，第三PDU set包括的PDU的总数；或者，第三PDU set成功解码所需的成功传输的PDU的数量；或者，第三PDU set成功解码所需的成功传输的PDU的数量和第三PDU set包括的PDU的总数的比值；或者，第三PDU set所含PDU属于第三PDU set的标识；或者，第三PDU set所含PDU在第三PDU set中的序列号。
该实施例中，为便于网络设备做PDU set完整性检测，终端设备可以在第三PDU set中携带用于完整性检测的第五指示信息。具体地，终端设备生成第三PDU set的过程可以参考图3所示的实施例中对于终端设备生成第二PDU set的过程的描述，此处不再赘述。
不同点在于网络设备无需确定第三PDU set所参考的PDU set。
例如，终端设备的AS某个协议层(如，SDAP或PDCP等)进行报头检测后，获知检测的第三PDU set的标识和第三PDU set所参考的PDU set的标识。终端设备能够根据第三PDU set的标识和第三PDU set所参考的PDU set的标识，确定第三PDU set所参考的PDU set，将第三PDU set的标识和第三PDU set所参考的PDU set的标识转载到第三PDU set相关协议层的数据包的报头。网络设备接收到第三PDU set之后无需获知第三PDU set所参考的PDU set。
或者，该实施例中终端设备发送的第三PDU set中携带用于完整性检测的信息，可以不携带指示第三PDU set所参考的PDU set的信息。
具体地，网络设备收到终端设备上传的第三PDU set后，对第三PDU set进行完整性检测，具体的完整性检测流程可以参考图3所示的实施例中网络设备对第二PDU set进行完整性检测的流程，此处不再赘述。
例如，对第三PDU set进行完整性检测是在PDCP层做完重排序后进行。在PDCP层做完重排序后，若发现第三PDU set的完整性有所缺失(如，网络设备通过确定成功接收的属于第三PDU set的PDU总数没有达到门限值以上，或者，网络设备通过确认不是所有的属于第三PDU set的PDU都被成功接收，来确认第三PDU set传输的完整性)，则触发网络设备产生一个PDCP status report。
网络设备确定第三PDU set完整性有所缺失，即PDCP层向SDAP层递交，或SDAP层向更高层递交的时候，发现并非所有第三PDU set的数据包或数据包分段都被完整接收(如，缺首包，或缺尾包，或缺中间部分的数据包)。发生此类情况，且第三PDU set需向上层递交，则触发网络设备产生PDCP status report。若此类情况发生，第三PDU set不能完整向上递交，网络设备可选择直接删除第三PDU set不向上递交。
进一步地，终端设备接收到第四指示信息之后，可以根据第四指示信息确定已经成功传输的数据包和传输失败的数据包，并可以根据传输失败的PDU所属的PDU set和其他PDU set之间的依赖关系，丢弃第一PDU。图5所示的方法流程还包括：
S530，终端设备丢弃第一PDU。
在第四指示信息用于指示网络设备未成功接收到的PDU的情况下，终端设备根据未成功接收到的PDU确定丢弃第一PDU，未成功接收到的PDU为第三PDU set中的PDU。第一PDU包括以下至少一项：第四PDU set包括的PDU、第三PDU set中未传输的PDU或第五PDU set包括的PDU，其中，第四PDU set为参考第三PDU set的PDU set，第五PDU set为参考第三PDU set和/或第四PDU set的PDU set，第四PDU set参考第三PDU set表示：第四PDU set的成功解码以第三PDU set的成功解码为前提，第五PDU set参考第三PDU set和/或第四PDU sett表示：第五PDU set的成功解码以第三PDU set和/或第四PDU set的成功解码为前提。
若终端设备确认已传输的第三PDU set的全部或部分数据包未成功传输，且终端设备依据对后续到达的第四PDU set的报头检测结果发现，第四PDU set依赖于第三PDU set，则终端设备将第四PDU set从buffer中删除，不再为上传第四PDU set分配上行资源。
若终端设备确认已传输的第三PDU set的部分数据包未成功传输，且网络设备已不再调度这一部分数据包，第三PDU set尚有另一部分数据包在RLC的buffer中未进行传输，则终端设备将该部分数据包从RLC的buffer中删除；若第三PDU set有部分数据包在HARQ buffer中，则依然传输。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
还应理解，在上述一些实施例中，主要以现有的网络架构中的设备为例进行了示例性说明(如网络设备、终端设备等等)，应理解，对于设备的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的设备都适用于本申请实施例。
可以理解的是，上述各个方法实施例中，由设备(如网络设备、终端设备)实现的方法和操作，也可以由设备的部件(例如芯片或者电路)实现。
以上，结合图3和图5详细说明了本申请实施例提供的通信方法。上述通信方法主要从网络设备和终端设备之间交互的角度进行了介绍。可以理解的是，网络设备和终端设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。
本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
以下结合图6至图9详细说明本申请提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应。因此，未详细描述的内容可以参见上文方法实施例，为了简洁，部分内容不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
示例性地，图6是本申请提供的一种通信装置的示意图。如图6示，装置600包括接收单元610、发送单元620和处理单元630。
作为一个示例，发送单元620，用于向网络设备上报第一指示信息，第一指示信息指示第一协议数据单元组PDU set所参考的第二PDU set。
处理单元630，用于根据终端设备的定时器的超时情况和网络设备对第一指示信息的反馈情况的至少之一，确定第二PDU set是否成功上传。
作为另一个示例，接收单元610，用于接收来自网络设备的第四指示信息，第四指示信息用于指示网络设备成功接收到的PDU和/或未成功接收到的PDU。
处理单元630，用于在第四指示信息用于指示网络设备未成功接收到的PDU的情况下，终端设备根据未成功接收到的PDU确定删除第一PDU。
装置600和方法实施例中的终端设备对应。装置600可以是方法实施例中的终端设备，或者方法实施例中的终端设备内部的芯片或功能模块。装置600的相应单元用于执行图3和图5所示的方法实施例中由终端设备执行的相应步骤。其中，装置600中的处理单元630用于执行方法实施例中终端设备对应与处理相关的步骤。例如，执行图3中的步骤S330，或执行图5中的步骤S530。装置600中的接收单元610用于执行方法实施例中终端设备接收步骤。例如，执行图5中的步骤S520。装置600中的发送单元620，用于执行方法实施例中终端设备发送的步骤。例如，执行图3中的步骤S311、S310。
其中，处理单元630可以是至少一个处理器。发送单元620可以是发射器或者接口电路，接收单元610可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选地，装置600还可包括存储单元，用于存储数据和/或信令。处理单元630、发送单元620、和接收单元610可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
示例性地，图7是本申请的终端设备的结构示意图。终端设备700可应用于图1所示出的系统中。为了便于说明，图7仅示出了终端设备的主要部件。如图7所示，终端设备700包括处理器、存储器、控制电路、天线以及输入输出装置。处理器用于控制天线以及输入输出装置收发信号，存储器用于存储计算机程序，处理器用于从存储器中调用并运行该计算机程序，以执行本申请提出的通信方法中由终端设备执行的相应流程和/或操作。此处不再赘述。
示例性地，图8是本申请提供的另一种通信装置的示意图。如图8所示，装置800包括接收单元810、发送单元820和处理单元830。
作为一个示例，接收单元810，用于接收来自终端设备的第一指示信息，第一指示信息用于指示第一协议数据单元组PDU set所参考的第二PDU set。
处理单元830，用于确定第二PDU set未成功接收的情况下，网络设备确定不调度第一PDU set。
作为另一个示例，接收单元810和处理单元830，用于确定第四指示信息，第四指示信息用于指示 网络设备成功接收到的PDU和/或未成功接收到的PDU。
发送单元820，用于在满足第一条件下，装置800向终端设备发送第四指示信息。
装置800和方法实施例中的网络设备对应。装置800可以是方法实施例中的网络设备，或者方法实施例中的网络设备内部的芯片或功能模块。装置800的相应单元用于执行图3和图5所示的方法实施例中由网络设备执行的相应步骤。其中，装置800中的处理单元830用于执行方法实施例中网络设备内部对应于处理相关的步骤。例如，执行图3中的步骤S312和S320，或执行图5中的步骤S510。装置800中的发送单元820，用于执行网络设备发送相关的步骤。例如，图5中的步骤S520。装置800中的接收单元810，用于执行方法实施例中网络设备的接收步骤。例如，执行图3的步骤S311和S310。
接收单元810和发送单元820可以组成收发单元，同时具有接收和发送的功能。处理单元830可以是至少一个处理器。发送单元可以是发射器或者接口电路。接收单元可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选地，装置800还可以包括存储单元，用于存储数据和/或信令。处理单元830、发送单元820、和接收单元810可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图9，图9是本申请的网络设备的结构示意图，可以用于实现上述通信方法中的网络设备的功能。
一种可能的方式中，例如在5G通信系统中的某些实现方案中，网络设备900可以包括集中单元(central unit，CU)、分布式单元(distributed unit，DU)和有源天线单元(active antenna unit,AAU)。相比于LTE通信系统中的接入网设备由一个或多个射频单元，如远端射频单元(remote radio unit，RRU)9010和一个或多个基带单元(base band unit，BBU)来说原BBU的非实时部分将分割出来，重新定义为CU；负责处理非实时协议和服务、BBU的部分物理层处理功能与原RRU及无源天线合并为AAU、BBU的剩余功能重新定义为DU，负责处理物理层协议和实时服务。简而言之，CU和DU，以处理内容的实时性进行区分、AAU为RRU和天线的组合。
CU、DU、AAU可以采取分离或合设的方式，所以会出现多种网络部署形态。一种可能的部署形态与传统4G接入网设备一致，CU与DU共硬件部署。应理解，图9只是一种示例，对本申请的保护范围并不限制。例如，部署形态还可以是DU部署在5G BBU机房，CU集中部署或DU集中部署，CU更高层次集中等。
AAU 901可以实现收发功能称为收发单元。可选地，该收发单元还可以称为收发机、收发电路、或者收发器等，其可以包括至少一个天线909和射频单元9010。可选地，收发单元可以包括接收单元和发送单元，接收单元可以对应于接收器(也可称为接收机、接收电路)，发送单元可以对应于发射器(也可称为发射机、发射电路)。CU和DU 902可以实现内部处理功能称为处理单元。可选地，处理单元可以对接入网设备进行控制等，可以称为控制器。AAU 901与CU和DU 902可以是物理上设置在一起，也可以物理上分离设置的。
另外，接入网设备不限于图9所示的形态，也可以是其它形态。例如，包括BBU和ARU，或者包括BBU和AAU；也可以为CPE，还可以为其它形态，本申请不限定。
应理解，图9所示的网络设备900能够实现图5和图7的方法实施例中涉及的网络设备。网络设备900中的各个单元的操作和/或功能，分别为了实现本申请方法实施例中由网络设备执行的相应流程。此处不再赘述。图9示例的网络设备的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的网络设备结构的可能。
本申请实施例还提供一种通信系统，其包括前述的终端设备和网络设备。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图3和图5所示的方法中终端设备或网络设备执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图3和图5所示的方法中终端设备或网络设备执行的各个步骤。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的通信方法中由终端设备或网络设备执行的相应操作和/或流程。上述的芯片也可以替 换为芯片系统，此处不再赘述。
本申请中的术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含。例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本领域技术人员可意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的。例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
另外，本申请中和/或表示存在三种关系。例如，A和/或B表示：单独存在A，同时存在A和B，单独存在B。另外，本文中字符/表示或。本申请中至少一个，表示一个和两个以上(含两个)。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    终端设备向网络设备上报第一指示信息，所述第一指示信息指示第一协议数据单元组PDU set所参考的第二PDU set；
    所述终端设备根据所述终端设备的定时器的超时情况和所述网络设备对所述第一指示信息的反馈情况的至少之一，确定所述第二PDU set是否成功上传；
    其中，所述第一PDU set包括所述终端设备待发送的PDU set，所述第二PDU set包括所述终端设备已经发送的PDU set；所述第一PDU set参考所述第二PDU set表示：所述第一PDU set的成功解码以所述第二PDU set的成功解码为前提。
  2. 根据权利要求1所述的方法，其特征在于，所述第一指示信息包括媒体接入控制层控制元素MAC CE，所述MAC CE包括逻辑信道标识LCID和所述第二PDU set的标识；其中，所述LCID指示所述MAC CE对应的逻辑信道，所述逻辑信道用于传输所述第一PDU set所参考的所述第二PDU set的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，在确定所述第二PDU set未成功上传的情况下，所述方法还包括：所述终端设备丢弃所述第一PDU set。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备丢弃所述第一PDU set，包括：
    在第一定时器到期时，若所述终端设备的缓存中缓存有所述第一PDU set，则将所述缓存中的所述第一PDU set丢弃；
    其中，所述第一定时器为所述终端设备针对所述第一PDU set设置的丢弃定时器，所述第一定时器的启动时刻为所述终端设备的分组数据汇聚层协议PDCP实体接收到所述第一PDU set最后一个PDU的最后一个比特的时刻，所述第一定时器的定时时长小于帧到达周期，所述帧到达周期指示相邻两个帧到达所述缓存的间隔。
  5. 根据权利要求1或2所述的方法，其特征在于，在确定所述第二PDU set成功上传的情况下，所述方法还包括：
    所述终端设备丢弃所述第一PDU set中部分PDU；或者，
    所述终端设备发送所述第一PDU set。
  6. 根据权利要求5所述的方法，其特征在于，所述终端设备丢弃所述第一PDU set中部分PDU，包括：
    在第一定时器到期时，若所述终端设备的缓存中缓存有所述第一PDU set中部分PDU，则将所述缓存中的所述第一PDU set中部分PDU丢弃；
    其中，所述第一定时器为所述终端设备针对所述第一PDU set设置的丢弃定时器，所述第一定时器的启动时刻为所述终端设备的分组数据汇聚层协议PDCP实体接收到所述第一PDU set最后一个PDU的最后一个比特的时刻。
  7. 根据权利要求4或6所述的方法，其特征在于，所述终端设备的缓存包括：
    所述终端设备的无线链路控制RLC层的缓存和/或所述终端设备的分组数据汇聚层协议PDCP层的缓存。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述终端设备根据所述网络设备对所述第一指示信息的反馈情况，确定所述第二PDU set未成功上传，包括：
    所述终端设备接收来自所述网络设备的第二指示信息，所述第二指示信息用于指示所述第二PDU set未成功上传。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述终端设备根据所述终端设备的定时器的超时情况，确定所述第二PDU set未成功上传，包括：
    所述终端设备在发送所述第一指示信息之时，启动第二定时器，若所述第二定时器超时，且所述终端设备未接收到来自所述网络设备的调度信息，所述终端设备确定所述第二PDU set未成功上传。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，在所述终端设备发送第一指示信息之前，所述方法还包括：
    所述终端设备向所述网络设备发送所述第二PDU set，所述第二PDU set包括第三指示信息，所述第三指示信息提供给所述网络设备，用于所述网络设备确定是否成功接收所述第二PDU set的所有PDU或达到指定数量的PDU。
  11. 根据权利要求10所述的方法，其特征在于，所述第三指示信息包括以下至少一种：
    所述第二PDU set包括的第一个和最后一个PDU的标识；或者，
    所述第二PDU set包括的PDU的总数；或者，
    所述第二PDU set成功解码所需要成功传输所需的PDU的数量；或者
    所述第二PDU set成功解码所需要成功传输所需的PDU的数量和所述第二PDU set包括的PDU的总数的比值；或者
    所述第二PDU set所含PDU属于所述第二PDU set的标识；或者
    所述第二PDU set所含PDU在所述第二PDU set中的序列号。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备的协议层实体在接收到所述终端设备的应用层产生的所述第一PDU set之时或之后，对所述第一PDU set进行报头检测，确定所述第一PDU set的标识和所述第一PDU set参考的至少一个PDU set的标识；
    所述终端设备的协议层将所述第一PDU set的标识和所述至少一个PDU set的标识封装在所述第一PDU set的所述协议层的报头中；
    其中，所述第一PDU set的第一个PDU或者每个PDU包括所述第一PDU set的标识和所述参考至少一个PDU set的标识，所述第二PDU set为所述至少一个PDU set中的一个。
  13. 根据权利要求12所述的方法，其特征在于，所述协议层包括以下至少一项：
    业务数据适配SDAP层、分组数据汇聚层协议PDCP层、非接入层NAS或无线资源控制RRC层。
  14. 一种通信方法，其特征在于，包括：
    网络设备接收来自终端设备的第一指示信息，所述第一指示信息用于指示第一协议数据单元组PDU set所参考的第二PDU set；
    在所述网络设备确定所述第二PDU set成功解码所需的PDU未全部成功接收的情况下，所述网络设备确定不调度所述第一PDU set；
    其中，所述第一PDU set包括所述终端设备待发送的PDU set，所述第二PDU set包括所述终端设备已经发送的所述第一PDU set所参考的PDU set，所述第一PDU set参考所述第二PDU set表示：所述第一PDU set的成功解码以所述第二PDU set的成功解码为前提。
  15. 根据权利要求14所述的方法，其特征在于，在所述网络设备确定所述第二PDU set成功接收的情况下，所述方法还包括：
    所述网络设备向所述终端设备发送调度信息，所述调度信息用于调度所述第一PDU set。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一指示信息包括媒体接入控制层控制元素MAC CE，所述MAC CE包括逻辑信道标识LCID和所述第二PDU set的标识；
    其中，所述LCID指示所述MAC CE对应的逻辑信道，所述逻辑信道用于传输所述第一PDU set所参考的所述第二PDU set的标识。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，所述网络设备确定所述第二PDU set成功解码所需的PDU未全部成功接收，包括：所述网络设备确定所述网络设备未保存有所述第二PDU set的标识。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收来自所述终端设备的所述第二PDU set，所述第二PDU set包括第三指示信息；
    所述网络设备根据所述三指示信息确定是否保存所述第二PDU set的标识。
  19. 根据权利要求18所述的方法，其特征在于，所述三指示信息包括以下至少一种：
    所述第二PDU set包括的第一个和最后一个PDU的标识；或者，
    所述第二PDU set包括的PDU的总数；或者，
    所述第二PDU set成功解码所需成功传输所需的PDU的数量；或者
    所述第二PDU set成功解码所需成功传输所需的PDU的数量和所述第二PDU set包括的PDU的总 数的比值；或者
    所述第二PDU set所含PDU属于所述第二PDU set的标识；或者，
    所述第二PDU set所含PDU在所述第二PDU set中的序列号。
  20. 根据权利要求14至19中任一项所述的方法，其特征在于，在所述网络设备确定不调度所述第一PDU set之后，所述方法还包括：
    所述网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示所述网络设备未成功接收所述第二PDU set成功解码所需的全部PDU。
  21. 根据权利要求20所述的方法，其特征在于，在所述网络设备向所述终端设备发送第二指示信息之前，所述方法还包括：
    所述网络设备确定第一定时器的定时时长大于帧到达周期，
    其中，所述第一定时器为所述终端设备针对所述第一PDU set设置的丢弃定时器，所述第一定时器的启动时刻为所述终端设备的分组数据汇聚层协议PDCP实体接收到所述第一PDU set的时刻，所述帧到达周期指示相邻两个帧到达所述终端设备缓存的间隔。
  22. 根据权利要求20或21所述的方法，其特征在于，所述第二指示信息用于指示网络设备未成功接收所述第二PDU set成功解码所需的全部PDU包括：
    所述第二指示信息包括至少一个PDU set的标识，指示所述至少一个PDU set未成功上传，所述第二PDU set为所述至少一个PDU set中的一个。
  23. 一种通信方法，其特征在于，包括：
    网络设备确定满足第一条件；
    所述网络设备向终端设备发送第四指示信息，所述第四指示信息用于指示所述网络设备成功接收到的PDU和/或未成功接收到的PDU；
    所述第一条件包括以下至少一项：所述第四指示信息为周期发送的信息，且到达发送所述第四指示信息的时刻、所述网络设备确定是否成功接收到第三PDU set、或所述网络设备接收到来自所述终端设备的触发信息；
    其中，所述触发信息用于触发所述网络设备确定所述第四指示信息。
  24. 根据权利要求23所述的方法，其特征在于，在所述第一条件为所述网络设备确定是否成功接收到第三PDU set的情况下，所述方法还包括：
    所述网络设备接收来自终端设备的所述第三PDU set，所述第三PDU set包括第五指示信息；
    所述网络设备根据所述第五指示信息确定是否成功接收到第三PDU set成功解码所需的所有PDU。
  25. 根据权利要求24所述的方法，其特征在于，所述五指示信息包括以下至少一种：
    所述第三PDU set包括的第一个和最后一个PDU的标识；或者，
    所述第三PDU set包括的PDU的总数；或者，
    所述第三PDU set成功解码所需成功传输所需的PDU的数量；或者
    所述第三PDU set成功解码所需成功传输所需的PDU的数量和所述第三PDU set包括的PDU的总数的比值；或者
    所述第三PDU set所含PDU属于所述第三PDU set的标识；或者，
    所述第三PDU set所含PDU在所述第三PDU set中的序列号。
  26. 根据权利要求24或25所述的方法，其特征在于，所述网络设备根据所述第五指示信息确定是否成功接收到第三PDU set包括的所有PDU，包括：所述网络设备根据所述第五指示信息确定接收到所述第三PDU set中的部分PDU，未成功接收到第三PDU set包括的所有PDU；
    所述方法还包括：所述网络设备丢弃所述第三PDU set中的部分PDU。
  27. 一种通信方法，其特征在于，包括：
    终端设备接收来自网络设备的第四指示信息，所述第四指示信息用于指示所述网络设备成功接收到的PDU和/或未成功接收到的PDU；
    在所述第四指示信息用于指示所述网络设备未成功接收到的PDU的情况下，所述终端设备根据所述未成功接收到的PDU确定丢弃第一PDU，所述未成功接收到的PDU为第三PDU set中的PDU；
    所述第一PDU包括以下至少一项：
    第四PDU set包括的PDU、所述第三PDU set中未传输的PDU或第五PDU set包括的PDU，
    其中，所述第四PDU set为参考所述第三PDU set的PDU set，所述第五PDU set为参考所述第三PDU set和/或所述第四PDU set的PDU set，所述第四PDU set参考所述第三PDU set表示：所述第四PDU set的成功解码以所述第三PDU set的成功解码为前提；所述第五PDU set参考所述第三PDU set和/或所述第四PDU set表示：所述第五PDU set的成功解码以所述第三PDU set和/或所述第四PDU set的成功解码为前提。
  28. 根据权利要求27所述的方法，其特征在于，在所述终端设备接收来自网络设备的第三指示信息之前，所述方法还包括：
    所述终端设备向网络设备发送所述第三PDU set，所述第三PDU set包括第五指示信息，所述第五指示信息提供给所述网络设备，用于所述网络设备确定是否成功接收所述第三PDU set。
  29. 根据权利要求28所述的方法，其特征在于，所述五指示信息包括以下至少一种：
    所述第三PDU set包括的第一个和最后一个PDU的标识；或者，
    所述第三PDU set包括的PDU的总数；或者，
    所述第三PDU set成功解码所需的成功传输的PDU的数量；或者
    所述第三PDU set成功解码所需的成功传输的PDU的数量和所述第三PDU set包括的PDU的总数的比值；或者
    所述第三PDU set所含PDU属于所述第三PDU set的标识；或者，
    所述第三PDU set所含PDU在所述第三PDU set中的序列号。
  30. 根据权利要求27至29中任一项所述的方法，其特征在于，所述方法还包括：
    在所述第三PDU set缓存至缓存中之前或之时，
    所述终端设备对应用层产生的所述第三PDU set进行报头检测，确定所述第三PDU set的标识和所述第三PDU set参考的至少一个PDU set的标识；
    所述终端设备将所述第三PDU set的标识和所述至少一个PDU set的标识封装在所述第三PDU set的协议层的报头中，
    其中，所述第三PDU set的第一个PDU或者每个PDU包括所述第三PDU set的标识和所述至少一个PDU set的标识，所述第三PDU set的成功解码以所述至少一个PDU set的成功解码为前提。
  31. 一种通信系统，其特征在于，包括终端设备和网络设备，所述终端设备用于执行如权利要求1至13中任一项所述的方法，所述网络设备用于执行如权利要求14至22中任一项所述的方法；或者，
    所述终端设备用于执行如权利要求27至30中任一项所述的方法，所述网络设备用于执行如权利要求23至26中任一项所述的方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机指令，当所述计算机指令在终端设备上运行时，使得所述终端设备执行如权利要求1至30中任一项所述的方法。
  33. 一种计算机程序产品，其特征在于，包含指令，当所述计算机指令在网络设备上运行时，使得所述网络设备执行如权利要求1至30中任一项所述的方法。
PCT/CN2023/100756 2022-06-27 2023-06-16 通信方法、终端设备、网络设备及通信系统 WO2024001831A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210745443.8 2022-06-27
CN202210745443 2022-06-27
CN202210872898.6 2022-07-21
CN202210872898.6A CN117375775A (zh) 2022-06-27 2022-07-21 通信方法、终端设备、网络设备及通信系统

Publications (1)

Publication Number Publication Date
WO2024001831A1 true WO2024001831A1 (zh) 2024-01-04

Family

ID=89383207

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100756 WO2024001831A1 (zh) 2022-06-27 2023-06-16 通信方法、终端设备、网络设备及通信系统

Country Status (1)

Country Link
WO (1) WO2024001831A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018071050A1 (en) * 2016-10-14 2018-04-19 Intel Corporation RETRANSMISSION PROCEDURES FOR FIFTH GENERATION (5G) NEW RADIO (NR) THINGS SIDELINK (tSL) COMMUNICATION
CN112136282A (zh) * 2018-05-18 2020-12-25 高通股份有限公司 指示媒体接入控制(mac)-控制元素(ce)信息
US20210368399A1 (en) * 2019-02-25 2021-11-25 Huawei Technologies Co., Ltd. PSCell Activation with Early Data-Forwarding for Dual Connectivity Based Handover
WO2022017517A1 (en) * 2020-07-24 2022-01-27 Qualcomm Incorporated Rateless coding at a layer two protocol layer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018071050A1 (en) * 2016-10-14 2018-04-19 Intel Corporation RETRANSMISSION PROCEDURES FOR FIFTH GENERATION (5G) NEW RADIO (NR) THINGS SIDELINK (tSL) COMMUNICATION
CN112136282A (zh) * 2018-05-18 2020-12-25 高通股份有限公司 指示媒体接入控制(mac)-控制元素(ce)信息
US20210368399A1 (en) * 2019-02-25 2021-11-25 Huawei Technologies Co., Ltd. PSCell Activation with Early Data-Forwarding for Dual Connectivity Based Handover
WO2022017517A1 (en) * 2020-07-24 2022-01-27 Qualcomm Incorporated Rateless coding at a layer two protocol layer

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "KI#5: Solution of PDU Set transmission coordination between RAN and UPF", 3GPP DRAFT; S2-2204388, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20220516 - 20220520, 6 May 2022 (2022-05-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052159888 *

Similar Documents

Publication Publication Date Title
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
TW201129191A (en) Method of handling resource assignment and related communication device
WO2018053692A1 (zh) 数据传输方法、装置及系统
CN107979847B (zh) 数据传输的方法、装置、用户设备和基站
CN110089060A (zh) 不具有始终在线的反馈的即时上行链路接入
US20220368494A1 (en) Uplink re-transmission with compact memory usage
WO2021023044A1 (zh) 一种通信方法和装置
CN108809540B (zh) 数据处理方法及设备
WO2022150937A1 (zh) 用于接收数据的方法与装置和用于发送数据的方法与装置
CN118042518A (zh) 一种通信方法和装置
WO2024001831A1 (zh) 通信方法、终端设备、网络设备及通信系统
WO2022223031A1 (zh) 一种数据传输的通信处理方法和相关设备
US20210298123A1 (en) Wireless communication system, transmission and reception method, recording medium, wireless communication base station device, control circuit, and control method
CN108886766B (zh) 一种控制信息的传输方法及装置
US20230308221A1 (en) Mrb architecture with pdcp retransmission
CN117375775A (zh) 通信方法、终端设备、网络设备及通信系统
CN113596915A (zh) 一种通信方法及装置
WO2024060985A1 (zh) 一种通信方法、网络设备和终端设备
CN113810949A (zh) 数据传输方法和装置
WO2024067467A1 (zh) 通信方法及装置
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置
WO2023216986A1 (zh) 缓存状态报告bsr指示方法和装置
WO2023098464A1 (zh) 数据传输的方法和装置
WO2024067374A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23830011

Country of ref document: EP

Kind code of ref document: A1