WO2023245450A1 - 定时提前量报告上报方法和装置 - Google Patents

定时提前量报告上报方法和装置 Download PDF

Info

Publication number
WO2023245450A1
WO2023245450A1 PCT/CN2022/100243 CN2022100243W WO2023245450A1 WO 2023245450 A1 WO2023245450 A1 WO 2023245450A1 CN 2022100243 W CN2022100243 W CN 2022100243W WO 2023245450 A1 WO2023245450 A1 WO 2023245450A1
Authority
WO
WIPO (PCT)
Prior art keywords
tar
network side
side device
terminal device
indication information
Prior art date
Application number
PCT/CN2022/100243
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280002083.0A priority Critical patent/CN115280832A/zh
Priority to PCT/CN2022/100243 priority patent/WO2023245450A1/zh
Publication of WO2023245450A1 publication Critical patent/WO2023245450A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0864—Round trip delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a timing advance report reporting method and device.
  • terminal equipment and network-side equipment can communicate through satellites, but there is RTT (Round Trip Time) between the terminal equipment and the network-side equipment.
  • the terminal device can report the timing advance report (TAR) to the network side device, so that the network side device can determine the RTT between the terminal device and the network side device, so that the network side device can determine the uplink based on the RTT.
  • the terminal device cannot determine whether the TAR is successfully reported, which is a problem that needs to be solved urgently.
  • Embodiments of the present disclosure provide a timing advance report reporting method and device, so that the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • embodiments of the present disclosure provide a method for reporting a timing advance report.
  • the method is executed by a terminal device.
  • the method includes: sending a timing advance report TAR to a network side device; and responding to receiving an instruction sent by the network side device. information to determine that the TAR is sent successfully, where the indication information is used to indicate that the network side device has received the TAR.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • embodiments of the present disclosure provide another timing advance report reporting method, which is executed by a network side device.
  • the method includes: receiving a timing advance report TAR sent by a terminal device; and sending indication information to the terminal device, where , the indication information is used to instruct the network side device to receive the TAR.
  • embodiments of the present disclosure provide a communication device that has some or all of the functions of a network-side device for implementing the method described in the first aspect.
  • the functions of the communication device may include some or all of those in the present disclosure.
  • the functions in all the embodiments may also be used to independently implement any one embodiment of the present disclosure.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to send a timing advance report TAR to the network side device; a processing module configured to determine the TAR in response to receiving indication information sent by the network side device. The transmission is successful, where the indication information is used to indicate that the network side device has received the TAR.
  • embodiments of the present disclosure provide another communication device that has some or all of the functions of the terminal device in the method example described in the second aspect.
  • the functions of the communication device may have some of the functions in the present disclosure.
  • the functions in all the embodiments may also be provided to implement the functions of any one embodiment in the present disclosure independently.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to receive a timing advance report TAR sent by a terminal device; a transceiver module further configured to send indication information to the terminal device, where the indication information is used to Indicates that the network side device has received TAR.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • embodiments of the present disclosure provide a timing advance report reporting system.
  • the system includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal equipment. When the instructions are executed, the terminal equipment is caused to execute the above-mentioned first aspect. method.
  • embodiments of the present invention provide a readable storage medium for storing instructions used by the above-mentioned network-side device. When the instructions are executed, the network-side device is caused to execute the above-mentioned second aspect. Methods.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the first aspect.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing data involved in the above method. and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system.
  • the chip system includes at least one processor and an interface for supporting the network side device to implement the functions involved in the second aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the network side device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect.
  • Figure 1 is a schematic diagram of an NTN communication method provided by an embodiment of the present disclosure
  • Figure 2 is a schematic diagram of another NTN communication method provided by an embodiment of the present disclosure.
  • Figure 3 is a schematic diagram of another NTN communication method provided by an embodiment of the present disclosure.
  • Figure 4 is an architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • Figure 5 is a flow chart of a timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 6 is a flow chart of another timing advance report reporting method provided by an embodiment of the present disclosure.
  • FIG. 7 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 8 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • FIG. 9 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 10 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 11 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 12 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 13 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 14 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 15 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 16 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 17 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 18 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 19 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 20 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • Figure 21 is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 22 is a structural diagram of another communication device provided by an embodiment of the present disclosure.
  • Figure 23 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • NTN non-terrestrialnetworks, non-terrestrial networks
  • NTN communications can be divided into transparent transmission mode and regeneration mode.
  • the transparent transmission mode is shown in Figure 2.
  • the NTN ground station sends the base station signal to the satellite.
  • the satellite converts the signal to the satellite frequency band and then sends it to the terminal (terminal equipment) through the satellite frequency band.
  • the satellite Does not demodulate base station signals.
  • the regeneration mode is shown in Figure 3. After the NTN ground station sends the base station signal to the satellite, the satellite first demodulates and decodes the signal, then re-encodes and modulates it, and sends the regenerated signal through the satellite frequency band.
  • Table 1 below gives the satellite altitude, orbit, and satellite coverage of a typical NTN network:
  • FIG. 4 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to one network side device and one terminal device.
  • the number and form of devices shown in Figure 4 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included.
  • the communication system 10 shown in Figure 4 includes a network side device 101 and a terminal device 102 as an example.
  • LTE long term evolution
  • 5th generation 5th generation
  • NR 5th generation new radio
  • side link in the embodiment of the present disclosure may also be called a side link or a through link.
  • the network side device 101 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the network side device 101 can be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other future mobile communication systems.
  • eNB evolved NodeB
  • TRP transmission reception point
  • gNB next generation base station
  • WiFi wireless fidelity
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the base station.
  • the base station may be composed of a centralized unit (central unit, CU) and a distributed unit (DU), where the CU may also be called a control unit (control unit), and CU-DU is used.
  • the structure can separate the protocol layer of the base station, such as the base station. Some protocol layer functions are centralized controlled by the CU, and the remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 102 in the embodiment of the present disclosure is an entity on the user side that is used to receive or transmit signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • FIG. 5 is a flow chart of a timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • both LTE/NR NTN support TAR and the terminal device supports reporting TAR (Timing Advance Reporting) to the network side device under various circumstances.
  • the terminal device For example, during the initial access of the terminal device (such as connection establishment/recovery/reconstruction), and the LTE PUR (preconfigured uplink resource, preconfigured uplink resource)/EDT (Early Data Transmission, early data transmission) process, if the network side The device instructs the terminal device to report TAR through system messages, and the terminal device will report TAR during the initial access/PUR/EDT process.
  • LTE PUR preconfigured uplink resource, preconfigured uplink resource
  • EDT Electronic Data Transmission, early data transmission
  • the terminal device For a terminal device in a connected state, if the network side device is configured with a TAR triggering threshold, and if the terminal device has not reported TAR or the TAR triggering threshold is met, the terminal device triggers reporting of TAR.
  • the terminal device For example, for a terminal device in a connected state, if the terminal device receives a switching command and TAR is indicated in the switching command, the terminal device triggers reporting of TAR.
  • the main purpose of TAR reporting is to let the network side device know the RTT from the terminal device to the network side device, so that the network side device can determine the uplink scheduling timing or uplink ACK/NACK feedback timing based on the RTT.
  • the network side device when a terminal device reports a TAR, it is impossible to determine whether the TAR is reported successfully. If the TAR is not reported successfully, the network side device cannot obtain the RTT of the terminal device and can only assume the worst RTT for scheduling. The network side device will determine the uplink based on the RTT. There will be a scheduling delay at the scheduling timing or uplink ACK/NACK feedback timing.
  • the condition for TAR reporting based on trigger threshold is to determine whether the change between the current TA value and the previously reported TA reaches a certain threshold before triggering TAR reporting.
  • the terminal device does not know whether the previous TA report was successful. If it was unsuccessful, and if the TA change has not met the threshold, the terminal device will never report the TA value, which will cause the network side device to be unable to obtain the TA of the terminal device, thus It directly affects the scheduling delay of the network-side device, because the network-side device can only assume the worst RTT for scheduling.
  • TAR reporting is configured when entering the connected state. If the reporting is unsuccessful, the network side device will not be able to obtain the TA of the terminal device.
  • the terminal device needs to be able to determine whether the reported TAR is successful, and if not, perform a certain retransmission.
  • S52 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device after the terminal device sends the timing advance report TAR to the network side device, it can determine in advance whether the TAR is sent successfully, that is, determine whether the network side device receives the TAR reported by the terminal device, where it can be determined before receiving If the instruction information sent by the network side device is received, it is determined that the TAR is sent successfully. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding scheduling delays in network-side devices.
  • the indication information includes at least one of the following:
  • Radio link control RLC PDU ACK with TAR in a MAC PDU Radio link control RLC PDU ACK with TAR in a MAC PDU.
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is the MAC CE (media access control control element, media access control layer) confirming the TAR. control unit), it is determined that the TAR is sent successfully.
  • the instruction information is the MAC CE (media access control control element, media access control layer) confirming the TAR. control unit
  • the terminal device sends a timing advance report TAR to the network side device; upon receiving the instruction information sent by the network side device, the instruction information is the PDCCH (Physical Downlink Control Channel) confirming the TAR. Next, confirm that the TAR is sent successfully.
  • PDCCH Physical Downlink Control Channel
  • the terminal device sends a timing advance report TAR to the network side device; when receiving the indication information sent by the network side device, and the indication information is differential KoffsetMAC CE, it is determined that the TAR is sent successfully.
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is HARQ (hybrid automatic repeat request, hybrid automatic repeat request) for sending TAR.
  • HARQ hybrid automatic repeat request, hybrid automatic repeat request
  • the terminal device sends a timing advance report TAR to the network side device; upon receiving the instruction information sent by the network side device, and the instruction information is an RRC (Radio Resource Control, Radio Resource Control) message to determine the TRA, Confirm that TAR is sent successfully.
  • RRC Radio Resource Control, Radio Resource Control
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the indication information sent by the network side device, the indication information is a MAC (media access control, media access control layer) PDU with the TAR. (Protocol data unit, protocol data unit) PDCP (packet data convergence protocol) PDU confirmation ACK, it is determined that the TAR is sent successfully.
  • MAC media access control, media access control layer
  • PDCP packet data convergence protocol
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is RLC (radio link control, wireless link control) in the same MAC PDU as the TAR. ) PDU ACK, it is determined that the TAR is sent successfully.
  • RLC radio link control, wireless link control
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR. . In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • FIG. 6 is a flow chart of another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the terminal device after the terminal device reports the TAR to the network side device in advance, it can determine in advance whether the TAR is successfully sent, that is, determine whether the network side device receives the TAR reported by the terminal device, wherein the first step of determining If the indication information sent by the network side device is received within the time period, it is determined that the TAR is sent successfully. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding scheduling delays in network-side devices.
  • the first time period may be determined according to the protocol agreement, or may be determined according to instructions from the network side device, etc. This embodiment of the present disclosure does not specifically limit this.
  • the first time period is determined by at least one of the following means:
  • the terminal device may determine the first time period based on the system message sent by the network side device.
  • the terminal device may determine the first time period based on the RRC message sent by the network side device.
  • the terminal device may receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the first time period.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate The network side device receives the TAR. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • FIG. 7 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S72 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR.
  • the terminal device after the terminal device sends the TAR to the network-side device, it can determine whether the re-transmission condition is met. If the re-transmission condition is met, the TAR is re-sent to the network-side device.
  • the retransmission condition may be that the terminal device reaches a preset time after sending the TAR, or the number of retransmissions by the terminal device does not reach a specified number, or is based on instructions from the network side device, etc.
  • the terminal device determines whether the retransmission condition is met. After sending the TAR to the network side device, it can pre-determine whether the TAR is sent successfully, wherein in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication The information is used to instruct the network side device to receive the TAR and determine that the retransmission conditions are not met. If the instruction information sent by the network side device is not received, it determines that the transmission was not successful and determines that the retransmission conditions are met. In this case, the The network side device resends the TAR.
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to satisfying the resend condition, the network side device resends the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • FIG. 8 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S82 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device after the terminal device sends the TAR to the network-side device, it can determine whether the re-transmission condition is met. If the re-transmission condition is met, the TAR is re-sent to the network-side device.
  • the resending condition may be that the terminal device does not receive the indication information sent by the network side device.
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission conditions are not met. When no indication information sent by the network side device is received, it is determined that the transmission was not successful. It is determined that the retransmission conditions are met. In this case, the TAR is retransmitted to the network side device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to the satisfaction that the terminal device has not received the indication information sent by the network side device, resends the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • FIG. 9 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S92 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device after the terminal device sends the TAR to the network-side device, it can determine whether the re-transmission condition is met. If the re-transmission condition is met, the TAR is re-sent to the network-side device.
  • the retransmission condition may be that the terminal device does not receive the indication information sent by the network side device within the second time period.
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission conditions are not met, and if the instruction information sent by the network side device is not received within the second time period, it is determined that the transmission was not successful, and it is determined that the retransmission conditions are met. In this case, the network side device Resend TAR.
  • the second time period is determined by at least one of the following means:
  • the terminal device may determine the second time period based on the system message sent by the network side device.
  • the terminal device may determine the second time period based on the RRC message sent by the network side device.
  • the terminal device may receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the second time period.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the second time period is determined based on a timer, wherein the timing duration of the timer is equal to the second time period.
  • the terminal device may determine the second time period based on the timer, where the timing length of the timer is the second time period.
  • the timer can be a new timer, or an existing timer can be reused, and its timing duration is the second time period, and it satisfies that the terminal device does not receive the message sent by the network side device within the second time period.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the PUSCH (Physical Uplink Shared Channel) transmission that the terminal device sends carrying TAR.
  • PUSCH Physical Uplink Shared Channel
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission that the terminal device sends carrying TAR plus the round-trip time RTT.
  • the terminal device receives third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the timer may be determined according to the instruction of the network side device, wherein the terminal device receives the third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the terminal device sends third capability indication information to the network side device, where the third capability indication information is used to instruct the terminal device to support the timer.
  • the terminal device may send the third capability indication information to the network side device in advance.
  • the user of the third capability indication information instructs the terminal device to support the timer.
  • the network side device sends the third configuration information to the terminal device. , to configure the timer to the end device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to the condition that the terminal device does not receive the indication information sent by the network side device within the second time period, resends the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • FIG. 10 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S101 Send a timing advance report TAR to the network side device.
  • S102 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device after the terminal device sends the TAR to the network-side device, it can determine whether the re-transmission condition is met. If the re-transmission condition is met, the TAR is re-sent to the network-side device.
  • the retransmission condition may be that the number of times the terminal device retransmits the TAR does not exceed a threshold number of times.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission conditions are not met. If the number of times the TAR is retransmitted does not exceed the threshold number, it is determined that the TAR was not successfully sent. It is determined that the retransmission conditions are met. In this case, the TAR is retransmitted to the network side device.
  • the threshold number is determined by at least one of the following ways:
  • the terminal device may determine the threshold number of times based on the system message sent by the network side device.
  • the terminal device may determine the threshold number of times based on the RRC message sent by the network side device.
  • the terminal device can receive the system message or the RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the threshold number.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to the fact that the number of times the terminal device resends the TAR does not exceed the threshold number, the network side device resends the TAR.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • FIG. 11 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • the terminal device after the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to instruct the network
  • the side device receives the TAR and determines that the retransmission conditions are not met. When the number of retransmissions of the TAR does not exceed the threshold number, it determines that the transmission was not successful and determines that the retransmission conditions are met. In this case, the TAR is retransmitted to the network side device. .
  • the method for determining the threshold number is the same as the method for determining the threshold number in the above embodiment. Please refer to the relevant description in the above embodiment and will not be described again here.
  • S112 In response to the number of TAR retransmissions exceeding the threshold number, trigger the wireless link failure RLF, or send a first message to the network side device, where the first message indicates TAR transmission failure.
  • the terminal device when the terminal device determines that the number of TAR retransmissions exceeds the threshold number, it triggers RLF (Radio Link Failure).
  • RLF Radio Link Failure
  • the terminal device when the terminal device determines that the number of TAR retransmissions exceeds a threshold number, the terminal device sends a first message to the network side device, where the first message indicates that TAR transmission fails.
  • S111 and S112 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S31 and S32 and/or in the embodiment of the present disclosure.
  • S41 and S42 and/or S51 and S52 and/or S61 and S62 and/or S71 to S73 and/or S81 to S83 and/or S91 to S93 and/or S101 to S103 are implemented together, which is not the case in the embodiment of the present disclosure. Make limitations.
  • Figure 12 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S122 In response to receiving the indication information sent by the network side device, determine that the TAR is successfully sent, where the indication information is used to instruct the network side device to receive the TAR.
  • S123 In response to receiving the first configuration information sent by the network side device, resend the TAR to the network side device, where the first configuration information is used to instruct the terminal device to resend the TAR to the network side device.
  • the terminal device after the terminal device sends the TAR to the network-side device, it can determine whether the re-transmission condition is met. If the re-transmission condition is met, the TAR is re-sent to the network-side device.
  • the retransmission condition may be that the terminal device receives the first configuration information sent by the network side device.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission condition is not met, and when the first configuration information sent by the network side device is received, it is determined that the transmission was not successful, and it is determined that the retransmission condition is met. In this case, the TAR is retransmitted to the network side device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to receiving the first configuration information sent by the network side device, resends the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • Figure 13 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S132 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • S133 Send first capability indication information to the network side device, where the first capability indication information is used to indicate that the terminal device supports TAR retransmission.
  • the terminal sb may send first capability indication information to the network side device in advance.
  • the first capability indication information is used to instruct the terminal device to support TAR retransmission to inform the network side device that it can repeat TAR.
  • S134 In response to receiving the first configuration information sent by the network side device, resend the TAR to the network side device, where the first configuration information is used to instruct the terminal device to resend the TAR to the network side device.
  • the terminal device after the terminal device sends TAR to the network side device, if it supports TAR retransmission, it can send the first capability indication information to the network side device, report that it supports TAR retransmission, and further determine whether the retransmission of TAR is satisfied. If the retransmission conditions are met, the TAR is retransmitted to the network side device.
  • the retransmission condition may be that the terminal device receives the first configuration information sent by the network side device.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission condition is not met, and when the first configuration information sent by the network side device is received, it is determined that the transmission was not successful, and it is determined that the retransmission condition is met. In this case, the TAR is retransmitted to the network side device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; sends first capability indication information to the network side device, where the first capability indication information is used to indicate that the terminal device supports retransmitting the TAR; in response to receiving the first configuration information sent by the network side device, Resend the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device.
  • FIG. 14 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S142 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device can cancel resending the TAR to the network side device based on the instruction of the network side device. For example, in the case of receiving the instruction information sent by the network side device, cancel the resending of the TAR to the network side device. TAR.
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to meeting the resend condition, resends the TAR to the network side device; in response to receiving the instruction information sent by the network side device, cancels resending the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device, and after receiving the instruction sent by the network side device In the case of information, cancel resending TAR to the network side device to avoid repeated sending and save power consumption of the terminal device.
  • FIG. 15 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S152 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device may cancel resending the TAR to the network side device based on the instruction of the network side device. For example, in the case of receiving the instruction information sent by the network side device within the third time period, cancel the resending of the TAR to the network side device.
  • the network side device resends the TAR.
  • the indication information has the same meaning as the indication information in the above embodiment. Please refer to the relevant description in the above embodiment, which will not be described again here.
  • the third time period is determined by at least one of the following means:
  • the terminal device may determine the third time period based on the system message sent by the network side device.
  • the terminal device may determine the third time period based on the RRC message sent by the network side device.
  • the terminal device can receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the third time period.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the third time period is determined based on a timer, wherein the timing duration of the timer is equal to the third time period.
  • the terminal device may determine the third time period based on the timer, where the timing length of the timer is the third time period.
  • the timer can be a new timer, or an existing timer can be reused, and its timing duration is the third time period, and the indication information sent by the network side device is received within the third time period, To cancel the condition for resending TAR to the network side device, you can set it as needed.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the PUSCH (Physical Uplink Shared Channel) transmission that the terminal device sends carrying TAR.
  • PUSCH Physical Uplink Shared Channel
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission that the terminal device sends carrying TAR plus the round-trip time RTT.
  • the terminal device receives third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the timer may be determined according to the instruction of the network side device, wherein the terminal device receives the third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the terminal device sends third capability indication information to the network side device, where the third capability indication information is used to instruct the terminal device to support the timer.
  • the terminal device may send the third capability indication information to the network side device in advance.
  • the user of the third capability indication information instructs the terminal device to support the timer.
  • the network side device sends the third configuration information to the terminal device. , to configure the timer to the end device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to meeting the retransmission condition, resends the TAR to the network side device; in response to receiving the instruction information sent by the network side device within the third time period, cancels resending the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device, and after receiving the instruction sent by the network side device In the case of information, cancel resending TAR to the network side device to avoid repeated sending and save power consumption of the terminal device.
  • FIG. 16 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S161 Send the timing advance report TAR to the network side device.
  • S162 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device can determine whether sending the TAR has reached the fourth time period, and if the sending TAR has not reached the fourth time period, cancel resending the TAR to the network side device.
  • the fourth time period is determined by at least one of the following means:
  • the terminal device may determine the fourth time period based on the system message sent by the network side device.
  • the terminal device may determine the fourth time period based on the RRC message sent by the network side device.
  • the terminal device may receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the fourth time period.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the fourth time period is determined based on a timer, wherein the timing duration of the timer is equal to the fourth time period.
  • the terminal device may determine the fourth time period based on the timer, where the timing length of the timer is the fourth time period.
  • the timer can be a new timer or an existing timer can be reused.
  • the timing duration is the fourth time period and the sending TAR has not reached the fourth time period, the retransmission to the network side device is cancelled.
  • TAR conditions can be set as needed.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the PUSCH (Physical Uplink Shared Channel) transmission carried by the terminal device.
  • PUSCH Physical Uplink Shared Channel
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission that the terminal device sends carrying TAR plus the round-trip time RTT.
  • the terminal device receives third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the timer may be determined according to the instruction of the network side device, wherein the terminal device receives the third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the terminal device sends third capability indication information to the network side device, where the third capability indication information is used to instruct the terminal device to support the timer.
  • the terminal device may send the third capability indication information to the network side device in advance.
  • the user of the third capability indication information instructs the terminal device to support the timer.
  • the network side device sends the third configuration information to the terminal device. , to configure the timer to the end device.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to the fact that the sent TAR has not reached the fourth time period, it cancels retransmitting the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device, and the TAR is sent before the fourth time period is reached. In this case, cancel resending TAR to the network side device to avoid repeated sending and save power consumption of the terminal device.
  • FIG. 17 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S171 Send the timing advance report TAR to the network side device.
  • S172 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device can determine whether the sending TAR reaches the fourth time period. If the sending TAR does not reach the fourth time period and receives the second configuration information sent by the network side device, cancel the sending of the TAR to the network side device. To resend TAR, the second configuration information is used to instruct the terminal device to cancel resending TAR to the network side device.
  • the method for determining the fourth time period is the same as the method for determining the fourth time period in the above embodiment. Please refer to the relevant description in the above embodiment and will not be described again here.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to meeting the retransmission condition, resends the TAR to the network side device; in response to sending the TAR that has not reached the fourth time period, and receiving the second configuration information sent by the network side device, cancels the request to the network side device.
  • the device resends the TAR, where the second configuration information is used to instruct the terminal device to cancel resending the TAR to the network side device.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device, and the TAR is sent before the fourth time period is reached. , and upon receiving the second configuration information sent by the network side device, cancel resending the TAR to the network side device to avoid repeated sending, so as to save power consumption of the terminal device.
  • FIG. 18 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S181 Send the timing advance report TAR to the network side device.
  • S182 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • S184 Send second capability indication information to the network side device, where the second capability indication information is used to instruct the terminal device to support canceling retransmission of TAR.
  • the terminal device supports reporting the capability information of supporting the cancellation of TAR retransmission to the network side device, wherein the second capability indication information can be reported to the network side device, and the second capability indication information is used to instruct the terminal device to support the cancellation of retransmission.
  • Send TAR the capability indication information of supporting the cancellation of TAR retransmission to the network side device.
  • S185 In response to sending the TAR that has not reached the fourth time period and receiving the second configuration information sent by the network side device, cancel resending the TAR to the network side device, where the second configuration information is used to instruct the terminal device to cancel sending the TAR to the network side device.
  • the device resends the TAR.
  • the terminal device can determine whether the sending TAR reaches the fourth time period. If the sending TAR does not reach the fourth time period and receives the second configuration information sent by the network side device, cancel the sending of the TAR to the network side device. To resend TAR, the second configuration information is used to instruct the terminal device to cancel resending TAR to the network side device.
  • the method for determining the fourth time period is the same as the method for determining the fourth time period in the above embodiment. Please refer to the relevant description in the above embodiment and will not be described again here.
  • the terminal device sends a timing advance report TAR to the network side device; in response to receiving the indication information sent by the network side device within the first time period, it is determined that the TAR transmission is successful, where the indication information is used to indicate
  • the network side device receives the TAR; in response to satisfying the retransmission condition, resends the TAR to the network side device; and sends second capability indication information to the network side device, where the second capability indication information is used to instruct the terminal device to support canceling the resending TAR.
  • the terminal device can determine whether the TAR is successfully sent, and if the retransmission conditions are met, the TAR can be resent to the network side device to avoid the scheduling delay of the network side device, and the TAR is sent before the fourth time period is reached. , and upon receiving the second configuration information sent by the network side device, cancel resending the TAR to the network side device to avoid repeated sending, so as to save power consumption of the terminal device.
  • FIG. 19 is a flow chart of yet another timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the terminal device.
  • the method may include but is not limited to the following steps:
  • S192 In response to receiving the indication information sent by the network side device, determine that the TAR is sent successfully, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device after the terminal device sends the TAR to the network side device, it can determine whether the TAR sending is successful. When receiving the instruction information sent by the network side device, it is determined that the TAR sending is successful. When it is determined that the TAR sending is unsuccessful, , and when the offset threshold timing advance TA is configured or reconfigured, TAR is sent to the network side device.
  • the terminal device sends a timing advance report TAR to the network side device; upon receiving the instruction information sent by the network side device, it is determined that the TAR is sent successfully, and it is determined that the TAR is sent unsuccessfully and is configured or In the case of reconfiguration offset threshold timing advance TA, TAR is sent to the network side device. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • Figure 20 is a flow chart of a timing advance report reporting method provided by an embodiment of the present disclosure.
  • the method is executed by the network side device.
  • the method may include but is not limited to the following steps:
  • both LTE/NR NTN support TAR and the terminal device supports reporting TAR (Timing Advance Reporting) to the network side device under various circumstances.
  • the terminal device For example, during the initial access of the terminal device (such as connection establishment/recovery/reconstruction), and the LTE PUR (preconfigured uplink resource, preconfigured uplink resource)/EDT (Early Data Transmission, early data transmission) process, if the network side The device instructs the terminal device to report TAR through system messages, and the terminal device will report TAR during the initial access/PUR/EDT process.
  • LTE PUR preconfigured uplink resource, preconfigured uplink resource
  • EDT Electronic Data Transmission, early data transmission
  • the terminal device For a terminal device in a connected state, if the network side device is configured with a TAR triggering threshold, and if the terminal device has not reported TAR or the TAR triggering threshold is met, the terminal device triggers reporting of TAR.
  • the terminal device For example, for a terminal device in a connected state, if the terminal device receives a switching command and TAR is indicated in the switching command, the terminal device triggers reporting of TAR.
  • the main purpose of TAR reporting is to let the network side device know the RTT from the terminal device to the network side device, so that the network side device can determine the uplink scheduling timing or uplink ACK/NACK feedback timing based on the RTT.
  • the network side device when a terminal device reports a TAR, it is impossible to determine whether the TAR is reported successfully. If the TAR is not reported successfully, the network side device cannot obtain the RTT of the terminal device and can only assume the worst RTT for scheduling. The network side device will determine the uplink based on the RTT. There will be a scheduling delay at the scheduling timing or uplink ACK/NACK feedback timing.
  • the condition for TAR reporting based on trigger threshold is to determine whether the change between the current TA value and the previously reported TA reaches a certain threshold before triggering TAR reporting.
  • the terminal device does not know whether the previous TA report was successful. If it was unsuccessful, and if the TA change has not met the threshold, the terminal device will never report the TA value, which will cause the network side device to be unable to obtain the TA of the terminal device, thus It directly affects the scheduling delay of the network-side device, because the network-side device can only assume the worst RTT for scheduling.
  • TAR reporting is configured when entering the connected state. If the reporting is unsuccessful, the network side device will not be able to obtain the TA of the terminal device.
  • the terminal device needs to be able to determine whether the reported TAR is successful, and if not, perform a certain retransmission.
  • S202 Send indication information to the terminal device, where the indication information is used to instruct the network side device to receive the TAR.
  • the network side device may send indication information to the terminal device to indicate to the terminal device that the network side device has received the TAR.
  • the terminal device may determine in advance whether the TAR is sent successfully, that is, determine whether the network side device receives the TAR reported by the terminal device.
  • the TAR may be determined to be sent successfully when it is determined that the indication information sent by the network side device is received. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding scheduling delays in network-side devices.
  • the indication information includes at least one of the following:
  • Radio link control RLC PDU ACK with TAR in a MAC PDU Radio link control RLC PDU ACK with TAR in a MAC PDU.
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is the MAC CE (media access control control element, media access control layer) confirming the TAR. control unit), it is determined that the TAR is sent successfully.
  • the instruction information is the MAC CE (media access control control element, media access control layer) confirming the TAR. control unit
  • the terminal device sends a timing advance report TAR to the network side device; upon receiving the instruction information sent by the network side device, the instruction information is the PDCCH (Physical Downlink Control Channel) confirming the TAR. Next, confirm that the TAR is sent successfully.
  • PDCCH Physical Downlink Control Channel
  • the terminal device sends a timing advance report TAR to the network side device; when receiving the indication information sent by the network side device, and the indication information is differential KoffsetMAC CE, it is determined that the TAR is sent successfully.
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is HARQ (hybrid automatic repeat request, hybrid automatic repeat request) for sending TAR.
  • HARQ hybrid automatic repeat request, hybrid automatic repeat request
  • the terminal device sends a timing advance report TAR to the network side device; upon receiving the instruction information sent by the network side device, and the instruction information is an RRC (Radio Resource Control, Radio Resource Control) message to determine the TRA, Confirm that TAR is sent successfully.
  • RRC Radio Resource Control, Radio Resource Control
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the indication information sent by the network side device, the indication information is a MAC (media access control, media access control layer) PDU with the TAR. (Protocol data unit, protocol data unit) PDCP (packet data convergence protocol) PDU confirmation ACK, it is determined that the TAR is sent successfully.
  • MAC media access control, media access control layer
  • PDCP packet data convergence protocol
  • the terminal device sends a timing advance report TAR to the network side device; after receiving the instruction information sent by the network side device, the instruction information is RLC (radio link control, wireless link control) in the same MAC PDU as the TAR. ) PDU ACK, it is determined that the TAR is sent successfully.
  • RLC radio link control, wireless link control
  • the network side device sends the indication information to the terminal device, including: the network side device sends the indication information to the terminal device within a first time period.
  • the network side device sends the instruction information to the terminal device, and may send the instruction information to the terminal device within the first time period, and the terminal device determines that it receives the instruction information sent by the network side device within the first time period. , confirm that the TAR is sent successfully. In this way, the terminal device can determine whether the TAR is successfully sent, thereby avoiding scheduling delays in network-side devices.
  • the determination method of the first time period is the same as the determination method in the above embodiment. Please refer to the relevant description in the above embodiment and will not be described again here.
  • the network side device receives the TAR retransmitted by the terminal device when the retransmission conditions are met.
  • the terminal device can resend the TAR to the network side device if the resending conditions are met.
  • the retransmission condition may be that the terminal device reaches a preset time after sending the TAR, or the number of retransmissions by the terminal device does not reach a specified number, or is based on instructions from the network side device, etc.
  • the terminal device determines whether the retransmission condition is met. After sending the TAR to the network side device, it can pre-determine whether the TAR is sent successfully, wherein in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication The information is used to instruct the network side device to receive the TAR and determine that the retransmission conditions are not met. If the instruction information sent by the network side device is not received, it determines that the transmission was not successful and determines that the retransmission conditions are met. In this case, the The network side device resends the TAR.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device.
  • the resending condition may be that the terminal device does not receive the indication information sent by the network side device.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission conditions are not met. When no indication information sent by the network side device is received, it is determined that the transmission was not successful. It is determined that the retransmission conditions are met. In this case, the TAR is retransmitted to the network side device.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device within the second time period.
  • the terminal device After the terminal device sends the TAR to the network side device, it determines in advance whether the TAR is sent successfully, wherein, in response to receiving the indication information sent by the network side device, it is determined that the TAR is sent successfully, where the indication information is used to indicate that the network side device receives the TAR, it is determined that the retransmission conditions are not met, and if the instruction information sent by the network side device is not received within the second time period, it is determined that the transmission was not successful, and it is determined that the retransmission conditions are met. In this case, the network side device Resend TAR.
  • the retransmission condition also includes that the number of times the terminal device resends the TAR does not exceed a threshold number of times.
  • the network side device receives a first message sent by the terminal device when the number of times the terminal device retransmits the TAR exceeds a threshold number, where the first message indicates that the TAR transmission fails.
  • the resend condition further includes receiving the first configuration information sent by the network side device, where the first configuration information is used to instruct the terminal device to resend the TAR to the network side device.
  • the network side device receives the first capability indication information sent by the terminal device, where the first capability indication information is used to indicate that the terminal device supports TAR retransmission.
  • the network side device receives the second capability indication information sent by the terminal device, where the second capability indication information is used to instruct the terminal device to support canceling TAR retransmission.
  • the retransmission condition is the same as the method in the above embodiment. Please refer to the relevant description in the above embodiment and will not be described again here.
  • At least one of the first time period, the second time period and the threshold number of times is determined by at least one of the following methods:
  • the second time period is determined based on the timer, where the timing duration of the timer is equal to the second time period.
  • the terminal device may determine the first time period based on the system message sent by the network side device.
  • the terminal device may determine the first time period based on the RRC message sent by the network side device.
  • the terminal device may receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the first time period.
  • RRC radio resource control, radio resource control
  • the terminal device may determine the second time period based on the system message sent by the network side device.
  • the terminal device may determine the second time period based on the RRC message sent by the network side device.
  • the terminal device can receive a system message or an RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the second time period.
  • RRC radio resource control, radio resource control
  • the terminal device may determine the threshold number of times based on the system message sent by the network side device.
  • the terminal device may determine the threshold number of times based on the RRC message sent by the network side device.
  • the terminal device can receive the system message or the RRC (radio resource control, radio resource control) message sent by the network side device, and then determine the threshold number.
  • RRC radio resource control, radio resource control
  • the system message of the network side device in LTE can be SIB31 (System Information Block), SIB1, or SIB2, etc.
  • the system message of the network side device in NR can also be SIB19 or SIB1.
  • the RRC message may be a connection reconfiguration message (including a handover command), a connection establishment message, a connection reestablishment message, a connection recovery message, or a connection release message, etc.
  • the second time period is determined based on a timer, wherein the timing duration of the timer is equal to the second time period.
  • the terminal device may determine the second time period based on the timer, where the timing length of the timer is the second time period.
  • the timer can be a new timer, or an existing timer can be reused, and its timing duration is the second time period, and it satisfies that the terminal device does not receive the message sent by the network side device within the second time period.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the PUSCH (Physical Uplink Shared Channel) transmission that the terminal device sends carrying TAR.
  • PUSCH Physical Uplink Shared Channel
  • the start time of the timer is the first symbol Symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission that the terminal device sends carrying TAR plus the round-trip time RTT.
  • the network side device sends third configuration information to the terminal device, where the third configuration information is used to indicate the timer.
  • the timer may be determined according to the instruction of the network side device, wherein the terminal device receives the third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the network side device receives third capability indication information sent by the terminal device, where the third capability indication information is used to instruct the terminal device to support the timer.
  • the terminal device may send the third capability indication information to the network side device in advance.
  • the user of the third capability indication information instructs the terminal device to support the timer.
  • the network side device sends the third configuration information to the terminal device. , to configure the timer to the end device.
  • the network side device receives the TAR sent by the terminal device when the TAR is unsuccessfully sent and the offset threshold timing advance TA is configured or reconfigured.
  • the terminal device after the terminal device sends the TAR to the network side device, it can determine whether the TAR sending is successful. When receiving the instruction information sent by the network side device, it is determined that the TAR sending is successful. When it is determined that the TAR sending is unsuccessful, , and when the offset threshold timing advance TA is configured or reconfigured, TAR is sent to the network side device.
  • the network side device receives the timing advance report TAR sent by the terminal device; and sends indication information to the terminal device, where the indication information is used to instruct the network side device to receive the TAR.
  • the terminal device can determine whether the TAR is successfully sent, thereby avoiding the scheduling delay of the network side device.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of terminal equipment and network side equipment.
  • the network side device and the terminal device may include a hardware structure and a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 21 is a schematic structural diagram of a communication device 1 provided by an embodiment of the present disclosure.
  • the communication device 1 shown in FIG. 21 may include a transceiver module 11 and a processing module 12.
  • the transceiver module may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module may implement the sending function and/or the receiving function.
  • the communication device 1 may be a terminal device, a device in the terminal device, or a device that can be used in conjunction with the terminal device.
  • the communication device 1 may be a network-side device, a device in the network-side device, or a device that can be used in conjunction with the network-side device.
  • Communication device 1 is terminal equipment:
  • the device includes: a transceiver module 11 and a processing module 12.
  • the transceiver module 11 is configured to send a timing advance report TAR to the network side device.
  • the processing module 12 is configured to determine that the TAR is successfully sent in response to receiving indication information sent by the network side device, where the indication information is used to indicate that the network side device receives the TAR.
  • the indication information includes at least one of the following:
  • Radio link control RLC PDU ACK with TAR in a MAC PDU Radio link control RLC PDU ACK with TAR in a MAC PDU.
  • the processing module 12 is further configured to determine that the TAR is sent successfully in response to receiving the indication information sent by the network side device within the first time period.
  • the processing module 12 is further configured to resend the TAR to the network side device in response to satisfying the resend condition.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device within the second time period.
  • the retransmission condition also includes that the number of times the terminal device resends the TAR does not exceed a threshold number of times.
  • the processing module 12 is further configured to trigger a wireless link failure RLF in response to the number of TAR retransmissions exceeding a threshold number, or send a first message to the network side device, where the first message indicates that TAR is sent. fail.
  • the resend condition further includes receiving the first configuration information sent by the network side device, where the first configuration information is used to instruct the terminal device to resend the TAR to the network side device.
  • the transceiver module 11 is further configured to send first capability indication information to the network side device, where the first capability indication information is used to indicate that the terminal device supports TAR retransmission.
  • the transceiver module 11 is further configured to cancel resending the TAR to the network side device in response to receiving the indication information sent by the network side device.
  • the transceiver module 11 is further configured to cancel retransmitting the TAR to the network side device in response to receiving the indication information sent by the network side device within the third time period.
  • the transceiver module 11 is further configured to cancel retransmitting the TAR to the network side device in response to the fact that the sending of the TAR has not reached the fourth time period.
  • the transceiver module 11 is further configured to cancel resending the TAR to the network side device in response to the sending of the TAR not reaching the fourth time period and receiving the second configuration information sent by the network side device, wherein the The second configuration information is used to instruct the terminal device to cancel resending TAR to the network side device.
  • the transceiver module 11 is further configured to send second capability indication information to the network side device, where the second capability indication information is used to instruct the terminal device to support canceling TAR retransmission.
  • At least one of the first time period, the second time period, the threshold number of times, the third time period and the fourth time period is determined by at least one of the following methods:
  • the processing module 12 is further configured to determine at least one of the second time period, the third time period, and the fourth time period based on a timer, wherein the timing length of the timer is equal to the second time period. , or the timing duration of the timer is equal to the third time period, or the timing duration of the timer is equal to the fourth time period.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the transceiver module 11 is further configured to receive third configuration information sent by the network side device, where the third configuration information is used to indicate the timer.
  • the transceiver module 11 is further configured to send third capability indication information to the network side device, where the third capability indication information is used to instruct the terminal device to support the timer.
  • the transceiver module 11 is further configured to send a TAR to the network side device in response to the terminal device failing to send the TAR and being configured or reconfigured with an offset threshold timing advance TA.
  • Communication device 1 is a network side device:
  • the device includes: a transceiver module 11.
  • the transceiver module 11 is configured to receive the timing advance report TAR sent by the terminal device.
  • the transceiver module 11 is also configured to send indication information to the terminal device, where the indication information is used to instruct the network side device to receive the TAR.
  • the indication information includes at least one of the following:
  • Radio link control RLC PDU ACK with TAR in a MAC PDU Radio link control RLC PDU ACK with TAR in a MAC PDU.
  • the transceiver module 11 is also configured to send indication information to the terminal device within the first time period.
  • the transceiver module 11 is also configured to receive the TAR retransmitted by the terminal device when the retransmission conditions are met.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device.
  • the retransmission condition includes that the terminal device does not receive the indication information sent by the network side device within the second time period.
  • the retransmission condition also includes that the number of times the terminal device resends the TAR does not exceed a threshold number of times.
  • the transceiver module 11 is further configured to receive a first message sent by the terminal device when the number of times the terminal device retransmits the TAR exceeds a threshold number, where the first message indicates that the TAR transmission failed.
  • the resend condition further includes receiving the first configuration information sent by the network side device, where the first configuration information is used to instruct the terminal device to resend the TAR to the network side device.
  • the transceiver module 11 is further configured to receive first capability indication information sent by the terminal device, where the first capability indication information is used to indicate that the terminal device supports TAR retransmission.
  • the transceiver module 11 is further configured to receive second capability indication information sent by the terminal device, where the second capability indication information is used to indicate that the terminal device supports canceling retransmission of TAR.
  • At least one of the first time period, the second time period and the threshold number of times is determined by at least one of the following methods:
  • the processing module 12 is further configured to determine the second time period based on a timer, where the timing duration of the timer is equal to the second time period.
  • the start time of the timer is at least one of the following:
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR;
  • the terminal equipment sends the first symbol after the end of the first transmission in the transmission bundle of the physical uplink shared channel PUSCH transmission carrying the TAR plus the round-trip time RTT.
  • the transceiver module 11 is also configured to send third configuration information to the terminal device, where the third configuration information is used to indicate the timer.
  • the transceiver module 11 is also configured to receive third capability indication information sent by the terminal device, where the third capability indication information is used to indicate that the terminal device supports a timer.
  • the communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the timing advance report reporting method provided in some of the above embodiments, and will not be described again here.
  • FIG. 22 is a schematic structural diagram of another communication device 1000 provided by an embodiment of the present disclosure.
  • the communication device 1000 may be a network-side device, a terminal device, a chip, a chip system, a processor, etc. that supports a network-side device to implement the above method, or a chip or a chip system that supports a terminal device to implement the above method. , or processor, etc.
  • the communication device 1000 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control and execute communication devices (such as network side equipment, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.)
  • a computer program processes data for a computer program.
  • the communication device 1000 may also include one or more memories 1002, on which a computer program 1004 may be stored.
  • the memory 1002 executes the computer program 1004, so that the communication device 1000 performs the method described in the above method embodiment.
  • the memory 1002 may also store data.
  • the communication device 1000 and the memory 1002 can be provided separately or integrated together.
  • the communication device 1000 may also include a transceiver 1005 and an antenna 1006.
  • the transceiver 1005 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1005 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1000 may also include one or more interface circuits 1007.
  • the interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001 .
  • the processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiment.
  • the communication device 1000 is a terminal device: the transceiver 1005 is used to perform S51 in Figure 5; S61 in Figure 6; S71 and S73 in Figure 7; S81 and S83 in Figure 8; S91 and S93 in Figure 9; Figure S101 and S103 in Figure 10; S111 and S112 in Figure 11; S121 and S123 in Figure 12; S131, S133 and S134 in Figure 13; S141, S143 and S144 in Figure 14; S151, S153 in Figure 15 and S154; S161, S163 and S164 in Figure 16; S171, S173 and S174 in Figure 17; S181, S183, S184 and S185 in Figure 18; S191 and S193 in Figure 19; the processor 1001 is used to execute the diagram S52 in Figure 5; S62 in Figure 6; S72 in Figure 7; S82 in Figure 8; S92 in Figure 9; S102 in Figure 10; S122 in Figure 12; S132 in Figure 13; S132 in Figure 14 S142 in Figure 15; S152 in Figure 15; S16
  • the communication device 1000 is a network-side device: the transceiver 1005 is used to perform S201 and S202 in Figure 20.
  • the processor 1001 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1001 may store a computer program 1003, and the computer program 1003 runs on the processor 1001, causing the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be solidified in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device in the description of the above embodiments may be a terminal device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 22 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • FIG. 23 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • Chip 1100 includes processor 1101 and interface 1103.
  • the number of processors 1101 may be one or more, and the number of interfaces 1103 may be multiple.
  • Interface 1103, used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the timing advance report reporting method as described in some of the above embodiments.
  • Interface 1103, used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the timing advance report reporting method as described in some of the above embodiments.
  • the chip 1100 also includes a memory 1102, which is used to store necessary computer programs and data.
  • Embodiments of the present disclosure also provide a timing advance report reporting system.
  • the system includes a communication device as a terminal device and a communication device as a network side device in the aforementioned embodiment of FIG. 20.
  • the system includes a communication device as in the aforementioned embodiment of FIG. 21.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present disclosure are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated therein.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

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

Abstract

本公开实施例公开了一种定时提前量报告上报方法和装置，可应用于通信技术领域，其中，由终端设备执行的方法包括：向网络侧设备发送定时提前量报告TAR；响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。

Description

定时提前量报告上报方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种定时提前量报告上报方法和装置。
背景技术
在移动通信技术中，终端设备与网络侧设备之间可以通过卫星进行通信，但是终端设备到网络侧设备之间存在RTT(Round Trip Time，往返时延)。
相关技术中，终端设备可以向网络侧设备上报定时提前量报告TAR(Timing Advance Reporting)，以使网络侧设备可以确定终端设备到网络侧设备之间的RTT，以便网络侧设备可以基于RTT确定上行调度时机或上行ACK(Acknowledgement，确认应答)/NACK(Negative ACKnowledgement，否认应答)反馈时机。
但是，终端设备无法确定是否成功上报TAR，这是亟需解决的问题。
发明内容
本公开实施例提供一种定时提前量报告上报方法和装置，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
第一方面，本公开实施例提供一种定时提前量报告上报方法，该方法由终端设备执行，该方法包括：向网络侧设备发送定时提前量报告TAR；响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
在该技术方案中，终端设备向网络侧设备发送定时提前量报告TAR；响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
第二方面，本公开实施例提供另一种定时提前量报告上报方法，该方法由网络侧设备执行，该方法包括：接收终端设备发送的定时提前量报告TAR；向终端设备发送指示信息，其中，指示信息用于指示网络侧设备接收到TAR。
第三方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中网络侧设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为向网络侧设备发送定时提前量报告TAR；处理模块，被配置为响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
第四方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中终端设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也 可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，该处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为接收终端设备发送的定时提前量报告TAR；收发模块，还被配置为向终端设备发送指示信息，其中，指示信息用于指示网络侧设备接收到TAR。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种定时提前量报告上报系统，该系统包括第三方面所述的通信装置以及第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述网络侧设备所用的指令，当所述指令被执行时，使所述网络侧设备执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络侧设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存网络侧设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种NTN通信方式示意图；
图2是本公开实施例提供的另一种NTN通信方式示意图；
图3是本公开实施例提供的又一种NTN通信方式示意图；
图4是本公开实施例提供的一种通信系统的架构图；
图5是本公开实施例提供的一种定时提前量报告上报方法的流程图；
图6是本公开实施例提供的另一种定时提前量报告上报方法的流程图；
图7是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图8是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图9是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图10是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图11是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图12是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图13是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图14是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图15是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图16是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图17是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图18是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图19是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图20是本公开实施例提供的又一种定时提前量报告上报方法的流程图；
图21是本公开实施例提供的一种通信装置的结构图；
图22是本公开实施例提供的另一种通信装置的结构图；
图23是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于理解本公开，此处对本公开实施例涉及到的部分概念作简单介绍。
1、NTN(non-terrestrialnetworks，非地面网络)通信方式例如图1所示。
依据卫星处理信号的方式的不同，NTN通信可以分为透传模式和再生模式。
其中，透传模式如图2所示，NTN地面站将基站信号发送给卫星，卫星将信号转换到卫星频段后再通过卫星频段下发给终端(终端设备)，除了频率转换与信号放大，卫星不对基站信号解调。
再生模式如图3所示，NTN地面站将基站信号发送给卫星后，卫星先将信号进行解调译码后再重新编码调制，并通过卫星频段发送再生的信号。
下表1给出了典型NTN网络的卫星高度，轨道，卫星覆盖范围：
Figure PCTCN2022100243-appb-000001
表1
为了更好的理解本公开实施例公开的一种定时提前量报告上报方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
请参见图4，图4为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络侧设备和一个终端设备，图4所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络侧设备，两个或两个以上的终端设备。图4所示的通信系统10以包括一个网络侧设备101和一个终端设备102为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。还需要说明的是，本公开实施例中的侧链路还可以称为侧行链路或直通链路。
本公开实施例中的网络侧设备101是网络侧的一种用于发射或接收信号的实体。例如，网络侧设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对基站所采用的具体技术和具体设备形态不做限定。本公开实施例提供的基站可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将基站，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备102是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设 备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本公开所提供的一种定时提前量报告上报方法和装置进行详细地介绍。
请参见图5，图5是本公开实施例提供的一种定时提前量报告上报方法的流程图。
如图5所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S51：向网络侧设备发送定时提前量报告TAR。
本公开实施例中，LTE/NR NTN均支持TAR，终端设备支持在多种情况下向网络侧设备上报TAR(Timing Advance Reporting)。
示例性地，终端设备在初始接入时(比如连接建立/恢复/重建)，以及LTE的PUR(preconfigured uplink resource，预配置上行资源)/EDT(Early DataTransmission，数据早传)流程，如果网络侧设备通过系统消息指示终端设备上报TAR，终端设备会在初始接入/PUR/EDT流程中上报TAR。
示例性地，对于处于连接态的终端设备，如果网络侧设备配置了TAR的触发门限，如果终端设备没上报过TAR或者TAR的触发门限满足后,终端设备触发上报TAR。
示例性地，对于处于连接态的终端设备，如果终端设备收到切换命令，且切换命令里指示TAR，终端设备触发上报TAR。
TAR上报的主要目的是为了让网络侧设备知道终端设备至网络侧设备的RTT，以便网络侧设备可以基于RTT来确定上行调度时机或上行ACK/NACK反馈时机。
相关技术中，终端设备上报TAR，无法确定是否成功上报，若未成功上报，网络侧设备无法获得终端设备的RTT，只能假设最差的RTT来进行调度，网络侧设备将基于RTT确定上行的调度时机或上行ACK/NACK反馈时机会存在调度时延。
其中，对于基于触发门限的TAR上报的条件是判断当前的TA值与之前上报的TA的变化是否达到一定门限后才触发TAR上报。但是终端设备并不知道之前的TA上报是否成功，如果未成功，而如果TA变化也一直没有满足门限，终端设备将永远不上报TA值，这会导致网络侧设备无法获得终端设备的TA，从而直接影响了网络侧设备的调度时延，因为网络侧设备只能假设最差的RTT来进行调度。
同样地，对其它原因触发的TAR，比如初始接入，进入连接态被配置TAR上报，如果未成功上报，也会导致网络侧设备无法获得终端设备的TA。
基于上述原因，终端设备需要能够判断出上报的TAR是否成功，以及如果未成功，进行一定的重传。
S52：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR之后，可以预先确定TAR是否发送成功，也即，确定网络侧设备是否接收到终端设备上报的TAR，其中，可以在确定接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功。从而终端设备可以确定是否成功发送TAR，进而避免网络侧设备出现调度时延。
在一些实施例中，指示信息包括以下至少一项：
确认TAR的媒体接入控制层控制单元MAC CE；
确认TAR的物理下行控制信道PDCCH；
差分KoffsetMAC CE；
针对发送TAR的混合自动重传请求HARQ过程的新传调度；
确定TRA的无线资源控制RRC消息；
与TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
与TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确认TAR的MAC CE(media access control control element，媒体接入控制层控制单元)的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确认TAR的PDCCH(Physical Downlink Control Channel，物理下行控制信道)的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为差分KoffsetMAC CE的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为针对发送TAR的HARQ(hybrid automatic repeat request，混合自动重传请求)过程的新传调度的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确定TRA的RRC(RadioResource Control，无线资源控制)消息的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为与TAR在一个MAC(media access control，媒体接入控制层)PDU(protocol data unit，协议数据单元)的PDCP(packet data convergence protocol，分组数据汇聚协议)PDU的确认ACK的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为与TAR在一个MAC PDU的RLC(radio link control，无线链路控制)PDU的ACK的情况下，确定TAR发送成功。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
请参见图6，图6是本公开实施例提供的另一种定时提前量报告上报方法的流程图。
如图6所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S61：向网络侧设备发送定时提前量报告TAR。
本公开实施例中，S61的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S62：响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功。
其中，指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，终端设备向网络侧设备定时提前量报告TAR之后，可以预先确定TAR是否发送成功，也即，确定网络侧设备是否接收到终端设备上报的TAR，其中，可以在确定第一时间段内接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功。从而终端设备可以确定是否成功发送TAR，进而避免网络侧设备出现调度时延。
其中，第一时间段可以根据协议约定确定，或者可以根据网络侧设备指示确定，等，本公开实施例对此不作具体限制。
在一些实施例中，第一时间段通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第一时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第一时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定第一时间段。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
请参见图7，图7是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图7所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S71：向网络侧设备发送定时提前量报告TAR。
S72：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S71和S72的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S73：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备发送TAR后到达预设时间、或者终端设备重发次数未到达指定次数、或者基于网络侧设备的指示，等等。
其中，终端设备确定是否满足重发条件，可以在向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在未接收到网络侧设备发送的指示信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
其中，指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足重发条件，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图8，图8是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图8所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S81：向网络侧设备发送定时提前量报告TAR。
S82：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S81和S82的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S83：响应于满足终端设备未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备未接收到网络侧设备发送的指示信息。指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在未接收到网络侧设备发送的指示信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足终端设备未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图9，图9是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图9所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S91：向网络侧设备发送定时提前量报告TAR。
S92：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S91和S92的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S93：响应于满足终端设备在第二时间段内未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备在第二时间段内未接收到网络侧设备发送的指示信息。指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在在第二时间段内未接收到网络侧设备发送的指示信息的情况下，确定未成功发 送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
在一些实施例中，第二时间段通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第二时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第二时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定第二时间段。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
在一些实施例中，基于定时器确定第二时间段，其中，定时器的定时时长等于第二时间段。
本公开实施例中，终端设备可以基于定时器确定第二时间段，其中，定时器的定时时长为第二时间段。其中，定时器可以为一个新的定时器，也可以复用现有的定时器，在其定时时长为第二时间段，且满足终端设备在第二时间段内未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR的条件的情况下，可以根据需要进行设置。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的PUSCH(Physical Uplink Shared Channel，物理上行共享信道)传输的传输束中的第一个传输结束后的第一个符号Symbol。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号Symbol加上往返时间RTT。
在一些实施例中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
本公开实施例中，定时器可以根据网络侧设备的指示确定，其中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，终端设备向网络侧设备发送第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
本公开实施例中，终端设备可以预先向网络侧设备发送第三能力指示信息，第三能力指示信息用户指示终端设备支持定时器，在此情况下，网络侧设备向终端设备发送第三配置信息，以向终端设备配置定时器。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足终端设备在第二时间段内未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图10，图10是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图10所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S101：向网络侧设备发送定时提前量报告TAR。
S102：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S101和S102的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S103：响应于满足终端设备重发TAR的次数不超过门限次数，向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备重发TAR的次数不超过门限次数。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在重发TAR的次数不超过门限次数的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
在一些实施例中，在一些实施例中，门限次数通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定门限次数。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定门限次数。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定门限次数。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足终端设备重发TAR的次数不超过门限次数，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图11，图11是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图11所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S111：响应于满足终端设备重发TAR的次数不超过门限次数，向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在重发TAR的次数不超过门限次数的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
其中，门限次数的确定方法与上述实施例中，门限次数的确定方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
S112：响应于重发TAR的次数超过门限次数，触发无线链路失败RLF，或者向网络侧设备发送第 一消息，其中，第一消息指示TAR发送失败。
本公开实施例中，终端设备在确定重发TAR的次数超过门限次数的情况下，触发RLF(Radio Link Failure，无线链路失败)。
本公开实施例中，终端设备在确定重发TAR的次数超过门限次数的情况下，向网络侧设备发送第一消息，其中，第一消息指示TAR发送失败。
需要说明的是，本公开实施例中，S111与S112可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S31与S32和/或S41与S42和/或S51与S52和/或S61与S62和/或S71至S73和/或S81至S83和/或S91至S93和/或S101至S103一起被实施，本公开实施例并不对此做出限定。
请参见图12，图12是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图12所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S121：向网络侧设备发送定时提前量报告TAR。
S122：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S121和S122的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S123：响应于满足接收到网络侧设备发送的第一配置信息，向网络侧设备重发TAR，其中，第一配置信息用于指示终端设备向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备接收到网络侧设备发送的第一配置信息。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在接收到网络侧设备发送的第一配置信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足接收到网络侧设备发送的第一配置信息，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图13，图13是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图13所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S131：向网络侧设备发送定时提前量报告TAR。
S132：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S131和S132的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S133：向网络侧设备发送第一能力指示信息，其中，第一能力指示信息用于指示终端设备支持重发TAR。
本公开实施例中，终端sb可以预先向网络侧设备发送第一能力指示信息，第一能力指示信息用于指示终端设备支持重发TAR，以告知网络侧设备，其可以重复TAR。
S134：响应于满足接收到网络侧设备发送的第一配置信息，向网络侧设备重发TAR，其中，第一配置信息用于指示终端设备向网络侧设备重发TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，在支持重发TAR的情况下，可以向网络侧设备发送第一能力指示信息，上报其支持重发TAR，进一步判断是否满足重发条件，在满足重发条件的情况下，向网络侧设备重发TAR。
其中，重发条件可以为终端设备接收到网络侧设备发送的第一配置信息。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在接收到网络侧设备发送的第一配置信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；向网络侧设备发送第一能力指示信息，其中，第一能力指示信息用于指示终端设备支持重发TAR；响应于满足接收到网络侧设备发送的第一配置信息，向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延。
请参见图14，图14是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图14所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S141：向网络侧设备发送定时提前量报告TAR。
S142：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
S143：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，S141至S143的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S144：响应于接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。
本公开实施例中，终端设备可以基于网络侧设备的指示，取消向网络侧设备重发TAR，示例性地，在接收到网络侧设备发送的指示信息的情况下，取消向网络侧设备重发TAR。
其中，指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足重发条件，向网络侧设备重发TAR；响应于接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延，并且在接收到网络侧设备发送的指示信息的情况下，取消向网络侧设备重发TAR，避免重复发送，以节省终端设备的功耗。
请参见图15，图15是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图15所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S151：向网络侧设备发送定时提前量报告TAR。
S152：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
S153：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，S151至S153的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S154：响应于在第三时间段内接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。
本公开实施例中，终端设备可以基于网络侧设备的指示，取消向网络侧设备重发TAR，示例性地，在第三时间段内接收到网络侧设备发送的指示信息的情况下，取消向网络侧设备重发TAR。
其中，指示信息与上述实施例中指示信息的含义相同，参见上述实施例中的相关描述，此处不再赘述。
在一些实施例中，在一些实施例中，第三时间段通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第三时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第三时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定第三时间段。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
在一些实施例中，基于定时器确定第三时间段，其中，定时器的定时时长等于第三时间段。
本公开实施例中，终端设备可以基于定时器确定第三时间段，其中，定时器的定时时长为第三时间段。其中，定时器可以为一个新的定时器，也可以复用现有的定时器，在其定时时长为第三时间段，且满足在第三时间段内接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR的条件的情况下，可以根据需要进行设置。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的PUSCH(Physical Uplink Shared Channel，物理上行共享信道)传输的传输束中的第一个传输结束后的第一个符号Symbol。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号Symbol加上往返时间RTT。
在一些实施例中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
本公开实施例中，定时器可以根据网络侧设备的指示确定，其中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，终端设备向网络侧设备发送第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
本公开实施例中，终端设备可以预先向网络侧设备发送第三能力指示信息，第三能力指示信息用户指示终端设备支持定时器，在此情况下，网络侧设备向终端设备发送第三配置信息，以向终端设备配置 定时器。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足重发条件，向网络侧设备重发TAR；响应于在第三时间段内接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延，并且在接收到网络侧设备发送的指示信息的情况下，取消向网络侧设备重发TAR，避免重复发送，以节省终端设备的功耗。
请参见图16，图16是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图16所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S161：向网络侧设备发送定时提前量报告TAR。
S162：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
S163：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，S161至S163的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S164：响应于发送TAR未到达第四时间段，取消向网络侧设备重发TAR。
本公开实施例中，终端设备可以判断发送TAR是否到达第四时间段，在发送TAR未到达第四时间段的情况下，取消向网络侧设备重发TAR。
在一些实施例中，在一些实施例中，第四时间段通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第四时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第四时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定第四时间段。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
在一些实施例中，基于定时器确定第四时间段，其中，定时器的定时时长等于第四时间段。
本公开实施例中，终端设备可以基于定时器确定第四时间段，其中，定时器的定时时长为第四时间段。其中，定时器可以为一个新的定时器，也可以复用现有的定时器，在其定时时长为第四时间段，且满足发送TAR未到达第四时间段，取消向网络侧设备重发TAR的条件的情况下，可以根据需要进行设置。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的PUSCH(Physical Uplink Shared  Channel，物理上行共享信道)传输的传输束中的第一个传输结束后的第一个符号Symbol。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号Symbol加上往返时间RTT。
在一些实施例中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
本公开实施例中，定时器可以根据网络侧设备的指示确定，其中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，终端设备向网络侧设备发送第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
本公开实施例中，终端设备可以预先向网络侧设备发送第三能力指示信息，第三能力指示信息用户指示终端设备支持定时器，在此情况下，网络侧设备向终端设备发送第三配置信息，以向终端设备配置定时器。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于发送TAR未到达第四时间段，取消向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延，并且在发送TAR未到达第四时间段的情况下，取消向网络侧设备重发TAR，避免重复发送，以节省终端设备的功耗。
请参见图17，图17是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图17所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S171：向网络侧设备发送定时提前量报告TAR。
S172：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
S173：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，S171至S173的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S174：响应于发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息，取消向网络侧设备重发TAR，其中，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。
本公开实施例中，终端设备可以判断发送TAR是否到达第四时间段，在发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息的情况下，取消向网络侧设备重发TAR，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。
本公开实施例中，第四时间段的确定方法与上述实施例中确定第四时间段的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足重发条件，向网络侧设备重发TAR；响应于发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息，取消向网络侧设备重发TAR，其中，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延，并且在发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息的情况下，取消向网络侧设备重发TAR，避免重复发 送，以节省终端设备的功耗。
请参见图18，图18是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图18所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S181：向网络侧设备发送定时提前量报告TAR。
S182：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
S183：响应于满足重发条件，向网络侧设备重发TAR。
本公开实施例中，S181至S183的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S184：向网络侧设备发送第二能力指示信息，其中，第二能力指示信息用于指示终端设备支持取消重发TAR。
本公开实施例中，终端设备支持向网络侧设备上报支持取消重发TAR的能力信息，其中，可以向网络侧设备上报第二能力指示信息，第二能力指示信息用于指示终端设备支持取消重发TAR。
S185：响应于发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息，取消向网络侧设备重发TAR，其中，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。
本公开实施例中，终端设备可以判断发送TAR是否到达第四时间段，在发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息的情况下，取消向网络侧设备重发TAR，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。
本公开实施例中，第四时间段的确定方法与上述实施例中确定第四时间段的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR；响应于满足重发条件，向网络侧设备重发TAR；向网络侧设备发送第二能力指示信息，其中，第二能力指示信息用于指示终端设备支持取消重发TAR；响应于发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息，取消向网络侧设备重发TAR，其中，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。由此，终端设备可以确定是否成功发送TAR，并且在满足重发条件的情况下，可以向网络侧设备重发TAR，避免网络侧设备的调度时延，并且在发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息的情况下，取消向网络侧设备重发TAR，避免重复发送，以节省终端设备的功耗。
请参见图19，图19是本公开实施例提供的又一种定时提前量报告上报方法的流程图。
如图19所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S191：向网络侧设备发送定时提前量报告TAR。
S192：响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，S191和S192的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S193：响应于终端设备发送TAR未成功，且被配置或重配偏移阈值定时提前量TA，向网络侧设备发送TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以对发送TAR是否成功进行判断，在接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功，在确定发送TAR未成功，且被配置或重配偏移阈值定时提前量TA的情况下，向网络侧设备发送TAR。
通过实施本公开实施例，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功，在确定发送TAR未成功，且被配置或重配偏移阈值定时提前量TA的情况下，向网络侧设备发送TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
请参见图20，图20是本公开实施例提供的一种定时提前量报告上报方法的流程图。
如图20所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S201：接收终端设备发送的定时提前量报告TAR。
本公开实施例中，LTE/NR NTN均支持TAR，终端设备支持在多种情况下向网络侧设备上报TAR(Timing Advance Reporting)。
示例性地，终端设备在初始接入时(比如连接建立/恢复/重建)，以及LTE的PUR(preconfigured uplink resource，预配置上行资源)/EDT(Early DataTransmission，数据早传)流程，如果网络侧设备通过系统消息指示终端设备上报TAR，终端设备会在初始接入/PUR/EDT流程中上报TAR。
示例性地，对于处于连接态的终端设备，如果网络侧设备配置了TAR的触发门限，如果终端设备没上报过TAR或者TAR的触发门限满足后,终端设备触发上报TAR。
示例性地，对于处于连接态的终端设备，如果终端设备收到切换命令，且切换命令里指示TAR，终端设备触发上报TAR。
TAR上报的主要目的是为了让网络侧设备知道终端设备至网络侧设备的RTT，以便网络侧设备可以基于RTT来确定上行调度时机或上行ACK/NACK反馈时机。
相关技术中，终端设备上报TAR，无法确定是否成功上报，若未成功上报，网络侧设备无法获得终端设备的RTT，只能假设最差的RTT来进行调度，网络侧设备将基于RTT确定上行的调度时机或上行ACK/NACK反馈时机会存在调度时延。
其中，对于基于触发门限的TAR上报的条件是判断当前的TA值与之前上报的TA的变化是否达到一定门限后才触发TAR上报。但是终端设备并不知道之前的TA上报是否成功，如果未成功，而如果TA变化也一直没有满足门限，终端设备将永远不上报TA值，这会导致网络侧设备无法获得终端设备的TA，从而直接影响了网络侧设备的调度时延，因为网络侧设备只能假设最差的RTT来进行调度。
同样地，对其它原因触发的TAR，比如初始接入，进入连接态被配置TAR上报，如果未成功上报，也会导致网络侧设备无法获得终端设备的TA。
基于上述原因，终端设备需要能够判断出上报的TAR是否成功，以及如果未成功，进行一定的重传。
S202：向终端设备发送指示信息，其中，指示信息用于指示网络侧设备接收到TAR。
本公开实施例中，网络侧设备接收到终端设备发送的定时提前量报告TAR之后，可以向终端设备发送指示信息，以向终端设备指示网络侧设备已接收到TAR。终端设备可以预先确定TAR是否发送成功，也即，确定网络侧设备是否接收到终端设备上报的TAR，其中，可以在确定接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功。从而终端设备可以确定是否成功发送TAR，进而避免网络侧设备出现调度时延。
在一些实施例中，指示信息包括以下至少一项：
确认TAR的媒体接入控制层控制单元MAC CE；
确认TAR的物理下行控制信道PDCCH；
差分KoffsetMAC CE；
针对发送TAR的混合自动重传请求HARQ过程的新传调度；
确定TRA的无线资源控制RRC消息；
与TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
与TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确认TAR的MAC CE(media access control control element，媒体接入控制层控制单元)的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确认TAR的PDCCH(Physical Downlink Control Channel，物理下行控制信道)的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为差分KoffsetMAC CE的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为针对发送TAR的HARQ(hybrid automatic repeat request，混合自动重传请求)过程的新传调度的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为确定TRA的RRC(RadioResource Control，无线资源控制)消息的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为与TAR在一个MAC(media access control，媒体接入控制层)PDU(protocol data unit，协议数据单元)的PDCP(packet data convergence protocol，分组数据汇聚协议)PDU的确认ACK的情况下，确定TAR发送成功。
本公开实施例中，终端设备向网络侧设备发送定时提前量报告TAR；在接收到网络侧设备发送的指示信息，指示信息为与TAR在一个MAC PDU的RLC(radio link control，无线链路控制)PDU的ACK的情况下，确定TAR发送成功。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，网络侧设备向终端设备发送指示信息，包括：网络侧设备在第一时间段内向终端设备发送指示信息。
本公开实施例中，网络侧设备向终端设备发送指示信息，可以在第一时间段内向终端设备发送指示信息，终端设备在确定第一时间段内接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功。从而终端设备可以确定是否成功发送TAR，进而避免网络侧设备出现调度时延。
其中，第一时间段的确定方法与上述实施例中的确定方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
在一些实施例中，网络侧设备接收终端设备在满足重发条件的情况下，重发的TAR。
本公开实施例中，终端设备在满足重发条件的情况下，可以向网络侧设备重发TAR。
其中，重发条件可以为终端设备发送TAR后到达预设时间、或者终端设备重发次数未到达指定次数、或者基于网络侧设备的指示，等等。
其中，终端设备确定是否满足重发条件，可以在向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在未接收到网络侧设备发送的指示信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
在一些实施例中，重发条件包括终端设备未接收到网络侧设备发送的指示信息。
其中，重发条件可以为终端设备未接收到网络侧设备发送的指示信息。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在未接收到网络侧设备发送的指示信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
在一些实施例中，重发条件包括终端设备在第二时间段内未接收到网络侧设备发送的指示信息。
其中，终端设备向网络侧设备发送TAR之后，预先判断TAR是否发送成功，其中，响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR，确定不满足重发条件，在在第二时间段内未接收到网络侧设备发送的指示信息的情况下，确定未成功发送，确定满足重发条件，在此情况下，向网络侧设备重发TAR。
在一些实施例中，重发条件还包括终端设备重发TAR的次数不超过门限次数。
在一些实施例中，网络侧设备接收终端设备在重发TAR的次数超过门限次数的情况下，发送的第一消息，其中，第一消息指示TAR发送失败。
在一些实施例中，重发条件还包括接收到网络侧设备发送的第一配置信息，其中，第一配置信息用于指示终端设备向网络侧设备重发TAR。
在一些实施例中，网络侧设备接收终端设备发送的第一能力指示信息，其中，第一能力指示信息用于指示终端设备支持重发TAR。
在一些实施例中，网络侧设备接收终端设备发送的第二能力指示信息，其中，第二能力指示信息用于指示终端设备支持取消重发TAR。
其中，重发条件与上述实施例中的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
在一些实施例中，第一时间段、第二时间段和门限次数中的至少一个，通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
基于定时器确定第二时间段，其中，定时器的定时时长等于第二时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第一时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第一时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定第一时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定第二时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定第二时间段。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无 线资源控制)消息，进而确定第二时间段。
本公开实施例中，终端设备可以基于网络侧设备发送的系统消息确定门限次数。
本公开实施例中，终端设备可以基于网络侧设备发送的RRC消息确定门限次数。
本公开实施例中，终端设备可以接收网络侧设备发送的系统消息或RRC(radio resource control，无线资源控制)消息，进而确定门限次数。
其中，LTE中的网络侧设备的系统消息可以为SIB31(System Information Block，系统信息块)、SIB1、或SIB2等。NR中的网络侧设备的系统消息还可以为SIB19或SIB1。RRC消息可以为连接重配消息(包括切换命令)，或连接建立消息，或连接重建消息，或连接恢复消息，或连接释放消息等。
在一些实施例中，基于定时器确定第二时间段，其中，定时器的定时时长等于第二时间段。
本公开实施例中，终端设备可以基于定时器确定第二时间段，其中，定时器的定时时长为第二时间段。其中，定时器可以为一个新的定时器，也可以复用现有的定时器，在其定时时长为第二时间段，且满足终端设备在第二时间段内未接收到网络侧设备发送的指示信息，向网络侧设备重发TAR的条件的情况下，可以根据需要进行设置。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的PUSCH(Physical Uplink Shared Channel，物理上行共享信道)传输的传输束中的第一个传输结束后的第一个符号Symbol。
本公开实施例中，定时器的启动时间为终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号Symbol加上往返时间RTT。
在一些实施例中，网络侧设备向终端设备发送第三配置信息，其中，第三配置信息用于指示定时器。
本公开实施例中，定时器可以根据网络侧设备的指示确定，其中，终端设备接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，网络侧设备接收终端设备发送的第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
本公开实施例中，终端设备可以预先向网络侧设备发送第三能力指示信息，第三能力指示信息用户指示终端设备支持定时器，在此情况下，网络侧设备向终端设备发送第三配置信息，以向终端设备配置定时器。
在一些实施例中，网络侧设备接收终端设备在发送TAR未成功，且被配置或重配偏移阈值定时提前量TA的情况下，发送的TAR。
本公开实施例中，终端设备向网络侧设备发送TAR之后，可以对发送TAR是否成功进行判断，在接收到网络侧设备发送的指示信息的情况下，确定TAR发送成功，在确定发送TAR未成功，且被配置或重配偏移阈值定时提前量TA的情况下，向网络侧设备发送TAR。
通过实施本公开实施例，网络侧设备接收终端设备发送的定时提前量报告TAR；向终端设备发送指示信息，其中，指示信息用于指示网络侧设备接收到TAR。由此，终端设备可以确定是否成功发送TAR，进而避免网络侧设备的调度时延。
上述本公开提供的实施例中，分别从终端设备、网络侧设备的角度对本公开实施例提供的方法进行 了介绍。为了实现上述本公开实施例提供的方法中的各功能，网络侧设备和终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图21，为本公开实施例提供的一种通信装置1的结构示意图。图21所示的通信装置1可包括收发模块11和处理模块12。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。或者，通信装置1可以是网络侧设备，也可以是网络侧设备中的装置，还可以是能够与网络侧设备匹配使用的装置。
通信装置1为终端设备：
该装置，包括：收发模块11和处理模块12。
收发模块11，被配置为向网络侧设备发送定时提前量报告TAR。
处理模块12，被配置为响应于接收到网络侧设备发送的指示信息，确定TAR发送成功，其中，指示信息用于指示网络侧设备接收到TAR。
在一些实施例中，指示信息，包括以下至少一项：
确认TAR的媒体接入控制层控制单元MAC CE；
确认TAR的物理下行控制信道PDCCH；
差分Koffset MAC CE；
针对发送TAR的混合自动重传请求HARQ过程的新传调度；
确定TRA的无线资源控制RRC消息；
与TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
与TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
在一些实施例中，处理模块12，还被配置为响应于在第一时间段内接收到网络侧设备发送的指示信息，确定TAR发送成功。
在一些实施例中，处理模块12，还被配置为响应于满足重发条件，向网络侧设备重发TAR。
在一些实施例中，重发条件包括终端设备未接收到网络侧设备发送的指示信息。
在一些实施例中，重发条件包括终端设备在第二时间段内未接收到网络侧设备发送的指示信息。
在一些实施例中，重发条件还包括终端设备重发TAR的次数不超过门限次数。
在一些实施例中，处理模块12，还被配置为响应于重发TAR的次数超过门限次数，触发无线链路失败RLF，或者向网络侧设备发送第一消息，其中，第一消息指示TAR发送失败。
在一些实施例中，重发条件还包括接收到网络侧设备发送的第一配置信息，其中，第一配置信息用于指示终端设备向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为向网络侧设备发送第一能力指示信息，其中，第一能力指示信息用于指示终端设备支持重发TAR。
在一些实施例中，收发模块11，还被配置为响应于接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为响应于在第三时间段内接收到网络侧设备发送的指示信息，取消向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为响应于发送TAR未到达第四时间段，取消向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为响应于发送TAR未到达第四时间段，且接收到网络侧设备发送的第二配置信息，取消向网络侧设备重发TAR，其中，第二配置信息用于指示终端设备取消向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为向网络侧设备发送第二能力指示信息，其中，第二能力指示信息用于指示终端设备支持取消重发TAR。
在一些实施例中，第一时间段、第二时间段、门限次数、第三时间段和第四时间段中的至少一个，通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
在一些实施例中，处理模块12，还被配置为基于定时器确定第二时间段、第三时间段和第四时间段中的至少一者，其中，定时器的定时时长等于第二时间段，或者定时器的定时时长等于第三时间段，或者定时器的定时时长等于第四时间段。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
在一些实施例中，收发模块11，还被配置为接收网络侧设备发送的第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，收发模块11，还被配置为向网络侧设备发送第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
在一些实施例中，收发模块11，还被配置为响应于终端设备发送TAR未成功，且被配置或重配偏移阈值定时提前量TA，向网络侧设备发送TAR。
通信装置1为网络侧设备：
该装置，包括：收发模块11。
收发模块11，被配置为接收终端设备发送的定时提前量报告TAR。
收发模块11，还被配置为向终端设备发送指示信息，其中，指示信息用于指示网络侧设备接收到TAR。
在一些实施例中，指示信息，包括以下至少一项：
确认TAR的媒体接入控制层控制单元MAC CE；
确认TAR的物理下行控制信道PDCCH；
差分KoffsetMAC CE；
针对发送TAR的混合自动重传请求HARQ过程的新传调度；
确定TRA的无线资源控制RRC消息；
与TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
与TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
在一些实施例中，收发模块11，还被配置为在第一时间段内向终端设备发送指示信息。
在一些实施例中，收发模块11，还被配置为接收终端设备在满足重发条件的情况下，重发的TAR。
在一些实施例中，重发条件包括终端设备未接收到网络侧设备发送的指示信息。
在一些实施例中，重发条件包括终端设备在第二时间段内未接收到网络侧设备发送的指示信息。
在一些实施例中，重发条件还包括终端设备重发TAR的次数不超过门限次数。
在一些实施例中，收发模块11，还被配置为接收终端设备在重发TAR的次数超过门限次数的情况下，发送的第一消息，其中，第一消息指示TAR发送失败。
在一些实施例中，重发条件还包括接收到网络侧设备发送的第一配置信息，其中，第一配置信息用于指示终端设备向网络侧设备重发TAR。
在一些实施例中，收发模块11，还被配置为接收终端设备发送的第一能力指示信息，其中，第一能力指示信息用于指示终端设备支持重发TAR。
在一些实施例中，收发模块11，还被配置为接收终端设备发送的第二能力指示信息，其中，第二能力指示信息用于指示终端设备支持取消重发TAR。
在一些实施例中，第一时间段、第二时间段和门限次数中的至少一个，通过以下至少一种方式确定：
基于网络侧设备发送的系统消息确定；
基于网络侧设备发送的RRC消息确定。
在一些实施例中，处理模块12，还被配置为基于定时器确定第二时间段，其中，定时器的定时时长等于第二时间段。
在一些实施例中，定时器的启动时间为以下至少一个：
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
终端设备发送携带TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
在一些实施例中，收发模块11，还被配置为向终端设备发送第三配置信息，其中，第三配置信息用于指示定时器。
在一些实施例中，收发模块11，还被配置为接收终端设备发送的第三能力指示信息，其中，第三能力指示信息用于指示终端设备支持定时器。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的定时提前量报告上报方法取得相同或相似的有益效果，此处不再赘述。
请参见图22，图22是本公开实施例提供的另一种通信装置1000的结构示意图。通信装置1000可以是网络侧设备，也可以是终端设备，也可以是支持网络侧设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，网络侧设备、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为终端设备：收发器1005用于执行图5中的S51；图6中的S61；图7中的S71和S73；图8中的S81和S83；图9中的S91和S93；图10中的S101和S103；图11中的S111和S112；图12中的S121和S123；图13中的S131、S133和S134；图14中的S141、S143和S144；图15中的S151、S153和S154；图16中的S161、S163和S164；图17中的S171、S173和S174；图18中的S181、S183、S184和S185；图19中的S191和S193；处理器1001用于执行图5中的S52；图6中的S62；图7中的S72；图8中的S82；图9中的S92；图10中的S102；图12中的S122；图13中的S132；图14中的S142；图15中的S152；图16中的S162；图17中的S172；图18中的S182；图19中的S192。
通信装置1000为网络侧设备：收发器1005用于执行图20中的S201和S202。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图22的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图23，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中网络侧设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的定时提前量报告上报方法。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的定时提前量报告上报方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种定时提前量报告上报系统，该系统包括前述图20实施例中作为终端设备的通信装置和作为网络侧设备的通信装置，或者，该系统包括前述图21实施例中作为终端设备的通信装置和作为网络侧设备的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区 分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (43)

  1. 一种定时提前量报告上报方法，其特征在于，所述方法由终端设备执行，包括：
    向网络侧设备发送定时提前量报告TAR；
    响应于接收到所述网络侧设备发送的指示信息，确定所述TAR发送成功，其中，所述指示信息用于指示所述网络侧设备接收到所述TAR。
  2. 如权利要求1所述的方法，其特征在于，所述指示信息，包括以下至少一项：
    确认所述TAR的媒体接入控制层控制单元MAC CE；
    确认所述TAR的物理下行控制信道PDCCH；
    差分Koffset MAC CE；
    针对发送所述TAR的混合自动重传请求HARQ过程的新传调度；
    确定所述TRA的无线资源控制RRC消息；
    与所述TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
    与所述TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
  3. 如权利要求1或2所述的方法，其特征在于，所述响应于接收到所述网络侧设备发送的指示信息，确定所述TAR发送成功，包括：
    响应于在第一时间段内接收到所述网络侧设备发送的所述指示信息，确定所述TAR发送成功。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，还包括：
    响应于满足重发条件，向所述网络侧设备重发所述TAR。
  5. 如权利要求4所述的方法，其特征在于，所述重发条件包括所述终端设备未接收到所述网络侧设备发送的所述指示信息。
  6. 如权利要求4所述的方法，其特征在于，所述重发条件包括所述终端设备在第二时间段内未接收到所述网络侧设备发送的所述指示信息。
  7. 如权利要求4至6中任一项所述的方法，其特征在于，所述重发条件还包括所述终端设备重发所述TAR的次数不超过门限次数。
  8. 如权利要求7所述的方法，其特征在于，还包括：
    响应于重发所述TAR的次数超过所述门限次数，触发无线链路失败RLF，或者向所述网络侧设备发送第一消息，其中，所述第一消息指示所述TAR发送失败。
  9. 如权利要求4至8中任一项所述的方法，其特征在于，所述重发条件还包括接收到所述网络侧设备发送的第一配置信息，其中，所述第一配置信息用于指示所述终端设备向所述网络侧设备重发所述TAR。
  10. 如权利要求9所述的方法，其特征在于，还包括：
    向所述网络侧设备发送第一能力指示信息，其中，所述第一能力指示信息用于指示所述终端设备支持重发所述TAR。
  11. 如权利要求4至10中任一项所述的方法，其特征在于，还包括：
    响应于接收到所述网络侧设备发送的所述指示信息，取消向所述网络侧设备重发所述TAR。
  12. 如权利要求11所述的方法，其特征在于，所述响应于接收到所述网络侧设备发送的所述指示信息，取消向所述网络侧设备重发所述TAR，包括：
    响应于在第三时间段内接收到所述网络侧设备发送的所述指示信息，取消向所述网络侧设备重发所述TAR。
  13. 如权利要求4至12中任一项所述的方法，其特征在于，还包括：
    响应于发送所述TAR未到达第四时间段，取消向所述网络侧设备重发所述TAR。
  14. 如权利要求13所述的方法，其特征在于，所述响应于发送所述TAR未到达第四时间段，取消向所述网络侧设备重发所述TAR，包括：
    响应于发送所述TAR未到达第四时间段，且接收到所述网络侧设备发送的第二配置信息，取消向所述网络侧设备重发所述TAR，其中，所述第二配置信息用于指示所述终端设备取消向所述网络侧设备重发所述TAR。
  15. 如权利要求14所述的方法，其特征在于，还包括：
    向所述网络侧设备发送第二能力指示信息，其中，所述第二能力指示信息用于指示所述终端设备支持取消重发所述TAR。
  16. 如权利要求3至15中任一项所述的方法，其特征在于，所述第一时间段、所述第二时间段、所述门限次数、所述第三时间段和所述第四时间段中的至少一个，通过以下至少一种方式确定：
    基于所述网络侧设备发送的系统消息确定；
    基于所述网络侧设备发送的RRC消息确定。
  17. 如权利要求6、12或13所述的方法，其特征在于，还包括；
    基于定时器确定所述第二时间段、所述第三时间段和所述第四时间段中的至少一者，其中，所述定时器的定时时长等于所述第二时间段，或者所述定时器的定时时长等于所述第三时间段，或者所述定时器的定时时长等于所述第四时间段。
  18. 如权利要求17所述的方法，其特征在于，所述定时器的启动时间为以下至少一个：
    所述终端设备发送携带所述TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
    所述终端设备发送携带所述TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
  19. 如权利要求17或18所述的方法，其特征在于，还包括：
    接收所述网络侧设备发送的第三配置信息，其中，所述第三配置信息用于指示所述定时器。
  20. 如权利要求19所述的方法，其特征在于，还包括：
    向所述网络侧设备发送第三能力指示信息，其中，所述第三能力指示信息用于指示所述终端设备支持所述定时器。
  21. 如权利要求1至20中任一项所述的方法，其特征在于，还包括：
    响应于所述终端设备发送所述TAR未成功，且被配置或重配偏移阈值定时提前量TA，向所述网络侧设备发送所述TAR。
  22. 一种定时提前量报告上报方法，其特征在于，所述方法由网络侧设备执行，包括：
    接收终端设备发送的定时提前量报告TAR；
    向所述终端设备发送指示信息，其中，所述指示信息用于指示所述网络侧设备接收到所述TAR。
  23. 如权利要求22所述的方法，其特征在于，所述指示信息，包括以下至少一项：
    确认所述TAR的媒体接入控制层控制单元MAC CE；
    确认所述TAR的物理下行控制信道PDCCH；
    差分KoffsetMAC CE；
    针对发送所述TAR的混合自动重传请求HARQ过程的新传调度；
    确定所述TRA的无线资源控制RRC消息；
    与所述TAR在一个媒体接入控制层MAC协议数据单元PDU的分组数据汇聚协议PDCP PDU的确认ACK；
    与所述TAR在一个MAC PDU的无线链路控制RLC PDU的ACK。
  24. 如权利要求22或23所述的方法，其特征在于，所述向所述终端设备发送指示信息，包括：
    在第一时间段内向所述终端设备发送所述指示信息。
  25. 如权利要求22至24中任一项所述的方法，其特征在于，还包括：
    接收所述终端设备在满足重发条件的情况下，重发的所述TAR。
  26. 如权利要求25所述的方法，其特征在于，所述重发条件包括所述终端设备未接收到所述网络侧设备发送的所述指示信息。
  27. 如权利要求25所述的方法，其特征在于，所述重发条件包括所述终端设备在第二时间段内未接收到所述网络侧设备发送的所述指示信息。
  28. 如权利要求25至27中任一项所述的方法，其特征在于，所述重发条件还包括所述终端设备重发所述TAR的次数不超过门限次数。
  29. 如权利要求28所述的方法，其特征在于，还包括：
    接收所述终端设备在重发所述TAR的次数超过所述门限次数的情况下，发送的第一消息，其中，所述第一消息指示所述TAR发送失败。
  30. 如权利要求25至29中任一项所述的方法，其特征在于，所述重发条件还包括接收到所述网络侧设备发送的第一配置信息，其中，所述第一配置信息用于指示所述终端设备向所述网络侧设备重发所述TAR。
  31. 如权利要求30所述的方法，其特征在于，还包括：
    接收所述终端设备发送的第一能力指示信息，其中，所述第一能力指示信息用于指示所述终端设备支持重发所述TAR。
  32. 如权利要求30所述的方法，其特征在于，还包括：
    接收所述终端设备发送的第二能力指示信息，其中，所述第二能力指示信息用于指示所述终端设备支持取消重发所述TAR。
  33. 如权利要求24至32中任一项所述的方法，其特征在于，所述第一时间段、所述第二时间段和所述门限次数中的至少一个，通过以下至少一种方式确定：
    基于所述网络侧设备发送的系统消息确定；
    基于所述网络侧设备发送的RRC消息确定。
  34. 如权利要求27所述的方法，其特征在于，还包括；
    基于定时器确定所述第二时间段，其中，所述定时器的定时时长等于所述第二时间段。
  35. 如权利要求34所述的方法，其特征在于，所述定时器的启动时间为以下至少一个：
    所述终端设备发送携带所述TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号；
    所述终端设备发送携带所述TAR的物理上行共享信道PUSCH传输的传输束中的第一个传输结束后的第一个符号加上往返时间RTT。
  36. 如权利要求34或35所述的方法，其特征在于，还包括：
    向终端设备发送第三配置信息，其中，所述第三配置信息用于指示所述定时器。
  37. 如权利要求36所述的方法，其特征在于，还包括：
    接收所述终端设备发送的第三能力指示信息，其中，所述第三能力指示信息用于指示所述终端设备支持所述定时器。
  38. 如权利要求22至37中任一项所述的方法，其特征在于，还包括：
    接收所述终端设备在发送所述TAR未成功，且被配置或重配偏移阈值定时提前量TA的情况下，发送的所述TAR。
  39. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为向网络侧设备发送定时提前量报告TAR；
    处理模块，被配置为响应于接收到所述网络侧设备发送的指示信息，确定所述TAR发送成功，其中，所述指示信息用于指示所述网络侧设备接收到所述TAR。
  40. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为接收终端设备发送的定时提前量报告TAR；
    所述收发模块，还被配置为向所述终端设备发送指示信息，其中，所述指示信息用于指示所述网络侧设备接收到所述TAR。
  41. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至21中任一项所述的方法，或所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求22至38中任一项所述的方法。
  42. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至21中任一项所述的方法，或用于运行所述代码指令以执行如权利要求22至38中任一项所述的方法。
  43. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至21中任一项所述的方法被实现，或当所述指令被执行时，使如权利要求22至38中任一项所述的方法被实现。
PCT/CN2022/100243 2022-06-21 2022-06-21 定时提前量报告上报方法和装置 WO2023245450A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002083.0A CN115280832A (zh) 2022-06-21 2022-06-21 定时提前量报告上报方法和装置
PCT/CN2022/100243 WO2023245450A1 (zh) 2022-06-21 2022-06-21 定时提前量报告上报方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/100243 WO2023245450A1 (zh) 2022-06-21 2022-06-21 定时提前量报告上报方法和装置

Publications (1)

Publication Number Publication Date
WO2023245450A1 true WO2023245450A1 (zh) 2023-12-28

Family

ID=83757994

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/100243 WO2023245450A1 (zh) 2022-06-21 2022-06-21 定时提前量报告上报方法和装置

Country Status (2)

Country Link
CN (1) CN115280832A (zh)
WO (1) WO2023245450A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770565A (zh) * 2020-06-23 2020-10-13 中国科学院上海微系统与信息技术研究所 一种非地面网络的定时提前调整方法
GB202104780D0 (en) * 2021-04-01 2021-05-19 Nec Corp Communication system
CN113382440A (zh) * 2020-03-10 2021-09-10 联发科技（新加坡）私人有限公司 非地面网络通信中的用户设备定时提前报告
US20220086780A1 (en) * 2020-09-11 2022-03-17 FG Innovation Company Limited Reporting user equipment specific timing advance in a non-terrestrial network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113382440A (zh) * 2020-03-10 2021-09-10 联发科技（新加坡）私人有限公司 非地面网络通信中的用户设备定时提前报告
CN111770565A (zh) * 2020-06-23 2020-10-13 中国科学院上海微系统与信息技术研究所 一种非地面网络的定时提前调整方法
US20220086780A1 (en) * 2020-09-11 2022-03-17 FG Innovation Company Limited Reporting user equipment specific timing advance in a non-terrestrial network
GB202104780D0 (en) * 2021-04-01 2021-05-19 Nec Corp Communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO: ""Summary of [AT116-e][106][NTN] RACH Aspects"", 3GPP TSG-RAN WG2 MEETING #116 ELECTRONIC R2-211XXXX, 4 November 2021 (2021-11-04), XP009551811 *

Also Published As

Publication number Publication date
CN115280832A (zh) 2022-11-01

Similar Documents

Publication Publication Date Title
US20220182206A1 (en) Retransmission feedback method and device for sidelink communication, and storage medium
CN112399374B (zh) 通信方法和通信装置
WO2023279302A1 (zh) 用于非地面网络的sdt处理方法、通信装置和存储介质
WO2023108657A1 (zh) 一种位置信息的确定方法及其装置
US20200067644A1 (en) Data feedback method and related device
US20220376829A1 (en) Sidelink data transmission method and terminal device
WO2023164952A1 (zh) 一种智能中继的控制方法及其装置
WO2023155201A1 (zh) 一种位置信息的确定方法及其装置
JP7481440B2 (ja) ハイブリッド自動再送要求処理方法及び通信装置
WO2021052210A1 (zh) 混合自动重传请求的指示方法、装置及存储介质
WO2023231035A1 (zh) 一种非授权频段下传输资源的确定方法及装置
WO2023245450A1 (zh) 定时提前量报告上报方法和装置
WO2022120519A1 (zh) 部分带宽处理方法及装置
WO2022198413A1 (zh) 一种上行控制信息uci的资源映射方法及其装置
WO2024031715A1 (zh) 一种harq反馈方法及其装置
WO2024000207A1 (zh) 一种定时提前报告tar的触发方法、装置、设备及存储介质
WO2024000180A1 (zh) 一种指示方法、装置、设备及存储介质
WO2022205005A1 (zh) 一种数据接收的处理方法及其装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
US20240032028A1 (en) Cg resource processing method, terminal device, and network device
WO2023097630A1 (zh) 混合自动重传的时隙偏移的确定、指示方法及装置
WO2023122988A1 (zh) 一种定时器同步方法及其装置
WO2022217448A1 (zh) 一种上行控制信息的复用方法及其装置
WO2024065095A1 (zh) 指示方法、装置、设备及存储介质
WO2023133742A1 (zh) 物理下行共享信道的处理时间参数的确定方法及装置

Legal Events

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

Ref document number: 22947230

Country of ref document: EP

Kind code of ref document: A1