CN115843445A - Discontinuous reception method, terminal equipment and network equipment - Google Patents

Discontinuous reception method, terminal equipment and network equipment Download PDF

Info

Publication number
CN115843445A
CN115843445A CN202080103159.XA CN202080103159A CN115843445A CN 115843445 A CN115843445 A CN 115843445A CN 202080103159 A CN202080103159 A CN 202080103159A CN 115843445 A CN115843445 A CN 115843445A
Authority
CN
China
Prior art keywords
drx
drx group
group
terminal device
state duration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202080103159.XA
Other languages
Chinese (zh)
Inventor
石聪
胡奕
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN115843445A publication Critical patent/CN115843445A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

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

Abstract

The embodiment of the application provides a discontinuous reception method, terminal equipment and network equipment, which can realize that the DCP is used to reduce unnecessary PDCCH monitoring of the terminal equipment on part or all DRX groups under the condition that a plurality of sets of DRX are configured aiming at one MAC entity, thereby achieving the purpose of saving electricity of the terminal. The discontinuous reception method comprises the following steps: the terminal equipment receives first information, wherein the first information is used for indicating at least one DRX group controlled by the DCP, and the at least one DRX group comprises a primary DRX group and/or a secondary DRX group.

Description

Discontinuous reception method, terminal equipment and network equipment Technical Field
The embodiment of the application relates to the field of communication, and in particular relates to a discontinuous reception method, a terminal device and a network device.
Background
In a New Radio (NR) system, a Media Access Control (MAC) entity is introduced to configure multiple (Dual) sets of Discontinuous Reception (DRX), however, how to configure Downlink Control Information Scrambled with Power Saving wireless Network Temporary identifier (DCP) in a case where the Dual DRX is configured by a Network device is an urgent problem to be solved.
Disclosure of Invention
The embodiment of the application provides a discontinuous reception method, terminal equipment and network equipment, which can realize that unnecessary PDCCH monitoring of the terminal equipment on part or all DRX groups is reduced by using a DCP under the condition that a plurality of sets of DRX are configured aiming at an MAC entity, thereby achieving the aim of saving electricity of the terminal.
In a first aspect, a method of discontinuous reception is provided, the method including:
the terminal equipment receives first information, wherein the first information is used for indicating at least one DRX group controlled by the DCP, and the at least one DRX group comprises a primary DRX group and/or a secondary DRX group.
In a second aspect, a method of discontinuous reception is provided, the method including:
the network equipment transmits first information which is used for indicating at least one DRX group controlled by the DCP, wherein the at least one DRX group comprises a primary DRX group and/or a secondary DRX group.
In a third aspect, a terminal device is provided for executing the method in the first aspect.
In particular, the terminal device comprises functional modules for performing the method in the first aspect described above.
In a fourth aspect, a network device is provided for performing the method of the second aspect.
In particular, the network device comprises functional modules for performing the method in the second aspect described above.
In a fifth aspect, a terminal device is provided that includes 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 sixth aspect, a network device is provided that includes 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 second aspect.
In a seventh aspect, an apparatus is provided for implementing the method in any one of the first to second aspects.
Specifically, the apparatus includes: a processor for calling and running the computer program from the memory so that the apparatus on which the apparatus is installed performs the method of any of the first to second aspects described above.
In an eighth aspect, there is provided a computer readable storage medium storing a computer program for causing a computer to perform the method of any one of the first to second aspects described above.
In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any of the first to second aspects above.
A tenth aspect provides a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects described above.
By the technical scheme, the network equipment can indicate at least one DRX group controlled by the DCP, and the at least one DRX group comprises a main DRX group and/or a secondary DRX group. That is to say, the application can achieve the purpose of reducing unnecessary PDCCH monitoring on part or all DRX groups by the terminal device by using the DCP when configuring a plurality of DRX groups for one MAC entity, thereby achieving the purpose of saving power for the terminal.
Drawings
Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
Fig. 2 is a schematic diagram of a DRX cycle provided in an embodiment of the present application.
Fig. 3 is a schematic flow chart of a method of discontinuous reception according to an embodiment of the present application.
Fig. 4 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
Fig. 5 is a schematic block diagram of a network device provided according to an embodiment of the present application.
Fig. 6 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
Fig. 7 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.
Fig. 8 is a schematic block diagram of a communication system provided in accordance with an embodiment of the present application.
Detailed Description
Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art without making any creative effort with respect to the embodiments in the present application belong to the protection scope of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (Advanced Long Term Evolution, LTE-a) System, a New Radio (NR) System, an Evolution System of an NR System, an LTE (LTE-based Access to unlicensed spectrum, LTE-U) System on an unlicensed spectrum, an NR (NR-based Access to unlicensed spectrum, non-Terrestrial communication network (network-telecommunications), a Wireless Local Area network (UMTS) System, a Wireless Local Area network (UMTS) 5 (Universal Mobile telecommunications network, UMTS) System, a Wireless Local Area network (Wireless Telecommunication System, wiFi) System, a Wireless Local Area network (Wireless Telecommunication System, or Wireless Telecommunication System, and the like.
Generally, the conventional Communication system supports a limited number of connections and is 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 (M2M) Communication, machine Type Communication (MTC), vehicle to Vehicle (V2V) Communication, or Vehicle to internet (V2X) Communication, and the embodiments of the present application can also be applied to these Communication systems.
Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.
Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; alternatively, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where the licensed spectrum may also be regarded as an unshared spectrum.
Various embodiments are described in conjunction with network Equipment and terminal Equipment, where the terminal Equipment may also be referred to as User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User device.
The terminal device may be a STATION (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) STATION, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication capability, 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 (PLMN) Network, and so on.
In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.).
In this embodiment, 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 (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in city (smart city), a wireless terminal device in smart home (smart home), or the like.
By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A 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 realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.
In this embodiment of the present application, the network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay Station or an Access Point, a vehicle-mounted device, a wearable device, and a network device or Base Station (gbb) in an NR network, or a network device or Base Station (gbb) in a PLMN network for future evolution, or a network device in an NTN network, and the like.
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. Alternatively, the network device may be a satellite, balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a geosynchronous Orbit (GEO) satellite, a High Elliptic Orbit (HEO) satellite, and the like. Alternatively, the network device may be a base station installed on land, water, or the like.
In this embodiment of the present application, a network device may provide a service for a cell, and 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 the network device (e.g., a base station), and the cell may belong to a macro base station or 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 transmission power, and are suitable for providing high-rate data transmission services.
Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area.
Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which are not limited in this embodiment.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
The terminology used in the description of the embodiments 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," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions.
It should be understood that "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication of an association relationship. For example, a indicates B, which may mean that a directly indicates B, e.g., B may be obtained by a; it may also mean that a indicates B indirectly, for example, a indicates C, and B may be obtained by C; it can also mean that there is an association between a and B.
In the description of the embodiments of the present application, the term "correspond" may indicate that there is a direct correspondence or an indirect correspondence between the two, may also indicate that there is an association between the two, and may also indicate and be indicated, configure and configured, and so on.
In the embodiment of the present application, "predefining" may be implemented by saving a corresponding code, table, or other manners that may be used to indicate related information in advance in a device (for example, including a terminal device and a network device), and the present application is not limited to a specific implementation manner thereof. Such as predefined, may refer to what is defined in the protocol.
In the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and for example, may include an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.
For better understanding of the embodiments of the present application, the 5G NR DRX related to the present application will be described.
In the 5G NR, the network device may configure a DRX function for the terminal, and the network device configures a DRX cycle (cycle) for the terminal in a Radio Resource Control (RRC) connected state. As shown in fig. 2, the DRX cycle includes an active period (On Duration) and a dormant period (Opportunity for DRX), and during the On Duration, the terminal device monitors and receives a Physical Downlink Control Channel (PDCCH); during Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption.
Wherein, each MAC entity has a DRX configuration, and the configuration parameters of DRX comprise:
DRX state duration timer (DRX-onDurationTimer): duration of terminal device wake-up at the beginning of one DRX Cycle (Cycle);
DRX slot offset (DRX-SlotOffset): the terminal equipment starts the time delay of the drx onDurationTimer;
DRX deactivation timer (DRX-inactivity timer): after receiving a PDCCH indicating uplink initial transmission or downlink initial transmission, the terminal equipment continues to monitor the duration of the PDCCH;
DRX downlink retransmission timer (DRX-retransmission timerdl): the terminal equipment monitors the longest duration of the PDCCH indicating the downlink retransmission scheduling. Each downlink HARQ process except for a broadcast Hybrid Automatic Repeat reQuest (HARQ) process corresponds to a drx-retransmission timerdl;
DRX uplink retransmission timer (DRX-retransmission timer ul): the terminal equipment monitors the longest duration of a PDCCH indicating uplink retransmission scheduling. Each uplink HARQ process corresponds to one drx-retransmission TimerUL;
DRX long cycle start offset (DRX-LongCycleStartOffset): a subframe offset for configuring a Long DRX Cycle (Long DRX Cycle), and a start of the Long DRX Cycle and a Short DRX Cycle (Short DRX Cycle);
DRX short cycle (DRX-short cycle): short DRX cycle, which is optional configuration;
DRX short cycle timer (DRX-ShortCycleTimer): the duration that the terminal device is in Short DRX cycle (and does not receive any PDCCH), which is an optional configuration;
DRX downlink HARQ Round Trip Time (RTT) timer (DRX-HARQ-RTT-TimerDL): terminal equipment expects to receive the minimum waiting time required by the PDCCH indicating downlink scheduling, and each downlink HARQ process except the broadcast HARQ process corresponds to one drx-HARQ-RTT-TimerDL;
DRX uplink HARQ RTT timer (DRX-HARQ-RTT-timerll): and the terminal equipment expects to receive the minimum waiting time required by the PDCCH indicating the uplink scheduling, and each uplink HARQ process corresponds to one drx-HARQ-RTT-TimerUL.
If the terminal device configures DRX, the terminal device needs to monitor PDCCH during DRX Active Time (Active Time). DRX Active Time includes several cases:
case 1: any one of 5 timers, drx-onDurationTimer, drx-inactivytimetr, drx-retransmission timerdl, drx-retransmission timerll, and random access contention resolution timer (ra-ContentionResolutionTimer), is running.
Case 2: a Scheduling Request (SR) is transmitted on a Physical Uplink Control Channel (PUCCH) and is in a waiting (pending) state.
Case 3: in the contention-based random access process, the terminal device does not receive one initial transmission indicated by a PDCCH scrambled by a Cell Radio Network Temporary identifier (C-RNTI) after successfully receiving a random access response.
Note that the DRX long cycle (DRX long cycle) is a default configuration, and the DRX short cycle (DRX short cycle) is an optional configuration. For a terminal configured with a short DRX cycle, the long DRX cycle and the short DRX cycle can be mutually converted, and the conversion mode is as follows:
the terminal device uses the DRX short cycle when any one of the following conditions is satisfied:
drx-inactivity timer times out;
the terminal device receives a DRX Command (Command) Media Access Control Element (MAC CE).
The terminal device uses the DRX long cycle when any one of the following conditions is satisfied:
drx-ShortCycleTimer times out;
the terminal equipment receives a long DRX command MAC CE.
The terminal device determines the time for starting the DRX-onDurationTimer according to whether the terminal device is currently in a short DRX cycle or a long DRX cycle, and the specific specification is as follows:
if Short DRX Cycle is used, and the current subframe satisfies [ (System Frame Number, SFN) × 10) + subframe Number (subframe Number) ] mod (DRX-Short) = (DRX-StartOffset) mod (DRX-Short); or
If the Long DRX Cycle is used, and the current subframe satisfies [ (SFN x 10) + subframe number ] mod (DRX-Long Cycle) = DRX-StartOffset;
wherein the DRX-onDurationTimer is started at a time after a DRX slot offset (DRX-SlotOffset) slots (slots) from the start of the current subframe.
The conditions for starting or restarting the drx-inactivytytytytimer by the terminal equipment are as follows:
if the terminal equipment receives a PDCCH indicating the downlink or uplink initial transmission, the terminal starts or restarts the drx-InactivetyTimer.
The conditions for starting and stopping the drx-retransmission timerdl by the terminal equipment are as follows:
when the terminal device receives a PDCCH indicating downlink transmission, or when the terminal device receives a Media Access Control Protocol Data Unit (MAC PDU) on the configured downlink grant resource, the terminal device stops drx-retransmission timerdl corresponding to the HARQ process. And the terminal equipment starts drx-HARQ-RTT-TimerDL corresponding to the HARQ process after finishing the transmission of the HARQ process feedback aiming at the downlink transmission.
If a timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ of the terminal device is overtime and the downlink data transmitted by using the HARQ process is unsuccessfully decoded, the terminal starts drx-retransmission TimerDL corresponding to the HARQ process.
The conditions for starting and stopping drx-retransmission timerll by the terminal equipment are as follows:
when the terminal equipment receives a PDCCH indicating uplink transmission or when the terminal equipment sends a MAC PDU on the configured uplink authorized resource, the terminal stops drx-retransmission TimerUL corresponding to the HARQ process. The terminal device starts drx-HARQ-RTT-timer ul corresponding to the HARQ process after completing the first retransmission (retransmission) of the Physical Uplink Shared Channel (PUSCH) of this time.
If a timer drx-HARQ-RTT-timerll corresponding to a certain HARQ of the terminal device is overtime, the terminal starts drx-retransmission timerll corresponding to the HARQ process.
Release16, R16 introduces Dual DRX, but it cannot be configured with DCP, i.e., if the network configures DCP, it cannot. In order to enable Dual DRX and DCP to be configured simultaneously, the DCP needs to be enhanced because currently, the DCP can only indicate one DRX-on duration timer corresponding to one DRX.
Based on the above problem, the present application provides a scheme for discontinuous reception, which can reduce unnecessary PDCCH monitoring on part or all DRX groups by a terminal device using a DCP under the condition that a plurality of DRX groups are configured for one MAC entity, thereby achieving the purpose of saving power for the terminal.
The technical solution of the present application is described in detail by specific examples below.
Fig. 3 is a schematic flow chart of a method 200 of discontinuous reception according to an embodiment of the present application, and as shown in fig. 3, the method 200 may include at least some of the following:
s210, a network device sends first information, wherein the first information is used for indicating at least one DRX group controlled by a DCP, and the at least one DRX group comprises a primary DRX group and/or a secondary DRX group;
s220, the terminal equipment receives the first information.
In the embodiment of the present application, at least two DRX groups may be configured for one MAC entity, where the at least two DRX groups may include one Primary DRX group (Primary DRX group) and at least one Secondary DRX group (Secondary DRX group).
That is, the first information may indicate whether a DRX group controlled by the DCP is a Primary DRX group or a Secondary DRX group, or indicate that the DCP controls both the Primary DRX group and the Secondary DRX group.
For further example, the first information indicates a DRX state duration timer corresponding to a Primary DRX group controlled by the DCP.
For another example, the first information indicates a DRX state duration timer corresponding to a Secondary DRX group controlled by the DCP.
For a further example, the first information indicates a DRX state duration timer corresponding to a Primary DRX group and a DRX state duration timer corresponding to a Secondary DRX group controlled by the DCP.
It should be noted that a DRX group is actually one or more serving cells, and a DRX group including a Special Cell (SpCell) is a primary DRX group, and a DRX group including only a Secondary Cell (SCell) is a Secondary DRX group. And the serving cells in the same DRX group adopt the same DRX configuration.
Optionally, the embodiments of the present application may be applied to a Carrier Aggregation (CA) scenario.
Optionally, the first information is RRC signaling. Alternatively, the first information is carried in an RRC signaling.
Optionally, in some embodiments, in a case that the terminal device receives the DCP, the terminal device determines, according to the first information, to start a DRX state duration timer corresponding to the at least one DRX group at a first time, where the first time is a time for starting the DRX state duration timer.
It should be noted that the first time is a time when the DRX state duration timer is started after receiving the DCP.
For example, in a case where the at least one DRX group includes a primary DRX group, the terminal device determines to start a DRX state duration timer corresponding to the primary DRX group at the first time.
For another example, in a case that the at least one DRX group includes a secondary DRX group, the terminal device determines to start a DRX state duration timer corresponding to the secondary DRX group at the first time.
For another example, in a case where the at least one DRX group includes a primary DRX group and a secondary DRX group, the terminal device determines to start a DRX state duration timer corresponding to the primary DRX group and a DRX state duration timer corresponding to the secondary DRX group at the first time.
Optionally, in some embodiments, in case that the terminal device receives the DCP, for DRX groups configured in the MAC entity other than the at least one DRX group, the terminal device may determine to start or not start its corresponding DRX state duration timer at the first time. That is, the terminal device may determine to start or not start a DRX state duration timer corresponding to a DRX group other than the at least one DRX group configured in the MAC entity at the first time.
For example, the terminal device may determine to start or not start a DRX state duration timer corresponding to a DRX group other than the at least one DRX group configured in the MAC entity at the first time according to the preconfiguration information.
Optionally, in some embodiments, in a case that the terminal device does not receive the DCP, the terminal device determines to start or not start a DRX state duration timer corresponding to a DRX group configured in the MAC entity at a first time, where the first time is a time when the DRX state duration timer is started.
For example, the terminal device determines to start or not start a DRX state duration timer corresponding to the DRX group configured in the MAC entity at the first time according to the pre-configuration information.
Optionally, the pre-configuration information is pre-configured by the network device, or the pre-configuration information is agreed by a protocol.
When it is necessary to say, the provisioning information may also be default configuration information or default configuration information.
Optionally, in some embodiments, the terminal device may determine whether to monitor the DCP at the DCP monitoring occasion (monitoring occasion) according to the first information and a DRX state of the terminal device at the DCP monitoring occasion.
For example, if the first information indicates that the DCP controls Primary DRX group, then: if the terminal device is in a Primary DRX group for Active Time (Active Time) during DCP monitoring occasion, the terminal device does not monitor the DCP on the DCP monitoring occasion.
For another example, if the first information indicates that the DCP controls the secondary DRX group, then: if the terminal device is in the second DRX group at DRX Active Time during DCP monitoring occasion, the terminal device does not monitor the DCP on the DCP monitoring occasion.
For another example, if the first information indicates that the DCP controls a Primary DRX group and a Secondary DRX group, then:
the method comprises the following steps: if the terminal device is in the Primary DRX group or the Secondary DRX group at DRX Active Time during DCP monitoring occasion, the terminal device does not monitor the DCP on the DCP monitoring occasion.
The method 2 comprises the following steps: if the terminal device is in DRX Active Time in both Primary DRX group and Secondary DRX group during DCP monitoring occasion, the terminal device does not monitor DCP on the DCP monitoring occasion.
Therefore, in the embodiment of the present application, the network device may indicate at least one DRX group controlled by the DCP, and the at least one DRX group includes a primary DRX group and/or a secondary DRX group. That is to say, the application can achieve the purpose of reducing unnecessary PDCCH monitoring on part or all DRX groups by the terminal device by using the DCP when configuring a plurality of DRX groups for one MAC entity, thereby achieving the purpose of saving power for the terminal. Meanwhile, the scheme of the application has small influence on the standard.
While method embodiments of the present application are described in detail above with reference to fig. 3, apparatus embodiments of the present application are described in detail below with reference to fig. 4-8, it being understood that apparatus embodiments correspond to method embodiments and that similar descriptions may refer to method embodiments.
Fig. 4 shows a schematic block diagram of a terminal device 300 according to an embodiment of the application. As shown in fig. 4, the terminal device 300 includes:
a communication unit 310, configured to receive first information indicating at least one DRX group controlled by a power-saving radio network temporary identity (DCP), wherein the at least one DRX group includes a primary DRX group and/or a secondary DRX group.
Optionally, the terminal device 300 further includes: a processing unit 320 for, among other things,
in a case that the terminal device receives the DCP, the processing unit 320 is configured to determine, according to the first information, to start a DRX state duration timer corresponding to the at least one DRX group at a first time, where the first time is a time for starting the DRX state duration timer.
Optionally, the processing unit 320 is specifically configured to:
determining to start a DRX state duration timer corresponding to the primary DRX group at the first time under the condition that the at least one DRX group comprises the primary DRX group; or,
determining to start a DRX state duration timer corresponding to the secondary DRX group at the first time when the at least one DRX group comprises the secondary DRX group; or,
and determining to start a DRX state duration timer corresponding to the primary DRX group and a DRX state duration timer corresponding to the secondary DRX group at the first time under the condition that the at least one DRX group comprises the primary DRX group and the secondary DRX group.
Optionally, the processing unit 320 is further configured to determine to start or not start a DRX state duration timer corresponding to a DRX group configured in the medium access control MAC entity except for the at least one DRX group at the first time.
Optionally, the processing unit 320 is specifically configured to:
and determining whether to start or not start a DRX state duration timer corresponding to the DRX groups except the at least one DRX group configured in the MAC entity at the first time according to the pre-configuration information.
Optionally, the terminal device 300 further includes: a processing unit 320 for, among other things,
in a case that the terminal device does not receive the DCP, the processing unit 320 is configured to determine to start or not start a DRX state duration timer corresponding to a DRX group configured in the MAC entity at a first time, where the first time is a time for starting the DRX state duration timer.
Optionally, the processing unit 320 is specifically configured to:
and determining to start or not start a DRX state duration timer corresponding to the DRX group configured in the MAC entity at the first time according to the pre-configuration information.
Optionally, the pre-configuration information is pre-configured by the network device, or the pre-configuration information is agreed by a protocol.
Optionally, the first information is radio resource control RRC signaling.
Optionally, the terminal device is applied to a carrier aggregation CA scenario.
Optionally, in some embodiments, the communication unit may be a communication interface or a 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 terminal device 300 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 above and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 3, and are not described herein again for brevity.
Fig. 5 shows a schematic block diagram of a network device 400 according to an embodiment of the application. As shown in fig. 5, the network device 400 includes:
a communication unit 410, configured to transmit first information indicating at least one DRX group controlled by the power saving radio network temporary identity (DCP), wherein the at least one DRX group includes a primary DRX group and/or a secondary DRX group.
Optionally, the first information is radio resource control RRC signaling.
Optionally, the network device is applied to a carrier aggregation CA scenario.
Optionally, in some embodiments, the communication unit may be a communication interface or a 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 400 according to the embodiment of the present application may correspond to a network device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 400 are respectively for implementing corresponding flows of the network device in the method 200 shown in fig. 3, and are not described herein again for brevity.
Fig. 6 is a schematic structural diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 shown in fig. 6 comprises a processor 510, and the processor 510 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 6, the communication device 500 may further include a memory 520. From the memory 520, the processor 510 can call and run a computer program to implement the method in the embodiment of the present application.
The memory 520 may be a separate device from the processor 510, or may be integrated into the processor 510.
Optionally, as shown in fig. 6, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.
The transceiver 530 may include a transmitter and a receiver, among others. The transceiver 530 may further include one or more antennas.
Optionally, the communication device 500 may specifically be a network device in the embodiment of the present application, and the communication device 500 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the communication device 500 may specifically be a mobile terminal/terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Fig. 7 is a schematic configuration diagram of an apparatus according to an embodiment of the present application. The apparatus 600 shown in fig. 7 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 7, the apparatus 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.
The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.
Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.
Optionally, the apparatus 600 may further comprise an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.
Optionally, the apparatus may be applied to the network device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the apparatus may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Alternatively, the device mentioned in the embodiments of the present application may also be a chip. For example, it may be a system-on-chip, a system-on-chip or a system-on-chip, etc.
Fig. 8 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 8, the communication system 700 includes a terminal device 710 and a network device 720.
The terminal device 710 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 720 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.
It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing the computer program.
Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.
Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. With regard to such understanding, the technical solutions of the present application may be essentially implemented or contributed to by the prior art, or may be implemented in a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (36)

  1. A method for Discontinuous Reception (DRX), comprising:
    the method comprises the steps that terminal equipment receives first information, wherein the first information is used for indicating at least one DRX group controlled by downlink control information (DCP) scrambled by an energy-saving wireless network temporary identifier, and the at least one DRX group comprises a main DRX group and/or an auxiliary DRX group.
  2. The method of claim 1, wherein the method further comprises:
    and under the condition that the DCP is received by the terminal equipment, the terminal equipment determines to start a DRX state duration timer corresponding to the at least one DRX group at a first time according to the first information, wherein the first time is the time for starting the DRX state duration timer.
  3. The method of claim 2, wherein the terminal device determining to start a DRX state duration timer corresponding to the at least one DRX group at a first time according to the first information comprises:
    under the condition that the at least one DRX group comprises a main DRX group, the terminal equipment determines to start a DRX state duration timer corresponding to the main DRX group at the first time; or,
    under the condition that the at least one DRX group comprises a secondary DRX group, the terminal equipment determines to start a DRX state duration timer corresponding to the secondary DRX group at the first time; or,
    and under the condition that the at least one DRX group comprises a main DRX group and an auxiliary DRX group, the terminal equipment determines to start a DRX state duration timer corresponding to the main DRX group and a DRX state duration timer corresponding to the auxiliary DRX group at the first time.
  4. The method of claim 2 or 3, wherein the method further comprises:
    and the terminal equipment determines to start or not start a DRX state duration timer corresponding to DRX groups except the at least one DRX group configured in the media access control MAC entity at the first time.
  5. The method of claim 4, wherein the terminal device determining whether to start or not start a DRX state duration timer corresponding to DRX groups other than the at least one DRX group configured in a MAC entity at the first time comprises:
    and the terminal equipment determines to start or not start a DRX state duration timer corresponding to the DRX groups except the at least one DRX group configured in the MAC entity at the first time according to the pre-configuration information.
  6. The method of claim 1, wherein the method further comprises:
    and under the condition that the terminal equipment does not receive the DCP, the terminal equipment determines to start or not start a DRX state duration timer corresponding to a DRX group configured in an MAC entity at a first time, wherein the first time is the time for starting the DRX state duration timer.
  7. The method of claim 6, wherein the terminal device determining whether to start or not start a DRX state duration timer corresponding to a DRX group configured in a MAC entity at a first time comprises:
    and the terminal equipment determines to start or not start a DRX state duration timer corresponding to the DRX group configured in the MAC entity at the first time according to the pre-configuration information.
  8. The method of claim 5 or 7,
    the pre-configuration information is pre-configured by the network equipment, or the pre-configuration information is agreed by a protocol.
  9. The method according to any of claims 1 to 8, wherein the first information is radio resource control, RRC, signaling.
  10. The method according to any of claims 1 to 9, wherein the method is applied to a carrier aggregation, CA, scenario.
  11. A method for Discontinuous Reception (DRX), comprising:
    the network equipment sends first information, wherein the first information is used for indicating at least one DRX group controlled by downlink control information (DCP) scrambled by energy-saving radio network temporary identification, and the at least one DRX group comprises a main DRX group and/or an auxiliary DRX group.
  12. The method of claim 11, wherein the first information is Radio Resource Control (RRC) signaling.
  13. The method according to claim 11 or 12, wherein the method is applied to a carrier aggregation, CA, scenario.
  14. A terminal device, comprising:
    the communication unit is used for receiving first information, wherein the first information is used for indicating at least one DRX group controlled by downlink control information (DCP) with scrambling of energy-saving wireless network temporary identity, and the at least one DRX group comprises a main DRX group and/or an auxiliary DRX group.
  15. The terminal device of claim 14, wherein the terminal device further comprises: a processing unit, wherein,
    and under the condition that the terminal equipment receives the DCP, the processing unit is used for determining to start a DRX state duration timer corresponding to the at least one DRX group at a first time according to the first information, wherein the first time is the time for starting the DRX state duration timer.
  16. The terminal device of claim 15, wherein the processing unit is specifically configured to:
    determining to start a DRX state duration timer corresponding to the primary DRX group at the first time when the at least one DRX group comprises the primary DRX group; or,
    determining to start a DRX state duration timer corresponding to the secondary DRX group at the first time, if the at least one DRX group comprises the secondary DRX group; or,
    and under the condition that the at least one DRX group comprises a main DRX group and an auxiliary DRX group, determining to start a DRX state duration timer corresponding to the main DRX group and a DRX state duration timer corresponding to the auxiliary DRX group at the first time.
  17. The terminal device of claim 15 or 16, wherein the processing unit is further configured to determine whether to start or not start DRX state duration timers corresponding to DRX groups other than the at least one DRX group configured in a medium access control, MAC, entity at the first time.
  18. The terminal device of claim 17, wherein the processing unit is specifically configured to:
    and determining to start or not start a DRX state duration timer corresponding to DRX groups except the at least one DRX group configured in the MAC entity at the first time according to the pre-configuration information.
  19. The terminal device of claim 14, wherein the terminal device further comprises: a processing unit, wherein,
    and the processing unit is configured to determine to start or not start a DRX state duration timer corresponding to a DRX group configured in a MAC entity at a first time when the DCP is not received by the terminal device, where the first time is a time for starting the DRX state duration timer.
  20. The terminal device of claim 19, wherein the processing unit is specifically configured to:
    and determining to start or not start a DRX state duration timer corresponding to a DRX group configured in the MAC entity at the first time according to the pre-configuration information.
  21. The terminal device according to claim 18 or 20,
    the pre-configuration information is pre-configured by the network equipment, or the pre-configuration information is agreed by a protocol.
  22. The terminal device according to any of claims 14 to 21, wherein the first information is radio resource control, RRC, signalling.
  23. The terminal device according to any of claims 14 to 22, wherein the terminal device is applied in a carrier aggregation, CA, scenario.
  24. A network device, comprising:
    the communication unit is used for sending first information, wherein the first information is used for indicating at least one DRX group controlled by downlink control information (DCP) scrambled by an energy-saving radio network temporary identifier, and the at least one DRX group comprises a main DRX group and/or a secondary DRX group.
  25. The network device of claim 24, wherein the first information is Radio Resource Control (RRC) signaling.
  26. Network device according to claim 24 or 25, wherein the network device is applied in a carrier aggregation, CA, scenario.
  27. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 10.
  28. A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 11 to 13.
  29. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 10.
  30. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 11 to 13.
  31. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 10.
  32. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 11 to 13.
  33. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 10.
  34. A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 11 to 13.
  35. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1-10.
  36. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 11-13.
CN202080103159.XA 2020-09-30 2020-09-30 Discontinuous reception method, terminal equipment and network equipment Pending CN115843445A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119565 WO2022067729A1 (en) 2020-09-30 2020-09-30 Discontinuous reception method, terminal device and network device

Publications (1)

Publication Number Publication Date
CN115843445A true CN115843445A (en) 2023-03-24

Family

ID=80951101

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080103159.XA Pending CN115843445A (en) 2020-09-30 2020-09-30 Discontinuous reception method, terminal equipment and network equipment

Country Status (2)

Country Link
CN (1) CN115843445A (en)
WO (1) WO2022067729A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651530A (en) * 2008-08-11 2010-02-17 中兴通讯股份有限公司 Method for processing conflict between discontinuous receiving and measurement clearance
CN102655668A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Discontinuous receiving method and device
US20150215912A1 (en) * 2014-01-30 2015-07-30 Satish Chandra Jha Discontinuous reception alignment in dual connectivity networks
CN110351898A (en) * 2018-04-04 2019-10-18 华为技术有限公司 Communication means, device, communication equipment and the communication system of discontinuous reception
US20200120596A1 (en) * 2017-06-16 2020-04-16 Huawei Technologies Co., Ltd. Drx configuration method, terminal device, network device, and communications system
CN111050423A (en) * 2018-10-15 2020-04-21 维沃移动通信有限公司 Discontinuous reception processing method and terminal
WO2020077643A1 (en) * 2018-10-19 2020-04-23 Oppo广东移动通信有限公司 Wireless communication method and terminal device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109429308B (en) * 2017-07-03 2021-07-20 中国移动通信有限公司研究院 Connection management method, terminal device, network device and storage medium
WO2020155166A1 (en) * 2019-02-02 2020-08-06 Zte Corporation Low power consumption cellular radio terminal

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651530A (en) * 2008-08-11 2010-02-17 中兴通讯股份有限公司 Method for processing conflict between discontinuous receiving and measurement clearance
CN102655668A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Discontinuous receiving method and device
US20150215912A1 (en) * 2014-01-30 2015-07-30 Satish Chandra Jha Discontinuous reception alignment in dual connectivity networks
US20200120596A1 (en) * 2017-06-16 2020-04-16 Huawei Technologies Co., Ltd. Drx configuration method, terminal device, network device, and communications system
CN110351898A (en) * 2018-04-04 2019-10-18 华为技术有限公司 Communication means, device, communication equipment and the communication system of discontinuous reception
CN111050423A (en) * 2018-10-15 2020-04-21 维沃移动通信有限公司 Discontinuous reception processing method and terminal
WO2020077643A1 (en) * 2018-10-19 2020-04-23 Oppo广东移动通信有限公司 Wireless communication method and terminal device

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
OPPO: "R2-2004553 "Further considerations on secondary DRX group"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 22 May 2020 (2020-05-22) *
VIVO: "R2-2004640 "Views on TEI for Secondary DRX Group"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 22 May 2020 (2020-05-22), pages 1 *
XIAOMI COMMUNICATIONS: "R2-2003103 "Discussion on PDCCH-WUS works with Dual DRX"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 10 April 2020 (2020-04-10) *
XIAOMI COMMUNICATIONS: "R2-2004786 "Views on introduction of Dual DRX"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 22 May 2020 (2020-05-22) *

Also Published As

Publication number Publication date
WO2022067729A1 (en) 2022-04-07

Similar Documents

Publication Publication Date Title
CN111869314B (en) Wireless communication method, terminal device, chip and medium
CN113728697B (en) Wireless communication method and terminal device
EP4250858A1 (en) Wireless communication method, terminal device and network device
EP4171162A1 (en) Data transmission method and terminal device
CN115699951A (en) Wireless communication method and terminal equipment
CN112740763A (en) Wireless communication method, terminal equipment and network equipment
CN116547933A (en) Wireless communication method, terminal equipment and network equipment
CN117320173A (en) Method and apparatus for wireless communication
CN115669133A (en) Wireless communication method, terminal equipment and network equipment
US20240023015A1 (en) Sidelink transmission method and terminal
CN114556988A (en) Physical channel monitoring method and terminal equipment
CN116744418A (en) Wireless communication method and terminal equipment
CN117859407A (en) Wireless communication method, terminal equipment and network equipment
CN116569644A (en) Wireless communication method and terminal equipment
CN116530149A (en) Paging indication method, terminal equipment and network equipment
CN115843445A (en) Discontinuous reception method, terminal equipment and network equipment
CN115843464A (en) Wireless communication method, terminal equipment and network equipment
WO2022233033A1 (en) Wireless communication method and device
EP4274315A1 (en) Wireless communication method, terminal device and network device
WO2023102788A1 (en) Wireless communication method, and terminal device and network device
CN118285140A (en) Wireless communication method, terminal equipment and network equipment
WO2022233031A1 (en) Wireless communication method and terminal devices
CN116530160A (en) Method for switching search space set packet SSSG by terminal equipment, terminal equipment and network equipment
CN117561790A (en) Wireless communication method, terminal equipment and network equipment
CN115988619A (en) Wireless communication method and terminal equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination