CN117561790A

CN117561790A - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN117561790A
Application number: CN202180099623.7A
Authority: CN
Inventors: 张轶; 徐婧
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-09-23
Filing date: 2021-09-23
Publication date: 2024-02-13
Also published as: WO2023044655A1

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, so that services are timely scheduled. The method of wireless communication includes: the terminal equipment receives first information in a first time unit set; the first time unit set is used for the terminal equipment to monitor the PDCCH, and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, and more particularly, to a wireless communication method, terminal equipment and network equipment.

Background

Discontinuous reception (Discontinuous Reception, DRX) is an important means of saving power consumption for a connected terminal, and for some services, such as eXtended Reality (XR) or Cloud Game (CG), the service packets arrive with jitter (jitter), in which case the service packets may arrive before or after the DRX duration (DRX on duration) of the DRX cycle. If the traffic packet arrives before the DRX duration, it is necessary to wait until the DRX duration, and if the traffic packet arrives after the DRX duration, it is necessary to wait until the next DRX duration, which adds to the scheduling delay, which is not friendly for delay sensitive traffic such as XR or CG.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, so that services are timely scheduled.

In a first aspect, a method of wireless communication is provided, the method comprising:

the terminal equipment receives first information in a first time unit set;

the first time unit set is used for the terminal equipment to monitor the PDCCH, and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.

In a second aspect, there is provided a method of wireless communication, the method comprising:

the network equipment sends first information to the terminal equipment in a first time unit set;

In a third aspect, a method of wireless communication is provided, the method comprising:

the terminal equipment receives first configuration information; wherein,

the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment; or,

the first configuration information is used for configuring a DRX configuration for the terminal device within a DRX group, the one DRX configuration comprising at least two sets of DRX parameters.

In a fourth aspect, a method of wireless communication is provided, the method comprising:

the network equipment sends first configuration information to the terminal equipment; wherein,

In a fifth aspect, a terminal device is provided for performing the method in the first aspect.

Specifically, the terminal device comprises functional modules for performing the method in the first aspect described above.

In a sixth aspect, a network device is provided for performing the method in the second aspect.

In particular, the network device comprises functional modules for performing the method in the second aspect described above.

A seventh aspect provides a terminal device for performing the method of the third aspect.

Specifically, the terminal device comprises a functional module for performing the method in the third aspect described above.

In an eighth aspect, a network device is provided for performing the method in the fourth aspect.

Specifically, the network device comprises functional modules for performing the method in the fourth aspect described above.

In a ninth aspect, a terminal device is provided, comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect.

In a tenth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect described above.

In an eleventh aspect, a terminal device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the third aspect described above.

In a twelfth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the fourth aspect described above.

In a thirteenth aspect, there is provided an apparatus for implementing the method of any one of the first to fourth aspects.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any one of the first to fourth aspects as described above.

In a fourteenth aspect, there is provided a computer-readable storage medium storing a computer program that causes a computer to execute the method of any one of the first to fourth aspects.

In a fifteenth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to fourth aspects above.

In a sixteenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to fourth aspects above.

With the technical solutions of the first and second aspects, the terminal device is configured or instructed to monitor the PDCCH in the first set of time units, and the terminal device monitors the PDCCH in the second set of time units based on the indication of the first information received in the first set of time units. I.e. the second set of time units may be for traffic that the traffic packet arrives after the DRX duration, such that traffic that the traffic packet arrives after the DRX duration is scheduled in time.

With the technical solutions of the third aspect and the fourth aspect, the terminal device is configured with at least two DRX configurations in the DRX group, or the terminal device is configured with one DRX configuration in the DRX group, and the DRX configuration includes at least two sets of DRX parameters. Further, different DRX configurations in the at least two DRX configurations may correspond to different services or service qualities, or different sets of DRX parameters in the at least two sets of DRX parameters may correspond to different services or service qualities, so that all services of the terminal may be scheduled in time.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application apply.

Fig. 2 is a schematic diagram of a DRX cycle provided herein.

Fig. 3 is a schematic diagram of a candidate packet arrival jitter provided herein.

Fig. 4 is a schematic diagram of a duration corresponding to a drx-onduration timer provided in the present application capable of covering a jitter range.

Fig. 5 is a schematic diagram of a drx-onduration timer provided in the present application, where the duration corresponding to the drx-onduration timer cannot cover the jitter range.

Fig. 6 is a schematic flow chart diagram of a method of wireless communication provided in accordance with an embodiment of the present application.

Fig. 7 is a schematic diagram of content indicated by first information provided according to an embodiment of the present application.

Fig. 8 is a schematic flow chart of a DRX cycle provided according to an embodiment of the present application.

Fig. 9 is a schematic flow chart diagram of another method of wireless communication provided in accordance with an embodiment of the present application.

Fig. 10 is a schematic flow chart of another DRX cycle provided in accordance with an embodiment of the present application.

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

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

Fig. 13 is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

Fig. 14 is a schematic block diagram of another network device provided in accordance with an embodiment of the present application.

Fig. 15 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 16 is a schematic block diagram of an apparatus provided in accordance with an embodiment of the present application.

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

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, universal packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), internet of things (internet of things, ioT), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication systems, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

In some embodiments, the communication system in the embodiments of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) networking scenario.

In some embodiments, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in telemedicine (remote media), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city) or a wireless terminal device in smart home (smart home), a vehicle-mounted communication device, a wireless communication Chip/application specific integrated circuit (application specific integrated circuit, ASIC)/System-on Chip (SoC), or the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device or a base station (gNB) in an NR network, a network device in a PLMN network of future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. In some embodiments, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. In some embodiments, the network device may also be a base station located on land, in water, etc.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices, and in some embodiments, the communication system 100 may include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment.

In some embodiments, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which are not limited in this application.

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

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

The terminology used in the description section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. The terms "first," "second," "third," and "fourth" and the like in the description and in the claims of this application and in the drawings, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the embodiment of the present application, the "pre-defining" or "pre-configuring" may be implemented by pre-storing a corresponding code, a table or other manners that may be used to indicate relevant information in a device (including, for example, a terminal device and a network device), and the specific implementation manner is not limited in this application. Such as predefined may refer to what is defined in the protocol.

In this embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in this application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

To facilitate a better understanding of embodiments of the present application, DRX relevant to the present application is described.

The DRX function is used to control the physical downlink control channel (Physical Downlink Control Channel, PDCCH) monitoring behaviour of the terminal. As shown in fig. 2, the DRX mechanism in the radio resource control (Radio Resource Control, RRC) connected state configures the terminal device with a DRX cycle consisting of a starting DRX duration (DRX on duration) and a potential sleep period (opportunity for DRX). The DRX duration may be understood as an active period in which the terminal needs to monitor the PDCCH, and in a potential sleep period, the terminal device may not monitor the PDCCH (PDCCH except for type 0 (type-0), type 1 (type-1), type 2 (type-2) search spaces) to reduce power consumption.

The RRC controls DRX operation of the terminal by configuring the following parameters:

DRX duration timer (DRX-onduration timer): a time (the duration at the beginning of a DRX cycle) for continuously monitoring PDCCH from the start of the DRX period;

DRX slot offset (DRX-SlotOffset): slot level offset of DRX active period (the delay before starting the DRX-onduration timer);

DRX inactivity timer (DRX-inactivity timer): when the terminal equipment successfully decodes a PDCCH indicating primary Uplink (UL) or Downlink (DL) data, continuing to activate the PDCCH for a time (the duration after the PDCCH occasion in which a PDCCH indicates a new UL or DL transmission for the MAC entity);

DRX long cycle start offset (DRX-longcycletartoffset): the period of the DRX cycle and the starting subframe (the Long DRX cycle and DRX-StartOffset which defines the subframe where the Long and Short DRX cycle starts);

downlink DRX hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) Round Trip Time (RTT) timer (DRX-HARQ-RTT-TimerDL) (per downlink HARQ process): a medium access control (Media Access Control, MAC) entity expects a minimum duration (the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity) before DL allocation for HARQ retransmission;

Downlink DRX retransmission timer (DRX-retransmission timer dl) (each HARQ process except for the broadcast process): the longest duration before the DL retransmission is received (the maximum duration until a DL retransmission is received);

uplink DRX HARQ RTT timer (DRX-HARQ-RTT-TimerUL) (per uplink HARQ process): the MAC entity expects the shortest duration (the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity) before UL HARQ retransmission authorization;

uplink DRX retransmission timer (DRX-retransmission timer ul) (per uplink HARQ process): a maximum duration (the maximum duration until a grant for UL retransmission is received) before receiving UL retransmission grant;

it should be noted that, the drx-HARQ-RTT-TimerDL and drx-retransmission TimerDL may be understood together, that is, when the terminal fails to demodulate initially, the PDCCH may not be monitored during operation of the drx-HARQ-RTT-TimerDL, because a certain time is required for the base station to schedule retransmission, and after the drx-HARQ-RTT-TimerDL times out, a drx-retransmission TimerDL timer is started, during which the terminal monitors the PDCCH for scheduling retransmission. Furthermore, drx-HARQ-RTT-TimerDL and drx-retransmission TimerDL are understood the same.

In some embodiments, the terminal device may determine the DRX start offset according to at least one of:

system frame number (System Frame Number, SFN), subframe number, DRX long cycle (DRX-LongCycle), DRX short cycle (DRX-ShortCycle).

Specifically, for example, the terminal device is configured to perform the following processing in subframes: [ (sfn×10) +subframe number ] mod (DRX long cycle) or DRX short cycle ] =drx start offset (DRX-StartOffset), and after the slot indicated by DRX slot offset (DRX-SlotOffset), DRX-onduration timer is turned on.

In some embodiments, the selectable values of the DRX cycle include: {2ms,3ms,4ms,5ms,6ms … }, {10ms,20ms,32ms, s40ms,60ms,64ms … }, the first set is the value of the DRX short period and the second set is the value of the DRX long period.

In some embodiments, one terminal configures at most two DRX groups, and when RRC signaling does not configure a secondary DRX group (secondary DRX group), all cells belong to one DRX group, and when RRC configures two DRX groups, each serving cell belongs to only one of the DRX groups. The parameters that can be respectively configured in the two DRX groups are as follows: the DRX-onduration timer and DRX-incavitytimer, other parameter configurations are shared in both DRX groups.

When DRX is configured, for a serving cell in one DRX group, the Active time (Active time) includes the following times:

the configured drx-onDurationTimer or drx-incaactytimer is running;

DRX-retransmission timer dl or DRX-retransmission timer ul run in any cell within the DRX group;

the scheduling request (Scheduling Request, SR) is sent in suspension (pending);

a random access contention resolution timer (ra-contentioresolute) or a message B in random access (msgB) response window information (msgB-response window) timer running period;

after successfully receiving a random access response corresponding to a random access preamble not selected in the contention-based random access for the medium access control (Media Access Control, MAC) entity, a PDCCH corresponding to a cell radio network temporary identity (Cell Radio Network Temporary Identity, C-RNTI) of the MAC entity indicating a new transmission has not been received.

If one DRX group is in Active Time: the terminal monitors the PDCCH on the serving cell within the DRX group.

To facilitate a better understanding of embodiments of the present application, search space collection groups (Search Space Set Group, SSSG) relevant to the present application are described.

In a power saving (power saving) mechanism under DRX activation time, a terminal is triggered to switch under different terminal behaviors through downlink control information (Downlink Control Information, DCI), where the different terminal behaviors may include: 1) skip (skip) PDCCH, 2) monitor PDCCH for sssg#0, 3) monitor PDCCH for sssg#1, 4) monitor PDCCH for sssg#2. The terminal behavior 1 is the most energy-saving state, i.e. skips PDCCH monitoring, which however has a certain influence on scheduling, increases scheduling delay, and in addition, the terminal can monitor PDCCHs (sssg#0 to sssg#2) on different SSSGs, and parameters of different SSSG cable configurations can be different, such as a monitoring period, PDCCH candidates, etc., if energy saving is desired, the PDCCH can be monitored on a sparser SSSG, and if timely scheduling is desired, the PDCCH can be monitored on a denser SSSG.

To facilitate a better understanding of embodiments of the present application, XR/CG associated with the present application is described.

One of the main services of XR/CG is video stream (video stream) service, and a more remarkable service feature is that XR/CG is not strictly periodic service, and service arrival is jittery on a periodic basis. As shown in fig. 3, the XR/CG service period is 16.67ms, but the service does not necessarily arrive on time after a period of 16.67ms interval, but with jitter (jitter). Jitter can be modeled as a truncated gaussian distribution with values ranging from [ -4,4] ms (baseline) or [ -5,5] ms (optional).

In the commercialization of XR or CG, battery life is becoming an important factor of increasing concern, which requires that XR or CG services while guaranteeing service requirements/service metrics, save energy consumption as much as possible. With the development of 5G, more frequent and larger data traffic demands, the energy consumption occupied by the communication module is not small. DRX is an important means for saving power consumption for a connected terminal. However, due to the effect of XR or CG service jitter, the network side needs to configure the drx-onduration timer long enough to cover the jitter (coverage jitter) value range, as shown in fig. 4, in this case, whenever a service packet arrives, it can be scheduled in time. However, the terminal is required to monitor the PDCCH for a long time, and the power saving effect is greatly reduced. However, if the DRX-onduration timer is configured to be relatively short, as shown in fig. 5, the service packet may arrive before or after the DRX duration (DRX on duration), if it arrives before, it needs to wait until the DRX on duration to be scheduled, if it arrives after, it needs to wait until the next DRX on duration to be scheduled, which clearly increases the scheduling delay, which is not friendly for time delay sensitive services such as XR/CG.

Based on the above problems, the present application proposes a solution for monitoring PDCCH, so that service is scheduled in time.

The technical scheme of the present application is described in detail below through specific embodiments.

Fig. 6 is a schematic flow chart of a method 200 of wireless communication according to an embodiment of the present application, as shown in fig. 6, the method 200 of wireless communication may include at least some of the following:

s210, the network equipment sends first information to the terminal equipment in a first time unit set; the first time unit set is used for the terminal equipment to monitor the PDCCH, and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set;

s220, the terminal device receives the first information in the first time unit set.

It will be appreciated that the first set of time units comprises one or more time units and similarly the second set of time units comprises one or more time units.

That is, in the embodiment of the present application, the terminal device listens to the PDCCH in the first time unit set.

In some embodiments, the network device configures or instructs the terminal device to listen to PDCCH for the first set of time units.

Specifically, for example, the network device configures or instructs the terminal device to monitor PDCCH in the first time unit set through at least one of system message, DCI, MAC CE, RRC.

In this embodiment of the present application, the terminal device monitors a PDCCH in the first time unit set, acquires a signaling carrying the first information from the monitored PDCCH, and acquires the first information through the signaling carrying the first information.

In some embodiments, the first set of Time units includes Time units within an Active Time (Active Time) corresponding to the DRX configuration, or the first set of Time units includes Time units during which a DRX duration timer (DRX duration timer) runs.

In some embodiments, the second set of time units includes at least time units other than DRX activation time. In some embodiments, the second set of time units may also include some or all of the time units in the first set of time units. That is, the second set of time units extends backwards on the basis of the first set of time units, more including some time units.

In some embodiments, the time units included in the second set of time units are different from the time units corresponding to the DRX activation time, or the time units included in the second set of time units do not include the time units corresponding to the DRX activation time.

In the embodiment of the present application, the terminal device may monitor the PDCCH in the second time unit set based on the first information.

