CN111512674B

CN111512674B - Data transmission method, terminal equipment and network equipment

Info

Publication number: CN111512674B
Application number: CN201880080613.7A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-11-30
Filing date: 2018-11-30
Publication date: 2022-02-11
Anticipated expiration: 2038-11-30
Also published as: WO2020107479A1; CN111512674A

Abstract

A method for transmitting data, a terminal device and a network device can ensure timely scheduling of services, and the method comprises the following steps: the terminal device is configured with a first timer, wherein the first timer is used for enabling the terminal device to be in an activated state under the condition that the network device schedules transmission.

Description

Data transmission method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a data transmission method, terminal equipment and network equipment.

Background

In a New Radio (NR) system, a network device may configure a Discontinuous Reception (DRX) mode for a terminal device, where a state of a timer in the DRX mode is affected by a scheduling condition of a Physical Downlink Control Channel (PDCCH), and a scheduling condition of the PDCCH is also affected by whether the terminal device is in an active state or an inactive state, and if the timer in the DRX mode is not activated, even if the PDCCH schedules a New Service, for example, a Service with a high Quality of Service (QoS) requirement, the terminal device does not monitor the PDCCH, and affects timely transmission of the Service.

Disclosure of Invention

The embodiment of the application provides a data transmission method, terminal equipment and network equipment, which can ensure the timely transmission of scheduling services.

In a first aspect, a method for transmitting data is provided, including: the terminal device is configured with a first timer, wherein the first timer is used for enabling the terminal device to be in an activated state under the condition that the network device schedules transmission.

In a second aspect, a method for transmitting data is provided, including: the method comprises the steps that network equipment configures a first timer for terminal equipment, wherein the first timer is used for enabling the terminal equipment to be in an activated state under the condition that the network equipment schedules transmission.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the terminal device comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

In a fourth aspect, there is provided a network device for performing the method of the second aspect or any possible implementation manner of the second aspect. In particular, the terminal device comprises means for performing the method of the second aspect described above or any possible implementation manner of the second aspect.

In a fifth aspect, a terminal device is provided, where the terminal device includes: including a processor and memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided, where the middle terminal includes: including a processor and memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.

In a seventh aspect, a chip is provided for implementing the method in the first aspect or its implementation manners.

Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method according to the first aspect to the second aspect or the implementation manners thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method of the first to second aspects or the implementation manners thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to make a computer execute the method of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program which, when run on a computer, causes the computer to perform the method of the first to second aspects or implementations thereof.

Based on the technical scheme, the terminal equipment is configured with the timer, so that the terminal equipment can be in an activated state when the network equipment has scheduling transmission, and timely scheduling of services can be guaranteed.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of a method for transmitting data according to an embodiment of the present disclosure.

Fig. 3 is a schematic diagram of a method for transmitting data according to an embodiment of the present disclosure.

Fig. 4 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

Fig. 5 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of a communication device according to another embodiment of the present application.

Fig. 7 is a schematic block diagram of a chip provided in an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication devices may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In this embodiment, the network device may configure the terminal device to operate in a DRX mode, where the terminal device is configured with a plurality of timers:

1. a Hybrid Automatic Repeat reQuest (HARQ) backhaul (RTT) Timer, i.e., drx-HARQ-RTT-Timer, configured to indicate a minimum Time duration that a terminal needs to wait before receiving expected uplink or downlink retransmission data. The drx-HARQ-RTT-Timer may include a HARQ RTT uplink Timer, i.e., drx-HARQ-RTT-timerll, and a HARQ RTT downlink Timer, i.e., drx-HARQ-RTT-TimerDL.

2. A retransmission timer (drx-retransmission timer) for uplink or downlink retransmission scenarios. The timer is used to indicate a maximum duration that the terminal device needs to continuously monitor in order to transmit the expected retransmission data. The drx retransmission timer may include an uplink retransmission timer, i.e., drx-retransmission timer ul, and a downlink retransmission timer, i.e., drx-retransmission timer rdl.

3. An inactivity timer (DRX-inactivity timer) that indicates a waiting duration required to continue to remain in an active state when the terminal device successfully decodes a PDCCH indicating a new uplink transmission or a new downlink transmission, and stops the DRX-inactivity timer when a DRX Command (Command) Media Access Control (MAC) Control Element (Control Element, CE) or a long (long) DRX Command MAC CE is received or the timer expires.

The start condition and stop condition of the three timers may be:

when the MAC entity is active, the terminal device may monitor a PDCCH, which may indicate the following:

1. the PDCCH indicates one downlink transmission or one downlink assignment (DL assignment) is configured;

in this case, the terminal device may start to perform HARQ process drx-HARQ-RTT-TimerDL on a first symbol after transmission of a corresponding Physical Uplink Control Channel (PUCCH) is finished; the drx-retransmission timerdl of the corresponding HARQ process is stopped.

2. The PDCCH indicates a primary uplink transmission;

in this case, the terminal device may start to perform HARQ process drx-HARQ-RTT-timer ul on a first symbol after the initial transmission of a corresponding Physical Uplink Shared Channel (PUSCH) is finished; the drx-retransmission timerll of the corresponding HARQ process is stopped.

3. The PDCCH indicates a new data transmission (uplink or downlink);

in this case, the terminal device may turn on or restart the drx-inactivity timer at the first symbol after the PDCCH reception is ended.

In addition, if there is a MAC Protocol Data Unit (PDU) transmitted on a configured Uplink resource grant, the terminal device may start to start the HARQ process drx-HARQ-RTT-timerll at a first symbol after initial transmission of a corresponding Physical Uplink Shared Channel (PUSCH) is finished; the drx-retransmission timerll of the corresponding HARQ process is stopped.

Therefore, when the PDCCH is used for scheduling transmission, if retransmission is scheduled, no timer is arranged on the terminal equipment, so that the terminal equipment can be in an activated state, and before the HARQ RTT timer is overtime, even if the PDCCH has scheduling service transmission, the terminal equipment cannot monitor the PDCCH, so that the service cannot be scheduled in time, and the user experience is influenced.

In view of this, the present application provides a method for transmitting data, where a timer is configured for a terminal device, so as to ensure that the terminal device can be in an activated state when a network device has scheduled transmission, thereby ensuring timely scheduling of a service.

Fig. 2 is a schematic flow chart of a method of transmitting data according to an embodiment of the present application, which may be performed by a terminal device in the communication system shown in fig. 1, as shown in fig. 2, the method 200 includes:

s210, a terminal device is configured with a first timer, where the first timer is used to enable the terminal device to be in an active state when a network device schedules transmission.

Optionally, in this embodiment of the present application, the first timer may be a newly defined timer, or an existing timer may be reused, for example, the definition, the starting condition, or the stopping condition of the existing timer is modified to ensure that the terminal device is in an active state when the network device schedules service transmission, which is not limited in this embodiment of the present application.

Optionally, in this embodiment of the present application, the network device may schedule uplink transmission for the network device or schedule downlink transmission for the network device, and whether the network device schedules uplink transmission or downlink transmission is not specifically limited; or may schedule transmission of a specific Service for the network device, and optionally, the specific Service may be a Service with higher transmission requirements, for example, a Service with higher Quality-of-Service (QoS) requirements, or a delay-sensitive Service, for example, a high-Reliable and Low Latency Communication (URLLC) Service.

It should be understood that, when the first timer is in the on state, the terminal device is in the active state, so that when the network schedules transmission, the terminal device is in the active state by turning on the first timer, thereby ensuring that the terminal device monitors the PDCCH in time, and further ensuring the timely scheduling of the service.

Hereinafter, a specific implementation of the first timer will be described with reference to embodiments 1 to 4.

Example 1: the first timer is a newly defined timer.

In a specific embodiment of this embodiment 1, the terminal device may start (start) or restart (restart) the first timer when the received PDCCH indicates one transmission.

Optionally, the one-time transmission may refer to one-time uplink transmission or one-time downlink transmission, and is not limited to one-time new data transmission or retransmission, or may also be only one-time retransmission; or may specifically be one uplink retransmission or one downlink retransmission. Therefore, when the network equipment schedules transmission, no matter the scheduled transmission is primary transmission or retransmission, a timer can be started, so that the terminal equipment is in an activated state, the terminal equipment can monitor the PDCCH, and the timely transmission of the service scheduled by the PDCCH is ensured.

In another specific embodiment of this embodiment 1, the terminal device may start or restart the first timer when the received PDCCH indicates one transmission for a specific service. It should be understood that the specific service may be a service with higher transmission requirement as described above, and will not be described herein. It should also be understood that the meaning of one transmission for the service is similar to that of the aforementioned one transmission, and is not described herein.

Optionally, in this embodiment of the present application, the specific service includes, but is not limited to: URLLC service, industrial internet of things service, vertical industry service, car networking service, and the like, and the meaning of the specific service is also applicable to other embodiments of the present application, and will not be described in detail later.

In still another specific embodiment of this embodiment 1, the terminal device may start or restart the first timer when the resource indicated by the received PDCCH satisfies a certain attribute.

Optionally, in this embodiment of the present application, the attribute of the resource includes, but is not limited to, at least one of the following:

1. subcarrier interval information of resource authorization or resource configuration;

2. transmitting time length information of a physical shared channel of resource authorization or resource configuration;

3. specific types of information for resource authorization or resource configuration;

4. serving cell information to which resource authorization or resource configuration is applied;

5. modulation and Coding Scheme (MCS) table information applied by resource authorization or resource configuration;

6. MCS table information for transmission precoding to which a resource grant or resource configuration is applied;

7. uplink Control Information (UCI) Information for physical shared channel transmission to which resource authorization or resource configuration is applied;

8. information of the number of repeated transmissions to which the resource authorization or resource configuration applies;

9. redundant transmission version number information of repeated transmission applied by resource authorization or resource configuration;

10. transmission cycle information to which resource authorization or resource configuration applies;

11. resource authorization or configuration authorization timer information to which the resource configuration applies;

12. modulation order, code rate and corresponding transmission block size information applied by resource authorization or resource configuration;

13. parameter information of resource authorization or configuration authorization applied by resource configuration;

14. Semi-Persistent Scheduling (SPS) configuration information to which resource grant or resource configuration is applied;

15. service information applied by resource authorization or resource configuration;

16. logical channel information to which resource authorization or resource configuration applies;

17. logical channel group information to which resource authorization or resource configuration is applied;

18. priority information of resource authorization or resource configuration;

19. radio Network Temporary Identity (RNTI) information used for scheduling resource authorization or resource configuration;

20. and service information corresponding to resource authorization or resource configuration.

As an example and not by way of limitation, the condition that the resource indicated by the PDCCH satisfies a certain attribute may mean that the subcarrier interval of the resource grant or the resource configuration is a specific subcarrier interval, the priority of the resource grant or the resource configuration is a specific priority, and the corresponding service of the resource grant or the resource configuration is a specific type of service.

In yet another specific embodiment of this embodiment 1, the terminal device may start or restart the first timer when the received PDCCH indicates one transmission for a specific logical channel.

Alternatively, the specific logical channel may be a logical channel carrying a specific service, and the specific logical channel may correspond to a specific logical channel identifier. It should be understood that the meaning of one transmission for a specific logical channel is similar to that of the aforementioned one transmission, and is not described herein.

In yet another specific embodiment of this embodiment 1, the terminal device may start or restart the first timer when the received PDCCH indicates one transmission for a specific logical channel group.

Alternatively, the specific logical channel group may be a logical channel group carrying a specific service, and the specific logical channel group may correspond to a specific logical channel group identifier. It should be understood that the meaning of one transmission for a specific logical channel group is similar to that of the aforementioned one transmission, and is not described herein.

Optionally, in this embodiment of the present application, the starting time of the first timer may be a first time after the PDCCH is received, that is, after the terminal device receives the PDCCH, in a scheduling transmission (uplink transmission or downlink transmission) process, the terminal device may be in an activated state, so that the terminal device may monitor the PDCCH, and ensure timely transmission of a service.

Alternatively, the first Time may be a symbol (symbol), a Transmission Time Interval (TTI), or a slot (slot), for example, the start Time of the first timer may be the first symbol, the first TTI, or the first slot after the PDCCH reception is finished.

Optionally, in this embodiment of the application, a duration range of the first timer includes a starting time of a harq rtt timer corresponding to the PDCCH.

In other words, the duration range of the first timer and the preset duration range of the HARQ RTT timer overlap or partially overlap, that is, the duration range of the first timer at least partially covers the preset duration range of the HARQ RTT timer.

Because the terminal device is in the inactive state before the HARQ RTT timer expires, and does not monitor the PDCCH, in this embodiment of the present application, the terminal device can enter the active state in advance by configuring the start time of the first timer before the HARQ RTT timer expires, so that the PDCCH can be monitored in time, and the service can be scheduled in time.

Optionally, as an embodiment, the HARQ RTT timer may time out when the first timer is started, that is, the stop condition of the HARQ RTT timer is that the first timer is started or restarted.

Optionally, as another embodiment, the HARQ RTT timer may time out after the first timer is started for a certain time, that is, the stop condition of the HARQ RTT timer may be a certain time after the first timer is started or restarted. Optionally, in a specific embodiment, a certain time after the first timer is started may be before a predetermined time of the HARQ RTT timer, so that the terminal device can be ensured to enter an active state in advance, and thus, the PDCCH is ensured to be monitored in time, and the service is scheduled in time.

Optionally, as a further embodiment, the first timer is configured to expire by the first timer at a time before the HARQ RTT timer is started. That is, the stop condition of the first timer is a time before the HARQ RTT timer starts, for example, a symbol or a slot before the HARQ RTT timer starts.

Optionally, as a further embodiment, the first timer is configured to time out when the HARQ RTT timer is started. Namely, the stop condition of the first timer is that the HARQ RTT timer is started.

Optionally, as a further embodiment, the first timer is configured to time out after a period of time after the HARQ RTT timer is started. That is, the stop time of the first timer is a certain time after the HARQ RTT timer is started, for example, an nth symbol or an nth slot after the HARQ RTT timer is started, where N is 1 or another value.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer at a first time before the end of the corresponding uplink transmission.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer when the corresponding uplink transmission is ended.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer at a first time after the end of the corresponding uplink transmission.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer at a first time before the start of the corresponding uplink transmission.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer when the corresponding uplink transmission starts.

Optionally, as a further embodiment, the first timer may also be configured to stop the first timer at a first time after the start of the corresponding uplink transmission.

It should be understood that the uplink transmission herein includes, but is not limited to: for the first time, the meaning of PUSCH initial transmission, PUSCH transmission, and PUCCH transmission may refer to the related description in other embodiments, and details are not repeated here.

Optionally, as another embodiment, the first timer is configured to have the same or different duration for uplink scheduling and downlink scheduling. That is, for uplink scheduling and downlink scheduling, the first timer may be configured to have a corresponding duration, and the corresponding durations may be the same or different.

Optionally, in this embodiment of the present application, the duration of the first timer may also be in units of a symbol (symbol), a Transmission Time Interval (TTI), a slot (slot), or the like.

In addition, optionally, the terminal device may also stop the first timer when receiving a DRX Command MAC CE or a Long DRX Command MAC CE or the first timer reaches a predetermined time.

In addition, optionally, if the network device configures the terminal device with the DRX short cycle, the terminal device may also start or restart a short cycle timer (DRX-ShortCycleTimer) at a time after the first timer expires, for example, a first symbol after the timeout or a first time slot.

In addition, optionally, the first timer duration may also be configurable.

In addition, optionally, the first timer duration may be related to a service characteristic, that is, the duration of the first timer may be configured according to a service characteristic, such as a service type, a Qos requirement, and the like, for example, a longer duration may be configured when the service type is a delay sensitive service, or a longer duration may be configured when the Qos requirement is higher.

Therefore, in the embodiment of the present application, by configuring the newly defined timer, even when the PDCCH schedules a service, no matter whether the service is newly transmitted or retransmitted, the terminal device can be ensured to be in an activated state, so that the service can be ensured to be scheduled in time.

Example 2: the first timer is an uplink retransmission timer drx-retransmission timerll.

That is, the existing drx-retransmission timerll can be reused to ensure that the terminal device is in an active state when the network device schedules transmission.

For example, the stop condition of drx-retransmission timerll may be modified so that the terminal device may be in an active state before the HARQ RTT timer starts or before it times out, thereby ensuring timely monitoring of the PDCCH.

Optionally, as an optional embodiment of this embodiment 2, the stop condition of the first timer may be a first time before the HARQ RTT uplink timer is started, that is, the first timer is stopped at the first time before the HARQ RTT uplink timer is started.

Specifically, at a first time before drx-HARQ-RTT-timerll of a HARQ process used for uplink transmission scheduled by the PDCCH is started, for example, an nth symbol or an nth slot before drx-HARQ-RTT-timerll is started, where N may be 1 or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as a specific embodiment of the embodiment 2, the stop condition of the first timer may be when an HARQ RTT uplink timer is started.

That is, when drx-HARQ-RTT-timerll of the HARQ process used for uplink transmission (i.e., PUSCH transmission) scheduled by the PDCCH is turned on, drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be a period of time after the HARQ RTT uplink timer is started, that is, the first timer is stopped at a first time after the HARQ RTT uplink timer is started.

Specifically, at a first time after drx-HARQ-RTT-timerll of a HARQ process used for uplink transmission scheduled by the PDCCH is turned on, for example, an nth symbol or an nth slot after drx-HARQ-RTT-timerll is turned on, where N may be 1 or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, the specific time may be before a preset duration of drx-HARQ-RTT-timerll, that is, before drx-HARQ-RTT-timerll expires, by controlling drx-retransmission timerll to be in an on state, it may be ensured that the terminal device keeps monitoring the PDCCH.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be a first time before the end of the initial transmission of the corresponding physical uplink shared channel PUSCH.

Specifically, at a first time before the PUSCH initial transmission scheduled by the PDCCH is ended, for example, an nth symbol or an nth slot before the PUSCH initial transmission is ended, where N may be 1, or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of this embodiment 2, the stopping condition of the first timer may be to stop the uplink retransmission timer of the corresponding HARQ process when the initial transmission of the corresponding physical uplink shared channel PUSCH ends, that is, when the initial transmission of the PUSCH scheduled by the PDCCH ends. Specifically, when the PUSCH primary transmission scheduled by the PDCCH is finished, drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be a first time after the end of the initial transmission of the corresponding physical uplink shared channel PUSCH.

Specifically, at a first time after the PUSCH primary transmission scheduled by the PDCCH is finished, for example, an nth symbol or an nth slot after the PUSCH primary transmission is finished, where N may be 1, or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, the first time may be before a preset duration of drx-HARQ-RTT-timerll, that is, before drx-HARQ-RTT-timerll expires, by controlling drx-retransmission timerll to be in an on state, it may be ensured that the terminal device keeps monitoring the PDCCH.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be a first time before the initial transmission of the corresponding physical uplink shared channel PUSCH starts.

Specifically, at a first time before the PUSCH initial transmission scheduled by the PDCCH is turned on, for example, an nth symbol or an nth slot before the PUSCH initial transmission is turned on, where N may be 1, or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be when the initial transmission of the corresponding physical uplink shared channel PUSCH starts. Specifically, when the PUSCH initial transmission scheduled by the PDCCH is turned on, drx-retransmission timerll of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 2, the stop condition of the first timer may be a first time after the initial transmission of the corresponding physical uplink shared channel PUSCH is started.

Specifically, at a first time after the PUSCH initial transmission scheduled by the PDCCH starts, for example, an nth symbol or an nth slot after the PUSCH initial transmission starts, where N may be 1 or another value, the drx-retransmission timerll of the corresponding HARQ process is stopped.

It should be understood that in embodiment 2, the starting condition or the stopping condition of drx-retransmission timerll may also be other times after the PDCCH is received and before drx-HARQ-RTT-timerll is timed out.

Example 3: the first timer is a downlink retransmission timer drx-retransmission timerdl.

That is, the existing drx-retransmission timerdl can be reused to ensure that the terminal device is in an activated state when the network device schedules transmission.

For example, the stop condition of drx-retransmission timerdl may be modified such that the terminal device may be in an active state before the HARQ RTT timer starts or times out, thereby ensuring timely monitoring of the PDCCH.

Optionally, as an optional embodiment of the embodiment 3, the stop condition of the first timer may be a first time before the HARQ RTT downlink timer is started, that is, the first timer is stopped at the first time before the HARQ RTT downlink timer is started.

Specifically, at a first time before drx-HARQ-RTT-TimerDL of an HARQ process used for PUCCH transmission scheduled by a PDCCH is turned on, for example, an nth symbol or an nth slot before drx-HARQ-RTT-TimerDL is turned on, where N may be 1 or another value, the drx-retransmission TimerDL of the corresponding HARQ process is stopped.

Optionally, as a specific embodiment of the embodiment 3, the stop condition of the first timer may be when a HARQ RTT downlink timer is started.

That is, when drx-HARQ-RTT-TimerDL of the HARQ process used for PUCCH transmission scheduled by the PDCCH is turned on, drx-retransmission TimerDL of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 3, the stop condition of the first timer may be a certain time after the HARQ RTT downlink timer is started, that is, the first timer is stopped at a first time after the HARQ RTT downlink timer is started. Specifically, at the first time after the drx-HARQ-RTT-TimerDL of the HARQ process adopted for pucch transmission scheduled by the PDCCH is turned on, the drx-retransmission TimerDL of the corresponding HARQ process is stopped.

Optionally, the first time may be before a preset duration of drx-HARQ-RTT-TimerDL, that is, before drx-HARQ-RTT-TimerDL expires, by controlling drx-retransmission TimerDL to be in an on state, it may be ensured that the terminal device keeps monitoring the PDCCH.

