WO2023207568A1

WO2023207568A1 - Communication method and apparatus

Info

Publication number: WO2023207568A1
Application number: PCT/CN2023/087383
Authority: WO
Inventors: 刘南南
Original assignee: 华为技术有限公司
Priority date: 2022-04-25
Filing date: 2023-04-10
Publication date: 2023-11-02
Also published as: CN117014109A

Abstract

Disclosed in the embodiments of the present application are a communication method and apparatus. The method comprises: receiving first control information, which is transmitted in a multicast mode, wherein the first control information is used for scheduling first data, the first control information and/or the first data is associated with a first RNTI, and the first control information and/or the first data is associated with a first HARQ process; or receiving first data on a first resource, wherein the first resource and/or the first data is associated with the first RNTI, and the first data is associated with the first HARQ process; and stopping a first timer, wherein the first timer is a retransmission timer corresponding to DRX associated with a second RNTI, and the first timer is associated with the first HARQ process. A terminal device stops a first timer, thereby avoiding meaningless operation of the first timer, such that the power consumption of the terminal device can be reduced.

Description

A communication method and device

This application claims priority to the Chinese patent application filed with the China Patent Office on April 25, 2022, with the application number 202210440228.7 and the application title "A communication method and device", the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and device.

Background technique

In wireless communication systems, in order to save the power consumption of terminal equipment while ensuring effective data transmission, discontinuous reception (DRX) is introduced. When the network device configures the DRX function for the terminal device, the terminal device can be allowed to enter the sleep state at certain times, so that the terminal device does not need to continuously monitor the physical downlink control channel (PDCCH). During PDCCH, the terminal device can wake up from the sleep state, thus saving the power consumption of the terminal device to a certain extent.

Multimedia broadcast multicast service (MBMS) or multicast broadcast services (multicast and broadcast services, or multicast/broadcast services, or multicast-broadcast services, MBS) can effectively utilize communication resources. The network provides a point-to-multipoint service that sends data from a data source to multiple users to realize resource sharing and improve resource utilization, especially air interface resources. Generally, in an MBMS or MBS scenario, information can be broadcast to all users or sent to a group of paid contract users for viewing. It can help operators carry out multimedia advertising, free and paid TV channels, multimedia message group sending, etc. Commercial applications.

When unicast DRX and multicast DRX coexist, how to save energy in terminal equipment becomes a technical issue that needs to be solved.

Contents of the invention

The embodiment of the present application discloses a communication method and device for reducing the power consumption of terminal equipment.

In a first aspect, this application discloses a communication method, which can be applied to terminal equipment, can also be applied to modules (for example, chips or processors) in the terminal equipment, and can also be applied to realize all or part of the terminal equipment. Functional logic modules or software. The following description takes the execution subject being a terminal device as an example. This communication method may include:

The terminal device receives the first control information transmitted in a multicast manner, the first control information is used to schedule the first data, the first control information and/or the first data and the first radio network temporary identifier (RNTI) Associated, the first control information and/or the first data are associated with the first HARQ process; or,

receiving first data on a first resource, the first resource and/or the first data being associated with the first RNTI, and the first data being associated with the first HARQ process;

Stop the first timer, the first timer is the retransmission timer corresponding to the DRX associated with the second RNTI, and the first timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.

In the embodiment of the present application, after the terminal device receives the first control information for scheduling the first data transmitted in a multicast manner or receives the first data on the first resource, it indicates that the first HARQ process now provides the first RNTI For the corresponding multicast use, the multicast data corresponding to the second RNTI that was previously used in the first HARQ process will not be retransmitted, and the first certain multicast data will not be retransmitted. The timer is run so that the terminal device can receive the retransmission of the multicast data corresponding to the second RNTI of the first HARQ process. Therefore, if the second RNTI corresponds to the first timer of the multicast (that is, retransmission transmission timer) is still running, you can stop the first timer. Since the terminal equipment stops the first timer, meaningless operation of the first timer is avoided, and unnecessary PDCCH monitoring can be avoided, thereby reducing the power consumption of the terminal equipment.

As a possible implementation, the communication method may also include:

The terminal device stops a second timer, the second timer is a retransmission timer corresponding to the DRX associated with the first RNTI, and the second timer is associated with the first HARQ process; and/or

Stop the third timer. The third timer is a retransmission timer corresponding to the DRX associated with the unicast. The third timer is associated with the first HARQ process.

In the embodiment of the present application, after the terminal device receives the first control information for scheduling the first data transmitted in a multicast manner or receives the first data on the first resource, it indicates that the multicast corresponding to the first RNTI uses the third A HARQ process transmits the first data and will not retransmit other multicast data corresponding to the first RNTI that was previously transmitted using the first HARQ process and/or unicast data that was transmitted using the first HARQ process, and the second timer And/or the third timer is run so that the terminal device can receive other data previously transmitted using the first HARQ process and/or unicast retransmission of data transmitted using the first HARQ process. Therefore, the first HARQ process can be stopped. The RNTI corresponds to the second timer corresponding to the first HARQ process used before multicasting, and/or the third timer corresponding to unicast transmission before the first HARQ. Since the terminal equipment stops the second timer and/or the third timer, meaningless operation of the second timer and/or the third timer can be avoided, thereby avoiding unnecessary monitoring of the PDCCH, thereby reducing the cost of the terminal equipment. power consumption.

As a possible implementation, the communication method may also include:

The terminal device receives the second control information transmitted in a multicast manner, the second control information is used to schedule the second data, the second control information and/or the second data are associated with the second RNTI, and the second control information and/or the second data is associated with the second RNTI. The second data is associated with the first HARQ process; or,

receiving second data on a second resource, the second resource and/or the second data being associated with the second RNTI, and the second data being associated with the first HARQ process;

Start or restart a fourth timer, the fourth timer is a round trip time (RTT) timer corresponding to the DRX associated with the second RNTI, and the fourth timer is associated with the first HARQ process; and/or,

Start or restart the fifth timer. The fifth timer is the RTT timer corresponding to the DRX associated with the unicast. The fifth timer is associated with the first HARQ process.

In the embodiment of the present application, after the terminal device receives the second control information for scheduling the second data transmitted in a multicast manner or receives the second data on the second resource, in order to ensure that the terminal device can subsequently receive the network device For the retransmitted second data, the terminal device can start or restart the corresponding RTT timer. During the running time of the RTT timer, when no other timers are running on the terminal device, the terminal device does not need to monitor the PDCCH, which can reduce the time for the terminal device to monitor the PDCCH, thus reducing the power consumption of the terminal device.

As a possible implementation, the communication method may also include:

The fourth timer times out and the second data reception or decoding fails, the terminal device starts or restarts the first timer; and/or,

When the fifth timer times out and the reception or decoding of the second data fails, the terminal device starts or restarts the third timer.

In the embodiment of this application, if the RTT timer times out and the data corresponding to the RTT timer fails to be received or decoded, the terminal device can start or restart the corresponding retransmission timer so that the terminal device can complete the retransmission within the running time of the retransmission timer. Receive data retransmitted by network devices.

As a possible implementation, the communication method may also include:

The terminal device receives third control information transmitted in a multicast manner, the third control information is used to schedule third data, the third control information and/or the third data are associated with the first RNTI, and the third control information and/or the third data are associated with the first RNTI. Three data are associated with the first HARQ process; or,

The terminal device receives third data on a third resource, the third resource and/or the third data are associated with the first RNTI, and the third data is associated with the first HARQ process;

The terminal device starts or restarts the sixth timer, the sixth timer is the RTT timer corresponding to the DRX associated with the first RNTI, and the sixth timer is associated with the first HARQ process; and/or,

The terminal device starts or restarts a fifth timer. The fifth timer is an RTT timer corresponding to the DRX associated with the unicast. The fifth timer is associated with the first HARQ process.

In the embodiment of the present application, after the terminal device receives the third control information for scheduling the third data transmitted in a multicast manner or receives the third data on the third resource, in order to ensure that the terminal device can subsequently receive the network device For the retransmitted third data, the terminal device can start or restart the corresponding RTT timer. During the running time of the RTT timer, when no other timers are running on the terminal device, the terminal device does not need to monitor the PDCCH, which can reduce the time for the terminal device to monitor the PDCCH, thus reducing the power consumption of the terminal device.

As a possible implementation, the communication method may also include:

The sixth timer times out and the third data reception or decoding fails, the terminal device starts or restarts the second timer; and/or,

When the fifth timer times out and reception or decoding of the third data fails, the terminal device starts or restarts the third timer.

As a possible implementation, the communication method may also include:

The terminal device receives fourth control information transmitted in a unicast manner, the fourth control information is used to schedule fourth data, and the fourth control information and/or the fourth data are associated with the first HARQ process; or,

The terminal device receives fourth data on a fourth resource, the fourth resource is a configuration resource corresponding to unicast, and the fourth data is associated with the first HARQ process;

In the embodiment of the present application, after the terminal device receives the fourth control information for scheduling the fourth data transmitted in unicast mode or receives the fourth data on the fourth resource, in order to ensure that the terminal device can subsequently receive the network device For the retransmitted fourth data, the terminal device can start or restart the corresponding RTT timer. During the running time of the RTT timer, when no other timers are running on the terminal device, the terminal device does not need to monitor the PDCCH, which can reduce the time for the terminal device to monitor the PDCCH, thus reducing the power consumption of the terminal device.

As a possible implementation, the communication method may also include:

When the fifth timer times out and the reception or decoding of the fourth data fails, the terminal device starts or restarts the third timer.

As a possible implementation manner, the first control information transmitted in a multicast manner includes: first control information scrambled by the first RNTI.

As a possible implementation, the first RNTI includes a first group RNTI (G-RNTI) and/or a first A group configured scheduling RNTI (G-CS-RNTI), and/or the second RNTI includes a second G-RNTI and/or a second G-CS-RNTI.

As a possible implementation manner, the first RNTI and/or the second RNTI are used for one or more of the following: for multicast, for scheduling multicast dynamic resources, and for scheduling retransmission resources of multicast dynamic resources. , used to activate multicast configuration resources, used to reactivate multicast configuration resources, used to deactivate multicast configuration resources, and used to schedule retransmission resources of multicast configuration resources.

In the second aspect, the present application discloses a communication method, which can be applied to terminal equipment, can also be applied to modules (for example, chips or processors) in terminal equipment, and can also be applied to terminal equipment that can realize all or part of Functional logic modules or software. The following description takes the execution subject being a terminal device as an example. This communication method may include:

The terminal device receives first control information transmitted in a multicast manner, the first control information is used to schedule first data, the first control information and/or the first data are associated with a first RNTI, and the The first control information and/or the first data are associated with the first HARQ process; or,

receiving first data on a first resource, the first resource and/or the first data being associated with a first RNTI, the first data being associated with a first HARQ process; or,

Receive fifth control information transmitted in a unicast manner, the fifth control information being used to schedule fifth data, the fifth control information and/or the fifth data being associated with the first HARQ process; or ,

Receive fifth data on a fifth resource, the fifth resource being a configuration resource corresponding to unicast, and the fifth data being associated with the first HARQ process;

Do one or more of the following:

Stop a fourth timer, the fourth timer is the RTT timer corresponding to the DRX associated with the second RNTI, the fourth timer is associated with the first HARQ process; and/or

Stop a fifth timer, the fifth timer is an RTT timer corresponding to the DRX associated with unicast, and the fifth timer is associated with the first HARQ process;

Stop a sixth timer, the sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI, and the sixth timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.

In the embodiment of the present application, the terminal device receives the first control information for scheduling the first data transmitted in a multicast manner or after receiving the first data on the first resource, or the terminal device transmits the first control information for scheduling in a unicast manner. The fifth control information of the fifth data or after receiving the fourth data on the fifth resource indicates that the first HARQ process is now used for unicast or multicast corresponding to the first RNTI, and will not be used for the previously used first HARQ process. The multicast data corresponding to the second RNTI, and/or other multicast data corresponding to the first RNTI, and/or unicast data are retransmitted, and the first timer, and/or the second timer, and /or the third timer is run so that the first timer, and/or the second timer, and/or the third timer times out, and the corresponding data reception or decoding fails, the corresponding retransmission timer is started, so that The terminal device may receive retransmissions of multicast data corresponding to the second RNTI of the first HARQ process, and/or other multicast data corresponding to the first RNTI, and/or unicast data. Therefore, if The RTT timers corresponding to these data are still running, and these RTT timers can be stopped. Since the terminal equipment stops these RTT timers, the operation of meaningless timers can be avoided, and unnecessary PDCCH monitoring can be avoided, thereby reducing the power consumption of the terminal equipment.

As a possible implementation, the communication method may also include:

The terminal device receives second control information transmitted in a multicast manner, the second control information is used to schedule second data, and the second control information and/or the second data are associated with the second RNTI, The second control information and/or the second data are associated with the first HARQ process; or,

receiving second data on a second resource, the second resource and/or the second data being associated with the second RNTI, The second data is associated with the first HARQ process;

Start or restart the fourth timer; and/or,

Start or restart the fifth timer.

As a possible implementation, the communication method may also include:

The terminal device receives third control information transmitted in a multicast manner, the third control information is used to schedule third data, and the third control information and/or the third data are associated with the first RNTI, The third control information and/or the third data are associated with the first HARQ process; or,

receiving third data on a third resource, the third resource and/or the third data being associated with the first RNTI, the third data being associated with the first HARQ process;

Start or restart the fifth timer; and/or,

Start or restart the sixth timer.

As a possible implementation, the communication method may also include:

The terminal device receives fourth control information transmitted in a unicast manner, the fourth control information is used to schedule fourth data, and the fourth control information and/or the fourth data are associated with the first HARQ process. ;or,

Receive fourth data on a fourth resource, the fourth resource being a configuration resource corresponding to unicast, and the fourth data being associated with the first HARQ process;

Start or restart the fifth timer.

In the embodiment of the present application, after the terminal device receives the fourth control information for scheduling the fourth data transmitted in unicast mode or receives the fourth data on the fourth resource, in order to ensure that the terminal device can subsequently receive the network device For the retransmitted fourth data, the terminal device can start or restart the corresponding RTT timer. Since it takes a period of time from the terminal device to send a negative response to the network device until the network device is ready to retransmit the fourth data, the terminal device cannot receive the retransmitted fourth data during this period of time. Therefore, the terminal device sends a message to the network device. After the denial, the RTT timer can be restarted or started for the first HARQ. During the running time of the RTT timer, if no other timer is running on the terminal device, the terminal device does not need to monitor the PDCCH, which can reduce the time for the terminal device to monitor the PDCCH. , thus reducing the power consumption of terminal equipment.

As a possible implementation, the first RNTI includes a first G-RNTI and/or a first G-CS-RNTI, and/or the second RNTI includes a second G-RNTI and/or a second G-CS-RNTI.

As a possible implementation manner, the first RNTI and/or the second RNTI are used for one or more of the following: for multicast, for scheduling multicast dynamic resources, and for scheduling multicast dynamic resources. retransmission resources, used to activate multicast configuration resources Source, retransmission resources used to reactivate multicast configuration resources, deactivate multicast configuration resources, and schedule multicast configuration resources.

In a third aspect, the present application discloses a communication device, which can be applied to terminal equipment, can also be applied to modules (for example, chips or processors) in terminal equipment, and can also be applied to realize all or part of terminal equipment. Functional logic modules or software. The communication device may include:

A transceiver unit, configured to receive first control information transmitted in a multicast manner, the first control information being used to schedule first data, the first control information and/or the first data being associated with the first RNTI, the first control information and /or the first data is associated with the first HARQ process; or,

A transceiver unit, configured to receive first data on a first resource, the first resource and/or the first data are associated with the first RNTI, and the first data is associated with the first HARQ process;

A processing unit, configured to stop a first timer, the first timer is a retransmission timer corresponding to the DRX associated with the second RNTI, and the first timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.

As a possible implementation, the processing unit is also used to:

Stop the second timer, the second timer is the retransmission timer corresponding to the DRX associated with the first RNTI, and the second timer is associated with the first HARQ process; and/or

As a possible implementation manner, the transceiver unit is also configured to receive second control information transmitted in a multicast manner, the second control information is used to schedule the second data, and the second control information and/or the second data are related to the second The RNTI is associated, the second control information and/or the second data are associated with the first HARQ process; or,

The transceiver unit is also configured to receive second data on the second resource, the second resource and/or the second data are associated with the second RNTI, and the second data is associated with the first HARQ process;

The processing unit is also configured to start or restart a fourth timer, the fourth timer is an RTT timer corresponding to the DRX associated with the second RNTI, and the fourth timer is associated with the first HARQ process; and/or,

The processing unit is also configured to start or restart a fifth timer. The fifth timer is an RTT timer corresponding to the DRX associated with unicast. The fifth timer is associated with the first HARQ process.

As a possible implementation, the processing unit is also used to:

The fourth timer times out and the second data reception or decoding fails, start or restart the first timer; and/or,

When the fifth timer times out and the reception or decoding of the second data fails, the third timer is started or restarted.

As a possible implementation manner, the transceiver unit is also configured to receive third control information transmitted in a multicast manner, the third control information is used to schedule the third data, and the third control information and/or the third data are consistent with the first RNTI is associated, the third control information and/or the third data is associated with the first HARQ process; or,

The transceiver unit is also configured to receive third data on a third resource, the third resource and/or the third data are associated with the first RNTI, and the third data is associated with the first HARQ process;

The processing unit is also configured to start or restart a sixth timer, the sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI, and the sixth timer is associated with the first HARQ process; and/or,

As a possible implementation, the processing unit is also used to:

The sixth timer times out and the third data reception or decoding fails, start or restart the second timer; and/or,

When the fifth timer times out and reception or decoding of the third data fails, the third timer is started or restarted.

As a possible implementation manner, the transceiver unit is also configured to receive fourth control information transmitted in a unicast manner, the fourth control information is used to schedule fourth data, and the fourth control information and/or the fourth data are consistent with the first HARQ process associated; or,

The transceiver unit is also configured to receive fourth data on a fourth resource, where the fourth resource is a configured resource corresponding to unicast, and the fourth data is associated with the first HARQ process;

As a possible implementation, the processing unit is also configured to start or restart the third timer when the fifth timer times out and the reception or decoding of the fourth data fails.

As a possible implementation, the first RNTI includes the first G-RNTI and/or the first G-CS-RNTI, and/or the second RNTI includes the second G-RNTI and/or the second G-CS-RNTI. RNTI.

In the fourth aspect, the present application discloses a communication device, which can be applied to terminal equipment, can also be applied to modules (for example, chips or processors) in terminal equipment, and can also be applied to realize all or part of the terminal equipment. Functional logic modules or software. The communication device may include:

A transceiver unit, configured to receive first control information transmitted in a multicast manner, the first control information being used to schedule first data, and the first control information and/or the first data being associated with a first RNTI. , the first control information and/or the first data are associated with the first HARQ process; or,

A transceiver unit configured to receive first data on a first resource, the first resource and/or the first data are associated with a first RNTI, and the first data is associated with a first HARQ process; or,

A transceiver unit, configured to receive fifth control information transmitted in a unicast manner, where the fifth control information is used to schedule fifth data, where the fifth control information and/or the fifth data are consistent with the first HARQ process associated; or,

A transceiver unit configured to receive fifth data on a fifth resource, where the fifth resource is a configuration resource corresponding to unicast, and the fifth data is associated with the first HARQ process;

Processing units are used for:

Wherein, the first RNTI and the second RNTI are associated with multicast.

As a possible implementation manner, the transceiver unit is also configured to receive second control information transmitted in a multicast manner, the second control information is used to schedule the second data, the second control information and/or the The second data is associated with the second RNTI, the second control information and/or the second data is associated with the first HARQ process; or,

a transceiver unit, further configured to receive second data on a second resource, the second resource and/or the second data are associated with the second RNTI, and the second data is associated with the first HARQ process Associated;

The processing unit is also used to start or restart the fourth timer; and/or,

The processing unit is also used to start or restart the fifth timer.

As a possible implementation manner, the transceiver unit is also configured to receive third control information transmitted in a multicast manner, the third control information is used to schedule third data, the third control information and/or the Third data is associated with the first RNTI, and the third control information and/or the third data is associated with the first HARQ process; or,

The transceiver unit is further configured to receive third data on a third resource, the third resource and/or the third data are associated with the first RNTI, and the third data is associated with the first HARQ process. Associated;

The processing unit is also used to start or restart the fifth timer; and/or,

The processing unit is also used to start or restart the sixth timer.

As a possible implementation manner, the transceiver unit is also configured to receive fourth control information transmitted in a unicast manner, the fourth control information is used to schedule fourth data, the fourth control information and/or the Fourth data is associated with the first HARQ process; or,

The transceiver unit is further configured to receive fourth data on a fourth resource, where the fourth resource is a configuration resource corresponding to unicast, and the fourth data is associated with the first HARQ process;

The processing unit is also used to start or restart the fifth timer.

As a possible implementation manner, the first RNTI and/or the second RNTI are used for one or more of the following: for multicast, for scheduling multicast dynamic resources, and for scheduling multicast dynamic resources. retransmission resources, retransmission resources for activating multicast configuration resources, reactivating multicast configuration resources, deactivating multicast configuration resources and scheduling multicast configuration resources.

In a fifth aspect, this application discloses a communication device. The communication device may be the terminal device in the above method embodiment, or a chip provided in the terminal device. The communication device includes a processor. The processor is coupled to a memory. The memory is used to store programs or instructions. When the program or instructions are executed by the processor, the communication device causes the communication device to execute the above method embodiment by the terminal device or the chip in the terminal device. or method executed by the processor.

In a sixth aspect, the present application discloses a communication device. The communication device may be the terminal device in the above method embodiment, or a chip provided in the terminal device. The communication device includes a processor and a memory. The memory is used to store programs or instructions. When the program or instructions are executed by the processor, the communication device causes the communication device to execute what is performed by the terminal device, or the chip or processor in the terminal device. method of execution.

In a seventh aspect, the present application discloses a communication device. The communication device may be the terminal device in the above method embodiment, or a chip provided in the terminal device. The communication device includes a communication interface and a processor, and optionally, a memory. Wherein, the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, the communication device is caused to execute the terminal equipment or the terminal equipment in the above method embodiment. The method performed by the chip.

In an eighth aspect, the present application discloses a computer program product. The computer program product includes: computer program code. When the computer program code is run on a processor, the above methods are executed.

In a ninth aspect, the present application discloses a chip system. The chip system includes a processor and is used to implement the functions in each of the above methods. In a possible design, the chip system also includes a memory for storing program instructions and/or data. The chip system may be composed of chips, or may include chips and other discrete devices.

In a tenth aspect, the present application discloses a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is run, the above methods are implemented.

The beneficial effects of the above-mentioned third aspect to the tenth aspect are similar to the beneficial effects of the corresponding methods in the first and second aspects. For detailed description, reference can be made to the beneficial effects of the corresponding methods.

Description of the drawings

Figure 1 is a schematic diagram of a network architecture disclosed in an embodiment of this application;

Figure 2a is a schematic diagram of another network architecture disclosed in the embodiment of the present application;

Figure 2b is a schematic diagram of another network architecture disclosed in the embodiment of the present application;

Figure 3 is a schematic diagram of a DRX cycle provided by an embodiment of the present application;

Figure 4 is a schematic flow chart of a communication method disclosed in the embodiment of the present application;

Figure 5 is a schematic flow chart of another communication method disclosed in the embodiment of the present application;

Figure 6 is a schematic structural diagram of a communication device disclosed in an embodiment of the present application;

Figure 7 is a schematic structural diagram of another communication device disclosed in the embodiment of the present application;

FIG. 8 is a schematic structural diagram of yet another communication device disclosed in an embodiment of the present application.

Detailed ways

The embodiment of the present application discloses a communication method and device for reducing the power consumption of terminal equipment. The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

In the description of this application, unless otherwise stated, "/" means "or". For example, A/B can mean A or B. "And/or" in this article is just an association relationship that describes related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone these three situations. In addition, "at least one" means one or more, and "plurality" means two or more. Words such as "first" and "second" do not limit the quantity and order of execution, and words such as "first" and "second" do not limit the number or order of execution. In this application, the words "exemplary" or "such as" are used to mean examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "exemplary" or "such as" is intended to present the concept in a concrete manner.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (TDD), universal mobile telecommunication system (UMTS), global interoperability for microwave access (WiMAX) communication system, fifth generation (5th generation, 5G) system or new radio (NR) and future communication systems are not limited here.

The communication method in the embodiment of the present application can be applied to next generation radio access networks (NG-RAN) systems, LTE systems, and sixth generation (NG-RAN) systems that may appear in the future. Systems such as 6th generation (6G) and 7th generation (7G) can also be applied to the centralized unit (CU)-distributed unit (DU) architecture, which is not limited by the embodiments of this application. .

Terminal equipment: A terminal equipment is a device with wireless transceiver functions, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device (such as a communication module) built into the above-mentioned equipment. , modem, or chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, including but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), car-to-everything (vehicle to everything, V2X), machine-to-machine/machine-type communications (M2M/MTC), Internet of things (IoT), virtual reality (VR) , augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wear, smart transportation , terminal equipment for smart cities, drones, robots and other scenarios. The terminal equipment may sometimes be called user equipment (UE), terminal, access station, UE station, remote station, wireless communication equipment, or user device, etc.

Network equipment: For example, it includes access network equipment and/or core network equipment. The access network device is a device with a wireless transceiver function and is used to communicate with the terminal device. The access network equipment includes but is not limited to the base station (BTS, Node B, eNodeB/eNB, or gNodeB/gNB), transceiver point (transmission reception point, TRP), third generation partner program (3rd generation partner plan) in the above communication system. generation partnership project, 3GPP) subsequent evolution of base stations, access nodes, wireless relay nodes, wireless backhaul nodes, etc. in wireless communication (wireless fidelity, WiFi) systems. The base station may be: a macro base station, a micro base station, a pico base station, a small station, a relay station, etc. Multiple base stations may support the network of the same access technology mentioned above, or may support the network of different access technologies mentioned above. A base station may contain one or more co-located or non-co-located transmission and reception points. The network device can also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. Network devices can also be servers, wearable devices, or vehicle-mounted devices, etc. For example, the network equipment in V2X technology can be a road side unit (RSU). The following description takes the access network equipment as a base station as an example. The multiple network devices in the communication system may be base stations of the same type or different types of base stations. The base station can communicate with the terminal device or communicate with the terminal device through the relay station. Terminal devices can communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of devices that implement core network functions in systems with different access technologies may be different, and this application does not limit this. Taking the 5G system as an example, the core network equipment includes: access and mobility management function (AMF), session management function (SMF), or user plane function (UPF) wait.

In this embodiment of the present application, the terminal device or network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. This hardware layer includes hardware such as central processing unit (CPU), memory management unit (MMU) and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system or windows operating system, etc. This application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Moreover, the embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as it can be recorded through the operation of the present application. The code program of the method provided by the embodiment of the present application can communicate according to the method provided by the embodiment of the present application. For example, the execution subject of the method provided by the embodiment of the present application may be a terminal device or a network device, or a terminal A functional module in a device or network device that can call a program and execute it.

Additionally, various aspects or features of the present application may be implemented as methods, apparatus, or articles of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, tapes, etc.), optical disks (e.g., compact discs (CD), digital versatile discs (DVD)) etc.), smart cards and flash memory devices (e.g. erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.

The terms "system" and "network" in the embodiments of this application may be used interchangeably.

The technical solution of the present application will be described in further detail below with reference to the accompanying drawings.

Figure 1 is a schematic diagram of a network architecture disclosed in an embodiment of this application. As shown in FIG. 1 , the terminal device 130 can access the wireless network to obtain services of an external network (such as the Internet) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices. The wireless network includes a radio access network (RAN) device 110 and a core network (CN) device 120. The RAN device 110 is used to connect the terminal device 130 to the wireless network, and the CN device 120 is used to connect the terminal device 130 to the wireless network. Manage terminal equipment and provide a gateway for communication with the external network. It should be understood that the number of each device in the communication system shown in Figure 1 is only for illustration, and the embodiments of the present application are not limited thereto. In actual applications, the communication system may also include more terminal devices 130 and more RAN devices. 110, which may also include other devices.

Figure 2a is a schematic diagram of another network architecture disclosed in the embodiment of this application. As shown in Figure 2a, the network architecture may include CN equipment, RAN equipment and terminal equipment. Among them, RAN equipment includes a baseband device and a radio frequency device. The baseband device can be implemented by one node or multiple nodes. The radio frequency device can be implemented independently from the baseband device, or it can be integrated in the baseband device, or have some functions. Independently integrated, some functions are integrated in the baseband device. For example, in the LTE communication system, the RAN equipment (eNB) includes a baseband device and a radio frequency device. The radio frequency device can be arranged remotely relative to the baseband device. For example, the radio frequency remote unit (remote radio unit, RRU) is relative to the indoor baseband processing unit. A remote wireless unit arranged in a building base unit (BBU).

Communication between RAN equipment and terminal equipment follows a certain protocol layer structure. For example, the control plane protocol layer structure can include a radio resource control (RRC) layer and a packet data convergence protocol (PDCP) layer. , wireless link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical layer and other protocol layer functions; the user plane protocol layer structure can include PDCP layer, RLC layer, MAC layer and physical layer and other protocol layer functions; in a possible implementation, the PDCP layer can also include a service data adaptation protocol (SDAP) layer.

RAN equipment can have one node implement the functions of protocol layers such as RRC, PDCP, RLC, and MAC, or multiple nodes can implement the functions of these protocol layers. For example, in an evolved structure, RAN equipment may include CUs and DUs, and multiple DUs may be centrally controlled by one CU. As shown in Figure 2a, CU and DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and above are set in the CU, and the functions of the protocol layers below PDCP, such as the RLC layer and MAC layer, are set in the DU.

This division of protocol layers is just an example. It can also be divided in other protocol layers. For example, in the RLC layer, the functions of the RLC layer and above are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, divide it in a certain protocol layer, for example, set some functions of the RLC layer and functions of the protocol layer above the RLC layer in the CU, and The remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. In addition, it can also be divided in other ways, such as by delay, and the functions whose processing time needs to meet the delay requirement are set in DU, and the functions that do not need to meet the delay requirement are set in CU.

In addition, the radio frequency device can be integrated independently, not placed in the DU, or it can be integrated in the DU, or partially remote and partially integrated in the DU, without any restrictions here.

Figure 2b is a schematic diagram of another network architecture disclosed in the embodiment of the present application. Compared with the network architecture shown in Figure 2a, in Figure 2b, the control plane (CP) and user plane (UP) of the CU can also be separated and implemented into different entities, namely CP and CU entities (i.e. CU-CP entity) and UP CU entity (that is, CU-UP entity).

In the above network architecture, the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the terminal device or CU without parsing the signaling. In the following embodiments, if the transmission of such signaling between the DU and the terminal device is involved, at this time, the sending or receiving of signaling by the DU includes such a scenario. For example, RRC or PDCP layer signaling will eventually be processed into PHY layer signaling and sent to the terminal device, or it will be converted from received physical (physical, PHY) layer signaling. Under this architecture, the RRC or PDCP layer signaling can also be considered to be sent by DU, or sent by DU and radio frequency loading.

The network architecture illustrated in Figure 1, Figure 2a or Figure 2b above can be applied to various radio access technology (RAT) communication systems, such as LTE communication systems or 5G (also known as The new wireless (new radio, NR) communication system can also be a transition system between the LTE communication system and the 5G communication system. The transition system can also be called a 4.5G communication system, and of course it can also be a future communication system. The network architecture and business scenarios described in the embodiments of this application are to more clearly explain the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the communication With the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. For example, the present invention can be applied to broadcast multicast scenarios.

The devices in the following embodiments of this application may be located in terminal equipment or network equipment according to the functions they implement. When the above CU-DU structure is adopted, the network device may be a CU node, a DU node, or a RAN device including a CU node and a DU node.

To facilitate understanding, some descriptions of concepts related to the embodiments of the present application are exemplarily provided for reference. As follows:

1. MBS:

The broadcast multicast service mentioned in the embodiment of this application may be MBS under the NR system. MBS is introduced by 3GPP to effectively utilize mobile communication network resources. It provides a data source in the mobile communication network to send data to multiple users for point-to-multipoint services, realizing network resource sharing and improving resource utilization, especially the air interface. Interface resources. NR MBS supports multicast and broadcast.

MBS transmission method: For the transmission of MBS services/data, there can be any one or more of the following transmission methods: dynamic transmission method and/or configuration transmission method.

Among them, the dynamic transmission method includes point-to-point (PTP) transmission method and/or point-to-multipoint (point-to-multipoint, PTM) transmission method.

PTP transmission method: Through this transmission method, the sender sends a copy of data to a receiver. The PTP transmission method can be understood as: (network equipment) PDCCH/downlink control information (downlink control information) scrambled with UE-specific RNTI (for example, cell-RNTI, C-RNTI), third RNTI , DCI) (for terminal equipment) scheduled data or UE-specific RNTI (e.g., C-RNTI, third RNTI) scrambling physical downlink shared channel (PDSCH)/data. The PTP transmission method can also be called the C+C transmission method.

In this application, DCI can be replaced by PDCCH, and PDCCH can be replaced by DCI.

In this application, RNTI scrambled PDCCH/DCI/control information can be understood as: RNTI scrambled PDCCH/DCI/control information cyclic redundancy check (cyclic redundancy check, CRC), or, PDCCH/DCI/control information The CRC is scrambled by RNTI.

PTM transmission method: Through PTM transmission method, the sender can send one piece of data to multiple receivers.

The PTM transmission method can be understood as: (network equipment) PDCCH/DCI (for terminal equipment) scrambled with a common RNTI (for example, G-RNTI, G-CS-RNTI) scheduling data or a common RNTI (for example, G-CS-RNTI) RNTI, G-CS-RNTI) scrambled PDSCH/data. Or it can be understood that the network side scrambles a DCI through a common RNTI, and the DCI is used to schedule a data scrambled through a common RNTI. In this case, multiple terminal devices receive the same DCI, and these multiple The data received by each terminal device is the same.

The PTM transmission method can also be called the G+G transmission method.

For example, PDSCH can also be understood as data.

The configuration transmission mode (or multicast configuration transmission mode) can be understood as: (network device) transmits data/multicast data (to the terminal device) on the configuration resource/multicast configuration resource; or (terminal device) in the configuration Resource/Multicast configuration resource receives data/multicast data (sent by network devices).

The configuration transmission method can also be called semi-static transmission method.

Configuration resources/multicast configuration resources can also be called semi-persistent scheduling (SPS) resources/multicast semi-persistent scheduling resources.

2. Multicast and unicast:

Multicast may include any one or more of the following: broadcast in MBMS or MBS; multicast in MBMS or MBS; multicast in MBMS or MBS; multicast in V2X; multicast in V2X; multicast in V2X Broadcast; multicast or multicast; groupcast; broadcast.

The multicast service may include/replace with any one or more of the following: broadcast service, multicast service, MBS service, MBS broadcast service, MBS multicast service, V2X multicast service, and V2X broadcast service.

The data corresponding to the multicast service can be called multicast data.

Unicast can include any one or more of the following: unicast in V2X; unicast. Optionally, unicast can be understood as unicast transmission.

"Multicast" in the embodiment of this application can also be replaced by nouns such as "multicast", and correspondingly, multicast service can also be replaced by multicast service.

Multicast can provide the same service and/or the same content data to a group/multiple terminal devices at the same time.

Multicast can be targeted at a specific group of terminal devices, and the terminal devices may need to undergo a "group joining process."

Correspondingly, unicast can be understood as providing the same service and/or the same content data to a terminal device at the same time. Unicast can be understood as: for a piece of data to be sent to multiple devices, the data needs to be sent to each device separately.

3. DRX:

In wireless communication systems, in order to further save the power consumption of terminal equipment while ensuring effective data transmission, a DRX function is introduced to control the behavior of terminal equipment in monitoring the physical downlink control channel PDDCH. When the network device configures the DRX function for the terminal device, the terminal device can be allowed to enter the sleep state at certain times, so that the terminal device does not need to continuously monitor the physical downlink control channel PDCCH. When it is necessary to monitor the PDCCH, the terminal device can Waking up from the sleep state can save the power consumption of the terminal device to a certain extent.

The following will briefly introduce DRX in conjunction with Figure 3: Figure 3 is a schematic diagram of a DRX cycle provided by an embodiment of the present application. As shown in Figure 3, a DRX cycle (DRX cycle) can include a duration (for example, on-duration) or wake-up time (for example, on-duration) and a sleep time (for example, opportunity for DRX). During the duration period, after the terminal device wakes up, it waits for the duration of receiving the PDCCH. During this period, the terminal device monitors the PDCCH. If the terminal device can successfully decode the PDCCH, the terminal device can remain in the awake state, or extend the activation time. During the sleep period, it is the sleep time of the terminal device. During this period, the terminal device does not need to monitor the PDCCH to save power consumption. It is understandable that the longer the sleep time of the terminal device, the lower the power consumption of the terminal device, but correspondingly, the delay of service transmission by the terminal device will increase.

The DRX function of the terminal device can be configured by the network device. It should be understood that even if the network device configures the DRX function for the terminal device, the terminal device can still monitor the PDCCH according to the requirements of other MAC layer processes, that is, when other MAC layer processes require the terminal device to keep monitoring the PDCCH, regardless of the DRX status at this time , the terminal equipment needs to continuously monitor the PDCCH.

(1) Unicast DRX:

In the absence of a DRX group (DRX group) configured (or in R15), the DRX parameters are configured by the network device for the MAC entity of each terminal device or for each terminal device, that is, the MAC entity of a terminal device Use a set of DRX parameters.

In the scenario of carrier aggregation (CA), the terminal equipment uses the same set of DRX parameters for all activated cells and runs a set of DRX.

In the scenario of multi-radio dual connectivity (MR-DC), the master node (MN) and the secondary node (SN) respectively correspond to the MAC entity of a terminal device. Therefore, the terminal device There are two independent sets of DRX parameters for MN and SN, and two sets of DRX are run. That is to say, the terminal device uses a set of DRX parameters and runs a set of DRX for all activated service cells in the master cell group (MCG); for all activated services in the secondary cell group (SCG) The cell uses another set of DRX parameters and runs the other set of DRX.

When no DRX group is configured, the activation time of DRX can include any one or more of the following: the running time of drx-onDurationTimer; the running time of drx-InactivityTimer; the running time of drx-RetransmissionTimerDL; the running time of drx-RetransmissionTimerUL ; The running time of drx-RetransmissionTimerSL; a scheduling request (SR) was sent on the physical uplink control channel (PUCCH), and the SR is waiting for processing; the non-contention random access process successfully received a random access After the random access response (RAR) is received (that is, after the non-contention random access (RA) is successful), the newly transmitted PDCCH with C-RNTI scrambled instructions has not been received, and so on.

Network devices configure one or more of the following parameters through RRC messages to control DRX operations:

drx-onDurationTimer: a period of time at the beginning of the DRX cycle; where the starting position of drx-onDurationTimer can be calculated based on the base station configuration parameters and the formula specified in the protocol.

drx-InactivityTimer: Indicates a period of time after the PDCCH opportunity (occasion) of the uplink or downlink new transmission schedule. For example, the terminal equipment receives the PDCCH, indicating that there is a new uplink or downlink transmission (ie, new transmission schedule), and starts or restarts the drx-InactivityTimer.

drx-RetransmissionTimerDL: The maximum length of time until a downlink (DL) retransmission is received. For example, drx-HARQ-RTT-TimerUL times out and the data is not successfully decoded, start drx-RetransmissionTimerDL.

drx-RetransmissionTimerUL: Maximum time until a grant for uplink (UL) retransmission is received. For example, in the first symbol after the drx-HARQ-RTT-TimerUL timeout, start the corresponding HARQ process drx-RetransmissionTimerUL.

drx-HARQ-RTT-TimerDL: The minimum length of time before the DL allocation of HARQ retransmissions that the MAC entity expects or the minimum length of time before the DL allocation of HARQ retransmissions that the MAC entity expects to receive. For example, the terminal device receives PDCCH, indicating that there is downlink transmission, or the terminal device receives data in the configured downlink allocation and starts or restarts drx-HARQ-RTT-TimerDL.

drx-HARQ-RTT-TimerUL: The minimum length of time before the MAC entity expects a UL HARQ retransmission grant or the minimum length of time before the MAC entity expects to receive a UL HARQ retransmission grant. For example, the terminal device sends a MAC protocol data unit (PDU) in the configured uplink authorization, or the terminal device receives PDCCH, indicating UL transmission; start or restart drx-HARQ-RTT-TimerUL.

drx-RetransmissionTimerSL: Maximum time until a grant for sidelink (SL) retransmission is received.

drx-HARQ-RTT-TimerSL: The minimum length of time before an SL retransmission grant is expected or the minimum length of time before an SL retransmission grant is expected to be received.

Compared with R15, in the R16 standard protocol, unicast DRX adds the function of DRX group.

The following will briefly introduce the DRX group.

DRX group: Within a MAC entity, different DRX groups are distinguished for different frequency ranges, or in other words, DRX groups are distinguished for frequency range (frequency range, FR)1 and FR2. That is, for cells on FR2, the concept of secondary DRX group is introduced.

There are a set of drx-onDurationTimer and drx-InactivityTimer parameters for FR1 and FR2 cells/DRX groups respectively, and other DRX parameters are common.

Each DRX group runs a set of DRX, that is, within a MAC entity, there can be two DRX groups running two DRXs.

When configuring a DRX group, the activation time of a DRX group can include any one or more of the following: the running time of the drx-onDurationTimer of the DRX group; the running time of the drx-InactivityTimer of the DRX group; the corresponding The running time of drx-RetransmissionTimerDL (or any cell in the DRX group); the running time of drx-RetransmissionTimerUL corresponding to the DRX group (or any cell in the DRX group); the running time of the DRX group corresponding The running time of drx-RetransmissionTimerSL (or any cell in the DRX group); the running time of drx-RetransmissionTimer-DL-PTM corresponding to the multicast corresponding to the DRX group; the SR is sent on the PUCCH, and the SR Waiting for processing; after the non-contention random access process successfully receives the RAR (that is, after the non-contention RA is successful), the newly transmitted PDCCH scrambled with the C-RNTI has not been received, and so on.

(2) Multicast DRX:

Multicast DRX and unicast DRX are independent. Multicast DRX parameters can be per (per) G-RNTI and/or G-CS-RNTI, and per G-RNTI and/or G-CS- RNTI runs multicast DRX.

The activation time (activity time) of each multicast DRX may include any one or more of the following: the running time of drx-onDurationTimerPTM or the running time of drx-InactivityTimerPTM or drx- RetransmissionTimerDL-PTM running time.

The multicast DRX function can be described as follows:

Network devices configure one or more of the following parameters through RRC messages to control multicast DRX operations:

drx-onDurationTimerPTM: a period of time at the beginning of the DRX cycle. The starting position of drx-onDurationTimerPTM is calculated based on the parameters configured by the base station and the formula specified by the protocol.

drx-InactivityTimerPTM: Indicates a period of time after the PDCCH opportunity for DL new transmission scheduling. For example, the terminal equipment receives the PDCCH, indicating that there is a new uplink or downlink transmission (i.e., new transmission scheduling), and starts or restarts drx-InactivityTimerPTM.

drx-RetransmissionTimerDL-PTM: Maximum time until DL retransmission is received. For example, drx-HARQ-RTT-TimerDL-PTM times out and the data is not successfully decoded. Start or restart drx-RetransmissionTimerDL-PTM.

drx-HARQ-RTT-TimerDL-PTM: The minimum length of time before a DL retransmission is expected or the minimum length of time before a DL retransmission is expected to be received. For example, the terminal device receives PDCCH, indicating that there is downlink transmission, or the terminal device receives data in the configured downlink allocation and starts or restarts drx-HARQ-RTT-TimerDL-PTM.

It should be noted that for DRX-related content, please refer to 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification", which will not be repeated here.

It should be noted that any one or more of drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL-PTM, drx-RetransmissionTimerDL-PTM is for each HARQ process. It can be understood that, for example, the terminal device maintains different drx-HARQ-RTT-TimerDL for different HARQ processes. For example, the terminal device maintains different drx-RetransmissionTimerUL for different HARQ processes. For example, the terminal device maintains different drx-HARQ-RTT-TimerDL-PTM for different HARQ processes. For example, the terminal device maintains different drx-RetransmissionTimerDL-PTM for different HARQ processes.

It should be noted that any one or more of drx-HARQ-RTT-TimerDL-PTM and drx-RetransmissionTimerDL-PTM is for each G-RNTI and/or G-CS-RNTI, or for each multicast /Multicast service. It can be understood that, for example, the terminal equipment maintains different drx-HARQ-RTT-TimerDL-PTM for different G-RNTI and/or G-CS-RNTI, or for different multicast/multicast services. . For example, the terminal equipment maintains different drx-RetransmissionTimerDL-PTM for different G-RNTI and/or G-CS-RNTI, or for different multicast/multicast services.

4. HARQ:

HARQ processes can be shared between unicast and multicast. For example, a HARQ process may be used for multicast at the first time and unicast at the second time; or in other words, a HARQ process may be associated with multicast at the first time and be used for unicast at the second time. Time and unicast association.

The HARQ process can be shared between multicast 1 and multicast 2. For example, a HARQ process may be used for multicast 2 for a while/first time, and for multicast 1 for a while/second time; or in other words, a HARQ process may be associated with multicast 2 for a while/first time, and then be used for multicast 1 for a while/second time. /Associated with multicast 1 at the second time.

HARQ processes can be shared between unicast and different multicasts. For example, a HARQ process may be used for multicast 2 for a while/first time, multicast 1 for a while/second time, and unicast for a while/third time; or in other words, a HARQ process may be used for multicast 2 for a while/second time. The first time is associated with multicast 2, the first/second time is associated with multicast 1, and the first/third time is associated with unicast.

In this application, multicast mode may also include/replace with multicast mode or broadcast mode. This application takes the multicast method as an example for explanation.

It should be noted that the embodiment of the present application takes a terminal device as an example for description. The terminal device may also be replaced by the MAC entity of the terminal device or other things, which is not limited by this application.

In the embodiment of this application, related can be understood as: corresponding.

In this application, the first multicast can be understood as the first multicast service. The second multicast can be understood as the second multicast service.

In this embodiment of the present application, the first HARQ process may include/understand as/replace with: a first HARQ process identity (ID).

In the embodiment of the present application, for example, receiving can be understood as: receiving, and/or, after/when receiving.

The length of time to wait before instructing the terminal device to receive a retransmission (e.g., data/DCI) may include/understood as any one or more of the following: Used to instruct the terminal device to receive/receive a retransmission (e.g., data/DCI) The length of time (e.g., minimum length) to wait before (e.g., DL data) is used to indicate that the terminal device expects to receive/receive the length of time (e.g., minimum time) to wait before retransmitting (e.g., data/DCI) (e.g., DL data) duration).

The duration used to indicate that the terminal device receives a retransmission (eg, data/DCI) may include/be understood as: used to indicate that the terminal device receives/receives a retransmission (eg, data/DCI) (eg, DL data or SL data) duration (e.g., maximum duration).

The question leads to:

Since the HARQ process is shared between unicast and multicast (including different multicasts), for a HARQ process, the terminal device may maintain a drx-HARQ-RTT-TimerDL, and/or, one or more drx-HARQ- RTT-TimerDL-PTM (eg, for different multicasts, or for different G-RNTI and/or G-CS-RNTI).

Since the HARQ process is shared between unicast and multicast (including different multicasts), for a HARQ process, the terminal device may maintain a drx-RetransmissionTimerUL, and/or, one or more drx-RetransmissionTimerDL-PTM (for example, For different multicasts, or for different G-RNTI and/or G-CS-RNTI).

And the duration of different timers may be the same or different.

Question 1: For a HARQ process, the UE receives the PTM transmission or configuration transmission of multicast 2. At this time, for the HARQ process, the DRX retransmission timer of multicast 1 may be running, because the UE has received When it comes to the transmission of multicast 2 for this HARQ process, the UE will no longer receive retransmissions for multicast 1 for this HARQ process. It is meaningless for the DRX retransmission timer of multicast 1 to continue to run, and will This causes the UE to consume power.

For example, for a HARQ process, after the UE receives the PTM transmission or configuration transmission of multicast 1, in order to receive the retransmission, it starts the retransmission timer of multicast 1's DRX (for example, it can be: first start the retransmission timer of multicast 1 The RTT timer of DRX will start the retransmission timer of DRX of multicast 1 after timeout, which is not limited by this application). Later, the UE receives the PTM transmission or configuration transmission of multicast 2 of the same HARQ process. At this time, If the retransmission timer of multicast 1's DRX continues to run, power will be consumed.

Question 2: For a HARQ process, the UE receives the PTM transmission or configuration transmission of multicast 2, or the UE receives a unicast transmission (for example, DCI or data). At this time, for the HARQ process, the UE receives the PTM transmission or configuration transmission of multicast 1. One or more of the RTT timer of DRX, the RTT timer of multicast 2 DRX, and the RTT timer of unicast DRX may be running. If the RTT timer of multicast 1 DRX, the RTT timer of multicast 2 DRX One or more of the RTT timer and the unicast DRX RTT timer continue to run. After timeout, the corresponding retransmission timer may be started because the UE has received the multicast 2 transmission for the HARQ process. (e.g., new transmission or retransmission) or unicast transmission (e.g., new transmission or retransmission), the UE will no longer receive retransmissions of multicast 1 for this HARQ process, or in other words, the UE does not need to receive any more For the multicast 1 retransmission or multicast 2 retransmission or unicast retransmission of the HARQ process, the RTT timer of the DRX of multicast 1, the RTT timer of the DRX of multicast 2, and the DRX of unicast The continued running of one or more of the RTT timers and/or the running of the corresponding retransmission timer that may be started after its expiration is meaningless and will cause the UE to consume power.

For example, for a HARQ process, after receiving the PTM transmission or configuration transmission of multicast 1, the UE starts the RTT timer of multicast 1's DRX and the unicast RTT timer. / or unicast RTT timer) before the UE receives the PTM transmission or configuration transmission or unicast transmission of multicast 2 of the same HARQ process. In this case, if the RTT timer of multicast 1 (or unicast RTT timer ) times out, the data of the HARQ process process (for example, the data previously received for the HARQ process or the data for the HARQ process is now received The received data) is not decoded successfully, and the UE will start the multicast 1 retransmission timer (or unicast retransmission timer), which will cause the UE to consume power.

Below, the method provided by this application is described. It should be understood that in the method embodiments described below, it is only taken as an example that the execution subject is a network device and/or a terminal device, but it is not limited to a network device and/or a terminal device, and the network device and/or a terminal device can be replaced. It is a device that can implement the method in the application, or a chip, chip system, processor, logic module or software that supports the device to implement the method. For example, the network device can also be replaced by a chip configured in the network device, and the terminal device can also be replaced by a chip configured in the terminal device.

In response to the technical problem in question 1 above, in order to reduce the power consumption of the terminal device, this application proposes a communication method. As shown in Figure 4, the communication method may include the following steps.

401. The terminal device receives the first control information transmitted in a multicast manner, or the terminal device receives the first data on the first resource. For example, correspondingly, the network device sends the first control information transmitted in a multicast manner, or the network device sends the first data on the first resource.

The first control information is used to schedule the first data or the first data transmitted in a multicast manner. For example, the first control information may be DCI or other control information transmitted through the PDCCH.

For example, the first control information and/or the first data are associated with the first RNTI.

For example, the first control information and/or the first data are associated with the first HARQ process.

For example, the first resource and/or the first data are associated with the first RNTI.

For example, the first data is associated with the first HARQ process.

In this application, the control information and/or data associated with the HARQ process may include: the control information includes the HARQ process ID.

The first control information transmitted in a multicast manner may include/be understood as: first control information scrambled by the first RNTI, or first control information associated with the first RNTI.

For example, "the first control information is associated with the first RNTI" or "the first control information is associated with the first RNTI" can be understood as: the first RNTI scrambled with the first control information, or the CRC of the first control information Scrambled by the first RNTI (e.g., PDCCH/DCI/Control Information with CRC scrambled by the first RNTI).

For example, the association of the first data with the first RNTI can be understood as: the first RNTI scrambles the first data.

The first data transmitted in a multicast manner may include/understood as: first data scrambled by the first RNTI, or first data associated with the first RNTI.

For example, the first RNTI is associated with the first multicast.

For example, the first data may be multicast data.

It can be understood that the first control information is control information used for scheduling multicast service data, and the first data is multicast service data.

For example, the first resource is/includes a resource/configuration resource associated with the multicast/first multicast.

The first resource is/includes resources/configuration resources associated with multicast/first multicast, which can be understood as: the first resource is within the public frequency resource corresponding to multicast, or the first resource is associated with multicast/first multicast. SPS resources corresponding to multicast.

The SPS resources corresponding to multicast/first multicast can be understood as public SPS resources (for example, PDSCH resources) corresponding to multicast/first multicast. It can be understood that any terminal device that receives the multicast/first multicast can receive data on the SPS resource corresponding to the multicast/first multicast.

Exemplarily, the terminal device can send messages through broadcast messages (for example, system information, MBS Control Channel (MBS Control Channel, MCCH) messages), RRC messages (for example, dedicated RRC messages), MAC messages (for example, MAC control messages (control element, CE)), physical layer messages (e.g., DCI), any One or more items of obtaining SPS resources/configuration of SPS resources and/or obtaining SPS resources/configuration of SPS resources corresponding to the multicast/first multicast.

For example, after the terminal device obtains the configuration of the SPS, it may need to be activated (for example, through physical layer message/DCI activation) to use the resource to receive data; it may also be able to directly use the resource to receive data (that is, no activation is required).

The public frequency resources corresponding to multicast can be understood as: the bandwidth part (BWP) corresponding to multicast, or the frequency range corresponding to multicast.

For example, the first resource may be a PDSCH resource.

The SPS resources corresponding to multicast can be replaced/understood as MBSSPS resources.

The first RNTI can be used for any one or more of the following: for multicast, for scheduling dynamic resources/multicast dynamic resources, for scheduling dynamic resources/retransmission resources of multicast dynamic resources, and for activating configuration Resources/multicast configuration resources, resources for reactivation of configuration resources/multicast configuration resources, resources for deactivation of configuration resources/multicast configuration resources, or retransmission resources for scheduling configuration resources/multicast configuration resources.

For example, the first RNTI may be used for activation/reactivation/deactivation of the first resource.

For example, the first RNTI may be used to schedule retransmission resources of the first resource.

For example, the first RNTI may include/be: the first G-RNTI and/or the first G-CS-RNTI.

For example, the first RNTI/first multicast is associated with the first multicast DRX. For example, the first multicast DRX is used to control monitoring/reception of the first RNTI/first multicast-related control information. It should be noted that the first multicast DRX can also be used to control the monitoring/reception of other control information, which is not limited by this application.

For example, the first multicast-related control information may include/be understood as: the (or scrambled) control information associated with the first G-RNTI and/or the first G-CS-RNTI, and/or the unicast RNTI. (e.g., C-RNTI and/or CS-RNTI) scrambled control information.

Exemplarily, the activation time of multicast DRX may include any one or more of the following: duration timer (for example, drx-onDurationTimerPTM) corresponding to multicast (for example, G-RNTI and/or G-CS-RNTI) The running time; the running time of the inactivation timer (for example, drx-InactivityTimerPTM) corresponding to multicast (for example, G-RNTI and/or G-CS-RNTI); or, the multicast (for example, G-RNTI and/or G-RNTI and/or or G-CS-RNTI) corresponding retransmission timer (for example, drx-RetransmissionTimerDL-PTM) running time.

It can be understood that within the activation time of the multicast DRX (for example, the first multicast DRX), the terminal device monitors control information related to the multicast (for example, the first RNTI/first multicast).

For example, the duration timer/duration timer corresponding to multicast is used to indicate the duration of waiting for the terminal device to receive control information (eg, DCI) after waking up.

For example, the inactivation timer/inactivation timer corresponding to multicast is used to indicate a period of time used to schedule newly transmitted control information or newly transmitted data.

For example, the retransmission timer/retransmission timer corresponding to multicast is used to indicate the length of time for the terminal device to receive retransmission (for example, retransmission of DCI, retransmission of data, retransmission of resources).

Optionally, the terminal device receiving the first control information transmitted in a multicast manner may include: the terminal device receiving the first control information and the first data transmitted in a multicast manner.

Optionally, after the terminal device receives the first control information transmitted in a multicast manner, or after the terminal device receives the first data on the first resource, the terminal device may start the corresponding fifth timer and/or the sixth timer. timer.

402. The terminal device performs any one or more of the following steps 402-1, 402-2, and 402-3:

402-1. The terminal device stops the first timer.

For example, after the terminal device receives the first control information or after receiving the first data on the first resource, the terminal device may To first determine if there is a running first timer. In case there is a running first timer, the first timer may be stopped.

For example, the first timer is associated with the second multicast DRX.

For example, the second RNTI/second multicast is associated with the second multicast DRX. For example, the second multicast DRX is used to control monitoring/reception of the second RNTI/second multicast-related control information. It should be noted that the second multicast DRX can also be used to control the monitoring/reception of other control information, which is not limited by this application.

For example, the second multicast-related control information may include/be understood as: second G-RNTI and/or second G-CS-RNTI associated (or scrambled) control information, and/or unicast RNTI (e.g., C-RNTI and/or CS-RNTI) scrambled control information.

For example, the first timer is a retransmission timer corresponding to multicast (for example, drx-RetransmissionTimerDL-PTM).

For example, the first timer is a retransmission timer corresponding to the DRX associated with the second RNTI or a retransmission timer corresponding to the second multicast DRX.

For example, the first timer is associated with the first HARQ process.

That is, it can be understood that the first timer is associated with another multicast, and this multicast is associated with the second RNTI. That is, the first timer is a retransmission timer corresponding to the DRX associated with the multicast corresponding to the second RNTI.

The second RNTI can be used for any one or more of the following: for multicast, for scheduling dynamic resources/multicast dynamic resources, for scheduling dynamic resources/retransmission resources of multicast dynamic resources, and for activating configuration Resources/multicast configuration resources, resources for reactivation of configuration resources/multicast configuration resources, resources for deactivation of configuration resources/multicast configuration resources, or retransmission resources for scheduling configuration resources/multicast configuration resources.

For example, the second RNTI may include/be: a second G-RNTI and/or a second G-CS-RNTI.

It can be understood that the first RNTI is different from the second RNTI, and the multicast corresponding to the first RNTI is different from the multicast corresponding to the second RNTI. The first data and the second data may be different.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Data 1 is received on the MBS SPS resource (e.g., associated with the first HARQ process), and the first timer associated with the second G-RNTI/second G-CS-RNTI (e.g., associated with the first HARQ process) The retransmission timer) may be running, and the end device may stop the first timer. It can be understood that the first timer is run so that the terminal device can receive retransmission (for example, retransmission of DCI and/or data 2) (for example, associated with the second G-RNTI/second G-CS-RNTI). or retransmitting data), but in this case, since the first HARQ process has been used for data 1, the terminal device will no longer receive retransmission of data 2. Therefore, in this case, it is meaningless if the first timer continues to run, and will cause the terminal device to consume power. In order to avoid the meaningless running of the first timer, the first timer can be stopped, and then the first timer can be stopped. Reduce the power consumption of terminal equipment.

402-2 (not shown in the figure). The terminal device stops the second timer.

Exemplarily, the second timer is associated with the first multicast DRX.

For example, the second timer is a retransmission timer corresponding to multicast (for example, drx-RetransmissionTimerDL-PTM).

For example, the second timer is a retransmission timer corresponding to the DRX associated with the first RNTI or a retransmission timer corresponding to the first multicast DRX.

For example, the retransmission timer/retransmission timer duration may be used to indicate how long the terminal device receives retransmissions (eg, data/DCI).

For example, the second timer is associated with the first HARQ process.

For example, after receiving the first control information or after receiving the first data on the first resource, the terminal device may first determine whether there is a running second timer. In the presence of a running second timer, it is possible to stop Stop the second timer.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Data 1 is received on the MBS SPS resource (e.g., associated with the first HARQ process), and the second timer associated with the first G-RNTI/first G-CS-RNTI (e.g., associated with the first HARQ process retransmission timer) may be running and the end device may stop the second timer. It can be understood that the second timer is run so that the terminal device can receive retransmission (for example, retransmission of DCI and/or DCI) of data 2 (for example, associated with the first G-RNTI/first G-CS-RNTI). or retransmitting data), but in this case, since the first HARQ process has been used for data 1, the terminal device will no longer receive retransmission of data 2. Therefore, in this case, it is meaningless if the second timer continues to run, and will cause the terminal device to consume power. In order to avoid the meaningless running of the second timer, the second timer can be stopped, and then the second timer can be stopped. Reduce the power consumption of terminal equipment.

402-3 (not shown in the figure). The terminal device stops the third timer.

Exemplarily, the third timer is associated with the first DRX.

The first DRX may be used to control monitoring of terminal device-specific control information.

It should be noted that the first DRX can also be used to control monitoring of control information that is not specific to the terminal device, which is not limited by this application.

For example, the first DRX can be used to control monitoring of control information for any one or more of the following RNTIs: C-RNTI, cancellation indication RNTI (CI-RNTI), configuration scheduling RNTI (configured scheduling RNTI, CS) -RNTI), interrupt RNTI (interruption RNTI, INT-RNTI), slot format indication RNTI (slot format indication RNTI, SFI-RNTI), semi-static channel state information (channel state information, CSI) RNTI (semi-persistent CSI RNTI , SP-CSI-RNTI), transmission power control-physical uplink control channel-RNTI (transmit power control-PUCCH-RNTI, TPC-PUCCH-RNTI), transmission power control-physical uplink shared channel-RNTI (transmit power control-PUSCH -RNTI, TPC-PUSCH-RNTI), transmission power control-sounding reference signal-RNTI (TPC-SRS-RNTI), acquisition indicator (acquisition indicator, AI)-RNTI, side Sidelink RNTI (sidelink RNTI, SL-RNTI), sidelink configured scheduling RNTI (sidelink configured scheduling RNTI, SLCS-RNTI), sidelink semi-persistent scheduling V2X RNTI (SL semi-persistent scheduling V-RNTI) .