In particular, for example, in the case where the time configuration of the DRX-onduration timer is relatively short, as shown in fig. 5, if a service packet or a data packet arrives after the DRX duration (DRX on duration), timely scheduling can be obtained in the second time unit set, which is beneficial for efficient transmission of time delay sensitive services such as XR/CG.

In some embodiments, the first information is carried by at least one of:

downlink control information (Downlink Control Information, DCI), medium access control element (Media Access Control Control Element, MAC CE), radio resource control (Radio Resource Control, RRC).

Specifically, for example, assuming that the first information is carried by DCI, the first information may be an element or field in the DCI. And are similarly carried in other ways, and are not described in detail herein.

It should be noted that, the first information may also be carried through other signaling, which is not limited in this application.

In some embodiments, the time units in the first set of time units are consecutive with the time units in the second set of time units. For example, the last time unit in the first set of time units is next to the first time unit in the second set of time units, i.e., the last time unit in the first set of time units is two consecutive time units to the first time unit in the second set of time units.

In some embodiments, the time units in the first set of time units are non-contiguous with the time units in the second set of time units. For example, there is another time cell interval between the last time cell in the first set of time cells and the first time cell in the second set of time cells.

In some embodiments, the second set of time units may include some or all of the time units in the first set of time units, i.e., the second set of time units and the first set of time units comprise some or all of the time units that are the same.

In some embodiments, the first information is further used to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

an offset of a first time cell in the second set of time cells relative to a reference time cell;

an offset of a last time unit in the second set of time units relative to a reference time unit;

the number of time units comprised by the second set of time units;

the second set of time units includes a number of time units starting from a first time unit after the first set of time units;

SSSG in the second set of time units that need to be listened to.

It should be noted that, the Search Space Set Group (SSSG) is used to identify a set of at least one search space having a specific parameter (such as a monitoring period, a PDCCH candidate, etc.) that the terminal device needs to monitor, and at the DRX activation time, the terminal device may monitor the PDCCH on the Search Space Set Group (SSSG).

In some embodiments, in the second time unit set, the terminal device may monitor PDCCH on one or more SSSGs (e.g., sssg#0-sssg#2), and parameters of different SSSG index configurations may be different, such as a monitoring period, PDCCH candidates, and so on. If it is desired to save energy as much as possible, the terminal device may monitor PDCCH on the sparser SSSG; if timely scheduling is desired, the terminal device may monitor the PDCCH on a denser SSSG.

In some embodiments, the SSSG required to be listened to in the second set of time units includes a default SSSG (default SSSG) required to be listened to in the second set of time units.

It should be noted that, the default SSSG is an SSSG that needs to be monitored by default after the terminal enters the DRX activation time; and/or, the default SSSG is the SSSG that needs to fall back after the timer times out when the terminal monitors other SSSGs.

In some embodiments, in the second set of time units, the terminal device may also receive other DCI for indicating SSSG switching. For example, a switch from sssg#0 to sssg#1 may be instructed. For another example, a switch from a sparser SSSG to a denser SSSG may be indicated.

Specifically, for example, the first information is further used to indicate: the second set of time units includes a number of time units starting from a first time unit after the first set of time units. In this case, the content indicated by the first information may be as shown in fig. 7, for example. Of course, the specific number of time units included in the first time unit set and the second time unit set in fig. 7 is merely an example, and is not limited to this application.

In some embodiments, the first information includes at least one of:

indication information for indicating a first time cell in the second set of time cells;

indication information for indicating a last time unit in the second set of time units;

indication information for indicating an offset of a first time unit in the second set of time units relative to a reference time unit;

Indication information for indicating an offset of a last time unit in the second set of time units relative to a reference time unit;

indication information for indicating the number of time units comprised by the second set of time units;

indication information for indicating the number of time units included in the second time unit set starting from the first time unit after the first time unit set;

indication information for indicating the SSSG to be listened to in the second time unit set.

In some embodiments, the reference time unit is configured by the network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by a hybrid automatic repeat request-acknowledgement (Hybrid Automatic Repeat request Acknowledgement, HARQ-ACK) corresponding to the first information.

In particular, for example, in case the reference time unit is the first time unit after the first set of time units, the reference time unit may be the first time unit after the last time unit in the first set of time units.

In some embodiments, the first information may also be used to indicate the reference time unit, or the first information includes indication information for indicating the reference time unit.

In some embodiments, the default SSSG to be listened to in the first set of time units is different from the default SSSG to be listened to in the second set of time units.

In some embodiments, the default SSSG to be listened to in the first set of time units is the same as the default SSSG to be listened to in the second set of time units.

In some embodiments, the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively configured or indicated by the network device, or the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively agreed by a protocol.

In some embodiments, the terminal device listens to the PDCCH in the third set of time units, or the terminal device does not listen to the PDCCH any more in the third set of time units; the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, where the first time unit is the last time unit occupied by the first information.

It should be noted that, the third time unit set does not include the first time unit, and the third time unit set includes the last time unit included in the first time unit set, that is, the third time unit set is a left-open-right interval.

Specifically, for example, the terminal device monitors the PDCCH in the third time unit set, so that scheduling of services other than XR/CG, such as group public service, can be ensured.

In particular, for another example, the terminal device does not monitor the PDCCH in the third time unit set, and is more energy-saving for the user with only the delay sensitive service (such as the XR service or the CG service).

In some embodiments, the first information includes first indication information, where the first indication information is used to instruct the terminal device to monitor the PDCCH in the third time unit set, or the first indication information is used to instruct the terminal device not to monitor the PDCCH any more in the third time unit set.

Specifically, the terminal device monitors the PDCCH in the third time unit set according to the first indication information, or the terminal device does not monitor the PDCCH in the third time unit set according to the first indication information. Or the terminal equipment determines to monitor the PDCCH in the third time unit set according to the first indication information, or the terminal equipment determines not to monitor the PDCCH in the third time unit set any more according to the first indication information.

Assuming that the first information is carried by DCI, for example, the first information may be an element in DCI, and the first indication information may be a field or field in the element. For another example, the first information may be one field in DCI, and the first indication information may be one field or a subfield in the field. The first information may be a field in the DCI, and the first indication information may be a field or sub-field in the field. And are similarly carried in other ways, and are not described in detail herein.

In some embodiments, the terminal device listens to the PDCCH in the third time unit set according to the information configured by the network device or the information agreed by the protocol, or the terminal device does not listen to the PDCCH in the third time unit set according to the information configured by the network device or the information agreed by the protocol.

In some embodiments, the terminal device determines to monitor the PDCCH in the third time unit set according to the information configured by the network device or the information agreed by the protocol, or the terminal device determines to not monitor the PDCCH in the third time unit set any more according to the information configured by the network device or the information agreed by the protocol.

In some embodiments, in a case that the terminal device listens to the PDCCH in the third time unit set, the network device may send the PDCCH to the terminal device in the third time unit set, or may not send the PDCCH to the terminal device in the third time unit set.

In some embodiments, the network device does not send PDCCH to the terminal device in the third set of time units if the terminal device is no longer listening to PDCCH in the third set of time units.

In some embodiments, the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol. In some embodiments, the time unit may also be an absolute time or a relative time, e.g., the time unit is milliseconds (ms) or microseconds (μs).

The time unit may be a time unit in the first time unit set, a time unit in the second time unit set, a time unit in the third time unit set, the reference time unit, or the first time unit.

In some embodiments, the signaling carrying the first information may be a DCI format that is newly defined, a DCI format used for scheduling a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH)/physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), or a DCI format not used for scheduling PDSCH/PUSCH.

Specifically, as shown in fig. 8, for example, the terminal device receives a DRX configuration on the network side, where the DRX configuration includes parameters such as a DRX cycle (DRX long cycle) or a DRX short cycle (DRX short cycle), a DRX duration timer (DRX-onduration timer), and the terminal device listens to the PDCCH during the DRX duration (DRX on duration), that is, the DRX on duration is the first time unit set. During the first DRX on duration, a data packet arrives, so that the data packet can be timely scheduled without triggering the second time unit set to monitor the PDCCH. During the second DRX on duration operation, no data packet arrives, and the data packet arrives after the DRX-onduration timer operation is finished, the network device sends first information (which may be carried by DCI or MAC CE or RRC) in the first time unit set, where the first information is used to instruct the terminal device to monitor the PDCCH in the second time unit set; the terminal device may continue to monitor the PDCCH or may not monitor the PDCCH any more in the third set of time units.

Thus, in the embodiments of the present application, the terminal device is configured or instructed to listen to the PDCCH in a first set of time units, and the terminal device is configured or instructed to listen to the PDCCH in a second set of time units based on the indication of the first information received in the first set of time units. I.e. the second set of time units may be for traffic that the traffic packet or data packet arrives after the DRX duration, such that traffic that the traffic packet or data packet arrives after the DRX duration is scheduled in time.

Further, the terminal device monitors the PDCCH in the third time unit set, so that scheduling of some non-delay sensitive services can be ensured. Or the terminal equipment does not monitor the PDCCH in the third time unit set, so that the energy is saved for the user with only delay sensitive service (such as XR service or CG service).

Fig. 9 is a schematic flow chart of a method 300 of wireless communication according to an embodiment of the present application, as shown in fig. 9, the method 300 of wireless communication may include at least some of the following:

s310, the network equipment sends first configuration information to the terminal equipment; the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment; or, the first configuration information is used for configuring a DRX configuration for the terminal device in a DRX group, where the DRX configuration includes at least two sets of DRX parameters;

S320, the terminal equipment receives the first configuration information sent by the network equipment.

In the embodiment of the application, the terminal equipment can monitor the PDCCH based on the first configuration information.

In some embodiments, the terminal device is configured with at least one DRX group. For example, the network device configures the terminal device with at least one DRX group through RRC signaling. For example, when the RRC signaling does not configure the secondary DRX group (secondary DRX group), all cells belong to one DRX group, and when the RRC configures two DRX groups, each serving cell belongs to only one of the DRX groups. The parameters that can be respectively configured in the two DRX groups are as follows: the DRX-onduration timer and DRX-incavitytimer, other parameter configurations are shared in both DRX groups.

The present application is described by taking only one DRX group as an example, and the configuration manners of other DRX groups are the same, which is not described herein again.

In some embodiments, different DRX configurations of the at least two DRX configurations may correspond to different traffic or quality of service, or different sets of DRX parameters of the at least two sets of DRX parameters may correspond to different traffic flows or quality of service (Quality of Service, qoS), thereby enabling all traffic of the terminal to be scheduled in time.

Specifically, for example, the at least two DRX configurations include a first DRX configuration and a second DRX configuration, where the first DRX configuration corresponds to enhanced mobile ultra-wideband (Enhance Mobile Broadband, eMBB) traffic, or the first DRX configuration corresponds to QoS corresponding to eMBB traffic; and/or, the second DRX configuration corresponds to XR and/or CG traffic, or the second DRX configuration corresponds to QoS corresponding to XR and/or CG traffic.

For another example, the at least two sets of DRX parameters include a first set of DRX parameters and a second set of DRX parameters; wherein, the first set of DRX parameters corresponds to eMBB service, or the first set of DRX parameters corresponds to QoS corresponding to eMBB service; and/or, the second set of DRX parameters corresponds to XR and/or CG service, or the second set of DRX parameters corresponds to QoS corresponding to XR and/or CG service.

In some embodiments, any one of the at least two sets of DRX parameters includes, but is not limited to, at least one of:

DRX cycle parameter, DRX duration timer (DRX-onduration timer), DRX inactivity timer (DRX-InactyTimer), DRX slot offset (DRX-SlotOffset), DRX long cycle start offset (DRX-longCyclostartOffset), downlink DRX retransmission timer (DRX-retransmission TimerDL), uplink DRX retransmission timer (DRX-retransmission TimerUL), downlink DRX HARQ RTT timer (DRX-HARQ-RTT-TimerDL), uplink DRX HARQ RTT timer (DRX-HARQ-RTT-TimerUL).

The types of parameters included in different sets of DRX parameters in the at least two sets of DRX parameters are the same, but values of some or all of the parameters included in different sets of DRX parameters are different.

In some embodiments, the DRX configuration of the at least two DRX configurations includes, but is not limited to, at least one of:

Note that, the parameter types included in different DRX configurations in the at least two DRX configurations are the same, but the values of some or all parameters included in different DRX configurations are different.

In some embodiments, the DRX cycle parameters may include a DRX long cycle (DRX-LongCycle) and/or a DRX short cycle (DRX-ShortCycle).

In some embodiments, in a case where the first configuration information is used to configure at least two DRX configurations for the terminal device within a DRX group, the activation time within the DRX group includes an activation time corresponding to a first DRX configuration of the at least two DRX configurations and an activation time corresponding to a second DRX configuration of the at least two DRX configurations.

In some embodiments, in a case that the first configuration information is used to configure one DRX configuration for the terminal device in a DRX group, and the one DRX configuration includes at least two sets of DRX parameters, an activation time in the DRX group includes an activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters and an activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters.

In some embodiments, the terminal device listens to the PDCCH at an activation time within the DRX group.

In some embodiments, the network device may or may not send PDCCH to the terminal device at the activation time within the DRX group.

In some embodiments, in a case where the first configuration information is used to configure at least two DRX configurations for the terminal device within a DRX group, an activation time corresponding to a first DRX configuration of the at least two DRX configurations is determined based on the second information, and/or an activation time corresponding to a second DRX configuration of the at least two DRX configurations is determined based on the second information and the third information.

In some embodiments, in a case that the first configuration information is used to configure one DRX configuration for the terminal device within a DRX group, and the one DRX configuration includes at least two sets of DRX parameters, an activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on the second information; and/or, determining the activation time corresponding to the second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information.

In some embodiments, the second information includes at least one of:

a DRX duration timer or a DRX deactivation timer (DRX-onDurationTimer or DRX-InactivityTimer configured for the DRX group is running) corresponding to the DRX group;

a downlink DRX retransmission timer or an uplink DRX retransmission timer (DRX-RetransmissionTimerDL or DRX-RetransmissionTimerUL is running on any Serving Cell in the DRX group) corresponding to any serving cell in the DRX group;

a random access contention resolution timer (ra-contentionresolution timer) or message B response window information (msgB-response window) in random access (ra-ContentionResolutionTimer or msgB-ResponseWindow is running);

a scheduling request is sent on a physical uplink control channel (Physical Uplink Control Channel, PUCCH) and in a suspended state (a Scheduling Request is sent on PUCCH and is pending);

after successfully receiving a random access response corresponding to a random access preamble, the PDCCH corresponding to the C-RNTI of the MAC entity indicating the new transmission has not been received, wherein the random access preamble is a random access preamble not selected in contention-based random access for the MAC entity (a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble).

In some embodiments, the third information is used to adjust an activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used to adjust a parameter value included in the second DRX configuration or the second set of DRX parameters.

In some embodiments, the third information is sent by the network device through higher layer signaling and/or physical layer downlink control information.

In some embodiments, two sets of DRX configurations are configured in one DRX group, the DRX activation time of one set of DRX configurations is adjusted based on the scheme in the method 200 for wireless communication, the activation time of the other set of DRX configurations is not affected, and the terminal device performs PDCCH monitoring in the union of the activation times of the two sets of DRX configurations.

Specifically, for example, the network device configures at least two DRX configurations within each DRX group for the terminal device, corresponding to different traffic/QoS, e.g., one DRX configuration corresponds to traffic 1/QoS1 (conventional eMBB traffic), e.g., DRX configuration 1 in fig. 10; another DRX configuration corresponds to traffic 2/QoS2 (e.g., XR/CG traffic), such as DRX configuration 2 in fig. 10. After the DRX configuration 2 is configured, dynamic/semi-static adjustment may be performed through downlink control information, MAC CE, RRC signaling (not reconfiguration), as in the DRX configuration 2 in fig. 10, where the terminal device receives signaling for indicating the second time unit set, and in this case, the terminal device listens to the PDCCH in the second time unit set. For one DRX group, the terminal equipment takes the sum of the activation time of the DRX configuration 1 and the activation time of the DRX configuration 2 as the total activation time, and monitors PDCCH.

Thus, in an embodiment of the present application, the terminal device is configured with at least two DRX configurations within a DRX group, or the terminal device is configured with one DRX configuration within a DRX group, and the DRX configuration comprises at least two sets of DRX parameters. Further, different DRX configurations of the at least two DRX configurations may correspond to different services or service qualities, or different sets of DRX parameters of the at least two sets of DRX parameters may correspond to different services or service qualities, so that all services of the terminal may be scheduled in time.

The method embodiments of the present application are described in detail above with reference to fig. 6 to 10, and the apparatus embodiments of the present application are described in detail below with reference to fig. 11 to 14, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 11 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in fig. 11, the terminal apparatus 400 includes:

a first communication unit 410 for receiving first information in a first set of time units;

the first time unit set is used for the terminal equipment to monitor a Physical Downlink Control Channel (PDCCH), and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.

In some embodiments, the time units in the first set of time units are consecutive with the time units in the second set of time units; alternatively, the time units in the first set of time units are discontinuous with the time units in the second set of time units.

In some embodiments, the second set of time units includes some or all of the time units in the first set of time units.

In some embodiments, the first information is used to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

the number of time units comprised by the second set of time units;

the set of search spaces to be listened to in the second set of time units SSSG.

In some embodiments, the SSSG required to be listened to in the second set of time units comprises a default SSSG required to be listened to in the second set of time units.

In some embodiments, the reference time unit is configured by the network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by the hybrid automatic repeat request-acknowledgement HARQ-ACK corresponding to the first information.

In some embodiments, the default SSSG required to be listened to in the first time unit set is different from the default SSSG required to be listened to in the second time unit set, or the default SSSG required to be listened to in the first time unit set is the same as the default SSSG required to be listened to in the second time unit set.

In some embodiments, the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively configured or indicated by the network side, or the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively agreed by a protocol.

In some embodiments, the terminal device 400 further comprises:

a second communication unit 420, configured to monitor the PDCCH in the third time unit set, or configured to not monitor the PDCCH in the third time unit set;

the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, where the first time unit is the last time unit occupied by the first information.

In some embodiments, the second communication unit 420 is specifically configured to:

monitoring the PDCCH in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol, or not monitoring the PDCCH in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol.

In some embodiments, the first information is carried by at least one of:

Downlink control information DCI, medium access control element MAC CE, radio resource control RRC.

In some embodiments, the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol.

In some embodiments, the first set of time units corresponds to time units within a discontinuous reception, DRX, activation time, and the second set of time units includes time units outside of the DRX activation time.

In some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip.

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

Fig. 12 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in fig. 12, the network device 500 includes:

a communication unit 510, configured to send first information to a terminal device in a first time unit set;

In some embodiments, the first information is used to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

the number of time units comprised by the second set of time units;

In some embodiments, the first information includes first indication information, where the first indication information is used to instruct the terminal device to monitor the PDCCH in the third time unit set, or the first indication information is used to instruct the terminal device not to monitor the PDCCH any more in the third time unit set;

wherein the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, the first time unit being a last time unit occupied by the first information.

In some embodiments, the network device 500 further comprises: a processing unit 520, wherein,

the processing unit 520 is configured to determine that the PDCCH is allowed to be transmitted to the terminal device in the third time unit set according to the information of the network device configuration or the information of the protocol assignment, or the processing unit 520 is configured to determine that the PDCCH is not transmitted to the terminal device in the third time unit set any more according to the information of the network device configuration or the information of the protocol assignment.

In some embodiments, the first information is carried by at least one of:

In some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method 200 shown in fig. 6, which is not described herein for brevity.

Fig. 13 shows a schematic block diagram of a terminal device 600 according to an embodiment of the present application. As shown in fig. 13, the terminal apparatus 600 includes:

A first communication unit 610 for receiving first configuration information; wherein,

the first configuration information is used for configuring at least two DRX configurations in a discontinuous reception DRX group for the terminal equipment; or,

In some embodiments, any one of the at least two sets of DRX parameters includes at least one of:

DRX cycle parameter, DRX duration timer DRX-onDurationTimer, DRX deactivation timer DRX-InactivityTimer, DRX slot offset DRX-SlotOffset, DRX long cycle start offset DRX-longCyclostartOffset, downlink DRX retransmission timer DRX-retransmission timer DRX-retransmission timer UL, downlink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerDL, uplink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerUL.

In some embodiments, in a case where the first configuration information is used to configure at least two DRX configurations within a DRX group for the terminal device, the activation time within the DRX group includes an activation time corresponding to a first DRX configuration of the at least two DRX configurations and an activation time corresponding to a second DRX configuration of the at least two DRX configurations.

In some embodiments, the terminal device 600 further comprises:

a second communication unit 620, configured to monitor a physical downlink control channel PDCCH at an activation time in the DRX group.

In some embodiments, in a case where the first configuration information is used to configure at least two DRX configurations for the terminal device within a DRX group, an activation time corresponding to a first DRX configuration of the at least two DRX configurations is determined based on the second information, and/or an activation time corresponding to a second DRX configuration of the at least two DRX configurations is determined based on the second information and the third information; or,

in the case that the first configuration information is used for configuring one DRX configuration in a DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on the second information; and/or, determining the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information;

Wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell corresponds to a downlink DRX retransmission timer or an uplink DRX retransmission timer in the DRX group; a random access contention resolution timer or a message B in random access responds to window information msgB-response window; a scheduling request is sent on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) corresponding to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity, which indicates new transmission, is not received yet, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

the third information is used for adjusting the activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used for adjusting the parameter values included in the second DRX configuration or the second set of DRX parameters.

It should be understood that the terminal device 600 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 600 are respectively for implementing the corresponding flow of the terminal device in the method 300 shown in fig. 9, which is not described herein for brevity.

Fig. 14 shows a schematic block diagram of a network device 700 according to an embodiment of the present application. As shown in fig. 14, the network device 700 includes:

a first communication unit 710, configured to send first configuration information to a terminal device; wherein,

Wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell corresponds to a downlink DRX retransmission timer or an uplink DRX retransmission timer in the DRX group; a random access contention resolution timer or a message B in random access responds to window information msgB-response window; the terminal equipment sends a scheduling request on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) corresponding to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity, which indicates new transmission, is not received yet, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

In some embodiments, the network device 700 further comprises:

and the second communication unit 720 is configured to send the third information to the terminal device through higher layer signaling and/or physical layer downlink control information.

It should be understood that the network device 700 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 700 are respectively for implementing the corresponding flow of the network device in the method 300 shown in fig. 9, and are not further described herein for brevity.

Fig. 15 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device 800 shown in fig. 15 comprises a processor 810, from which the processor 810 may call and run a computer program to implement the method in the embodiments of the present application.

In some embodiments, as shown in fig. 15, the communication device 800 may also include a memory 820. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application.

Wherein the memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

In some embodiments, as shown in fig. 15, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices, and in particular, may transmit information or data to other devices, or receive information or data transmitted by other devices.

Among other things, transceiver 830 may include a transmitter and a receiver. Transceiver 830 may further include antennas, the number of which may be one or more.

In some embodiments, the communication device 800 may be specifically a network device in the embodiments of the present application, and the communication device 800 may implement corresponding flows implemented by the network device in each method in the embodiments of the present application, which are not described herein for brevity.

In some embodiments, the communication device 800 may be specifically a terminal device in the embodiments of the present application, and the communication device 800 may implement a corresponding flow implemented by the terminal device in each method in the embodiments of the present application, which is not described herein for brevity.

Fig. 16 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 900 shown in fig. 16 includes a processor 910, and the processor 910 may call and execute a computer program from a memory to implement the methods in the embodiments of the present application.

In some embodiments, as shown in fig. 16, apparatus 900 may further comprise a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the methods in the embodiments of the present application.

Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.

In some embodiments, the apparatus 900 may also include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

In some embodiments, the apparatus 900 may further include an output interface 940. Wherein the processor 910 may control the output interface 940 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

In some embodiments, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement corresponding flows implemented by the network device in each method in the embodiments of the present application, which are not described herein for brevity.

In some embodiments, the apparatus may be applied to a terminal device in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiments of the present application, which is not described herein for brevity.

In some embodiments, the device mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 17 is a schematic block diagram of a communication system 1000 provided in an embodiment of the present application. As shown in fig. 17, the communication system 1000 includes a terminal device 1010 and a network device 1020.

The terminal device 1010 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1020 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

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

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

In some embodiments, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

In some embodiments, the computer readable storage medium may be applied to a terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

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

In some embodiments, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

In some embodiments, the computer program product may be applied to a terminal device in an embodiment of the present application, and the computer program instructions cause the computer to execute corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

In some embodiments, the computer program may be applied to a network device in the embodiments of the present application, where the computer program when executed on a computer causes the computer to execute corresponding processes implemented by the network device in the methods in the embodiments of the present application, and for brevity, will not be described in detail herein.

In some embodiments, the computer program may be applied to a terminal device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

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

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

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

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

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

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

A method of wireless communication, comprising:

the terminal equipment receives first information in a first time unit set;

the first time unit set is used for the terminal equipment to monitor a Physical Downlink Control Channel (PDCCH), and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.
The method of claim 1, wherein,

the time units in the first time unit set are continuous with the time units in the second time unit set; or,

the time units in the first set of time units are discontinuous with the time units in the second set of time units.
The method of claim 1 or 2, wherein,

the second set of time units includes some or all of the time units in the first set of time units.
A method according to any one of claims 1 to 3, wherein the first information is further used to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

an offset of a first time cell in the second set of time cells relative to a reference time cell;

an offset of a last time unit in the second set of time units relative to a reference time unit;

the number of time units comprised by the second set of time units;

the number of time units included in the second time unit set starting from the first time unit after the first time unit set;

and the search space set group SSSG to be monitored in the second time unit set.
The method of claim 4, wherein the SSSG required to be listened to in the second set of time units comprises a default SSSG required to be listened to in the second set of time units.
The method of claim 4 or 5, wherein,

the reference time unit is configured by a network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by the hybrid automatic repeat request-acknowledgement (HARQ-ACK) corresponding to the first information.
The method according to any one of claim 1 to 6,

the default SSSG required to be monitored in the first time unit set is different from the default SSSG required to be monitored in the second time unit set, or the default SSSG required to be monitored in the first time unit set is the same as the default SSSG required to be monitored in the second time unit set.
The method according to any one of claim 1 to 7,

the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively configured or indicated by the network equipment, or the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively agreed by a protocol.
The method of any one of claims 1 to 8, wherein the method further comprises:

the terminal equipment monitors the PDCCH in the third time unit set, or the terminal equipment does not monitor the PDCCH any more in the third time unit set;

wherein the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, the first time unit being a last time unit occupied by the first information.
The method of claim 9, wherein the first information comprises first indication information, wherein the first indication information is used to instruct the terminal device to monitor PDCCH in the third set of time units, or the first indication information is used to instruct the terminal device not to monitor PDCCH anymore in the third set of time units.
The method of claim 9, wherein the terminal device listening for PDCCH in a third set of time units, comprising:

and the terminal equipment monitors the PDCCH in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol.
The method of claim 9, wherein the terminal device is no longer listening for PDCCH in a third set of time units, comprising:

and the terminal equipment does not monitor the PDCCH in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol.
The method of any one of claims 1 to 12, wherein the first information is carried by at least one of:

downlink control information DCI, medium access control element MAC CE, radio resource control RRC.
The method of any one of claims 1 to 13, wherein the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol.
The method according to any of claims 1 to 14, wherein the first set of time units corresponds to time units within a discontinuous reception, DRX, activation time, and the second set of time units comprises time units outside the DRX activation time.
A method of wireless communication, comprising:

the network equipment sends first information to the terminal equipment in a first time unit set;

the first time unit set is used for the terminal equipment to monitor a Physical Downlink Control Channel (PDCCH), and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.
The method of claim 16, wherein,

the time units in the first time unit set are continuous with the time units in the second time unit set; or,

the time units in the first set of time units are discontinuous with the time units in the second set of time units.
The method of claim 16 or 17, wherein,

The second set of time units includes some or all of the time units in the first set of time units.
The method of any of claims 16 to 18, wherein the first information is further used to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

an offset of a first time cell in the second set of time cells relative to a reference time cell;

an offset of a last time unit in the second set of time units relative to a reference time unit;

the number of time units comprised by the second set of time units;

the number of time units included in the second time unit set starting from the first time unit after the first time unit set;

and the search space set group SSSG to be monitored in the second time unit set.
The method of claim 19, wherein the SSSG required to be listened to in the second set of time units comprises a default SSSG required to be listened to in the second set of time units.
The method of claim 19 or 20, wherein,

The reference time unit is configured by the network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by the hybrid automatic repeat request-response (HARQ-ACK) corresponding to the first information.
The method according to any one of claim 16 to 21, wherein,

the default SSSG required to be monitored in the first time unit set is different from the default SSSG required to be monitored in the second time unit set, or the default SSSG required to be monitored in the first time unit set is the same as the default SSSG required to be monitored in the second time unit set.
The method according to any one of claim 16 to 22,

the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively configured or indicated by the network device, or the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively agreed by a protocol.
The method of any of claims 16 to 23, wherein the first information comprises first indication information, wherein the first indication information is used to instruct the terminal device to monitor PDCCH in a third set of time units, or the first indication information is used to instruct the terminal device not to monitor PDCCH any more in a third set of time units;

wherein the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, the first time unit being a last time unit occupied by the first information.
The method of claim 24, wherein the method further comprises:

and the network equipment determines to send the PDCCH to the terminal equipment in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol, or the network equipment determines not to send the PDCCH to the terminal equipment in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol.
The method of any of claims 16 to 25, wherein the first information is carried by at least one of:

Downlink control information DCI, medium access control element MAC CE, radio resource control RRC.
The method of any one of claims 16 to 26, wherein the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol.
The method according to any of claims 16 to 27, wherein the first set of time units corresponds to time units within a discontinuous reception, DRX, activation time, and the second set of time units comprises time units outside the DRX activation time.
A method of wireless communication, comprising:

the terminal equipment receives first configuration information; wherein,

the first configuration information is used for configuring at least two DRX configurations in a discontinuous reception DRX group for the terminal equipment; or,

the first configuration information is used for configuring one DRX configuration for the terminal equipment in a DRX group, and the one DRX configuration comprises at least two sets of DRX parameters.
The method of claim 29, wherein any one of the at least two sets of DRX parameters comprises at least one of:

DRX cycle parameter, DRX duration timer DRX-onDurationTimer, DRX deactivation timer DRX-InactivityTimer, DRX slot offset DRX-SlotOffset, DRX long cycle start offset DRX-longCyclostartOffset, downlink DRX retransmission timer DRX-retransmission timer DRX-retransmission timer UL, downlink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerDL, uplink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerUL.
The method of claim 29 or 30, wherein,

and under the condition that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time in the DRX group comprises the activation time corresponding to a first DRX configuration in the at least two DRX configurations and the activation time corresponding to a second DRX configuration in the at least two DRX configurations.
The method of claim 29 or 30, wherein,

and when the first configuration information is used for configuring one DRX configuration in the DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time in the DRX group comprises the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters and the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters.
The method of claim 31 or 32, wherein the method further comprises:

and the terminal equipment monitors a physical downlink control channel PDCCH at the activation time in the DRX group.
The method of any one of claim 29 to 33,

in the case that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time corresponding to a first DRX configuration in the at least two DRX configurations is determined based on second information, and/or the activation time corresponding to a second DRX configuration in the at least two DRX configurations is determined based on second information and third information; or,

In the case that the first configuration information is used for configuring one DRX configuration in a DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on second information; and/or, determining the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information;

wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell is in the corresponding downlink DRX retransmission timer or uplink DRX retransmission timer in the DRX group; a random access contention resolution timer or a message B in random access responds to window information msgB-response window; the terminal equipment sends a scheduling request on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) which indicates new transmission and corresponds to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity is not received, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

The third information is used for adjusting the activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used for adjusting the parameter values included in the second DRX configuration or the second set of DRX parameters.
The method of claim 34, wherein the third information is sent by a network device via higher layer signaling and/or physical layer downlink control information.
A method of wireless communication, comprising:

the network equipment sends first configuration information to the terminal equipment; wherein,

the first configuration information is used for configuring at least two DRX configurations in a discontinuous reception DRX group for the terminal equipment; or,

the first configuration information is used for configuring one DRX configuration for the terminal equipment in a DRX group, and the one DRX configuration comprises at least two sets of DRX parameters.
The method of claim 36, wherein any one of the at least two sets of DRX parameters comprises at least one of:

DRX cycle parameter, DRX duration timer DRX-onDurationTimer, DRX deactivation timer DRX-InactivityTimer, DRX slot offset DRX-SlotOffset, DRX long cycle start offset DRX-longCyclostartOffset, downlink DRX retransmission timer DRX-retransmission timer DRX-retransmission timer UL, downlink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerDL, uplink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerUL.
The method of claim 36 or 37, wherein,

and under the condition that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time in the DRX group comprises the activation time corresponding to a first DRX configuration in the at least two DRX configurations and the activation time corresponding to a second DRX configuration in the at least two DRX configurations.
The method of claim 36 or 37, wherein,

and when the first configuration information is used for configuring one DRX configuration in the DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time in the DRX group comprises the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters and the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters.
The method of any one of claim 36 to 39,

in the case that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time corresponding to a first DRX configuration in the at least two DRX configurations is determined based on second information, and/or the activation time corresponding to a second DRX configuration in the at least two DRX configurations is determined based on second information and third information; or,

In the case that the first configuration information is used for configuring one DRX configuration in a DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on second information; and/or, determining the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information;

wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell is in the corresponding downlink DRX retransmission timer or uplink DRX retransmission timer in the DRX group; a random access contention resolution timer or a message B in random access responds to window information msgB-response window; the terminal equipment sends a scheduling request on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) which indicates new transmission and corresponds to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity is not received, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

The third information is used for adjusting the activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used for adjusting the parameter values included in the second DRX configuration or the second set of DRX parameters.
The method of claim 40, wherein the third information is sent by the network device via higher layer signaling and/or physical layer downlink control information.
A terminal device, comprising:

a first communication unit for receiving first information in a first set of time units;

the first time unit set is used for the terminal equipment to monitor a Physical Downlink Control Channel (PDCCH), and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.
The terminal device of claim 42, wherein,

the time units in the first time unit set are continuous with the time units in the second time unit set; or,

the time units in the first set of time units are discontinuous with the time units in the second set of time units.
The terminal device of claim 42 or 43, wherein the second set of time units comprises part or all of the time units in the first set of time units.
The terminal device of any of claims 42 to 44, wherein the first information is further for indicating at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

an offset of a first time cell in the second set of time cells relative to a reference time cell;

an offset of a last time unit in the second set of time units relative to a reference time unit;

the number of time units comprised by the second set of time units;

the number of time units included in the second time unit set starting from the first time unit after the first time unit set;

and the search space set group SSSG to be monitored in the second time unit set.
The terminal device of claim 45, wherein the SSSG required to be listened to in the second set of time units comprises a default SSSG required to be listened to in the second set of time units.
The terminal device of claim 45 or 46,

the reference time unit is configured by a network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by the hybrid automatic repeat request-acknowledgement (HARQ-ACK) corresponding to the first information.
The terminal device of any one of claims 42 to 47,

the default SSSG required to be monitored in the first time unit set is different from the default SSSG required to be monitored in the second time unit set, or the default SSSG required to be monitored in the first time unit set is the same as the default SSSG required to be monitored in the second time unit set.
The terminal device of any one of claims 42 to 48,

the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively configured or indicated by the network equipment, or the default SSSG to be monitored in the first time unit set and the default SSSG to be monitored in the second time unit set are respectively agreed by a protocol.
The terminal device of any of claims 42 to 49, wherein the terminal device further comprises:

a second communication unit, configured to monitor the PDCCH in the third time unit set, or configured to not monitor the PDCCH in the third time unit set;

wherein the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, the first time unit being a last time unit occupied by the first information.
The terminal device of claim 50, wherein the first information comprises first indication information, wherein the first indication information is used to instruct the terminal device to monitor PDCCH in the third set of time units, or the first indication information is used to instruct the terminal device not to monitor PDCCH anymore in the third set of time units.
The terminal device of claim 50, wherein the second communication unit is specifically configured to:

and monitoring the PDCCH in the third time unit set according to the information configured by the network equipment or the information agreed by the protocol.
The terminal device of claim 50, wherein the second communication unit is specifically configured to:

and according to the information configured by the network equipment or the information agreed by the protocol, the PDCCH is not monitored any more in the third time unit set.
The terminal device of any of claims 42 to 53, wherein the first information is carried by at least one of:

downlink control information DCI, medium access control element MAC CE, radio resource control RRC.
The terminal device of any of claims 42 to 54, wherein the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol.
The terminal device of any of claims 42 to 55, wherein the first set of time units corresponds to time units within a discontinuous reception, DRX, activation time, and the second set of time units comprises time units outside of the DRX activation time.
A network device, comprising:

a communication unit, configured to send first information to a terminal device in a first time unit set;

the first time unit set is used for the terminal equipment to monitor a Physical Downlink Control Channel (PDCCH), and the first information is used for indicating the terminal equipment to monitor the PDCCH in the second time unit set.
The network device of claim 57, wherein,

the time units in the first time unit set are continuous with the time units in the second time unit set; or,

the time units in the first set of time units are discontinuous with the time units in the second set of time units.
The network device of claim 57 or 58,

the second set of time units includes some or all of the time units in the first set of time units.
The network device of any one of claims 57 to 59, wherein the first information is further to indicate at least one of:

a first time cell in the second set of time cells;

the last time unit in the second set of time units;

an offset of a first time cell in the second set of time cells relative to a reference time cell;

an offset of a last time unit in the second set of time units relative to a reference time unit;

the number of time units comprised by the second set of time units;

the number of time units included in the second time unit set starting from the first time unit after the first time unit set;

and the search space set group SSSG to be monitored in the second time unit set.
The network device of claim 60, wherein the SSSG required to be listened to in the second set of time units comprises a default SSSG required to be listened to in the second set of time units.
The network device of claim 60 or 61,

the reference time unit is configured by the network device, or the reference time unit is agreed by a protocol, or the reference time unit is the last time unit in the first time unit set, or the reference time unit is the first time unit after the first time unit set, or the reference time unit is the last time unit occupied by the first information, or the reference time unit is the last time unit occupied by the hybrid automatic repeat request-response (HARQ-ACK) corresponding to the first information.
The network device of any one of claims 57 to 62,

the default SSSG required to be monitored in the first time unit set is different from the default SSSG required to be monitored in the second time unit set, or the default SSSG required to be monitored in the first time unit set is the same as the default SSSG required to be monitored in the second time unit set.
The network device of any one of claims 57 to 63,

the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively configured or indicated by a network side, or the default SSSG required to be monitored in the first time unit set and the default SSSG required to be monitored in the second time unit set are respectively agreed by a protocol.
The network device of any one of claims 57 to 64, wherein the first information comprises first indication information, wherein the first indication information is used to instruct the terminal device to listen for PDCCH in a third set of time units, or the first indication information is used to instruct the terminal device to no longer listen for PDCCH in a third set of time units;

Wherein the third time unit set includes all time units from a first time unit to a last time unit included in the first time unit set, the first time unit being a last time unit occupied by the first information.
The network device of claim 65, wherein the network device further comprises: a processing unit, wherein,

the processing unit is configured to determine that the PDCCH is sent to the terminal device in the third time unit set according to the information configured by the network device or the information agreed by the protocol, or the processing unit is configured to determine that the PDCCH is not sent to the terminal device in the third time unit set any more according to the information configured by the network device or the information agreed by the protocol.
The network device of any one of claims 57 to 66, wherein the first information is carried by at least one of:

downlink control information DCI, medium access control element MAC CE, radio resource control RRC.
The network device of any one of claims 57 to 67, wherein the time unit is one of: frame, subframe, slot, sub-slot, time domain symbol.
The network device of any one of claims 57 to 68, wherein the first set of time units corresponds to time units within a discontinuous reception, DRX, activation time, and the second set of time units comprises time units outside of the DRX activation time.
A terminal device, comprising:

a first communication unit configured to receive first configuration information; wherein,

the first configuration information is used for configuring at least two DRX configurations in a discontinuous reception DRX group for the terminal equipment; or,

the first configuration information is used for configuring one DRX configuration for the terminal equipment in a DRX group, and the one DRX configuration comprises at least two sets of DRX parameters.
The terminal device of claim 70, wherein any one of the at least two sets of DRX parameters comprises at least one of:

DRX cycle parameter, DRX duration timer DRX-onDurationTimer, DRX deactivation timer DRX-InactivityTimer, DRX slot offset DRX-SlotOffset, DRX long cycle start offset DRX-longCyclostartOffset, downlink DRX retransmission timer DRX-retransmission timer DRX-retransmission timer UL, downlink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerDL, uplink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerUL.
The terminal device of claim 70 or 71,

and under the condition that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time in the DRX group comprises the activation time corresponding to a first DRX configuration in the at least two DRX configurations and the activation time corresponding to a second DRX configuration in the at least two DRX configurations.
The terminal device of claim 70 or 71,

and when the first configuration information is used for configuring one DRX configuration in the DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time in the DRX group comprises the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters and the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters.
The terminal device of claim 72 or 73, wherein the terminal device further comprises:

and the second communication unit is used for monitoring the physical downlink control channel PDCCH at the activation time in the DRX group.
The terminal device of any of claims 70 to 74,

In the case that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time corresponding to a first DRX configuration in the at least two DRX configurations is determined based on second information, and/or the activation time corresponding to a second DRX configuration in the at least two DRX configurations is determined based on second information and third information; or,

in the case that the first configuration information is used for configuring one DRX configuration in a DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on second information; and/or, determining the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information;

wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell is in the corresponding downlink DRX retransmission timer or uplink DRX retransmission timer in the DRX group; a random access contention resolution timer or a message B in random access responds to window information msgB-response window; a scheduling request is sent on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) which indicates new transmission and corresponds to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity is not received, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

The third information is used for adjusting the activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used for adjusting the parameter values included in the second DRX configuration or the second set of DRX parameters.
The terminal device of claim 75, wherein the third information is sent by a network device through higher layer signaling and/or physical layer downlink control information.
A network device, comprising:

a first communication unit, configured to send first configuration information to a terminal device; wherein,

the first configuration information is used for configuring at least two DRX configurations in a discontinuous reception DRX group for the terminal equipment; or,

the first configuration information is used for configuring one DRX configuration for the terminal equipment in a DRX group, and the one DRX configuration comprises at least two sets of DRX parameters.
The network device of claim 77, wherein any one of the at least two sets of DRX parameters comprises at least one of:

DRX cycle parameter, DRX duration timer DRX-onDurationTimer, DRX deactivation timer DRX-InactivityTimer, DRX slot offset DRX-SlotOffset, DRX long cycle start offset DRX-longCyclostartOffset, downlink DRX retransmission timer DRX-retransmission timer DRX-retransmission timer UL, downlink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerDL, uplink DRX hybrid automatic repeat request round-trip transmission time timer DRX-HARQ-RTT-TimerUL.
The network device of claim 77 or 78,

and under the condition that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time in the DRX group comprises the activation time corresponding to a first DRX configuration in the at least two DRX configurations and the activation time corresponding to a second DRX configuration in the at least two DRX configurations.
The network device of claim 77 or 78,

and when the first configuration information is used for configuring one DRX configuration in the DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time in the DRX group comprises the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters and the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters.
The network device of any one of claims 77 to 80,

in the case that the first configuration information is used for configuring at least two DRX configurations in a DRX group for the terminal equipment, the activation time corresponding to a first DRX configuration in the at least two DRX configurations is determined based on second information, and/or the activation time corresponding to a second DRX configuration in the at least two DRX configurations is determined based on second information and third information; or,

In the case that the first configuration information is used for configuring one DRX configuration in a DRX group for the terminal equipment, and the one DRX configuration comprises at least two sets of DRX parameters, the activation time corresponding to a first set of DRX parameters in the at least two sets of DRX parameters is determined based on second information; and/or, determining the activation time corresponding to a second set of DRX parameters in the at least two sets of DRX parameters based on the second information and the third information;

wherein the second information includes at least one of: a DRX duration timer or a DRX deactivation timer corresponding to the DRX group; any service cell is in the corresponding downlink DRX retransmission timer or uplink DRX retransmission timer in the DRX group; the message B responds to window information msgB-responseWindow in a random access contention resolution timer or random access; the terminal equipment sends a scheduling request on a Physical Uplink Control Channel (PUCCH) and is in a suspension state; after a random access response corresponding to a random access preamble is successfully received, a Physical Downlink Control Channel (PDCCH) which indicates new transmission and corresponds to a cell radio network temporary identifier (C-RNTI) of a Media Access Control (MAC) entity is not received, wherein the random access preamble is a random access preamble which is not selected in contention-based random access aiming at the MAC entity;

The third information is used for adjusting the activation time corresponding to the second DRX configuration or the second set of DRX parameters, or the third information is used for adjusting the parameter values included in the second DRX configuration or the second set of DRX parameters.
The network device of claim 81, wherein the network device further comprises:

and the second communication unit is used for sending the third information to the terminal equipment through higher layer signaling and/or physical layer downlink control information.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 15, or to perform the method according to any of claims 29 to 35.
A network device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 16 to 28, or to perform the method according to any of claims 36 to 41.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 15, or to perform the method of any one of claims 16 to 28, or to perform the method of any one of claims 29 to 35, or to perform the method of any one of claims 36 to 41.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 15, or to perform the method of any one of claims 16 to 28, or to perform the method of any one of claims 29 to 35, or to perform the method of any one of claims 36 to 41.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 15, or to perform the method of any one of claims 16 to 28, or to perform the method of any one of claims 29 to 35, or to perform the method of any one of claims 36 to 41.
A computer program, characterized in that the computer program causes a computer to perform the method of any one of claims 1 to 15, or to perform the method of any one of claims 16 to 28, or to perform the method of any one of claims 29 to 35, or to perform the method of any one of claims 36 to 41.