Optionally, as another specific embodiment of the embodiment 3, the stop condition of the first timer may be to stop the downlink retransmission timer of the corresponding HARQ process at a first time before the end of the initial transmission of the corresponding PUCCH, that is, at a first time before the end of the initial transmission of the PUCCH scheduled by the PDCCH.

Specifically, at a first time before the end of the initial transmission of the PUCCH scheduled by the PDCCH, for example, the nth symbol or nth slot before the end of the initial transmission of the PUCCH, where N may be 1, or another value, the drx-retransmission timerdl of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 3, the stopping condition of the first timer may be to stop the downlink retransmission timer of the corresponding HARQ process when the corresponding PUCCH initial transmission ends, that is, when the PUCCH initial transmission scheduled by the PDCCH ends.

Specifically, when the initial transmission of the PUCCH scheduled by the PDCCH is finished, drx-retransmission timerdl of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 3, the stop condition of the first timer may be a first time after the end of the first transmission of the corresponding PUCCH.

Specifically, at a first time after the PUCCH initial transmission scheduled by the PDCCH is ended, for example, the mth symbol or the mth slot after the PUCCH initial transmission is ended, where M may be 1, or another value, the drx-retransmission timerdl of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 3, the stop condition of the first timer may be a first time before the start of the initial transmission of the corresponding PUCCH.

Specifically, at a first time before the PUCCH initial transmission scheduled by the PDCCH starts, for example, the K-th symbol or K-th slot before the PUCCH initial transmission starts, where K may be 1, or another value, the drx-retransmission timerdl of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of this embodiment 3, the stop condition of the first timer may be when the initial transmission of the corresponding PUCCH starts. Specifically, when the initial transmission of the PUCCH scheduled by the PDCCH is turned on, drx-retransmission timerdl of the corresponding HARQ process is stopped.

Optionally, as another specific embodiment of the embodiment 3, the stop condition of the first timer may be a first time after the initial transmission of the corresponding PUCCH is turned on.

Specifically, at a first time after the initial transmission of the PUCCH scheduled by the PDCCH starts, for example, the P-th symbol or P-th slot after the initial transmission of the PUCCH is started, where P may be 1, or another value, the drx-retransmission timerdl of the corresponding HARQ process is stopped.

It should be understood that in this embodiment 3, the starting condition or the stopping condition of drx-retransmission TimerDL may also be other times after the PDCCH is received and before drx-HARQ-RTT-TimerDL is timed out.

Example 4: the first timer is an inactivity timer drx-inactivity timer.

That is, the existing drx-inactivity timer can be reused to ensure that the terminal device is in an activated state when the network device schedules transmission.

For example, the definition of drx-inactivity timer may be modified, and the start condition or the stop condition may be modified such that the terminal device may enter the active state before the HARQ RTT timer expires, thereby ensuring timely monitoring of the PDCCH.

Optionally, as an embodiment, the drx-inactivytytytimer may be turned on or restarted when the received PDCCH indicates one transmission.

Optionally, the one-time transmission may be one-time uplink transmission, one-time downlink transmission, one-time uplink retransmission, or one-time downlink retransmission.

Optionally, the terminal device may turn on or turn back on the drx-inactivity timer at a specific time after the PDCCH reception is ended, for example, at the first symbol.

Similar to example 1, the activation condition of the drx-inactivytytimer may also be one of the following:

the received PDCCH indicates one transmission for a specific service; alternatively, the first and second electrodes may be,

if the received resources indicated by the PDCCH meet certain attributes; alternatively, the first and second electrodes may be,

if the received PDCCH indicates a transmission for a specific logical channel; alternatively, the first and second electrodes may be,

if the received PDCCH indicates a transmission for a specific logical channel group;

the received PDCCH indicates new transmission;

the received PDCCH indicates the transmission, including new transmissions and retransmissions, either initial or retransmissions.

For specific implementation, reference may be made to the description related to embodiment 1, which is not described herein again.

It should be understood that the content included in the attribute that is satisfied by the resource indicated by the PDCCH may refer to the relevant description in embodiments 1 to 3, and is not described herein again.

The method for power allocation according to the embodiment of the present application is described in detail from the perspective of a terminal device with reference to fig. 2, and the method for power allocation according to another embodiment of the present application is described in detail from the perspective of a network device with reference to fig. 3. It should be understood that the description of the network device side and the description of the terminal device side correspond to each other, and similar descriptions may be referred to above, and are not repeated herein to avoid repetition.

Fig. 3 is a schematic flow chart of a method 300 of power allocation according to another embodiment of the present application, the method 300 may be performed by a network device in the communication system shown in fig. 1, as shown in fig. 3, the method 300 includes the following:

s310, a network device configures a first timer for a terminal device, wherein the first timer is used for enabling the terminal device to be in an activated state under the condition that the network device schedules transmission.

Optionally, the first timer is a newly defined timer, and a duration of the first timer is a specific duration after receiving the PDCCH.

Optionally, the starting condition or the restarting condition of the first timer is that a physical downlink control channel PDCCH indicates one transmission. Optionally, the one-time transmission is one of:

one uplink transmission, one downlink transmission, one retransmission, one uplink retransmission, and one downlink retransmission.

Optionally, the start condition or restart condition of the first timer comprises at least one of: the PDCCH indicates one transmission for a specific service; the resources indicated by the PDCCH meet certain attributes; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group; the PDCCH indicates one transmission for retransmission.

Optionally, the starting time or the restarting time of the first timer is a first time after the PDCCH reception is finished.

Optionally, when the first timer is in an on state, the terminal device is in an active state.

Optionally, the duration range of the first timer includes an opening time of a hybrid automatic repeat request HARQ backhaul RTT timer corresponding to the PDCCH.

Optionally, the first timer is configured to time out the HARQ RTT timer when the first timer is on.

Optionally, the first timer is configured to time out the HARQ RTT timer after the first timer is started for a period of time.

Optionally, the first timer is configured to expire at a first time before the HARQ RTT timer starts.

Optionally, the first timer is configured to time out when the HARQ RTT timer is on.

Optionally, the first timer is configured to time out after the HARQ RTT timer is started for a period of time.

Optionally, the first timer is configured to stop the first timer at a first time before the end of the corresponding uplink transmission.

Optionally, the first timer is configured to stop the first timer when the corresponding uplink transmission ends.

Optionally, the first timer is configured to stop the first timer at a first time after the end of the corresponding uplink transmission.

Optionally, the first timer is configured to stop the first timer at a first time before the start of the corresponding uplink transmission.

Optionally, the first timer is configured to be stopped when the corresponding uplink transmission starts.

Optionally, the first timer is configured to stop the first timer at a first time after the start of the corresponding uplink transmission.

Uplink transmissions here include, but are not limited to: PUSCH primary transmission, PUSCH transmission, PUCCH transmission.

Optionally, the first timer is configured to have the same or different duration for uplink scheduling and downlink scheduling.

Optionally, the first timer is an uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped when the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is an uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped for a period of time after the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time before the end of the initial transmission of the corresponding PUSCH.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding physical uplink shared channel PUSCH is finished.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding physical uplink shared channel PUSCH is finished.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time before the start of the initial transmission of the corresponding PUSCH.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding PUSCH starts.

Optionally, the first timer is the uplink retransmission timer, wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUSCH is started.

Optionally, the first timer is a downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped when the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is a downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped for a period of time after the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is the downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time before the end of the initial transmission of the corresponding physical uplink control channel PUCCH.

Optionally, the first timer is the downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding physical uplink control channel PUCCH is finished.

Optionally, the first timer is the downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUCCH is finished.

Optionally, the first timer is the downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time before the initial transmission of the corresponding PUCCH is started.

Optionally, the first timer is the downlink retransmission timer, wherein the downlink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding PUCCH starts.

Optionally, the first timer is the downlink retransmission timer, and the downlink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUCCH is started.

Optionally, the first timer is an inactivity timer, wherein the first timer is started or restarted when the PDCCH indicates one transmission.

Optionally, the one-time transmission is one of: one uplink transmission, one downlink transmission, one retransmission, one uplink retransmission, and one downlink retransmission.

Optionally, the first timer is an inactive timer, and the start condition or the restart condition of the first timer includes at least one of: the PDCCH indicates one transmission for a specific service; the resources indicated by the PDCCH meet certain attributes; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group.

Optionally, the starting time of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

Optionally, the duration of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

Optionally, the specific service is a service with a quality of service QoS greater than a first QoS threshold or a service with a delay requirement lower than a first delay threshold.

Optionally, the specific logical channel is a logical channel corresponding to a specific service.

Optionally, the specific logical channel group is a logical channel group corresponding to a specific service.

Optionally, the specific logical channel corresponds to a specific logical channel identifier.

Optionally, the specific logical channel group corresponds to a specific logical channel group identifier.

While the method embodiments of the present application have been described in detail with reference to fig. 2 to 3, the apparatus embodiments of the present application will be described in detail with reference to fig. 4 to 7, it should be understood that the apparatus embodiments correspond to the method embodiments, and similar descriptions may refer to the method embodiments.

Fig. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. The terminal device 400 is configured with a first timer, where the first timer is used to enable the terminal device to be in an active state when a network device schedules transmission.

Optionally, the terminal device includes: and the determining module is used for determining whether the first timer is started or restarted under the condition that the terminal equipment is in the activated state.

Optionally, the terminal device includes: a processing module 410, configured to start or restart the first timer if the received PDCCH indicates one transmission.

Optionally, the processing module 410 is further configured to: if the received PDCCH indicates one-time transmission aiming at a specific service, starting or restarting the first timer; or, if the resource indicated by the received PDCCH meets a certain attribute, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel group, starting or restarting the first timer.

Optionally, the processing module 410 is specifically configured to: and starting or restarting the first timer at a first moment after the PDCCH reception is finished.

Optionally, the first timer is configured to time out when the HARQ RTT timer is on. Optionally, the first timer is configured to time out after the HARQ RTT timer is started for a period of time.

Optionally, the first timer is an uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process when an HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is an uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process for a period of time after an HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: the processing module 410 is configured to stop the uplink retransmission timer of the corresponding HARQ process at a first time before the end of the initial transmission of the corresponding PUSCH.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process when the initial transmission of the corresponding physical uplink shared channel PUSCH is finished.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: the processing module 410 is configured to stop the uplink retransmission timer of the corresponding HARQ process at a first time after the end of the initial transmission of the corresponding PUSCH.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process at a first time before a start of initial transmission of a corresponding PUSCH.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process when a corresponding PUSCH initial transmission starts.

Optionally, the first timer is the uplink retransmission timer, and the terminal device includes: a processing module 410, configured to stop an uplink retransmission timer of a corresponding HARQ process at a first time after a start of initial transmission of a corresponding PUSCH.

Optionally, the first timer is a downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process when an HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is a downlink retransmission timer, and the terminal device includes: the processing module 410 is configured to stop the downlink retransmission timer of the corresponding HARQ process for a period of time after the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process at a first time before the end of initial transmission of a corresponding physical uplink control channel PUCCH.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process when initial transmission of a corresponding physical uplink control channel PUCCH is finished.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop the downlink retransmission timer of the corresponding HARQ process at a first time after the initial transmission of the corresponding PUCCH is finished.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process at a first time before a start of initial transmission of a corresponding PUCCH.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process when initial transmission of a corresponding PUCCH starts.

Optionally, the first timer is the downlink retransmission timer, and the terminal device includes: a processing module 410, configured to stop a downlink retransmission timer of a corresponding HARQ process at a first time after initial transmission of a corresponding PUCCH is started.

Optionally, the first timer is an inactive timer, and the terminal device includes: a processing module 410, configured to start or restart the first timer if the received PDCCH indicates one transmission.

Optionally, the one-time transmission is one of:

Optionally, the first timer is an inactive timer, and the terminal device includes: the processing module 410 is configured to:

if the received PDCCH indicates one-time transmission aiming at a specific service, starting or restarting the first timer; or, if the resource indicated by the received PDCCH meets a certain attribute, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel group, starting or restarting the first timer.

Optionally, the specific logical channel group corresponds to a specific logical channel group identity.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to a terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing a corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.

Fig. 5 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of fig. 5 includes:

a communication module 510, configured to configure a first timer for a terminal device, where the first timer is configured to enable the terminal device to be in an active state when the network device schedules transmission.

Optionally, in this embodiment of the present application, the network device 500 may also include:

and the processing module is used for controlling the starting or restarting of a second timer, wherein the second timer corresponds to the first timer on the terminal equipment.

Specifically, the starting condition or the restarting condition of the second timer may refer to the description related to the first timer at the terminal device side, that is, the processing module of the network device may adopt operations similar to those related to the processing module of the terminal device to control the state of the second timer maintained at the network side, and for brevity, details are not repeated here.

Optionally, the starting condition or the restarting condition of the first timer is that a physical downlink control channel PDCCH indicates one transmission.

Optionally, the start condition or restart condition of the first timer comprises at least one of: the PDCCH indicates one transmission for a specific service; the resources indicated by the PDCCH meet certain attributes; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group; the PDCCH indicates one transmission for a specific logical channel group.

Optionally, the first timer is an inactive timer, and the start condition or the restart condition of the first timer includes at least one of:

the PDCCH indicates one transmission for a specific service; the resources indicated by the PDCCH meet certain attributes; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to a terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 500 are respectively for implementing corresponding flows of the network device in the method 300 shown in fig. 3, and are not described herein again for brevity.

Fig. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 6, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application. The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, as shown in fig. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.

Optionally, the communication device 600 may specifically be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 600 may specifically be a mobile terminal/terminal device in this embodiment, and the communication device 600 may implement a corresponding process implemented by the mobile terminal/terminal device in each method in this embodiment, which is not described herein again for brevity.

Fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the chip 700 may further include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application. The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.

Optionally, 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 in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 8 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 8, the communication system 900 includes a terminal device 910 and a network device 920. The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of transmitting data, comprising:

monitoring a Physical Downlink Control Channel (PDCCH), and determining to start a first timer in response to that resources indicated by the PDCCH meet a target attribute, wherein the first timer is a timer configured on a terminal device and is used for enabling the terminal device to be still in an activated state when detecting that an inactivated timer of the terminal device is not started under the condition that network equipment schedules transmission;

monitoring the starting condition of a HARQ RTT timer, and determining the overtime time of the first timer based on the starting time of the HARQ RTT timer;

monitoring the starting time of the first timer, and determining the overtime time of the HARQ RTT timer based on the starting time of the first timer;

the resource satisfying target attribute indicated by the PDCCH means that the subcarrier interval of the resource authorization or the resource configuration is a specific subcarrier interval, the priority of the resource authorization or the resource configuration is a specific priority, and the corresponding service of the resource authorization or the resource configuration is a specific type of service.

2. The method of claim 1, wherein the first timer is a newly defined timer, and wherein a duration of the first timer is a specific duration after receiving a Physical Downlink Control Channel (PDCCH).

3. The method of claim 1, further comprising:

and under the condition that the terminal equipment is in an activated state, determining whether the first timer is started or restarted.

4. The method of claim 1, further comprising:

and if the received PDCCH indicates one-time transmission, starting or restarting the first timer.

5. The method of claim 4, wherein the one transmission is one of:

6. The method of claim 4, further comprising:

if the received PDCCH indicates one-time transmission aiming at a specific service, starting or restarting the first timer; or the like, or, alternatively,

if the received PDCCH indicates one-time transmission aiming at a specific logic channel, starting or restarting the first timer; or the like, or, alternatively,

and if the received PDCCH indicates one transmission aiming at a specific logic channel group, starting or restarting the first timer.

7. The method of claim 4, wherein the starting or restarting the first timer comprises: starting or restarting the first timer at a first time after the PDCCH reception is finished.

8. The method of claim 1, wherein the terminal device is in an active state when the first timer is in an on state.

9. The method of claim 1, wherein a duration range of the first timer comprises a starting time of a hybrid automatic repeat request, HARQ, backhaul RTT timer corresponding to the PDCCH.

10. The method of claim 1, wherein the first timer is configured to timeout a HARQ RTT timer when the first timer is started.

11. The method of claim 1, wherein the first timer is configured to expire a HARQ RTT timer after the first timer is started for a period of time.

12. The method of claim 1, wherein the first timer is configured to expire at a first time before a HARQ RTT timer is started.

13. The method of claim 1, wherein the first timer is configured to time out when a HARQ RTT timer is started.

14. The method of claim 1, wherein the first timer is configured to time out after a HARQ RTT timer is started for a period of time.

15. The method of claim 1, wherein the first timer is configured to have a same or different duration for uplink scheduling and downlink scheduling.

16. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and when the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started, stopping the uplink retransmission timer of the corresponding HARQ process.

17. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and stopping the uplink retransmission timer of the corresponding HARQ process for a period of time after the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

18. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and stopping the uplink retransmission timer of the corresponding HARQ process at the first moment before the end of the initial transmission of the corresponding PUSCH.

19. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and when the initial transmission of the corresponding physical uplink shared channel PUSCH is finished, stopping the uplink retransmission timer of the corresponding HARQ process.

20. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and stopping the uplink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUSCH is finished.

21. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and stopping the uplink retransmission timer of the corresponding HARQ process at the first moment before the initial transmission of the corresponding PUSCH starts.

22. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and when the initial transmission of the corresponding PUSCH starts, stopping the uplink retransmission timer of the corresponding HARQ process.

23. The method of claim 1, wherein the first timer is an uplink retransmission timer, and wherein the method further comprises: and stopping the uplink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUSCH is started.

24. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and when the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started, stopping the downlink retransmission timer of the corresponding HARQ process.

25. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and stopping the downlink retransmission timer of the corresponding HARQ process for a period of time after the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

26. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and stopping the downlink retransmission timer of the corresponding HARQ process at a first moment before the initial transmission of the corresponding physical uplink control channel PUCCH is finished.

27. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and when the initial transmission of the corresponding physical uplink control channel PUCCH is finished, stopping the downlink retransmission timer of the corresponding HARQ process.

28. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and stopping the downlink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUCCH is finished.

29. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and stopping the downlink retransmission timer of the corresponding HARQ process at the first moment before the initial transmission of the corresponding PUCCH is started.

30. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises:

and when the initial transmission of the corresponding PUCCH is started, stopping the downlink retransmission timer of the corresponding HARQ process.

31. The method of claim 1, wherein the first timer is a downlink retransmission timer, and wherein the method further comprises: and stopping the downlink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUCCH is started.

32. The method of claim 1, wherein the first timer is an inactivity timer, the method further comprising: and if the received PDCCH indicates one-time transmission, starting or restarting the first timer.

33. The method of claim 32, wherein the one transmission is one of:

34. The method of claim 1, wherein the first timer is an inactivity timer, the method further comprising:

35. The method of any one of claims 1 to 34, wherein an on time of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

36. The method of any one of claims 1 to 34, wherein the duration of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

37. The method according to claim 6 or 34, wherein the specific traffic is a traffic with a quality of service QoS greater than a first QoS threshold or a traffic with a latency requirement lower than a first latency threshold.

38. The method according to claim 6 or 34, wherein the specific logical channel is a logical channel corresponding to a specific service.

39. The method according to claim 6 or 34, wherein the specific logical channel group is a logical channel group corresponding to a specific service.

40. The method according to claim 6 or 34, wherein the specific logical channel corresponds to a specific logical channel identification.

41. The method of claim 6 or 34, wherein the specific logical channel group corresponds to a specific logical channel group identity.

42. A method of transmitting data, comprising:

the method comprises the steps that a network device configures a first timer for a terminal device, wherein the first timer is used for enabling an inactive timer of the terminal device to be still in an active state under the condition that the network device schedules transmission, the terminal device is used for monitoring a Physical Downlink Control Channel (PDCCH), the first timer is determined to be started in response to that a resource indicated by the PDCCH meets a target attribute, the terminal device is used for monitoring the starting condition of a hybrid automatic repeat request (HARQ) Round Trip Time (RTT) timer, the timeout time of the first timer is determined based on the starting time of the HARQ RTT timer, the terminal device is also used for monitoring the starting time of the first timer, and the timeout time of the HARQ RTT timer is determined based on the starting time of the first timer, wherein the resource indicated by the PDCCH meets the target attribute and indicates that the resource authorization or the inter-carrier interval of the resource configuration is a specific sub-carrier interval, The priority of the resource authorization or the resource configuration is a specific priority, and the corresponding service of the resource authorization or the resource configuration is a specific type of service.

43. The method of claim 42, wherein the first timer is a newly defined timer, and wherein a duration of the first timer is a specific duration after receiving a Physical Downlink Control Channel (PDCCH).

44. The method of claim 42, wherein an on condition or a restart condition of the first timer indicates one transmission for a Physical Downlink Control Channel (PDCCH).

45. The method of claim 44, wherein the one transmission is one of:

46. The method of claim 42, wherein the start condition or restart condition of the first timer comprises at least one of: the PDCCH indicates one transmission for a specific service; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group; the PDCCH indicates one transmission for a specific logical channel group.

47. The method of claim 42, wherein a starting time or a restarting time of the first timer is a first time after PDCCH reception ends.

48. The method of claim 42, wherein the terminal device is in an active state when the first timer is in an on state.

49. The method of claim 42, wherein a duration range of the first timer comprises an opening time of a hybrid automatic repeat request (HARQ) backhaul RTT timer corresponding to a PDCCH.

50. The method of claim 42, wherein the first timer is configured to timeout a HARQ RTT timer when the first timer is started.

