CN117676472A

CN117676472A - Communication method and device

Info

Publication number: CN117676472A
Application number: CN202210993583.7A
Authority: CN
Inventors: 刘南南; 常俊仁
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-08-09
Filing date: 2022-08-18
Publication date: 2024-03-08

Abstract

The application provides a communication method and device. The method is applied to the terminal equipment and comprises the following steps: satisfying a first condition, performing one or more of: controlling discontinuous reception DRX associated with multicast to be in an active time; stopping the first timer or shortening the residual running duration of the first timer, wherein the first timer is an inactive timer corresponding to the DRX associated with unicast. The first condition includes: the first data comprises a first logical channel identification LCID and no first downlink control information DCI is received. The first data is scheduled by a second DCI, which is transmitted in a unicast manner. The first LCID is an identification of a first multicast broadcast service traffic channel MTCH, the first DCI is transmitted in a multicast manner, and the first DCI is used to schedule first data. The method is beneficial to the terminal equipment to receive DCI transmitted in a multicast mode, improves the communication reliability, reduces the communication time delay and/or reduces the power consumption of the terminal equipment.

Description

Communication method and device

The present application claims priority from the chinese patent application filed at 2022, 8 and 9, filed with the chinese national intellectual property agency, application number 202210952507.1, application name "a communication method and apparatus", the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a communications method and apparatus.

Background

Multicast and broadcast services (multicast and broadcast services, MBS) in the new air interface (NR) system support multicast and broadcast. Multicast may support point-to-point (PTP) transmission and point-to-multipoint (PTM) transmission. In addition, the multicast PTM transmission supports a hybrid automatic repeat request (hybrid automatic repeat request, HARQ) feedback mechanism. The network device sends the primary downlink control information (downlink control information, DCI) and/or data by using a PTM transmission method, and if the terminal device receives the DCI but does not successfully decode the DCI scheduled data, the terminal device may feedback a Negative-acknowledgement (NACK) to the network device. The network device may perform HARQ retransmission by using a PTM transmission method or a PTP transmission method.

For a multicast transmission, if the terminal device does not receive the DCI transmitted in the PTM transmission mode, and the network device performs HARQ retransmission to the terminal device in the PTP transmission mode, the terminal device may misjudge the DCI and/or data transmitted in the PTP transmission mode as unicast transmission or transmission of other multicast.

In this case, how to handle the terminal device is one of the problems to be studied.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which are beneficial to terminal equipment to receive DCI transmitted in a multicast mode, improve communication reliability, reduce communication delay and/or reduce power consumption of the terminal equipment.

In a first aspect, embodiments of the present application provide a communication method that may be applied to a terminal device (e.g., a device or a chip of a terminal device). The method comprises the following steps: satisfying a first condition, performing one or more of: controlling discontinuous reception DRX associated with multicast to be in an active time; stopping the first timer or shortening the remaining operation time of the first timer.

The first timer is an inactive timer corresponding to the DRX associated with unicast, i.e., the first timer is DRX-inactivity timer. The first condition includes: the first data comprises a first logical channel identification LCID and no first downlink control information DCI is received. The first data is scheduled by a second DCI, which is transmitted in a unicast manner. The first LCID is an identification of a first multicast broadcast service channel MTCH, the first DCI is transmitted in a multicast manner, and the first DCI is used for scheduling the first data.

In the embodiment of the present application, the terminal device determines that the first data is multicast retransmission data by satisfying the first condition. Thus, the second DCI scheduling the first data and transmitted in unicast is scheduling retransmission of the multicast, and the terminal device may perform one or more of the above.

The first condition is met, the terminal equipment executes the control of the DRX associated with the multicast to be in the active time, and the situation that the inactivity timer corresponding to the DRX associated with the multicast is not started or restarted due to the fact that the first DCI transmitted in the multicast mode is not received can be avoided. Therefore, DRX associated with multicast is not in active time, and the subsequent terminal equipment cannot receive DCI transmitted in a multicast mode. Therefore, the method is beneficial to the terminal equipment to receive the DCI transmitted by the multicast mode, improves the communication reliability and reduces the communication time delay.

The first condition is met, the terminal device executes stopping of the first timer or shortening of the residual operation time of the first timer, so that DCI (second DCI) which is retransmitted in a multicast mode at this time can be avoided, and when the DCI is judged to be DCI which is retransmitted in a unicast mode at this time, the excessive power consumption caused by starting or restarting the first timer can be avoided, and the power consumption or the power consumption of the terminal device can be saved.

The first condition is met, the terminal equipment performs control on the DRX associated with multicast to be in the active time, and stops the first timer or shortens the residual operation time of the first timer, so that the situation that the first DCI transmitted in the multicast mode is not received and the DCI transmitted in the multicast mode cannot be received afterwards can be avoided, namely the terminal equipment is facilitated to receive the DCI transmitted in the multicast mode, the communication reliability is improved, the communication time delay is reduced, and when the second DCI transmitted in the unicast mode is misjudged to be the DCI transmitted for the first time in the unicast mode, the power consumption or the power consumption of the terminal equipment can be saved due to the fact that the first timer is started or restarted.

In an alternative embodiment, controlling multicast associated discontinuous reception DRX to be active time includes: starting or restarting one or more of the following timers: a second timer, a third timer and a fourth timer.

The second timer is an inactive timer corresponding to the DRX associated with the multicast, i.e., the second timer is DRX-inactivity timer ptm. The third timer is a duration timer corresponding to DRX associated with multicast, i.e. the second timer is DRX-onduration timer ptm. The fourth timer is a retransmission timer corresponding to the DRX associated with the multicast, and is a downlink retransmission timer corresponding to the DRX associated with the multicast, namely the fourth timer is DRX-retransmission TimerDL-PTM.

It can be seen that the terminal device can cause multicast-associated DRX to be active time by starting or restarting one or more of the second timer, the third timer, and the fourth timer. Therefore, even if the terminal equipment does not receive the DCI (i.e. the first DCI) originally transmitted in the multicast mode, the subsequent terminal equipment can still receive other DCIs transmitted in the multicast mode.

In an alternative embodiment, if the discontinuous reception DRX performing control multicast association is active, the first condition further comprises any one or more of: multicast-associated DRX is not active time; after receiving the second DCI, the second timer is not started or restarted; or after receiving the third DCI, the second timer is not started or restarted; the third DCI is used to schedule the first data, the third DCI preceding the second DCI.

As can be seen, when the first data includes the first LCID and the first DCI transmitted in the multicast manner is not received, if the terminal device determines that the DRX associated with the multicast is not in the active time, it indicates that the terminal device does not start or restart the inactivity timer corresponding to the DRX associated with the multicast due to the fact that the first DCI transmitted in the multicast manner is not received, so that the DRX associated with the multicast is not in the active time. In this case, in order to enable the terminal device to subsequently receive other DCI transmitted in the multicast manner, the terminal device controls the DRX associated with the multicast to be in an active time.

In an alternative embodiment, if the discontinuous reception DRX performing control multicast association is active, the first condition further comprises: the second duration is less than the configuration duration of the second timer, and the second duration is a duration from the terminal equipment to successfully decode the first data after receiving the second DCI or the third DCI.

Optionally, if the terminal device receives the second DCI, the second timer is not started or restarted, which indicates that the terminal device does not receive other DCI that is initially transmitted through multicast after receiving the second DCI, so that the inactivity timer corresponding to the DRX associated with multicast is not started or restarted yet. Therefore, in this case, the terminal device also needs to control the DRX associated with the multicast to be active, so that other DCI transmitted by the multicast mode may be received later.

Optionally, if the terminal device receives the third DCI, the second timer is not started or restarted, and the third DCI is the first DCI for PTP retransmission that is scheduled for the first data and received by the terminal device, which indicates that after the terminal device receives the first DCI for PTP retransmission, other DCIs for initial transmission by multicast are not received, so that the inactivity timer corresponding to the DRX associated with multicast is not started or restarted. Therefore, in this case, in order for the terminal device to subsequently receive other DCI transmitted by multicast, the terminal device also needs to control the DRX associated with multicast to be in active time.

Optionally, when the terminal device performs discontinuous reception DRX for controlling multicast association is at an active time, the first condition further includes multiple of the three items, so that the terminal device may subsequently receive other DCI transmitted in a multicast manner.

In an alternative embodiment, if the stopping the first timer is performed, the first condition further comprises: receiving second DCI or third DCI, wherein the first timer is not operated; and/or; after receiving the second DCI or the third DCI, the first timer is not started or restarted.

And when the terminal equipment receives the second DCI or the third DCI and the first timer does not run, the terminal is indicated that the terminal does not receive the DCI transmitted in the unicast mode before receiving the second DCI or the third DCI. After receiving the second DCI or the third DCI, the terminal device does not start or restart the first timer, which indicates that after receiving the second DCI or the third DCI, the terminal device does not receive other DCI transmitted in the unicast mode.

Therefore, if the first data includes the first LCID, the terminal device does not receive the first DCI transmitted in the multicast manner, and receives the second DCI or the third DCI, the first timer is not operated; and/or; after receiving the second DCI or the third DCI, the first timer is not started or restarted. When the terminal equipment receives the first data, the operation of the first timer is caused by misjudging the second DCI or the third DCI as the DCI transmitted in the unicast mode when the initial transmission is performed, so that the first timer is stopped, and the redundant power consumption caused by the operation of the first timer is reduced.

In another alternative embodiment, if shortening the remaining operation duration of the first timer is performed, the first condition further includes: receiving second DCI or third DCI, and running a first timer; and/or after receiving the second DCI or the third DCI, the first timer is not started or restarted.

The terminal equipment receives the second DCI or the third DCI, and the first timer runs, which indicates that before the terminal equipment receives the second DCI or the third DCI, the first timer is started or restarted due to the fact that other DCIs which are initially transmitted in a unicast mode are received before the terminal equipment receives the second DCI or the third DCI. Therefore, if the terminal device determines that the first data is multicast retransmission data by satisfying the first condition, that is, determines that the second DCI or the third DCI for scheduling the first data is multicast DCI for the present retransmission, and receives the second DCI or the third DCI, the first timer operates. Then, the operation of the first timer is that the terminal device starts or restarts the second DCI or the third DCI by misjudging the first DCI transmitted in the unicast mode. In this way, the terminal device needs to shorten the remaining operation duration of the first timer, and ensure the remaining operation duration of the first timer when the first timer is started or restarted before receiving the second DCI or the third DCI, so that the redundant power consumption caused by starting or restarting the first timer can be reduced.

After receiving the second DCI or the third DCI, the terminal device does not start or restart the first timer, which indicates that after receiving the second DCI or the third DCI, the terminal device does not start or restart the first timer due to receiving other unicast transmissions. Thus, the first timer is started or restarted due to the reception of the second DCI or the third DCI, which is actually a multicast retransmission, and the first timer should not be started or restarted. Thus, the terminal device needs to shorten the remaining operation time of the first timer.

In an alternative embodiment, the second DCI is transmitted in a unicast mode and includes: the second DCI is scrambled by a cell-radio network temporary identifier C-RNTI. It can be seen that the second DCI is C-RNTI scrambled, equivalently to the second DCI being transmitted in unicast.

In an alternative embodiment, the first DCI is transmitted by multicast mode and includes: the first DCI is scrambled by a first RNTI. Wherein the first RNTI is used for one or more of: the method is used for multicasting, scheduling multicast dynamic resources and scheduling retransmission resources of the multicast dynamic resources.

In an alternative embodiment, the first LCID is associated with a first RNTI and/or the multicast associated DRX is associated with the first RNTI. Wherein the first RNTI is used for one or more of: the method is used for multicasting, scheduling multicast dynamic resources and scheduling retransmission resources of the multicast dynamic resources.

In a second aspect, the present application also provides a communication device. The communication device has a function of realizing part or all of the terminal device described in the first aspect. For example, the function of the communication device may be provided in some or all of the embodiments of the terminal device described in the first aspect of the present application, or may be provided to implement the functions of any of the embodiments of the present application alone. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one possible design, the communication device may include a processing unit and a communication unit in a structure, where the processing unit is configured to support the communication device to perform the corresponding functions in the method. The communication unit is used for supporting communication between the communication device and other communication devices. The communication device may further comprise a memory unit for coupling with the processing unit and the communication unit, which holds the necessary program instructions and data of the communication device.

In one embodiment, the communication device includes: a processing unit and a communication unit; the communication unit is used for carrying out data/signaling transceiving; a processing unit for:

Satisfying a first condition, performing one or more of:

controlling discontinuous reception DRX associated with multicast to be in an active time;

stopping a first timer or shortening the residual operation duration of the first timer, wherein the first timer is an inactive timer corresponding to the DRX associated with unicast;

wherein the first condition includes: the first data comprises a first logic channel identification LCID, and no first downlink control information DCI is received;

the first data is scheduled by a second DCI, the second DCI is transmitted in a unicast mode, the first LCID is an identification of a first multicast broadcast service channel (MTCH), the first DCI is transmitted in a multicast mode, and the first DCI is used for scheduling the first data.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the relevant content of the first aspect, which is not described in detail herein.

As an example, the communication unit may be a transceiver or a communication interface, the storage unit may be a memory, and the processing unit may be a processor.

In one embodiment, the communication device includes: a processor and a transceiver; the transceiver is used for carrying out data/signaling transceiving; a processor for:

Satisfying a first condition, performing one or more of:

In addition, in this aspect, other optional embodiments of the uplink communication device may be referred to in the relevant content of the first aspect, which is not described in detail herein.

In another embodiment, the communication device is a chip or a system-on-chip. The processing unit may also be embodied as a processing circuit or logic circuit; the transceiver unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or system-on-chip.

In an implementation, a processor may be used to perform, for example but not limited to, baseband related processing, and a transceiver may be used to perform, for example but not limited to, radio frequency transceiving. The above devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. For example, the processor may be further divided into an analog baseband processor and a digital baseband processor. Wherein the analog baseband processor may be integrated on the same chip as the transceiver and the digital baseband processor may be provided on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, the digital baseband processor may be integrated on the same chip as a variety of application processors (e.g., without limitation, graphics processors, multimedia processors, etc.). Such a chip may be referred to as a system on a chip (SoC). Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The implementation form of the device is not limited in the embodiment of the application.

In a third aspect, the present application also provides a processor for performing the above-described methods. In performing these methods, the process of transmitting the above information and receiving the above information in the above methods may be understood as a process of outputting the above information by a processor and a process of receiving the above information inputted by the processor. When outputting the information, the processor outputs the information to the transceiver for transmission by the transceiver. This information, after being output by the processor, may also require additional processing before reaching the transceiver. Similarly, when the processor receives the input of the information, the transceiver receives the information and inputs it to the processor. Further, after the transceiver receives the information, the information may need to be further processed before being input to the processor.

With respect to operations such as transmission and reception, etc., related to the processor, unless specifically stated otherwise, or if there is no conflict with the actual role or inherent logic of the operations in the related description, the operations such as output and reception, input, etc., of the processor may be understood more generally, rather than the operations such as transmission and reception, which are directly performed by the radio frequency circuit and the antenna.

In implementation, the processor may be a processor dedicated to performing the methods, or may be a processor that executes computer instructions in a memory to perform the methods, e.g., a general purpose processor. The memory may be a non-transitory (non-transitory) memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of the memory and the manner of providing the memory and the processor are not limited in this embodiment of the present application.

In a fourth aspect, the present application also provides a communication system comprising one or more network devices, and one or more terminal devices. In another possible design, the system may also include other devices that interact with the network device, the terminal device.

In a fifth aspect, the present application provides a computer readable storage medium storing instructions which, when executed by a computer, implement a method according to any one of the first aspects.

In a sixth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, implement the method of any one of the first aspects above.

In a seventh aspect, the present application provides a chip system, the chip system comprising a processor and an interface, the interface being configured to obtain a program or an instruction, and the processor being configured to invoke the program or the instruction to implement or support the terminal device to implement the functionality involved in the first aspect. For example, at least one of the data and information involved in the above method is determined or processed. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In an eighth aspect, the present application provides a communications apparatus comprising a processor for executing a computer program or executable instructions stored in a memory, which when executed causes the apparatus to perform a method as in each possible implementation of the first aspect.

In one possible implementation, the processor and memory are integrated together;

in another possible implementation, the memory is located outside the communication device.

The advantages of the second to eighth aspects may refer to those of the first aspect, and are not described here again.

Drawings

Fig. 1 is a schematic system structure of a communication system according to an embodiment of the present application;

FIG. 2 is a schematic illustration of a discontinuous reception cycle provided by an embodiment of the present application;

fig. 3a is a schematic diagram of channel mapping provided in an embodiment of the present application;

fig. 3b is an entity schematic diagram of a terminal device according to an embodiment of the present application;

FIG. 4a is a schematic diagram of a transmission provided in an embodiment of the present application;

FIG. 4b is another transmission schematic provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of yet another transmission provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of yet another transmission provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a communication method according to an embodiment of the present application;

FIG. 8 is a schematic diagram of yet another transmission provided by an embodiment of the present application;

FIG. 9 is a schematic illustration of a communication provided by an embodiment of the present application;

FIG. 10 is a flow chart of another communication method according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application.

Wherein the terms "first" and "second" and the like in the description, claims and drawings of the present application are used for distinguishing between different objects and not for describing a particular sequential order. The terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be understood that in this application, "plurality" means two or more. And/or, for describing the association relationship of the association object, means that three relationships may exist. For example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. The terms "…" and "if" refer to a process that is performed under an objective condition, and are not intended to be limiting, nor are they intended to require a judgment in terms of implementation, nor are they intended to be limiting.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion that may be readily understood.

A communication system.

In order to better understand the communication method disclosed in the embodiments of the present application, a communication system to which the embodiments of the present application are applicable will be described.

The embodiment of the application can be applied to a fifth generation mobile communication (5th generation mobile communication,5G) system, a sixth generation mobile communication (6th generation mobile communication,6G) system, a next generation wireless access network (next generation radio access networks, NG-RAN), satellite communication, short-range wireless communication systems and the like, and the system architecture is shown in fig. 1. A wireless communication system may include one or more network devices and one or more terminal devices. Wireless communication systems may also perform point-to-point communications, such as communication between multiple end devices.

It is to be appreciated that the wireless communication systems mentioned in embodiments of the present application include, but are not limited to: narrowband internet of things (NB-IoT) system, long term evolution (long term evolution, LTE), three major application scenarios of 5G/6G mobile communication system: enhanced mobile broadband (enhanced mobile broadband, emmbb), ultra-reliable low latency communication (ultra reliable low latency communication, URLLC), and mass machine type communication (massive machine type of communication, mctc), wireless fidelity (wireless fidelity, wiFi) systems, or 5G later mobile communication systems, etc.

In the embodiment of the present application, the network device is a device with a wireless transceiver function, and is used for communicating with the terminal device, and may be an evolved Node B (eNB or eNodeB) in LTE, or a base station in a 5G/6G network or a base station in a public land mobile network (public land mobile network, PLMN) that evolves in the future, a broadband network service gateway (broadband network gateway, BNG), a convergence switch, or a non-third generation partnership project (3rd generation partnership project,3GPP) access device, and so on. Optionally, the network device in the embodiments of the present application may include various forms of base stations, for example: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, devices that implement base station functions in the future, access nodes in WiFi systems, transmission and reception points (transmitting and receiving point, TRP), transmission points (transmitting point, TP), mobile switching centers (mobile switching centers, D2D), devices that assume base station functions in vehicle-to-device (V2X), machine-to-machine (M2M) communications, and the like, which are not particularly limited in this embodiment of the present application.

The network device can perform communication interaction with the core network device, and provide communication services for the terminal device. The core network device is, for example, a device in a 5G network Core Network (CN). The core network is used as a bearing network to provide an interface to the data network, and provides communication connection, authentication, management, policy control, bearing of data service and the like for the terminal.

The terminal device according to the embodiments of the present application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, which have wireless communication functions. The terminal device may also be referred to as a terminal. The terminal device may also refer to a User Equipment (UE), an access terminal, a subscriber unit (subscriber unit), a user agent, a cellular phone (cell phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (handset), a laptop computer (laptop computer), a machine type communication (machine type communication, MTC) terminal, a communication device carried on an aerial plane, a wearable device, an unmanned aerial vehicle, a robot, a terminal in a device-to-device communication (D2D), a terminal in a vehicle-to-all (vehicle to everything, V2X), a Virtual Reality (VR) terminal device, a wireless terminal in an augmented reality (augmented reality, AR) terminal device, a wireless terminal in an industrial control (industrial control), a wireless terminal in a wireless driver (self-aid), a wireless terminal in a remote medical (smart) network, a wireless terminal in a smart network (smart) of a smart device, a smart device in a future communication terminal, a smart device in a smart network of a smart device, or the like.

And II, related concepts.

For better understanding of the communication method disclosed in the embodiments of the present application, the related concepts related to the embodiments of the present application are briefly described.

1. Multicast and broadcast services (multicast and broadcast services, MBS).

The broadcast multicast service mentioned in the embodiment of the present application may be an MBS in an NR system. MBS is introduced by 3GPP for effectively utilizing mobile communication network resources, and provides a point-to-multipoint service in which one data source transmits data to a plurality of users in a mobile communication network, so as to implement network resource sharing and improve resource utilization, in particular, air interface resources. NR MBS supports multicast and broadcast.

2. Multicast and unicast.

Multicasting may include any one or more of the following: multimedia broadcast and multicast services (multimedia broadcast multicast service, MBMS) or broadcast in MBS; multicast in MBMS or MBS; multicast in MBMS or MBS; multicasting in V2X; multicast in V2X; broadcast in V2X (broadcast); multicast or multicasting (multicast); multicast (groupcast); and (5) broadcasting.

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

The data corresponding to the multicast service may be referred to as multicast data.

Unicast may include any one or more of the following: unicast in V2X; unicast (unicasting). Unicast is understood to mean unicast transmission.

Multicast services may also be understood as multicast sessions or MBS sessions.

The term "multicast" in the embodiments of the present application may also be replaced by the term "multicast". Correspondingly, the multicast service can be replaced by the multicast service.

Multicasting may provide the same service and/or the same content data to a group/groups of terminal devices simultaneously.

For example, multicasting may be for a particular group of terminal devices, which may need to perform a "group joining process".

Correspondingly, unicast is understood to mean that the same service and/or the same content data are provided to one terminal device at the same time. Unicast can be understood as: for one data, if it is to be transmitted to a plurality of devices, it is necessary to transmit the data separately to each device.

3. Multicast and unicast transmission modes.

And 3.1, a multicast transmission mode.

For transmission of multicast traffic/data, or for transmission of data related to a multicast broadcast service traffic channel (MBS traffic channel, MTCH) corresponding to multicast, there may be any one or more of the following transmission modes: a multicast dynamic transmission mode and/or a multicast configuration transmission mode.

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

PTP transmission mode: in this transmission mode, the transmitting end transmits a piece of data to a receiving end. For example, a physical downlink control channel (physical uplink control channel, PDCCH) scrambled (by the network device with a UE-specific radio network temporary identifier (radio network temporary identity, RNTI) may also be referred to as a c+c transmission scheme, scheduling a physical downlink shared channel (physical downlink shared channel, PDSCH) for the terminal device or a pdsch.ptp transmission scheme scrambled (by the network device) with a UE-specific RNTI for the terminal device.

For example, the UE-specific RNTI may include any one or more of: a cell radio network temporary identifier (cell-RNTI, C-RNTI), a configured scheduling RNTI (configured scheduling RNTI, CS-RNTI), a second RNTI.

PTM transmission scheme: the transmitting end can transmit one data to a plurality of receiving ends through a PTM transmission mode.

For example, the network device schedules PDSCH for the terminal device with the common RNTI-scrambled PDCCH or schedules common RNTI-scrambled PDSCH for the terminal device. Or it may be understood that the network side scrambles a DCI through a common RNTI, the DCI is used to schedule a data scrambled through a common RNTI, in which case a plurality of terminal devices receive the same DCI and the data received by the plurality of terminal devices are the same. The PTM transmission scheme may also be referred to as g+g transmission scheme.

For example, the common RNTI may include any one or more of the following: a group radio network temporary identifier (G-RNTI), a group configuration scheduling radio network temporary identifier (group configured scheduling RNTI, G-CS-RNTI), a first RNTI.

The multicast configuration transmission mode can be understood as: the network device transmits data/multicast data to the terminal device on the multicast configuration resource; or, the terminal device receives the data/multicast data sent by the network device on the multicast configuration resource.

The multicast configuration transmission mode may also be referred to as a multicast semi-static transmission mode.

The multicast configuration resources may also be referred to as multicast semi-persistent scheduling (SPS) resources.

For the transmission of the data related to the MTCH corresponding to the multicast, for convenience of description, the data may be collectively referred to as: multicast MTCH related transmissions.

And 3.2, a unicast transmission mode.

For transmission of unicast traffic (or unicast data) and/or transmission of data related to a dedicated traffic channel (dedicate traffic channel, DTCH) corresponding to multicast, any one or more of the following transmission modes may be adopted: unicast dynamic transmission mode and/or unicast configuration transmission mode.

The unicast dynamic transmission scheme may also be referred to as PTP transmission scheme.

Unicast dynamic transmission mode: in this transmission mode, the transmitting end transmits a piece of data to a receiving end. For example, the network device schedules PDSCH for the terminal device with the UE-specific RNTI-scrambled PDCCH or the UE-specific RNTI-scrambled PDSCH for the terminal device.

The unicast configuration transmission mode can be understood as: the network equipment transmits data to the terminal equipment on unicast configuration resources; or, the terminal device receives the data sent by the network device on the unicast configuration resource.

The unicast configured transmission scheme may also be referred to as a unicast semi-static transmission scheme.

Unicast configuration resources may also be referred to as unicast SPS resources.

For the transmission of unicast traffic (or unicast data) and/or the transmission of data related to a dedicated traffic channel (dedicate traffic channel, DTCH) corresponding to multicast, for convenience of description, may be collectively referred to as: unicast transmission. For example, unicast new transmissions, or unicast retransmissions.

4. Discontinuous reception (discontinuous reception, DRX).

In a wireless communication system, in order to further save power consumption of a terminal device on the premise of ensuring that data can be effectively transmitted, a DRX function is introduced to control the behavior of the terminal device in monitoring PDCCH. Under the condition that the network equipment configures the DRX function for the terminal equipment, the terminal equipment can enter a sleep state at certain moments, so that the terminal equipment does not need to monitor the PDCCH continuously, and when the PDCCH is required to be monitored, the terminal equipment can wake up from the sleep state, thereby saving the power consumption of the terminal equipment to a certain extent.

The following will briefly introduce DRX in connection with fig. 2: fig. 2 is a schematic diagram of a DRX cycle provided in an embodiment of the present application. As shown in fig. 2, one DRX cycle (DRX cycle) may include one duration (e.g., on-duration) or a wake-up time (e.g., on-duration) and one sleep time (e.g., opportunity for DRX). And waiting for the duration of receiving the PDCCH after the terminal equipment is awakened in the duration period, and monitoring the PDCCH by the terminal equipment in the duration period. If the terminal device can successfully decode the PDCCH, the terminal device can remain in an awake state or extend an activation time. In the sleep time period, the sleep time of the terminal equipment is the sleep time of the terminal equipment, and the terminal equipment does not need to monitor the PDCCH in the sleep time period so as to save power consumption. It can be understood that the longer the sleep time of the terminal device, the lower the power consumption of the terminal device, but correspondingly, the delay of the terminal device for service transmission increases.

The DRX functionality of the terminal device may be configured by the network device. It should be noted that, even if the network device configures the DRX function for the terminal device, the terminal device may monitor the PDCCH according to the requirements of other media access control (medium access control, MAC) layer procedures, that is, when the other MAC layer procedures require the terminal device to keep monitoring the PDCCH, the terminal device needs to continuously monitor the PDCCH regardless of the DRX state at this time.

4.1, unicast DRX.

In the case where no DRX group is configured (or, in R15), the DRX parameters are configured by the network device for each terminal device's MAC entity or for each terminal device, i.e. one terminal device's MAC entity uses a set of DRX parameters.

In the context of carrier aggregation (carrier aggregation, CA), the terminal device uses the same set of DRX parameters for all active cells and runs a set of DRX.

In a multi-mode dual connection (MR-DC) scenario, a Master Node (MN) and a Secondary Node (SN) respectively correspond to MAC entities of one terminal device. Thus, the terminal device has two independent sets of DRX parameters for MN and SN, and runs two sets of DRX. That is, the terminal device runs a set of DRX for all active serving cells within the master cell group (master cell group, MCG) using a set of DRX parameters; another set of DRX parameters is used for all active serving cells within the secondary cell group (secondary cell group, SCG), which is run.

In the case where the DRX group is not configured, the activation time of DRX may include any one or more of the following: run time of drx-onDurationTimer; run time of drx-InactivityTimer; run time of drx-retransmission timerdl; run time of drx-retransmission timer ul; run time of drx-retransmission timer SL; a scheduling request (scheduling request, SR) is sent on a physical uplink control channel (physical uplink control channel, PUCCH) and the SR is waiting for processing; after the non-contention random access procedure successfully receives the random access response (random access response, RAR) (i.e., after the non-contention Random Access (RA) is successful), a PDCCH scrambled with the C-RNTI indicating a new transmission has not been received, and so on.

The network device controls DRX operation by configuring any one or more of the following parameters with a radio resource control (Radio Resource Control, RRC) message:

drx-onDurationTimer: a period of time at the beginning of the DRX cycle. The starting or restarting position of the drx-onduration timer can be calculated according to parameters configured by the base station and a formula specified by a protocol.

drx-InactivityTimer: a period of time after a PDCCH timing (occalation) of an uplink or downlink new transmission is indicated. For example, the terminal device receives a PDCCH (e.g., C-RNTI or CS-RNTI scrambled PDCCH), indicates a new uplink or downlink transmission (i.e., a new transmission schedule), and starts or restarts the drx-InactivityTimer.

drx-retransmission timer DL: until a maximum duration of a Downlink (DL) retransmission is received. For example, drx-HARQ-RTT-timertul times out and the data is not successfully decoded, drx-retransmission timerdl is started or restarted.

drx-retransmission timer UL: until a maximum duration of grant for Uplink (UL) retransmission is received. For example, in the first symbol after the drx-HARQ-RTT-timer ul timeout, drx-retransmission timer ul is started or restarted for the corresponding HARQ process.

drx-HARQ-RTT-TimerDL: the minimum duration before DL allocation of the HARQ retransmission expected by the MAC entity or the minimum duration before DL allocation of the HARQ retransmission expected by the MAC entity is received. For example, the terminal device receives a PDCCH (e.g., a C-RNTI or CS-RNTI scrambled PDCCH), indicates that there is a downlink transmission, or the terminal device receives data in a configured downlink allocation (e.g., unicast associated SPS resources), and starts or restarts drx-HARQ-RTT-TimerDL after feedback. Wherein RTT represents Round Trip Time (Round Trip Time).

drx-HARQ-RTT-TimerUL: the minimum duration before UL HARQ retransmission grant expected by the MAC entity or the minimum duration before UL HARQ retransmission grant expected by the MAC entity is received. For example, the terminal device sends a MAC protocol data unit (protocol data unit, PDU) in a configured uplink grant (e.g., unicast associated SPS resource), or the terminal device receives PDCCH, indicates UL transmission, starts or restarts drx-HARQ-RTT-TimerUL.

drx-retransmission timer SL: until a maximum duration of grant for a Sidelink (SL) retransmission is received.

drx-HARQ-RTT-TimerSL: the minimum duration before a desired SL retransmission grant or the minimum duration before a desired one is received.

Unicast DRX adds functionality to the DRX group compared to R15 in the R16 standard protocol.

A brief description of a DRX group (group) will be given below.

DRX group: within one MAC entity, different DRX groups are distinguished for different frequency ranges. For example, DRX groups are distinguished for Frequency Ranges (FR) 1 and FR 2. I.e. for cells on FR2, the concept of a secondary DRX group is introduced. Each cell belongs to one DRX group.

For cell group/DRX group of FR1 and FR2 there is a set of parameters of DRX-ondurationTimer and DRX-Inactigytimer, respectively, the other DRX parameters are common.

There may be two DRX groups per DRX group running one set of DRX, i.e. within one MAC entity.

In the case of configuring DRX groups, the activation time of one DRX group may include any one or more of the following: the run time of DRX-onduration timer of the DRX group; run time of DRX-InactvityTimer of the DRX group; run time of DRX-retransmission timer dl corresponding to the DRX group (or any cell in the DRX group); run time of DRX-retransmission timer ul corresponding to the DRX group (or any cell in the DRX group); run time of DRX-retransmission timer sl corresponding to the DRX group (or any cell in the DRX group); an SR is transmitted on the PUCCH and is waiting for processing; after the non-contention random access procedure successfully receives the RAR (i.e., after the non-contention RA is successful), a PDCCH scrambled with the C-RNTI indicating a new transmission has not been received, and so on.

And 4.2, multicasting DRX.

The multicast DRX and the unicast DRX are independent, and the multicast DRX parameter may be and run per (per) G-RNTI and/or G-CS-RNTI. It should be noted that there may be some association or interaction between unicast DRX and multicast DRX. For example, when the terminal device receives the DCI scrambled by the G-RNTI, it may start or restart the DRX-HARQ-RTT-timer dl of the unicast DRX and/or stop the DRX-retransmission timer dl of the unicast DRX.

For one multicast, or for one G-RNTI or G-CS-RNTI, the activation time (active time) of the multicast DRX may include any one or more of the following: the run time of the drx-onduration TimerPTM for the G-RNTI or G-CS-RNTI, the run time of the drx-InactigityTimerPTM for the G-RNTI or G-CS-RNTI, or the run time of the drx-retransmission TimerDL-PTM for the G-RNTI or G-CS-RNTI.

The DRX functionality for multicast may be described as follows:

the network device configures any one or more of the following parameters via RRC message to control multicast DRX operation:

drx-ondurationtimertm: a period of time at the beginning of the DRX cycle. The location of the drx-onduration timertm start or restart is calculated according to the parameters of the base station configuration and the formulas specified by the protocol.

drx-InactivityTimerPTM: a period of time after the PDCCH occasion of DL new transmission scheduling is indicated. For example, the terminal device receives a PDCCH (e.g., a G-RNTI or a G-CS-RNTI scrambled PDCCH), indicates a new downlink transmission (i.e., a new transmission schedule), and starts or restarts the drx-InactigitTimerPTM.

drx-retransmission TimerDL-PTM: up to the maximum duration of the DL retransmission is received. For example, drx-HARQ-RTT-TimerDL-PTM times out and the data is not successfully decoded, the drx-retransmission TimerDL-PTM is started or restarted.

drx-HARQ-RTT-TimerDL-PTM: the minimum duration before DL retransmission is expected or the minimum duration before DL retransmission is expected to be received. For example, the terminal device receives a PDCCH (e.g., a G-RNTI or a G-CS-RNTI scrambled PDCCH) indicating a downlink transmission, or the terminal device receives data in a downlink allocation of a multicast configuration, starts or restarts the drx-HARQ-RTT-TimerDL-PTM.

Any one or more of drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerSL, drx-RetransmissionTimerSL, drx-HARQ-RTT-TimerSL, drx-HARQ-RTT-TimerDL-PTM, drx-retransmission TimerDL-PTM is per (per) HARQ process. For example, the terminal device maintains different drx-HARQ-RTT-TimerDL for different HARQ processes. For example, the terminal device maintains different drx-retransmission timerul 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-retransmission timer dl-PTM for different HARQ processes.

Any one or more of the drx-HARQ-RTT-TimerDL-PTM, drx-retransmission TimerDL-PTM is per (per) G-RNTI and/or G-CS-RNTI, or per (per) multicast/multicast service. For example, the terminal device maintains different drx-HARQ-RTT-TimerDL-PTM for different G-RNTIs and/or G-CS-RNTIs, or for different multicast/multicast services. For example, the terminal device maintains different drx-retransmission timerdl-PTM for different G-RNTIs and/or G-CS-RNTIs, or for different multicast/multicast services.

Note that, DRX related content may refer to 3gpp TS 38.321: "NR; medium Access Control (MAC); protocol specification ", which are not described in detail herein.

5. Multicast and unicast corresponding logical channels.

The multicast-corresponding logical channels include DTCH and MTCH. The unicast corresponding logical channel includes DTCH. As shown in fig. 3a, fig. 3a is a schematic diagram of channel mapping. For the transmission of multicast data, the corresponding logical channel, transmission channel and physical channel are respectively: DTCH and MTCH, downlink-shared channel (DL-SCH), physical downlink shared channel (physical downlink shared channel, PDSCH).

A multicast service may correspond to/include one or more MBS Radio Bearers (MRBs). One RB/MRB corresponds to one PDCP entity. For MRB, one PDCP entity of the terminal device may correspond to one RLC entity (e.g., one PTP RLC entity or one PTM RLC entity) of the terminal device, or may correspond to two RLC entities (e.g., one PTP RLC entity and one PTM RLC entity). Taking a PDCP entity corresponding to one MRB as an example, 2 RLC entities are illustrated, as shown in fig. 3b, a packet data convergence protocol (packet data convergence protocol, PDCP) entity corresponds to a PTP radio link control (radio link control, RLC) entity and a PTM RLC entity, and both PTP RLC entity and PTM RLC entity correspond to MAC entities. The logical channel corresponding to the PTP RLC entity is DTCH, and the logical channel corresponding to the PTM RLC entity is MTCH. The MTCH and DTCH are logical channels corresponding to different RLC entities. That is, for multicast data, it may be associated with DTCH or MTCH.

For one terminal device, the following possibilities may exist:

(1) For a multicast service, it may correspond to one or more MTCHs and/or one or more DTCHs. The LCID of each logical channel is different for one or more MTCHs and/or one or more DTCHs corresponding to the multicast service.

(2) For different multicast traffic, which may correspond to different MTCHs and/or DTCHs, the LCID for each logical channel is also different. For unicast traffic, it may correspond to DTCH.

(3) For unicast traffic and multicast traffic, which may correspond to different DTCHs, the LCID for each logical channel is also different.

It will be appreciated that, within a terminal device, the LCID of each logical channel is different for a plurality of logical channels corresponding to unicast traffic and multicast traffic.

One multicast service corresponds to one G-RNTI and/or one G-CS-RNTI, one multicast service may correspond to one or more MTCHs, data corresponding to the one or more MTCHs may be multiplexed together to form a MAC PDU, and the MAC PDU may be scheduled for transmission through a PDCCH scrambled by the G-RNTI, or the MAC PDU may be transmitted on a multicast SPS resource corresponding to the G-RNTI and/or the G-CS-RNTI. In addition, if the MAC PDU is scheduled to be transmitted through the G-RNTI scrambled PDCCH, retransmission of the MAC PDU may be scheduled to be transmitted through the G-RNTI scrambled PDCCH or may be scheduled to be transmitted through the C-RNTI scrambled PDCCH. If the MAC PDU is transmitted on the multicast SPS resource corresponding to the G-RNTI and/or the G-CS-RNTI, the retransmission of the MAC PDU can be scheduled to be transmitted through the PDCCH scrambled by the G-CS-RNTI or through the PDCCH scrambled by the CS-RNTI. And the monitoring of the PDCCH scrambled by the G-RNTI and/or the G-CS-RNTI is controlled by the multicast DRX corresponding to the G-RNTI and/or the G-CS-RNTI. Note that the transmission of MTCH related data may affect multicast DRX. In addition, since retransmission of MTCH related data may be scheduled to be transmitted through a C-RNTI-scrambled PDCCH or scheduled to be transmitted through a CS-RNTI-scrambled PDCCH, transmission of MTCH related data may also affect unicast DRX.

One multicast service may also correspond to one or more DTCHs, and DTCHs corresponding to different multicast services and data corresponding to DTCHs corresponding to unicast services may be multiplexed together to form a MAC PDU, where the MAC PDU may be scheduled for transmission through a PDCCH scrambled by the C-RNTI, or the MAC PDU may be transmitted on unicast SPS resources. In addition, if the MAC PDU is scheduled to be transmitted through the PDCCH scrambled by the C-RNTI, retransmission of the MAC PDU may be scheduled to be transmitted through the PDCCH scrambled by the C-RNTI. If the MAC PDU is transmitted on unicast SPS resources, retransmission of the MAC PDU may be scheduled for transmission through a CS-RNTI scrambled PDCCH. And the monitoring of the PDCCH scrambled by the C-RNTI or the CS-RNTI is controlled by unicast DRX. Note that the transmission of DTCH related data may affect unicast DRX.

6、HARQ。

6.1, HARQ process.

HARQ processes may be shared between unicast and multicast. For example, one HARQ process may be for multicast for a while/first time, and for unicast for a while/second time; in other words, one HARQ process is associated with a multicast at a first time and a unicast at a second time.

HARQ processes may be shared between multicast 1 and multicast 2. For example, one HARQ process may be for multicast 2 for a while/first time and for multicast 1 for a while/second time; in other words, one HARQ process is associated with multicast 2 for a while/first time, and multicast 1 for a while/second time.

HARQ processes may be shared between unicast and different multicast. For example, one HARQ process may be for multicast 2 for a duration/first time, for multicast 1 for a duration/second time, and for unicast for a duration/third time; in other words, one HARQ process is associated with multicast 2 for a moment/first time, multicast 1 for a moment/second time, and unicast for a moment/third time.

6.2, HARQ retransmission.

For multicast PTM transmission (e.g., the primary transmission is transmitted by using a PTM transmission mode), the network device may perform HARQ retransmission by using a PTP transmission mode or a PTM transmission mode. For example, the network device may schedule the G-RNTI scrambled data for initial transmission using the G-RNTI scrambled DCI, the network device may schedule the C-RNTI scrambled data for HARQ retransmission using the C-RNTI scrambled DCI, and/or the network device may schedule the G-RNTI scrambled data for HARQ retransmission using the G-RNTI scrambled DCI. In any of the above, the HARQ process ID and NDI corresponding to the HARQ retransmission (or the HARQ process ID and NDI in the DCI corresponding to the HARQ retransmission) are the same as those corresponding to the new transmission.

For the configuration transmission of multicast (for example, the initial transmission is transmitted by adopting a configuration transmission mode), the network device can perform HARQ retransmission by using a PTP transmission mode or a PTM transmission mode. For example, the network device may perform initial transmission on the multicast SPS resource, and the network device may schedule the CS-RNTI scrambled data for HARQ retransmission using the CS-RNTI scrambled DCI, and/or the network device may also schedule the G-CS-RNTI scrambled data for HARQ retransmission using the G-CS-RNTI scrambled DCI. For example, whichever HARQ retransmission is used, the HARQ process ID and NDI corresponding to the HARQ retransmission (or the HARQ process ID and NDI in DCI corresponding to the HARQ retransmission) are the same as those corresponding to the new transmission.

And 6.3, judging new transmission/retransmission.

In unicast transmission, the terminal device may determine whether the current transmission is a new transmission or a retransmission according to whether a new data indication (new data indication, NDI) corresponding to the same HARQ process or HARQ process ID is flipped. For example, for the same HARQ process, if the NDI of the current transmission is flipped compared with the NDI of the previous transmission, the terminal device determines that the current transmission is a new transmission; if the overturn does not occur, the terminal equipment determines that the transmission is retransmission.

For the same HARQ process or HARQ process ID, the terminal device may consider the present transmission as a new transmission in any one or more of the cases shown in the following table 1:

(1) The former transmission adopts multicast configuration transmission mode transmission (namely MBS SPS), and the present transmission adopts DCI dynamic scheduling transmission scrambled by C-RNTI (namely Dynamic scheduling via C-RNTI);

(2) The previous transmission adopts DCI dynamic scheduling transmission scrambled by G-CS-RNTI (namely Dynamic scheduling via G-CS-RNTI), and the current transmission adopts DCI dynamic scheduling transmission scrambled by C-RNTI (namely Dynamic scheduling via C-RNTI);

(3) The former transmission adopts a unicast configuration transmission mode (namely SPS), and the present transmission adopts DCI dynamic scheduling transmission scrambled by G-RNTI (namely Dynamic scheduling via G-RNTI);

(4) The former transmission adopts multicast configuration transmission mode transmission (namely MBS SPS), and the present transmission adopts DCI dynamic scheduling transmission scrambled by G-RNTI (namely Dynamic scheduling via G-RNTI);

(5) The previous transmission adopts DCI dynamic scheduling transmission (Dynamic scheduling via other G-RNTI) scrambled by other G-RNTI, and the current transmission adopts DCI dynamic scheduling transmission (Dynamic scheduling via G-RNTI) scrambled by G-RNTI;

(6) The previous transmission adopts DCI dynamic scheduling transmission scrambled by G-CS-RNTI (Dynamic scheduling via G-CS-RNTI), and the current transmission adopts DCI dynamic scheduling transmission scrambled by G-RNTI (namely Dynamic scheduling via G-RNTI);

(7) The previous transmission uses C-RNTI scrambled DCI dynamic scheduling transmission (Dynamic scheduling via C-RNTI), and the present transmission uses G-RNTI scrambled DCI dynamic scheduling transmission (i.e., dynamic scheduling via G-RNTI).

TABLE 1

As can be seen from the above transmission methods and HARQ retransmissions, the terminal device receives the DCI scrambled by the C-RNTI or the CS-RNTI, and the DCI scheduled data may be related to the MTCH or the DTCH.

For example, please refer to fig. 4a, fig. 4a is a schematic diagram of unicast transmission. As shown in fig. 4a, when the network device transmits data #a, DCI of scheduling data #a is transmitted 4 times, which can be understood that the network device performs initial transmission and 3 retransmissions of data #a. When the network device transmits data #a, 0 in the box represents that NDI in DCI of scheduling data #a is 0. When the network device transmits the data #b, the terminal device does not receive DCI originally transmitted by the scheduling data #b. Then, the network device performs retransmission of the data #b, and after the terminal device receives the first DCI scheduling retransmission of the data #b, since the NDI in the DCI received this time is inverted compared to the NDI in the DCI received last time (DCI scheduling retransmission of the data #a), the terminal device regards this retransmission of the data #b as the initial transmission of the data #b. The terminal device may start or restart the DRX-incaviytimer corresponding to the DRX associated with the unicast, so that the terminal device may continue to receive DCI transmitted in the unicast manner.

In unicast transmission, if the terminal device loses DCI for scheduling a certain data primary transmission, and receives DCI for subsequently scheduling the data retransmission, the terminal device may regard the retransmission as the primary transmission, and may start or restart DRX-inactivity timer corresponding to the DRX associated with unicast, thereby prolonging the activation time of the DRX associated with unicast. Thus, the terminal device may subsequently also receive DCI transmitted in unicast.

However, in MBS, if the terminal device does not receive DCI which is primarily transmitted in the PTM transmission mode and the network device performs HARQ retransmission in the PTP transmission mode, according to information in DCI corresponding to HARQ retransmission (e.g., HARQ process ID and NDI in DCI), the terminal device may not be able to correctly determine whether the data scheduled by the DCI is for unicast transmission, for multicast MTCH related transmission of the multicast service, or for multicast MTCH related transmission of other multicast services. The terminal device may misjudge the transmission as being for unicast transmission or multicast MTCH related transmission for other multicast services, the terminal device will not start or restart DRX-incaviytimtm corresponding to DRX associated with multicast (for example, the multicast service), the activation time of DRX associated with multicast will not be aligned compared with other terminal devices and network devices receiving the multicast service, and the terminal device may enter a sleep state earlier compared with other terminal devices and network devices receiving the multicast service, which may cause the terminal device to fail to receive a PDCCH scrambled by a subsequent G-RNTI or G-CS-RNTI (or a subsequent PTM transmission sent by the network device), affecting transmission reliability or increasing transmission delay, or may cause the terminal device to fail to report CSI and SRS, failing to assist multicast scheduling of a base station, affecting system performance. In addition, the terminal device may misjudge the transmission as a new unicast transmission, and the terminal device may start or restart the DRX-InactivityTimer corresponding to the DRX associated with unicast, which may cause the terminal device to charge electricity, and may cause the terminal device to unnecessarily report the CSI and the SRS.

For example, as shown in fig. 4b, the terminal device does not receive the first DCI of data 1 transmitted by the PTM transmission method (e.g., scheduling the G-RNTI scrambled DCI), and the network device retransmits the data 1 by the PTP transmission method (e.g., scheduling the C-RNTI scrambled DCI), and the terminal device receives the DCI corresponding to the retransmission, and HARQ process id=1 and ndi=1 in the DCI. The previous transmission received by the terminal device for the same HARQ process corresponds to a C-RNTI, and NDI is 0. Because NDI is flipped, the terminal device will misjudge the transmission of the retransmission of the data 1 by PTP transmission mode as unicast new transmission, and the terminal device will start or restart the DRX-Inactivitytimer corresponding to the DRX associated with unicast. Actually, DCI for retransmitting data 1 by PTP transmission schedules retransmission of multicast MTCH-related transmission.

As shown in fig. 5, when the network device performs MBS transmission with multiple terminal devices, if the terminal device #1 does not receive the DCI of the initial transmission of the data 1 transmitted in the PTM transmission mode, the subsequent network device performs retransmission of the data 1 for the terminal device #1 in the PTP transmission mode, that is, the network device sends the DCI of the retransmission of the data 1 to the terminal device #1 in the PTP transmission mode. In this case, since the terminal device #1 does not receive the DCI of the initial transmission of the data 1 transmitted by the PTM transmission mode, the terminal device #1 does not start or restart the DRX-incaactyittime PTM associated with the multicast, so that the activation time of the DRX associated with the multicast cannot be prolonged, and further the terminal device #1 may not subsequently receive the DCI of other or subsequent data transmitted by the network device by the PTM transmission mode. However, other terminal devices in the group receive the DCI of the initial transmission of data 1 transmitted in the PTM transmission mode, so that the other terminal devices in the group may start or restart the drx-incaactytimer PTM associated with multicast, and the other terminal devices may subsequently receive the DCI of other data transmitted in the PTM transmission mode.

In addition, if the terminal device #1 misjudges the initial transmission of the data 1 transmitted by the network device through the PTM transmission mode as a unicast new transmission, the terminal device #1 may start or restart the DRX-InactivityTimer corresponding to the DRX associated with the unicast. However, the network device does not start or restart the DRX-inactivity timer corresponding to the DRX associated with unicast, which may bring additional power consumption to the terminal device # 1.

For example, as shown in fig. 6, the network device performs initial transmission and retransmission of the data #a by adopting a unicast dynamic transmission mode, and NDI in DCI for scheduling the initial transmission and retransmission of the data #a is 1. The NDI in DCI of the network device scheduling data #b initial transmission and retransmission is 0. The network device adopts a PTM transmission mode to carry out primary transmission of the data #b, but the terminal device does not receive DCI for scheduling the primary transmission of the data #b. And then the network equipment retransmits the data #b in a PTP transmission mode. The terminal device receives the DCI retransmitted by the first scheduling data #b, and the NDI in the DCI is flipped compared to the NDI in the DCI (DCI retransmitted by the scheduling data #a) received the previous time. Then, the terminal device may misjudge the retransmission of the data #b as a unicast new transmission, so as to start or restart the DRX-InactivityTimer corresponding to the unicast associated DRX, and prolong the activation time of the unicast associated DRX, which may bring additional power consumption to the terminal device.

Embodiments of the present disclosure will present various aspects, embodiments, or features of the present disclosure around a system comprising a plurality of devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

In this application, "not received" may include/be understood as: no detection was made.

In this application, the multicast mode may also include/be replaced by a multicast mode or a broadcast mode. The present application is described by way of example in terms of multicasting.

In this application, DCI may be replaced with PDCCH, and PDCCH may be replaced with DCI.

In this application, data may be replaced with PDSCH, and PDSCH may be replaced with data.

In this application, the RNTI scrambling PDCCH/DCI/control information may be understood as: the RNTI scrambles a cyclic redundancy check (cyclic redundancy check, CRC) of the PDCCH/DCI/control information or the CRC of the PDCCH/DCI/control information is scrambled by the RNTI.

In the embodiment of the present application, the association may be understood as: corresponding to the above.

In this application, the first multicast may be understood as a first multicast service.

In this application, the duration of the wait before the terminal device receives the retransmission (e.g., data/DCI) may include/be understood as any one or more of the following: for indicating a length of time (e.g., a minimum length of time) for the terminal device to wait before receiving/receiving a retransmission (e.g., data/DCI) (e.g., DL data) and for indicating a length of time (e.g., a minimum length of time) for the terminal device to wait before desiring to receive/receive a retransmission (e.g., data/DCI) (e.g., DL data).

In this application, the duration for instructing the terminal device to receive the retransmission (e.g., data/DCI) may include/be understood as: for indicating a duration (e.g., maximum duration) for which a terminal device receives/receives a retransmission (e.g., data/DCI) (e.g., DL data or SL data).

In this application, the initial transmission may be replaced with a new transmission.

In this application, start-up is understood to be a start-up or a restart.

In this application, a non-start or a restart is understood to be a non-start or a non-restart.

In this application, NDI flip may be understood as different NDI, and NDI not flipped may be understood as the same NDI.

In the embodiment of the present application, the terminal device is taken as an example for explanation, and the terminal device may be replaced by a MAC entity of the terminal device or another device, which is not limited in the present application.

Third, communication method 100.

The embodiment of the application proposes a communication method 100, and fig. 7 is a schematic flow chart of the communication method 100. The communication method 100 is illustrated from the point of view of the terminal device side. The communication method 100 includes, but is not limited to, the steps of:

s101, the terminal equipment receives second downlink control information DCI transmitted in a unicast mode.

The second DCI transmitted in unicast may include/be understood as: the second RNTI scrambled second DCI or a second DCI associated with the second RNTI.

The second RNTI may be used for any one or more of: for unicast, for scheduling dynamic resources, for retransmission resources of dynamic resources, for activating configuration resources, for reactivating configuration resources, for deactivating configuration resources, for scheduling retransmission resources of configuration resources, for scrambling (e.g., for scrambling PDCCH or PDSCH).

The second RNTI may include/be a C-RNTI, and/or a CS-RNTI, for example.

The second DCI is used to schedule first data (e.g., first data transmitted in a unicast manner). The first data transmitted in unicast may include/be understood as: the second RNTI scrambles the first data or the first data associated with the second RNTI.

The second DCI is associated with a first HARQ process ID (or first HARQ process) and a first NDI. For example, the first HARQ process ID and the first NDI are included in the second DCI.

The first data is associated with a first HARQ process ID (or first HARQ process) and a first NDI.

S102, the terminal equipment receives the first data.

Optionally, the terminal device receives the first data, which may include: the terminal device successfully decodes the first data.

S103, the terminal equipment executes any one or more of S103-1 and S103-2 when the first condition is met.

The first condition includes: the first data includes a first logical channel identification LCID, and the terminal device does not receive the first DCI.

The first DCI is transmitted via multicast.

Wherein, the first LCID is an identification of the first multicast broadcast service MTCH. The first LCID is associated with a first multicast service. The first LCID is associated with the MTCH.

The first data comprises/is a first MAC PDU.

The first DCI is transmitted by multicast, which may include/be understood as: the first DCI scrambled by the first RNTI or the first DCI associated with the first RNTI.

The first RNTI may be used for any one or more of: for multicasting, for scheduling dynamic resources, for retransmitting resources of dynamic resources, for activating configuration resources, for reactivating configuration resources, for deactivating configuration resources, for scheduling retransmitting resources of configuration resources, for scrambling (e.g., for scrambling PDCCH or PDSCH).

The first RNTI may include/be a G-RNTI, and/or a G-CS-RNTI, for example. For example, the first RNTI may include a first G-RNTI and/or a first G-CS-RNTI. For example, the first multicast service is associated with a first G-RNTI and/or a first G-CS-RNTI.

One possible implementation, the first DCI is used to schedule first data (e.g., first data transmitted in a multicast manner). The first data transmitted in multicast may include/be understood as: the first RNTI scrambled first data or first data associated with the first RNTI.

In another possible implementation, the first DCI is used to activate a multicast configuration resource (e.g., a first multicast configuration resource). For example, the first multicast configuration resource is associated with any one or more of a first G-RNTI, a first G-CS-RNTI, a first multicast service. For example, the first data is transmitted on a first multicast configuration resource.

Illustratively, the first RNTI is a G-RNTI and the second RNTI is a C-RNTI.

Illustratively, the first RNTI is a G-CS-RNTI and the second RNTI is a CS-RNTI.

The first DCI is associated with a first HARQ process ID (or first HARQ process) and a first NDI. For example, the first DCI includes a first HARQ process ID and a first NDI.

The first DCI may include one or more DCIs. The first DCI is not received, which may include/be understood as: one DCI (e.g., first DCI) is not received, or a plurality of DCIs (e.g., first dci#1 and first dci#2) are not received. For example, the network device may have transmitted a first dci#1, where the first dci#1 is used to schedule first data (e.g., first data transmitted in a multicast manner), and the terminal device does not receive the first dci#1; the network device may also send a first dci#2, the first dci#2 being used to schedule first data (e.g., first data transmitted in a multicast manner), the terminal device also not receiving the first dci#2.

Optionally, not receiving the first DCI may include: no DCI transmitted in a multicast manner for scheduling first data (e.g., first data transmitted in a multicast manner) is received. For example, not receiving the first DCI may include: all/any DCI transmitted in a multicast manner for scheduling first data (e.g., first data transmitted in a multicast manner) is not received.

DCI transmitted by multicast may include/be understood as: the first RNTI scrambled DCI or DCI associated with the first RNTI.

It is understood that MTCH and DTCH share LCID space, but the LCID value of MTCH and LCID value of DTCH are not the same. That is, the LCID value of MTCH and the LCID value of DTCH are selected within the same range, but the LCID value of MTCH and the LCID value of DTCH are not the same. Thus, the terminal device may determine from the first LCID that the first LCID corresponds to the MTCH. Alternatively, the terminal device may determine, according to the first LCID, which MTCH or multicast or which multicast service or which G-RNTI (or G-CS-RNTI) corresponds to the first data.

The first data includes an identification of the first MTCH, indicating that the first data corresponds to the MTCH, or indicating that the first data is for multicast MTCH related transmissions, or indicating that the first data is associated with any one or more of a first multicast service, a first G-RNTI, a first G-CS-RNTI.

Optionally, the first LCID is associated with a first RNTI and/or a first multicast service.

Optionally, the multicast-associated DRX is associated with a first RNTI and/or a first multicast service. For example, multicast-associated DRX includes: a multicast associated DRX associated with the first RNTI, or a DRX associated with the first RNTI.

S103-1, the terminal equipment controls the DRX associated with multicast to be in an active time.

For example, the terminal device controlling multicast associated DRX to be active time may be understood/include any one or more of the following: making multicast associated DRX at an active time; enabling the terminal equipment to monitor a PDCCH corresponding to the first multicast service or the first RNTI; extending/elongating the activation time of multicast-associated DRX.

Optionally, the terminal device controlling the DRX of the multicast association to be active time may include: the terminal device starts or restarts one or more of the following timers: the second timer, the third timer, the fourth timer and the fifth timer.

For example, the second timer is an inactivity timer (e.g., DRX-inactivity timer ptm) corresponding to the DRX associated with the multicast.

For example, the third timer is a duration timer (e.g., DRX-onduration timer ptm) corresponding to DRX associated with multicast.

For example, the fourth timer is a retransmission timer (e.g., DRX-retransmission timer dl-PTM) corresponding to DRX associated with multicast.

The fifth timer may be a newly defined timer, which is not limited in this application.

For example, a duration timer corresponding to multicast-associated DRX is used to indicate a duration of waiting to receive control information (e.g., DCI) after a terminal device is awakened.

For example, the inactivity timer corresponding to the multicast-associated DRX is used to indicate a duration after scheduling the newly transmitted control information or newly transmitted data.

For example, a retransmission timer corresponding to the DRX associated with the multicast is used to indicate a duration for which the terminal device receives a retransmission (e.g., retransmitting DCI, retransmitting data).

As can be seen from the above, when one or more of the second timer, the third timer, and the fourth timer are running, DRX associated with multicast may be enabled at an active time.

Optionally, the first condition may further include any one or more of:

condition 1: multicast-associated DRX is not active time, or the second timer is not running;

condition 2: after receiving the second DCI, the terminal equipment does not start or restart the second timer; or, starting from the terminal equipment to receive the second DCI, wherein the second timer is not started or restarted;

Condition 3: after receiving third DCI, the terminal equipment does not start or restart the second timer, the third DCI is used for scheduling the first data, and the third DCI is before the second DCI; or, starting from the terminal device receiving the third DCI, the second timer is not started or restarted.

Optionally, the multicast associated DRX not being active time may include the terminal device determining that the multicast associated DRX is not active time.

The second timer not being started or restarted may include: the second timer is not started or restarted. It will be appreciated that "the second timer is not started or restarted" does not define whether the second timer is running.

Optionally, after the terminal device receives the second DCI, the second timer is not started or restarted; or, starting from the terminal device receiving the second DCI, the second timer not being started or restarted "may include one or more of: after the terminal equipment starts or restarts the second timer, the second timer is not started or restarted; after the terminal equipment starts or restarts the second timer due to the second DCI, the second timer is not started or restarted; after the terminal device receives the second DCI or from the terminal device, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service); after the terminal device starts or restarts the second timer, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service); after the terminal device starts or restarts the second timer due to the second DCI, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service).

Optionally, after the terminal device receives the third DCI, the second timer is not started or restarted; or, starting from the terminal device receiving the third DCI, the second timer not being started or restarted "may include one or more of: after the terminal equipment starts or restarts the second timer, the second timer is not started or restarted; after the terminal equipment starts or restarts the second timer due to the third DCI, the second timer is not started or restarted; after the terminal device receives the third DCI or from the terminal device, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service); after the terminal device starts or restarts the second timer, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service); after the terminal device starts or restarts the second timer due to the third DCI, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions of multicast transmissions associated with the first RNTI or the first multicast service).

Optionally, after the terminal device receives the second DCI or the third DCI, the second timer is not started or restarted; or, starting from the terminal device receiving the second DCI or the third DCI, the second timer not being started or restarted "may include one or more of:

(1) After the terminal equipment receives the second DCI or the third DCI or starts from the terminal equipment to receive the second DCI or the third DCI, the second timer is not started or restarted when the terminal equipment successfully decodes the first data or when the terminal equipment determines that the first condition is met or when the terminal equipment is about to/wants to control the DRX (discontinuous reception) associated with the multicast to be in the activation time;

(2) After the terminal equipment starts or restarts the second timer, the second timer is not started or restarted until the terminal equipment successfully decodes the first data, or until the terminal equipment determines that the first condition is met, or until the terminal equipment is in the activation time with/wants to control the DRX associated with the multicast;

(3) After the second timer is started or restarted by the second DCI or the third DCI, the second timer is not started or restarted until the first data is successfully decoded by the terminal equipment, or until the terminal equipment determines that the first condition is met, or until the terminal equipment is in the activation time with/wants to control the DRX associated with the multicast;

(4) After the terminal device receives the second DCI or the third DCI or from the terminal device to start to receive the second DCI or the third DCI, when the terminal device successfully decodes the first data, or when the terminal device determines that the first condition is met, or when the terminal device will/wants to control DRX associated with multicast to be at an active time, the second timer is not started or restarted by other transmissions (for example, initial transmission associated with the first RNTI or the first multicast service and transmitted by multicast mode);

(5) After the terminal device starts or restarts the second timer, the second timer is not started or restarted by other transmissions (e.g., initial transmissions associated with the first RNTI or the first multicast service and transmitted by multicast) until the terminal device successfully decodes the first data, or until the terminal device determines that the first condition is satisfied, or until the DRX associated with the multicast will/want to be controlled by the terminal device is at an active time;

(6) After the terminal device starts or restarts the second timer due to the second DCI or the third DCI, the second timer is not started or restarted due to other transmissions (e.g., initial transmissions associated with the first RNTI or the first multicast service and transmitted by multicast), until the terminal device successfully decodes the first data, or until the terminal device determines that the first condition is satisfied, or until the terminal device will/wants to control the DRX associated with the multicast to be active.

Optionally, the second DCI is a first DCI transmitted in a unicast manner and received by the terminal device, where the first DCI is used to schedule the first data.

The third DCI is transmitted in a unicast manner.

The third DCI is associated with a first HARQ process ID (or first HARQ process) and a first NDI. For example, the first HARQ process ID and the first NDI are included in the third DCI.

For example, the third DCI may include a first DCI received by the terminal device transmitted in a unicast manner for scheduling the first data.

Alternatively, there may be other DCI transmitted in a unicast manner for scheduling the first data in addition to the third DCI and the second DCI, which is not limited in this application.

For example, when/after the terminal device successfully decodes the first data, or when/after the terminal device determines that the first data includes the first LCID and the terminal device does not receive the first DCI transmitted by multicast, it determines whether the DRX associated with multicast is active, if the DRX associated with multicast is not active, then other DCIs transmitted by multicast cannot be received due to the DRX associated with multicast not being active. Therefore, the terminal equipment controls the multicast DRX to be in the activation time, so that the terminal equipment can receive other DCIs transmitted in a multicast mode subsequently, the communication reliability is improved, and the communication time delay is reduced.

For example, if the terminal device determines that the first data includes the first LCID, the terminal device does not receive the first DCI transmitted by the multicast mode, and if the DRX associated with the multicast is active, the control of the DRX associated with the multicast is not performed.

In one possible scenario, during or after the time domain position corresponding to the second DCI or the third DCI, until the terminal device successfully decodes the first data, or until the terminal device determines that the first condition is met, or until the terminal device will/wants to control the DRX associated with multicast to be in an active time period, the terminal device may receive other DCIs transmitted in a multicast manner, so that the terminal device starts or restarts an inactivity timer corresponding to the DRX associated with multicast to make the DRX associated with multicast to be in an active time period, so that the terminal device aligns the active time of the DRX associated with other terminal devices and network devices that receive the multicast service, and the terminal device may receive the DCI transmitted in a multicast manner subsequently. Then the terminal device does not need to control the multicast associated DRX at the activation time any more.

Optionally, when the terminal device determines that the first data includes the first LCID and the terminal device does not receive the first DCI transmitted in the multicast manner, if the terminal device receives the second DCI or the third DCI, the second timer is not started or restarted, which indicates that the terminal device does not receive other initial transmissions transmitted in the multicast manner after receiving the second DCI or the third DCI, so that the inactivity timer corresponding to the DRX associated with the multicast is not started or restarted, and therefore, the activation time of the DRX associated with the multicast between the terminal device and other terminal devices receiving the multicast service and the network device is still not aligned. Therefore, in this case, the terminal device needs to control the DRX associated with the multicast to be in an active time, so that other DCI transmitted in the multicast manner can be received subsequently, so as to improve the communication reliability and reduce the communication delay.

Optionally, when the terminal device determines that the first data includes the first LCID and the terminal device does not receive the first DCI transmitted in the multicast manner, if the terminal device receives the third DCI, the second timer is not started or restarted, which indicates that the terminal device does not receive other initial transmissions transmitted in the multicast manner after receiving the first DCI transmitted in the unicast manner for scheduling the first data, so that the inactivity timer corresponding to the DRX associated with the multicast is not started or restarted, so the activation time of the DRX associated with the multicast between the terminal device and other terminal devices receiving the multicast service and the network device is still not aligned. Therefore, in this case, the terminal device needs to control the DRX associated with the multicast to be in an active time, so that other DCI transmitted in the multicast manner can be received subsequently, so as to improve the communication reliability and reduce the communication delay.

For example, as shown in fig. 8, the first data is data #b. When the network device transmits data #b to the terminal device, the terminal device does not receive the first DCI originally transmitted by the scheduling data #b, and the first DCI is transmitted by a multicast mode. The network device schedules retransmission of the data #b through a third DCI transmitted through a unicast. The terminal device receives the third DCI scheduling the retransmission of data #b, but does not successfully decode the data #b. The network device thus continues to schedule retransmission of data #b via the second DCI, which is also transmitted via unicast. The terminal device receives the second DCI and successfully decodes the data #b. Optionally, the terminal device may also receive other DCIs for scheduling retransmission of data #b in the time between receiving the third DCI and receiving the second DCI, but none of the DCIs successfully decoded data #b. If the terminal device determines that the first data includes the first LCID, and the first DCI transmitted in the multicast manner is not received, and the second timer is not started or restarted from the time when the third DCI is received to the time when the data #b is successfully decoded (i.e., the time period denoted by T in fig. 8), which indicates that the terminal device does not receive other initial transmissions transmitted in the multicast manner after receiving the third DCI. Thus, the second timer is not started or restarted all the time, so the activation time of the multicast-associated DRX between the terminal device and other terminal devices receiving the multicast service and the network device is still not aligned. Therefore, in this case, the terminal device needs to control the DRX associated with the multicast to be in an active time, so that other DCI transmitted in the multicast manner can be received subsequently, so as to improve the communication reliability and reduce the communication delay.

Optionally, considering that a certain time is required for receiving DCI transmitted in a unicast manner and scheduling first data from the terminal device to correctly decode the first data, if the configuration duration of the second timer is less than the certain time, even if other terminal devices receive DCI transmitted in a multicast manner and scheduling first data and start the second timer, by the time point when the terminal devices correctly decode the first data, the other terminal devices start or restart the second timer already times out because of receiving DCI transmitted in a multicast manner and scheduling first data, in this case, if the terminal devices start the second timer, it is unnecessary and the power consumption of the terminal devices is increased. Optionally, because the network device may consider the sixth timer and/or the seventh timer on the terminal device side when scheduling the retransmission, the certain time may also consider the configuration duration of the sixth timer and/or the configuration duration of the seventh timer.

Alternatively, the first condition may further include condition 8.

Condition 8: the second duration is less than a configuration duration of the second timer.

Illustratively, the second duration may include any one or more of the following or include a sum of any one or more of the following: a period from receiving the second DCI (or the third DCI) from the terminal device to successfully decoding the first data by the terminal device; receiving a second DCI (or a third DCI) from the terminal equipment to determine a duration of meeting the first condition; receiving a second DCI (or a third DCI) from the terminal equipment to the duration that the terminal equipment will/wants to control the DRX associated with the multicast to be in an active time; the configuration duration of the sixth timer; the configuration duration of the seventh timer; a first preset time period. For example, the second duration is: the second DCI (or third DCI) is received from the terminal device for a period of time for the terminal device to successfully decode the first data. For example, the second duration is: the second DCI (or third DCI) is received from the terminal device to the sum of the length of time for which the terminal device successfully decodes the first data and the configuration length of the sixth timer. For example, the second duration is: the second DCI (or third DCI) is received from the terminal device to the sum of the length of time the terminal device successfully decodes the first data and the configuration length of the seventh timer. For example, any one or more of the configuration duration of the second timer, the configuration duration of the sixth timer, and the configuration duration of the seventh timer may be configured by the network device to the terminal device. For example, the configured duration of the timer (e.g., the configured duration of the second timer) may also be referred to as a preset duration of the timer (e.g., the preset duration of the second timer).

Alternatively, "the terminal device receives the second DCI (or the third DCI)" may include/be replaced with: time domain position of the second DCI (or third DCI). For example, the time domain position of the second DCI (or third DCI) may also be referred to as: the time domain position where the second DCI (or the third DCI) is located, or the time domain position corresponding to the second DCI (or the third DCI). For example, "the terminal device receives the second DCI (or the third DCI)" may include/be replaced with: the terminal device receives a start time domain position or an end time domain position or an intermediate time domain position of the second DCI (or the third DCI), which is not limited in this application. For example, the time domain position of the second DCI or the third DCI may include: the starting time domain position or ending time domain position or intermediate time domain position of the second DCI (or third DCI) is not limited in this application.

For example, the sixth timer is an RTT timer (e.g., DRX-HARQ-RTT-TimerDL-PTM) corresponding to DRX associated with multicast. For example, the RTT timer corresponding to the DRX associated with multicast is used to indicate a duration of waiting before the terminal device receives a retransmission (e.g., retransmitting DCI and/or retransmitting data).

For example, a seventh timer is associated with the first DRX. Illustratively, the seventh timer is a unicast corresponding RTT timer (e.g., drx-HARQ-RTT-TimerDL). For example, the unicast corresponding RTT timer is used to indicate a duration of waiting before the terminal device receives a retransmission (e.g., retransmitting DCI and/or retransmitting data). For example, the seventh timer is an RTT timer corresponding to DRX associated with unicast or an RTT timer corresponding to first DRX. Optionally, the seventh timer is associated with a DRX group corresponding to the first cell. Illustratively, the seventh timer is DRX-HARQ-RTT-TimerDL associated with the DRX group corresponding to the first cell.

For example, the first preset duration may be configured by the network device for the terminal device, or may be specified by a protocol, or may be preconfigured, or may be stored by the terminal device, or may be acquired by the terminal device through other manners, which is not limited in this application.

In an alternative implementation, the running duration of the second timer is less than or equal to the configuration duration of the second timer minus the third duration. For example, the running duration of the second timer is the configuration duration of the second timer minus the third duration. For example, the first condition is satisfied, and the terminal device starts or restarts the second timer, where the running duration of the second timer is less than or equal to the configured duration of the second timer minus the third duration, or the running duration of the started or restarted second timer is less than or equal to the configured duration of the second timer minus the third duration. For example, the run length of the second timer may include/be referred to as: the remaining run length of the second timer. For example, the first condition includes any one or more of condition 1, condition 2, condition 3, and condition 8.

Optionally, "the running duration of the second timer is less than or equal to the configuration duration of the second timer minus the third duration" may include: the terminal device sets/determines that the running duration of the second timer is less than or equal to the configuration duration of the second timer minus the third duration.

Illustratively, the third duration may include any one or more of the following or include a sum of any one or more of the following: a period from receiving the second DCI (or the third DCI) from the terminal device to successfully decoding the first data by the terminal device; receiving a second DCI (or a third DCI) from the terminal equipment to determine a duration of meeting the first condition; receiving a second DCI (or a third DCI) from the terminal equipment to the duration that the terminal equipment will/wants to control the DRX associated with the multicast to be in an active time; the configuration duration of the sixth timer; the configuration duration of the seventh timer; a first preset time period; and a second preset time period. It should be noted that the third duration may be the same as the second duration, or may be different from the second duration, which is not limited in this application.

For example, the second preset duration may be configured by the network device for the terminal device, or may be specified by a protocol, or may be preconfigured, or may be stored by the terminal device, or may be acquired by the terminal device through other manners, which is not limited in this application.

In an alternative implementation, the first condition is not met and the terminal device does not perform S103-1. For example, if the second time period is greater than or equal to the configuration time period of the second timer, the terminal device does not start or restart the second timer. For example, the first condition includes any one or more of condition 1, condition 2, condition 3, and condition 8.

For example, as shown in fig. 8, the first data is data #b. When the network device transmits data #b to the terminal device, the terminal device does not receive the first DCI originally transmitted by the scheduling data #b, and the first DCI is transmitted by a multicast mode. The network device schedules retransmission of the data #b through a third DCI transmitted through a unicast. The terminal device receives the third DCI scheduling the retransmission of data #b, but does not successfully decode the data #b. The network device thus continues to schedule retransmission of data #b via the second DCI, which is also transmitted via unicast. The terminal device receives the second DCI and successfully decodes the data #b. Optionally, the terminal device may also receive other DCIs for scheduling retransmission of data #b in the time between receiving the third DCI and receiving the second DCI, but none of the DCIs successfully decoded data #b. If the terminal device determines that the first data includes the first LCID, and the first DCI transmitted by multicast is not received, and the second timer is not started or restarted from the time when the third DCI is received to the time when the data #b is successfully decoded (i.e., the time period denoted by T in fig. 8). If the time period from the receipt of the third DCI to the successful decoding of the data #b (i.e., the time period represented by T in fig. 8) is less than the configuration duration of the second timer, the terminal device may start or restart the second timer, and set the operation duration of the second timer to (configuration duration of the second timer-T); if the period of time from the receipt of the third DCI until the successful decoding of the data #b (i.e., the period of time denoted by T in fig. 8) is greater than or equal to the configuration duration of the second timer, the terminal device may not start or restart the second timer. Thus, in some cases (for example, in a case where the activation time of the DRX associated with multicast is not aligned between the terminal device and other terminal devices and network devices that receive the multicast service), the terminal device needs to control the DRX associated with multicast to be at the activation time, so that other DCI transmitted in the multicast manner can be received subsequently, improving communication reliability and reducing communication delay; in other cases (for example, in the case where the activation time of the DRX associated with multicast between the terminal device and other terminal devices receiving the multicast service and the network device is already aligned), the terminal device does not need to control the DRX associated with multicast to be in the activation time, which can avoid unnecessary increase of power consumption of the terminal device and is beneficial to energy saving of the terminal device.

Alternatively, the first condition may further include condition a or condition B or condition C.

For example, if the second RNTI is a C-RNTI and/or the first RNTI is a first G-RNTI, the first condition may also include condition a or condition B or condition C.

Condition a includes: before the second DCI or the third DCI, the transmission for the first HARQ process or the transmission of the first HARQ process ID received by the terminal device includes any one of the following:

(1) Transmitting by adopting a multicast configuration transmission mode (namely MBS SPS); for example, a transmission corresponding to data transmitted on a first multicast configuration resource or other multicast configuration resources (or multicast configuration resources associated with other G-RNTIs or G-CS-RNTIs or multicast traffic).

(2) DCI dynamic scheduling transmission scrambled by adopting G-CS-RNTI (namely Dynamic scheduling via G-CS-RNTI); for example, the transmission is dynamically scheduled using a first G-CS-RNTI or other G-CS-RNTI scrambled DCI.

(3) Transmitting (SPS) by adopting a unicast configuration transmission mode;

(4) DCI dynamic scheduling transmission scrambled with CS-RNTI (i.e. Dynamic scheduling via CS-RNTI);

(5) A DCI dynamic scheduling transmission scrambled with a G-RNTI (i.e., dynamic scheduling via G-RNTI) and corresponding NDI of the transmission is different from the first NDI (e.g., NDI flip); for example, a transmission (i.e., dynamic scheduling via G-RNTI) is dynamically scheduled with a first G-RNTI or other G-RNTI scrambled DCI and the corresponding NDI is different from the first NDI.

(6) The C-RNTI scrambled DCI is used to dynamically schedule a transmission (i.e., dynamic scheduling via other C-RNTI) and the corresponding NDI for the transmission is different from the first NDI (e.g., NDI flip).

It may be appreciated that in one or more cases of (1) to (6), the terminal device receives the third DCI or the second DCI, and the terminal device regards the transmission corresponding to the third DCI or the second DCI as a unicast new transmission.

Condition B includes: before the second DCI or the third DCI, the transmission for the first HARQ process or the transmission of the first HARQ process ID received by the terminal device is: the C-RNTI scrambled DCI is used to dynamically schedule a transmission (i.e., dynamic scheduling via other C-RNTI) and the corresponding NDI for the transmission is the same as the first NDI (e.g., the NDI is not flipped). It may be appreciated that in this case, the terminal device receives the third DCI or the second DCI, and the terminal device regards the transmission corresponding to the third DCI or the second DCI as unicast retransmission.

When the condition a or the condition B corresponds to the above, the terminal device receives the third DCI or the second DCI, and the terminal device may consider the transmission corresponding to the third DCI or the second DCI as unicast transmission because the terminal device does not receive the first DCI.

Condition C includes: before the second DCI or the third DCI, the transmission for the first HARQ process or the transmission of the first HARQ process ID received by the terminal device is: other G-RNTI scrambled DCI is employed to dynamically schedule a transmission (i.e., dynamic scheduling via G-RNTI) and the NDI corresponding to the transmission is the same as the first NDI (e.g., NDI is not flipped). It may be appreciated that, in this case, the terminal device receives the third DCI or the second DCI, and the terminal device may consider the transmission corresponding to the third DCI or the second DCI as a retransmission of the multicast MTCH related transmission related to the other G-RNTI because the terminal device does not receive the first DCI.

Alternatively, the first condition may further include condition D or condition E.

For example, if the second RNTI is a CS-RNTI and/or the first RNTI is a first G-CS-RNTI, the first condition may also include condition D or condition E.

Condition D includes: before the second DCI or the third DCI, the transmission for the first HARQ process or the transmission of the first HARQ process ID received by the terminal device includes any one of the following:

(1) Transmitting (SPS) by adopting a unicast configuration transmission mode;

(2) The DCI scrambled with the CS-RNTI dynamically schedules a transmission (i.e., dynamic scheduling via CS-RNTI) and the corresponding NDI for the transmission is the same as the first NDI (e.g., the NDI is not flipped).

It may be understood that, in one or more cases of (1) or (2) above, the terminal device receives the third DCI or the second DCI, and the terminal device may consider the transmission corresponding to the third DCI or the second DCI as unicast retransmission because the terminal device does not receive the first DCI.

Condition E includes: before the second DCI or the third DCI, the transmission for the first HARQ process or the transmission of the first HARQ process ID received by the terminal device is: transmitting by adopting a multicast configuration transmission mode (namely MBS SPS); for example, the transmission corresponding to data transmitted on other multicast configuration resources (or multicast configuration resources associated with other G-RNTI or G-CS-RNTI or multicast traffic). It may be understood that in this case, the terminal device receives the third DCI or the second DCI, and the terminal device may consider the transmission corresponding to the third DCI or the second DCI as the retransmission of the multicast MTCH related transmission related to the other G-RNTI or the G-CS-RNTI because the terminal device does not receive the first DCI.

It may be understood that, in the case of the condition a or the condition B or the condition C or the condition D or the condition E, the terminal device receives the third DCI or the second DCI, and the terminal device may treat the transmission corresponding to the third DCI or the second DCI as unicast transmission or other multicast-related multicast MTCH-related transmission, and may not start or restart the inactivity timer corresponding to the DRX associated with multicast, and may not receive other DCIs transmitted in the multicast manner due to the fact that the DRX associated with multicast is not in the active time. Therefore, the terminal equipment controls the multicast DRX to be in the activation time, so that the terminal equipment can receive other DCIs transmitted in a multicast mode subsequently, the communication reliability is improved, and the communication time delay is reduced.

Optionally, the terminal device not receiving the first DCI may include/be replaced with: condition a or condition B or condition C or condition D or condition E.

It may be appreciated that in the case where the condition a or the condition B or the condition C or the condition D or the condition E corresponds, the first data includes the first LCID, and the terminal device may determine that the terminal device does not receive the first DCI.

S103-2, the terminal equipment stops the first timer or shortens the residual operation duration of the first timer.

Illustratively, the first timer is associated with a first DRX.

The first DRX may be used to control the listening of terminal device specific control information.

Alternatively, the first DRX may also be used to control the listening of control information that is not specific to the terminal device, which is not limited in this application.

For example, the first DRX may be used to control the listening of control information for any one or more of the following RNTIs: C-RNTI, cancellation indication RNTI (cancellation indication RNTI, CI-RNTI), configuration scheduling RNTI (configured scheduling RNTI, CS-RNTI), interrupt RNTI (INT-RNTI), time 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 (transmit power control-sounding reference signal-RNTI, TPC-SRS-RNTI), acquisition indicator (acquisition indicator, AI) -RNTI, side-RNTI (sidelink, SL-configuration scheduling (sidelink configured scheduling, SLCS-RNTI), side-semi-static scheduling V2X (SL-persistent scheduling V-semi).

For example, the first DRX may be a unicast DRX, or a DRX group (e.g., one DRX group).

Illustratively, the activation time of the first DRX may include any one or more of the following: unicast the run time of the corresponding duration timer (e.g., drx-onduration timer); unicast the run time of the corresponding inactivity timer (e.g., drx-InactivityTimer); or, unicast the running time of the corresponding retransmission timer.

Illustratively, the unicast corresponding retransmission timer may include any one or more of the following: a downlink retransmission timer (e.g., drx-retransmission timer dl), an uplink retransmission timer (e.g., drx-retransmission timer ul), or a side uplink retransmission timer (e.g., drx-retransmission timer sl).

It can be appreciated that during the activation time of the first DRX, the terminal device listens for terminal device specific control information.

For example, a unicast corresponding duration timer/duration timer is used to indicate the duration of waiting to receive control information (e.g., DCI) after a terminal device is awakened.

For example, unicast corresponding inactivity timers/inactivity timers are used to indicate a length of time after control information or new transmission data is scheduled for a new transmission.

For example, a unicast corresponding retransmission timer/retransmission timer is used to indicate the duration of time for which a terminal device receives a retransmission (e.g., retransmitting DCI, retransmitting data, retransmitting resources).

For example, the unicast corresponding downlink retransmission timer/downlink retransmission timer is used to indicate a duration for which the terminal device receives downlink retransmission (e.g., retransmitting DCI, retransmitting data, retransmitting resources).

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

For example, a unicast corresponding side-uplink retransmission timer/side-uplink retransmission timer is used to indicate the duration of a terminal device receiving a side-uplink retransmission (e.g., retransmitting DCI, retransmitting data, retransmitting resources).

Illustratively, the activation time of the first DRX may include any one or more of the following: the run time of a duration timer (e.g., DRX-onduration timer) corresponding to the DRX group; run time of an inactivity timer (e.g., DRX-inactivity timer) corresponding to the DRX group; or, the running time of the retransmission timer corresponding to the DRX group.

Optionally, the activation time of the first DRX may further include other times, which is not limited in this application. Illustratively, the content of the activation time of the first DRX may be referred to as 3GPP TS 38.321: "NR; medium Access Control (MAC); protocol specification).

Illustratively, the first timer is a unicast corresponding inactivity timer (e.g., drx-InactivityTimer).

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

Optionally, the first timer is associated with a DRX group corresponding to the first cell. The first cell is associated with any one or more of first data, first DCI, second DCI, third DCI, a first multicast service, a first G-RNTI, a first G-CS-RNTI. For example, the terminal device receives first data, second DCI, third DCI in a first cell. Illustratively, the first timer is a DRX group associated DRX-inactivity timer corresponding to the first cell.

The remaining operation duration of the first timer may also be referred to as the operation duration of the first timer.

In an alternative embodiment, the terminal device stops the first timer if the first condition is met.

Optionally, the first condition may further include one or more of:

condition 4: the terminal equipment receives the second DCI or the third DCI, and the first timer is not operated;

condition 5: after receiving the second DCI or the third DCI, the terminal equipment does not start or restart the first timer;

Condition 6: the operation of the first timer is due to the second DCI or the third DCI; alternatively, the operation of the first timer is due to the second DCI or the third DCI starting or restarting the first timer; or, the terminal equipment starts or restarts the first timer due to the second DCI or the third DCI;

condition 9: the first timer is configured to be longer than the third time period.

The configuration duration of the first timer may be configured by the network device to the terminal device, for example. For example, the configuration duration of the first timer may also be referred to as a preset duration of the first timer.

Illustratively, the third duration includes any one of: starting or restarting a time point T1 of the first timer by the terminal equipment because of the reception of the second DCI or the third DCI until the time length of successfully decoding the first data by the terminal equipment; determining a time length satisfying the first condition from a time point T1 at which the terminal device starts or restarts the first timer due to reception of the second DCI or the third DCI to the terminal device; starting or restarting the first timer from a time point T1 when the terminal device starts or restarts the first timer due to the reception of the second DCI or the third DCI to the time point when the terminal device will/wants to stop the first timer or shorten the remaining operation duration of the first timer; (T2-T1). Optionally, "the terminal device receives the second DCI or the third DCI, the first timer is not running" may include any one or more of the following:

(1) After receiving the second DCI or the third DCI, the terminal equipment does not operate the first timer;

(2) After the terminal equipment receives the first duration or the first moment after receiving the second DCI or the third DCI, the first timer does not run;

(3) When the terminal equipment starts or restarts the first timer, the first timer does not run; or, when the terminal device starts or restarts the first timer due to the second DCI or the third DCI, the first timer is not operated.

For example, "due to the second DCI or the third DCI" may include: due to the reception of the second DCI or the third DCI.

Wherein the first time may be the a-th symbol/slot/subframe/frame, etc. Wherein a is an integer greater than or equal to 0. For example, a is 1. The value of the first time/value of a/value of the first duration may be network device configured or preconfigured or protocol specified, and the application is not limited.

For example, the terminal device starts or restarts the first timer on the first symbol after receiving the second DCI or the third DCI.

The first timer not being started or restarted may include: the first timer is not started or restarted. Alternatively, "the first timer is not started or restarted" does not define whether the first timer is running.

Optionally, "after the terminal device receives the second DCI or the third DCI, the first timer is not started or restarted" may include one or more of the following: after the terminal equipment starts or restarts the first timer, the first timer is not started or restarted; after the terminal equipment starts or restarts the first timer due to the second DCI or the third DCI, the first timer is not started or restarted; after the terminal device receives the second DCI or the third DCI, the first timer is not started or restarted due to other transmissions (e.g., unicast new transmissions); after the terminal device starts or restarts the first timer, the first timer is not started or restarted due to other transmissions (e.g., unicast initial transmissions); after the terminal device starts or restarts the first timer due to the second DCI or the third DCI, the first timer is not started or restarted due to other transmissions (e.g., unicast initial transmissions).

Optionally, "after the terminal device receives the second DCI or the third DCI, the first timer is not started or restarted" may include one or more of the following:

(1) After the terminal equipment receives the second DCI or the third DCI, the first timer is not started or restarted when the terminal equipment successfully decodes the first data, or when the terminal equipment determines that the first condition is met, or when the terminal equipment stops/wants to stop the first timer;

(2) After the terminal equipment starts or restarts the first timer, the first timer is not started or restarted until the terminal equipment successfully decodes the first data, or until the terminal equipment determines that the first condition is met, or until the terminal equipment stops/wants to stop the first timer;

(3) After the first timer is started or restarted by the second DCI or the third DCI, the first timer is not started or restarted by the time when the first data is successfully decoded by the terminal equipment or the terminal equipment determines that the first condition is met or the terminal equipment stops/wants to stop the first timer;

(4) After the terminal device receives the second DCI or the third DCI, the first timer is not started or restarted by other transmissions (e.g., unicast initial transmissions) until the terminal device successfully decodes the first data, or until the terminal device determines that the first condition is met, or until the terminal device will/wants to stop the first timer;

(5) After the terminal device starts or restarts the first timer, the first timer is not started or restarted by other transmissions (e.g., unicast initial transmissions) until the terminal device successfully decodes the first data, or until the terminal device determines that the first condition is satisfied, or until the terminal device will/wants to stop the first timer;

(6) After the first timer is started or restarted by the second DCI or the third DCI, the first timer is not started or restarted by other transmissions (e.g., unicast initial transmissions) by the time the terminal device successfully decodes the first data, or by the time the terminal device determines that the first condition is met, or by the time the terminal device will/wants to stop the first timer.

In one possible scenario, if the first data includes a first LCID, the terminal device does not receive the first DCI transmitted by multicast, and the first timer is not running when the terminal device receives the second DCI or the third DCI, the terminal device stops the first timer.

In another possible case, if the first data includes the first LCID, the terminal device does not receive the first DCI transmitted by the multicast mode, and the terminal device does not start or restart the first timer after receiving the second DCI or the third DCI, the terminal device stops the first timer.

In still another possible case, the first data includes a first LCID, the terminal device does not receive the first DCI transmitted by the multicast manner, and the first timer is not operated when the terminal device receives the second DCI or the third DCI, and the first timer is not started or restarted after the terminal device receives the second DCI or the third DCI, so that the power consumption of the terminal device is reduced. The terminal device determines that the first data is multicast MTCH related data, and the first timer is not operated when the terminal device receives the second DCI or the third DCI, and the first timer is not started or restarted due to other transmissions after the terminal device receives the second DCI or the third DCI. If the terminal device receives the second DCI or the third DCI, it may misjudge the transmission corresponding to the second DCI or the third DCI as unicast initial transmission, and the terminal device starts or restarts the first timer, the operation of the first timer is caused by misjudging the transmission corresponding to the second DCI or the third DCI as unicast initial transmission by the terminal device, in this case, the network device does not start or restart the first timer by the second DCI or the third DCI, and the operation of the first timer of the terminal device will cause electricity consumption, so that the terminal device needs to stop the first timer.

Note that, the terminal device not receiving the first DCI may include/be replaced with: any one or more of condition 4, condition 5, and condition 6. For example, it may be understood that in the case where the condition 6 corresponds, or in the case where the condition 4 and/or the condition 5 corresponds, the first data includes the first LCID, and the terminal device may determine that the terminal device does not receive the first DCI.

In another alternative embodiment, the terminal device shortens the remaining run length of the first timer if the first condition is met.

Optionally, the first condition may further include one or more of:

condition 7: the terminal equipment receives the second DCI or the third DCI, and the first timer runs;

The first timer operation may include: the first timer is running.

Optionally, "the terminal device receives the second DCI or the third DCI, the first timer running" may include any one or more of the following:

(1) After/when the terminal equipment receives the second DCI or the third DCI, the first timer runs;

(2) After the terminal equipment receives the first duration or the first moment after receiving the second DCI or the third DCI, the first timer runs;

(3) When the terminal equipment starts or restarts the first timer, the first timer operates; or, when the terminal device starts or restarts the first timer due to the second DCI or the third DCI, the first timer operates.

It can be understood that, before the terminal device receives the second DCI or the third DCI, the first timer runs, which indicates that the terminal device starts or restarts the first timer due to the terminal device receiving other DCIs transmitted in the unicast mode before the terminal device receives the second DCI or the third DCI.

The terminal equipment determines that the first data is multicast MTCH related data, the first timer runs when the terminal equipment receives the second DCI or the third DCI, and the first timer is not started or restarted due to other transmission after the terminal equipment receives the second DCI or the third DCI. The terminal device receives the second DCI or the third DCI, and may misjudge the transmission corresponding to the second DCI or the third DCI as unicast initial transmission, and the terminal device starts or restarts the first timer, so that the running time of the first timer of the terminal device may be prolonged. In this case, the network device does not start or restart the first timer due to the second DCI or the third DCI, so that the terminal device needs to shorten the remaining operation duration of the first timer, thereby reducing the power consumption of the terminal device.

Optionally, after the terminal device receives the second DCI or the third DCI, the first timer is not started or restarted, which indicates that after the terminal device receives the second DCI or the third DCI, no other DCI transmitted through unicast is received, so that the first timer is not started or restarted. Thus, the start or restart of the first timer is due to the second DCI or the third DCI. However, the second DCI or the third DCI is actually the DCI scheduling the data retransmission by multicast, and the first timer should not be started or restarted. Therefore, the terminal equipment needs to shorten the residual operation time of the first timer so as to reduce the power consumption of the terminal equipment.

Optionally, the "remaining operation duration of the first timer shortened by the terminal device" is determined according to any one or more of the following: the terminal device starts or restarts the remaining operation duration STL of the first timer at the time point T1 of the first timer due to the reception of the second DCI or the third DCI, the time point T2 of the remaining operation duration of the first timer shortened due to the satisfaction of the first condition, and the preset duration YTL of the first timer.

For example, if STL is greater than (T2-T1), the remaining operation duration of the first timer shortened by the terminal device includes: the terminal device shortens the residual operation time of the first timer to STL- (T2-T1).

"(T2-T1)" is a time interval between a time point T2 of the remaining operation duration of the first timer shortened by the terminal device because the first condition is satisfied and a time point T1 of the first timer started or restarted by the terminal device because the reception of the second DCI or the third DCI.

For example, if the STL is less than or equal to (T2-T1), the remaining operation duration of the first timer shortened by the terminal device includes: the terminal device shortens the residual operation duration of the first timer to 0, or the terminal device stops the first timer.

For example, as shown in fig. 9, the terminal device starts or restarts the first timer at time t0 due to receiving the fourth DCI transmitted in the unicast manner, the preset duration of the first timer is 10s, and starts or restarts the first timer at time t1 due to receiving the second DCI or the third DCI (e.g., the terminal device misjudges the transmission corresponding to the second DCI or the third DCI as a unicast new transmission). the time t0 is smaller than the time t1, and the residual operation duration of the first timer is 6s when the time t1 is. Then, when the terminal device starts or restarts the first timer at time t1, the remaining operation duration of the first timer is prolonged from 6s to 10s, so that excessive power consumption is brought to the terminal device. At time t2, the terminal device determines that the first condition is met, the duration of the interval between t2 and t1 is 2s, and the remaining operation duration of the first timer at time t2 is 8s. At time t2, the terminal device may shorten the remaining operation duration of the first timer from 8s to 4s. Optionally, if the duration of the interval between t2 and t1 is greater than the remaining operation duration of the first timer at the time t1, the terminal device may stop the first timer, or the terminal device may shorten the remaining operation duration of the first timer to 0s.

Note that, the terminal device not receiving the first DCI may include/be replaced with: any one or more of condition 7, condition 5, and condition 6. For example, it may be understood that in the case where the condition 6 corresponds, or in the case where the condition 7, the condition 5, and the condition 6 correspond, the first data includes the first LCID, and the terminal device may determine that the terminal device does not receive the first DCI.

Optionally, if the second RNTI is a C-RNTI or the first RNTI is a first G-RNTI, the first condition may further include condition a. The condition a is as described above, and will not be described again.

It may be understood that, when the terminal device receives the third DCI or the second DCI under the condition corresponding to the condition a, the terminal device may consider the transmission corresponding to the third DCI or the second DCI as a unicast new transmission, so that the first timer may be started or restarted, but the network device may not start or restart the first timer due to the second DCI or the third DCI, the activation time of the unicast DRX of the terminal device is not aligned with the network device, and the activation time of the unicast DRX of the terminal device may be longer than that of the network device, so that unnecessary power consumption may be brought to the terminal device. Therefore, the terminal device may stop the first timer or shorten the remaining operation duration of the first timer under the first condition, so as to reduce the power consumption of the terminal device.

Optionally, the terminal device not receiving the first DCI may include/be replaced with: condition a.

It may be appreciated that, in the case that the condition a corresponds, the first data includes the first LCID, and the terminal device may determine that the terminal device does not receive the first DCI.

It can be seen that in the embodiment of the present application, the first condition is satisfied, and the terminal device performs control on the DRX associated with multicast to be in the active time, so that the terminal device can be prevented from being unable to receive other DCI transmitted in a multicast manner, so that the transmission reliability can be improved, and the transmission delay can be reduced. Alternatively, the activation time of DRX associated with multicast of the terminal device and other terminal devices receiving the multicast service and the network device may be aligned as much as possible. And the first condition is met, the terminal equipment executes to stop the first timer or shortens the residual operation time of the first timer, so that the energy saving of the terminal equipment is facilitated, and unnecessary reporting of the CSI and the SRS by the terminal equipment can be avoided.

Fourth, communication method 200.

An embodiment of the present application proposes a communication method 200, and fig. 10 is a schematic flow chart of the communication method 200. The communication method 200 is illustrated from the point of view of the terminal device side. The communication method 200 includes, but is not limited to, the steps of:

S201, the terminal equipment receives the fifth DCI and/or the second data, or the terminal equipment receives the second data on the first resource. For example, the network device transmits the fifth DCI and/or the second data transmitted in a unicast manner, or the network device transmits the second data on the first resource, correspondingly.

The fifth DCI is transmitted through a unicast mode.

The fifth DCI is transmitted in unicast, and may include/be understood as: the second RNTI scrambled first DCI or a fifth DCI associated with the second RNTI.

Wherein the fifth DCI is used to schedule the second data or the second data transmitted in a unicast manner.

For example, the fifth DCI and/or the second data is associated with the first HARQ process.

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

The first resource being/comprising resources/configuration resources associated with unicast may be understood as: the first resource is an SPS resource corresponding to unicast.

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

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

The second data comprises/is the first MAC PDU.

S202, the terminal equipment controls the DRX associated with the multicast to be in the activation time when the second condition is met.

The second condition includes: the second data includes a second LCID.

Wherein, the second LCID is an identification of DTCH. The first LCID is associated with a first multicast service. The first multicast service is associated with a first RNTI.

Optionally, the multicast-associated DRX is associated with a first multicast service and/or a first RNTI.

The description of "the terminal device controls the DRX in active time associated with the multicast" may refer to the content in S103-1, and will not be described herein.

It may be understood that after the terminal device successfully decodes the second data, it determines that the second data includes the second LCID, and determines that the second data includes data related to the first multicast service, then DCI and/or data related to the first multicast service may be transmitted in a multicast manner, and the terminal device may control DRX associated with multicast to be in an active time, so as to further receive the subsequent possible DCI and/or data, which is beneficial to improving reliability of multicast data transmission and reducing transmission delay.

It can be appreciated that the prior art may change with the evolution of the technical solution, and the technical solution provided in the present application is not limited to the provided prior art.

It is to be understood that different embodiments, or portions of the steps (e.g., any one or more steps) of different embodiments, may be combined with each other to form new embodiments. Optionally, some steps or any one or more steps in different embodiments may include optional steps in a certain embodiment, may also include optional steps in a certain embodiment, and may also include optional steps and optional steps in a certain embodiment, which is not limited in this application.

It is to be understood that the terms and/or descriptions of the various embodiments are consistent with and may be referred to each other unless specifically indicated as such and as logic conflicts.

It will be understood that the sequence of steps in the embodiments of the present application is not limited in this application.

It can be understood that the sequence of the judgment of the different conditions in the embodiment of the present application is not limited in this application.

It is understood that "post", "time" in this application is not strictly limited to the point in time.

Fifth, the communication device.

In order to implement the functions in the method provided in the embodiment of the present application, the communication device may include a hardware structure and/or a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

As shown in fig. 11, an embodiment of the present application provides a communication device 1100. The communication device 1100 is a component (e.g., an integrated circuit, a chip, etc.) of a terminal device. The communication device 1100 may also be other communication units for implementing the method in the method embodiments of the present application. The communication device 1100 may include: a communication unit 1101 and a processing unit 1102. Optionally, a storage unit 1103 may also be included.

In one possible design, one or more of the elements of FIG. 11 may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memories, and transceivers, to which embodiments of the present application are not limited. The processor, the memory and the transceiver can be arranged separately or integrated.

The communication apparatus 1100 has a function of implementing the terminal device described in the embodiments of the present application. For example, the communication apparatus 1100 includes modules or units or means (means) corresponding to the steps involved in executing the terminal device described in the embodiments of the present application by the terminal device, where the functions or units or means (means) may be implemented by software, or implemented by hardware, or implemented by executing corresponding software by hardware, or implemented by a combination of software and hardware. Reference is further made in detail to the corresponding description in the foregoing corresponding method embodiments.

In one possible design, a communication device 1100 may include: a processing unit 1102 and a communication unit 1101; the communication unit 1101 is configured to perform data/signaling transmission and reception;

A processing unit 1102, configured to satisfy a first condition, and perform one or more of:

In an alternative implementation manner, the processing unit 1102 controls the discontinuous reception DRX associated with the multicast to be at an active time, which is specifically used for: starting or restarting one or more of the following timers: a second timer, a third timer, a fourth timer;

the second timer is an inactive timer corresponding to the DRX associated with the multicast, the third timer is a duration timer corresponding to the DRX associated with the multicast, and the fourth timer is a retransmission timer corresponding to the DRX associated with the multicast.

In an alternative implementation, if the processing unit 1102 performs the controlling multicast associated discontinuous reception DRX to be active, the first condition further includes any one or more of: the multicast associated DRX is not in active time; after receiving the second DCI, the second timer is not started or restarted; after receiving the second DCI, the second timer is not started or restarted, the third DCI is used for scheduling the first data, and the third DCI precedes the second DCI.

In an alternative implementation, if the processing unit 1102 executes the stopping the first timer, the first condition further includes: receiving the second DCI or the third DCI, wherein the first timer is not operated; and/or after receiving the second DCI or the third DCI, the first timer is not started or restarted.

In an alternative implementation manner, if the processing unit 1102 performs the shortening the remaining operation duration of the first timer, the first condition further includes: receiving the second DCI or the third DCI, and running the first timer; and/or after receiving the second DCI or the third DCI, the first timer is not started or restarted.

In an alternative implementation, the second DCI is transmitted in a unicast manner including: the second DCI is scrambled by a cell-radio network temporary identifier C-RNTI.

In an alternative implementation, the first DCI is transmitted by multicast mode including: the first DCI is first RNTI scrambled; wherein the first RNTI is used for one or more of: the method is used for multicasting, scheduling multicast dynamic resources and scheduling retransmission resources of the multicast dynamic resources.

In an alternative implementation, the first LCID is associated with a first RNTI and/or the multicast-associated DRX is associated with a first RNTI; wherein the first RNTI is used for one or more of: the method is used for multicasting, scheduling multicast dynamic resources and scheduling retransmission resources of the multicast dynamic resources.

The embodiments of the present application and the embodiments of the above-mentioned method are based on the same concept, and the technical effects brought by the embodiments are the same, and the specific principles refer to the description of the above-mentioned embodiments, and are not repeated.

The embodiment of the application further provides a communication device 1200, and fig. 12 is a schematic structural diagram of the communication device 1200. The communication device 1200 may be a terminal device, or may be a chip, a chip system, a processor, or the like that supports the terminal device to implement the above method. The device can be used for realizing the method described in the method embodiment, and can be particularly referred to the description in the method embodiment.

The communications device 1200 may include one or more processors 1201. The processor 1201 may be a general purpose processor or a special purpose processor, or the like. For example, it may be a baseband processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or a central processing unit (central processing unit, CPU). The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, distributed Units (DUs) or Centralized Units (CUs), etc.), execute software programs, and process data of the software programs.

Optionally, the communications apparatus 1200 may include one or more memories 1202 on which instructions 1204 may be stored, which may be executed on the processor 1201, to cause the communications apparatus 1200 to perform the methods described in the method embodiments above. Optionally, the memory 1202 may also store data. The processor 1201 and the memory 1202 may be provided separately or may be integrated.

The Memory 1202 may include, but is not limited to, nonvolatile Memory such as Hard Disk Drive (HDD) or Solid State Drive (SSD), random access Memory (Random Access Memory, RAM), erasable programmable read-Only Memory (Erasable Programmable ROM, EPROM), ROM or portable read-Only Memory (Compact Disc Read-Only Memory, CD-ROM), and the like.

Optionally, the communication device 1200 may further include a transceiver 1205, an antenna 1206. The transceiver 1205 may be referred to as a transceiver unit, a transceiver circuit, etc. for implementing a transceiver function. The transceiver 1205 may include a receiver, which may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

The communication apparatus 1200 is a terminal device: the processor 1201 is configured to perform S103 in the communication method 100 and S202 in the communication method 200 described above; the transceiver 1205 is used to perform S101, S102 in the communication method 100 described above, and S201 in the communication method 200.

In another possible design, the processor 1201 may include a transceiver to implement the receive and transmit functions. For example, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or may be integrated. The transceiver circuit, interface or interface circuit may be used for reading and writing codes/data, or the transceiver circuit, interface or interface circuit may be used for transmitting or transferring signals.

In yet another possible design, the processor 1201 may optionally have instructions 1203 stored thereon, where the instructions 1203 run on the processor 1201, cause the communication apparatus 1200 to perform the method described in the method embodiment above. Instructions 1203 may be solidified in processor 1201, in which case processor 1201 may be implemented in hardware.

In yet another possible design, the communication device 1200 may include circuitry that may implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processors and transceivers described in embodiments of the present application may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency integrated circuits (radio frequency integrated circuit, RFIC), mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronics, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (complementary metal oxide semiconductor, CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiment may be the first device, but the scope of the communication device described in the embodiment of the present application is not limited thereto, and the structure of the communication device may not be limited by fig. 12. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication device may be:

(1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem;

(2) A set of one or more ICs, optionally including storage means for storing data, instructions;

(3) An ASIC, such as a modem;

(4) Modules that may be embedded within other devices;

for the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in fig. 13. Chip 1300 shown in fig. 13 includes a processor 1301 and an interface 1302. Wherein the number of processors 1301 may be one or more, and the number of interfaces 1302 may be a plurality. The processor 1301 may be a logic circuit, and the interface 1302 may be an input-output interface, an input interface, or an output interface. The chip 1300 may also include a memory 1303.

In one design, for the case where the chip is used to implement the functions of the terminal device in the embodiments of the present application:

The processor 1301 is configured to satisfy a first condition, and perform one or more of the following:

The implementation manner of the communication device 1100 described above may also be implemented by the communication device 1200 and the chip 1300 in the embodiments of the present application. Those of skill would further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.

The embodiments of the present application and the embodiments of the communication method 100 and the communication method 200 are based on the same concept, and the technical effects brought by the embodiments of the present application are the same, and the specific principles refer to the descriptions of the embodiments of the communication method 100 and the communication method 200, and are not repeated.

The present application also provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

The present application also provides a computer program product for storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

The present application also provides a computer program which, when run on a computer, implements the functions of any of the method embodiments described above.

The present application also provides a communication system comprising one or more network devices and one or more terminal devices. In another possible design, the system may further include other devices that interact with the network device and the terminal device in the solution provided in the present application.

In the above embodiments, the implementation may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., SSD), etc.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, the method comprising:

satisfying a first condition, performing one or more of:

2. The method of claim 1, wherein the controlling multicast associated discontinuous reception, DRX, at active time comprises:

starting or restarting one or more of the following timers: a second timer, a third timer, a fourth timer;

3. The method according to claim 1 or 2, wherein if the discontinuous reception, DRX, performing the control multicast association is active, the first condition further comprises any one or more of:

the multicast associated DRX is not in active time;

after receiving the second DCI, the second timer is not started or restarted;

after receiving a third DCI, the second timer is not started or restarted, the third DCI is used for scheduling the first data, and the third DCI precedes the second DCI.

4. A method according to any of claims 1-3, wherein if the discontinuous reception, DRX, performing the control multicast association is active, the first condition further comprises:

The second duration is less than the configuration duration of the second timer, and the second duration is a duration from the terminal equipment to successfully decode the first data after receiving the second DCI or the third DCI.

5. The method of any one of claims 1 to 4, wherein if the stopping the first timer is performed, the first condition further comprises:

receiving the second DCI or the third DCI, wherein the first timer is not operated; and/or the number of the groups of groups,

after receiving the second DCI or the third DCI, the first timer is not started or restarted.

6. The method according to any one of claims 1 to 4, wherein if the shortening of the remaining operation duration of the first timer is performed, the first condition further comprises:

receiving the second DCI or the third DCI, and running the first timer; and/or the number of the groups of groups,

7. The method of any one of claims 1 to 6, wherein the second DCI is transmitted in a unicast manner comprising:

the second DCI is scrambled by a cell-radio network temporary identifier C-RNTI.

8. The method of any one of claims 1 to 7, wherein the first DCI is transmitted by multicast comprising:

the first DCI is first RNTI scrambled;

wherein the first RNTI is used for one or more of: the method is used for multicasting, scheduling multicast dynamic resources and scheduling retransmission resources of the multicast dynamic resources.

9. The method according to any one of claim 1 to 8, wherein,

the first LCID is associated with a first RNTI and/or the multicast-associated DRX is associated with a first RNTI;

10. A communication device, the device comprising a processing unit configured to:

satisfying a first condition, performing one or more of:

11. The apparatus according to claim 10, wherein the processing unit is configured to control multicast associated discontinuous reception, DRX, to be active time, in particular for:

12. The apparatus according to claim 10 or 11, wherein if the processing unit performs the control multicast associated discontinuous reception, DRX, at active time, the first condition further comprises any one or more of:

the multicast associated DRX is not in active time;

after receiving the second DCI, the second timer is not started or restarted; or alternatively, the first and second heat exchangers may be,

13. The apparatus according to any of claims 10-12, wherein if the processing unit performs the controlling multicast associated discontinuous reception, DRX, at an active time, the first condition further comprises:

14. The apparatus of any one of claims 10 to 13, wherein if the processing unit executes the stop first timer, the first condition further comprises:

15. The apparatus according to any one of claims 10 to 12, wherein if the processing unit performs the shortening of the remaining operation duration of the first timer, the first condition further comprises:

16. The apparatus of any of claims 10 to 15, wherein the second DCI is transmitted via unicast comprising:

17. The apparatus of any one of claims 10 to 16, wherein the first DCI is transmitted by multicast comprising:

the first DCI is first RNTI scrambled;

18. The device according to any one of claims 10 to 17, wherein,

19. A communication device comprising a processor and a transceiver for communicating with other communication devices; the processor is configured to run a program to cause the communication device to implement the method of any one of claims 1 to 9.

20. A computer readable storage medium storing instructions which, when run on a computer, cause the method of any one of claims 1 to 9 to be performed.

21. A computer program product containing instructions which, when run on a computer, cause the method of any one of claims 1 to 9 to be performed.