For example, the first DRX may be unicast DRX, or a DRX group (for example, a DRX group).

Exemplarily, the activation time of the first DRX may include any one or more of the following: the running time of the duration timer corresponding to unicast (for example, drx-onDurationTimer); the inactivation timer corresponding to unicast (for example, drx-InactivityTimer); or, the running time of the retransmission timer corresponding to unicast.

For example, the retransmission timer corresponding to unicast may include any one or more of the following: downlink retransmission timer (for example, drx-RetransmissionTimerDL), uplink retransmission timer (for example, drx-RetransmissionTimerUL), or, Sidelink retransmission timer (e.g., drx-RetransmissionTimerSL).

It can be understood that, within the activation time of the first DRX, the terminal device monitors control information specific to the terminal device.

For example, the duration timer/duration timer corresponding to unicast is used to indicate the duration of waiting for the terminal device to receive control information (eg, DCI) after waking up.

For example, the inactivation timer/inactivation timer corresponding to unicast is used to indicate a period of time after the newly transmitted control information or newly transmitted data is scheduled.

For example, the retransmission timer/retransmission timer corresponding to unicast is used to indicate the length of time for the terminal device to receive retransmission (for example, retransmission of DCI, retransmission of data, retransmission of resources).

For example, the downlink retransmission timer/downlink retransmission timer corresponding to unicast is used to instruct the terminal device to receive the downlink retransmission (eg For example, the duration of retransmitting DCI, retransmitting data, retransmitting resources).

For example, the uplink retransmission timer/uplink retransmission timer corresponding to unicast is used to indicate the length of time for the terminal device to receive uplink retransmission (for example, retransmission of DCI, retransmission of data, retransmission of resources).

For example, the sidelink retransmission timer/sidelink retransmission timer corresponding to unicast is used to instruct the terminal device to receive sidelink retransmission (for example, retransmission of DCI, retransmission of data, retransmission of resources) duration.

Exemplarily, the activation time of the first DRX may include any one or more of the following: the running time of the duration timer (for example, drx-onDurationTimer) corresponding to the DRX group; the inactivation timer corresponding to the DRX group (for example, drx-InactivityTimer); or, the running time of the retransmission timer corresponding to the DRX group.

It should be noted that the activation time of the first DRX may also include other times, which is not limited by this application. For example, for the activation time of the first DRX, please refer to 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification".

For example, the third timer is a retransmission timer corresponding to unicast (for example, drx-RetransmissionTimerDL-PTM).

For example, the third timer is a retransmission timer corresponding to the DRX associated with the unicast or a retransmission timer corresponding to the first DRX.

For example, the third timer is associated with the first HARQ process.

For example, after receiving the first control information or after receiving the first data on the first resource, the terminal device may first determine whether there is a running third timer. In case there is a running third timer, the third timer may be stopped.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Data 1 is received on the MBS SPS resource (e.g., associated with the first HARQ process), a third timer associated with the unicast (e.g., a retransmission timer associated with the first HARQ process) may be running, and the terminal The device can stop the third timer. It can be understood that the third timer runs so that the terminal device can receive retransmission (e.g., retransmission of DCI and/or retransmission of data) of data 2 (e.g., associated with unicast), but in this case , since the first HARQ process has been used by data 1, therefore, the terminal device will no longer receive retransmission of data 2. Therefore, in this case, it is meaningless if the third timer continues to run, and will cause the terminal device to consume power. In order to avoid the meaningless running of the third timer, the third timer can be stopped, and then the third timer can be stopped. Reduce the power consumption of terminal equipment.

Optionally, the communication method may also include: 403 (not shown in the figure). The terminal device receives the second control information transmitted in a multicast manner, or the terminal device receives the second data on the second resource. For example, correspondingly, the network device sends the second control information transmitted in a multicast manner, or the network device sends the second data on the second resource.

The second control information is used to schedule second data or second data transmitted in a multicast manner. For example, the second control information may be DCI or other control information transmitted through the PDCCH.

For example, the second control information and/or the second data are associated with the second RNTI.

For example, the second control information and/or the second data are associated with the first HARQ process.

For example, the second resource and/or the second data are associated with the second RNTI.

For example, the second data is associated with the first HARQ process.

The second control information transmitted in a multicast manner may include/be understood as: second control information scrambled by the second RNTI, or second control information associated with the second RNTI.

For example, "the second control information is associated with the second RNTI" or "the second control information is associated with the second RNTI" can be understood as: the second RNTI scrambles the second control information, or the CRC of the second control information Scrambled by the second RNTI (eg, PDCCH/DCI/control information with CRC scrambled by the second RNTI).

For example, association of the second data with the second RNTI can be understood as: the second RNTI scrambles the second data.

The second data transmitted in a multicast manner may include/be understood as: second data scrambled by the second RNTI, or second data associated with the second RNTI.

For example, the second RNTI is associated with the second multicast.

For example, the second data may be multicast data.

It can be understood that the second control information is control information used for scheduling multicast service data, and the second data is multicast service data.

For example, the second resource is/includes a resource/configuration resource associated with multicast/second multicast.

The second resource is/includes resources/configuration resources associated with multicast/second multicast, which can be understood as: the second resource is within the public frequency resource corresponding to multicast, or the second resource is associated with multicast/second multicast. SPS resources corresponding to multicast.

The SPS resources corresponding to multicast/second multicast can be understood as common SPS resources (for example, PDSCH resources) corresponding to multicast/second multicast. It can be understood that any terminal device that receives multicast/second multicast can receive data on the SPS resource corresponding to the multicast/second multicast.

Exemplarily, the terminal device can send messages through broadcast messages (for example, system information, MCCH) messages, RRC messages (for example, proprietary RRC messages), MAC messages (for example, MAC CE), physical layer messages (for example, DCI), preset messages, etc. Any one or more items in the configuration obtain SPS resources/configuration of SPS resources and/or obtain SPS resources/configuration of SPS resources corresponding to the multicast/second multicast.

For example, the second resource may be a PDSCH resource.

For example, the second RNTI may be used for activation/reactivation/deactivation of the second resource.

For example, the second RNTI may be used to schedule retransmission resources of the second resource.

For example, the first resource is different from the second resource.

Optionally, the communication method may also include: 404. The terminal device performs any one or more of the following steps 404-1 and 404-2:

404-1 (not shown in the figure). The terminal device starts or restarts the fourth timer.

Exemplarily, the fourth timer is associated with the second multicast DRX.

Exemplarily, the fourth timer is an RTT timer corresponding to multicast (for example, drx-HARQ-RTT-TimerDL-PTM).

For example, the RTT timer/RTT timer duration is used to indicate the length of time the terminal device waits before receiving a retransmission (eg, data/DCI).

For example, the fourth timer is an RTT timer corresponding to the DRX associated with the second RNTI or an RTT timer corresponding to the second multicast DRX.

For example, the fourth timer is associated with the first HARQ process.

Optionally, starting or restarting the fourth timer must meet the following conditions: HARQ feedback is enabled.

Optionally, starting or restarting the fourth timer includes: the terminal device sends second feedback information, the second feedback information is used to indicate whether the terminal device receives the second data successfully or fails; or, during the second feedback time or the second feedback time After or before the second feedback time, start or restart the fourth timer. The second feedback time is the time domain position where the second feedback resource is located, and the second feedback resource is associated with the second data.

The second feedback information may include: confirm (acknowledge, ACK) ACK and/or deny (not acknowledge, NACK).

For example, the second feedback resource associated with the second data may include/be understood as: the second feedback resource is used by the terminal device to send the second feedback information.

For example, the second feedback resource may be the first feedback resource in the time domain or the first feedback resource in the time domain associated with the second data. The last feedback resource on this application is not limited. For example, multiple terminal devices receive the second data, and the feedback resources corresponding to the multiple terminal devices may be the same in the time domain (for example, time-divided). The second feedback resource may be in the time domain among the multiple feedback resources. on the first feedback resource or on the last feedback resource in the time domain. In this way, the activation time of different terminal devices (activation time of DRX associated with multicast) can be aligned to ensure that the terminal device can receive control information and/or data sent by the network device.

For example, the terminal device may send the second feedback information on PUCCH resources or PUSCH resources.

For example, the second feedback resource may include PUCCH resources.

Optionally, starting or restarting the fourth timer must meet the following conditions: the terminal device fails to receive/decode the second data.

Optionally, the terminal device may start the fourth timer after a third time period/at a third time after receiving the second control information, or start the fourth timer after a third time period/at a third time after receiving the second data. or, start the fourth timer after the third time period/the third time after sending the second feedback information, or start the fourth timer after the third time period/the third time after the second feedback time.

The third moment may be the c-th symbol/slot/subframe/frame, etc. Among them, c is an integer greater than or equal to 0. For example, c is 1. The value of the third moment/the value of c/the value of the third duration may be configured or pre-configured by the network device or specified by the protocol, which is not limited by this application.

Optionally, the communication method may also include: when the fourth timer times out, the terminal device starts or restarts the first timer; or when the fourth timer times out, the terminal device fails to receive/decode the second data, and the terminal device starts or restarts the first timer. A timer.

Optionally, the terminal device may start the first timer after the fourth time period/at the fourth moment after the fourth timer times out.

The fourth moment may be the dth symbol/slot/subframe/frame, etc. Among them, d is an integer greater than or equal to 0. For example, d is 1. The value of the fourth moment/the value of d/the value of the fourth duration may be configured or pre-configured by the network device or specified by the protocol, which is not limited by this application.

For example, the terminal device receives DCI and/or data transmitted through the G+G transmission mode (for example, DCI1 scrambled by the second G-RNTI/second G-CS-RNTI (for example, associated with the first HARQ process)) , or receive data transmitted in a configured transmission mode (for example, receive data 1 on the MBS SPS resource associated with the second G-RNTI/second G-CS-RNTI (for example, associated with the first HARQ process)), the network The device may subsequently retransmit the data through G+G transmission. In order to ensure that the terminal device can receive DCI and/or data subsequently transmitted by the network device through the G+G transmission mode, the terminal device can start or restart the fourth timer corresponding to the DRX associated with the second multicast. Optionally, after the fourth timer times out, start or restart the first timer corresponding to the DRX associated with the second multicast. In this way, if the network device transmits other DCI and/or data through G+G transmission mode (or C+G transmission mode transmission) during the running time of the first timer, or retransmits the data, it can ensure that the terminal device DCI and/or data can be received, or in other words, the terminal device can be prevented from being in a sleep state and unable to receive DCI and/or data, thereby improving the reliability of data transmission. In addition, the terminal device starts or restarts the fourth timer corresponding to the DRX associated with the second multicast, and after the fourth timer times out, starts or restarts the first timer corresponding to the DRX associated with the second multicast, or it can Avoiding monitoring the retransmission of the data during the running time of the fourth timer is beneficial to energy saving of the terminal device. Starting or restarting the first timer corresponding to the DRX associated with the second multicast can ensure that the terminal device can receive DCI and/or data, or it can avoid the terminal device being in a sleep state and unable to receive DCI and/or data, improving improves the reliability of data transmission.

404-2 (not shown in the figure). The terminal device starts or restarts the fifth timer.

Exemplarily, the fifth timer is associated with the first DRX.

For example, the fifth timer is an RTT timer corresponding to unicast (for example, drx-HARQ-RTT-TimerDL).

For example, the fifth timer is an RTT timer corresponding to the DRX associated with unicast or an RTT timer corresponding to the first DRX.

For example, the fifth timer is associated with the first HARQ process.

Optionally, starting or restarting the fifth timer must meet the following conditions: HARQ feedback is enabled.

Optionally, starting or restarting the fifth timer includes: the terminal device sends second feedback information, the second feedback information is used to indicate whether the terminal device receives the second data successfully or fails; or, during the second feedback time or the second feedback time After or before the second feedback time, start or restart the fifth timer. The second feedback time is the time domain position where the second feedback resource is located, and the second feedback resource is associated with the second data.

Optionally, starting or restarting the fifth timer must meet the following conditions: the terminal device fails to receive/decode the second data.

Optionally, the terminal device can start the fifth timer after the fifth time period/the fifth time after receiving the second control information, or start the fifth timer after the fifth time period/the fifth time after receiving the second data. or, start the fifth timer after the fifth time period/the fifth time after sending the second feedback information, or start the fifth timer after the fifth time period/the fifth time after the second feedback time.

It should be noted that the fifth duration and the third duration may be the same or different, without limitation.

It should be noted that the fifth moment and the third moment may be the same or different, without limitation.

The fifth moment may be the e-th symbol/slot/subframe/frame, etc. Among them, e is an integer greater than or equal to 0. For example, e is 1. The value of the fifth moment/the value of e/the value of the fifth duration may be configured or pre-configured by the network device or specified by the protocol, which is not limited by this application.

Optionally, the communication method may also include: when the fifth timer times out, the terminal device starts or restarts the third timer; or when the fifth timer times out, the terminal device fails to receive/decode the second data, and the terminal device starts or restarts the third timer. Three timers.

Optionally, the terminal device may start the third timer after the sixth time/sixth time after the fifth timer expires.

It should be noted that the sixth duration and the fourth duration may be the same or different, without limitation.

It should be noted that the sixth moment and the fourth moment may be the same or different, without limitation.

The sixth moment may be the f-th symbol/slot/subframe/frame, etc. Among them, f is an integer greater than or equal to 0. For example, f is 1. The value of the sixth moment/the value of f/the value of the sixth duration may be configured or pre-configured by the network device or specified by the protocol, which is not limited by this application.

For example, the terminal device receives DCI and/or data transmitted through the G+G transmission mode (for example, DCI1 scrambled by the second G-RNTI/second G-CS-RNTI (for example, associated with the first HARQ process)) , or receiving data transmitted in a configured transmission mode (for example, receiving data 1 on the MBS SPS resource associated with the second G-RNTI/second G-CS-RNTI (for example, associated with the first HARQ process)), the network The device may subsequently retransmit the data through C+C transmission. In order to ensure that the terminal device can receive DCI and/or data subsequently transmitted by the network device through the C+C transmission mode, the terminal device can start or restart the fifth timer corresponding to the DRX associated with unicast. Optionally, after the fifth timer times out, start or restart the third timer corresponding to the DRX associated with the unicast. In this way, if the network device transmits other DCI and/or data through G+G transmission mode (or C+G transmission mode transmission) during the running time of the third timer, or retransmits the data, it can ensure that the terminal device DCI and/or data can be received, or in other words, the terminal device can be prevented from being in a sleep state and unable to receive DCI and/or data, thereby improving the reliability of data transmission. In addition, the terminal device starts or restarts the fifth timer corresponding to the DRX associated with the unicast, and after the fifth timer times out, starts or restarts the third timer corresponding to the DRX associated with the unicast, which can also avoid the fifth timer. Monitoring the retransmission of the data during the running time of the timer is beneficial to energy saving of the terminal device. Starting or restarting the third timer corresponding to the DRX associated with unicast can ensure that the terminal device can receive DCI and/or data, or in other words, it can avoid terminal The device is in sleep state and cannot receive DCI and/or data, which improves the reliability of data transmission.

For example, before step 401 or step 402, the communication method may further include: step 403 and/or step 404.

Optionally, the communication method may also include: 405 (not shown in the figure). The terminal device receives the third control information transmitted in a multicast manner, or the terminal device receives the third data on the third resource. For example, correspondingly, the network device sends the third control information transmitted in a multicast manner, or the network device sends the third data on the third resource.

The third control information is used to schedule third data or third data transmitted in a multicast manner. For example, the third control information may be DCI or other control information transmitted through the PDCCH.

For example, the third control information and/or the third data are associated with the first RNTI.

For example, the third control information and/or the third data are associated with the first HARQ process.

For example, the third resource and/or the third data are associated with the first RNTI.

For example, the third data is associated with the first HARQ process.

The third control information transmitted in a multicast manner may include/be understood as: the third control information scrambled by the first RNTI, or the third control information associated with the first RNTI.

For example, "the third control information is associated with the first RNTI" or "the third control information is associated with the first RNTI" can be understood as: the first RNTI scrambling the third control information, or the CRC of the third control information Scrambled by the first RNTI (e.g., PDCCH/DCI/Control Information with CRC scrambled by the first RNTI).

For example, association of the third data with the first RNTI can be understood as: the first RNTI scrambles the third data.

The third data transmitted in a multicast manner may include/be understood as: third data scrambled by the first RNTI, or third data associated with the first RNTI.

For example, the third data may be multicast data.

It can be understood that the third control information is control information used for scheduling multicast service data, and the third data is multicast service data.

The third resource is/includes a resource/configuration resource associated with the multicast/first multicast.

The third resource is/includes resources/configuration resources associated with multicast/first multicast, which can be understood as: the third resource is within the public frequency resource corresponding to multicast, or the third resource is associated with multicast/first multicast. SPS resources corresponding to multicast.

For example, the third resource may be a PDSCH resource.

For example, the first resource and the third resource may be the same or different.

Optionally, the communication method may also include: 406. The terminal device performs any one or more of the following steps 406-1 and 406-2:

406-1 (not shown in the figure). The terminal device starts or restarts the sixth timer.

Exemplarily, the sixth timer is associated with the first multicast DRX.

For example, the sixth timer is an RTT timer corresponding to multicast (for example, drx-HARQ-RTT-TimerDL-PTM).

For example, the sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI or an RTT timer corresponding to the first multicast DRX.

For example, the sixth timer is associated with the first HARQ process.

Optionally, starting or restarting the sixth timer must meet the following conditions: HARQ feedback is enabled.

Optionally, starting or restarting the sixth timer includes: the terminal device sends third feedback information, the third feedback information is used to indicate whether the terminal device receives the third data successfully or fails; or, during the third feedback time or the third feedback time After or before the third feedback time, the third feedback time is the time domain position where the third feedback resource is located, and the third feedback resource is associated with the third data; start or restart the sixth timer.

The third feedback information may include: ACK and/or NACK.

For example, the third feedback resource associated with the third data may include/be understood as: the third feedback resource is used by the terminal device to send third feedback information.

For example, the third feedback resource may be the first feedback resource in the time domain or the last feedback resource in the time domain associated with the third data, which is not limited by this application. For example, multiple terminal devices receive the third data, and the feedback resources corresponding to the multiple terminal devices may be the same in the time domain (for example, time-divided). The third feedback resource may be the time domain among the multiple feedback resources. on the first feedback resource or on the last feedback resource in the time domain. In this way, the activation time of different terminal devices (activation time of DRX associated with multicast) can be aligned to ensure that the terminal device can receive control information and/or data sent by the network device.

For example, the terminal device may send the third feedback information on PUCCH resources or PUSCH resources.

For example, the third feedback resource may include PUCCH resources.

Optionally, starting or restarting the sixth timer must meet the following conditions: the terminal device fails to receive/decode the third data.

Optionally, the terminal device may start the sixth timer after a third period of time/at a third moment after receiving the third control information, or start the sixth timer after a third period of time/at a third moment after receiving the third data. or, start the sixth timer after the third time period/the third time after sending the third feedback information, or start the sixth timer after the third time period/the third time after the third feedback time.

Optionally, the communication method may also include: when the sixth timer times out, the terminal device starts or restarts the second timer; or when the sixth timer times out, the terminal device fails to receive/decode the third data, and the terminal device starts or restarts the third timer. A timer.

Optionally, the terminal device may start the second timer after the fourth time period/at the fourth moment after the sixth timer expires.

For example, the terminal device receives DCI and/or data transmitted through the G+G transmission mode (for example, DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (for example, associated with the first HARQ process)) , or receiving data transmitted in a configured transmission mode (for example, receiving data 1 on the MBS SPS resource associated with the first G-RNTI/first G-CS-RNTI (for example, associated with the first HARQ process)), the network The device may subsequently retransmit the data through G+G transmission. In order to ensure that the terminal device can receive DCI and/or data subsequently transmitted by the network device through the G+G transmission mode, the terminal device can start or restart the sixth timer corresponding to the DRX associated with the first multicast. Optionally, after the sixth timer times out, start or restart the second timer corresponding to the DRX associated with the first multicast. In this way, if the network device transmits other DCI and/or data through G+G transmission mode (or C+G transmission mode transmission) during the running time of the second timer, or retransmits the data, it can ensure that the terminal device DCI and/or data can be received, or in other words, the terminal device can be prevented from being in a sleep state and unable to receive DCI and/or data; the reliability of data transmission is improved. In addition, the terminal device starts or restarts the sixth timer corresponding to the DRX associated with the first multicast, and after the sixth timer times out, starts or restarts the second timer corresponding to the DRX associated with the first multicast, or it can Avoiding monitoring the retransmission of the data during the running time of the sixth timer is beneficial to energy saving of the terminal device. Starting or restarting the second timer corresponding to the DRX associated with the first multicast can ensure that the terminal device can receive DCI and/or data, or it can prevent the terminal device from being in a sleep state and unable to receive DCI and/or data; improve improves the reliability of data transmission.

406-2 (not shown in the figure), the terminal device starts or restarts the fifth timer.

For content related to "the terminal device starts or restarts the fifth timer", please refer to the description in step 404-2 and will not be described again here.

For example, the terminal device receives DCI and/or data transmitted through the G+G transmission mode (for example, DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (for example, associated with the first HARQ process)) , or receive data transmitted in a configured transmission mode (for example, connect on the MBS SPS resource associated with the first G-RNTI/first G-CS-RNTI After receiving data 1 (for example, associated with the first HARQ process)), the network device may subsequently transmit a retransmission of the data through the C+C transmission mode. In order to ensure that the terminal device can receive DCI and/or data subsequently transmitted by the network device through the C+C transmission mode, the terminal device can start or restart the fifth timer corresponding to the DRX associated with unicast. Optionally, after the fifth timer times out, start or restart the third timer corresponding to the DRX associated with the unicast. In this way, if the network device transmits other DCI and/or data through G+G transmission mode (or C+G transmission mode transmission) during the running time of the third timer, or retransmits the data, it can ensure that the terminal device DCI and/or data can be received, or in other words, the terminal device can be prevented from being in a sleep state and unable to receive DCI and/or data; the reliability of data transmission is improved. In addition, the terminal device starts or restarts the fifth timer corresponding to the DRX associated with the unicast, and after the fifth timer times out, starts or restarts the third timer corresponding to the DRX associated with the unicast, which can also avoid the fifth timer. Monitoring the retransmission of the data during the running time of the timer is beneficial to energy saving of the terminal device. Starting or restarting the third timer corresponding to the DRX associated with unicast can ensure that the terminal device can receive DCI and/or data, or it can avoid the terminal device being in a sleep state and unable to receive DCI and/or data; improving data Transmission reliability.

For example, before step 401 or step 402, the communication method may further include: step 405 and/or step 406.

Optionally, the communication method may also include: 407 (not shown in the figure), the terminal device receives the fourth control information transmitted in a unicast manner, or the terminal device receives the fourth data on the fourth resource. For example, correspondingly, the network device sends fourth control information transmitted in a unicast manner, or the network device sends fourth data on a fourth resource.

The fourth control information is used to schedule fourth data or fourth data transmitted in a unicast manner. For example, the fourth control information may be DCI or other control information transmitted through the PDCCH.

For example, the fourth control information and/or the fourth data are associated with the unicast/third RNTI.

The third RNTI may be used for any one or more of the following: used for unicast, used for scheduling dynamic resources, used for retransmission resources of dynamic resources, used for activating configuration resources, used for reactivating configuration resources, used For deactivating configuration resources, retransmission resources for scheduling configuration resources are used for scrambling (for example, for scrambling PDCCH or PDSCH).

For example, the third RNTI may include/be C-RNTI and/or CS-RNTI.

For example, the fourth control information and/or the fourth data are associated with the first HARQ process.

For example, the fourth resource and/or the fourth data are associated with the third RNTI.

For example, the fourth data is associated with the first HARQ process.

The fourth control information transmitted in a unicast manner may include/be understood as: fourth control information scrambled by the third RNTI, or fourth control information associated with the third RNTI.

For example, "the fourth control information is associated with the third RNTI" or "the fourth control information is associated with the third RNTI" can be understood as: the third RNTI scrambles the fourth control information, or the CRC of the fourth control information Scrambled by the third RNTI (e.g., PDCCH/DCI/Control Information with CRC scrambled by the third RNTI).

For example, the association of the fourth data with the third RNTI can be understood as: the third RNTI scrambles the fourth data.

The fourth data transmitted in a unicast manner may include/be understood as: fourth data scrambled by the third RNTI, or fourth data associated with the third RNTI.

For example, the third RNTI is associated with unicast.

For example, the fourth data may be/include unicast data or multicast data.

It can be understood that the fourth control information is control information used for scheduling unicast data, and the fourth data is unicast data.

The fourth resource is/includes resources/configuration resources associated with unicast.

The fourth resource is/includes resources/configuration resources associated with unicast and can be understood as: the fourth resource is an SPS resource corresponding to unicast.

Exemplarily, the terminal device can send messages through broadcast messages (for example, system information, MCCH messages), RRC messages (for example, proprietary RRC messages), MAC messages (for example, MAC CE), physical layer messages (for example, DCI), preset messages, etc. Any one or more items in the configuration obtain SPS resources/configuration of SPS resources and/or obtain SPS resources/configuration of SPS resources corresponding to unicast.

For example, the fourth resource may be a PDSCH resource.

For example, the third RNTI may be used for activation/reactivation/deactivation of the fourth resource.

For example, the third RNTI may be used to schedule retransmission resources of the fourth resource.

For example, the first resource is different from the fourth resource. For example, the first resource is different from the second resource. For example, the first resource is different from the third resource.

Optionally, the communication method may also include: 408. The terminal device starts or restarts the fifth timer.

For example, the terminal device receives DCI and/or data transmitted through the C+C transmission method (for example, C-RNTI or CS-RNTI scrambled DCI1 (for example, associated with the first HARQ process)), or receives the configuration transmission method For the transmitted data (for example, data 1 is received on the SPS resource associated with unicast (for example, associated with the first HARQ process)), the network device may subsequently transmit a retransmission of the data through the C+C transmission mode. In order to ensure that the terminal device can receive DCI and/or data subsequently transmitted by the network device through the C+C transmission mode, the terminal device can start or restart the fifth timer corresponding to the DRX associated with unicast. Optionally, after the fifth timer times out, start or restart the third timer corresponding to the DRX associated with the unicast. In this way, if the network device transmits other DCI and/or data through G+G transmission mode (or C+G transmission mode transmission) during the running time of the third timer, or retransmits the data, it can ensure that the terminal device DCI and/or data can be received, or in other words, the terminal device can be prevented from being in a sleep state and unable to receive DCI and/or data, thereby improving the reliability of data transmission. In addition, the terminal device starts or restarts the fifth timer corresponding to the DRX associated with the unicast, and after the fifth timer times out, starts or restarts the third timer corresponding to the DRX associated with the unicast, which can also avoid the fifth timer. Monitoring the retransmission of the data during the running time of the timer is beneficial to energy saving of the terminal device. Starting or restarting the third timer corresponding to the DRX associated with unicast can ensure that the terminal device can receive DCI and/or data, or it can avoid the terminal device being in a sleep state and unable to receive DCI and/or data, thus improving the data Transmission reliability.

For example, before step 401 or step 402, the communication method may further include: step 407 and/or step 408.

It should be understood that after the terminal device receives the first control information transmitted in a multicast manner, or after receiving the first data on the first resource, the terminal device can stop all multicasts corresponding to the first HARQ process (for example, all running ) corresponding retransmission timer and/or unicast corresponding retransmission timer.

In response to the technical problem in question 2 above, in order to reduce the power consumption of the terminal device, this application proposes a communication method. As shown in Figure 5, the communication method may include the following steps.

501. The terminal device receives the first control information transmitted in a multicast mode, or the terminal device receives the first data on the first resource, or the terminal device receives the fifth control information transmitted in a unicast mode, or the terminal device Receive fifth data on a fifth resource. For example, correspondingly, the network device sends the first control information transmitted in a multicast mode, or the network device sends the first data on the first resource, or the network device sends the fifth control information transmitted in a unicast mode, or , the network device sends fifth data on the fifth resource.

For content related to the first control information and the first data, please refer to the description in step 401 and will not be described again here.

The fifth control information is used to schedule fifth data or fifth data transmitted in a unicast manner. For example, the fifth control information may be DCI or other control information transmitted through the PDCCH.

For example, the fifth control information and/or the fifth data are associated with the unicast/third RNTI.

For example, fifth control information and/or fifth data are associated with the first HARQ process.

For example, the fifth resource and/or the fifth data are associated with the third RNTI.

For example, the fifth data is associated with the first HARQ process.

The fifth control information transmitted in a unicast manner may include/be understood as: fifth control information scrambled by the third RNTI, or fifth control information associated with the third RNTI.

For example, "the fifth control information is associated with the third RNTI" or "the fifth control information is associated with the third RNTI" can be understood as: the third RNTI scrambles the fifth control information, or the CRC of the fifth control information Scrambled by the third RNTI (e.g., PDCCH/DCI/Control Information with CRC scrambled by the third RNTI).

For example, the association of the fifth data with the third RNTI can be understood as: the third RNTI scrambles the fifth data.

The fifth data transmitted in a unicast manner may include/be understood as: fifth data scrambled by the third RNTI, or fifth data associated with the third RNTI.

For example, the fifth data may be/include unicast data or multicast data.

It can be understood that the fifth control information is control information used for scheduling data of the unicast service, and the fifth data is data of the unicast service.

The fifth resource is/includes resources/configuration resources associated with unicast.

The fifth resource is/includes resources/configuration resources associated with unicast and can be understood as: the fifth resource is an SPS resource corresponding to unicast.

For example, the fifth resource may be a PDSCH resource.

For example, the third RNTI may be used for activation/reactivation/deactivation of the fifth resource.

For example, the third RNTI may be used to schedule retransmission resources of the fifth resource.

For example, the first resource is different from the fifth resource. For example, the fourth resource is the same as or different from the fifth resource.

502. The terminal device performs any one or more of the following steps 502-1, 502-2, and 502-3:

502-1. The terminal device stops the fourth timer.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Data1 is received on the MBS SPS resource (e.g., associated with the first HARQ process) or C-RNTI/CS-RNTI scrambled DCI1 (e.g., associated with the first HARQ process) or on the MBS SPS resource associated with the unicast Data 1 is received on the SPS resource (e.g., associated with the first HARQ process), the fourth timer associated with the second G-RNTI/second G-CS-RNTI (e.g., the RTT associated with the first HARQ process timer) may be running, the terminal device may stop the fourth timer. It can be understood that the fourth timer runs so that the first timer can be started after timeout, so that the terminal device can receive data 2 (for example, with the second G-RNTI/second G-CS during the running of the first timer). -RNTI associated) retransmission (for example, retransmission of DCI and/or retransmission of data), but in this case the terminal device will no longer receive the retransmission of data 2. Therefore, in this case, if the fourth timer continues to run, it is meaningless to start or restart the first timer after the fourth timer times out, and will cause the terminal device to consume power. In order to avoid the fourth timer and /Or the first timer runs meaninglessly, the fourth timer can be stopped, and then the Low terminal device power consumption.

