CN117375775A - Communication method, terminal device, network device and communication system - Google Patents
Communication method, terminal device, network device and communication system Download PDFInfo
- Publication number
- CN117375775A CN117375775A CN202210872898.6A CN202210872898A CN117375775A CN 117375775 A CN117375775 A CN 117375775A CN 202210872898 A CN202210872898 A CN 202210872898A CN 117375775 A CN117375775 A CN 117375775A
- Authority
- CN
- China
- Prior art keywords
- pdu
- pdu set
- indication information
- terminal device
- network device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 174
- 238000004891 communication Methods 0.000 title claims abstract description 104
- 239000000872 buffer Substances 0.000 claims description 63
- 230000005540 biological transmission Effects 0.000 claims description 37
- 238000001514 detection method Methods 0.000 claims description 32
- 230000015654 memory Effects 0.000 claims description 26
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 claims description 15
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 15
- 230000003139 buffering effect Effects 0.000 claims description 5
- 230000006978 adaptation Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 40
- 230000006870 function Effects 0.000 description 36
- 230000008569 process Effects 0.000 description 19
- 230000011664 signaling Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 12
- 239000002699 waste material Substances 0.000 description 10
- 230000001419 dependent effect Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 9
- 238000013461 design Methods 0.000 description 7
- 230000001960 triggered effect Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 4
- 230000000737 periodic effect Effects 0.000 description 4
- 208000033748 Device issues Diseases 0.000 description 3
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 3
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 3
- 230000003190 augmentative effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
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/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
-
- 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
- H04L1/188—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application provides a communication method, terminal equipment, network equipment and a communication system. The method comprises the following steps: the terminal equipment reports first indication information to the network equipment, the first indication information indicates a second PDU set which is already transmitted and referred by a first protocol data unit group PDUs to be transmitted, and whether the second PDU set is successfully uploaded is determined according to at least one of the overtime condition of a timer of the terminal equipment and the feedback condition of the network equipment on the first indication information. And indicating the second PDU set referred by the first PDU set to be transmitted through reporting the indication information, and after the indication information is transmitted, the terminal equipment acquires whether the second PDU set is successfully uploaded according to the overtime condition of a timer and/or the feedback condition of the network equipment on the first indication information so as to facilitate the terminal equipment to determine to upload or discard the first PDU set.
Description
The present application claims priority from the chinese patent application filed at 2022, month 06 and 27, filed with the national intellectual property agency, application number 202210745443.8, entitled "a data transmission method, terminal device, network device", the entire contents of which are incorporated herein by reference.
Technical Field
The embodiment of the application relates to the field of communication, in particular to a communication method, terminal equipment, network equipment and a communication system.
Background
The uplink scheduling of the network device to the terminal device is based on a scheduling request (scheduling request, SR) and a buffer status report (buffer status report, BSR) sent by the terminal device. The network device can learn that the terminal device has uplink data to be transmitted based on the SR, and can learn the data amount cached in the cache of the terminal device based on the BSR.
Disclosure of Invention
After receiving the uplink scheduling request, the network device schedules uplink data through downlink control information (downlink control information, DCI). And after receiving the scheduling DCI, the terminal equipment uploads uplink data on the appointed time-frequency resource. The network device does not immediately reply to an Acknowledgement (ACK) or a negative acknowledgement (negative acknowledgment, NACK) by the HARQ of the MAC layer after receiving the uplink data, indicating whether the uplink data is successfully received. Therefore, the terminal device cannot immediately determine whether the uplink data is successfully uploaded, so that the terminal device cannot determine the processing mode of the data related to the uplink data, and the uplink resource is not fully utilized, so that the waste of the uplink resource is caused. For example, on the premise that the network device does not instruct the terminal device to retransmit the uplink data #1, the terminal device defaults to successful uploading of the uplink data #1. In practice, the uplink data #1 is not uploaded successfully, and the number of retransmissions of the uplink data #1 reaches the upper limit, so that the network device does not instruct to retransmit the uplink data #1. And the terminal device defaults to successful upload of the uplink data #1, so that the terminal device can continue uploading the uplink data #2 related to the uplink data #1 (e.g., decoding of the uplink data #2 needs to depend on the uplink data # 1). In this case, the terminal device uploads the uplink data #2, which may result in waste of uplink resources.
In order to solve the technical problems, the application provides a communication method, so that a terminal device can determine whether uplink data uploading is successful or not, and waste of uplink resources caused by uploading data under the condition that the data uploading is not needed is avoided.
In a first aspect, a method of communication is provided. The method may be performed by the terminal device or may be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited in this application. For convenience of description, an example of the terminal device execution will be described below.
The communication method comprises the following steps: the terminal device reports first indication information to the network device, wherein the first indication information indicates a second PDU set referenced (also called as dependent) by the first protocol data unit group (Protocol Data Unit set, PDU set); the terminal equipment determines whether the second PDU set is successfully uploaded according to at least one of the overtime condition of the timer of the terminal equipment and the feedback condition of the network equipment to the first indication information. The first PDU set includes a PDU set to be sent by the terminal device, the second PDU set includes a PDU set that has been sent by the terminal device, and the first PDU set refers to a second PDU set representation: successful decoding of the first PDU set is premised on successful decoding of the second PDU set.
Based on the above technical solution, the terminal device reports the indication information indicating the second PDU set that has been transmitted and referred to by the first PDU set to be transmitted, and after the first indication information is transmitted, determines whether the second PDU set is successfully uploaded according to at least one of the timeout condition of the started timer (such as the timing duration, whether the timer is overtime, etc.) and the feedback condition of the network device on the received first indication information (such as issuing the information in response to the first indication information). That is to say, through this technical solution, the terminal device can determine whether the second PDU set is successfully uploaded.
In addition, in the technical solution, the terminal device may determine the processing of the first PDU set according to the result of determining whether the second PDU set is successfully uploaded. For example, the second PDU set is not successfully uploaded, nor is the terminal device determining that the first PDU set is to be uploaded. Since successful decoding of the first PDU set is premised on successful decoding of the second PDU set, in case the second PDU set is not successfully uploaded, even if the first PDU set is uploaded, it cannot be decoded correctly. Therefore, the first PDU set does not need to be uploaded, so that the terminal equipment can determine the processing mode of the first PDU set according to the judging result, and the waste of uplink resources caused by uploading the first PDU set under the condition that the first PDU set does not need to be uploaded is avoided.
In certain implementations of the first aspect, the first indication information includes a medium access control layer control element (media access control control element, MAC CE) including a logical channel identification LCID and an identification of the second PDU set. Wherein, the LCID indicates a logical channel corresponding to the MAC CE, and the logical channel is used for transmitting the identifier of the second PDU set referenced by the first PDU set.
Based on the above technical solution, the signaling format of the first indication information reported by the terminal device may be a MAC CE, and the signaling format already defined in the existing protocol (for example, the format of the MAC CE defined in 3gpp TS 38.321) is used, so that the function of implementing the first indication information by newly defining the signaling format is avoided, and the solution is simplified.
In certain implementations of the first aspect, in a case where it is determined that the second PDU set was not successfully uploaded, the method further includes: the terminal device discards the first PDU set.
Based on the above technical solution, when determining that the second PDU set is not successfully uploaded, the terminal device can determine that the first PDU set cannot be correctly parsed even if the first PDU set is uploaded, so that the first PDU set does not need to be uploaded. Further, to save buffer space, the first PDU set may be discarded or deleted from the buffer.
In certain implementations of the first aspect, the terminal device discards the first PDU set, including: after the first timer expires or when the first timer expires, if the buffer of the terminal device has the first PDU set buffered therein, discarding the first PDU set in the buffer. 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 time (also referred to as a time point) when the last bit of the last PDU of the first PDU set is received by a packet data convergence layer protocol (packet data convergence protocol, PDCP) entity of the terminal device, and the timing duration of the first timer is less than a frame arrival period, wherein the frame arrival period indicates the interval between two adjacent frames arriving at the buffer. Wherein the PDCP entity of the terminal device may be understood as a transport entity (also referred to as transmitting PDCP entity) of the PDCP layer of the terminal device.
In certain implementations of the first aspect, after expiration of the first timer (wherein expiration may also be referred to as timeout) or when expiration of the first timer (may also be referred to as time point), the buffer of the terminal device has the first PDU set buffered therein, indicating that the second PDU set was not successfully uploaded.
In certain implementations of the first aspect, in a case where the second PDU set is determined to be successfully uploaded, the method further includes: the terminal equipment discards partial PDU in the first PDU set; alternatively, the terminal device transmits the first PDU set.
Based on the above technical solution, when the terminal device determines that the second PDU set is successfully uploaded, the terminal device can indirectly learn that the PDU included in the first PDU set can be uploaded, but the specific uploading condition needs to be scheduled according to the network device. For example, the network device may only successfully schedule 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, in case the terminal device determines that the second PDU set is successfully uploaded, the subsequent processing of the first PDU set may be a partial successful transmission or a complete successful transmission.
In certain implementations of the first aspect, the terminal device discards a portion of the PDUs in the first PDU set, including: and within the timeout of the first timer, if part of the PDUs in the first PDU set are cached in the cache of the terminal equipment, discarding part of the PDUs in the first PDU set in the cache. 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 the time when the PDCP entity of the terminal device receives the last bit of the last PDU of the first PDU set.
In certain implementations of the first aspect, the buffering of the terminal device includes a buffering of a radio link control (radio link control, RLC) layer of the terminal device or a buffering of a packet data convergence layer protocol (packet data convergence protocol, PDCP) layer of the terminal device. Wherein, when the buffer of the terminal device is the buffer of the RLC layer, the PDCP layer of the terminal device notifies the RLC layer of discarding the PDU set and/or the PDU in the buffer of the RLC layer by the notification message after or when the first timer expires.
Based on the technical scheme, the buffer memory of the terminal equipment can be buffer memories of different protocol layers, so that the flexibility of the scheme is improved.
In certain implementations of the first aspect, the determining, by the terminal device, that the second PDU set is not successfully uploaded according to a feedback condition of the network device on the first indication information includes: the terminal device receives second indication information from the network device, where the second indication information is used to indicate that the second PDU set is not successfully uploaded.
In certain implementations of the first aspect, the second indication information is configured to indicate that the second PDU set was not successfully uploaded, including: the second indication information indicates that part or all of the PDUs included in the second PDU set are not 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.
In certain implementations of the first aspect, the determining, by the terminal device, that the second PDU set was not successfully uploaded according to a timeout condition of a timer of the terminal device includes: and when the terminal equipment sends the first indication information, starting a second timer, and if the second timer is overtime and the terminal equipment does not receive the scheduling information from the network equipment, determining that the second PDU set is not successfully uploaded by the terminal equipment.
In certain implementations of the first aspect, before the terminal device sends the first indication information, the method further includes: the terminal device transmits a second PDU set to the network device, the second PDU set including third indication information for the network device to determine whether all PDUs of the second PDU set are successfully received or a specified number of PDUs is reached.
In certain implementations of the first aspect, the third indication information includes at least one of: the second PDU set includes the identity of the first and last PDUs; alternatively, the second PDU set includes the total number of PDUs; or, the second PDU set successfully decodes the number of PDUs that need to be successfully transmitted; alternatively, the second PDU set successfully decodes the ratio of the number of PDUs required to be successfully transmitted to the total number of PDUs included in the second PDU set; or, the identification of the PDU contained in the second PDU set belonging to the second PDU set; or, the sequence number of the PDU contained in the second PDU set.
In certain implementations of the first aspect, the method further comprises: the protocol layer entity of the terminal equipment performs header detection on the first PDU set (after) or when receiving the first PDU set generated by the application layer of the terminal equipment, and determines the identification of the first PDU set and the identification of at least one PDU set referenced by the first PDU set. The protocol layer of the terminal device encapsulates the identity of the first PDU set and the identity of the at least one PDU set in a header of the protocol layer of the first PDU set. Wherein the first PDU set generated by the application layer comprises an identity of the first PDU set and an identity referring to at least one PDU set, specifically, the first PDU of the first PDU set or each PDU comprises an identity of the first PDU set and an identity referring to at least one PDU set, and the second PDU set is one of the at least one PDU set.
Based on the above technical solution, the terminal device can obtain the identity of a certain PDU set and the identity of another PDU set referred to by the PDU set through header detection, so that the terminal device can obtain the reference relationship between different PDU sets.
In certain implementations of the first aspect, the protocol layer includes at least one of: a service data adaptation (service data adaptation protocol, SDAP) layer, PDCP layer, non-Access Stratum (NAS) or radio resource control (radio resource control, RRC) layer.
In a second aspect, a communication method is provided. The method may be performed by a network device, or may be performed by a component (e.g., a chip or a circuit) of a network device, which is not limited in this application. For convenience of description, an example of the network device execution will be described below.
The communication method comprises the following steps: the network device receives first indication information from the terminal device, wherein the first indication information is used for indicating a second PDU set referenced by the first protocol data unit group PDU set. In case the network device determines that the PDUs required for successful decoding of the second PDU set are not all successfully received, the network device determines not to schedule the first PDU set. The first PDU set includes a PDU set to be sent by the terminal device, the second PDU set includes a PDU set referenced by the first PDU set sent by the terminal device, and the first PDU set refers to a second PDU set representation: successful decoding of the first PDU set is premised on successful decoding of the second PDU set. The description of the first indication information may refer to the description of the first indication information in the first aspect, which is not repeated herein.
In certain implementations of the second aspect, the network device schedules the first PDU set in case the network device determines that the second PDU set was successfully received.
In certain implementations of the second aspect, the network device determining that all PDUs required for successful decoding of the second PDU set were not successfully received includes: the network device determines that the network device does not hold the identity of the second PDU set.
In certain implementations of the second aspect, the method further comprises: the network device receives a second PDU set from the terminal device, the second PDU set including the third indication information. The network device determines whether to save the identity of the second PDU set according to the three indication information. The description of the third indication information may refer to the description of the third indication information in the first aspect, which is not described herein.
In certain implementations of the second aspect, after the network device determines not to schedule the first PDU set, the method further includes: the network device sends second indication information to the terminal device, where the second indication information is used to indicate that the network device does not successfully receive all PDUs required for successfully decoding the second PDU set.
In certain implementations of the second aspect, before the network device sends the second indication information to the terminal device, the method further includes: the network device determines that the timing of the first timer is longer 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 time when the PDCP entity of the terminal device receives the first PDU set, and the frame arrival period indicates the interval of two adjacent frames arriving at the buffer of the terminal device.
In certain implementations of the second aspect, the second indication information for indicating that the network device did not successfully receive all PDUs required for successful decoding of the second PDU set includes: the second indication information includes an identification of at least one PDU set, indicating that the at least one PDU set was not successfully uploaded, the second PDU set being one of the at least one PDU set.
The technical effects of the method shown in the above second aspect and its possible designs can be referred to the technical effects in the first aspect and its possible designs.
In a third aspect, a communication method is provided. The method may be performed by a network device, or may be performed by a component (e.g., a chip or a circuit) of a network device, which is not limited in this application. For convenience of description, an example of the network device execution will be described below.
The communication method comprises the following steps: the network equipment determines that a first condition is met; the network device sends fourth indication information to the terminal device, wherein the fourth indication information is used for indicating the successfully received PDU and/or the unsuccessfully received PDU of the network device. The first condition includes at least one of: on the premise that the fourth indication information is sent periodically, the time when the fourth indication information is sent is reached, the network equipment determines whether the third PDU set is successfully received or not, or the network equipment receives trigger information from the terminal equipment. The triggering information is used for triggering the network equipment to determine fourth indication information.
Based on the above technical solution, the network device may notify the terminal device of the successfully received PDU and/or the unsuccessfully received PDU through the fourth indication information under the condition that the first condition is satisfied, so that the terminal device determines whether the uplink data is uploaded successfully.
In certain implementations of the third aspect, the network device determining whether the third PDU set was successfully received includes: the network device determines whether all the PDUs included in the third PDU set are successfully received and/or whether the number of PDUs successfully received by the network device exceeds a first threshold, where the received PDUs successfully received by the network device are PDUs included in the third PDU set. Wherein the first threshold is predefined.
In certain implementations of the third aspect, in the case where the first condition is that the network device determines whether the third PDU set was successfully received, the method further includes: the network device receives a third PDU set from the terminal device, the third PDU set including 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.
Based on the above technical solution, when the terminal device sends the uplink third PDU set, the fifth indication information may be carried in the third PDU set, so that the network device determines whether to successfully receive all PDUs included in the third PDU set according to the fifth indication information.
In certain implementations of the third aspect, the five-indicator information includes at least one of: the third PDU set includes the identity of the first and last PDUs; alternatively, the third PDU set includes the total number of PDUs; alternatively, the third PDU set successfully decodes the number of PDUs that need to be successfully transmitted; or the ratio of the number of successfully transmitted PDUs required for successful decoding of the third PDU set and the total number of PDUs included in the third PDU set; or the identification of the PDU contained in the third PDU set belonging to the third PDU set; or the sequence number of the PDU contained in the third PDU set.
In certain implementations of the third aspect, the network device determining, according to the fifth indication information, whether all PDUs included in the third PDU set are successfully received, includes: the network equipment determines that part of PDUs in the third PDU set are received according to the fifth indication information, and all PDUs included in the third PDU set are not successfully received; the method further comprises the steps of: the network device deletes or discards a portion of the PDUs in the third PDU set.
Based on the above technical solution, in the case that the network device determines that all the PDUs included in the third PDU set are not successfully received, but receives the partial PDU included in the third PDU set, the network device may discard the received partial PDU.
In a fourth aspect, a communication method is provided. The method may be performed by the terminal device or may be performed by a component (e.g., a chip or a circuit) of the terminal device, which is not limited in this application. For convenience of description, an example of the terminal device execution will be described below.
The communication method comprises the following steps: the terminal device receives fourth indication information from the network device, where the fourth indication information is used to indicate the successfully received PDU and/or the unsuccessfully received PDU by the network device. And under the condition that the fourth indication information is used for indicating the PDU which is not successfully received by the network equipment, the terminal equipment determines to delete the first PDU according to the PDU which is not successfully received. The unsuccessfully received PDU is a PDU in the third PDU set, the first PDU comprising at least one of: the fourth PDU set includes a PDU, an undelivered PDU in the third PDU set, or a PDU included in the fifth PDU set. The fourth PDU set is a PDU set referring to the third PDU set, the fifth PDU set is a PDU set referring to the third PDU set and/or the fourth PDU set, and the fourth PDU set refers to the third PDU set and indicates: successful decoding of the fourth PDU set is premised on successful decoding of the third PDU set, the fifth PDU set being represented with reference to the third PDU set and/or the fourth PDU sett: the successful decoding of the fifth PDU set is premised on the successful decoding of the third PDU set and/or the fourth PDU set.
Based on the above technical solution, the terminal device may 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. Therefore, the PDU set of the reference PDU set #1 is determined to be unnecessary to upload by the terminal equipment, or other PDUs in the PDU set #1 are unnecessary to upload, so that the terminal equipment discards the PDU set or the PDU which is unnecessary to upload, and the buffer and uplink resources of the terminal equipment are saved.
In certain implementations of the fourth aspect, before the terminal device receives the third indication information from the network device, the method further includes: the terminal device sends a third PDU set to the network device, wherein the third PDU set includes fifth indication information, and the fifth indication information is provided for the network device so as to be used as a basis for the network device to determine whether the third PDU set is successfully received. The description of the fifth instruction information may refer to the description of the fifth instruction information in the third aspect, which is not described herein.
In certain implementations of the fourth aspect, the method further comprises: before or while the third PDU set is buffered in the buffer, the terminal device performs header detection on the third PDU set generated by the application layer, and determines the identity of the third PDU set and the identity of at least one PDU set referenced by the third PDU set. The terminal device encapsulates the identity of the third PDU set and the identity of the at least one PDU set in a header of a protocol layer of the third PDU set. Wherein the third PDU set generated by the application layer includes an identification of the third PDU set and an identification of at least one PDU set. Specifically, the first PDU of the third PDU set or each PDU comprises an identification of the third PDU set and an identification of the at least one PDU set, the successful decoding of the third PDU set being premised on the successful decoding of the at least one PDU set.
Based on the above technical solution, the terminal device can obtain the identity of a certain PDU set and the identity of another PDU set referred to by the PDU set through header detection, so that the terminal device can obtain the reference relationship between different PDU sets.
In a fifth aspect, a terminal device is provided. The terminal device is configured to perform the method provided in the first aspect and any implementation manner thereof, and the fourth aspect and any implementation manner thereof. Specifically, the terminal device includes a processor and a memory for storing a computer program; the processor is configured to invoke and run the computer program from the memory, so that the terminal device performs the method provided in the first aspect and any implementation manner thereof, or in the fourth aspect and any implementation manner thereof.
In a sixth aspect, a network device is provided. The network device is configured to perform the method provided in the second or third aspect above. In particular, the network device comprises a processor and a memory for storing a computer program; the processor is configured to invoke and run the computer program from the memory, to cause the network device to perform the method provided by the second aspect and any of its embodiments or the third aspect and any of its embodiments described above.
In a seventh aspect, a communication device is provided. The communication device is configured to perform the method provided in the first aspect and any implementation manner or in the fourth aspect and any implementation manner thereof. In particular, the communication device may comprise means and/or modules (e.g. a processing unit, a transceiver unit) for performing the method provided in the first aspect and any of its embodiments or in the fourth aspect and any of its embodiments.
In one implementation, the communication device is a terminal device. When 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.
In another implementation, the communication device may be a chip, a system-on-chip or a circuit in the terminal device. At this time, the transceiver unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, a related circuit, or the like on the chip, the chip system, or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
In an eighth aspect, a communication device is provided. The communication device is configured to perform the method provided by the second aspect and any of its embodiments or the third aspect and any of its embodiments. In particular, the communication device may comprise means and/or modules, such as a processing unit and a transceiver unit, for performing the method provided by the second aspect and any of its embodiments or the third aspect and any of its embodiments.
In one implementation, the communication apparatus is a network device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.
In another implementation, when the communication device is a chip, a system-on-chip or a circuit in the network device, the transceiver unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
In a ninth aspect, the present application provides a processor configured to perform the method provided in the above aspects.
The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited in this application.
In a tenth aspect, a computer readable storage medium is provided. The computer readable storage medium stores a computer program which, when run on a communication device, causes the communication device to perform the method of any one of the implementations of the first to fourth aspects described above.
In an eleventh aspect, a computer program product comprising instructions is provided. The computer program product, when run on a computer, causes the computer to perform the method provided by any one of the implementations of the first to fourth aspects described above.
In a twelfth aspect, a chip is provided, the chip includes a processor and a communication interface, the processor reads instructions stored on a memory through the communication interface, and performs the method provided in any implementation manner of the first aspect to the fourth aspect.
Optionally, as an implementation manner, the chip further includes a memory, where the memory stores a computer program or an instruction, and the processor is configured to execute the computer program or the instruction stored on the memory, where the processor is configured to execute the method provided in any implementation manner of the first aspect to the fourth aspect.
A thirteenth aspect provides a communication system comprising the terminal device of the fifth aspect and the network device of the sixth aspect.
Drawings
Fig. 1 is a schematic diagram of a communication system to which the present application is applicable.
Fig. 2 is a schematic diagram of a protocol layer structure between a network device and a terminal device.
Fig. 3 is a schematic flow chart of a communication method provided in the present application.
Fig. 4 (a) to (d) are schematic diagrams of determining whether to successfully upload the second PDU set by the terminal device according to the embodiment of the present application.
Fig. 5 is a schematic flow chart of another communication method provided herein.
Fig. 6 is a schematic diagram of a communication device provided in the present application.
Fig. 7 is a schematic structural diagram of a terminal device of the present application.
Fig. 8 is a schematic diagram of another communication device provided herein.
Fig. 9 is a schematic structural diagram of a network device of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be specifically described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems. For example: a fifth generation (5th generation,5G) system or New Radio (NR), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system.
The technical solutions of the embodiments of the present application may also be applied to device-to-device (D2D) communication, vehicle-to-device (V2X) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and internet of things (internet of things, ioT) communication systems or other communication systems.
To facilitate an understanding of the embodiments of the present application, a communication system to which the present application is applicable is exemplarily first described with reference to fig. 1. The terminal device (terminal equipment) in the embodiment of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a relay station, a remote terminal, a mobile device, a user terminal (UE), a terminal (terminal), a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (public land mobile network, PLMN) or a terminal device in a future internet of vehicles, etc., as the embodiments of the application are not limited in this regard.
For example, in the embodiment of the present application, the wearable device may also be referred to as a wearable smart device, which is a generic term for applying wearable technology to intelligently design daily wear and develop wearable devices. Such as glasses, gloves, watches, apparel, shoes, etc. The wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device comprises full functions, and can realize complete or partial functions independent of the intelligent mobile phone. For example: smart watches or smart glasses, etc. In addition, the portable device can be a portable device which only focuses on certain application functions and needs to be matched with other devices such as a smart phone. Such as various intelligent bracelets, intelligent jewelry, etc. for physical sign monitoring.
Furthermore, in the embodiments of the present application, the terminal device may also be a terminal device in an IoT system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. In the embodiment of the application, the IoT technology can achieve mass connection, deep coverage and terminal power saving through, for example, a Narrowband (NB) technology.
In addition, in the embodiment of the present application, the terminal device may further include a sensor, and the main functions include collecting data (part of the terminal device), receiving control information of the network device and downlink data, and transmitting electromagnetic waves to the network device to transmit uplink data.
The network device in the embodiment of the present application may be any communication device having a wireless transceiver function for communicating with a terminal device. The apparatus includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a home evolved Node B, heNB, or home Node B, HNB, a baseBand unit (BBU), an Access Point (AP), a radio relay Node, a radio backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP) in a wireless fidelity (wireless fidelity, WIFI) system, or the like, may also be a gNB in a 5G system, such as an NR system, or a transmission point (TRP or TP), one or a set of antenna panels (including a plurality of antenna panels) of a base station in a 5G system, or may also be a network Node constituting a gNB or a transmission point, such as a baseBand unit (BBU), or a Distributed Unit (DU), or the like.
Network devices and terminal devices may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. In the embodiment of the application, the scene where the network device and the terminal device are located is not limited.
In the embodiment of the application, the terminal device or the network device includes a hardware layer, an operating system layer running above the hardware layer, and an application layer running above the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes via processes, e.g.,operating system>Operating system>Operating system>Operating systems orAn operating system, etc. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like.
Furthermore, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape, etc.), optical disks (e.g., compact Disk (CD), digital versatile disk (digital versatile disc, DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable storage medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
To facilitate understanding of the embodiments of the present application, a communication system suitable for the embodiments of the present application will be described in detail first with reference to the communication system shown in fig. 1 as an example. As shown in fig. 1, the communication system 100 may include at least one network device 101 and at least one terminal device 102 to 107. Wherein the terminal devices 102 to 107 may be mobile or stationary. One or more of network device 101 and terminal devices 102-107 may each communicate over a wireless link. Each network device may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.
Alternatively, the terminal devices may communicate directly with each other. Direct communication between terminal devices may be implemented, for example, using device-to-device (D2D) technology or the like. As shown in fig. 1, communication may be directly performed between the terminal devices 105 and 106, and between the terminal devices 105 and 107 using D2D technology. Terminal device 106 and terminal device 107 may communicate with terminal device 105 separately or simultaneously.
Terminal devices 105 to 107 may also communicate with network device 101, respectively. For example, may communicate directly with network device 101 as terminal devices 105 and 106 in the figure may communicate directly with network device 101. Or indirectly with the network device 101, such as the terminal device 107 in fig. 1 via the terminal device 105 with the network device 101.
Each communication device may be configured with multiple antennas. For each communication device in communication system 100, the plurality of antennas configured may include at least one transmit antenna for transmitting signals and at least one receive antenna for receiving signals. Thus, communication may be performed between communication devices in communication system 100 via multiple antenna techniques.
The interface between the network device and the terminal device may be a Uu interface (or referred to as a null interface). Of course, in future communications, the names of these interfaces may be unchanged or may be replaced with other names, which are not limited in this application. The communication between the network device and the terminal device follows a certain protocol layer structure, and the network layering is to send, forward, package or unpack data of the network node (such as the network device and the terminal device), load or unpack control information, and the like, which are respectively finished by different hardware and software modules. This makes it possible to simplify the complex problem of communication and interconnection of networks. For ease of understanding, 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.
As can be seen from fig. 2, the network hierarchy of the network device and the terminal device comprises: an application layer, an RRC layer, an SDAP layer, a PDCP layer, an RLC layer and a MAC layer. The application layer mainly functions to provide a plurality of services for application software, such as file servers, database services, e-mails and other network software services; the RRC layer implementing functions include establishing, maintaining, and releasing an RRC connection, allocating or reconfiguring radio resources for the RRC connection; one of the functions of the SDAP layer is to map between a quality of service (Quality of Service) stream and a Data Radio Bearer (DRB); the PDCP layer is responsible for compressing and decompressing IP headers, maintaining PDCP layer sequence numbers, ciphering and deciphering, and so on; the RLC layer mainly provides a radio link control function and provides services such as segmentation, retransmission control and transmission on demand for an upper layer; the function of the MAC layer includes mapping between logical channels and transport channels, selecting the appropriate transport format for each transport channel.
It should be noted that, in the embodiment of the present application, the network hierarchy of the terminal device and the network device is not limited, and fig. 2 is only an example, and the protection scope of the present application is not limited in any way.
It should be appreciated that fig. 1 is a simplified schematic diagram that is merely exemplary for ease of understanding, and that other network devices may also be included in communication system 100 or other terminal devices (not shown in fig. 1) may also be included. For example, the communication system 100 may also include a core network device. The access network equipment provides wireless access connection for the terminal equipment on one hand, and can send data to the terminal equipment or receive the data sent by the terminal equipment; on the other hand, the access network device and the core network device are also connected, and can forward the data received from the terminal device to the core network or receive the data required to be sent to the terminal device from the core network.
To facilitate an understanding of the embodiments of the present application, some basic concepts that are referred to herein are briefly described. It should be understood that the basic concepts described below are described by taking as an example the basic concepts specified in the NR protocol, but the embodiments of the present application are not limited to be applied to NR systems only. Therefore, the standard names appearing when describing the NR system as an example are all functional descriptions, and specific names are not limited, and only indicate functions of the device, and can be correspondingly extended to other systems in the future.
1. Augmented Reality (XR): including Virtual Reality (VR), augmented Reality (Augmented Reality, AR), and Mixed Reality (MR), etc., are among the most attractive applications for future 5G networks. XR applications provide a virtual immersion world for users by providing audio and video signals. Among them, the transmission of video frames is classified into I-frame (I-frame) transmission and P-frame (P-frames) transmission.
2. I-frame and P-frame: i-frames, which may be referred to as intra-coded frames, are independent frames with their own full information that can be decoded independently without reference to other pictures. A P frame, which may be referred to as a predictive coded frame, is predicted from a P frame or an I frame preceding it when coding for a continuous moving picture, and compares difference information or data with the P frame or the I frame preceding it, i.e., performs inter-frame compression in consideration of the characteristics of motion.
3. Protocol data unit (Protocol Data Unit, PDU): a specific data frame format is that in a layered network structure, a PDU is to be built up at each layer of the transmission system, which contains information from the upper layer and entity-attached information of the current layer, which is to be transferred to the next lower layer.
4. Protocol data unit set (Protocol Data Unit set, PDU set): a PDU set consists of one or more PDUs, which is a unit of information generated by the application layer, which may refer to a frame or slice in the XR media service.
In some applications, the application layer needs to receive all PDUs within one PDU set to use the one unit of information. In other applications, the application layer only needs to receive a portion of one PDU set to recover some or all of the unit information.
At the application layer, all PDUs within one PDU set are handled as one whole. For example, a frame within a group of pictures (group of pictures, goP) can only be decoded normally after all frames it depends on are received and decoded. If such dependency between PDU sets is not considered, the random dropped packet of 5GS may affect normal decoding of the subsequently transmitted packet, resulting in transmission of invalid packets and wireless waste.
5. PDU set sequence number (PDU set sequence number, PS-SN) and reference PDU set sequence number (reference PDU set sequence number, RPS-SN): to indicate the reference (or dependency) relationship between PDU sets, PDU sets may carry two sequence numbers: PS-SN and RPS-SN. If the reference PDU set is not successfully transmitted, the subsequent PDU set depending on the reference PDU set may not be transmitted to save radio resources.
For convenience of description, the referenced PDU set may be referred to as a reference PDU set, and the PDU set referring to the reference PDU set is referred to as a dependent PDU set.
6. New data indication (new data indicator, NDI) field and hybrid automatic request retransmission (hybrid automatic repeat request, HARQ) process number: the NDI field of 1bit and HARQ process number of 4bits in DCI (e.g., DCI format 0_0,0_1 or 0_2) for scheduling uplink data are used to indicate whether a network device is scheduling retransmission data or scheduling new transmission data.
NDI in combination HARQ process number is used to indicate whether the uploaded data is a new transmission or a retransmission. For the same HARQ process number, if the NDI indication value is the same as the previous scheduling, the current scheduling is a retransmission of the previous scheduling data, and if the NDI indication value is different from the previous scheduling (0, 1, or vice versa), the current scheduling is a new transmission. After receiving the new transmission of the NDI instruction, the terminal equipment utilizes the data which is not transmitted to refresh the buffer of the associated HARQ process; if the NDI instruction retransmission is received, the data in the buffer corresponding to the HARQ process is re-uploaded.
7. And (5) uplink scheduling: and the network equipment schedules the uplink data of the terminal equipment based on the SR and BSR signaling sent by the terminal equipment. The SR is physical layer signaling, and the terminal device uploads the SR to the network device, and may use a proprietary and periodic physical layer uplink control channel (physical uplink control channel, PUCCH) channel. After receiving the SR signal sent by the terminal device, the network device knows that the terminal device has uplink data to be transmitted, and can allocate uplink resources for the terminal device. However, with the SR signal, the network device cannot determine how much data the terminal device has to transmit, and cannot determine how much uplink resources should be allocated to the terminal device. Therefore, the subsequent terminal device still needs to send BSR signals to the network device to report how much data is buffered in the buffer at the terminal device side, so as to apply for uplink resources.
After receiving the uplink scheduling request, the network device uses DCI (e.g., DCI format 0_0,0_1 or 0_2) to schedule the uplink data. And the terminal equipment uploads data in the appointed time-frequency resource block after receiving the scheduling DCI. After receiving the uploaded data, the network device is different from the downlink transmission, and does not feed back an ACK/NACK signal to the terminal device. If the uploading of a certain data is unsuccessful, the network device decides whether to retransmit the data. The network device directly sends DCI for scheduling retransmission signals to the terminal device to schedule data needing to be retransmitted; if the unsuccessfully uploaded data does not need to be retransmitted, the network equipment directly schedules the newly uploaded data, and does not schedule the unsuccessfully uploaded data.
8. Unacknowledged mode (unacknowledgement mode, UM): in WCDMA systems, the RLC layer is located above the MAC layer, as part of L2, and provides segmentation and retransmission services for users and control data. Each RLC entity is configured by RRC and there are three modes depending on the type of service: transparent Mode (TM), unacknowledged Mode (UM), acknowledged mode (acknowledged mode, AM). Wherein, non-acknowledged mode: the transmitting entity adds the necessary control protocol overhead on the higher layer PDUs and then transmits but does not guarantee delivery to the peer entity and does not use the retransmission protocol. The receiving entity marks the received error data as an error and submits the error data, or the error data is directly discarded and reported to a high layer. Since RLC PDUs contain sequence numbers, the integrity of higher layer PDUs can be checked.
In addition, in order to facilitate understanding of the embodiments of the present application, the following description is made.
First, in this application, "for indicating" may include for direct indication and for indirect indication. When describing that certain indication information is used for indicating a, the indication information may be included to directly indicate a or indirectly indicate a, and does not necessarily indicate that a is included in the indication information.
The information indicated by the indication information is called information to be indicated, and in a specific implementation process, various ways for indicating the information to be indicated exist. The information to be indicated can be sent together as a whole or can be divided into a plurality of pieces of sub-information to be sent separately, and the sending periods and/or sending occasions of the sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and/or the transmission timing of the sub-information may be predefined, for example, predefined according to a protocol, or may be configured by the transmitting end device by transmitting configuration information to the receiving end 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. Wherein radio resource control signaling such as packet RRC signaling; the MAC layer signaling includes, for example, a MAC Control Element (CE); the physical layer signaling includes, for example, DCI.
Second, the term "at least one" as used herein means one or more, and the term "plurality" means two or more. In addition, in the embodiments of the present application, "first", "second", and various numerical numbers (e.g., "#1", "#2", etc.) are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. The following sequence numbers of the processes do not mean the order of execution, which should be determined by its functions and internal logic, but should not constitute any limitation on the implementation process of the embodiments of the present application, and it should be understood that the objects thus described may be interchanged where appropriate so as to be able to describe schemes other than the embodiments of the present application. Moreover, in the embodiments of the present application, the words "510", "610", "810" and the like are merely identifiers made for descriptive convenience and do not limit the order in which the steps are performed.
Third, in this application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
Fourth, references to "save" in embodiments of the present 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, processor, or communication device. The one or more memories may also be provided separately in part, and integrated in the decoder, processor, or communication device. The type of memory may be any form of storage medium, and this application is not limited in this regard.
Fifth, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in this application.
Sixth, in the embodiment of the present application, the control channels may include PDCCH, enhanced physical downlink control channel (enhanced physical downlink control channel, EPDCCH), and other physical layer control channels, but for convenience of description, the following terms or concepts are described by taking PDCCH as an example only, but the embodiment of the present application is not limited thereto.
It should be understood that, in the embodiment of the present application, the downlink control channel is taken as an example of the physical downlink control channel PDCCH, but the embodiment of the present application is not limited to this, and in fact, the downlink control channel may be defined as other terms or concepts, which all apply to the technical solutions of the embodiments of the present application. In the embodiment of the present application, the downlink control channel and the PDCCH may be used alternately, and the PDCCH may be considered as an example description of the uplink control channel.
Seventh, in the embodiment of the present application, terms and english abbreviations, such as Downlink Control Information (DCI), medium access control element (MAC-CE), radio Resource Control (RRC), etc., are given as exemplary examples for convenience of description, and should not be construed as limiting the present application in any way. This application does not exclude the possibility of defining other terms in existing or future protocols that perform the same or similar functions.
Eighth, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
The scenario in which the communication method provided by the embodiment of the present application can be applied is briefly described above in connection with fig. 1, and basic concepts possibly related to the embodiment of the present application are described, and a current uplink scheduling manner is described in the basic concepts, where the following problems exist in the foregoing known current uplink scheduling manner:
1) When the network device schedules uplink data, the network device does not immediately feed back an ACK/NACK signal to the terminal device. The terminal device cannot immediately confirm whether the current uploading 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 both because the network device successfully received the data and because the maximum number of retransmissions was reached and the network device no longer scheduled retransmissions. Therefore, the terminal device cannot confirm whether the uploaded data is successfully uploaded.
2) The compression coding of video frames in XR service has an interdependence relationship, if PDU set#2 depends on PDU set#1, but PDU set#1 is not successfully uploaded, even if PDU set#2 is successfully uploaded, PDU set#2 cannot be successfully decoded at the application layer. Since the terminal device cannot confirm whether the PDU set #1 is successfully uploaded, the terminal cannot actively discard the uploading of the PDU set #2 even if the PDU set #1 fails to upload, that is, the PDU set #2 scheduled by the network device is an invalid frame, which causes waste of uplink resources.
In order to solve the problem existing in the current uplink scheduling, the application provides a communication method for determining whether uplink data is successfully uploaded or not, and avoiding waste of uplink resources caused by scheduling invalid frames.
It should be appreciated that the communication method provided by the embodiments of the present application may be applied to a system that communicates through multiple antenna technology, such as the communication system 100 shown in fig. 1. The communication system may comprise at least one network device and at least one terminal device. The network device and the terminal device may communicate via multiple antenna technology.
It should also be understood that the embodiments shown below are not particularly limited to the specific structure of the execution body of the method provided by the embodiments of the present application, as long as communication can be performed by the method provided according to the embodiments of the present application by running a program in which the code of the method provided by the embodiments of the present application is recorded. For example, the execution body of the method provided in the embodiment of the present application may be a terminal device or a network device, or may be a functional module in the terminal device or the network device that can call a program and execute the program.
The communication method provided in the embodiment of the present application is described in detail below by taking interaction between a network device and a terminal device as an example.
Fig. 3 is a schematic flow chart of a communication method provided in the present application. The method comprises the following steps:
s310, the terminal device sends first indication information to the network device, or the network device receives the first indication information from the terminal device.
The first indication information is used to indicate a second PDU set to which the first PDU set refers (may also be referred to as dependent). The first PDU set references (may also be referred to as dependency) the second PDU set may be understood that a successful decoding of the first PDU set is premised on a successful decoding of the second PDU set. That is, the first PDU set may be successfully decoded on the premise that the second PDU set is successfully decoded (or on the premise that the second PDU set is successfully uploaded).
Specifically, the first PDU set is a PDU set to be sent by the terminal device, for example, the PDU set is buffered in a buffer of the terminal device (for example, the PDU set is buffered in a buffer of an RLC layer of the terminal device and/or a buffer of a PDCP layer of the terminal device).
For example, after the first PDU set enters the buffer of the RLC layer of the terminal device, the trigger of the terminal device sends the first indication information to the network device before submitting the MAC layer packet of the terminal device.
As can be seen from the above, the first indication information can indicate the second PDU set. For example, the first indication information includes information that can be used to indicate the second PDU set. Optionally, the first indication information includes an identification of the second PDU set (e.g., a sequence number of the second PDU set).
In this embodiment, the terminal device may learn the identity of the second PDU set by:
the protocol layer of the terminal device can obtain the identification of the first PDU set and the identification of the second PDU set referenced by the first PDU set through header detection (e.g. deep packet detection, packet filtering, etc.) when or after receiving the first PDU set generated by the application layer of the terminal device. Specifically, when the application layer of the terminal equipment packages the data of the first PDU set, the application layer of the terminal equipment generates the first PDU set, enters an access layer (AS) layer, performs header detection on a certain protocol layer (such AS an SDAP layer or PDCP layer or NAS layer or RRC layer) of the AS layer, and obtains the identity of the first PDU set and the identity of at least one PDU set referenced by the first PDU set, where the identity of the first PDU set and the identity of the at least one PDU set referenced by the first PDU set may be carried by the packet header of each PDU belonging to the first PDU set, or may be carried by the packet header of the first PDU set only.
The second PDU set is the PDU set already transmitted by the terminal device, and the PDU set referenced by the first PDU set is not transmitted or is being transmitted (e.g., the PDU set referenced by the first PDU set buffered in the RLC layer of the terminal device or the PDCP layer of the terminal device) need not be indicated by the first indication information.
For example, 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 already been transmitted by the terminal device, PDU set#2 and PDU set#3 are PDU sets that have not been transmitted by the terminal device, or PDU set#2 and PDU set#3 are PDU sets that are being transmitted by the terminal device, the first indication information may indicate PDU set#1, and no indication of PDU set#2 and PDU set#3 is required. The reason is that: the purpose of the first indication information is to determine whether the PDU set #1 that has been transmitted is successfully received by the network device, and if the terminal device knows that PDU set #2 and PDU set #3 have not been successfully transmitted, the terminal device already knows that the network device has not successfully received PDU set #2 and PDU set #3, and it is not necessary to indicate PDU set #2 and PDU set #3 through the first indication information again, in order for the network device to determine whether PDU set #2 and PDU set #3 have been successfully received.
It should be understood that the already transmitted PDU set referred to by the first PDU set may also include other PDU sets besides the second PDU set, in which case the first indication information may also be used to indicate other PDU sets referred to by the first PDU set, and for convenience of description, the PDU set referred to by the first PDU set is described as the second PDU set, that is, no matter how many already transmitted PDU sets referred to by the first PDU set are referred to by the first PDU set may be referred to as the second PDU set.
In addition, the terminal device may report information indicating the transmitted PDU set referred to by the plurality of PDU sets at a time. That is, the terminal device can indicate the PDU sets respectively referenced by the plurality of PDU sets in the buffer at a time by one indication information.
For example, the first PDU set includes a first PDU set#1, a first PDU set#2, and a first PDU set#3, and the second PDU set#1 and the second PDU set#2 referenced by the first PDU set#1 have been transmitted, the second PDU set#3 and the second PDU set#4 referenced by the first PDU set#2 have been transmitted, and the second PDU set#5 and the second PDU set#6 referenced by the first PDU set#3 have been transmitted. 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.
For example, to simplify the scheme, the first indication information may follow a currently existing signaling format. For example, the first indication information is a MAC CE, where the MAC CE includes a logical channel identifier LCID and an identifier of the second PDU set, where LCID indicates a logical channel corresponding to the MAC CE, and the logical channel is used to transmit the identifier of the PDU set referenced by the first PDU set. It can be understood that the LCID is used to indicate that the type of MAC CE is a MAC CE indicating the PDU set referenced by the first PDU set. The identity of the second PDU set is used to identify the second PDU set.
For example, the MAC CE may be referred to as a dependent (Dependency) MAC CE, and the signaling format of Dependency MAC CE is shown in table 1 below:
the identifier of the second PDU set#1 may be a sequence number of the second PDU set#1, or other information that may identify the second PDU set#1; similarly, the identifier of the second PDU set#2 may be a sequence number of the second PDU set#2, or other information that may identify the second PDU set#2.
It should be noted that, in this embodiment, mainly, the case that the first PDU set has the referenced second PDU set is considered, and for the PDU sets belonging to the independent frame (for example, a certain PDU set does not refer to other PDU sets and may be referred to as an independent PDU set), the PDU set that is not referenced, that is, the PDU set that is not referenced needs to be reported through the first indication information.
For example, the first indication information may not be transmitted for an independent PDU set without reference PDU set, or the first indication information may be transmitted, and a field indicating the referenced PDU set in the first indication information is set to 0.
For example Dependency MAC CE, which is triggered by PDU set for a certain independent frame, the field of the dependent PDU set SN included in the Dependency MAC C is set to 0.
As a possible implementation manner, after the terminal device triggers the MAC CE if the MAC layer of the terminal device has uplink resources, the first indication information is the MAC CE, and the first indication information and the MAC CE of the buffer status report (buffer status report, BSR) may be sent to the network device together.
As another possible implementation manner, the terminal device may request allocation of uplink resources for transmission of the first indication information.
In this embodiment, it is not limited how the terminal device sends the first indication information to the network device.
Further, in this embodiment, after receiving the first indication information, the network device may compare the identifier of the second PDU set with the identifier of at least one locally stored PDU set, and determine whether the first PDU set needs to be scheduled according to the comparison result. The method flow shown in fig. 3 further comprises:
S320, the network device determines whether to schedule the first PDU set.
As a possible implementation, in case the network device determines that the second PDU set was not successfully received, the network device determines not to schedule the first PDU set.
For example, the PDU set successfully received by the network device includes PDU set#1 and PDU set#3, and the network device locally holds the identities "#1" and "#3" of PDU set#1 and PDU set#3. After the network device receives the first indication information, knowing that the identifier of the second PDU set is "#2", determining that the identifier "#2" is not saved locally by the network device, and determining that the second PDU set is not successfully received by the network device.
It can be seen from the foregoing that 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 is not successfully received, and determines that the first indication information indicates the second PDU set referred to by the first PDU set through the information indicating the first indication information function (e.g., the LCID in the first indication information), the network device determines that the second PDU set is not successfully received, and the first PDU set is not scheduled. So that in this implementation the network device determines not to schedule the first PDU set.
As another possible implementation, in case the network device determines that the second PDU set was received successfully, the network device determines to schedule the first PDU set.
For example, the PDU set successfully received by the network device includes PDU set #2 and PDU set #3, and the network device locally stores identifiers "#2" and "#3" of PDU set #1 and PDU set #3, after the network device receives the first indication information, knows that the identifier of the second PDU set is "#2", determines that the network device locally stores the identifier "#2", and then the network device determines that the second PDU set is successfully received, so that the network device determines to schedule the first PDU set.
For example, if the network device decides to schedule the first PDU set, the network device may send scheduling information (e.g., DCI signaling) to the terminal device through the PDCCH channel.
As can be seen from the above step S320, the network device determines whether the first PDU set needs to be scheduled by determining whether the second PDU set is successfully received, and the method shown in fig. 3 further includes:
s311, 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.
Specifically, the second PDU set includes third indication information provided to the network device so that the network device determines whether the second PDU set is successfully received based on the third indication information. Alternatively, the third indication information may be referred to as integrity indication information.
Illustratively, the third indication information includes at least one of: the second PDU set includes the identity of the first and last PDUs; alternatively, the second PDU set includes the total number of PDUs; or, the second PDU set successfully decodes the number of PDUs required to be successfully transmitted; or the ratio of the number of PDUs that the second PDU set successfully decodes and the total number of PDUs that the second PDU set includes; or the identification of the PDU contained in the second PDU set belonging to the second PDU set; or, the sequence number of the PDU contained in the second PDU set.
In this embodiment, the function of the third indication information may be implemented in different ways.
As can be seen from the above, the second PDU set includes the third indication information for integrity detection, and for convenience of understanding, the following briefly describes how the terminal device generates the second PDU set including the third indication information:
when the application layer of the terminal equipment packages the data of the second PDU set, the following data are carried in the packet header of the PDU belonging to the second PDU set (for example, the packet header of each PDU belonging to the second PDU set may be carried in the packet header of the first PDU of the second PDU set:
sequence Number (SN) of the second PDU set, and sequence number of PDU set on which the second PDU set depends.
For example, the application layer of the terminal device generates a second PDU set, the first PDU of the second PDU set or each PDU comprising an identification of the second PDU set and an identification of at least one PDU set referenced by the second PDU set.
It should be understood that, in a similar manner to the manner in which the application layer of the terminal device generates the other PDU sets and generates the second PDU set (or the first PDU set), if a certain PDU set refers to multiple PDU sets, the application layer of the terminal device should carry the identifiers of all the PDU sets referred to by the PDU set in the packet header of the PDU set (e.g., the first PDU of the PDU set or each PDU of the PDU sets). If a certain PDU set is an independent PDU set, the terminal device may set the field carrying the identifier of the PDU set referenced by the independent PDU set in the packet header of the independent PDU set to zero.
Further, after generating the second PDU set, the application layer of the terminal device enters the AS layer, and performs header detection at a certain protocol layer (e.g., the SDAP layer or the PDCP layer) of the AS layer, to obtain the identifier of the second PDU set and the identifier of the second PDU set referenced by the second PDU set, and reloads the two types of identifiers into the header of the SDAP layer or the PDCP layer of the second PDU set.
In this embodiment, to facilitate the network device to perform PDU set integrity detection, the terminal device may carry third indication information for integrity detection in the second PDU set.
As a possible implementation, the terminal device identifies in the first PDU and the last PDU of the second PDU set, indicated as the first and the last PDU of the second PDU set, respectively.
In addition, the terminal device adds the identity of the PDU in the second PDU set in each PDU belonging to the second PDU set. For example, a PDU sequence number of the PDU in the second PDU set is added in each PDU.
In this implementation, the third indication information may be understood as including: identification information of the first and last PDUs of the second PDU set, and PDU sequence numbers of the PDUs contained in the second PDU set.
As another possible implementation, the terminal device provides the total number of PDUs contained in the second PDU set, and the identity of the PDU contained in the second PDU set belonging to the second PDU set.
In this implementation, the third indication information may be understood as including: the total number of PDUs contained in the second PDU set and the identity of the PDU from which the second PDU set belongs.
As a further possible implementation, the terminal device provides a minimum value of 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.
In this implementation, the third indication information may be understood as including: the number of PDUs required for successful transmission of the second PDU set, and the identity of the PDU contained in the second PDU set belonging to the second PDU set.
It should be understood that the above is merely taken as an example of generating the second PDU set including the third indication information, and how the terminal device generates the PDU set including the information for integrity check in this embodiment is not limited in any way. For example, for other PDU sets except the second PDU set, the procedure of generating the second PDU set by the terminal device may refer to the procedure of generating the second PDU set by the terminal device, which is not described herein.
After the network device receives the PDU included in the second PDU set, it may 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 determination result, where the method flow shown in fig. 3 further includes:
s312, the network device determines whether to save the identity of the second PDU set.
Specifically, in this embodiment, after receiving data sent by the terminal device, the network device needs to perform detection on the integrity of the PDU set on the received data, and record the SN of the PDU set that is completely received. For convenience of description, the second PDU set is taken as an example for the network device to perform integrity detection, and for other PDU sets, the flow of the network device to perform integrity detection is similar, and the description is not repeated.
Illustratively, the procedure for the network device to perform integrity check on the second PDU set is as follows:
AS described above, after the AS of the terminal device performs header detection on a protocol layer (e.g., SDAP or PDCP, etc.), the identity of the detected second PDU set and the identity of the PDU set referenced by the second PDU set are transferred to the header of the data packet of the second PDU set-related protocol layer. Correspondingly, after the network device receives the data of the terminal device, the integrity detection of the PDU set is also performed at the corresponding protocol layer.
If the detected identity of the second PDU set and the identity of the PDU set referenced by the second PDU set are loaded on the SDAP layer of the second PDU set, the network device performs integrity detection on the second PDU set at the SDAP layer.
If the detected identity of the second PDU set and the identity of the PDU set referenced by the second PDU set are loaded in the PDCP layer of the second PDU set, the network device performs integrity detection on the second PDU set in the PDCP layer.
For example, if the network device performs integrity detection on the second PDU set at the PDCP layer, the integrity detection may be performed on the second PDU set when the packet of the second PDU set is submitted to the upper layer after the PDCP layer reorders the second PDU set. The detection is used to determine whether all PDUs comprised by the second PDU set have been successfully received or whether the number of successfully received PDUs in the second PDU set exceeds a first threshold.
As a possible implementation manner, after receiving the data packet uploaded by the terminal device, the network device determines, at the aforementioned protocol layer (e.g., SDAP or PDCP, etc.), the first and last PDUs belonging to the second PDU set, and determines whether the second PDU set is completely received through consistency of the identities of the PDUs in the second PDU set.
For example, the third indication information indicates that the first and last PDUs of the second PDU set are PDU #1 and PDU#/6, respectively, and that the identification of the PDU in the second PDU set is PDU #1, PDU #2, PDU #3, PDU #4, PDU #5, PDU #6. When the network device successfully receives the PDU #1 and the PDU #/6 and the identifiers of the received PDUs in the second PDU set are consistent, the second PDU set is determined to be completely received, otherwise, the second PDU set is determined not to be completely received.
As another possible implementation, the network device confirms whether the second PDU set is completely received by determining the total number of data packets belonging to the second PDU set and the identity of the PDU belonging to the second PDU set.
For example, the third indication information indicates that the PDU is identified as pdu#1, pdu#2, pdu#3, pdu#4, pdu#5, pdu#6 in the second PDU set, and the second PDU set includes a total number of PDUs of 6. When the network device receives 6 PDUs and the identities of the PDUs are PDU #1, PDU #2, PDU #3, PDU #4, PDU #5, PDU #6, respectively, it is determined that the second PDU set is completely received, otherwise it is determined that the second PDU set is not completely received.
As yet another possible implementation manner, the network device determines whether the second PDU set is completely received by determining whether the total number of successfully received data packets belonging to the second PDU set reaches a threshold value.
For example, the third indication information indicates that the total number of successfully received data packets belonging to the second PDU set is 3, and the identities of the PDUs in the second PDU set are PDU #1, PDU #2, PDU #3, PDU #4, PDU #5, PDU #6. When the network device receives 3 or more PDUs and the identification of at least 3 PDUs is 3 of 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 is not completely received.
It should be understood that the foregoing is merely illustrative of a possible manner in which the network device performs integrity detection on the second PDU set, and the scope of protection of the present application is not limited in any way, and other methods capable of performing integrity detection on the data packet are also within the scope of protection of the present application, which is not described herein.
If the network device judges that the second PDU set is completely received, the network device stores the identification of the second PDU set, otherwise, the network device does not store the identification of the second PDU set.
For example, the identifier of the second PDU set is "#2", and when the network device determines that the second PDU set is completely received, the network device saves "#2"; otherwise, the network device does not save "#2".
For example, the network device may automatically empty the identities of the PDU sets saved before the time T or before the identity of the N PDU sets. The setting of the T value and the N value satisfies that the identification of the cleared PDU set does not refer to the identification of the PDU set referenced by the PDU set transmitted later.
From the above, the network device determines whether the second PDU set referenced by the first PDU set is successfully uploaded in step S320 through the saved identification of the PDU set. If the identifier of the second PDU set reported by the first indication information is one of the identifiers of the PDU sets stored by the network equipment, the corresponding second PDU set is indicated to be successfully uploaded, otherwise, the second PDU set is indicated to be unsuccessfully uploaded.
Further, in this embodiment, after the terminal device sends the first indication information, whether the second PDU set is successfully uploaded may be determined according to at least one of a timeout condition of a timer of the terminal device and a feedback condition of the network device to the first indication information. The method flow shown in fig. 3 further comprises:
s330, the terminal equipment determines whether the second PDU set is successfully uploaded.
As a possible implementation, the terminal device determines whether the second PDU set was successfully uploaded according to the local timeout condition of the first timer.
Specifically, 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 time when the PDCP entity of the terminal device receives the first PDU set, and in this implementation manner, the timing duration of the first timer is smaller than a frame arrival period, where the frame arrival period in this embodiment indicates the interval of buffering that two adjacent frames arrive at the terminal device. The PDCP entity of the terminal device may be understood as a transport entity (e.g., transmitting PDCP entity) of the PDCP layer of the terminal device.
Illustratively, the starting time of the first timer is the time when the PDCP entity of the terminal device receives the first PDU set, which may be further understood as the time when the PDCP layer of the terminal device transfers the first PDU set to the RLC layer of the terminal device, and may be further understood as the time when the first PDU set is buffered in the buffer.
It should be understood that, in this embodiment, the setting of the first timer and the frame arrival period is not limited, and reference may be made to the description in the related art, and in this embodiment, whether the second PDU set is successfully uploaded is determined by multiplexing the timeout condition of the existing timer.
In addition, the network device can learn information about the first timer and the period of the arrival period of the periodic frame, which can be understood that in this embodiment, the network device can learn that the expiration time (or the termination time) of the first timer is earlier than the time when the second frame arrives at the buffer of the terminal device, where the second frame is the next frame of the first frame, and the first frame includes the first PDU set.
For example, the first timer is configured for the network device, and the network device can determine information (such as information about a timing duration, a starting time, etc.) related to the first timer; and reporting the information related to the cycle frame arrival cycle to the network equipment for the terminal equipment.
In this implementation, the determining, by the terminal device, that the second PDU set is not successfully uploaded according to the timeout condition of the local first timer includes: after the first timer expires or when the first timer expires, the terminal equipment does not receive the scheduling information of the network equipment, and the terminal equipment determines that the second PDU set is not successfully uploaded; or,
the terminal equipment determines that the second PDU set is successfully uploaded according to the timeout condition of the local first timer, and the method comprises the following steps: before the first timer expires, the terminal device receives scheduling information of the network device. The terminal device uploads the first PDU set according to the scheduling information. It should be appreciated that the scheduling information of the network device may schedule a partial PDU in the first PDU set. After the first timer expires or when the first timer expires, if the buffer of the terminal device further buffers a part of the PDUs in the first PDU set, the terminal device discards the part of the PDUs that are not uploaded.
For ease of understanding, it is described in detail in connection with (a) of fig. 4 how the terminal device determines whether the second PDU set was successfully uploaded according to the timeout condition of the first timer.
As shown in fig. 4 (a), the PDU set to be transmitted by the terminal device is PDU set #1 (i.e., the first PDU set described above), the PDU set #1 is one PDU set included in the frame #1, the PDU set #1 enters the buffer (buffer) of the RLC layer of the terminal device at time t1, and the terminal device starts a first Timer (e.g., a discard Timer) at time t1, which is used to indicate that if no DCI for scheduling the PDU set #1 is received before the first Timer expires, the PDU set #1 is discarded.
In this embodiment, before the terminal device submits the PDU set#1 to the MAC layer packet, reporting Dependency MAC CE is triggered (e.g., reporting the first indication information at the time t2 after the time t 1), where Dependency MAC CE indicates PDU set#0 (i.e., the second PDU set described above) on which PDU set#1 depends, where PDU set#0 is a PDU set that has been reported, e.g., the PDU set#0 is a PDU set included in the frame#0.
For example, if the network device determines that PDU set#0 is not successfully uploaded (e.g., the network device determines that PDU set in frame#0 is not successfully uploaded), the network device determines that PDU set#1 in the buffer of the terminal device is not scheduled, but the network device does not display a notification to the terminal device that PDU set#0 is not successfully received, the terminal device waits until the first timer expires, the terminal device still does not receive the scheduling information of the network device, default PDU set#0 is not successfully received, and PDU set#1 in the buffer is cleared.
Also for example, the network device determines that PDU set #0 was successfully uploaded (e.g., the network device determines that PDU set in frame #0 has been successfully uploaded), the network device determines to schedule PDU set #1 in the terminal device buffer, and the network device issues scheduling information (e.g., DCI) to schedule PDU set #1. If the first timer expires, the buffer of the terminal device also caches a part of the PDU of PDU set#1, and clears the part of the PDU in the buffer.
In this embodiment, the timing duration of the first timer is less than or equal to the frame arrival period, that is, the first timer expires before the PDU set included in the next frame enters the buffer of the terminal device RLC/PDCP layer (e.g., time t3 shown in (a) of fig. 4).
As can be seen from the above, in the case that the network device determines that the PDU set#0 is not successfully uploaded, the network device does not need to display a notification to the terminal device that the PDU set#0 is not successfully received, and the terminal device can determine that the PDU set#0 is not successfully received according to the timeout condition of the timer of the terminal device (for example, the first timer is overtime, and the timing duration of the first timer is smaller than the frame arrival period), thereby determining that the PDU set#1 also does not need to be uploaded, and discarding the PDU set#1 in order to save the local buffer space.
As another possible implementation, the terminal device determines whether the second PDU set was successfully uploaded according to the local timeout condition of the second timer.
Specifically, the second timer is a timer started by the terminal device when the first indication information is sent, and the starting time of the second timer is the time when the first indication information is sent by the terminal device (or the time when the first indication information is sent by the terminal device).
As a possible implementation, the expiration of the second timer is before the second frame arrives at the buffer of the terminal device, the second frame being the next frame to the first frame, the first frame comprising the first PDU set.
In this implementation, the determining, by the terminal device, that the second PDU set is not successfully uploaded according to the timeout condition of the local second timer includes: when the second timer is not overtime (or the second timer runs, the terminal equipment does not receive the scheduling information of the network equipment, and the terminal equipment determines that the second PDU set is not successfully uploaded; or,
the terminal equipment determines that the second PDU set is successfully uploaded according to the timeout condition of the local second timer, and the method comprises the following steps: and when the second timer is not overtime (or the second timer runs, the terminal equipment receives the scheduling information of the network equipment, and the terminal equipment determines that the second PDU set is successfully uploaded.
For ease of understanding, it is described in detail in connection with (b) of fig. 4 how the terminal device determines that the second PDU set was not successfully uploaded based on the timeout condition of the second timer.
As shown in (b) of fig. 4, the PDU set to be transmitted by the terminal device is PDU set #1, the PDU set #1 is one PDU set included in the frame #1, the PDU set #1 enters a buffer (buffer) of the RLC layer of the terminal device at time t1, the terminal device starts a first Timer (e.g., starts a discard Timer) at time t1, and the first Timer is used to indicate that if DCI for scheduling the PDU set #1 is not received before the first Timer expires, the PDU set #1 is discarded.
In this embodiment, before the terminal device submits PDU set #1 to the MAC layer packet, reporting Dependency MAC CE is triggered (e.g., reporting the first indication information at time t2 after time t 1), and a second timer (e.g., a packet loss timer (droppingpacket timer)) is started at time of reporting Dependency MAC CE. Specifically, the Dependency MAC CE indicates PDU set#0 on which PDU set#1 depends, the PDU set#0 being one PDU set that has been reported, the PDU set#0 being one PDU set included in frame#0.
If the terminal equipment receives DCI of the scheduling uplink data sent by the network equipment in the operation period of the droping packet timer, the operation of the droping packet timer is terminated. For example, the network device determines that PDU set#0 was successfully uploaded, and may schedule PDU set#1 through DCI, and the terminal device determines that PDU set#0 was successfully uploaded to terminate the droppingPacketTimer.
If the terminal device receives DCI transmitted by the network device and retransmitted by the scheduling Dependency MAC CE during the operation of the droppingPacketTimer, the terminal device restarts the droppingPacketTimer after retransmitting Dependency MAC CE. For example, the network device may instruct the terminal device to retransmit Dependency MAC CE without successfully receiving Dependency MAC CE, and the processing for the retransmission Dependency MAC CE is similar to the initial transmission Dependency MAC CE described above, and will not be repeated.
If the terminal device does not receive DCI for scheduling uplink data (e.g., DCI for scheduling uplink data and DCI for scheduling Dependency MAC CE retransmission) during the operation of the droppingPacketTimer, the terminal device determines that PDU set#0 is not successfully uploaded, the network device does not schedule PDU set#1 in the buffer, and the terminal device may clear PDU set#1 in the buffer.
In this embodiment, the timing of the first timer is longer than the frame arrival period, that is, the first timer expires after the PDU set included in the next frame enters the buffer of the terminal device RLC/PDCP layer (e.g., time t3 shown in (b) of fig. 4).
It should be noted that if a new PDU set (e.g., PDU set of frame # 2) arrives at the buffer during the running period of the second timer after the second frame arrives at the buffer, the terminal device does not send the scheduling request (scheduling request, SR) and the first indication information (e.g., dependency MAC CE for the new PDU set) about the new PDU set. As shown in (c) of fig. 4, after the expiration of the second timer (as in t4 of (c) of fig. 4), SR and the first indication information about the new PDU set are transmitted.
As a further possible implementation manner, the terminal device determines whether the second PDU set is successfully uploaded according to the feedback condition of the network device for the first indication information.
Specifically, the feedback condition of the network device for the first indication information may be whether the network device issues the second indication information for the first indication information, which indicates that the second PDU set is not successfully uploaded.
In this implementation manner, the determining, by the terminal device, whether the second PDU set is successfully uploaded according to the feedback condition of the network device for the first indication information includes: the terminal device receives second indication information from the network device, where the second indication information is used to indicate that the second PDU set is not successfully uploaded.
Illustratively, the second indication information indicates that the second PDU set was not successfully uploaded, including: the second indication information indicates that part or all of the PDUs included in the second PDU set are not successfully uploaded; alternatively, the second indication information indicates that the number of successfully uploaded PDUs in the second PDU set is less than the first threshold.
It should be understood that the foregoing is merely illustrative of a possible manner in which the second indication information indicates that the second PDU set is not successfully uploaded, and the scope of protection of the present application is not limited in any way, and other manners that can be used to indicate that the second PDU set is not successfully uploaded are also within the scope of protection of the present application, which is not repeated herein.
As a possible implementation manner, in the case that the timing of the first Timer is longer than the frame arrival period, in order to avoid that the UE waits until the discard Timer of the frame #1 expires, discarding the PDU set #1 of the frame #1 will cause that the PDU set #1 of the frame #1 must be scheduled first when the PDU set of the frame #2 is scheduled, which causes resource waste.
For example, frame #2 is not dependent on frame #1, and the network device may schedule the PDU set included in frame #2 after receiving Dependency MAC CE for the PDU set included in frame # 2. In the case where the network device schedules the PDU set included in the frame #2, if the PDU set #1 of the frame #1 is also buffered in the buffer of the UE, the terminal device may send the PDU set #1 through the uplink resource for transmitting the PDU set included in the frame #2, resulting in resource waste. Therefore, in this implementation, the network device is required to issue the second indication information, which instructs the terminal device to discard PDU set #1 of frame # 1.
As another possible implementation manner, if the network device detects that some of the dependent PDU sets reported by Dependency MAC CE have been successfully uploaded and another part of the dependent PDU sets have not been successfully uploaded, the network device issues second indication information to indicate to the terminal device an identification of the PDU sets that have not been successfully uploaded, where the PDU sets that have not been successfully uploaded include PDU set #0 described above.
For ease of understanding, the determination that the second PDU set was not successfully uploaded by the terminal device network device for the feedback case of the first indication information will be described in detail with reference to (d) in fig. 4.
As shown in (d) of fig. 4, the PDU set to be transmitted by the terminal device is PDU set #1, the PDU set #1 is one PDU set included in the frame #1, the PDU set #1 enters a buffer (buffer) of the PDCP layer of the terminal device at time t1, the terminal device starts a first Timer (e.g., starts a discard Timer) at time t1, and the first Timer is used to indicate that if DCI for scheduling the PDU set #1 is not received before the first Timer expires, the PDU set #1 is discarded.
As a possible implementation manner, before the terminal device submits the PDU set#1 to the MAC layer packet in this embodiment, reporting Dependency MAC CE is triggered (e.g., reporting the first indication information at the time t2 after the time t 1), where Dependency MAC CE indicates PDU set#0 on which PDU set#1 depends, where PDU set#0 is a reported PDU set, and PDU set#0 is a PDU set included in the frame#0.
For example, the network device determines that PDU set #0 was not successfully uploaded (e.g., PDU set in frame #0 was not successfully uploaded), the network device determines that PDU set #1 in the terminal device buffer is not scheduled, and the network device determines that the timing time of the first timer is longer than the frame arrival period, that is, the first timer expires after PDU set included in the next frame enters the buffer of the terminal device RLC/PDCP layer (e.g., time t3 shown in (d) of fig. 4). The network device determines not to schedule PDU set #1, and notifies the terminal device of discarding PDU set #1 in the buffer through the second indication information (e.g., transmits the second indication information at time t5 shown in (d) of fig. 4).
As another possible implementation manner, before the terminal device submits the PDU set#1 to the MAC layer packet in this embodiment, reporting Dependency MAC CE is triggered (e.g., reporting the first indication information at the time t2 after the time t 1), where Dependency MAC CE indicates that PDU set#1 depends on PDU set#0 and PDU set#0_1, PDU set#0 and PDU set#0_1 are reported PDU sets, and PDU set#0 and PDU set#0_1 are PDU sets included in frame#0.
For example, the network device determines that PDU set#0 was not successfully uploaded (e.g., PDU set in frame#0 was not successfully uploaded) and PDU set#0_1 was successfully uploaded, and notifies the terminal device that PDU set#0 was not successfully uploaded through second indication information (e.g., second indication information is transmitted at time t5 shown in (d) of fig. 4), and after receiving the second indication information, the terminal device determines that PDU set#0 was not successfully uploaded, and determines that PDU set#1 depends on PDU set#0, and then deletes PDU set#1 from buffer.
The example shown in (d) of fig. 4 is similar to the example shown in (a) of fig. 4, except that frame #2 is not dependent on frame #1, and the network device can schedule PDU set of frame # 2. If the UE waits until the discard timer of the frame #1 expires and discards the PDU set #1 of the frame #1, the PDU set of the frame #1 is scheduled first when the PDU set of the frame #2 is scheduled, resulting in resource waste. Therefore, the network device in the example shown in (d) of fig. 4 is required to additionally issue second indication information instructing the UE to discard PDU set #1 of frame # 1. The second indication information may be a MAC CE, PDCP report, or SDAP report, and a format and a protocol layer of the second indication information are not limited.
It should be understood that the embodiment shown in fig. 3 is described taking the uplink data as PDU set as an example, and the embodiments of the present application are also applicable to other uplink data having a dependency relationship. For example, in the case that the first uplink data and the second uplink data have a dependency relationship, before the terminal device sends the first uplink data, the terminal device may also notify the network device that the first uplink data depends on the second uplink data through the first indication information, and in the case that it is determined that the second uplink data is not uploaded successfully, it is not necessary to schedule the first uplink data, that is, in the foregoing embodiment, the first PDU set may be replaced by a general description "first uplink data", the second PDU set may be replaced by a general description "second uplink data", and the dependency relationship between the uplink data may be understood as a strong correlation between the first uplink data and the second uplink data, and if the second uplink data is not uploaded successfully, it is not significant even if the first uplink data is uploaded successfully.
In the embodiment shown in fig. 3, the terminal device reports the indication information indicating the second PDU set that has been transmitted and referred to by the first PDU set to be transmitted, and after the first indication information is transmitted, determines whether the second PDU set is successfully uploaded according to at least one of the timeout condition of the started timer (e.g., the timing duration, whether the timer times out, etc.) and the feedback condition of the network device on the received first indication information (e.g., the information in response to the first indication information is issued). That is to say, in this technical solution, the terminal device may know whether the second PDU set is successfully uploaded.
In addition, in the embodiment shown in fig. 3, the terminal device may determine the processing of the first PDU set based on the result of whether the second PDU set is successfully uploaded, for example, the second PDU set is not successfully uploaded, and 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 based on the successful decoding of the second PDU set, and in the case that the second PDU set is not successfully uploaded, the terminal device may discard the first PDU set even if the first PDU set is uploaded.
The application also provides a communication method, and the network device sends the fourth indication information to indicate whether a certain PDU is successfully received or not under the condition that a certain condition is met, so that the terminal device can determine whether uplink data is successfully uploaded or not. The communication method is described in detail below in conjunction with fig. 5.
Fig. 5 is a schematic flow chart of another communication method provided herein. The method comprises the following steps:
s510, the network device determines that the first condition is satisfied.
S520, the network device sends the fourth indication information to the terminal device, or the terminal device receives the fourth indication information from the network device.
The fourth indication information is used for indicating the successfully received PDU and/or the unsuccessfully received PDU of the network equipment.
The first condition includes at least one of:
the fourth indication information is periodically sent information, and reaches the moment of sending the fourth indication information, the network device determines whether the third PDU set is successfully received, or the network device receives trigger information from the terminal device, wherein the trigger information is used for triggering the network device to determine the fourth indication information.
Wherein the network device determining whether the third PDU set was successfully received comprises: the network device determines whether all PDUs comprised by the third PDU set were successfully received and/or whether PDU data of the third PDU set successfully received by the network device exceeds a first threshold, wherein the first threshold is predefined.
For example, the fourth indication information may be called PDCP status report, PDCP status report, which is transmitted to the terminal device by the RLC and/or MAC layer submitted to the network device after being triggered.
As a possible implementation manner, in a case where the first condition is that the fourth indication information is periodically transmitted information, and the time when the fourth indication information is transmitted arrives, the network device periodically transmits the fourth indication information.
For example, the network device detects the uplink PDU, records the successfully received PDU and the unsuccessfully received PDU, and periodically notifies the terminal device of the successfully received PDU and/or the unsuccessfully received PDU through the fourth indication information. Optionally, the period size of the periodic transmission of the fourth indication information is preset (for example, the fourth indication information is transmitted once every 10min, and the starting time of the periodic transmission may be the time when the first PDU is received).
As another possible implementation manner, in the case that the first condition is that the network device receives the trigger information from the terminal device, where the trigger information is used to instruct the network device to issue fourth indication information indicating a successfully received PDU and/or an unsuccessfully received PDU.
For example, the network device receives the trigger information of the terminal device, determines the successfully received PDU and the unsuccessfully received PDU before receiving the trigger information, and notifies the terminal device of the successfully received PDU and/or the unsuccessfully received PDU through the fourth indication information.
As yet another possible implementation, in case 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, the third PDU set including fifth indication information for the network device to determine whether the third PDU set is successfully received.
Alternatively, the fifth indication information may be referred to as integrity indication information.
The network device determines whether the third PDU set is successfully received according to the fifth indication information. The network device determines whether all PDUs included in the third PDU set are successfully received or not, for example, according to the fifth indication information, or also determines whether the number of PDUs of the third PDU set that are successfully received exceeds the first threshold, for example, according to the fifth indication information.
The fifth indication information includes at least one of: the third PDU set includes the identity of the first and last PDUs; alternatively, the third PDU set includes the total number of PDUs; alternatively, the third PDU set successfully decodes the number of successfully transmitted PDUs required; alternatively, the third PDU set may be a ratio of the number of successfully transmitted PDUs required for successful decoding and the total number of PDUs included in the third PDU set; or, the identification of the PDU contained in the third PDU set belonging to the third PDU set; or, the sequence number of the PDU contained in the third PDU set.
In this embodiment, to facilitate the network device to perform PDU set integrity detection, the terminal device may carry fifth indication information for integrity detection in the third PDU set. Specifically, the procedure of generating the third PDU set by the terminal device may refer to the description of the procedure of generating the second PDU set by the terminal device in the embodiment shown in fig. 3, which is not repeated herein.
The difference is that the network device does not need to determine the PDU set referenced by the third PDU set.
For example, after the AS of the terminal device performs header detection on a protocol layer (e.g., SDAP or PDCP), the identity of the detected third PDU set and the identity of the PDU set referenced by the third PDU set are known. The terminal device can determine the PDU set referenced by the third PDU set according to the identifier of the third PDU set and the identifier of the PDU set referenced by the third PDU set, and transfer the identifier of the third PDU set and the identifier of the PDU set referenced by the third PDU set to the header of the data packet of the third PDU set related protocol layer. The network device need not learn the PDU set referenced by the third PDU set after receiving the third PDU set.
Alternatively, the third PDU set sent by the terminal device in this embodiment carries information for integrity detection, and may not carry information indicating the PDU set referred to by the third PDU set.
Specifically, after the network device receives the third PDU set uploaded by the terminal device, the integrity detection is performed on the third PDU set, and the specific integrity detection flow may refer to the flow of the integrity detection of the second PDU set by the network device in the embodiment shown in fig. 3, which is not described herein again.
For example, the integrity check of the third PDU set is performed after the PDCP layer has reordered. After the PDCP layer performs reordering, if the integrity of the third PDU set is found to be lost (e.g., the network device determines that the total number of successfully received PDUs belonging to the third PDU set does not reach above a threshold value, or the network device determines the integrity of the transmission of the third PDU set by determining that not all PDUs belonging to the third PDU set are successfully received), then the network device is triggered to generate a PDCP status report.
The network device determines that the third PDU set has missing integrity, i.e., the PDCP layer delivers to the SDAP layer, or the SDAP layer delivers to a higher layer, it finds that not all the packets or packet fragments of the third PDU set are received intact (e.g., missing a header packet, or missing a trailer packet, or missing a middle portion of packets). This occurs and the third PDU set needs to be submitted to the upper layer, triggering the network device to generate PDCP status report. If such a situation occurs, the third PDU set cannot be completely submitted upwards, and the network device may choose to delete the third PDU set directly without being submitted upwards.
Further, after receiving the fourth indication information, the terminal device may determine, according to the fourth indication information, a data packet that has been successfully transmitted and a data packet that has failed to be transmitted, and discard the first PDU according to a dependency relationship between a PDU set to which the PDU that has failed to be transmitted belongs and other PDU sets. The method flow shown in fig. 5 further comprises:
s530, the terminal device discards the first PDU.
And under the condition that the fourth indication information is used for indicating the PDU which is not successfully received by the network equipment, the terminal equipment determines to discard the first PDU according to the PDU which is not successfully received, and the PDU which is not successfully received is the PDU in the third PDU set. The first PDU includes at least one of: the fourth PDU set includes a PDU, an undelivered PDU in the third PDU set, or a PDU included in the fifth PDU set, wherein the fourth PDU set is a PDU set referring to the third PDU set, the fifth PDU set is a PDU set referring to the third PDU set and/or the fourth PDU set, and the fourth PDU set refers to the third PDU set and indicates: successful decoding of the fourth PDU set is premised on successful decoding of the third PDU set, the fifth PDU set being represented with reference to the third PDU set and/or the fourth PDU sett: the successful decoding of the fifth PDU set is premised on the successful decoding of the third PDU set and/or the fourth PDU set.
If the terminal device confirms that all or part of the data packets of the transmitted third PDU set are not successfully transmitted and the terminal device finds that the fourth PDU set depends on the third PDU set according to the header detection result of the subsequently arrived fourth PDU set, the terminal device deletes the fourth PDU set from the buffer and does not allocate uplink resources for uploading the fourth PDU set.
If the terminal equipment confirms that the part of the data packet of the transmitted third PDU set is not successfully transmitted and the network equipment does not schedule the part of the data packet any more, and the third PDU set has another part of the data packet which is not transmitted in the buffer of the RLC, the terminal equipment deletes the part of the data packet from the buffer of the RLC; if the third PDU set has a partial packet in the HARQ buffer, the transmission is still performed.
It should be understood that the sequence numbers of the above processes do not mean the order of execution, and the execution order of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application.
It is also to be understood that in the various embodiments of the application, terms and/or descriptions of the various embodiments are consistent and may be referenced to one another in the absence of a particular explanation or logic conflict, and that the features of the various embodiments may be combined to form new embodiments in accordance with their inherent logic relationships.
It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for the explanation (such as network devices, terminal devices, etc.), and it should be understood that the embodiments of the present application are not limited to specific forms of the devices. For example, devices that can achieve the same functionality in the future are suitable for use in the embodiments of the present application.
It will be appreciated that in the foregoing embodiments of the methods and operations implemented by a device (e.g., a network device, a terminal device) may also be implemented by a component (e.g., a chip or circuit) of the device.
The communication method provided in the embodiment of the present application is described in detail above with reference to fig. 3 and 5. The above communication method is mainly described in terms of interaction between the network device and the terminal device. It will be appreciated that the network device and the terminal device, in order to implement the above-mentioned functions, comprise corresponding hardware structures and/or software modules for performing the respective functions.
Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The following describes in detail the communication device provided in the present application with reference to fig. 6 to 9. It should be understood that the descriptions of apparatus embodiments and the descriptions of method embodiments correspond to each other. Therefore, reference may be made to the above method embodiments for details, and some of these are not described again for brevity.
The embodiment of the application may divide the function modules of the transmitting end device or the receiving end device according to the above method example, for example, each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation. The following description will take an example of dividing each functional module into corresponding functions.
Illustratively, fig. 6 is a schematic diagram of a communication device provided herein. As shown in fig. 6, the apparatus 600 includes a receiving unit 610, a transmitting unit 620, and a processing unit 630.
As an example, the sending unit 620 is configured to report first indication information to the network device, where the first indication information indicates a second PDU set referenced by the first PDU set.
A processing unit 630, configured to determine whether the second PDU set is successfully uploaded according to at least one of a timeout condition of a timer of the terminal device and a feedback condition of the network device to the first indication information.
As another example, the receiving unit 610 is configured to receive fourth indication information from the network device, where the fourth indication information is configured to indicate a PDU successfully received by the network device and/or a PDU not successfully received by the network device.
And a processing unit 630, configured to determine, when the fourth indication information is used to indicate the network device that the PDU was not successfully received, to delete the first PDU according to the PDU that was not successfully received.
The apparatus 600 corresponds to a terminal device in the method embodiment. The apparatus 600 may be a terminal device in a method embodiment, or a chip or a functional module inside a terminal device in a method embodiment. The respective units of the apparatus 600 are adapted to perform the respective steps performed by the terminal device in the method embodiments shown in fig. 3 and 5. The processing unit 630 in the apparatus 600 is configured to perform steps corresponding to the processing related to the terminal device in the method embodiment. For example, step S330 in fig. 3 is performed, or step S530 in fig. 5 is performed. The receiving unit 610 in the apparatus 600 is configured to perform the terminal device receiving step in the method embodiment. For example, step S520 in fig. 5 is performed. A sending unit 620 in the apparatus 600 is configured to perform the step of sending by the terminal device in the method embodiment. For example, steps S311, S310 in fig. 3 are performed.
Wherein the processing unit 630 may be at least one processor. The transmitting unit 620 may be a transmitter or an interface circuit, and the receiving unit 610 may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.
Optionally, the apparatus 600 may further comprise 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 a storage unit, e.g. read or invoke data and/or signaling in the storage unit, such that the methods of the above embodiments are performed.
The above units may exist independently or may be integrated in whole or in part.
Fig. 7 is a schematic structural diagram of a terminal device of the present application. The terminal device 700 may be applied to the system shown in fig. 1. For convenience of explanation, fig. 7 shows only major components of the terminal device. As shown in fig. 7, the terminal device 700 includes a processor, a memory, a control circuit, an antenna, and an input-output means. The processor is used for controlling the antenna and the input-output device to send and receive signals, the memory is used for storing a computer program, and the processor is used for calling and running the computer program from the memory so as to execute corresponding processes and/or operations executed by the terminal equipment in the communication method. And will not be described in detail herein.
Fig. 8 is a schematic diagram of another communication device provided herein. As shown in fig. 8, the apparatus 800 includes a receiving unit 810, a transmitting unit 820, and a processing unit 830.
As an example, the receiving unit 810 is configured to receive first indication information from the terminal device, where the first indication information is used to indicate a second PDU set referenced by the first PDU set.
A processing unit 830, configured to determine not to schedule the first PDU set if the second PDU set is not successfully received.
As another example, the receiving unit 810 and the processing unit 830 are configured to determine fourth indication information, where the fourth indication information is used to indicate a PDU successfully received by the network device and/or a PDU not successfully received.
A sending unit 820, configured to send the fourth indication information to the terminal device by the apparatus 800 when the first condition is satisfied.
Apparatus 800 corresponds to a network device in an embodiment of the method. The apparatus 800 may be a network device in a method embodiment, or a chip or a functional module inside a network device in a method embodiment. The respective units of the apparatus 800 are adapted to perform the respective steps performed by the network device in the method embodiments shown in fig. 3 and 5. Wherein the processing unit 830 in the apparatus 800 is configured to perform steps corresponding to processing related steps inside the network device in the method embodiment. For example, steps S312 and S320 in fig. 3 are performed, or step S510 in fig. 5 is performed. A transmitting unit 820 in the apparatus 800 is configured to perform the steps related to the network device transmission. For example, step S520 in fig. 5. The receiving unit 810 in the apparatus 800 is configured to perform the receiving step of the network device in the method embodiment. For example, steps S311 and S310 of fig. 3 are performed.
The receiving unit 810 and the transmitting unit 820 may constitute a transceiving unit, and have both receiving and transmitting functions. The processing unit 830 may be at least one processor. The transmitting unit may be a transmitter or an interface circuit. The receiving unit may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.
Optionally, the apparatus 800 may further comprise a storage unit for storing data and/or signaling. The processing unit 830, the transmitting unit 820, and the receiving unit 810 may interact or be coupled with a storage unit, e.g. read or invoke data and/or signaling in the storage unit, such that the methods of the above embodiments are performed.
The above units may exist independently or may be integrated in whole or in part.
Referring to fig. 9, fig. 9 is a schematic structural diagram of a network device of the present application, which may be used to implement the functions of the network device in the above-described communication method.
In one possible approach, for example, in some implementations in 5G communication systems, network device 900 may include a Centralized Unit (CU), a Distributed Unit (DU), and an active antenna unit (active antenna unit, AAU). Compared with an access network device in an LTE communication system, a non-real-time portion of an original Base Band Unit (BBU) is divided by one or more radio frequency units, such as a remote radio unit (remote radio unit, RRU) 9010 and one or more Base Band Units (BBU), and redefined as a CU; and the rest functions of the physical layer processing functions, which are responsible for processing non-real-time protocols and services and BBU, combined with the original RRU and the passive antenna into AAU and BBU are redefined into DUs, and are responsible for processing physical layer protocols and real-time services. In short, CUs and DUs differentiate in real-time of the processing content, AAU is a combination of RRU and antenna.
CU, DU, AAU may take a separate or co-located form, so multiple network deployment modalities may occur. One possible deployment modality is consistent with a legacy 4G access network device, CU and DU co-hardware deployment. It should be understood that fig. 9 is only an example and is not intended to limit the scope of the present application. For example, the deployment mode may be that the DUs are deployed in a 5G BBU room, CU is deployed in a centralized manner or DU is deployed in a centralized manner, CU is deployed in a higher level set, etc.
AAU 901 may implement a transceiving function referred to as a transceiving unit. Alternatively, the transceiver unit may also be referred to as a transceiver, transceiver circuitry, or transceiver, etc., which may include at least one antenna 909 and a radio frequency unit 9010. Alternatively, the transceiver unit may include a receiving unit, which may correspond to a receiver (may also be referred to as a receiver, a receiving circuit), and a transmitting unit, which may correspond to a transmitter (may also be referred to as a transmitter, a transmitting circuit). CU and DU 902 may implement internal processing functions called processing units. Alternatively, the processing unit may control the access network device, etc., and may be referred to as a controller. The AAU 901 and the CUs and DUs 902 may be physically disposed together or may be physically separated.
The access network device is not limited to the configuration shown in fig. 9, and may be other configurations. For example, including BBU and ARU, or including BBU and AAU; the present invention is not limited to this application, and CPE may be used.
It should be understood that the network device 900 shown in fig. 9 is capable of implementing the network devices involved in the method embodiments of fig. 5 and 7. The operations and/or functions of the various units in the network device 900 are respectively for implementing the corresponding procedures performed by the network device in the method embodiments of the present application. And will not be described in detail herein. The architecture of the network device illustrated in fig. 9 is only one possible configuration and should not be construed as limiting the embodiments herein in any way. The present application does not exclude the possibility of other forms of network device architecture that may occur in the future.
The embodiment of the application also provides a communication system which comprises the terminal equipment and the network equipment.
The present application also provides a computer readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the steps performed by the terminal device or the network device in the methods shown in fig. 3 and 5 described above.
The present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps performed by a terminal device or a network device in the method as shown in fig. 3 and 5.
The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory to perform the corresponding operations and/or flows performed by the terminal device or the network device in the communication method provided in the present application. The chip may be replaced by a chip system, and will not be described herein.
The terms "comprising" and "having" and any variations thereof herein are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of this application.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logic function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. The object of the present embodiment can be achieved by actually selecting some or all of the units therein. In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In addition, three relationships exist in this application and/or are represented. For example, a and/or B represent: a is present alone, while A and B are present together, and B is present alone. In addition, characters/representations or herein. At least one of the present applications means one or more than two (including two).
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application.
Claims (33)
1. A method of communication, comprising:
the terminal equipment reports first indication information to the network equipment, wherein the first indication information indicates a second PDU set referenced by a first protocol data unit group PDU set;
the terminal equipment determines whether the second PDU set is successfully uploaded according to at least one of the overtime condition of the timer of the terminal equipment and the feedback condition of the network equipment to the first indication information;
the first PDU set comprises a PDU set to be sent by the terminal equipment, and the second PDU set comprises a PDU set sent by the terminal equipment; the first PDU set refers to the second PDU set representation: successful decoding of the first PDU set is premised on successful decoding of the second PDU set.
2. The method of claim 1, wherein the first indication information comprises a medium access control layer control element, MAC CE, comprising a logical channel identity, LCID, and an identity of the second PDU set; the LCID indicates a logical channel corresponding to the MAC CE, where the logical channel is used to transmit the identifier of the second PDU set referred to by the first PDU set.
3. The method according to claim 1 or 2, wherein in case it is determined that the second PDU set was not successfully uploaded, the method further comprises: the terminal device discards the first PDU set.
4. A method according to claim 3, wherein the terminal device discards the first PDU set, comprising:
when a first timer expires, if the first PDU set is cached in a cache of the terminal equipment, discarding the first PDU set in the cache;
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 time when the packet data convergence layer protocol PDCP entity of the terminal device receives the last bit of the last PDU of the first PDU set, the timing duration of the first timer is smaller than a frame arrival period, and the frame arrival period indicates the interval of two adjacent frames arriving at the buffer.
5. The method according to claim 1 or 2, wherein in case it is determined that the second PDU set was successfully uploaded, the method further comprises:
the terminal equipment discards partial PDU in the first PDU set; or,
The terminal device transmits the first PDU set.
6. The method of claim 5, wherein the terminal device discards a portion of the PDUs in the first PDU set, comprising:
when a first timer expires, if a part of PDUs in the first PDU set are cached in a cache of the terminal equipment, discarding the part of PDUs in the first PDU set in the cache;
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 the time when the packet data convergence layer protocol PDCP entity of the terminal device receives the last bit of the last PDU of the first PDU set.
7. The method according to claim 4 or 6, wherein the buffering of the terminal device comprises:
and the buffer memory of the Radio Link Control (RLC) layer of the terminal equipment and/or the buffer memory of the packet data convergence layer protocol (PDCP) layer of the terminal equipment.
8. The method according to any one of claims 1 to 7, wherein the determining, by the terminal device, that the second PDU set was not successfully uploaded according to the feedback situation of the network device to the first indication information, includes:
The terminal equipment receives second indication information from the network equipment, wherein the second indication information is used for indicating that the second PDU set is not successfully uploaded.
9. The method according to any of claims 1 to 8, wherein the terminal device determining that the second PDU set was not successfully uploaded according to the timeout condition of the timer of the terminal device comprises:
and when the terminal equipment sends the first indication information, starting a second timer, and if the second timer is overtime and the terminal equipment does not receive the scheduling information from the network equipment, determining that the second PDU set is not successfully uploaded by the terminal equipment.
10. The method according to any of claims 1 to 9, characterized in that before the terminal device sends the first indication information, the method further comprises:
the terminal device sends the second PDU set to the network device, wherein the second PDU set comprises third indication information, and the third indication information is provided for the network device and is used for determining whether all PDUs of the second PDU set are successfully received or a specified number of PDUs are reached by the network device.
11. The method of claim 10, wherein the third indication information comprises at least one of:
the second PDU set includes the identity of the first and last PDUs; or,
the second PDU set includes a total number of PDUs; or,
the second PDU set successfully decodes the number of PDUs required for successful transmission; or alternatively
The ratio of the number of PDUs required for successful transmission required for successful decoding of the second PDU set and the total number of PDUs comprised by the second PDU set; or alternatively
The PDU contained in the second PDU set belongs to the identifier of the second PDU set; or alternatively
And the sequence number of the PDU contained in the second PDU set.
12. The method according to any one of claims 1 to 11, further comprising:
the protocol layer entity of the terminal equipment detects a header of the first PDU set when or after receiving the first PDU set generated by an application layer of the terminal equipment, and determines the identification of the first PDU set and the identification of at least one PDU set referenced by the first PDU set;
the protocol layer of the terminal equipment encapsulates the identification of the first PDU set and the identification of the at least one PDU set in the header of the protocol layer of the first PDU set;
Wherein the first or each PDU of the first PDU set comprises an identity of the first PDU set and an identity of the reference at least one PDU set, and the second PDU set is one of the at least one PDU set.
13. The method of claim 12, wherein the protocol layer comprises at least one of:
the service data adaptation SDAP layer, the packet data convergence layer protocol PDCP layer, the non-access stratum NAS or the radio resource control RRC layer.
14. A method of communication, comprising:
the network equipment receives first indication information from the terminal equipment, wherein the first indication information is used for indicating a second PDU set referenced by a first protocol data unit group PDU set;
in case the network device determines that all PDUs required for successful decoding of the second PDU set are not successfully received, the network device determines not to schedule the first PDU set;
wherein the first PDU set includes a PDU set to be sent by the terminal device, the second PDU set includes a PDU set referred to by the first PDU set that has been sent by the terminal device, and the first PDU set refers to the second PDU set representation: successful decoding of the first PDU set is premised on successful decoding of the second PDU set.
15. The method of claim 14, wherein if the network device determines that the second PDU set was successfully received, the method further comprises:
the network device sends scheduling information to the terminal device, wherein the scheduling information is used for scheduling the first PDU set.
16. The method according to claim 14 or 15, wherein the first indication information comprises a medium access control layer control element, MAC CE, comprising a logical channel identity, LCID, and an identity of the second PDU set;
the LCID indicates a logical channel corresponding to the MAC CE, where the logical channel is used to transmit the identifier of the second PDU set referred to by the first PDU set.
17. The method according to any of claims 14 to 16, wherein the network device determining that the PDUs required for successful decoding of the second PDU set have not all been successfully received comprises: the network device determines that the network device does not store the identity of the second PDU set.
18. The method according to any one of claims 14 to 17, further comprising:
the network device receives the second PDU set from the terminal device, wherein the second PDU set comprises third indication information;
And the network equipment determines whether to store the identification of the second PDU set according to the three indication information.
19. The method of claim 18, wherein the three indication information comprises at least one of:
the second PDU set includes the identity of the first and last PDUs; or,
the second PDU set includes a total number of PDUs; or,
the second PDU set successfully decodes the number of PDUs required for successful transmission; or alternatively
The ratio of the number of PDUs required for successful decoding of the second PDU set and the total number of PDUs comprised by the second PDU set; or alternatively
The PDU contained in the second PDU set belongs to the identifier of the second PDU set; or,
and the sequence number of the PDU contained in the second PDU set.
20. The method according to any of claims 14 to 19, wherein after the network device determines not to schedule the first PDU set, the method further comprises:
the network device sends second indication information to the terminal device, where the second indication information is used to indicate that the network device does not successfully receive all PDUs required by the second PDU set for successful decoding.
21. The method of claim 20, wherein prior to the network device sending the second indication information to the terminal device, the method further comprises:
the network device determines that the timing 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 time when the packet data convergence layer protocol PDCP entity of the terminal device receives the first PDU set, and the frame arrival period indicates the interval between two adjacent frames arriving at the buffer of the terminal device.
22. The method according to claim 20 or 21, wherein the second indication information for indicating that the network device did not successfully receive all PDUs required for successful decoding of the second PDU set comprises:
the second indication information includes an identification of at least one PDU set, indicating that the at least one PDU set was not successfully uploaded, and the second PDU set is one of the at least one PDU set.
23. A method of communication, comprising:
the network equipment determines that a first condition is met;
the network equipment sends fourth indication information to the terminal equipment, wherein the fourth indication information is used for indicating the successfully received PDU and/or the unsuccessfully received PDU of the network equipment;
The first condition includes at least one of: the fourth indication information is periodically sent information, and the time when the fourth indication information is sent arrives, the network equipment determines whether the third PDU set is successfully received or not, or the network equipment receives trigger information from the terminal equipment;
the triggering information is used for triggering the network equipment to determine the fourth indication information.
24. The method of claim 23, wherein if the first condition determines for the network device whether a third PDU set was successfully received, the method further comprises:
the network device receives the third PDU set from the terminal device, wherein the third PDU set comprises 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.
25. The method of claim 24, wherein the five-indicator information comprises at least one of:
the third PDU set includes the identity of the first and last PDUs; or,
the third PDU set includes a total number of PDUs; or,
The third PDU set successfully decodes the number of PDUs required for successful transmission; or alternatively
The ratio of the number of PDUs required for successful decoding of the required successful transmission by the third PDU set and the total number of PDUs comprised by the third PDU set; or alternatively
The PDU contained in the third PDU set belongs to the identifier of the third PDU set; or,
and the sequence number of the PDU contained in the third PDU set.
26. The method according to claim 24 or 25, wherein the network device determining whether all PDUs included in the third PDU set were successfully received according to the fifth indication information, comprises: the network equipment determines that part of PDUs in the third PDU set are received according to the fifth indication information, and all PDUs included in the third PDU set are not successfully received;
the method further comprises the steps of: the network device discards a portion of the PDUs in the third PDU set.
27. A method of communication, comprising:
the terminal equipment receives fourth indication information from the network equipment, wherein the fourth indication information is used for indicating the PDU successfully received by the network equipment and/or the PDU not successfully received by the network equipment;
under the condition that the fourth indication information is used for indicating the PDU which is not successfully received by the network equipment, the terminal equipment determines to discard the first PDU according to the PDU which is not successfully received, and the PDU which is not successfully received is a PDU in a third PDU set;
The first PDU includes at least one of:
a fourth PDU set includes a PDU, a PDU not transmitted in the third PDU set or a PDU included in a fifth PDU set,
wherein the fourth PDU set is a PDU set referring to the third PDU set, the fifth PDU set is a PDU set referring to the third PDU set and/or the fourth PDU set, and the fourth PDU set is expressed referring to the third PDU set: the successful decoding of the fourth PDU set is premised 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 representation: successful decoding of the fifth PDU set is premised on successful decoding of the third PDU set and/or the fourth PDU set.
28. The method of claim 27, wherein prior to the terminal device receiving the third indication information from the network device, the method further comprises:
the terminal device sends the third PDU set to the network device, wherein the third PDU set comprises fifth indication information, and the fifth indication information is provided to the network device for the network device to determine whether the third PDU set is successfully received.
29. The method of claim 28, wherein the five-indicator information comprises at least one of:
The third PDU set includes the identity of the first and last PDUs; or,
the third PDU set includes a total number of PDUs; or,
the number of successfully transmitted PDUs required for successful decoding of the third PDU set; or alternatively
A ratio of the number of successfully transmitted PDUs required for the successful decoding of the third PDU set to the total number of PDUs included in the third PDU set; or alternatively
The PDU contained in the third PDU set belongs to the identifier of the third PDU set; or,
and the sequence number of the PDU contained in the third PDU set.
30. The method according to any one of claims 27 to 29, further comprising:
before or while the third PDU set is buffered in the buffer,
the terminal equipment performs header detection on the third PDU set generated by the application layer, and determines the identification of the third PDU set and the identification of at least one PDU set referenced by the third PDU set;
the terminal device encapsulates the identity of the third PDU set and the identity of the at least one PDU set in a header of a protocol layer of the third PDU set,
wherein the first or each PDU of the third PDU set comprises an identity of the third PDU set and an identity of the at least one PDU set, a successful decoding of the third PDU set being premised on a successful decoding of the at least one PDU set.
31. A communication system comprising a terminal device for performing the method of any of claims 1 to 13 and a network device for performing the method of any of claims 14 to 22; or,
the terminal device being adapted to perform the method of any of claims 27 to 30, the network device being adapted to perform the method of any of claims 23 to 26.
32. A computer readable storage medium storing computer instructions which, when run on a terminal device, cause the terminal device to perform the method of any one of claims 1 to 30.
33. A computer program product comprising instructions which, when run on a network device, cause the network device to perform the method of any one of claims 1 to 30.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2023/100756 WO2024001831A1 (en) | 2022-06-27 | 2023-06-16 | Communication method, terminal device, network device and communication system |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210745443 | 2022-06-27 | ||
| CN2022107454438 | 2022-06-27 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117375775A true CN117375775A (en) | 2024-01-09 |
Family
ID=89402881
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210872898.6A Pending CN117375775A (en) | 2022-06-27 | 2022-07-21 | Communication method, terminal device, network device and communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117375775A (en) |
-
2022
- 2022-07-21 CN CN202210872898.6A patent/CN117375775A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6907444B2 (en) | Data transmission methods, communication devices, terminals, and base stations | |
| WO2018202037A1 (en) | Data transmission method, terminal device, and network device | |
| CN113840385A (en) | Service transmission method and device | |
| CN113766567A (en) | Communication method and device | |
| CN110089060A (en) | Instant uplink access without feedback online always | |
| WO2021023044A1 (en) | Communication method and device | |
| CN108809540B (en) | Data processing method and device | |
| CN108631959A (en) | Communication means, data cell and control unit | |
| CN114979839A (en) | Transmission control protocol proxy method and communication device | |
| EP4175356A1 (en) | Wireless communication method, terminal device, and network device | |
| WO2023207846A1 (en) | Communication method and apparatus | |
| CN116261173A (en) | Communication method and device | |
| WO2024001831A1 (en) | Communication method, terminal device, network device and communication system | |
| CN117375775A (en) | Communication method, terminal device, network device and communication system | |
| CN110999455B (en) | Communication method and related equipment | |
| CN113596915A (en) | Communication method and device | |
| CN113810949A (en) | Data transmission method and device | |
| WO2024060985A1 (en) | Communication method, network device and terminal device | |
| WO2023216986A1 (en) | Buffer status report (bsr) indication method, and apparatus | |
| WO2024067374A1 (en) | Communication method and apparatus | |
| WO2024055871A1 (en) | Data transmission method in communication system, and communication apparatus | |
| WO2024067467A1 (en) | Communication method and apparatus | |
| US11909537B2 (en) | Data transmission method and apparatus | |
| WO2023210705A1 (en) | Communication control method | |
| WO2023108413A1 (en) | Method and apparatus of reporting buffer status |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |