WO2022077174A1 - 无线通信方法和设备 - Google Patents

无线通信方法和设备 Download PDF

Info

Publication number
WO2022077174A1
WO2022077174A1 PCT/CN2020/120456 CN2020120456W WO2022077174A1 WO 2022077174 A1 WO2022077174 A1 WO 2022077174A1 CN 2020120456 W CN2020120456 W CN 2020120456W WO 2022077174 A1 WO2022077174 A1 WO 2022077174A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink
timer
uplink
rtt
rtt timer
Prior art date
Application number
PCT/CN2020/120456
Other languages
English (en)
French (fr)
Inventor
李海涛
胡奕
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080103165.5A priority Critical patent/CN115868132B/zh
Priority to PCT/CN2020/120456 priority patent/WO2022077174A1/zh
Publication of WO2022077174A1 publication Critical patent/WO2022077174A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the embodiments of the present application relate to the field of communication, and more particularly, to wireless communication methods and devices.
  • both the uplink and the downlink in the New Radio support the Hybrid Automatic Repeat Request (HARQ) mechanism.
  • HARQ Hybrid Automatic Repeat Request
  • the terminal device will first start an uplink discontinuous reception (Discontinuous Reception, DRX) HARQ round trip transmission time (Round Trip Time, RTT) timer (drx-HARQ-RTT-TimerUL) after completing the uplink transmission.
  • DRX Downlink discontinuous reception
  • RTT Red Trip Time
  • the terminal After completing the feedback of the HARQ process for downlink transmission, the device will first start a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL).
  • the terminal device is in a dormant state during the running period of drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL, and does not monitor PDCCH.
  • the terminal device After the drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL times out, the terminal device starts monitoring the uplink retransmission schedule or determines whether to start monitoring the downlink retransmission schedule according to the feedback.
  • drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL is related to RTT and the processing time of the network device.
  • Non-terrestrial communication network Non Terrestrial Network, NTN
  • communication services can be provided to terrestrial users by means of satellite communication.
  • a satellite can cover a large ground and orbit the earth.
  • the signal propagation delay between user equipment (UE) and satellites in the NTN network is greatly increased, which makes the HARQ process in NR unable to meet the needs of the NTN network.
  • the running time of drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL is increased, thereby increasing the power consumption of the terminal device.
  • the embodiments of the present application provide a wireless communication method and device, which can not only ensure the continuity of data transmission without increasing the number of HARQ processes, but also be suitable for reducing the power consumption of terminal devices.
  • a wireless communication method including:
  • the physical downlink shared channel PDSCH used for scheduling downlink transmission, or the last repeated transmission of the PDSCH start or restart the downlink round-trip transmission time RTT timer;
  • the downlink retransmission timer is started or restarted.
  • a wireless communication method including:
  • the uplink retransmission timer is started or restarted.
  • a terminal device for executing the method in the above-mentioned first aspect or each implementation manner thereof.
  • the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.
  • a terminal device for executing the method in the second aspect or each of its implementations.
  • the terminal device includes a functional module for executing the method in the second aspect or each implementation manner thereof.
  • a terminal device including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for invoking and running the computer program stored in the memory, so as to execute the method in any one of the above-mentioned first aspect to the second aspect or the respective implementations thereof.
  • a chip for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the chip includes: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes any one of the above-mentioned first to second aspects or each of its implementations method in .
  • a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute the method in any one of the above-mentioned first aspect to the second aspect or each of its implementations.
  • a computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above-mentioned first to second aspects or the implementations thereof.
  • a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-mentioned first to second aspects or the respective implementations thereof.
  • the monitoring duration of the scheduling information can be reduced. Accordingly, not only the running time of the downlink RTT timer can be reduced, but also the power consumption of the terminal device can be reduced. It can also ensure data transmission continuity without increasing the number of HARQ processes.
  • 1 to 3 are examples of application scenarios of the present application.
  • FIG. 4 is a schematic block diagram of a DRX according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.
  • 6 to 8 are schematic diagrams of starting a downlink RTT timer and a downlink retransmission timer provided by an embodiment of the present application.
  • FIG. 9 is another schematic flowchart of a wireless communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of starting an uplink RTT timer and an uplink retransmission timer provided by an embodiment of the present application.
  • FIG. 11 and FIG. 12 are schematic block diagrams of terminal devices provided by embodiments of the present application.
  • FIG. 13 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a chip provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • the communication system 100 may include a terminal device 110 and a network device 120 .
  • the network device 120 may communicate with the terminal device 110 through the air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120 .
  • the embodiment of the present application only uses the communication system 100 for exemplary description, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (Long Term Evolution, LTE) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile communication system (Universal mobile communication system) Mobile Telecommunication System, UMTS), 5G communication system (also known as New Radio (New Radio, NR) communication system), or future communication systems, etc.
  • LTE Long Term Evolution
  • TDD Time Division Duplex
  • Universal mobile communication system Universal mobile communication system
  • Mobile Telecommunication System Universal mobile communication system
  • UMTS Universal mobile communication system
  • 5G communication system also known as New Radio (New Radio, NR) communication system
  • future communication systems etc.
  • the network device 120 may be an access network device that communicates with the terminal device 110 .
  • An access network device may provide communication coverage for a particular geographic area, and may communicate with terminal devices 110 (eg, UEs) located within the coverage area.
  • the network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, Or a base station (gNB) in an NR system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable Devices, hubs, switches, bridges, routers, or network devices in the future evolved Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the terminal device 110 may be any terminal device, which includes, but is not limited to, a terminal device that adopts a wired or wireless connection with the network device 120 or other terminal devices.
  • the terminal equipment 110 may refer to an access terminal, a user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, user agent, or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, end devices in 5G networks or end devices in future evolved networks, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device 110 may be used for device-to-device (Device to Device, D2D) communication.
  • D2D Device to Device
  • the wireless communication system 100 may further include a core network device 130 that communicates with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an Access and Mobility Management Function (Access and Mobility Management Function). , AMF), another example, authentication server function (Authentication Server Function, AUSF), another example, user plane function (User Plane Function, UPF), another example, session management function (Session Management Function, SMF).
  • the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of an LTE network, for example, a session management function+core network data gateway (Session Management Function+Core Packet Gateway, SMF+PGW- C) Equipment.
  • EPC evolved packet core
  • the SMF+PGW-C can simultaneously implement the functions that the SMF and the PGW-C can implement.
  • the above-mentioned core network equipment may also be called by other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in this embodiment of the present application.
  • the various functional units in the communication system 100 may also establish a connection through a next generation network (next generation, NG) interface to implement communication.
  • NG next generation network
  • the terminal equipment establishes an air interface connection with the access network equipment through the NR interface to transmit user plane data and control plane signaling; the terminal equipment can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); access Network equipment, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network equipment can establish a control plane signaling with the AMF through the NG interface 2 (N2 for short).
  • gNB next generation wireless access base station
  • UPF can establish a control plane signaling connection with SMF through NG interface 4 (N4 for short); UPF can exchange user plane data with the data network through NG interface 6 (N6 for short); AMF can communicate with SMF through NG interface 11 (N11 for short)
  • the SMF establishes a control plane signaling connection; the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).
  • FIG. 1 exemplarily shows one base station, one core network device and two terminal devices.
  • the wireless communication system 100 may include multiple base station devices and the coverage area of each base station may include other numbers of terminals equipment, which is not limited in this embodiment of the present application.
  • the above communication system 100 can be applied to NTN networks.
  • the NTN network can provide communication services to terrestrial users by means of satellite communication. Compared with terrestrial cellular network communication, satellite communication has many unique advantages.
  • satellite communication is not limited by the user's geographical area.
  • general land communication cannot cover areas such as oceans, mountains, deserts, etc. where communication equipment cannot be set up or cannot be covered due to sparse population.
  • satellite communication due to a single Satellites can cover a large ground, and satellites can orbit around the earth, so theoretically every corner of the earth can be covered by satellite communications.
  • satellite communication has great social value. Satellite communications can be covered at low cost in remote mountainous areas and poor and backward countries or regions, so that people in these regions can enjoy advanced voice communication and mobile Internet technologies, which is conducive to narrowing the digital divide with developed regions and promoting development in these areas.
  • the satellite communication distance is long, and the communication cost does not increase significantly when the communication distance increases; finally, the satellite communication has high stability and is not limited by natural disasters.
  • FIG. 2 is a schematic structural diagram of another communication system provided by an embodiment of the present application.
  • a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102 .
  • the network formed between the terminal device 1101 and the satellite 1102 may also be referred to as NTN.
  • the satellite 1102 can function as a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. Under the system architecture, satellite 1102 may be referred to as a network device.
  • the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, which are not limited in this embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of another communication system provided by an embodiment of the present application.
  • the terminal device 1201 and the satellite 1202 can communicate wirelessly, and the satellite 1202 and the base station 1203 can communicate.
  • the network formed between the terminal device 1201, the satellite 1202 and the base station 1203 may also be referred to as NTN.
  • the satellite 1202 may not have the function of the base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed through the satellite 1202 .
  • the base station 1203 may be referred to as a network device.
  • the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices, which are not limited in this embodiment of the present application.
  • the network device 1203 may be the network device 120 in FIG. 1 .
  • satellite 1102 or satellite 1202 includes but is not limited to:
  • Satellites can use multiple beams to cover the ground. For example, a satellite can form dozens or even hundreds of beams to cover the ground. In other words, a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers to ensure satellite coverage and increase the system capacity of the entire satellite communication system.
  • the altitude range of LEO can be 500km to 1500km
  • the corresponding orbital period can be about 1.5 hours to 2 hours
  • the signal propagation delay of single-hop communication between users can generally be less than 20ms
  • the maximum satellite visibility time can be 20 minutes
  • LEO The signal propagation distance is short and the link loss is small, and the transmit power requirements of the user terminal are not high.
  • the orbital height of GEO can be 35786km
  • the rotation period around the earth can be 24 hours
  • the signal propagation delay of single-hop communication between users can generally be 250ms.
  • FIG. 1 to FIG. 3 only illustrate systems to which the present application applies in the form of examples, and of course, the methods shown in the embodiments of the present application may also be applied to other systems.
  • system and “network” are often used interchangeably herein.
  • the term “and/or” in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases.
  • packet-based data streams can be transmitted between end devices and network devices, however, packet-based data streams are usually bursty.
  • the end device has data transmission for a period of time, but no data transmission for a longer period of time next. Therefore, if the terminal device has been blindly checking the physical downlink control channel (Physical Downlink Control Channel, PDCCH), the power consumption of the terminal device will be too large.
  • PDCCH Physical Downlink Control Channel
  • the network device can configure a discontinuous reception (Discontinuous Reception, DRX) function for the terminal device, so that the terminal device can monitor the PDCCH discontinuously, so as to achieve the purpose of saving power of the terminal.
  • DRX discontinuous Reception
  • the network can configure the terminal to wake up at the time predicted by the network (DRX ON), and the terminal monitors the downlink control channel; at the same time, the network can also configure the terminal to sleep at the time predicted by the network (DRX OFF), that is, the terminal The device does not need to monitor the downlink control channel.
  • the network device can schedule the terminal device during the time when the terminal device is in DRX ON, and during the DRX OFF time, because the radio frequency is turned off, the power consumption of the terminal can be reduced.
  • a media access control (Media Access Control, MAC) entity entity
  • MAC Media Access Control
  • RRC Radio Resource Control
  • FIG. 4 is a schematic block diagram of DRX provided by an embodiment of the present application.
  • the DRX cycle configured by the network device for the terminal device consists of an activation period (On Duration) and a sleep period (Opportunity for DRX).
  • On Duration activation period
  • Opportunity for DRX the DRX cycle configured by the network device for the terminal device
  • the MAC entity can monitor and receive the PDCCH within the On Duration time; during the Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption.
  • the terminal device in the dormant period in this embodiment of the present application does not receive the PDCCH, but can receive data from other physical channels.
  • This embodiment of the present invention is not specifically limited.
  • the terminal device may receive a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), acknowledgment/non-acknowledgement (ACK/NACK), and the like.
  • PDSCH Physical Downlink Shared Channel
  • ACK/NACK acknowledgment/non-acknowledgement
  • SPS semi-persistent scheduling
  • the terminal device may receive periodically configured PDSCH data.
  • the configuration parameters for DRX include:
  • DRX active period timer (drx-onDurationTimer): the duration at the beginning of a DRX Cycle (the duration at the beginning of a DRX Cycle).
  • DRX slot offset timer (drx-SlotOffset): the delay before starting the drx-onDurationTimer (the delay before starting the drx-onDurationTimer).
  • DRX-InactivityTimer The duration after the PDCCH occasion in which a PDCCH indicates a new UL or DL transmission for the MAC entity).
  • DRX downlink retransmission timer (drx-RetransmissionTimerDL): the maximum duration until a DL retransmission is received before receiving DL retransmission; each DL HARQ process except the broadcast process (per DL HARQ process except for the broadcast process).
  • DRX Uplink Retransmission Timer (drx-RetransmissionTimerUL): The maximum duration until a grant for UL retransmission is received before the UL grant is received; per UL HARQ process.
  • DRX long cycle start offset (drx-LongCycleStartOffset): The Long DRX cycle and drx-StartOffset are used to define the subframe where the Long DRX cycle and the short DRX cycle start (the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX Cycle starts).
  • DRX short cycle (drx-ShortCycle), can be used as an optional parameter.
  • DRX Short Cycle Timer (drx-ShortCycleTimer): The duration the UE shall follow the Short DRX cycle; the DRX Short Cycle Timer can be used as an optional parameter.
  • DRX Downlink HARQ RTT Timer (drx-HARQ-RTT-TimerDL): The minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity) ;per DL HARQ process except for the broadcast process.
  • DRX Uplink HARQ RTT Timer (drx-HARQ-RTT-TimerUL): The minimum duration before a UL HARQ retransmission grant is expected by the MAC entity.
  • the terminal device If the terminal device is configured with DRX, it needs to monitor the PDCCH during the DRX activation period.
  • the DRX activation period includes the following situations:
  • the SR is sent on the PUCCH and is in a pending state.
  • the terminal device has not received an initial transmission indicated by the PDCCH scrambled by the C-RNTI after successfully receiving the random access response.
  • the conditions for the terminal device to start or restart the drx-InactivityTimer are:
  • the terminal If the terminal receives a PDCCH indicating downlink or uplink initial transmission, the terminal starts or restarts the drx-InactivityTimer.
  • the terminal When the terminal receives a PDCCH indicating downlink transmission, or when the terminal receives a MAC PDU on the configured downlink grant resource, the terminal stops the drx-RetransmissionTimerDL corresponding to the HARQ process. The terminal starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process after completing the transmission of the HARQ process feedback for this downlink transmission.
  • the terminal If the timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ of the terminal times out, and the decoding of downlink data transmitted using this HARQ process is unsuccessful, the terminal starts the drx-RetransmissionTimerDL corresponding to this HARQ process.
  • the terminal When the terminal receives a PDCCH indicating uplink transmission, or when the terminal sends a MAC PDU on the configured uplink grant resource, the terminal stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first repetition of the PUSCH.
  • the terminal device will first start an uplink discontinuous reception (Discontinuous Reception, DRX) HARQ round trip transmission time (Round Trip Time, RTT) timer (drx-HARQ-RTT-TimerUL) after completing the uplink transmission, similar to , the terminal device will first start a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL) after completing the feedback of the HARQ process for downlink transmission.
  • the terminal device is in a dormant state during the running period of drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL, and does not monitor PDCCH.
  • the terminal device After the drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL times out, the terminal device starts monitoring the uplink retransmission schedule or determines whether to start monitoring the downlink retransmission schedule according to the feedback.
  • drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL is related to RTT and the processing time of the network device.
  • Non-terrestrial communication network Non Terrestrial Network, NTN
  • communication services can be provided to terrestrial users by means of satellite communication.
  • a satellite can cover a large ground and orbit the earth.
  • the signal propagation delay between user equipment (UE) and satellites in the NTN network is greatly increased, which makes the HARQ process in NR unable to meet the needs of the NTN network.
  • the running time of drx-HARQ-RTT-TimerUL or drx-HARQ-RTT-TimerDL is increased, thereby increasing the power consumption of the terminal device.
  • FIG. 5 shows a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application, and the method 200 may be executed by a terminal device.
  • the terminal device shown in FIG. 5 may be the terminal device shown in FIG. 1 .
  • the method 200 may include:
  • the monitoring duration of the scheduling information can be reduced. Accordingly, not only the running time of the downlink RTT timer can be reduced to reduce the power consumption of the terminal device, but also it can be ensured The continuity of data transmission is guaranteed when the number of HARQ processes is increased.
  • the implementation manner of the downlink RTT timer is not specifically limited in this embodiment of the present application.
  • the downlink RTT timer may also be called drx-HARQ-RTT-TimerDL, instead of drx-HARQ-RTT-TimerDL in NR.
  • the downlink RTT timer may also be a redefined RTT timer, that is, a timer different from drx-HARQ-RTT-TimerDL in NR.
  • the function of the downlink RTT timer may be combined, attached or added to the drx-HARQ-RTT-TimerDL in the NR.
  • both the downlink RTT timer and the downlink retransmission timer are associated with a downlink HARQ process in which the hybrid automatic repeat request HARQ feedback function is disabled.
  • the network device may continue to schedule retransmission of downlink transmission before receiving the feedback information for downlink transmission.
  • the terminal device may receive the PDSCH transmission scheduled for downlink continuously (or at a certain interval).
  • associating both the downlink RTT timer and the downlink retransmission timer to a downlink HARQ process in which the HARQ feedback function of HARQ is disabled not only can the HARQ feedback function be disabled, so that the terminal device does not need to report to the network device.
  • Sending the HARQ feedback information for the PDSCH can also enable the terminal device to still support HARQ retransmission when the HARQ feedback function is turned off, thereby ensuring the reliability of data transmission.
  • the duration of the downlink RTT timer is determined according to the time diversity setting and/or the processing delay of the network device.
  • the duration of the downlink RTT timer may be used to reflect the minimum time interval required by the terminal device from downlink transmission to receiving the retransmission scheduling sent by the network device.
  • the minimum time interval is determined according to the RTT and/or the processing time of the network device.
  • the duration of the downlink RTT timer may depend on the implementation of the network device. For example, network equipment needs to introduce a certain time interval into two consecutive PDCCH scheduling when blindly scheduling retransmission. The time interval depends on the processing delay of the network equipment on the one hand, and the time diversity effect on the other hand. The transmission takes a period of time. If the downlink RTT timer is sufficiently small, between a PDCCH and PDSCH transmission, the network device can transmit other scheduling information of the same HARQ process.
  • the method 200 may further include:
  • Receive configuration information the configuration information is used to configure at least one of the following timers:
  • the discontinuous reception DRX cycle, the active period timer, the deactivation timer, the downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer is not limited to, the active period timer, the deactivation timer, the downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer.
  • the terminal device may receive RRC configuration information sent by the network device.
  • the RRC configuration information may include DRX related parameters and/or MAC main configuration.
  • DRX related parameters include but are not limited to:
  • DRX cycle (DRX cycle), DRX activation period timer (drx-onDurationTimer), deactivation timer (drx-InactivityTimer), the downlink RTT timer (drx-HARQ-RTT-TimerDL), uplink RTT timer (drx -HARQ-RTT-TimerUL), the downlink retransmission timer (drx-RetransmissionTimerDL) or the uplink retransmission timer (drx-RetransmissionTimerUL).
  • the MAC main configuration may include information for configuring whether to disable the HARQ feedback function for all or part of the HARQ processes.
  • the terminal device receives the configuration information of the downlink RTT timer and the downlink retransmission timer to start or restart the downlink RTT timer and the downlink retransmission timer based on the configuration information of the downlink RTT timer and the downlink retransmission timer .
  • the PDSCH is scheduled by the PDCCH, or the PDSCH is preconfigured.
  • the PDSCH may also be scheduled by other PDCCHs.
  • the method 200 may further include:
  • scheduling information for scheduling downlink transmission is received.
  • the terminal device receives scheduling information for scheduling downlink retransmission (Retransmission).
  • the terminal device receives scheduling information for scheduling new downlink transmissions during the running period of the downlink retransmission timer.
  • the downlink retransmission timer may directly Called the downlink transmission timer.
  • the S210 may include:
  • the downlink RTT timer is started or restarted, and the downlink retransmission timer is stopped.
  • FIG. 6 is a schematic diagram of starting a downlink RTT timer and a downlink retransmission timer provided by an embodiment of the present application.
  • the terminal device After receiving the DL assignment (assignment), that is, the PDCCH, the terminal device starts or restarts the downlink RTT timer associated with the downlink HARQ process; at the same time, the described The terminal device may also stop the downlink retransmission timer associated with the downlink HARQ process.
  • the DL assignment that is, the PDCCH
  • the terminal device may start or restart the downlink retransmission timer of the downlink HARQ process.
  • FIG. 6 is only an example of the present application, and should not be construed as a limitation of the present application.
  • the multiple repetition (repetition) transmission of the PDSCH shown in FIG. 6 may be dynamically scheduled, for example, the PDCCH shown in FIG. 6 is scheduled; in other alternative embodiments, it may also be pre-configured , which can be scheduled by SPS, for example.
  • the multiple repeated transmissions of the PDSCH shown in FIG. 6 are continuous, and in other alternative embodiments, they may also be spaced.
  • the PDCCH shown in FIG. 6 is used to schedule repeated transmission of PDSCH, and in other alternative embodiments, it can also be used to schedule other newly transmitted PDSCH.
  • the S210 may include:
  • the downlink RTT timer is started or restarted.
  • FIG. 7 is a schematic diagram of starting a downlink RTT timer and a downlink retransmission timer provided by an embodiment of the present application.
  • the terminal device After the terminal device receives the DL assignment (assignment), that is, the PDCCH, the terminal device stops the downlink retransmission timer associated with the downlink HARQ process; After the first repetition (repetition) transmission of the PDSCH, the downlink RTT timer associated with the downlink HARQ process is started or restarted.
  • the DL assignment that is, the PDCCH
  • the terminal device may start or restart the downlink retransmission timer of the downlink HARQ process.
  • FIG. 7 is only an example of the present application and should not be construed as a limitation of the present application.
  • the terminal device after receiving the last repetition (repetition) transmission of the PDSCH, the terminal device starts or restarts the downlink RTT timer associated with the downlink HARQ process.
  • the multiple repetition (repetition) transmission of the PDSCH shown in FIG. 7 may be dynamically scheduled, for example, the PDCCH shown in FIG. 7 is scheduled; in other alternative embodiments, it may also be pre-configured , which can be scheduled by SPS, for example.
  • the multiple repeated transmissions of the PDSCH shown in FIG. 7 are continuous, and in other alternative embodiments, they may also be spaced.
  • the PDCCH shown in FIG. 7 is used for scheduling repeated transmission of PDSCH, and in other alternative embodiments, it can also be used for scheduling other newly transmitted PDSCH.
  • the S210 may include:
  • the downlink RTT timer is started or restarted, and the downlink retransmission timer is stopped.
  • FIG. 8 is a schematic diagram of starting a downlink RTT timer and a downlink retransmission timer provided by an embodiment of the present application.
  • the terminal device starts or restarts the downlink RTT timer associated with the downlink HARQ process after receiving the first repetition transmission of the PDSCH; at the same time, The terminal device may also stop the downlink retransmission timer associated with the downlink HARQ process.
  • the terminal device may start or restart the downlink retransmission timer of the downlink HARQ process.
  • FIG. 8 is only an example of the present application and should not be construed as a limitation of the present application.
  • the terminal device after receiving the last repetition transmission of the PDSCH, the terminal device starts or restarts the downlink RTT timer associated with the downlink HARQ process; at the same time, the terminal device can also Stop the downlink retransmission timer associated with the downlink HARQ process.
  • the multiple repetition (repetition) transmission of the PDSCH shown in FIG. 8 may be dynamically scheduled, for example, the PDCCH shown in FIG. 8 is scheduled; in other alternative embodiments, it may also be pre-configured , which can be scheduled by SPS, for example.
  • the multiple repeated transmissions of the PDSCH shown in FIG. 8 are continuous, and in other alternative embodiments, they may also be spaced.
  • the PDCCH shown in FIG. 8 is used to schedule the repeated transmission of the PDSCH, and in other alternative embodiments, it can also be used to schedule other newly transmitted PDSCHs.
  • FIG. 9 shows a schematic flowchart of a wireless communication method 300 according to an embodiment of the present application, and the method 300 may be executed by a terminal device.
  • the terminal device shown in FIG. 9 may be the terminal device shown in FIG. 1 .
  • the method 300 may include:
  • the monitoring duration of the scheduling information can be reduced, and accordingly, not only can the running time of the uplink RTT timer be reduced to reduce the power consumption of the terminal equipment, but also it can be ensured The continuity of data transmission is guaranteed when the number of HARQ processes is increased.
  • the implementation manner of the uplink RTT timer is not specifically limited in this embodiment of the present application.
  • the uplink RTT timer may also be called drx-HARQ-RTT-TimerUL to replace drx-HARQ-RTT-TimerUL in NR.
  • the uplink RTT timer may also be a redefined RTT timer, that is, a timer different from drx-HARQ-RTT-TimerUL in NR.
  • the function of the uplink RTT timer may be combined, attached or added to the drx-HARQ-RTT-TimerUL in the NR.
  • both the uplink RTT timer and the uplink retransmission timer are associated with an uplink HARQ process in which the hybrid automatic repeat request HARQ feedback function is disabled.
  • the network device may continue to schedule retransmission of uplink transmission before receiving uplink transmission.
  • the terminal equipment depends on the implementation of the network equipment.
  • the terminal equipment can receive uplink transmission scheduling continuously (or at certain intervals), for example, it can receive the uplink grant scheduled by the same HARQ process before sending the first PUSCH.
  • the terminal equipment can still support the HARQ feedback function when the HARQ feedback function is disabled. HARQ retransmission, thereby ensuring the reliability of data transmission.
  • the duration of the uplink RTT timer is determined according to the time diversity setting and/or the processing delay of the network device.
  • the duration of the uplink RTT timer may be used to reflect the minimum time interval required by the terminal device from uplink transmission to receiving the retransmission scheduling sent by the network device.
  • the minimum time interval is determined according to the RTT and/or the processing time of the network device.
  • the duration of the uplink RTT timer may depend on the implementation of the network device. For example, network equipment needs to introduce a certain time interval into two consecutive PDCCH scheduling when blindly scheduling retransmission. The time interval depends on the processing delay of the network equipment on the one hand, and the time diversity effect on the other hand. The transmission takes a period of time. If the uplink RTT timer is small enough, between a PDCCH and PDSCH transmission, the network device can transmit other scheduling information of the same HARQ process.
  • the method 300 may further include:
  • Receive configuration information the configuration information is used to configure at least one of the following timers:
  • Discontinuous reception DRX cycle active period timer, deactivation timer, downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer.
  • the terminal device may receive RRC configuration information sent by the network device.
  • the RRC configuration information may include DRX related parameters and/or MAC main configuration.
  • DRX related parameters include but are not limited to:
  • DRX cycle (DRX cycle), DRX activation period timer (drx-onDurationTimer), deactivation timer (drx-InactivityTimer), downlink RTT timer (drx-HARQ-RTT-TimerDL), uplink RTT timer (drx-HARQ -RTT-TimerUL), downlink retransmission timer (drx-RetransmissionTimerDL) or uplink retransmission timer (drx-RetransmissionTimerUL).
  • the MAC main configuration may include information for configuring whether to disable the HARQ feedback function for all or part of the HARQ processes.
  • the terminal device receives the configuration information of the uplink RTT timer and the uplink retransmission timer to start or restart the uplink RTT timer and the uplink retransmission timer based on the configuration information of the uplink RTT timer and the uplink retransmission timer .
  • the method 300 may further include:
  • scheduling information for scheduling uplink transmission is received.
  • the terminal device receives scheduling information for scheduling uplink retransmission (Retransmission). It should be understood that, in other alternative embodiments, the terminal device receives scheduling information for scheduling new uplink transmissions during the running period of the uplink retransmission timer. In this case, the uplink retransmission timer may directly It is called the upstream transmission timer.
  • the S310 may include:
  • the uplink round trip transmission time RTT timer is started or restarted, and the uplink retransmission timer is stopped.
  • FIG. 10 is a schematic diagram of starting an uplink RTT timer and an uplink retransmission timer provided by an embodiment of the present application.
  • the terminal device After receiving the uplink grant (UL grant), that is, the PDCCH, the terminal device starts or restarts the uplink RTT timer associated with the uplink HARQ process; at the same time, all The terminal device may also stop the uplink retransmission timer associated with the uplink HARQ process.
  • UL grant UL grant
  • the terminal device may also stop the uplink retransmission timer associated with the uplink HARQ process.
  • the terminal device may start or restart the uplink retransmission timer of the uplink HARQ process.
  • FIG. 10 is only an example of the present application, and should not be construed as a limitation of the present application.
  • the terminal device after receiving the first or last repetition transmission of the PDSCH, the terminal device starts or restarts the uplink RTT timer associated with the uplink HARQ process; at the same time, the The terminal device may also stop the uplink retransmission timer associated with the uplink HARQ process.
  • the multiple repetition (repetition) transmission of the PDSCH shown in FIG. 10 may be dynamically scheduled, for example, the PDCCH shown in FIG. 10 is scheduled; in other alternative embodiments, it may also be pre-configured , which can be scheduled by SPS, for example.
  • the multiple repeated transmissions of the PDSCH shown in FIG. 10 are continuous, and in other alternative embodiments, they may also be spaced.
  • the PDCCH shown in FIG. 10 is used to schedule repeated transmission of PDSCH, and in other alternative embodiments, it can also be used to schedule other newly transmitted PDSCH.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the present application.
  • the implementation of the embodiments constitutes no limitation.
  • the terms “downlink” and “uplink” are used to indicate the transmission direction of signals or data, wherein “downlink” is used to indicate that the transmission direction of signals or data is from the site to the user equipment of the cell In the first direction, “uplink” is used to indicate that the transmission direction of the signal or data is the second direction sent from the user equipment of the cell to the site.
  • downlink signal indicates that the transmission direction of the signal is the first direction.
  • the term “and/or” is only an association relationship for describing associated objects, indicating that there may be three kinds of relationships. Specifically, A and/or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/" in this document generally indicates that the related objects are an "or" relationship.
  • FIG. 11 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 may include a processing unit 410, and the processing unit 410 is specifically configured to:
  • the physical downlink shared channel PDSCH used for scheduling downlink transmission, or the last repeated transmission of the PDSCH start or restart the downlink round-trip transmission time RTT timer;
  • both the downlink RTT timer and the downlink retransmission timer are associated with a downlink HARQ process in which the hybrid automatic repeat request HARQ feedback function is disabled.
  • the processing unit 410 is specifically configured to:
  • the downlink RTT timer is started or restarted, and the downlink retransmission timer is stopped.
  • the processing unit 410 is specifically configured to:
  • the downlink RTT timer is started or restarted.
  • the processing unit 410 is specifically configured to:
  • the downlink RTT timer is started or restarted, and the downlink retransmission timer is stopped.
  • the PDSCH is scheduled by the PDCCH, or the PDSCH is preconfigured.
  • the duration of the downlink RTT timer is determined according to the time diversity setting and/or the processing delay of the network device.
  • the processing unit 410 is further configured to:
  • Receive configuration information the configuration information is used to configure at least one of the following timers:
  • the discontinuous reception DRX cycle, the active period timer, the deactivation timer, the downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer is not limited to, the active period timer, the deactivation timer, the downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer.
  • the processing unit 410 is further configured to:
  • scheduling information for scheduling downlink transmission is received.
  • the apparatus embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments.
  • the terminal device 400 shown in FIG. 11 may correspond to the corresponding subject in executing the method 200 of the embodiment of the present application, and the aforementioned and other operations and/or functions of the various units in the terminal device 400 are respectively for the purpose of realizing the method shown in FIG. 5 .
  • the corresponding processes in each of the methods are not repeated here.
  • FIG. 12 is a schematic block diagram of a terminal device 500 provided by an embodiment of the present application.
  • the terminal device includes a processing unit 510, and the processing unit 510 is configured to:
  • the uplink retransmission timer is started or restarted.
  • both the uplink RTT timer and the uplink retransmission timer are associated with an uplink HARQ process in which the hybrid automatic repeat request HARQ feedback function is disabled.
  • the processing unit 510 is specifically configured to:
  • the uplink round trip transmission time RTT timer is started or restarted, and the uplink retransmission timer is stopped.
  • the duration of the uplink RTT timer is determined according to the time diversity setting and/or the processing delay of the network device.
  • processing unit 510 is further configured to:
  • Receive configuration information the configuration information is used to configure at least one of the following timers:
  • Discontinuous reception DRX cycle active period timer, deactivation timer, downlink RTT timer, the uplink RTT timer, the downlink retransmission timer or the uplink retransmission timer.
  • processing unit 510 is further configured to:
  • scheduling information for scheduling uplink transmission is received.
  • the apparatus embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments.
  • the terminal device 500 shown in FIG. 12 may correspond to the corresponding subject in executing the method 300 of the embodiment of the present application, and the aforementioned and other operations and/or functions of the various units in the terminal device 500 are respectively for the purpose of realizing the method shown in FIG. 9 .
  • the corresponding processes in each of the methods are not repeated here.
  • the steps of the method embodiments in the embodiments of the present application may be completed by an integrated logic circuit of hardware in the processor and/or instructions in the form of software, and the steps of the methods disclosed in combination with the embodiments of the present application may be directly embodied as hardware
  • the execution of the decoding processor is completed, or the execution is completed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.
  • processing unit referred to above may be implemented by a processor.
  • FIG. 8 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device 600 may include a processor 610 .
  • the processor 610 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.
  • the communication device 600 may further include a memory 620 .
  • the memory 620 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 610 .
  • the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may also include a transceiver 630 .
  • the processor 610 can control the transceiver 630 to communicate with other devices, and specifically, can send information or data to other devices, or receive information or data sent by other devices.
  • Transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • each component in the communication device 600 is connected through a bus system, wherein the bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • the communication device 600 may be a terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application.
  • the communication device 600 may correspond to the terminal device 400 or the terminal device 500 in the embodiment of the present application, and may correspond to the corresponding subject in executing the method 200 or 300 according to the embodiment of the present application, which is not repeated here for brevity.
  • the embodiment of the present application also provides a chip.
  • the chip may be an integrated circuit chip, which has a signal processing capability, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • the chip may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • FIG. 9 is a schematic structural diagram of a chip 700 according to an embodiment of the present application.
  • the chip 700 includes a processor 710 .
  • the processor 710 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be used to store instruction information, and may also be used to store codes, instructions and the like executed by the processor 710 .
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip 700 can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, and can also implement the various methods of the embodiments of the present application.
  • the corresponding process implemented by the terminal device in FIG. 1 is not repeated here.
  • bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.
  • the processors referred to above may include, but are not limited to:
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the processor may be used to implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory mentioned above includes but is not limited to:
  • Non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Random Access Memory
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium stores one or more programs including instructions that, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform any of the methods 200 or 300. method of an example.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , for brevity, will not be repeated here.
  • the embodiments of the present application also provide a computer program product, including a computer program.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program When the computer program is executed by a computer, the computer can execute the method of the embodiment shown in method 200 or 300 .
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • an embodiment of the present application further provides a communication system, which may include the above-mentioned terminal equipment and network equipment to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity.
  • a communication system which may include the above-mentioned terminal equipment and network equipment to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity.
  • system and the like in this document may also be referred to as “network management architecture” or “network system” and the like.
  • a software functional unit If implemented in the form of a software functional unit and sold or used as a stand-alone product, it may be stored in a computer-readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art or the parts of the technical solutions, and the computer software products are stored in a storage medium , which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.
  • division of units, modules or components in the apparatus embodiments described above is only a logical function division, and other division methods may be used in actual implementation.
  • multiple units, modules or components may be combined or integrated.
  • To another system, or some units or modules or components can be ignored, or not implemented.
  • the above-mentioned units/modules/components described as separate/display components may or may not be physically separated, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units/modules/components may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

Landscapes

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

Abstract

本申请实施例提供了一种无线通信方法和设备。所述方法包括：在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。通过重新定义所述下行RTT定时器的启动条件，不仅能够在不增加HARQ进程数目的情况下保证数据传输连续性，还能够适用于降低终端设备的功耗。

Description

无线通信方法和设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及无线通信方法和设备。
背景技术
截止目前，新空口(New Radio,NR)中的上行和下行都支持混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)机制。
例如，终端设备在完成上行传输后会先启动一个上行非连续接收(Discontinuous Reception，DRX)HARQ往返传输时间(Round Trip Time，RTT)定时器(drx-HARQ-RTT-TimerUL)，类似的，终端设备在完成针对下行传输的HARQ进程的反馈后会先启动一个下行DRX HARQ RTT定时器(drx-HARQ-RTT-TimerDL)。终端设备在drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL的运行期间内处于休眠状态，不监听PDCCH。等drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL超时后终端设备才开始监听上行重传调度或者根据反馈情况确定是否开始监听下行重传调度。
其中，drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL和RTT以及网络设备的处理时间相关。
但是，而针对非地面通信网络(Non Terrestrial Network，NTN)技术，可以采用卫星通信的方式向地面用户提供通信服务。例如，一颗卫星即可以覆盖较大的地面，且可以围绕地球做轨道运动。
与传统NR采用的蜂窝网络相比，NTN网络中的用户设备(User Equipment，UE)与卫星之间的信号传播时延大幅增加，导致NR中的HARQ进程满足不了NTN网络的需求。此外，增加了drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL的运行时间，进而增加了终端设备的功耗。
发明内容
本申请实施例提供一种无线通信方法和设备，不仅能够在不增加HARQ进程数目的情况下保证数据传输连续性，还能够适用于降低终端设备的功耗。
第一方面，提供了一种无线通信方法，包括：
在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；
在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。
第二方面，提供了一种无线通信方法，包括：
在收到用于调度上行传输的物理下行控制信道PDCCH的情况下，启动或重启上行往返传输时间RTT定时器；
在所述上行RTT定时器超时的情况下，启动或重启上行重传定时器。
第三方面，提供了一种终端设备，用于执行上述第一方面或其各实现方式中的方法。具体地，所述终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第四方面，提供了一种终端设备，用于执行上述第二方面或其各实现方式中的方法。具体地，所述终端设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第六方面，提供了一种芯片，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。具体地，所述芯片包括：处理器，用于从存储器中调用并运行计 算机程序，使得安装有所述芯片的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第八方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
基于以上技术方案，通过定义下行RTT定时器的启动或重启条件，能够减小调度信息的监控时长，相应的，不仅能够降低所述下行RTT定时器的运行时间，以降低终端设备的功耗，还能够保证在不增加HARQ进程数目的情况下保证数据传输连续性。
综上，通过重新定义所述下行RTT定时器的启动条件，不仅能够在不增加HARQ进程数目的情况下保证数据传输连续性，还能够适用于降低终端设备的功耗。
附图说明
图1至图3是本申请应用场景的示例。
图4是本申请实施例的DRX的示意性框图。
图5是本申请实施例提供的无线通信方法的示意性流程图。
图6至图8是本申请实施例提供的启动下行RTT定时器和下行重传定时器的示意图。
图9是本申请实施例提供的无线通信方法的另一示意性流程图。
图10是本申请实施例提供的启动上行RTT定时器和上行重传定时器的示意图。
图11和图12是本申请实施例提供的终端设备的示意性框图。
图13是本申请实施例提供的通信设备的示意性框图。
图14是本申请实施例提供的芯片的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是本申请实施例的一个应用场景的示意图。
如图1所示，通信系统100可以包括终端设备110和网络设备120。网络设备120可以通过空口与终端设备110通信。终端设备110和网络设备120之间支持多业务传输。
应理解，本申请实施例仅以通信系统100进行示例性说明，但本申请实施例不限定于此。也就是说，本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、5G通信系统(也称为新无线(New Radio，NR)通信系统)，或未来的通信系统等。
在图1所示的通信系统100中，网络设备120可以是与终端设备110通信的接入网设备。接入网设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备110(例如UE)进行通信。
网络设备120可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是下一代无线接入网(Next Generation Radio Access Network，NG RAN)设备，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备120可以为中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器，或 者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
终端设备110可以是任意终端设备，其包括但不限于与网络设备120或其它终端设备采用有线或者无线连接的终端设备。
例如，所述终端设备110可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进网络中的终端设备等。
终端设备110可以用于设备到设备(Device to Device，D2D)的通信。
无线通信系统100还可以包括与基站进行通信的核心网设备130，该核心网设备130可以是5G核心网(5G Core，5GC)设备，例如，接入与移动性管理功能(Access and Mobility Management Function，AMF)，又例如，认证服务器功能(Authentication Server Function，AUSF)，又例如，用户面功能(User Plane Function，UPF)，又例如，会话管理功能(Session Management Function，SMF)。可选地，核心网络设备130也可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)设备，例如，会话管理功能+核心网络的数据网关(Session Management Function+Core Packet Gateway，SMF+PGW-C)设备。应理解，SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。在网络演进过程中，上述核心网设备也有可能叫其它名字，或者通过对核心网的功能进行划分形成新的网络实体，对此本申请实施例不做限制。
通信系统100中的各个功能单元之间还可以通过下一代网络(next generation，NG)接口建立连接实现通信。
例如，终端设备通过NR接口与接入网设备建立空口连接，用于传输用户面数据和控制面信令；终端设备可以通过NG接口1(简称N1)与AMF建立控制面信令连接；接入网设备例如下一代无线接入基站(gNB)，可以通过NG接口3(简称N3)与UPF建立用户面数据连接；接入网设备可以通过NG接口2(简称N2)与AMF建立控制面信令连接；UPF可以通过NG接口4(简称N4)与SMF建立控制面信令连接；UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据；AMF可以通过NG接口11(简称N11)与SMF建立控制面信令连接；SMF可以通过NG接口7(简称N7)与PCF建立控制面信令连接。
图1示例性地示出了一个基站、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个基站设备并且每个基站的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
需要说明的是，上述通信系统100可以适用于NTN网络。NTN网络可以采用卫星通信的方式向地面用户提供通信服务。相比地面蜂窝网通信，卫星通信具有很多独特的优点。
首先，卫星通信不受用户地域的限制，例如一般的陆地通信不能覆盖海洋、高山、沙漠等无法搭设通信设备或由于人口稀少而不做通信覆盖的区域，而对于卫星通信来说，由于一颗卫星即可以覆盖较大的地面，加之卫星可以围绕地球做轨道运动，因此理论上地球上每一个角落都可以被卫星通信覆盖。其次，卫星通信有较大的社会价值。卫星通信在边远山区、贫穷落后的国家或地区都可以以较低的成本覆盖到，从而使这些地区的人们享受到先进的语音通信和移动互联网技术，有利于缩小与发达地区的数字鸿沟，促进这些地区的发展。再次，卫星通信距离远，且通信距离增大通讯的成本没有明显增加；最后，卫星通信的稳定性高，不受自然灾害的限制。
图2为本申请实施例提供的另一种通信系统的架构示意图。
如图2所示，包括终端设备1101和卫星1102，终端设备1101和卫星1102之间可以进行无线通信。终端设备1101和卫星1102之间所形成的网络还可以称为NTN。在图2所示的通信系统的架构中，卫星1102可以具有基站的功能，终端设备1101和卫星1102之间可以直接通信。在系统架构下，可以将卫星1102称为网络设备。在本申请的一些实施例中，通信系统中可以包括多个网络设备1102，并且每个网络设备1102的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
图3为本申请实施例提供的另一种通信系统的架构示意图。
如图3所示，包括终端设备1201、卫星1202和基站1203，终端设备1201和卫星1202之间可以进行无线通信，卫星1202与基站1203之间可以通信。终端设备1201、卫星1202和基站1203之间所形成的网络还可以称为NTN。在图3所示的通信系统的架构中，卫星1202可以不具有基站的功能，终端设备1201和基站1203之间的通信需要通过卫星1202的中转。在该种系统架构下，可以将基站1203称为网络设备。在本申请的一些实施例中，通信系统中可以包括多个网络设备1203，并且每个网络设备1203的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。所述网络设备1203可以是图1中的网络设备120。
应理解，上述卫星1102或卫星1202包括但不限于：
低地球轨道(Low-Earth Orbit，)LEO卫星、中地球轨道(Medium-Earth Orbit，MEO)卫星、地球同步轨道(Geostationary Earth Orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等等。卫星可采用多波束覆盖地面，例如，一颗卫星可以形成几十甚至数百个波束来覆盖地面。换言之，一个卫星波束可以覆盖直径几十至上百公里的地面区域，以保证卫星的覆盖以及提升整个卫星通信系统的系统容量。
作为示例，LEO的高度范围可以为500km～1500km，相应轨道周期约可以为1.5小时～2小时，用户间单跳通信的信号传播延迟一般可小于20ms，最大卫星可视时间可以为20分钟，LEO的信号传播距离短且链路损耗少，对用户终端的发射功率要求不高。GEO的轨道高度可以35786km，围绕地球旋转周期可以24小时，用户间单跳通信的信号传播延迟一般可为250ms。
需要说明的是，图1至图3只是以示例的形式示意本申请所适用的系统，当然，本申请实施例所示的方法还可以适用于其它系统。
此外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为了便于理解本申请的方案，下面对5G NR系统中的DRX进行说明。
在5G NR中，终端设备和网络设备之间可以传输基于包的数据流，然而，基于包的数据流通常是突发性的。
终端设备在一段时间内有数据传输，但在接下来的一段较长时间内没有数据传输。由此，如果终端设备一直对物理下行链路控制信道(Physical Downlink Control Channel，PDCCH)盲检，会导致终端设备的功耗过大。
基于此，网络设备可以为终端设备配置非连续接收(Discontinuous Reception，DRX)功能，使终端设备可以非连续地监听PDCCH，以达到终端省电的目的。
例如，DRX的主要想法是：网络可以配置终端在网络预知的时间醒来(DRX ON)，终端监听下行控制信道；同时网络也可以配置终端在网络预知的时间睡眠(DRX OFF)，即，终端设备不用监听下行控制信道。这样，如果网络设备有数据要传给终端设备，网路设备可以在终端设备处于DRX ON的时间内调度所述终端设备，而DRX OFF时间内，由于射频关闭，可以减少终端耗电。
具体地，媒体介入控制(Media Access Control，MAC)实体(entity)由无线资源控 制(Radio Resource Control，RRC)配置DRX功能，用于控制终端监测PDCCH的行为。
图4是本申请实施例提供的DRX的示意性框图。
如图4所示，网络设备为终端设备配置的DRX cycle由激活期(On Duration)和休眠期(Opportunity for DRX)组成，在RRC连接态(RRC CONNECTED)模式下，如果终端设备配置了DRX功能，MAC entity可以在On Duration时间内，终端设备监听并接收PDCCH；在Opportunity for DRX时间内，终端设备不接收PDCCH以减少功耗。
应理解，本申请实施例中的处于休眠期的终端设备不接收PDCCH，但是可以接收来自其它物理信道的数据。本发明实施例不作具体限定，例如，该终端设备可以接收物理下行共享信道(Physical Downlink Shared Channel，PDSCH)、确认/非确认(ACK/NACK)等。又例如，在半永久性调度(Semi-Persistent Scheduling，SPS)中，该终端设备可以接收周期性配置的PDSCH数据。
例如，DRX的配置参数包含：
DRX激活期定时器(drx-onDurationTimer)：DRX周期开始时的持续时间(the duration at the beginning of a DRX Cycle)。
DRX时隙偏移定时器(drx-SlotOffset)：启动drx-onDurationTimer之前的延迟(the delay before starting the drx-onDurationTimer)。
DRX去激活定时器(drx-InactivityTimer)：PDCCH指示MAC实体进行新的上行(UL)或下行(DL)传输的PDCCH时机之后的持续时间(the duration after the PDCCH occasion in which a PDCCH indicates a new UL or DL transmission for the MAC entity)。
DRX下行重传定时器(drx-RetransmissionTimerDL)：收到DL重传之前的最大持续时间(the maximum duration until a DL retransmission is received)；除广播过程外的每个DL HARQ进程(per DL HARQ process except for the broadcast process)。
DRX上行重传定时器(drx-RetransmissionTimerUL)：收到UL授权之前的最大持续时间(the maximum duration until a grant for UL retransmission is received)；每个UL HARQ进程(per UL HARQ process)。
DRX长周期开始偏移(drx-LongCycleStartOffset):长DRX周期和drx-StartOffset用于定义长DRX周期和短DRX周期开始的子帧(the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX Cycle starts)。
DRX短周期(drx-ShortCycle)，可作为可选参数。
DRX短周期定时器(drx-ShortCycleTimer)：UE应遵循短DRX周期的持续时间(the duration the UE shall follow the Short DRX cycle)；DRX短周期定时器可作为可选参数。
DRX下行HARQ RTT定时器(drx-HARQ-RTT-TimerDL)：MAC实体期望用于HARQ重传的DL调度之前的最小持续时间(the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity)；除广播过程外的每个DL HARQ过程(per DL HARQ process except for the broadcast process)。
DRX上行HARQ RTT定时器(drx-HARQ-RTT-TimerUL)：MAC实体预期获得UL HARQ重传授权之前的最小持续时间(the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity)。
如果终端设备配置有DRX，则需要在DRX激活期监听PDCCH。DRX激活期包括如下几种情况：
1).drx-onDurationTimer,drx-InactivityTimer,drx-RetransmissionTimerDL,drx-RetransmissionTimerUL以及ra-ContentionResolutionTimer中的任何一个定时器正在运行。
2).在PUCCH上发送了SR并处于挂起(pending)状态。
3).在基于竞争的随机接入过程中，终端设备在成功接收到随机接入响应后还没有接收到C-RNTI加扰的PDCCH指示的一次初始传输。
终端设备启动或重启drx-InactivityTimer的条件为：
如果终端接收到一个指示下行或者上行初始传输的PDCCH，则终端启动或者重启drx-InactivityTimer。
终端启动和停止drx-RetransmissionTimerDL的条件为：
当终端接收到一个指示下行传输的PDCCH，或者当终端在配置的下行授权资源上接收到一个MAC PDU，则终端停止该HARQ进程对应的drx-RetransmissionTimerDL。终端在完成针对这次下行传输的HARQ进程反馈的传输之后启动该HARQ进程对应的drx-HARQ-RTT-TimerDL。
如果终端的某个HARQ对应的定时器drx-HARQ-RTT-TimerDL超时，并且使用这个HARQ进程传输的下行数据解码不成功，则终端启动这个HARQ进程对应的drx-RetransmissionTimerDL。
终端启动和停止drx-RetransmissionTimerUL的条件为：
当终端接收到一个指示上行传输的PDCCH，或者当终端在配置的上行授权资源上发送一个MAC PDU，则终端停止该HARQ进程对应的drx-RetransmissionTimerUL。终端在完成这次PUSCH的第一次重复传输(repetition)之后启动该HARQ进程对应的drx-HARQ-RTT-TimerUL。
如果终端的某个HARQ对应的定时器drx-HARQ-RTT-TimerUL超时，则终端启动这个HARQ进程对应的drx-RetransmissionTimerUL。
可以看出，终端设备在完成上行传输后会先启动一个上行非连续接收(Discontinuous Reception，DRX)HARQ往返传输时间(Round Trip Time，RTT)定时器(drx-HARQ-RTT-TimerUL)，类似的，终端设备在完成针对下行传输的HARQ进程的反馈后会先启动一个下行DRX HARQ RTT定时器(drx-HARQ-RTT-TimerDL)。终端设备在drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL的运行期间内处于休眠状态，不监听PDCCH。等drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL超时后终端设备才开始监听上行重传调度或者根据反馈情况确定是否开始监听下行重传调度。
其中，drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL和RTT以及网络设备的处理时间相关。
但是，而针对非地面通信网络(Non Terrestrial Network，NTN)技术，可以采用卫星通信的方式向地面用户提供通信服务。例如，一颗卫星即可以覆盖较大的地面，且可以围绕地球做轨道运动。
与传统NR采用的蜂窝网络相比，NTN网络中的用户设备(User Equipment，UE)与卫星之间的信号传播时延大幅增加，导致NR中的HARQ进程满足不了NTN网络的需求。此外，增加了drx-HARQ-RTT-TimerUL或drx-HARQ-RTT-TimerDL的运行时间，进而增加了终端设备的功耗。
图5示出了根据本申请实施例的无线通信方法200的示意性流程图，所述方法200可以由终端设备执行。图5中所示的终端设备可以是如图1所示的终端设备。
如图5所示，所述方法200可包括：
S210，在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；
S220，在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。
通过定义下行RTT定时器的启动或重启条件，能够减小调度信息的监控时长，相应的，不仅能够降低所述下行RTT定时器的运行时间，以降低终端设备的功耗，还能够保证在不增加HARQ进程数目的情况下保证数据传输连续性。
综上，通过重新定义所述下行RTT定时器的启动条件，不仅能够在不增加HARQ进程数目的情况下保证数据传输连续性，还能够适用于降低终端设备的功耗。
需要说明的是，本申请实施例对下行RTT定时器的实现方式不作具体限定。例如，所述下行RTT定时器也可称为drx-HARQ-RTT-TimerDL，以替代NR中的drx-HARQ-RTT-TimerDL。再如，所述下行RTT定时器还可以是重新定义的RTT定时器，即与NR中的drx-HARQ-RTT-TimerDL不同的定时器。再如，可以将所述下行RTT定时器的功能结合、附加或添加至到NR中的drx-HARQ-RTT-TimerDL。
在本申请的一些实施例中，所述下行RTT定时器和所述下行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的下行HARQ进程。
例如，针对HARQ的反馈功能已关闭的情况下，由于没有了针对HARQ的反馈信息，网络设备可以在接收到针对下行传输的反馈信息之前继续调度下行传输的重传。对于终端设备而言，终端设备可以连续(或者以一定的间隔)接收下行调度的PDSCH传输。
换言之，将所述下行RTT定时器和所述下行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的下行HARQ进程，不仅可以关闭HARQ反馈功能，使得终端设备不需要向网络设备发送针对PDSCH的HARQ反馈信息，还可以在关闭HARQ反馈功能的情况下，使得终端设备仍然支持HARQ重传，进而保证数据传输可靠性。
在本申请的一些实施例中，所述下行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
例如，所述下行RTT定时器的时长可以用于反映终端设备从下行传输到接收到网络设备下发的重传调度所需要的最小时间间隔。
可选的，所述最小时间间隔根据RTT和/或网络设备的处理时间确定。
换言之，所述下行RTT定时器的时长可以取决于网络设备的实现。例如网络设备在盲调度重传时需要在连续两个PDCCH调度中引入一定的时间间隔，时间间隔一方面取决于所述网络设备的处理时延，另一方面取决于时间分集效应，即相邻的传输需要间隔一段时间。如果下行RTT定时器足够小，一次PDCCH和PDSCH传输之间，网络设备可以传输同一个HARQ进程的其它调度信息。
在本申请的一些实施例中，所述方法200还可包括：
接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
非连续接收DRX周期、激活期定时器、去激活定时器、所述下行RTT定时器，上行RTT定时器，所述下行重传定时器或上行重传定时器。
例如，终端设备可接收网络设备发送的RRC配置信息。
例如，所述RRC配置信息可包括DRX的相关参数和/或MAC主(main)配置。
例如，DRX的相关参数包括但不限于：
DRX周期(DRX cycle)、DRX激活期定时器(drx-onDurationTimer)、去激活定时器(drx-InactivityTimer)、所述下行RTT定时器(drx-HARQ-RTT-TimerDL)、上行RTT定时器(drx-HARQ-RTT-TimerUL)、所述下行重传定时器(drx-RetransmissionTimerDL)或上行重传定时器(drx-RetransmissionTimerUL)。
例如，MAC main配置可以包括用于配置所有HARQ进程或者部分HARQ进程是否关闭HARQ反馈功能的信息。
换言之，终端设备接收下行RTT定时器和下行重传定时器的配置信息，以基于所述下行RTT定时器和下行重传定时器的配置信息，启动或重启下行RTT定时器和下行重传定时器。
在本申请的一些实施例中，所述PDSCH为所述PDCCH调度的，或所述PDSCH为预配置的。
当然，所述PDSCH也可以是其他PDCCH调度的。
在本申请的一些实施例中，所述方法200还可包括：
在所述下行重传定时器的运行期间内，接收用于调度下行传输的调度信息。
例如，所述终端设备在所述下行重传定时器的运行期间内，接收用于调度下行重传 (Retransmission)的调度信息。应理解，在其他可替代实施例中，述终端设备在所述下行重传定时器的运行期间内，接收用于调度下行新传的调度信息，此时，所述下行重传定时器可以直接称为下行传输定时器。
在本申请的一些实施例中，所述S210可包括：
在收到所述PDCCH的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
图6是本申请实施例提供的启动下行RTT定时器和下行重传定时器的示意图。
如图6所示，对于关闭HARQ功能的下行HARQ进程，终端设备在收到DL任务(assignment)，即PDCCH后，启动或重启该下行HARQ进程关联的下行RTT定时器；与此同时，所述终端设备还可以停止该下行HARQ进程关联的下行重传定时器。
当该下行HARQ进程关联的下行RTT定时器超时后，所述终端设备可以启动或重启该下行HARQ进程的下行重传定时器。
应理解，图6仅为本申请的示例，不应理解为对本申请的限制。
再如，图6所示的所述PDSCH的多次重复(repetition)传输可以是动态调度的，例如图6所示的PDCCH调度的；在其他可替代实施例中，其还可以是预配置的，例如可以是SPS调度的。
再如，图6所示的PDSCH的多次重复传输是连续的，在其他可替代实施例中，其也可以是间隔开的。再如，图6所示的PDCCH用于调度PDSCH的重复传输，在其他可替代实施例中，其也可以用于调度其他新传PDSCH。
在本申请的一些实施例中，所述S210可包括：
在收到用于调度所述PDSCH的调度信息的情况下，停止所述下行重传定时器；
在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器。
图7是本申请实施例提供的启动下行RTT定时器和下行重传定时器的示意图。
如图7所示，对于关闭HARQ功能的下行HARQ进程，终端设备在收到DL分配(assignment)，即PDCCH后，终端设备停止该下行HARQ进程关联的下行重传定时器；终端设备在收到PDSCH的第一次重复(repetition)传输后，启动或重启该下行HARQ进程关联的下行RTT定时器。
当该下行HARQ进程关联的下行RTT定时器超时后，所述终端设备可以启动或重启该下行HARQ进程的下行重传定时器。
应理解，图7仅为本申请的示例，不应理解为对本申请的限制。
例如，在其他可替代实施例中，终端设备在收到PDSCH的最后一次重复(repetition)传输后，启动或重启该下行HARQ进程关联的下行RTT定时器。
再如，图7所示的所述PDSCH的多次重复(repetition)传输可以是动态调度的，例如图7所示的PDCCH调度的；在其他可替代实施例中，其还可以是预配置的，例如可以是SPS调度的。
再如，图7所示的PDSCH的多次重复传输是连续的，在其他可替代实施例中，其也可以是间隔开的。再如，图7所示的PDCCH用于调度PDSCH的重复传输，在其他可替代实施例中，其也可以用于调度其他新传PDSCH。
在本申请的一些实施例中，所述S210可包括：
在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
图8是本申请实施例提供的启动下行RTT定时器和下行重传定时器的示意图。
如图8所示，对于关闭HARQ功能的下行HARQ进程，终端设备在收到PDSCH的第一次重复(repetition)传输后，启动或重启该下行HARQ进程关联的下行RTT定时器；与此同时，所述终端设备还可以停止该下行HARQ进程关联的下行重传定时器。
当该下行HARQ进程关联的下行RTT定时器超时后，所述终端设备可以启动或重启该下行HARQ进程的下行重传定时器。
应理解，图8仅为本申请的示例，不应理解为对本申请的限制。
例如，在其他可替代实施例中，终端设备在收到PDSCH的最后一次重复(repetition)传输后，启动或重启该下行HARQ进程关联的下行RTT定时器；与此同时，所述终端设备还可以停止该下行HARQ进程关联的下行重传定时器。
再如，图8所示的所述PDSCH的多次重复(repetition)传输可以是动态调度的，例如图8所示的PDCCH调度的；在其他可替代实施例中，其还可以是预配置的，例如可以是SPS调度的。
再如，图8所示的PDSCH的多次重复传输是连续的，在其他可替代实施例中，其也可以是间隔开的。再如，图8所示的PDCCH用于调度PDSCH的重复传输，在其他可替代实施例中，其也可以用于调度其他新传PDSCH。
图9示出了根据本申请实施例的无线通信方法300的示意性流程图，所述方法300可以由终端设备执行。图9中所示的终端设备可以是如图1所示的终端设备。
如图9所示，所述方法300可包括：
S310，在收到用于调度上行传输的物理下行控制信道PDCCH的情况下，启动或重启上行往返传输时间RTT定时器；
S320，在所述上行RTT定时器超时的情况下，启动或重启上行重传定时器。
通过定义上行RTT定时器的启动或重启条件，能够减小调度信息的监控时长，相应的，不仅能够降低所述上行RTT定时器的运行时间，以降低终端设备的功耗，还能够保证在不增加HARQ进程数目的情况下保证数据传输连续性。
综上，通过重新定义所述上行RTT定时器的启动条件，不仅能够在不增加HARQ进程数目的情况下保证数据传输连续性，还能够适用于降低终端设备的功耗。
需要说明的是，本申请实施例对上行RTT定时器的实现方式不作具体限定。例如，所述上行RTT定时器也可称为drx-HARQ-RTT-TimerUL，以替代NR中的drx-HARQ-RTT-TimerUL。再如，所述上行RTT定时器还可以是重新定义的RTT定时器，即与NR中的drx-HARQ-RTT-TimerUL不同的定时器。再如，可以将所述上行RTT定时器的功能结合、附加或添加至到NR中的drx-HARQ-RTT-TimerUL。
在本申请的一些实施例中，所述上行RTT定时器和所述上行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的上行HARQ进程。
例如，针对HARQ的反馈功能已关闭的情况下，由于没有了针对HARQ的反馈信息，网络设备可以在接收到上行传输之前继续调度上行传输的重传。对于终端设备而言，终端设备取决于网络设备的实现，终端设备可以连续(或者以一定的间隔)接收上行传输调度，例如发送第一个PUSCH之前就可以接收同一个HARQ进程调度的上行授权。
换言之，将所述上行RTT定时器和所述上行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的上行HARQ进程，可以在关闭HARQ反馈功能的情况下，使得终端设备仍然支持HARQ重传，进而保证数据传输可靠性。
在本申请的一些实施例中，所述上行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
例如，所述上行RTT定时器的时长可以用于反映终端设备从上行传输到接收到网络设备下发的重传调度所需要的最小时间间隔。
可选的，所述最小时间间隔根据RTT和/或网络设备的处理时间确定。
换言之，所述上行RTT定时器的时长可以取决于网络设备的实现。例如网络设备在盲调度重传时需要在连续两个PDCCH调度中引入一定的时间间隔，时间间隔一方面取决于所述网络设备的处理时延，另一方面取决于时间分集效应，即相邻的传输需要间隔一段时间。如果上行RTT定时器足够小，一次PDCCH和PDSCH传输之间，网络设备 可以传输同一个HARQ进程的其它调度信息。
在本申请的一些实施例中，所述方法300还可包括：
接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
非连续接收DRX周期、激活期定时器、去激活定时器、下行RTT定时器，所述上行RTT定时器，下行重传定时器或所述上行重传定时器。
例如，终端设备可接收网络设备发送的RRC配置信息。
例如，所述RRC配置信息可包括DRX的相关参数和/或MAC主(main)配置。
例如，DRX的相关参数包括但不限于：
DRX周期(DRX cycle)、DRX激活期定时器(drx-onDurationTimer)、去激活定时器(drx-InactivityTimer)、下行RTT定时器(drx-HARQ-RTT-TimerDL)、上行RTT定时器(drx-HARQ-RTT-TimerUL)、下行重传定时器(drx-RetransmissionTimerDL)或上行重传定时器(drx-RetransmissionTimerUL)。
例如，MAC main配置可以包括用于配置所有HARQ进程或者部分HARQ进程是否关闭HARQ反馈功能的信息。
换言之，终端设备接收上行RTT定时器和上行重传定时器的配置信息，以基于所述上行RTT定时器和上行重传定时器的配置信息，启动或重启上行RTT定时器和上行重传定时器。
在本申请的一些实施例中，所述方法300还可包括：
在所述上行重传定时器的运行期间内，接收用于调度上行传输的调度信息。
例如，所述终端设备在所述上行重传定时器的运行期间内，接收用于调度上行重传(Retransmission)的调度信息。应理解，在其他可替代实施例中，述终端设备在所述上行重传定时器的运行期间内，接收用于调度上行新传的调度信息，此时，所述上行重传定时器可以直接称为上行传输定时器。
在本申请的一些实施例中，所述S310可包括：
在收到所述PDCCH的情况下，启动或重启上行往返传输时间RTT定时器，且停止所述上行重传定时器。
图10是本申请实施例提供的启动上行RTT定时器和上行重传定时器的示意图。
如图10所示，对于关闭HARQ功能的上行HARQ进程，终端设备在收到上行授权(UL grant)，即PDCCH后，启动或重启该上行HARQ进程关联的上行RTT定时器；与此同时，所述终端设备还可以停止该上行HARQ进程关联的上行重传定时器。
当该上行HARQ进程关联的上行RTT定时器超时后，所述终端设备可以启动或重启该上行HARQ进程的上行重传定时器。
应理解，图10仅为本申请的示例，不应理解为对本申请的限制。
例如，在其他可替代实施例中，终端设备在收到PDSCH的第一次或最后一次重复(repetition)传输后，启动或重启该上行HARQ进程关联的上行RTT定时器；与此同时，所述终端设备还可以停止该上行HARQ进程关联的上行重传定时器。
再如，图10所示的所述PDSCH的多次重复(repetition)传输可以是动态调度的，例如图10所示的PDCCH调度的；在其他可替代实施例中，其还可以是预配置的，例如可以是SPS调度的。
再如，图10所示的PDSCH的多次重复传输是连续的，在其他可替代实施例中，其也可以是间隔开的。再如，图10所示的PDCCH用于调度PDSCH的重复传输，在其他可替代实施例中，其也可以用于调度其他新传PDSCH。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避 免不必要的重复，本申请对各种可能的组合方式不再另行说明。又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。
还应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。此外，在本申请实施例中，术语“下行”和“上行”用于表示信号或数据的传输方向，其中，“下行”用于表示信号或数据的传输方向为从站点发送至小区的用户设备的第一方向，“上行”用于表示信号或数据的传输方向为从小区的用户设备发送至站点的第二方向，例如，“下行信号”表示该信号的传输方向为第一方向。另外，本申请实施例中，术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。具体地，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
上文结合图1至图10，详细描述了本申请的方法实施例，下文结合图11至图14，详细描述本申请的装置实施例。
图11是本申请实施例的终端设备400的示意性框图。
如图11所示，所述终端设备400可包括处理单元410，所述处理单元410具体用于：
在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；
在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。
在本申请的一些实施例中，所述下行RTT定时器和所述下行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的下行HARQ进程。
在本申请的一些实施例中，所述处理单元410具体用于：
在收到所述PDCCH的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
在本申请的一些实施例中，所述处理单元410具体用于：
在收到用于调度所述PDSCH的调度信息的情况下，停止所述下行重传定时器；
在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器。
在本申请的一些实施例中，所述处理单元410具体用于：
在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
在本申请的一些实施例中，所述PDSCH为所述PDCCH调度的，或所述PDSCH为预配置的。
在本申请的一些实施例中，所述下行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
在本申请的一些实施例中，所述处理单元410还用于：
接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
非连续接收DRX周期、激活期定时器、去激活定时器、所述下行RTT定时器，上行RTT定时器，所述下行重传定时器或上行重传定时器。
在本申请的一些实施例中，所述处理单元410还用于：
在所述下行重传定时器的运行期间内，接收用于调度下行传输的调度信息。
应理解，装置实施例与方法实施例可以相互对应，类似的描述可以参照方法实施例。具体地，图11所示的终端设备400可以对应于执行本申请实施例的方法200中的相应主体，并且终端设备400中的各个单元的前述和其它操作和/或功能分别为了实现图5中的 各个方法中的相应流程，为了简洁，在此不再赘述。
图12是本申请实施例提供的终端设备500的示意性框图。
如图12所示，所述终端设备包括处理单元510，所述处理单元510用于：
在收到用于调度上行传输的物理下行控制信道PDCCH的情况下，启动或重启上行往返传输时间RTT定时器；
在所述上行RTT定时器超时的情况下，启动或重启上行重传定时器。
在本申请的一些实施例中，所述上行RTT定时器和所述上行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的上行HARQ进程。
在本申请的一些实施例中，所述处理单元510具体用于：
在收到所述PDCCH的情况下，启动或重启上行往返传输时间RTT定时器，且停止所述上行重传定时器。
在本申请的一些实施例中，所述上行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
在本申请的一些实施例中，所述处理单元510还用于：
接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
非连续接收DRX周期、激活期定时器、去激活定时器、下行RTT定时器，所述上行RTT定时器，下行重传定时器或所述上行重传定时器。
在本申请的一些实施例中，所述处理单元510还用于：
在所述上行重传定时器的运行期间内，接收用于调度上行传输的调度信息。
应理解，装置实施例与方法实施例可以相互对应，类似的描述可以参照方法实施例。具体地，图12所示的终端设备500可以对应于执行本申请实施例的方法300中的相应主体，并且终端设备500中的各个单元的前述和其它操作和/或功能分别为了实现图9中的各个方法中的相应流程，为了简洁，在此不再赘述。
上文中结合附图从功能模块的角度描述了本申请实施例的通信设备。应理解，该功能模块可以通过硬件形式实现，也可以通过软件形式的指令实现，还可以通过硬件和软件模块组合实现。
具体地，本申请实施例中的方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路和/或软件形式的指令完成，结合本申请实施例公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。
可选地，软件模块可以位于随机存储器，闪存、只读存储器、可编程只读存储器、电可擦写可编程存储器、寄存器等本领域的成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法实施例中的步骤。
例如，上文涉及的处理单元可由处理器实现。
图8是本申请实施例的通信设备600示意性结构图。
如图8所示，所述通信设备600可包括处理器610。
其中，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
请继续参见图8，通信设备600还可以包括存储器620。
其中，该存储器620可以用于存储指示信息，还可以用于存储处理器610执行的代码、指令等。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
请继续参见图8，通信设备600还可以包括收发器630。
其中，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
应当理解，该通信设备600中的各个组件通过总线系统相连，其中，总线系统除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
还应理解，该通信设备600可为本申请实施例的终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由终端设备实现的相应流程，也就是说，本申请实施例的通信设备600可对应于本申请实施例中的终端设备400或终端设备500，并可以对应于执行根据本申请实施例的方法200或300中的相应主体，为了简洁，在此不再赘述。
此外，本申请实施例中还提供了一种芯片。
例如，芯片可能是一种集成电路芯片，具有信号的处理能力，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。所述芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。可选地，该芯片可应用到各种通信设备中，使得安装有该芯片的通信设备能够执行本申请实施例中的公开的各方法、步骤及逻辑框图。
图9是根据本申请实施例的芯片700的示意性结构图。
如图9所示，所述芯片700包括处理器710。
其中，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
请继续参见图9，所述芯片700还可以包括存储器720。
其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。该存储器720可以用于存储指示信息，还可以用于存储处理器710执行的代码、指令等。存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
请继续参见图9，所述芯片700还可以包括输入接口730。
其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
请继续参见图9，所述芯片700还可以包括输出接口740。
其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
应理解，所述芯片700可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，也可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
还应理解，该芯片700中的各个组件通过总线系统相连，其中，总线系统除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
上文涉及的处理器可以包括但不限于：
通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等等。
所述处理器可以用于实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
上文涉及的存储器包括但不限于：
易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器 (Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
应注意，本文描述的存储器旨在包括这些和其它任意适合类型的存储器。
本申请实施例中还提供了一种计算机可读存储介质，用于存储计算机程序。该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行方法200或300所示实施例的方法。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例中还提供了一种计算机程序产品，包括计算机程序。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例中还提供了一种计算机程序。当该计算机程序被计算机执行时，使得计算机可以执行方法200或300所示实施例的方法。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
此外，本申请实施例还提供了一种通信系统，所述通信系统可以包括上述涉及的终端设备和网络设备，以形成如图1所示的通信系统100，为了简洁，在此不再赘述。需要说明的是，本文中的术语“系统”等也可以称为“网络管理架构”或者“网络系统”等。
还应当理解，在本申请实施例和所附权利要求书中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请实施例。
例如，在本申请实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”、“上述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
所属领域的技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的范围。
如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计 算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。
例如，以上所描述的装置实施例中单元或模块或组件的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或模块或组件可以结合或者可以集成到另一个系统，或一些单元或模块或组件可以忽略，或不执行。
又例如，上述作为分离/显示部件说明的单元/模块/组件可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元/模块/组件来实现本申请实施例的目的。
最后，需要说明的是，上文中显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
以上内容，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以权利要求的保护范围为准。

Claims (23)

  1. 一种无线通信方法，其特征在于，包括：
    在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；
    在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。
  2. 根据权利要求1所述的方法，其特征在于，所述下行RTT定时器和所述下行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的下行HARQ进程。
  3. 根据权利要求1或2所述的方法，其特征在于，所述启动或重启下行往返传输时间RTT定时器，包括：
    在收到所述PDCCH的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
  4. 根据权利要求1或2所述的方法，其特征在于，所述启动或重启下行往返传输时间RTT定时器，包括：
    在收到用于调度所述PDSCH的调度信息的情况下，停止所述下行重传定时器；
    在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器。
  5. 根据权利要求1或2所述的方法，其特征在于，所述启动或重启下行往返传输时间RTT定时器，包括：
    在收到所述PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启所述下行RTT定时器，并停止所述下行重传定时器。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述PDSCH为所述PDCCH调度的，或所述PDSCH为预配置的。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述下行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
    非连续接收DRX周期、激活期定时器、去激活定时器、所述下行RTT定时器，上行RTT定时器，所述下行重传定时器或上行重传定时器。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    在所述下行重传定时器的运行期间内，接收用于调度下行传输的调度信息。
  10. 一种无线通信方法，其特征在于，包括：
    在收到用于调度上行传输的物理下行控制信道PDCCH的情况下，启动或重启上行往返传输时间RTT定时器；
    在所述上行RTT定时器超时的情况下，启动或重启上行重传定时器。
  11. 根据权利要求10所述的方法，其特征在于，所述上行RTT定时器和所述上行重传定时器均关联至一个混合自动重传请求HARQ反馈功能关闭的上行HARQ进程。
  12. 根据权利要求10或11所述的方法，其特征在于，所述启动或重启上行往返传输时间RTT定时器，包括：
    在收到所述PDCCH的情况下，启动或重启上行往返传输时间RTT定时器，且停止所述上行重传定时器。
  13. 根据权利要求10至12中任一项所述的方法，其特征在于，所述上行RTT定时器的时长根据时间分集的设置和/或网络设备的处理时延确定。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，所述方法还包括：
    接收配置信息，所述配置信息用于配置以下定时器中的至少一项：
    非连续接收DRX周期、激活期定时器、去激活定时器、下行RTT定时器，所述上行RTT定时器，下行重传定时器或所述上行重传定时器。
  15. 根据权利要求10至14中任一项所述的方法，其特征在于，所述方法还包括：
    在所述上行重传定时器的运行期间内，接收用于调度上行传输的调度信息。
  16. 一种终端设备，其特征在于，包括处理单元，所述处理单元用于：
    在收到用于调度下行传输的物理下行控制信道PDCCH、物理下行共享信道PDSCH的第一次重复传输或所述PDSCH的最后一次重复传输的情况下，启动或重启下行往返传输时间RTT定时器；
    在所述下行RTT定时器超时的情况下，启动或重启下行重传定时器。
  17. 一种终端设备，其特征在于，包括处理单元，所述处理单元用于：
    在收到用于调度上行传输的物理下行控制信道PDCCH的情况下，启动或重启上行往返传输时间RTT定时器；
    在所述上行RTT定时器超时的情况下，启动或重启上行重传定时器。
  18. 一种终端设备，其特征在于，包括：
    处理器、存储器和收发器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求1至9中任一项所述的方法。
  19. 一种终端设备，其特征在于，包括：
    处理器、存储器和收发器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求10至15中任一项所述的方法。
  20. 一种芯片，其特征在于，包括：
    处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至9中任一项所述的方法或如权利要求10至15中任一项所述的方法。
  21. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至9中任一项所述的方法或如权利要求10至15中任一项所述的方法。
  22. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得计算机执行如权利要求1至9中任一项所述的方法或如权利要求10至15中任一项所述的方法。
  23. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至9中任一项所述的方法或如权利要求10至15中任一项所述的方法。
PCT/CN2020/120456 2020-10-12 2020-10-12 无线通信方法和设备 WO2022077174A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080103165.5A CN115868132B (zh) 2020-10-12 2020-10-12 无线通信方法和设备
PCT/CN2020/120456 WO2022077174A1 (zh) 2020-10-12 2020-10-12 无线通信方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/120456 WO2022077174A1 (zh) 2020-10-12 2020-10-12 无线通信方法和设备

Publications (1)

Publication Number Publication Date
WO2022077174A1 true WO2022077174A1 (zh) 2022-04-21

Family

ID=81208825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/120456 WO2022077174A1 (zh) 2020-10-12 2020-10-12 无线通信方法和设备

Country Status (2)

Country Link
CN (1) CN115868132B (zh)
WO (1) WO2022077174A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067002A1 (zh) * 2022-09-28 2024-04-04 华为技术有限公司 控制信息的监听方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730137A (zh) * 2008-10-31 2010-06-09 华为技术有限公司 数据处理方法及系统
US20170134124A1 (en) * 2015-11-06 2017-05-11 Lg Electronics Inc. Method for handling of drx timers for multiple repetition transmission in wireless communication system and a device therefor
CN109155709A (zh) * 2016-05-23 2019-01-04 Lg 电子株式会社 接收下行链路控制信息的方法和用户设备
CN110035502A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 通信方法、通信设备和网络设备
CN110958088A (zh) * 2018-09-27 2020-04-03 华为技术有限公司 一种通信方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3499767A4 (en) * 2016-08-10 2019-08-28 Huawei Technologies Co., Ltd. HYBRID AUTOMATIC REPEAT REQUEST PROCESS AND DEVICE DEVICE
CN110351898B (zh) * 2018-04-04 2023-06-30 华为技术有限公司 非连续接收的通信方法、装置、通信设备和通信系统
WO2020071698A1 (ko) * 2018-10-05 2020-04-09 주식회사 케이티 비지상 네트워크를 이용하여 통신을 수행하는 방법 및 그 장치
CN111050423B (zh) * 2018-10-15 2022-01-04 维沃移动通信有限公司 一种非连续接收的处理方法及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730137A (zh) * 2008-10-31 2010-06-09 华为技术有限公司 数据处理方法及系统
US20170134124A1 (en) * 2015-11-06 2017-05-11 Lg Electronics Inc. Method for handling of drx timers for multiple repetition transmission in wireless communication system and a device therefor
CN109155709A (zh) * 2016-05-23 2019-01-04 Lg 电子株式会社 接收下行链路控制信息的方法和用户设备
CN110035502A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 通信方法、通信设备和网络设备
CN110958088A (zh) * 2018-09-27 2020-04-03 华为技术有限公司 一种通信方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067002A1 (zh) * 2022-09-28 2024-04-04 华为技术有限公司 控制信息的监听方法及装置

Also Published As

Publication number Publication date
CN115868132A (zh) 2023-03-28
CN115868132B (zh) 2024-07-30

Similar Documents

Publication Publication Date Title
US20220232596A1 (en) Discontinuous reception method, terminal device and storage medium
US12048051B2 (en) Method and apparatus for data transmission, terminal, and storage medium
US20230224091A1 (en) Wireless communication method and device
US20240129072A1 (en) Method for determing drx activation time and terminal device
WO2022082353A1 (zh) 非连续接收重传定时器的启动方法、装置、设备及介质
WO2022056854A1 (zh) 无线通信方法和设备
WO2022077174A1 (zh) 无线通信方法和设备
US20230337320A1 (en) Wireless communication method and terminal device
WO2021155605A1 (zh) 配置授权定时器的使用方法与装置、终端设备和网络设备
WO2022082749A1 (zh) 无线通信方法和设备
WO2021227030A1 (zh) 一种非连续接收的处理方法、电子设备及存储介质
CN114173362B (zh) 无线通信的方法和设备
WO2022099514A1 (zh) 无线通信方法和设备
WO2021068224A1 (zh) 无线通信方法、终端设备和网络设备
WO2022227086A1 (zh) 通信方法及装置
WO2023108642A1 (zh) 通信方法、装置、设备、芯片、存储介质、产品及程序
WO2022205482A1 (zh) 无线通信方法和终端设备
WO2021227050A1 (zh) 一种信息处理方法、终端设备及存储介质
US20230389126A1 (en) Pdcch monitoring method and drx uplink retransmission timer control method
WO2023279295A1 (zh) 信息处理方法、装置、终端设备及存储介质
WO2022160137A1 (zh) 无线通信方法、终端设备和网络设备
WO2023010586A1 (zh) 无线通信方法、终端设备和网络设备
WO2023206010A1 (zh) 通信方法、装置、设备、存储介质、芯片、产品及程序
WO2023097504A1 (zh) 通信方法、装置、设备、存储介质、芯片、产品及程序
WO2022133675A1 (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: 20956956

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20956956

Country of ref document: EP

Kind code of ref document: A1