502-2. The terminal device stops the fifth timer.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Receive data 1 on the MBS SPS resource (e.g., associated with the first HARQ process) or receive C-RNTI/CS-RNTI scrambled DCI1 (e.g., associated with the first HARQ process) or on the unicast associated Data 1 is received on the SPS resource (e.g., associated with the first HARQ process), the fifth timer associated with the unicast (e.g., the retransmission timer associated with the first HARQ process) may be running, and the terminal device may Stop the fifth timer. It can be understood that the fifth timer runs so that the third timer can be started after timeout, so that the terminal device can receive data 2 (for example, related to unicast/C-RNTI/CS-RNTI) during the running of the third timer. (for example, retransmitting DCI and/or retransmitting data), the terminal device will no longer receive retransmissions of data 2. Therefore, in this case, if the fifth timer continues to run, it is meaningless to start or restart the third timer after the fifth timer times out, and will cause the terminal device to consume power. In order to avoid the fifth timer and /Or the third timer runs meaninglessly, the fifth timer can be stopped, thereby reducing the power consumption of the terminal device.

502-3. The terminal device stops the sixth timer.

For example, the terminal device receives the DCI1 scrambled by the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) or in association with the first G-RNTI/first G-CS-RNTI. Receive data 1 on the MBS SPS resource (e.g., associated with the first HARQ process) or receive C-RNTI/CS-RNTI scrambled DCI1 (e.g., associated with the first HARQ process) or on the unicast associated Data 1 is received on the SPS resource (eg, associated with the first HARQ process), the sixth timer associated with the first G-RNTI/first G-CS-RNTI (eg, associated with the first HARQ process) transmission timer) may be running, the terminal device may stop the sixth timer. It can be understood that the sixth timer runs so that the second timer can be started after timeout, so that the terminal device can receive data 2 (for example, with the first G-RNTI/first G-CS during the running of the second timer). -RNTI associated) retransmission (for example, retransmission of DCI and/or retransmission of data), the terminal device will no longer receive retransmission of data 2. Therefore, in this case, it is meaningless if the sixth timer continues to run. After the sixth timer times out, start or restart the second timer, which will cause the terminal device to consume power. In order to avoid the sixth timer and/or the second timer runs meaninglessly, the sixth timer can be stopped, thereby reducing the power consumption of the terminal device.

Optionally, the communication method may also include: 503 (not shown in the figure). The terminal device receives the second control information transmitted in a multicast manner, or the terminal device receives the second data on the second resource. For example, correspondingly, the network device sends the second control information transmitted in a multicast manner, or the network device sends the second data on the second resource.

Optionally, the communication method may also include: 504. The terminal device performs any one or more of the following steps 504-1 and 504-2:

504-1 (not shown in the figure). The terminal device starts or restarts the fourth timer.

504-2 (not shown in the figure). The terminal device starts or restarts the fifth timer.

For example, before step 501 or step 502, the communication method may further include: step 503 and/or step 504.

Optionally, the communication method may also include: 505 (not shown in the figure). The terminal device receives the third control information transmitted in a multicast manner, or the terminal device receives the third data on the third resource. For example, correspondingly, the network device sends the third control information transmitted in a multicast manner, or the network device sends the third data on the third resource.

Optionally, the communication method may also include: 506. The terminal device performs any one or more of the following steps 506-1 and 506-2:

506-1 (not shown in the figure). The terminal device starts or restarts the sixth timer.

506-2 (not shown in the figure). The terminal device starts or restarts the fifth timer.

For information related to "the terminal device starts or restarts the fifth timer", please refer to the description in step 504-2 and will not be described again here.

For example, before step 501 or step 502, this embodiment also includes: step 505 and/or step 506.

Optionally, the communication method may also include: 507 (not shown in the figure). The terminal device receives the fourth control information transmitted in a unicast manner, or the terminal device receives the fourth data on the fourth resource. For example, correspondingly, the network device sends fourth control information transmitted in a unicast manner, or the network device sends fourth data on a fourth resource.

Optionally, the communication method may also include: 508. The terminal device starts or restarts the fifth timer.

For example, before step 501 or 502, the communication method may further include: step 507 and/or step 508.

It should be noted that the content/explanation of the embodiment shown in FIG. 5 may refer to the description of the embodiment shown in FIG. 4 and will not be described again here.

It should be understood that the terminal device receives the first control information transmitted in a multicast manner, or after the terminal device receives the first data on the first resource, or after receiving the fifth control information transmitted in a unicast manner, or After receiving the fifth data on the fifth resource, all multicast (for example, all running) corresponding RTT timers and/or unicast corresponding RTT timers corresponding to the first HARQ process may be stopped.

In one embodiment, a communication method may simultaneously include the communication method corresponding to Figure 4 and the communication method corresponding to Figure 5. For example, the communication method may include step 501. The communication method may also include step 402 and/or step 502. Optionally, the communication method may also include any one or more of steps 403/503, 404/504, 405/505, 406/506, 407/507, and 408/508.

It should be understood that in the above communication method, the terminal device can also obtain the DRX configuration. DRX configuration is used to configure different timers corresponding to DRX. The durations of different timers can be the same or different.

It should be understood that in the above communication method, the data received by the terminal device or the data scheduled for the terminal device may be newly transmitted data or retransmitted data.

It should be understood that the relevant descriptions of the same information or corresponding information in different communication methods or in different steps, different locations, or different embodiments in the same communication method can refer to each other.

It should be understood that the existing technology may change with the evolution of technical solutions, and the technical solutions provided in this application are not limited to the existing technologies provided.

It should be noted that different embodiments or some steps (for example, any one or more steps) in different embodiments in this application can be combined with each other to form new embodiments. It should be noted that some steps in different embodiments are not limited or any one or more steps may include optional steps in a certain embodiment, or may include mandatory steps in a certain embodiment, or may include certain steps. The optional steps and required steps in each embodiment are not limited by this application.

It should be noted that, if there is no special explanation or logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referenced to each other.

It should be noted that the order of the steps in the embodiments of this application is not limited by this application.

Based on the above network architecture, please refer to FIG. 6 , which is a schematic structural diagram of a communication device disclosed in an embodiment of the present application. As shown in Figure 6, the communication device may include a transceiver unit 601 and a processing unit 602.

The communication device may be a terminal device, a chip, a chip system, or a processor that supports the terminal device to implement the method, or a logic module or software that can realize all or part of the functions of the terminal device.

In one case, the transceiver unit 601 is used to receive first control information transmitted in a multicast manner, the first control information is used to schedule first data, and the first control information and/or the first data are associated with the first RNTI. , the first control information and/or the first data are associated with the first HARQ process; or,

The transceiver unit 601 is configured to receive the first data on the first resource, the first resource and/or the first data are associated with the first RNTI, and the first data is associated with the first HARQ process;

The processing unit 602 is configured to stop a first timer, the first timer is a retransmission timer corresponding to the DRX associated with the second RNTI, and the first timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.

In one embodiment, the processing unit 602 is also used to:

In one embodiment, the transceiver unit 601 is also configured to receive second control information transmitted in a multicast manner, the second control information is used to schedule the second data, the second control information and/or the second data and the second RNTI associated, the second control information and/or the second data are associated with the first HARQ process; or,

The transceiver unit 601 is also configured to receive second data on the second resource, the second resource and/or the second data are associated with the second RNTI, and the second data is associated with the first HARQ process;

The processing unit 602 is also configured to start or restart a fourth timer, the fourth timer is an RTT timer corresponding to the DRX associated with the second RNTI, and the fourth timer is associated with the first HARQ process; and/or,

The processing unit 602 is also configured to start or restart a fifth timer. The fifth timer is an RTT timer corresponding to the DRX associated with unicast. The fifth timer is associated with the first HARQ process.

In one embodiment, the processing unit 602 is also used to:

In one embodiment, the transceiver unit 601 is also configured to receive third control information transmitted in a multicast manner, the third control information is used to schedule the third data, and the third control information and/or the third data are consistent with the first RNTI. associated, the third control information and/or the third data are associated with the first HARQ process; or,

The transceiver unit 601 is also configured to receive third data on a third resource, the third resource and/or the third data are associated with the first RNTI, and the third data is associated with the first HARQ process;

The processing unit 602 is also configured to start or restart a sixth timer. The sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI. The sixth timer is associated with the first HARQ process; and/or,

In one embodiment, the processing unit 602 is also used to:

In one embodiment, the transceiver unit 601 is also configured to receive the fourth control information transmitted in a unicast manner, the fourth control information is used to schedule the fourth data, the fourth control information and/or the fourth data are related to the first HARQ process associated; or,

The transceiver unit 601 is also configured to receive fourth data on a fourth resource, where the fourth resource is a configuration resource corresponding to unicast, and the fourth data is associated with the first HARQ process;

In one embodiment, the processing unit 602 is also configured to start or restart the third timer when the fifth timer times out and the reception or decoding of the fourth data fails.

In one embodiment, the first control information transmitted in a multicast manner includes: first control information scrambled by the first RNTI.

In one embodiment, the first RNTI includes a first G-RNTI and/or a first G-CS-RNTI, and/or the second RNTI includes a second G-RNTI and/or a second G-CS-RNTI.

In one embodiment, the first RNTI and/or the second RNTI are used for one or more of the following: for multicast, for scheduling multicast dynamic resources, for scheduling retransmission resources of multicast dynamic resources, for For activating multicast configuration resources, for reactivating multicast configuration resources, for deactivating multicast configuration resources, and for scheduling retransmission resources of multicast configuration resources.

A more detailed description of the above transceiver unit 601 and the processing unit 602 can be obtained directly by referring to the relevant description of the terminal device in the above method embodiment shown in Figure 4, and will not be described again here.

In another case, the transceiver unit 601 is used to receive the first control information transmitted in a multicast manner, the first control information is used to schedule the first data, and the first control information and/or the first data are related to the first RNTI. associated, the first control information and/or the first data are associated with the first HARQ process; or,

Transceiver unit 601, configured to receive first data on a first resource, the first resource and/or the first data are associated with the first RNTI, and the first data is associated with the first HARQ process; or,

Transceiver unit 601, configured to receive fifth control information transmitted in a unicast manner, the fifth control information is used to schedule fifth data, and the fifth control information and/or the fifth data are associated with the first HARQ process; or,

The transceiver unit 601 is configured to receive fifth data on a fifth resource, where the fifth resource is a configuration resource corresponding to unicast, and the fifth data is associated with the first HARQ process;

The processing unit 602 is used for:

Stop the fourth timer, the fourth timer is the RTT timer corresponding to the DRX associated with the second RNTI, and the fourth timer is associated with the first HARQ process; and/or

Stop the fifth timer. The fifth timer is the RTT timer corresponding to the DRX associated with unicast. The fifth timer is associated with the first HARQ process;

Stop the sixth timer, the sixth timer is the RTT timer corresponding to the DRX associated with the first RNTI, and the sixth timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.

The processing unit 602 is also used to start or restart the fourth timer; and/or,

The processing unit 602 is also used to start or restart the fifth timer.

The processing unit 602 is also used to start or restart the fifth timer; and/or,

The processing unit 602 is also used to start or restart the sixth timer.

The processing unit 602 is also used to start or restart the fifth timer.

A more detailed description of the above-mentioned transceiver unit 601 and processing unit 602 can be obtained directly by referring to the relevant description of the terminal device in the above-mentioned method embodiment shown in Figure 5, and will not be described again here.

Based on the above network architecture, please refer to FIG. 7 , which is a schematic structural diagram of another communication device disclosed in an embodiment of the present application. As shown in FIG. 7 , the communication device may include a processor 701 , a memory 702 , a transceiver 703 and a bus 704 . The memory 702 may exist independently and may be connected to the processor 701 through a bus 704. Memory 702 may also be integrated with processor 701. Among them, bus 704 is used to realize the connection between these components. In one case, as shown in Figure 7, transceiver 703 may include a transmitter 7031, a receiver 7032, and an antenna 7033. In another case, transceiver 703 may include a transmitter (i.e., an output interface) and a receiver (i.e., an input interface). A transmitter may include a transmitter and an antenna, and a receiver may include a receiver and an antenna.

The communication device may be a terminal device or a module in the terminal device. When the computer program instructions stored in the memory 702 are executed, the processor 701 is used to perform the operations performed by the processing unit 602 in the above embodiment, and the transceiver 703 is used to perform the operations performed by the transceiver unit 601 in the above embodiment. The above communication device can also be used to perform various methods performed by the terminal device in the above method embodiments of Figure 4 and/or Figure 5, which will not be described again.

Based on the above network architecture, please refer to FIG. 8 , which is a schematic structural diagram of another communication device disclosed in an embodiment of the present application. As shown in FIG. 8 , the communication device may include an input interface 801 , a logic circuit 802 and an output interface 803 . The input interface 801 and the output interface 803 are connected through a logic circuit 802 . Among them, the input interface 801 is used to receive information from other communication devices, and the output interface 803 is used to output, schedule or send information to other communication devices. The logic circuit 802 is used to perform operations other than the operations of the input interface 801 and the output interface 803, such as implementing the functions implemented by the processor 701 in the above embodiment. Wherein, the communication device may be a terminal device (or a module within the terminal device)). Among them, a more detailed description of the input interface 801, the logic circuit 802 and the output interface 803 can be directly obtained by referring to the relevant description of the terminal device in the above method embodiment, and will not be described again here.

It should be understood that each of the above modules can be independent or integrated together. For example, the transmitter, receiver and antenna can be separate or integrated into a transceiver. For another example, the input interface and the output interface can be independent or integrated into a communication interface.

An embodiment of the present application also discloses a computer-readable storage medium on which instructions are stored. When the instructions are executed, the method in the above method embodiment is executed.

An embodiment of the present application also discloses a computer program product including computer instructions. When the computer instructions are executed, the method in the above method embodiment is executed.

An embodiment of the present application also discloses a communication system, which may include a centralized controller, a route calculator, and a route executor. For specific description, reference may be made to the communication method shown above.

The above-mentioned specific embodiments further describe the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above-mentioned are only specific embodiments of the present application and are not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solution of this application shall be included in the scope of protection of this application.

Obviously, the above-described embodiments are only some of the embodiments of the present application, but not all of the embodiments. Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present embodiment application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will understand, both explicitly and implicitly, that the embodiments described herein may be combined with other embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a series of steps or units are included, or optionally, steps or units that are not listed, or optionally other steps or units that are inherent to these processes, methods, products or devices.

The drawings show only part but not all of the content relevant to the present application. Before discussing example embodiments in more detail, it should be mentioned that some example embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe various operations (or steps) as a sequential process, many of the operations may be performed in parallel, concurrently, or simultaneously. Additionally, the order of operations can be rearranged. The process may be terminated when its operation is completed, but may also have additional steps not included in the figures.

The terms "unit" and the like used in this specification are used to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software or software in execution. For example, a unit may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program and/or distributed between two or more computers. Additionally, these units can execute from various computer-readable media having various data structures stored thereon. A unit may, for example, respond to a signal having one or more data packets (eg, data from a second unit interacting with another unit, a local system, a distributed system, and/or a network. For example, the Internet interacting with other systems via signals) Communicate through local and/or remote processes.

With different user needs, current terminal equipment is divided into traditional terminal equipment and low capability (reduced capability, REDCAP) terminal equipment. Among them, REDCAP terminal equipment refers to low-complexity devices used for industrial wireless sensors, video surveillance and wearable devices. On the one hand, since the capabilities of REDCAP terminal devices are lower than those of existing traditional terminal devices, when they access the network, they may need the network to provide them with more resources, which the network may refuse due to load or policy reasons. REDCAP terminal equipment is connected, so the network needs to identify the REDCAP terminal equipment before the REDCAP terminal equipment is connected; on the other hand, due to the reduced capability of the REDCAP terminal equipment, the network is adjusting for it. Special processing is required when allocating resources, such as scheduling resources for the REDCAP terminal device within the bandwidth range supported by the REDCAP terminal device. Therefore, the network also needs to identify the REDCAP terminal device before the REDCAP terminal device is connected. To this end, one possible method is to introduce a separate initial bandwidth part (BWP) for REDCAP terminal equipment, which can also be understood as a specific initial bandwidth part. This separate initial bandwidth part is configurable. REDCAP terminal equipment in the non-connected state only listens for paging on the initial BWP associated with CD-SSB (cell defined synchronization signal and PBCH block, CD-SSB). REDCAP terminal equipment in the non-connected state only monitors paging on the initial BWP associated with CD-SSB. Measurement is performed, where the initial BWP can be a non-REDCAP specific initial BWP or a REDCAP specific initial BWP (also called a separate initial BWP).

Small data transmission (SDT) is a process in which terminal devices transmit data in a non-connected state. The terminal device can perform small data transmission in the non-connected state through small data transmission based on random access, or can perform data transmission in the inactive state through configuration-based authorization resources. During small data transmission, the transmission of multiple uplink and/or downlink data is supported. During the small data transmission process, the terminal equipment needs to monitor the paging of system information change instructions and public warning system (PWS) notifications. PWS includes earthquake and tsunami warning system (earthquake and tsunami warning system, ETWS) and commercial mobile phones. Early warning system (commercial mobile alert system, CMAS). On the other hand, during small data transmission, the terminal equipment needs to perform synchronization signal and PBCH block (SSB) measurements, such as when verifying the timing to be effectively selected in advance or when performing SSB selection.

For REDCAP terminal equipment, when configuring a separate initial BWP, SDT resources can be configured on the separate initial BWP, including SDT resources based on random access and/or SDT resources based on configuration authorization. When the terminal device triggers the SDT process in a separate initial BWP, but the separate initial BWP does not contain CD-SSB and control resource set #0 (control-resource set#0, CORESET#0), the terminal device will Leading to conflict or overlap in at least two of the following: measurement, paging, downlink control information (DCI) for scheduling authorization, uplink transmission, or downlink transmission. At this time, how the UE handles this conflict is an issue that needs to be resolved urgently.

In one implementation method, the terminal device triggers the SDT process in a separate initial BWP. When the separate initial BWP does not contain CD-SSB and CORESET#0, the terminal device conflicts or overlaps with at least the following two items in the SDT process: Measure, paging, and schedule authorized downlink control information (DCI), or uplink transmission. The terminal device determines to perform at least one of the following according to the configured priority information: measurement, monitoring paging, monitoring downlink control information (DCI) for scheduling authorization, uplink transmission, or downlink transmission.

The measurement can be SSB measurement for TA verification of configuration authorization, or it can be measurement performed during SDT selection during uplink transmission. Paging can include system information changes, and/or PWS notifications; optionally, REDCAP terminal equipment can monitor system information change notifications at specific paging opportunities in each modification cycle during the SDT process. Optional, REDCAP terminal equipment The PWS notification can be monitored at specific paging opportunities in each default paging cycle during the SDT process, where the specific paging times can be one or more. The downlink control information of the scheduled grant can be understood as the grant scheduled by the network for downlink or uplink transmission through DCI. The optional DCI may overlap or partially overlap with the measurement timing. Uplink transmission includes an uplink grant dynamically scheduled by the network or a preconfigured uplink grant transmission opportunity. The uplink transmission may overlap or partially overlap with measurement or paging.

The configured priority information can be preconfigured or network configured. Optionally, the network can configure priority information through system information or dedicated signaling. When any two of the following events conflict: measurement, paging, downlink control information (DCI) of scheduling authorization, uplink transmission, or downlink transmission; the configured priority information includes high-priority events. It can be understood that when any two items A and B conflict or overlap, the configured priority information includes: A's priority is higher than B's priority, or B's priority is higher than A's priority. For example, when measurement and paging reception timing conflict When configured, the measurement priority is higher than the paging priority, or the paging priority is higher than the measurement priority. For example, when uplink transmission and paging conflict, the uplink transmission has a higher priority, and the terminal device performs uplink transmission without receiving paging. For another example, when measurement and paging conflict, the paging priority is high, and the terminal device receives paging without performing measurements. At this time, if the terminal device is on a separate initial BWP, the UE needs to switch to the initial BWP (or non-REDCAP). A specific initial BWP) receives the page. When any three of the following events conflict: measurement, paging, downlink control information (DCI) of scheduling authorization, uplink transmission, or downlink transmission; the configured priority information includes high-priority events or priority order. It can be understood that when any three items A, B and C conflict, the configured priority information includes: the priority from high to low is ABC or ACB or BCA or BAC or CAB or CBA; or the configured priority information includes: A has the highest priority or B has the highest priority or C has the highest priority. For example, when measurement, paging reception, and downlink transmission conflict, configure the downlink transmission priority to be higher than measurement, and the measurement priority to be higher than paging, or configure the highest priority to downlink transmission, and the terminal device performs downlink transmission and gives up or ignores the measurement. and paging reception. Optionally, if the measurement or paging priority is higher, the terminal device needs to perform BWP switching to perform measurement or paging reception. When any four of the following events conflict: measurement, paging, downlink control information (DCI) of scheduling authorization, uplink transmission, or downlink transmission; the configured priority information includes high-priority events or priority order. It can be understood that when any four items A, B, C and D conflict, the configured priority information includes: the priority from high to low is any combination of A, B, C, and D; or the configured priority information includes: A has the highest priority or B has the highest priority or C has the highest priority or D has the highest priority. There are 24 situations in any combination of A, B, C, and D priorities from high to low. When any five of the following events conflict: measurement, paging, downlink control information (DCI) of scheduling authorization, uplink transmission, or downlink transmission; the configured priority information includes high-priority events or priority order. It can be understood that when any five items A, B, C, D and E conflict, the configured priority information includes: the priority from high to low is any combination of A, B, C, D, E; or the configured Priority information includes: A has the highest priority or B has the highest priority or C has the highest priority or D has the highest priority or E has the highest priority. Optionally, if the measurement or paging priority is higher, the terminal device needs to perform BWP switching to perform measurement or paging reception.

In this implementation, by configuring the priorities of different conflict events, it is possible to ensure that the terminal device determines its operation or behavior when a conflict occurs, ensuring the alignment of the terminal device and the network device. Optionally, REDCAP terminal equipment is required to monitor system information change notifications at specific paging opportunities in each modification cycle during the SDT process. It can monitor PWS at specific paging opportunities during each default paging cycle during the SDT process. Notification, instead of listening for at least one SI change indication at any paging opportunity in each modification cycle, and not listening for at least one PWS notification at any paging opportunity in each default paging cycle, reducing the probability of conflict. Specifying specific paging timings to monitor paging ensures that the network schedules paging at specific paging timings, reducing the frequency of network paging transmission. At the same time, the network can avoid conflicts between other downlink scheduling and paging to a certain extent, reducing REDCAP The probability of conflict occurring when terminal equipment performs SDT.

Claims

A communication method, characterized by including:

receiving first control information transmitted in a multicast manner, the first control information being used to schedule first data, and the first control information and/or the first data being associated with a first wireless network temporary identifier RNTI, The first control information and/or the first data are associated with a first hybrid automatic repeat request HARQ process; or,

receiving first data on a first resource, the first resource and/or the first data being associated with a first RNTI, the first data being associated with the first HARQ process;

Stop a first timer, the first timer is a retransmission timer corresponding to the discontinuous reception DRX associated with the second RNTI, and the first timer is associated with the first HARQ process;

Wherein, the first RNTI and the second RNTI are associated with multicast.
The method of claim 1, further comprising:

Stop a second timer, the second timer is a retransmission timer corresponding to the DRX associated with the first RNTI, the second timer is associated with the first HARQ process; and/or

Stop a third timer, the third timer is a retransmission timer corresponding to the DRX associated with unicast, and the third timer is associated with the first HARQ process.
The method according to claim 1 or 2, characterized in that, the method further includes:

Receive second control information transmitted in a multicast manner, the second control information is used to schedule second data, the second control information and/or the second data are associated with the second RNTI, the The second control information and/or the second data are associated with the first HARQ process; or,

receiving second data on a second resource, the second resource and/or the second data being associated with the second RNTI, the second data being associated with the first HARQ process;

Start or restart a fourth timer, the fourth timer is a round-trip time RTT timer corresponding to the DRX associated with the second RNTI, the fourth timer is associated with the first HARQ process; and/ or,

Start or restart a fifth timer, the fifth timer is an RTT timer corresponding to the DRX associated with unicast, and the fifth timer is associated with the first HARQ process.
The method of claim 3, further comprising:

The fourth timer times out and the second data reception or decoding fails, start or restart the first timer; and/or,

If the fifth timer times out and the second data reception or decoding fails, the third timer is started or restarted.
The method according to any one of claims 1-4, characterized in that the method further includes:

Receive third control information transmitted in a multicast manner, the third control information is used to schedule third data, the third control information and/or the third data are associated with the first RNTI, the The third control information and/or the third data are associated with the first HARQ process; or,

receiving third data on a third resource, the third resource and/or the third data being associated with the first RNTI, the third data being associated with the first HARQ process;

Start or restart a sixth timer, the sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI, the sixth timer is associated with the first HARQ process; and/or,

Start or restart a fifth timer, the fifth timer is an RTT timer corresponding to the DRX associated with unicast, and the fifth timer is associated with the first HARQ process.
The method of claim 5, further comprising:

The sixth timer times out and the third data reception or decoding fails, start or restart the second timer; and/or,

When the fifth timer times out and the third data reception or decoding fails, the third timer is started or restarted.
The method according to any one of claims 1-6, characterized in that the method further includes:

Receive fourth control information transmitted in a unicast manner, the fourth control information being used to schedule fourth data, the fourth control information and/or the fourth data being associated with the first HARQ process; or ,

Receive fourth data on a fourth resource, the fourth resource being a configuration resource corresponding to unicast, and the fourth data being associated with the first HARQ process;

Start or restart a fifth timer, the fifth timer is an RTT timer corresponding to the DRX associated with unicast, and the fifth timer is associated with the first HARQ process.
The method of claim 7, further comprising:

If the fifth timer times out and the fourth data fails to be received or decoded, the third timer is started or restarted.
The method according to any one of claims 1 to 8, characterized in that the first control information transmitted in a multicast manner includes: the first control information scrambled by the first RNTI.
The method according to any one of claims 1 to 9, characterized in that the first RNTI includes a first group of wireless network temporary identifiers G-RNTI and/or a first group of configuration and scheduling wireless network temporary identifiers G-CS- RNTI, and/or,

The second RNTI includes a second G-RNTI and/or a second G-CS-RNTI.
A communication device, characterized by including:

A transceiver unit, configured to receive first control information transmitted in a multicast manner, where the first control information is used to schedule first data, where the first control information and/or the first data are temporarily connected to the first wireless network. The identification RNTI is associated, and the first control information and/or the first data is associated with the first hybrid automatic repeat request HARQ process; or,

A transceiver unit configured to receive first data on a first resource, the first resource and/or the first data are associated with a first RNTI, and the first data is associated with the first HARQ process;

A processing unit configured to stop a first timer, the first timer being a retransmission timer corresponding to the discontinuous reception DRX associated with the second RNTI, the first timer being associated with the first HARQ process ;

Wherein, the first RNTI and the second RNTI are associated with multicast.
The device according to claim 11, characterized in that the processing unit is also used for:

Stop a second timer, the second timer is a retransmission timer corresponding to the DRX associated with the first RNTI, the second timer is associated with the first HARQ process; and/or

Stop a third timer, the third timer is a retransmission timer corresponding to the DRX associated with unicast, and the third timer is associated with the first HARQ process.
The device according to claim 11 or 12, characterized in that the transceiver unit is also used to receive second control information transmitted in a multicast manner, the second control information is used to schedule the second data, and the Second control information and/or the second data are associated with the second RNTI, and the second control information and/or the second data are associated with the first HARQ process; or,

The transceiver unit is further configured to receive second data on a second resource, the second resource and/or the second data are associated with the second RNTI, and the second data is associated with the first HARQ process associated;

The processing unit is also configured to start or restart a fourth timer. The fourth timer is a round-trip time RTT timer corresponding to the DRX associated with the second RNTI. The fourth timer is related to the third timer. A HARQ process is associated; and/or,

The processing unit is also configured to start or restart a fifth timer. The fifth timer is a DRX pair associated with unicast. Corresponding RTT timer, the fifth timer is associated with the first HARQ process.
The device according to claim 13, characterized in that the processing unit is also used to:

The fourth timer times out and the second data reception or decoding fails, start or restart the first timer; and/or,

If the fifth timer times out and the second data reception or decoding fails, the third timer is started or restarted.
The device according to any one of claims 11 to 14, characterized in that the transceiver unit is also used to receive third control information transmitted in a multicast manner, and the third control information is used to schedule third data. , the third control information and/or the third data are associated with the first RNTI, and the third control information and/or the third data are associated with the first HARQ process; or,

The transceiver unit is further configured to receive third data on a third resource, the third resource and/or the third data are associated with the first RNTI, and the third data is associated with the first RNTI. HARQ process associated;

The processing unit is also configured to start or restart a sixth timer. The sixth timer is an RTT timer corresponding to the DRX associated with the first RNTI. The sixth timer is related to the first HARQ process associated; and/or,

The processing unit is also configured to start or restart a fifth timer. The fifth timer is an RTT timer corresponding to the DRX associated with unicast. The fifth timer is associated with the first HARQ process. .
The device according to claim 15, characterized in that the processing unit is also used to:

The sixth timer times out and the third data reception or decoding fails, start or restart the second timer; and/or,

When the fifth timer times out and the third data reception or decoding fails, the third timer is started or restarted.
The device according to any one of claims 11 to 16, characterized in that the transceiver unit is also used to receive fourth control information transmitted in a unicast manner, and the fourth control information is used to schedule fourth data. , the fourth control information and/or the fourth data are associated with the first HARQ process; or,

The transceiver unit is further configured to receive fourth data on a fourth resource, where the fourth resource is a configuration resource corresponding to unicast, and the fourth data is associated with the first HARQ process;

The processing unit is also configured to start or restart a fifth timer. The fifth timer is an RTT timer corresponding to the DRX associated with unicast. The fifth timer is associated with the first HARQ process. .
The device according to claim 17, wherein the processing unit is further configured to start or restart the third timer when the fifth timer times out and the fourth data fails to be received or decoded.
The device according to any one of claims 11 to 18, wherein the first control information transmitted in a multicast manner includes: the first control information scrambled by the first RNTI.
The device according to any one of claims 11 to 19, characterized in that the first RNTI includes a first group of wireless network temporary identifiers G-RNTI and/or a first group of configuration scheduling wireless network temporary identifiers G-CS- RNTI, and/or,

The second RNTI includes a second G-RNTI and/or a second G-CS-RNTI.
A communication device, characterized in that it includes a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device executes The method according to any one of claims 1-10.
A computer-readable storage medium, characterized in that a computer program or computer instructions are stored in the computer-readable storage medium. When the computer program or computer instructions are executed, any one of claims 1-10 is implemented. the method described.
A computer program product, characterized in that the computer program product includes computer program code, and when the computer program code is run, the method according to any one of claims 1-10 is implemented.