51. The method of claim 42, wherein the first timer is configured to timeout a HARQ RTT timer after the first timer is started for a period of time.

52. The method of claim 42, wherein the first timer is configured to expire at a first time before a HARQ RTT timer is started.

53. The method of claim 42, wherein the first timer is configured to expire when a HARQ RTT timer is started.

54. The method of claim 42, wherein the first timer is configured to expire after a HARQ RTT timer is started for a period of time.

55. The method of claim 42, wherein the first timer is configured to have a same or different duration for uplink scheduling and downlink scheduling.

56. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped when an HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

57. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped a period of time after an HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

58. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time before the end of the corresponding PUSCH initial transmission.

59. The method according to claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped when the initial transmission of a corresponding physical uplink shared channel, PUSCH, is finished.

60. The method according to claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time after the end of the initial transmission of the corresponding Physical Uplink Shared Channel (PUSCH).

61. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time before the start of the corresponding PUSCH initial transmission.

62. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped when a corresponding PUSCH initial transmission is started.

63. The method of claim 42, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of the corresponding HARQ process is stopped at a first time after the start of the initial transmission of the corresponding PUSCH.

64. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of a corresponding HARQ process is stopped when an HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

65. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of a corresponding HARQ process is stopped a period of time after an HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

66. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time before the end of the initial transmission of the corresponding Physical Uplink Control Channel (PUCCH).

67. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding Physical Uplink Control Channel (PUCCH) is finished.

68. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUCCH is finished.

69. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time before the beginning of the initial transmission of the corresponding PUCCH.

70. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped when the initial transmission of the corresponding PUCCH starts.

71. The method of claim 42, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUCCH is started.

72. The method of claim 42, wherein the first timer is an inactivity timer, wherein the first timer is started or restarted if PDCCH indicates a transmission.

73. The method of claim 72, wherein the one transmission is one of:

74. The method according to claim 42, wherein the first timer is an inactive timer, and wherein the start-up condition or the restart condition of the first timer comprises at least one of: the PDCCH indicates one transmission for a specific service; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group.

75. The method according to any of claims 42-74, wherein the first timer is started in symbol, transmission time interval, TTI, or slot.

76. The method of any one of claims 42 to 74, wherein the duration of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

77. The method according to claim 46 or 74, wherein said specific traffic is traffic with a quality of service QoS larger than a first QoS threshold or traffic with a latency requirement lower than a first latency threshold.

78. The method according to claim 46 or 74, wherein the specific logical channel is a logical channel corresponding to a specific service.

79. The method according to claim 46 or 74, wherein the specific logical channel group is a logical channel group corresponding to a specific service.

80. The method according to claim 46 or 74, wherein said specific logical channel corresponds to a specific logical channel identification.

81. The method of claim 46 or 74, wherein said specific logical channel group corresponds to a specific logical channel group identity.

82. A terminal device is configured with a first timer, where the first timer is configured to enable an inactive timer of the terminal device to be still in an active state under the condition that a network device schedules transmission, where the terminal device is configured to monitor a Physical Downlink Control Channel (PDCCH), determine to start the first timer in response to that a resource indicated by the PDCCH meets a target attribute, the terminal device is configured to monitor the starting condition of an HARQ RTT timer, determine a timeout time of the first timer based on the starting time of the HARQ RTT timer, and monitor a starting time of the first timer, determine the timeout time of the HARQ RTT timer based on the starting time of the first timer, where the resource indicated by the PDCCH meets the target attribute, where the resource authorization or a subcarrier interval of a resource configuration is a specific subcarrier interval The subcarrier interval, the priority of resource authorization or resource configuration of the method is a specific priority, and the corresponding service of the resource authorization or resource configuration is a specific type of service.

83. The terminal device of claim 82, wherein the first timer is a newly defined timer, and wherein a duration of the first timer is a specific duration after a Physical Downlink Control Channel (PDCCH) is received.

84. The terminal device of claim 82, wherein the terminal device comprises:

and the determining module is used for determining whether the first timer is started or restarted under the condition that the terminal equipment is in the activated state.

85. The terminal device of claim 82, wherein the terminal device comprises:

and the processing module is used for starting or restarting the first timer if the received PDCCH indicates one-time transmission.

86. The terminal device of claim 85, wherein the one transmission is one of:

87. The terminal device of claim 85, wherein the processing module is further configured to:

if the received PDCCH indicates one-time transmission aiming at a specific logic channel, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel group, starting or restarting the first timer.

88. The terminal device of claim 85, wherein the processing module is specifically configured to: and starting or restarting the first timer at a first moment after the PDCCH reception is finished.

89. The terminal device of claim 82, wherein the terminal device is in an active state when the first timer is in an on state.

90. The terminal device of claim 82, wherein a duration range of the first timer comprises a starting time of a hybrid automatic repeat request, HARQ, backhaul RTT timer corresponding to the PDCCH.

91. The terminal device of claim 82, wherein the first timer is configured to timeout a HARQ RTT timer when the first timer is started.

92. The terminal device of claim 82, wherein the first timer is configured to expire the HARQ RTT timer after the first timer is started for a period of time.

93. The terminal device of claim 82, wherein the first timer is configured to expire at a first time before a HARQ RTT timer is started.

94. The terminal device of claim 82, wherein the first timer is configured to expire when a HARQ RTT timer is started.

95. The terminal device of claim 82, wherein the first timer is configured to expire after a HARQ RTT timer is started for a period of time.

96. The terminal device of claim 82, wherein the first timer is configured to have a same or different duration for uplink scheduling and downlink scheduling.

97. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process when the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

98. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process within a period of time after the HARQ RTT uplink timer of the HARQ process scheduled by the PDCCH is started.

99. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process at a first moment before the end of the initial transmission of the corresponding PUSCH.

100. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process when the initial transmission of the corresponding physical uplink shared channel PUSCH is finished.

101. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUSCH is finished.

102. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process at a first moment before the initial transmission of the corresponding PUSCH starts.

103. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process when the initial transmission of the corresponding PUSCH starts.

104. The terminal device of claim 82, wherein the first timer is an uplink retransmission timer, and wherein the terminal device comprises: and the processing module is used for stopping the uplink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUSCH is started.

105. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process when the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

106. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process within a period of time after the HARQ RTT downlink timer of the HARQ process scheduled by the PDCCH is started.

107. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process at a first moment before the initial transmission of the corresponding physical uplink control channel PUCCH is finished.

108. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process when the initial transmission of the corresponding physical uplink control channel PUCCH is finished.

109. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process at a first moment after the initial transmission of the corresponding PUCCH is finished.

110. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process at a first moment before the initial transmission of the corresponding PUCCH is started.

111. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process when the initial transmission of the corresponding PUCCH is started.

112. The terminal device according to claim 82, wherein the first timer is a downlink retransmission timer, and the terminal device comprises: and the processing module is used for stopping the downlink retransmission timer of the corresponding HARQ process at the first moment after the initial transmission of the corresponding PUCCH is started.

113. The terminal device of claim 82, wherein the first timer is an inactivity timer, the terminal device comprising: and the processing module is used for starting or restarting the first timer if the received PDCCH indicates one-time transmission.

114. The terminal device of claim 113, wherein the one transmission is one of: one uplink transmission, one downlink transmission, one retransmission, one uplink retransmission, and one downlink retransmission.

115. The terminal device of claim 82, wherein the first timer is an inactivity timer, the terminal device comprising: the processing module is used for: if the received PDCCH indicates one-time transmission aiming at a specific service, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel, starting or restarting the first timer; or, if the received PDCCH indicates one transmission for a specific logical channel group, starting or restarting the first timer.

116. The terminal device of any one of claims 82-115, wherein an on time of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

117. The terminal device of any one of claims 82-115, wherein the duration of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

118. The terminal device of claim 87 or 115, wherein the specific traffic is traffic with a quality of service QoS greater than a first QoS threshold or traffic with a latency requirement below a first latency threshold.

119. The terminal device according to claim 87 or 115, wherein the specific logical channel is a logical channel corresponding to a specific service.

120. The terminal device of claim 87 or 115, wherein the specific logical channel group is a logical channel group corresponding to a specific service.

121. The terminal device of claim 87 or 115, wherein the specific logical channel corresponds to a specific logical channel identity.

122. The terminal device of claim 87 or 115, wherein the specific logical channel group corresponds to a specific logical channel group identity.

123. A network device, comprising:

a communication module, configured to configure a first timer for a terminal device, where the first timer is configured to enable an inactive timer of the terminal device to be still in an active state under a condition that the network device schedules transmission, the terminal device is configured to monitor a physical downlink control channel PDCCH, determine to start the first timer in response to that a resource indicated by the PDCCH satisfies a target attribute, the terminal device is configured to monitor a starting condition of an HARQ RTT timer, determine a timeout time of the first timer based on the starting time of the HARQ RTT timer, monitor a starting time of the first timer, and determine the timeout time of the HARQ timer based on the starting time of the first timer, where the resource indicated by the PDCCH satisfies the target attribute, where the resource authorization or a subcarrier interval of the resource configuration is a specific subcarrier interval, The priority of the resource authorization or the resource configuration is a specific priority, and the corresponding service of the resource authorization or the resource configuration is a specific type of service.

124. The network device of claim 123, wherein the first timer is a newly defined timer, and wherein a duration of the first timer is a specific duration after receiving a Physical Downlink Control Channel (PDCCH).

125. The network device of claim 123, wherein an on condition or a restart condition of the first timer is that a Physical Downlink Control Channel (PDCCH) indicates one transmission.

126. The network device of claim 125, wherein the one transmission is one of: one uplink transmission, one downlink transmission, one retransmission, one uplink retransmission, and one downlink retransmission.

127. The network device of claim 123, wherein the start condition or restart condition of the first timer comprises at least one of: the PDCCH indicates one transmission for a specific service; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group; the PDCCH indicates one transmission for a specific logical channel group.

128. The network device of claim 123, wherein a turn-on time or a restart time of the first timer is a first time after the PDCCH reception ends.

129. The network device of claim 123, wherein the terminal device is in an active state when the first timer is in an on state.

130. The network device of claim 123, wherein a duration range of the first timer comprises a starting time of a hybrid automatic repeat request, HARQ, backhaul RTT timer corresponding to the PDCCH.

131. The network device of claim 123, wherein the first timer is configured to timeout a HARQ RTT timer when the first timer is on.

132. The network device of claim 123, wherein the first timer is configured to expire the HARQ RTT timer after the first timer is started for a period of time.

133. The network device of claim 123, wherein the first timer is configured to expire at a first time before a HARQ RTT timer starts.

134. The network device of claim 123, wherein the first timer is configured to time out when a HARQ RTT timer is started.

135. The network device of claim 123, wherein the first timer is configured to expire after a HARQ RTT timer is started for a period of time.

136. The network device of claim 123, wherein the first timer is configured to have a duration that is the same or different for uplink scheduling and downlink scheduling.

137. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped when an HARQ RTT uplink timer of an HARQ process scheduled by the PDCCH is started.

138. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped a period of time after an HARQ RTT uplink timer of an HARQ process scheduled by the PDCCH is started.

139. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer for a corresponding HARQ process is stopped at a first time before the end of the corresponding PUSCH initial transmission.

140. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped when an initial transmission of a corresponding physical uplink shared channel, PUSCH, ends.

141. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer of a corresponding HARQ process is stopped at a first time after the end of the initial transmission of a corresponding physical uplink shared channel, PUSCH.

142. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer for a corresponding HARQ process is stopped at a first time before a corresponding PUSCH initial transmission is started.

143. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer for a corresponding HARQ process is stopped when a corresponding PUSCH initial transmission begins.

144. The network device of claim 123, wherein the first timer is an uplink retransmission timer, and wherein the uplink retransmission timer for a corresponding HARQ process is stopped at a first time after a corresponding PUSCH initial transmission is started.

145. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of a corresponding HARQ process is stopped when an HARQ RTT downlink timer of an HARQ process scheduled by a PDCCH is started.

146. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of a corresponding HARQ process is stopped a period of time after an HARQ RTT downlink timer of an HARQ process scheduled by the PDCCH is started.

147. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time before the end of the initial transmission of the corresponding physical uplink control channel, PUCCH.

148. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of a corresponding HARQ process is stopped when an initial transmission of a corresponding physical uplink control channel, PUCCH, is ended.

149. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer of the corresponding HARQ process is stopped at a first time after the end of the initial transmission of the corresponding PUCCH.

150. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer for the corresponding HARQ process is stopped at a first time before the beginning of the initial transmission of the corresponding PUCCH.

151. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer for a corresponding HARQ process is stopped when an initial transmission of a corresponding PUCCH starts.

152. The network device of claim 123, wherein the first timer is a downlink retransmission timer, and wherein the downlink retransmission timer for the corresponding HARQ process is stopped at a first time after the initial transmission of the corresponding PUCCH is started.

153. The network device of claim 123, wherein the first timer is an inactivity timer, wherein the first timer is started or restarted if PDCCH indicates one transmission.

154. The network device of claim 153, wherein the one transmission is one of: one uplink transmission, one downlink transmission, one retransmission, one uplink retransmission, and one downlink retransmission.

155. The network device of claim 123, wherein the first timer is an inactivity timer, and wherein the start condition or restart condition of the first timer comprises at least one of:

the PDCCH indicates one transmission for a specific service; PDCCH indicates one transmission for a specific logical channel; the PDCCH indicates one transmission for a specific logical channel group.

156. The network device of any one of claims 123-155, wherein an on time of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

157. The network device of any one of claims 123-155, wherein a duration of the first timer is in units of symbols, transmission time intervals, TTIs, or time slots.

158. The network device of claim 127 or 155, wherein the specific traffic is traffic with a quality of service, QoS, greater than a first QoS threshold or traffic with a latency requirement below a first latency threshold.

159. The network device of claim 127 or 155, wherein the specific logical channel is a logical channel corresponding to a specific service.

160. The network device of claim 127 or 155, wherein the specific logical channel group is a logical channel group corresponding to a specific service.

161. The network device of claim 127 or 155, wherein the particular logical channel corresponds to a particular logical channel identification.

162. The network device of claim 127 or 155, wherein the particular logical channel group corresponds to a particular logical channel group identification.

163. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 41.

164. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 41.

165. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 41.

166. A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 42 to 81.

167. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 42 to 81.

168. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 42 to 81.

169. A communication system, comprising:

the terminal device of any one of claims 82-122; and

a network device as claimed in any one of claims 123 to 162.