WO2021129508A1 - 唤醒信号处理方法、唤醒信号配置方法及相关设备 - Google Patents

唤醒信号处理方法、唤醒信号配置方法及相关设备 Download PDF

Info

Publication number
WO2021129508A1
WO2021129508A1 PCT/CN2020/137151 CN2020137151W WO2021129508A1 WO 2021129508 A1 WO2021129508 A1 WO 2021129508A1 CN 2020137151 W CN2020137151 W CN 2020137151W WO 2021129508 A1 WO2021129508 A1 WO 2021129508A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
wus
groups
group
cycle
Prior art date
Application number
PCT/CN2020/137151
Other languages
English (en)
French (fr)
Inventor
鲍炜
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP20904501.2A priority Critical patent/EP4054249A4/en
Publication of WO2021129508A1 publication Critical patent/WO2021129508A1/zh
Priority to US17/737,987 priority patent/US20220264696A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE 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/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of communication technology, and in particular to a wake-up signal processing method, a wake-up signal configuration method and related equipment.
  • DRX Discontinuous Reception
  • the terminal device in the DRX state does not need to continuously monitor the Physical Downlink Control Channel (PDCCH), and the network side device can predict the service of the terminal device Data volume, configure corresponding DRX parameters for terminal equipment, such as DRX cycle, offset, continuous monitoring timer, etc.
  • PDCCH Physical Downlink Control Channel
  • WUS PDCCH-based wake-up signal
  • DCI loop Redundancy check downlink control information
  • DCP loop Redundancy check downlink control information
  • the current WUS operation mode is defined based on the terminal device having only one set of DRX configuration. However, when the terminal device is configured with multiple DRX groups, there is no relevant solution for how to perform wake-up or sleep instructions on multiple DRX groups.
  • the embodiment of the present invention provides a wake-up signal processing method, a wake-up signal configuration method, and related equipment, so as to provide a relatively simple WUS indication solution when a terminal device is configured with multiple DRX groups.
  • the present invention is implemented as follows:
  • an embodiment of the present invention provides a wake-up signal processing method, which is applied to a terminal device, and the method includes:
  • the terminal device is configured with at least two discontinuous reception DRX groups, receiving a wake-up signal WUS;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups.
  • embodiments of the present invention also provide a wake-up signal configuration method, which is applied to a network side device, and the method includes:
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups.
  • an embodiment of the present invention also provides a terminal device, which includes:
  • a receiving module configured to receive a wake-up signal WUS when the terminal device is configured with at least two discontinuous receiving DRX groups;
  • the embodiment of the present invention also provides a network side device.
  • the network side equipment includes:
  • the configuration module is configured to configure a wake-up signal WUS for the terminal device when at least two discontinuous reception DRX groups are configured for the terminal device;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups.
  • an embodiment of the present invention also provides a terminal device, including a processor, a memory, and a computer program stored on the memory and running on the processor, the computer program being executed by the processor When realizing the steps of the wake-up signal processing method provided in the first aspect above.
  • an embodiment of the present invention also provides a network-side device, including a processor, a memory, and a computer program stored on the memory and running on the processor, and the computer program is used by the processor. When executed, the steps of the wake-up signal configuration method provided in the second aspect are implemented.
  • an embodiment of the present invention also provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the wake-up signal processing provided in the first aspect is implemented.
  • the terminal device when the terminal device is configured with multiple DRX groups, by receiving the WUS indicating whether to start the onDuration timer of the next DRX cycle of all DRX groups, the terminal device can decide based on the WUS Whether to start the onDuration timer in the next DRX cycle of each DRX group.
  • the embodiment of the present invention provides a relatively simple WUS indication solution for the situation that a terminal device is configured with multiple DRX groups.
  • Figure 1 is a structural diagram of a network system applicable to an embodiment of the present invention
  • Figure 3 is one of the schematic diagrams of the configuration of WUS in the DRX group provided by an embodiment of the present invention
  • FIG. 4 is the second schematic diagram of the configuration of WUS in the DRX group according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a wake-up signal configuration method provided by an embodiment of the present invention.
  • Figure 6 is a structural diagram of a terminal device provided by an embodiment of the present invention.
  • FIG. 7 is a structural diagram of a network side device provided by an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a terminal device provided by another embodiment of the present invention.
  • Fig. 9 is a structural diagram of a network side device provided by another embodiment of the present invention.
  • the terminal device can support two DRX cycles: a long DRX cycle and a short DRX cycle. If the data volume of the terminal equipment is predicted to be more frequent or the service is sensitive to delay, the network side equipment can configure the terminal equipment to use DRX short cycle; if the terminal data volume is predicted to be sparse and the delay is not sensitive, the network side equipment can configure the terminal equipment only Use long DRX cycle. In order to facilitate the terminal device to switch between the long DRX cycle and the short DRX cycle, the long DRX cycle is required to be an integer multiple of the short DRX cycle to ensure that the continuous monitoring time of the two is aligned.
  • the network side device will configure DRX-related timers and parameters for the terminal device, including:
  • drx-LongCycleStartOffset used to configure the period and offset of the long DRX cycle, the unit of period and offset is milliseconds;
  • drx-ShortCycle used to configure the period and offset of the short DRX cycle, the unit of period and offset is milliseconds;
  • drx-ShortCycleTimer used to control the duration of the short DRX cycle used by the terminal device, the unit is an integer, which means that once the terminal device enters the short DRX cycle, it should maintain the integer multiple of the short cycle;
  • drx-onDurationTimer DRX continuous monitoring timer. During the running of this timer, the terminal device needs to continuously monitor the PDCCH control channel of the network. The unit of this timer is milliseconds;
  • drx-SlotOffset The delay for the terminal device to start drx-onDurationTimer. This parameter is used to set the offset of the start time of DRX onDuration relative to the start of the subframe.
  • the offset is an integer multiple of 1/32 milliseconds.
  • the role of WUS is to inform the terminal device whether it needs to monitor the PDCCH during the onDuration of a specific DRX. When there is no data, the terminal device does not need to monitor the PDCCH during onDuration, which is equivalent to the terminal device can be in a sleep state during the entire DRX Long cycle, thereby further saving power.
  • WUS is a downlink physical control channel (Downlink Control Information, DCI), referred to as DCP (DCI with CRC scrambled by PS-RNTI), in which the power-saving wireless network temporary identifier PS-RNTI is allocated by the network for terminal equipment specifically for saving
  • DCI Downlink Control Information
  • PS-RNTI Downlink Control Information
  • the terminal device decides whether to start the onDuration timer in the next DRX cycle and whether to perform PDCCH monitoring.
  • Figure 1 is a structural diagram of a network system applicable to an embodiment of the present invention. As shown in Figure 1, it includes a terminal device 11 and a network side device 12.
  • the terminal device 11 may be a mobile phone or a tablet computer ( User-side devices such as Tablet Personal Computer, Laptop Computer, Personal Digital Assistant (PDA), Mobile Internet Device (MID), or Wearable Device (Wearable Device), etc. It is noted that the specific type of the terminal device 11 is not limited in the embodiment of the present invention.
  • the network side device 12 may be a base station, such as a macro station, LTE eNB, 5G NR NB, gNB, etc.; the network side device 12 may also be a small station, such as low power node (LPN) pico, femto, etc. Or, the network side device 12 may be an access point (Access Point, AP); the base station may also be a network node composed of a central unit (Central Unit, CU) and multiple TRPs managed and controlled by it. It should be noted that the specific type of the network side device 12 is not limited in the embodiment of the present invention.
  • the aforementioned network system may be a 5G communication system or a Long Term Evolution (LTE) communication system, which is not specifically limited.
  • LTE Long Term Evolution
  • the wake-up signal processing method provided by the embodiment of the present invention may be executed by the above-mentioned terminal device 11; the wake-up signal configuration method provided by the embodiment of the present invention may be executed by the above-mentioned network-side device 12, please refer to the following description for details.
  • FIG. 2 is a flowchart of a wake-up signal processing method provided by an embodiment of the present invention. As shown in FIG. 2, it includes the following steps:
  • Step 201 When the terminal device is configured with at least two discontinuous reception DRX groups, receive a wake-up signal WUS;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups.
  • the terminal device may be configured with multiple DRX groups, and a WUS may be configured in one of the DRX groups.
  • One WUS is used to control the at least two DRX groups to work together, and the WUS can indicate all Whether the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups is started.
  • Different DRX groups in the above at least two DRX groups can be understood as different carrier groups configured with different DRX parameter sets, where the DRX parameter set may include a set of DRX parameters.
  • component carriers (CCs) with different characteristics can be configured as different DRX groups, and corresponding DRX parameter sets can be configured for each DRX group.
  • the network side device may configure DRX parameters for the UE.
  • the UE configures/activates multiple CCs, if these CCs have different characteristics, for example, some of the CCs are at low frequency and some of the CCs are at high frequency. Therefore, in these two types of CCs, their transmission characteristics, such as those used for transmission
  • the parameter set (namely numerology) is very different, so a more efficient way is to configure two different DRX parameters for the UE, which are used for CC groups with different characteristics.
  • This is equivalent to configuring two sets of DRX parameters for the UE, which are used for two CC groups respectively.
  • the UE can be configured according to the DRX parameters to allocate and start and maintain the corresponding DRX state for the two DRX groups.
  • each set of DRX parameters can include DRX cycle (long DRX cycle, short DRX cycle, etc.), offset, the length of time the UE uses the short DRX cycle, the DRX continuous monitoring timer, the delay for the UE to start the DRX continuous monitoring timer, etc. .
  • the terminal device when the terminal device is configured with at least two DRX groups, the terminal device can receive the WUS sent by the network side device, and can activate or deactivate the WUS according to the instructions of the WUS.
  • the onDuration timer of the next DRX cycle of all DRX groups in at least two DRX groups may be in the case where the WUS instructs to start the onDuration timer of the next DRX cycle of all DRX groups (for example, the WUS is Wake-up indication WUS on), and start the onDuration timer of the next DRX cycle of all DRX groups at the same time.
  • WUS is configured on the primary cell (Primary cell, Pcell)/Special cell (Special cell, Spcell).
  • the DRX group in which the Pcell is located is called Pcell DRX group or Primary DRX group, and other DRX groups are called Secondary cell (Scell) DRX group or Secondary DRX group.
  • WUS can use common bits (ie bits) to indicate multiple Wake up/sleep of DRX group.
  • the network side device configures two DRX groups for the UE, and configures a WUS on DRX group1.
  • the two DRX groups are described in detail below. How does the group perform the wake-up and sleep operations expected by the network side device under the control of a WUS?
  • Figure 3 shows the running status of an optional two DRX group configuration timers.
  • DRX group1 and DRX group2 can have different timer lengths, for example, onDuration timer, Inactivity timer, or even mixed Automatic retransmission request (Hybrid Automatic Repeat reQuest, HARQ) Round Trip Time (RTT) timer, HARQ retransmission (Retransmission, RETX) timer, etc., whether the short DRX cycle (short DRX cycle) is started and its duration
  • RTT Round Trip Time
  • RETX HARQ retransmission
  • the configuration, DRX cycle offset (DRX cycle offset) and other parameters can all have different values.
  • the final effect is that these two DRX groups perform their own independent DRX status and timer maintenance according to their own timers and parameter configurations, and according to data scheduling and retransmission conditions.
  • the UE monitors (receives) WUS on the time-frequency resources configured by WUS, and according to the content indicated by WUS, determines DRX group1 in the next DRX cycle (as shown in Figure 2 DRX group1 is located in WUS on/WUS In the adjacent DRX cycle after the off time domain position, whether the onDuration timer is started and whether to monitor the PDCCH. Although there are two DRX groups at this time, two groups need to be controlled by one WUS at the same time. Therefore, although there is no WUS configuration on DRX group2, the WUS indication in DRX group1 is also applicable to determine the timer status of DRX group2 And PDCCH monitoring status.
  • a WUS can indicate all the cells in the DRX group at the same time, and they will be in the dormant state in the next DRX cycle, further saving the power of the UE; only when there is a service to be transmitted, WUS Only instruct the cells in the two DRX groups to start the onDuration timer and PDCCH monitoring in the next DRX cycle to prepare for data transmission.
  • the method further includes:
  • the UE may also determine whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups according to the indication of the WUS.
  • the onDuration timer may be set in the WUS If it is a wake-up indication (for example, the received WUS indication value is on), it is determined to start the onDuration timer of the next DRX cycle of all DRX groups, and the WUS indication is a sleep indication (for example, the received WUS indication value is off) In the case, it is determined not to start the onDuration timer of the next DRX cycle of all DRX groups.
  • the UE may start the onDuration timer of the next DRX cycle of all DRX groups or not start the onDuration timer of the next DRX cycle of all DRX groups according to the determination result.
  • the method before the receiving the wake-up signal WUS, the method further includes:
  • Receiving the WUS means giving up receiving the WUS.
  • the determining whether to receive the WUS according to the state of some or all of the DRX groups in the at least two DRX groups may include any one of the following:
  • the time domain position of the WUS is located at the activation time of the first DRX group, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS; wherein, the first DRX group is the at least two DRX groups The DRX group in which the WUS is configured;
  • the time domain position of the WUS is located at the activation time of all DRX groups in the at least two DRX groups, determine to abandon receiving the WUS, otherwise determine to receive the WUS;
  • the time domain position of the WUS is located at the activation time of any one of the at least two DRX groups, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS.
  • the UE When the configured time domain location of WUS overlaps with Activetime, that is, the time location where WUS should be monitored. Due to the scheduling of the previous DRX cycle, the UE is still in the monitoring active state, that is, it continues to monitor the PDCCH state. Need to monitor WUS, directly enter the continuous activation state, that is, start the onDuration timer and monitor the PDCCH in the next DRX cycle.
  • the primary DRX group (Primary DRX group) is in Activetime to determine whether the WUS is in the Activetime period, that is, whether the time domain position of the WUS conflicts with Activetime, and then decide whether or not according to whether there is a conflict.
  • Monitoring WUS where the Primary DRX group may be a DRX group configured with the WUS among the at least two DRX groups.
  • the time domain position of the WUS may be located at the activation time of the first DRX group, that is, When the time domain position of the WUS overlaps with the activation time of the first DRX group, it is determined that the time domain position of the WUS conflicts with the activation time of the first DRX group, thereby determining to abandon receiving the WUS;
  • the time domain position of the WUS is not located at the activation time of the first DRX group, or the time domain position of the WUS is located at the non-active time of the first DRX group (Non-Activetime), that is, When the time domain location of the WUS does not overlap with the activation time of the first DRX group, it can be determined that the time domain location of the WUS does not conflict with the activation time of the first DRX group, so as to determine to receive the WUS.
  • the Activetime of each DRX group in the at least two DRX groups may be considered at the same time to determine whether the time domain position of the WUS conflicts with Activetime, and then whether to listen to the WUS is determined according to whether the conflict is. Divided into two different situations:
  • the time domain position of the WUS may be in the overlapping area of the activation time of each DRX group in the at least two DRX groups, that is, the time domain position of the WUS and each DRX group
  • the activation times of the groups overlap, and it is determined that the time domain position of the WUS conflicts with the activation time of each DRX group, so as to determine to abandon receiving the WUS; and the time domain position of the WUS is not located in the activation time of each DRX group
  • time that is, when there is at least one DRX group activation time that does not overlap with the time domain position of the WUS, it can be determined that the time domain position of the WUS does not conflict with the activation time of the at least two DRX groups, and thus Confirm to receive the WUS.
  • the time domain position of the WUS may be located at the activation time of any DRX group of the at least two DRX groups, that is, there is the activation time of at least one DRX group and the WUS
  • the time domain position of the WUS overlaps, and it is determined that the time domain position of the WUS conflicts with the activation time of the at least two DRX groups, thereby determining to abandon receiving the WUS; and the time domain position of the WUS is not located in any DRX group
  • the time domain of the WUS can be determined The location does not conflict with the activation time of the at least two DRX groups, thereby determining to receive the WUS.
  • the method may further include the following items:
  • start the onDuration timer of the next DRX cycle of the second DRX group of the at least two DRX groups where the second DRX group is the at least two DRX groups.
  • the DRX group in which the WUS is configured in or the second DRX group is a DRX group in the at least two DRX groups whose activation time and the time domain position of the WUS overlap.
  • the at least two DRX groups can be directly activated without monitoring WUS The onDuration timer of the next DRX cycle of some or all of the DRX groups.
  • the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups can be directly started, which is not only simpler to implement, but also can reduce transmission Time delay.
  • only the onDuration timer of the next DRX cycle of a certain DRX group of the at least two DRX groups may be started. For example, only at least two DRX cycles may be started.
  • Each DRX group is configured with the onDuration timer of the next DRX cycle of the DRX group of the WUS, or it may only start the next DRX cycle of the DRX group whose activation time conflicts with the time domain position of the WUS in at least two DRX groups
  • the onDuration timer can reduce the transmission delay while saving power.
  • the following takes the UE configured with two DRX groups (Primary DRX group and Secondary DRX group) as an example to describe this embodiment. Since the activation states of the two DRX groups are independent of each other, the two DRX groups and the time domains configured by WUS The positional relationship has the following four situations:
  • Case 1 In the time domain position configured by WUS, the status of Primary DRX group (that is, the group where WUS is located) is Activetime, and the status of Secondary DRX group (that is, the group without WUS) is Non-Activetime;
  • Case 2 In the time domain position configured by WUS, the status of Primary DRX group is Activetime, and the status of Secondary DRX group is also Activetime;
  • Case 3 In the time domain position configured by WUS, the status of Primary DRX group is Non-Activetime, and the status of Secondary DRX group is Activetime;
  • the status of the two DRX groups, Primary DRX group and Secondary DRX group can correspond to the four situations shown in the following table.
  • Method 1 Only consider whether the Primary DRX group is in Active time to determine whether WUS is in Active time:
  • case1 and case2 are judged as conflicts, and the UE does not need to perform WUS monitoring at the time-frequency position configured by WUS, and by default two DRX groups in the next DRX cycle start onDuration timers at the same time and monitor PDCCH at the same time;
  • case3 and case4 are judged to be non-conflicting, and the UE needs to monitor WUS at the time-frequency position configured by WUS, and according to WUS instructions, such as on or off, to determine whether two DRX groups simultaneously start onDuration timers in the next DRX cycle , Whether to monitor the PDCCH at the same time.
  • Method 2 Consider the Active time of Primary DRX group and Secondary DRX group at the same time. This method is divided into two sub-branch:
  • Branch 1 Only when the two DRX groups in the time domain where WUS is located are in Activetime (ie case2), it is determined that WUS conflicts with Activetime, and the other cases (case1, case3, and case4) are all determined to be non-conflicting;
  • Branch 2 Only when the two DRX groups in the time domain where WUS is located are in Non-Activetime (ie case4), it is determined that WUS and Activetime do not conflict, and the rest of the cases (case1, case2, and case3) are all judged as conflicts.
  • the UE When it is judged that WUS conflicts with Activetime, the UE does not need to perform WUS monitoring at the time-frequency position configured by WUS, and by default two DRX groups in the next DRX cycle start onDuration timers at the same time and monitor PDCCH at the same time;
  • the UE When it is judged that WUS and Activetime do not conflict, the UE needs to monitor WUS at the time-frequency position configured by WUS, and according to WUS instructions, such as on or off, determines whether two DRX groups simultaneously start onDuration timers in the next DRX cycle , Whether to monitor the PDCCH at the same time.
  • the method further includes any one of the following:
  • the WUS reception fails, it is determined whether to start the onDuration timer of the next DRX cycle of some or all of the DRX groups of the at least two DRX groups according to the first indication; wherein, the first indication is the protocol preset Definition or network side device configuration;
  • the WUS reception fails, it is determined whether to start the onDuration timer of the next DRX cycle of some or all of the DRX groups in the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups .
  • the UE After the network side device configures the WUS time-frequency position for the UE, the UE needs to perform WUS detection on the time-frequency position configured by the WUS to receive WUS, but in actual transmission, the communication link quality may be poor, or the UE needs Perform other high-priority operations, and cause the UE to fail to detect WUS correctly, and thus fail to receive WUS. Therefore, it is impossible to know whether the next DRX cycle notified by the network-side device is a wake-up indication or a sleep indication. In this case, The behavior of the UE in the at least two DRX groups needs to be clearly defined to ensure that the behavior of the UE is within the controllable range of the network side device.
  • the proposed corresponding processing solution for the monitoring behavior of the at least two DRX groups of the UE in the next DRX cycle may specifically include the following three different processing solutions.
  • the corresponding indication can be pre-configured to inform the UE how to determine its monitoring behavior.
  • the first indication can be pre-defined by the protocol or configured by the network side device to indicate that the UE fails to receive the WUS. In this case, whether to start the onDuration timer of the next DRX cycle of part or all of the at least two DRX groups.
  • the network-side device configures the first instruction for the UE, the network-side device can deliver the configured first instruction to the UE, so that the UE can receive the first instruction from the first instruction if the WUS reception fails. It is determined in an instruction that the onDuration timer of the next DRX cycle of which of the at least two DRX groups needs to be started.
  • the first indication may instruct the UE to only start the onDuration timer of the next DRX cycle of the partial DRX groups of the at least two DRX groups, for example, only start the major DRX group and the DRX configured with the WUS.
  • the onDuration timer of the next DRX cycle of the DRX group or the DRX group currently scheduled with data to ensure terminal services and save transmission resources; alternatively, the UE can also be instructed to start the next DRX of all DRX groups of the at least two DRX groups Periodic onDuration timer to guarantee the service transmission of the terminal first; alternatively, it can also instruct the UE not to start the onDuration timer of the next DRX cycle of some DRX groups of the at least two DRX groups, such as not starting the non-primary onDuration timer.
  • the onDuration timer of the next DRX cycle of all DRX groups in the group is not started, so as to save transmission resources and power first.
  • the first indication may include one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications They respectively correspond to different DRX groups of the at least two DRX groups.
  • a common indication may be configured for the at least two DRX groups to instruct the UE to start or not to start the onDuration timer of the next DRX cycle of all DRX groups at the same time; it may also be the at least two DRX groups
  • Each DRX group in each DRX group is configured with an independent indication, or a common indication is configured for a certain part of the at least two DRX groups, or a common indication is configured for a certain part of the at least two DRX groups
  • the network-side device can configure the UE to be in the waked up or dormant state when the UE misses/misdetects WUS through Radio Resource Control (RRC) signaling, where the network-side device can Configure a common WUS misdetection state indicator for Primary DRX group and Secondary DRX group, or configure an independent WUS misdetection state indicator for them.
  • RRC Radio Resource Control
  • the common WUS misdetection state indicator when the common WUS misdetection state indicator is configured to be on, if the UE has a WUS misdetection, the UE defaults to the two DRX groups in the next DRX cycle to start the onDuration timer at the same time and monitor the PDCCH at the same time; when the common WUS misdetection When the state indicator is configured as off, if the UE has a WUS misdetection, the UE defaults that the two DRX groups in the next DRX cycle do not start the onDuration timer at the same time, and do not monitor the PDCCH at the same time;
  • the UE When the independent WUS misdetection state indicators are configured separately, if the UE has a WUS misdetection, the UE independently decides whether to start the onDuration timer in the next DRX cycle and whether to monitor the PDCCH according to the instructions configured for the respective DRX group.
  • the UE can determine its monitoring behavior by itself according to preset rules. Specifically, in the case that the UE fails to receive the WUS, it can initiate the downloading of some or all of the at least two DRX groups. A DRX cycle onDuration timer.
  • the UE may only start the onDuration timer of the next DRX cycle of the partial DRX group of the at least two DRX groups, such as only the main DRX group, the DRX group configured with the WUS, or the one that currently has data scheduling.
  • the onDuration timer of the next DRX cycle of the DRX group to ensure its services and save transmission resources; or, it is also possible to start the onDuration timer of the next DRX cycle of all DRX groups of the at least two DRX groups to ensure priority Its business transmission.
  • starting the onDuration timer of the next DRX cycle of part or all of the DRX groups of the at least two DRX groups includes any one of the following:
  • the third DRX group is the DRX group configured with the WUS among the at least two DRX groups .
  • a simple and direct UE behavior is that the UE wakes up by default, that is, if the UE has WUS misdetection, the UE will start onDuration timing by default for all DRX groups in the next DRX cycle. It also monitors the PDCCH, which can avoid missing the scheduling of the network-side equipment, improve the service transmission experience and delay, and because the probability of WUS misdetection is not high, it has little impact on power consumption.
  • only the DRX group configured with the WUS among the at least two DRX groups may be awakened by default.
  • the WUS is configured in the Primary DRX group
  • the UE may determine its monitoring behavior according to the status of at least one DRX group in the at least two DRX groups. Specifically, when the WUS reception fails, the UE may determine its monitoring behavior according to the at least two DRX groups. At least one DRX group in the DRX group is currently active or inactive to determine whether to start the onDuration timer of the next DRX cycle of some or all of the DRX groups of the at least two DRX groups; wherein, the at least one DRX group It may be the main DRX group of the at least two DRX groups, the DRX group configured with the WUS, or the DRX group currently having data scheduling.
  • Part of the DRX groups of the at least two DRX groups may be related to the at least one DRX group.
  • the DRX group corresponding to the DRX group may also be the main DRX group of the at least two DRX groups, the DRX group configured with the WUS, or the DRX group currently scheduled with data.
  • the onDuration timer of the next DRX cycle of some DRX groups in the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups for example, in the
  • a certain part of the DRX group of at least two DRX groups is in Activetime in the time domain of WUS, it can be judged that the possibility of data scheduling for this part of the DRX group in the next DRX cycle is very high, so the next DRX of this part of the DRX group can be started Periodic onDuration timer; or, it is also possible to determine whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups, For example, when some or all of the at least two DRX groups are in Activetime in the time domain position of the WUS, the onDuration timer of the next
  • determining whether to start the next DRX of some or all of the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups Periodic onDuration timer including:
  • the fourth DRX group is any one of the at least two DRX groups.
  • the onDuration timer of the next DRX cycle of the DRX group whose activation time overlaps with the time domain position of the WUS in the at least two DRX groups can be started, and Do not start the onDuration timer of the next DRX cycle of other DRX groups.
  • a DRX group is in Activetime during the WUS time domain, it is considered that data scheduling is possible in the next DRX cycle
  • the UE will start the onDuration timer by default to monitor the PDCCH; and for a DRX group in the non-active time during the WUS time domain, it is considered that the possibility of sleeping in the next DRX cycle is very high. If the DRX group is larger, in the next DRX cycle, the UE does not start the onDuration timer by default and does not monitor the PDCCH.
  • the fifth DRX group is configured with a long DRX cycle parameter and a short DRX cycle parameter, the long DRX cycle is an integer multiple of the short DRX cycle, and the fifth DRX group is the at least two DRX cycles Any DRX group in the group;
  • the method also includes the following:
  • the fifth DRX group works in the short DRX cycle
  • WUS time window before onDuration of the long DRX cycle is configured with the time domain position of the WUS, then according to the long DRX cycle WUS received in the WUS time window before onDuration, determining whether to start onDuration timers of all short DRX cycles within the range of the long DRX cycle;
  • the time domain position of the WUS is configured according to each short DRX cycle.
  • the WUS received in the WUS time window before the onDuration of the DRX cycle determines whether to start the onDuration timer of each short DRX cycle.
  • a DRX group can be configured with a long DRX cycle and a short DRX cycle at the same time.
  • the short DRX cycle can be used.
  • the long DRX cycle can be configured to be an integer multiple of the short DRX cycle, so that the continuous monitoring time can be aligned.
  • the fifth DRX group of the at least two DRX groups is configured with long DRX cycle parameters and short DRX cycle parameters, and the fifth DRX group works in the short DRX cycle
  • the fifth DRX group may be a DRX group configured with the WUS among the at least two DRX groups.
  • the network-side device may only configure one WUS time window in each long DRX cycle of the fifth DRX group to instruct the UE to uniformly start or not start the long DRX through a WUS All onDuration timers in the cycle, so that WUS only appears in the WUS time window before onDuration of each long DRX cycle.
  • the UE can monitor WUS in the WUS time window before onDuration of each long DRX cycle , And can determine whether to start onDuration timers of all short DRX cycles within the range of the long DRX cycle according to the monitored WUS, that is, the received WUS.
  • the onDuration timers of all short DRX cycles within the range of the long DRX cycle can be started, if it is before the onDuration of a long DRX cycle If the WUS received in the WUS time window indicates dormancy, the onDuration timers of all short DRX cycles within the range of the long DRX cycle may not be started.
  • the WUS received in the WUS time window before onDuration of the long DRX cycle can be used to determine whether to activate the N short DRX cycles within the range of the long DRX cycle.
  • An onDuration timer is if a long DRX cycle includes N short DRX cycles, the WUS received in the WUS time window before onDuration of the long DRX cycle can be used to determine whether to activate the N short DRX cycles within the range of the long DRX cycle.
  • the network-side device may perform each short DRX cycle of the fifth DRX group separately.
  • a WUS time window is configured in the WUS to instruct the UE to start or not start the onDuration timer in the short DRX cycle through an independent WUS.
  • WUS will appear in the WUS time window before the onDuration of each short DRX cycle.
  • the UE can monitor the WUS in the WUS time window before the onDuration of each short DRX cycle, and can determine whether to start the onDuration timer of each short DRX cycle according to the monitored WUS, that is, the received WUS.
  • the onDuration timer of the short DRX cycle can be started, if the WUS indication received in the WUS time window before onDuration of a short DRX cycle In sleep mode, the onDuration timer of the short DRX cycle may not be started.
  • a long DRX cycle includes N short DRX cycles, it can be determined whether to start the onDuration timer corresponding to the short DRX cycle according to the WUS received in the WUS time window before the onDuration of the N short DRX cycles.
  • the configuration of the short DRX cycle is to switch between being awakened and sleeping faster during the data burst, so that the data can be quickly scheduled when the data connection arrives.
  • Long DRX cycle i.e. long DRX cycle
  • short DRX cycle i.e. Short DRX cycle
  • the advantage of this is that it is convenient to switch between long DRX cycle and short DRX cycle .
  • the long DRX cycle is 5 times the short DRX cycle.
  • the UE enters the short DRX cycle, which is shown by the shorter protrusion in the figure.
  • the location is during the onDuration timer in each short DRX cycle.
  • the length of the onDuration timer in the short DRX cycle and the long DRX cycle is the same.
  • the short DRX cycle configuration parameters can specify the duration parameters of the short DRX cycle. After the short DRX cycle, if there is still no data transmission, it will return to the long DRX cycle.
  • the UE will always be in the long DRX cycle. After the short DRX cycle shown in Figure 4, there is still no data scheduling, and the UE enters the long DRX cycle again.
  • the short DRX cycle is configured only when the business needs require short delay requirements.
  • the DRX group configuration is related to the carrier, and the carrier can also have a configuration binding relationship with the service transmission. For example, only when Services transmitted on the Secondary DRX group need to be configured with short DRX cycle.
  • different short DRX cycle parameters can be configured for different DRX groups, such as whether the short DRX cycle is activated, and the number of continuous short cycles.
  • the short DRX cycle can be performed according to whether it is started or not and the specific parameters. Maintain separately.
  • WUS can be executed in the following different ways:
  • Method 1 When WUS only appears in the WUS time window (WUS window) before the onDuration of the long DRX cycle, that is, there is only one WUS time window position in a long DRX cycle. At this time, the WUS indication or the various types described in the previous embodiments The awakened/sleeping behavior can be applied to all possible onDuration timers in the long DRX cycle at the same time.
  • the WUS indicator before the first long DRX cycle is on, then the onDuration in the long DRX cycle
  • the timer (implied in the first longer protrusion) and the onDuration timers of 4 short DRX cycles will both start and monitor the PDCCH; while the WUS indicator before the onDuration of the second long DRX cycle is off, the first All onDuration timers in the two long DRX cycles are not started, and the PDCCH is not monitored.
  • Method 2 If after entering the short DRX cycle, there is a corresponding WUS configuration before the onDuration of each short DRX cycle, and whether the onDuration timer of each short DRX cycle is started is determined by the corresponding WUS instruction. In particular, if the WUS is only configured in the Primary DRX group, in simple terms, the Primary DRX group enters the short DRX cycle and monitors the WUS before the onDuration of each short DRX cycle.
  • a certain DRX group in the at least two DRX groups is configured with a long DRX cycle and a short DRX cycle, and the DRX group works in a short DRX cycle, it can be based on the WUS time window configured in each DRX cycle Receive WUS, and determine whether to start the onDuration timer in the corresponding DRX cycle according to the received WUS, so as to effectively indicate how the DRX group performs wake-up or sleep behavior.
  • the terminal device when the terminal device is configured with multiple DRX groups, by receiving WUS indicating whether to start the onDuration timer of the next DRX cycle of all DRX groups, the terminal device can be based on The WUS determines whether to start the onDuration timer in the next DRX cycle of each DRX group.
  • the embodiment of the present invention provides a relatively simple WUS indication solution for the situation that a terminal device is configured with multiple DRX groups.
  • FIG. 5 is a flowchart of a wake-up signal configuration method provided by an embodiment of the present invention. As shown in FIG. 5, it includes the following steps:
  • Step 501 When at least two discontinuous reception DRX groups are configured for a terminal device, configure a wake-up signal WUS for the terminal device;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups.
  • one WUS can be configured for the terminal device, and one WUS is used to control the at least two DRX groups to work together, that is, the WUS can
  • the onDuration timers indicating the next DRX cycle of all DRX in the at least two DRX groups are all started or all dormant.
  • this embodiment is used as an implementation manner of the network side device corresponding to the embodiment shown in FIG. 2.
  • the relevant description in the embodiment shown in FIG. 2 please refer to the relevant description in the embodiment shown in FIG. 2, in order to avoid repetitive descriptions. , This embodiment will not go into details.
  • the terminal device when at least two DRX groups are configured for a terminal device, the terminal device is configured to indicate whether to start the onDuration timer of the next DRX cycle of all DRX. , The terminal device can determine whether to start the onDuration timer in the next DRX cycle of each DRX group based on the WUS, which provides a simpler WUS indication solution.
  • the method may further include:
  • the first indication is used to indicate whether to start the onDuration timer of the next DRX cycle of part or all of the at least two DRX groups when the WUS reception fails.
  • the first indication includes one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications The indications respectively correspond to different DRX groups of the at least two DRX groups.
  • the terminal device 600 includes:
  • the receiving module 601 is configured to receive a wake-up signal WUS when the terminal device is configured with at least two discontinuous receiving DRX groups;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups.
  • the terminal device 600 further includes:
  • the first determining module is configured to determine whether to receive the WUS according to the state of some or all of the DRX groups in the at least two DRX groups.
  • the first determining module is specifically used for the following items:
  • the time domain position of the WUS is located at the activation time of the first DRX group, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS; wherein, the first DRX group is the at least two DRX groups The DRX group in which the WUS is configured;
  • the time domain position of the WUS is located at the activation time of all DRX groups in the at least two DRX groups, determine to abandon receiving the WUS, otherwise determine to receive the WUS;
  • the time domain position of the WUS is located at the activation time of any one of the at least two DRX groups, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS.
  • the terminal device 600 further includes a first startup module, which is specifically used for the following items:
  • start the onDuration timer of the next DRX cycle of the second DRX group of the at least two DRX groups where the second DRX group is the at least two DRX groups.
  • the DRX group in which the WUS is configured in or the second DRX group is a DRX group in the at least two DRX groups whose activation time and the time domain position of the WUS overlap.
  • the terminal device 600 further includes:
  • the second determining module is configured to determine whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups according to the WUS.
  • the terminal device 600 further includes the following items:
  • the third determining module is configured to determine whether to start the onDuration timer of the next DRX cycle of part or all of the at least two DRX groups according to the first indication when the WUS reception fails; where
  • the first instruction is protocol pre-defined or network side device configuration;
  • the second starting module is configured to start the onDuration timer of the next DRX cycle of part or all of the DRX groups of the at least two DRX groups when the WUS reception fails;
  • the fourth determining module is configured to determine whether to start downloading some or all of the DRX groups in the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups when the WUS reception fails A DRX cycle onDuration timer.
  • the first indication includes one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications The indications respectively correspond to different DRX groups of the at least two DRX groups.
  • the second startup module is specifically used for one of the following:
  • the third DRX group is the DRX group configured with the WUS among the at least two DRX groups .
  • the fourth determining module is specifically configured to, in the case that the WUS reception fails, if the time domain position of the WUS is located at the activation time of the fourth DRX group, start downloading of the fourth DRX group A DRX cycle onDuration timer;
  • the fourth DRX group is any one of the at least two DRX groups.
  • the fifth DRX group is configured with long DRX cycle parameters and short DRX cycle parameters, the long DRX cycle is an integer multiple of the short DRX cycle, and the fifth DRX group is the at least two DRX cycles Any DRX group in the group;
  • the terminal device 600 also includes a fifth determining module, which is specifically used for the following items:
  • the fifth DRX group works in the short DRX cycle
  • the WUS time window before onDuration of the long DRX cycle is configured with the time domain position of the WUS, then according to the long DRX cycle
  • the WUS received in the WUS time window before onDuration determines whether to start onDuration timers of all short DRX cycles within the range of the long DRX cycle;
  • the time domain position of the WUS is configured according to the time domain respectively.
  • the WUS received in the WUS time window before the onDuration of the short DRX cycle determines whether to start the onDuration timer of each short DRX cycle.
  • the terminal device 600 provided in the embodiment of the present invention can implement the various processes implemented by the terminal device in the above embodiment of the wake-up signal processing method. In order to avoid repetition, details are not described herein again.
  • the terminal device 600 of the embodiment of the present invention receives WUS indicating whether to start the onDuration timer of the next DRX cycle of all DRX groups, so that the terminal device can determine based on the WUS Whether to start the onDuration timer in the next DRX cycle of each DRX group provides a simpler WUS indication solution when the terminal device is configured with multiple DRX groups.
  • FIG. 7 is a structural diagram of a network side device according to an embodiment of the present invention.
  • the network side device 700 includes:
  • the configuration module 701 is configured to configure a wake-up signal WUS for the terminal device when at least two discontinuous reception DRX groups are configured for the terminal device;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups.
  • the network side device 700 further includes:
  • a sending module configured to send a first instruction to the terminal device
  • the first indication is used to indicate whether to start the onDuration timer of the next DRX cycle of part or all of the at least two DRX groups when the WUS reception fails.
  • the first indication includes one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications The indications respectively correspond to different DRX groups of the at least two DRX groups.
  • the network-side device 700 provided in the embodiment of the present invention can implement the various processes implemented by the network-side device in the above embodiment of the wake-up signal configuration method. In order to avoid repetition, details are not described herein again.
  • the network side device 700 in the embodiment of the present invention configures the terminal device with WUS that is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX,
  • the terminal device can determine whether to start the onDuration timer in the next DRX cycle of each DRX group based on the WUS, which provides a simpler WUS indication solution when the terminal device is configured with multiple DRX groups.
  • FIG. 8 is a structural diagram of another terminal device provided by an embodiment of the present invention.
  • the terminal device 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, processing 810, and power supply 811.
  • a radio frequency unit 801 for example, a radio frequency unit 801
  • the terminal device 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, processing 810, and power supply 811.
  • the structure of the terminal device shown in FIG. 8 does not constitute a limitation on the terminal device, and the terminal device may include more or fewer components than shown in the figure, or a combination of certain components, or different components.
  • terminal devices include, but are not
  • the radio frequency unit 801 is configured to receive the wake-up signal WUS when the terminal device is configured with at least two discontinuous reception DRX groups;
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX groups in the at least two DRX groups.
  • the processor 810 is configured to:
  • processor 810 is further used for the following items:
  • the time domain position of the WUS is located at the activation time of the first DRX group, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS; wherein, the first DRX group is the at least two DRX groups The DRX group in which the WUS is configured;
  • the time domain position of the WUS is located at the activation time of all DRX groups in the at least two DRX groups, determine to abandon receiving the WUS, otherwise determine to receive the WUS;
  • the time domain position of the WUS is located at the activation time of any one of the at least two DRX groups, it is determined to abandon receiving the WUS, otherwise it is determined to receive the WUS.
  • processor 810 is further used for the following items:
  • start the onDuration timer of the next DRX cycle of the second DRX group of the at least two DRX groups where the second DRX group is the at least two DRX groups.
  • the DRX group in which the WUS is configured in or the second DRX group is a DRX group in the at least two DRX groups whose activation time and the time domain position of the WUS overlap.
  • processor 810 is further configured to:
  • processor 810 is further used for the following items:
  • the WUS reception fails, it is determined whether to start the onDuration timer of the next DRX cycle of some or all of the DRX groups of the at least two DRX groups according to the first indication; wherein, the first indication is a protocol preset Definition or network side device configuration;
  • the WUS reception fails, it is determined whether to start the onDuration timer of the next DRX cycle of some or all of the DRX groups in the at least two DRX groups according to the state of at least one DRX group in the at least two DRX groups .
  • processor 810 is further used for the following items:
  • the first indication includes one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications are respectively related to all DRX groups.
  • the at least two DRX groups correspond to different DRX groups.
  • processor 810 is further used for the following items:
  • the third DRX group is the DRX group configured with the WUS among the at least two DRX groups .
  • processor 810 is further configured to:
  • the fourth DRX group is any one of the at least two DRX groups.
  • the fifth DRX group is configured with long DRX cycle parameters and short DRX cycle parameters, the long DRX cycle is an integer multiple of the short DRX cycle, and the fifth DRX group is the at least two DRX cycles Any DRX group in the group;
  • the processor 810 is also used for the following items:
  • the fifth DRX group works in the short DRX cycle
  • the WUS time window before onDuration of the long DRX cycle is configured with the time domain position of the WUS, then according to the long DRX cycle
  • the WUS received in the WUS time window before onDuration determines whether to start onDuration timers of all short DRX cycles within the range of the long DRX cycle;
  • the time domain position of the WUS is configured according to the time domain respectively.
  • the WUS received in the WUS time window before the onDuration of the short DRX cycle determines whether to start the onDuration timer of each short DRX cycle.
  • the terminal device 800 can implement the various processes implemented by the terminal device in the foregoing embodiments, and in order to avoid repetition, details are not described herein again.
  • the terminal device 600 of the embodiment of the present invention receives WUS indicating whether to start the onDuration timer of the next DRX cycle of all DRX groups, so that the terminal device can determine based on the WUS Whether to start the onDuration timer in the next DRX cycle of each DRX group.
  • the embodiment of the present invention provides a relatively simple WUS indication solution for the situation that a terminal device is configured with multiple DRX groups.
  • the radio frequency unit 801 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, the downlink data from the base station is received and processed by the processor 810; in addition, Uplink data is sent to the base station.
  • the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 801 can also communicate with the network and other devices through a wireless communication system.
  • the terminal device provides users with wireless broadband Internet access through the network module 802, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 803 can convert the audio data received by the radio frequency unit 801 or the network module 802 or stored in the memory 809 into audio signals and output them as sounds. Moreover, the audio output unit 803 may also provide audio output related to a specific function performed by the terminal device 800 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 803 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 804 is used to receive audio or video signals.
  • the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042.
  • the graphics processor 8041 is configured to monitor images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
  • the processed image frame may be displayed on the display unit 806.
  • the image frame processed by the graphics processor 8041 may be stored in the memory 809 (or other storage medium) or sent via the radio frequency unit 801 or the network module 802.
  • the microphone 8042 can receive sound and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 801 for output in the case of a telephone call mode.
  • the terminal device 800 also includes at least one sensor 805, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 8061 according to the brightness of the ambient light
  • the proximity sensor can close the display panel 8061 and the display panel 8061 when the terminal device 800 is moved to the ear. / Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of the terminal device (such as horizontal and vertical screen switching, related games) , Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; sensor 805 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, Infrared sensors, etc., will not be repeated here.
  • the display unit 806 is used to display information input by the user or information provided to the user.
  • the display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 807 can be used to receive inputted number or character information, and generate key signal input related to user settings and function control of the terminal device.
  • the user input unit 807 includes a touch panel 8071 and other input devices 8072.
  • the touch panel 8071 also called a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 8071 or near the touch panel 8071. operating).
  • the touch panel 8071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 810, the command sent by the processor 810 is received and executed.
  • the touch panel 8071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 807 may also include other input devices 8072.
  • other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 8071 can be overlaid on the display panel 8061.
  • the touch panel 8071 detects a touch operation on or near it, it transmits it to the processor 810 to determine the type of the touch event, and then the processor 810 determines the type of the touch event according to the touch.
  • the type of event provides corresponding visual output on the display panel 8061.
  • the touch panel 8071 and the display panel 8061 are used as two independent components to implement the input and output functions of the terminal device, in some embodiments, the touch panel 8071 and the display panel 8061 can be integrated
  • the implementation of the input and output functions of the terminal device is not specifically limited here.
  • the interface unit 808 is an interface for connecting an external device with the terminal device 800.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 808 can be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal device 800 or can be used to connect the terminal device 800 to an external device. Transfer data between devices.
  • the memory 809 can be used to store software programs and various data.
  • the memory 809 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc.
  • the memory 809 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 810 is the control center of the terminal device. It uses various interfaces and lines to connect the various parts of the entire terminal device, runs or executes the software programs and/or modules stored in the memory 809, and calls the data stored in the memory 809. , Perform various functions of the terminal equipment and process data, so as to monitor the terminal equipment as a whole.
  • the processor 810 may include one or more processing units; preferably, the processor 810 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface and application programs, etc., the modem
  • the processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 810.
  • the terminal device 800 may also include a power source 811 (such as a battery) for supplying power to various components.
  • a power source 811 such as a battery
  • the power source 811 may be logically connected to the processor 810 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. And other functions.
  • the terminal device 800 includes some functional modules not shown, which will not be repeated here.
  • the embodiment of the present invention also provides a terminal device, including a processor 810, a memory 809, and a computer program stored on the memory 809 and running on the processor 810.
  • a terminal device including a processor 810, a memory 809, and a computer program stored on the memory 809 and running on the processor 810.
  • the computer program is executed by the processor 810,
  • Each process of the foregoing wake-up signal processing method embodiment is realized, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.
  • the network side device 900 includes: a processor 901, a memory 902, a bus interface 903, and a transceiver 904, where the processor 901, the memory 902, and the transceiver 904 are all connected to the bus interface 903.
  • the network side device 900 further includes: a computer program stored in the memory 902 and capable of running on the processor 901, and when the computer program is executed by the processor 901, the following steps are implemented:
  • the WUS is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX in the at least two DRX groups.
  • the first indication is used to indicate whether to start the onDuration timer of the next DRX cycle of part or all of the at least two DRX groups when the WUS reception fails.
  • the first indication includes one sub-indication, and the one sub-indication corresponds to all DRX groups of the at least two DRX groups; or the first indication includes at least two sub-indications, and the at least two sub-indications The indications respectively correspond to different DRX groups of the at least two DRX groups.
  • the network side device 900 of the embodiment of the present invention configures the terminal device with WUS that is used to indicate whether to start the onDuration timer of the next DRX cycle of all DRX, Based on the WUS, the terminal device can determine whether to start the onDuration timer in the next DRX cycle of each DRX group.
  • the embodiment of the present invention provides a relatively simple WUS indication solution for the case where a terminal device is configured with multiple DRX groups.
  • the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, each process of the above wake-up signal processing method embodiment is realized, and the same The technical effect, in order to avoid repetition, will not be repeated here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
  • the embodiment of the present invention also provides another computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, each process of the above wake-up signal configuration method embodiment is realized, and the same can be achieved. In order to avoid repetition, I won’t repeat them here.
  • the computer-readable storage medium such as ROM, RAM, magnetic disk or optical disk, etc.
  • the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes a number of instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present invention.
  • a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

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

Abstract

本发明提供一种唤醒信号处理方法、唤醒信号配置方法及相关设备，其中唤醒信号处理方法包括：在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。

Description

唤醒信号处理方法、唤醒信号配置方法及相关设备
相关申请的交叉引用
本申请主张在2019年12月24日在中国提交的中国专利申请号No.201911349121.6的优先权，其全部内容通过引用包含于此。
技术领域
本发明涉及通信技术领域，尤其涉及一种唤醒信号处理方法、唤醒信号配置方法及相关设备。
背景技术
非连续接收(Discontinuous Reception，DRX)的目的是用于省电，处于DRX状态的终端设备不需要连续监听物理下行控制信道(Physical Downlink Control Channel，PDCCH)，网络侧设备可以通过预测终端设备的业务数据量，为终端设备配置对应的DRX参数，如DRX周期、偏移、持续监听定时器等。
现有通信系统中，为了进一步提高终端设备的省电性能，引入了基于PDCCH的唤醒信号(Wake Up Signal，WUS)，其中，WUS也可以称为省电无线网络临时标识加扰的带有循环冗余校验的下行控制信息(DCI with CRC scrambled by PS-RNTI，DCP)。WUS的作用是告知终端设备在DRX的持续监听期间(onDuration)，是否需要监听PDCCH，从而终端设备可根据该WUS指示，决定下一个DRX周期是否启动onDuration定时器，以及是否进行PDCCH监听。
目前WUS操作方式是基于终端设备只有一组DRX配置进行定义的。然而，在终端设备被配置了多个DRX组的情况下如何对多个DRX组进行唤醒或休眠指示，并没有相关的解决方案。
发明内容
本发明实施例提供一种唤醒信号处理方法、唤醒信号配置方法及相关设备，以实现在终端设备配置有多个DRX组的情况下提供一种较为简便的 WUS指示方案。
为了解决上述技术问题，本发明是这样实现的：
第一方面，本发明实施例提供了一种唤醒信号处理方法，应用于终端设备，该方法包括：
在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
第二方面，本发明实施例还提供了一种唤醒信号配置方法，应用于网络侧设备，该方法包括：
在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
第三方面，本发明实施例还提供一种终端设备，该终端设备包括：
接收模块，用于在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
第四方面，本发明实施例还提供一种网络侧设备。该网络侧设备包括：
配置模块，用于在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
第五方面，本发明实施例还提供一种终端设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述第一方面提供的唤醒信号处理方法的步骤。
第六方面，本发明实施例还提供一种网络侧设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机 程序被所述处理器执行时实现上述第二方面提供的唤醒信号配置方法的步骤。
第七方面，本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面提供的唤醒信号处理方法的步骤，或者实现上述第二方面提供的唤醒信号配置方法的步骤。
本发明实施例中，在终端设备配置有多个DRX组的情况下，通过接收用于指示是否启动全部DRX组的下一个DRX周期的onDuration定时器的WUS，从而终端设备可基于该WUS，决定在各DRX组的下一个DRX周期是否启动onDuration定时器。本发明实施例针对终端设备配置有多个DRX组的情况，提供了一种较为简便的WUS指示方案。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例可应用的一种网络系统的结构图；
图2是本发明实施例提供的唤醒信号处理方法的流程图；
图3是本发明实施例提供的WUS在DRX组中的配置示意图之一；
图4是本发明实施例提供的WUS在DRX组中的配置示意图之二；
图5是本发明实施例提供的唤醒信号配置方法的流程图；
图6是本发明实施例提供的终端设备的结构图；
图7是本发明实施例提供的网络侧设备的结构图；
图8是本发明又一实施例提供的终端设备的结构图；
图9是本发明又一实施例提供的网络侧设备的结构图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是 全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例，例如除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外，说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一，例如A和/或B和/或C，表示包含单独A，单独B，单独C，以及A和B都存在，B和C都存在，A和C都存在，以及A、B和C都存在的7种情况。
为便于理解本发明实施例，首先对本发明实施例中所涉及到的一些相关概念进行说明。
1、DRX技术
如果终端设备长时间不监听PDCCH控制信道，那么一旦有数据达到，将会增加数据传输的时延。为了兼顾省电和传输时延，根据终端设备监听信道的时间长短，终端设备可支持两种DRX周期：长DRX周期和短DRX周期。如果预测终端设备数据量达到比较频繁或者业务对时延比较敏感，网络侧设备可以配置终端设备使用DRX短周期；如果预测终端数据量比较稀疏且时延不敏感，网络侧设备可以配置终端设备仅使用长DRX周期。为了便于终端设备进行长DRX周期和短DRX周期的切换，要求长DRX周期是DRX短周期的整数倍，以保证两者的持续监听时间对齐。
为了支持DRX机制，网络侧设备会为终端设备配置DRX相关定时器和参数，具体包括：
drx-LongCycleStartOffset：用于配置长DRX周期的周期和偏移，周期和偏移的单位是毫秒；
drx-ShortCycle：用于配置短DRX周期的周期和偏移，周期和偏移的单 位是毫秒；
drx-ShortCycleTimer：用于控制终端设备使用短DRX周期的时长，单位为整数，表示终端设备一旦进入短DRX周期，要维持所述整数倍个短周期；
drx-onDurationTimer：DRX持续监听定时器，在该定时器运行期间，终端设备需要持续监听网络的PDCCH控制信道，该定时器单位是毫秒；
drx-SlotOffset：终端设备启动drx-onDurationTimer的时延，通过该参数设置DRX onDuration的起始时刻相对于子帧起点的偏移量，偏移量是1/32毫秒的整数倍。
2、唤醒信号WUS
WUS的作用是告知终端设备在特定的DRX的onDuration期间，是否需要监听PDCCH。当没有数据的情况，终端设备可以不需要监听onDuration期间的PDCCH，相当于终端设备在整个DRX Long cycle中都可以处于休眠状态，从而更进一步的省电。
WUS是一种下行物理控制信道(Downlink Control Information，DCI)，简称DCP(DCI with CRC scrambled by PS-RNTI)，其中省电无线网络临时标识PS-RNTI是网络为终端设备分配的专门用于省电特性的RNTI，以该RNTI加扰的DCI，即携带了网络对终端设备的唤醒/休眠指示。终端设备根据该指示，决定下一个DRX周期是否启动onDuration定时器，以及是否进行PDCCH监听。
参见图1，图1是本发明实施例可应用的一种网络系统的结构图，如图1所示，包括终端设备11和网络侧设备12，其中，终端设备11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(Personal Digital Assistant，PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等用户侧设备，需要说明的是，在本发明实施例中并不限定终端设备11的具体类型。网络侧设备12可以是基站，例如：宏站、LTE eNB、5G NR NB、gNB等；网络侧设备12也可以是小站，如低功率节点(Low Power Node，LPN)pico、femto等小站，或者网络侧设备12可以接入点(Access Point，AP)；基站也可以是中央单元(Central Unit，CU)与其管理是和控制的多个TRP共同组成的网络节点。需 要说明的是，在本发明实施例中并不限定网络侧设备12的具体类型。上述网络系统可以是5G通信系统或长期演进(Long Term Evolution，LTE)通信系统，具体可不作限定。
需要说明的是，本发明实施例提供的唤醒信号处理方法可以由上述终端设备11执行；本发明实施例提供的唤醒信号配置方法可以由上述网络侧设备12执行，详细内容请参见下述说明。
本发明实施例提供一种唤醒信号处理方法，应用于终端设备。参见图2，图2是本发明实施例提供的唤醒信号处理方法的流程图，如图2所示，包括以下步骤：
步骤201、在终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
本发明实施例中，所述终端设备可以被配置有多个DRX组，以及在其中一个DRX组中配置了WUS，通过一个WUS来控制所述至少两个DRX组共同工作，该WUS可以指示所述至少两个DRX组中的全部DRX的下一个DRX周期的onDuration定时器是否启动。
上述至少两个DRX组中不同的DRX组(即DRX group)可以理解为配置有不同DRX参数集合的不同载波组，其中，上述DRX参数集合可以包括一套DRX参数。实际应用中，可以将具有不同特性的成员载波(Component Carrier，CC)配置为不同的DRX组，并可以分别为各个DRX组配置对应的DRX参数集合。
具体地，可以是在终端设备(以下简称UE)根据其业务特性和自身特性，确定需要进行省电配置时，网络侧设备可以为UE配置DRX参数。当UE配置/激活了多个CC时，如果这些CC有不同的特性，例如，其中一些CC处于低频，另一些CC处于高频，因此在这两类CC中，他们的传输特性，如传输所用的参数集(即numerology)有很大差别，那么更高效率的一种方式，是为UE配置两组不同的DRX参数，分别用于不同特性的CC组。例如，将所有低频(例如FR1)的载波，配置为一个DRX group 1，并为DRX group 1 中的CC配置一套DRX参数，而将其它高频(例如FR2)的载波，配置为DRX group 2，并为DRX group 2中的CC配置另外一套DRX参数。这样相当于为UE配置了两套DRX参数，分别用于两个CC group。UE可以按照DRX参数配置，为这两个DRX group分配启动和维护对应的DRX状态。
其中，每套DRX参数可以包括DRX周期(长DRX周期、短DRX周期等)、偏移、UE使用DRX短周期的时长、DRX持续监听定时器、UE启动DRX持续监听定时器的时延等参数。
故本实施例中，在所述终端设备配置有至少两个DRX组的情况下，所述终端设备可以接收网络侧设备发送的WUS，并可依据所述WUS的指示，启动或不启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器，具体地，可在所述WUS指示启动全部DRX组的下一个DRX周期的onDuration定时器的情况下(如所述WUS为唤醒指示WUS on)，同时启动全部DRX组的下一个DRX周期的onDuration定时器，在所述WUS指示不启动全部DRX组的下一个DRX周期的onDuration定时器的情况下(如所述WUS为休眠指示WUS off)，不启动全部DRX组的下一个DRX周期的onDuration定时器。
需说明的是，当终端设备被配置了多组DRX配置，且同时配置了一个WUS时，一般来说WUS配置在主小区(Primary cell，Pcell)/特殊小区(Special cell，Spcell)上，将Pcell所在的DRX组称为Pcell DRX group或者Primary DRX group，其它DRX组称为辅小区(Secondary cell，Scell)DRX group或者Secondary DRX Group，WUS中可采用公共的比特位(即bit)指示多个DRX group的唤醒/休眠。
下面结合图3对本发明实施例具体实施方式进行举例说明，如图3所示，网络侧设备为UE配置了两个DRX group，并在DRX group1上配置了一个WUS，下面详细说明这两个DRX group如何在一个WUS的控制下，进行网络侧设备期望的唤醒和休眠操作。
图3是一个可选的两个DRX group配置的定时器的运行状态，其中，DRX group1和DRX group2可以有不同的定时器长度，例如，onDuration定时器，不活动(Inactivity)定时器，甚至混合自动重传请求(Hybrid Automatic Repeat  reQuest，HARQ)往返时延(Round Trip Time，RTT)定时器，HARQ重传(Retransmission，RETX)定时器等，短DRX周期(short DRX cycle)是否启动及其时长配置，和DRX周期偏移(DRX cycle offset)等参数都可以有不同的取值。最终的效果是这两个DRX group分别根据属于自己的定时器和参数配置，按照数据调度和重传情况，进行各自独立的DRX状态和定时器维护。
在多个DRX group配置的基础上，如果需要进一步的配置一个WUS来动态指示每个DRX周期是否唤醒/休眠onDuration定时器和PDCCH监听，一种可行的方式是，在所有配置/激活的CC中挑选一个CC来配置WUS，一般来说是Pcell或者Spcell，也就是说WUS是配置在一个DRX group内。例如图3中，如果Pcell/Spcell是属于DRX group 1，则WUS在DRX group 1中的特殊小区上进行监听。
其中，通过一个WUS来控制两个DRX group共同工作的基本方式如下：
UE在WUS配置好的时频资源上，去监听(接收)WUS，并根据WUS指示的内容，来决定DRX group1在紧接着的下一个DRX周期(如图2中DRX group1上位于WUS on/WUS off的时域位置后且相邻的DRX周期)内，其onDuration定时器是否启动，是否监听PDCCH。虽然此时有两个DRX group，但需要两个group同时听从一个WUS的控制，因此DRX group2上虽然没有WUS配置，但位于DRX group1的WUS的指示，同时也适用于决定DRX group2的定时器状态和PDCCH监听状态。这样达到的效果是，当UE没有业务需要传输时，一个WUS可以同时指示所有DRX group里的小区，在下一个DRX周期中都处于休眠状态，进一步节省UE电量；只有当有业务需要传输时，WUS才指示两个DRX group里的小区，在下一个DRX cycle启动onDuration定时器和PDCCH监听，准备进行数据传输。
可选的，在接收所述唤醒信号WUS之后，所述方法还包括：
根据所述WUS确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器。
在接收所述WUS后，UE还可以根据所述WUS的指示，确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器，具体地，可以在所述WUS为唤醒指示(如接收的WUS指示值为on) 的情况下，确定启动全部DRX组的下一个DRX周期的onDuration定时器，在所述WUS指示为休眠指示(如接收的WUS指示值为off)的情况下，确定不启动全部DRX组的下一个DRX周期的onDuration定时器。进而，UE可依据确定结果，启动全部DRX组的下一个DRX周期的onDuration定时器，或不启动全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述接收唤醒信号WUS之前，所述方法还包括：
根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS。
在利用WUS控制多个DRX组的唤醒/休眠状态的过程中，还存在特殊情况需要作进一步考虑和解决，例如，当UE的某些DRX组中正在进行数据业务时，这些DRX组已处于唤醒工作状态，此时可以考虑是否需要监听WUS，即接收WUS。
故该实施方式中，在接收WUS之前，可以先根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS，若确定接收，则接收所述WUS，否则可以不接收所述WUS，也即放弃接收所述WUS。
具体地，可以根据所述至少两个DRX组中的部分或者全部DRX组当前时刻是否处于激活状态(即唤醒状态)，或是否处于非激活状态(即休眠状态)，来确定是否接收所述WUS，更为具体地，可以在所述至少两个DRX组中的部分或者全部DRX组当前时刻处于激活状态的情况下，确定不接收所述WUS，在所述至少两个DRX组中的部分或者全部DRX组当前时刻处于非激活状态的情况下，确定接收所述WUS。
更进一步地，在确定不接收所述WUS的情况下，考虑到当前部分或者全部DRX组处于激活状态，故判断UE的所述部分或者全部DRX组在下一个DRX周期进行业务的可能性较大，因此，为保证UE业务的正常进行和降低传输时延，可以在不监听WUS的情况下，直接启动全部DRX组的下一个DRX周期的onDuration定时器。
这样，通过根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS，可以在不影响终端业务的情况下，进一步地节省传输资源，也更加省电。
可选的，所述根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS，可以包括如下任一项：
在所述WUS的时域位置位于第一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；其中，所述第一DRX组为所述至少两个DRX组中配置有所述WUS的DRX组；
在所述WUS的时域位置位于所述至少两个DRX组中全部DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；
在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS。
该实施方式中，可以根据所述WUS的时域位置与所述至少两个DRX组中的部分或全部DRX组的激活时间(Activetime)的重叠情况，确定是接收所述WUS，还是确定放弃接收所述WUS。
当配置的WUS所在的时域位置与Activetime重叠时，即应该监听WUS的时间位置处，UE由于前一个DRX周期的调度情况，仍旧处于监听的激活状态，即持续监听PDCCH状态，此时就不需要进行WUS的监听，直接进入持续激活状态，即在下一个DRX周期启动onDuration定时器和监听PDCCH。
一种方式中，可以仅考虑主要DRX组(Primary DRX group)是否处于Activetime，来判断所述WUS是否位于Activetime期间，也即所述WUS的时域位置是否与Activetime冲突，进而根据是否冲突决定是否监听WUS，其中，所述Primary DRX group可以是所述至少两个DRX组中配置有所述WUS的DRX组。
具体地，当所述WUS配置在所述至少两个DRX组中的第一DRX组时，可以在所述WUS的时域位置位于所述第一DRX组的激活时间的情况下，也即所述WUS的时域位置与所述第一DRX组的激活时间重叠时，判断所述WUS的时域位置与所述第一DRX组的激活时间冲突，从而确定放弃接收所述WUS；而在所述WUS的时域位置不位于所述第一DRX组的激活时间，或者说所述WUS的时域位置位于所述第一DRX组的非激活时间(Non-Activetime)的情况下，也即所述WUS的时域位置与所述第一DRX组的激活时间不重叠时，可以判断所述WUS的时域位置与所述第一DRX组 的激活时间不冲突，从而确定接收所述WUS。
另一种方式中，可以同时考虑所述至少两个DRX组中每个DRX组的Activetime，来判断所述WUS的时域位置是否与Activetime冲突，进而根据是否冲突决定是否监听WUS，具体还可以分为两种不同情况：
一种情况中，可以是在所述WUS的时域位置位于所述至少两个DRX组中每个DRX组的激活时间重叠区域的情况下，也即所述WUS的时域位置与每个DRX组的激活时间都重叠，判断所述WUS的时域位置与每个DRX组的激活时间冲突，从而确定放弃接收所述WUS；而在所述WUS的时域位置不位于每个DRX组的激活时间的情况下，也即存在至少一个DRX组激活时间与所述WUS的时域位置不重叠时，可以判断所述WUS的时域位置与所述至少两个DRX组的激活时间不冲突，从而确定接收所述WUS。
另一种情况中，可以是在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，也即存在至少一个DRX组的激活时间与所述WUS的时域位置重叠，判断所述WUS的时域位置与所述至少两个DRX组的激活时间冲突，从而确定放弃接收所述WUS；而在所述WUS的时域位置不位于任一DRX组的激活时间的情况下，也即所述WUS的时域位置位于每个DRX组的非激活时间，而不存在DRX组与所述WUS的时域位置重叠时，可以判断所述WUS的时域位置与所述至少两个DRX组的激活时间不冲突，从而确定接收所述WUS。
进一步的，在确定放弃接收所述WUS的情况下，所述方法还可以包括如下一项：
启动所述至少两个DRX组中每个DRX组的下一个DRX周期的onDuration定时器；
在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组的第二DRX组的下一个DRX周期的onDuration定时器，其中，所述第二DRX组为所述至少两个DRX组中配置有所述WUS的DRX组，或者所述第二DRX组为所述至少两个DRX组中激活时间与所述WUS的时域位置存在重叠的DRX组。
对于上述确定放弃接收WUS的情况，均是由于所述WUS的时域位置位 于部分或全部DRX组的激活时间导致的冲突，而无需监听WUS，也就是说当前存在部分或全部DRX组正在进行业务传输，进而可推断UE在下一个DRX周期进行业务的可能性较大，故为保证UE业务的正常进行和降低传输时延，可以在不监听WUS的情况下，直接启动所述至少两个DRX组中部分或全部的DRX组的下一个DRX周期的onDuration定时器。
在一实施方式中，在确定放弃接收所述WUS的情况下，可以直接启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器，不仅实现较为简单，还可以降低传输时延。
在另一实施方式中，在确定放弃接收所述WUS的情况下，可以仅启动所述至少两个DRX组中某一个DRX组的下一个DRX周期的onDuration定时器，例如，可以仅启动至少两个DRX组中配置有所述WUS的DRX组的下一个DRX周期的onDuration定时器，或者可以仅启动至少两个DRX组中激活时间与WUS的时域位置冲突的DRX组的下一个DRX周期的onDuration定时器，可以在兼顾省电的同时降低传输时延。
下面以UE配置有两个DRX group(Primary DRX group和Secondary DRX group)为例对本实施方式进行说明，由于两个DRX group的激活状态是各自独立的，因此两个DRX group与WUS配置的时域位置的关系有如下四种情况：
Case1：WUS配置的时域位置上，Primary DRX group(即WUS所在的group)的状态为Activetime，Secondary DRX group(即没有WUS的group)的状态为Non-Activetime；
Case2：WUS配置的时域位置上，Primary DRX group的状态为Activetime，Secondary DRX group的状态也是Activetime；
Case3：WUS配置的时域位置上，Primary DRX group的状态为Non-Activetime，Secondary DRX group的状态是Activetime；
Case4：WUS配置的时域位置上，Primary DRX group的状态为Non-Activetime，Secondary DRX group的状态也是Non-Activetime；
其中，Primary DRX group和Secondary DRX group这两个DRX group的状态可以对应有下表所示四种情况。
表1两个DRX group的状态情况
  Primary DRX group Secondary DRX group
Case1 Activetime Non-Activetime
Case2 Activetime Activetime
Case3 Non-Activetime Activetime
Case4 Non-Activetime Non-Activetime
那么有如下两种方式来定义WUS所在的时域位置与Active time的冲突以及根据是否冲突决定相关的监听WUS行为：
方式一：仅仅考虑Primary DRX group是否处于Active time，来判断WUS是否位于Active time期间：
上述case1和case2判断为冲突，UE不需要在WUS配置的时频位置进行WUS监听，并默认下一个DRX周期中两个DRX group同时启动onDuration定时器，同时监听PDCCH；
上述case3和case4判断为不冲突，UE需要在WUS配置的时频位置进行WUS监听，并根据WUS的指示，例如on或off，来决定下一个DRX周期中两个DRX group是否同时启动onDuration定时器，是否同时监听PDCCH。
需要注意的是，由于在这种方式中，仅仅考虑了Primary DRX group的状态，当Secondary DRX group状态与之不一致时，例如case 3，在WUS指示了off的情况下，虽然当前Secondary DRX group仍旧处于Activetime，但当前使UE进入Activetime的定时器超时之后，由于下一个DRX周期中onDuration定时器不再启动，UE在Secondary DRX group也将进入休眠状态。
方式二：同时考虑Primary DRX group和Secondary DRX group的Active time，该方式又分为两个子分支：
分支一：只有WUS所在时域位置两个DRX group都处于Activetime(即case2)时，才判定WUS与Activetime冲突，其余情况(case1，case3和case4)都判断为不冲突；
分支二：只有当WUS所在的时域位置两个DRXgroup都处于Non-Activetime时(即case4)，才判定WUS与Activetime不冲突，其余情况(case1，case2和case3)都判断为冲突。
当判断为WUS与Activetime冲突时，UE不需要在WUS配置的时频位置进行WUS监听，并默认下一个DRX周期中两个DRX group同时启动onDuration定时器，同时监听PDCCH；
当判断为WUS与Activetime不冲突时，UE需要在WUS配置的时频位置进行WUS监听，并根据WUS的指示，例如on或off，来决定下一个DRX周期中两个DRXgroup是否同时启动onDuration定时器，是否同时监听PDCCH。
这样，通过基于所述WUS的时域位置与所述至少两个DRX组中的部分或全部DRX组的激活时间的关系，判断所述WUS是否与所述至少两个DRX组冲突，进而确定是否接收所述WUS，可以有效地节省传输资源，节省电量。
可选的，所述方法还包括如下任一项：
在所述WUS接收失败的情况下，根据第一指示确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；其中，所述第一指示为协议预定义或网络侧设备配置；
在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；
在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器。
在网络侧设备为UE配置好WUS的时频位置后，UE需要在WUS配置的时频位置上进行WUS检测即接收WUS，但在实际传输中，可能会出现通信链路质量差，或者UE需要进行其它高优先级的操作，而导致UE并没有正确检测到WUS即接收WUS失败，因此也就无法得知网络侧设备通知的下一个DRX周期到底是唤醒指示还是休眠指示，此种情况下，UE在所述至少两个DRX组的行为需要规定清楚，以保证UE的行为在网络侧设备可控的范围之内。
本实施方式就是针对WUS接收失败的情况，提出的UE的所述至少两个DRX组在下一个DRX周期如何进行监听行为的相应处理方案，具体可以有以下三种不同的处理方案。
第一种方式中，可以预先配置相应的指示，来告知UE如何决定其监听行为，具体地，可以由协议预定义或网络侧设备配置第一指示，用于指示UE在所述WUS接收失败的情况下，是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。当由网络侧设备为UE配置所述第一指示时，所述网络侧设备可以将配置好的所述第一指示下发至UE，使得UE可在接收WUS失败的情况下，从所述第一指示中确定需要启动所述至少两个DRX组中的哪些DRX组的下一个DRX周期的onDuration定时器。
也就是说，所述第一指示可以指示UE仅启动所述至少两个DRX组的部分DRX组的下一个DRX周期的onDuration定时器，如仅启动较为主要DRX组、配置有所述WUS的DRX组或当前有数据调度的DRX组的下一个DRX周期的onDuration定时器，以保障终端业务和节省传输资源；或者，也可以指示UE启动所述至少两个DRX组的全部DRX组的下一个DRX周期的onDuration定时器，以优先保障所述终端的业务传输；或者，还可以指示UE不启动所述至少两个DRX组的部分DRX组的下一个DRX周期的onDuration定时器，如不启动非主要DRX组、未配置有所述WUS的DRX组或当前没有数据调度的DRX组的下一个DRX周期的onDuration定时器，以节省传输资源和电量；还或者，可以指示UE的所述至少两个DRX组的全部DRX组的下一个DRX周期的onDuration定时器均不启动，以优先节省传输资源和电量。
其中，所述第一指示可以包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
也就是说，可以为所述至少两个DRX组配置共同的指示，以指示UE同时启动或同时不启动全部DRX组的下一个DRX周期的onDuration定时器；也可以为所述至少两个DRX组中每个DRX组分别配置独立的指示，或者分别为所述至少两个DRX组中的某部分DRX组配置一个共同的指示，还或者为所述至少两个DRX组中的某部分DRX组配置一个共同的指示，为所述至少两个DRX组中另一部分DRX组中的每个DRX组分别配置独立的指示， 等等，以指示UE同时启动或同时不启动部分DRX组的下一个DRX周期的onDuration定时器，或指示UE分别启动或不启动某DRX组的下一个DRX周期的onDuration定时器。
例如，网络侧设备可以通过无线资源控制(Radio Resource Control，RRC)信令配置UE在漏检/误检WUS时，所述至少两个DRX组处于被唤醒还是休眠状态，其中，网络侧设备可以为Primary DRX group和Secondary DRX group配置共同的WUS漏检状态指示(WUS misdetection state indicator)，也可以为他们配置独立的WUS misdetection state indicator。
举例说明，当共同的WUS misdetection state indicator被配置为on时，如果UE发生了WUS misdetection，则UE默认下一个DRX周期中两个DRX group同时启动onDuration定时器，同时监听PDCCH；当共同的WUS misdetection state indicator被配置为off时，如果UE发生了WUS misdetection，则UE默认下一个DRX周期中两个DRX group同时不启动onDuration定时器，同时不监听PDCCH；
当独立的WUS misdetection state indicator被分别配置时，如果UE发生了WUS misdetection，则UE按照配置给各自DRX group的指示独立决定下一个DRX周期中是否启动onDuration定时器，是否监听PDCCH。
第二种方式中，可以由UE按照预设规则自行决定其监听行为，具体地，UE在所述WUS接收失败的情况下，可以启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
也就是说，UE可以仅启动所述至少两个DRX组的部分DRX组的下一个DRX周期的onDuration定时器，如仅启动主要DRX组、配置有所述WUS的DRX组或当前有数据调度的DRX组的下一个DRX周期的onDuration定时器，以保障其业务和节省传输资源；或者，也可以启动所述至少两个DRX组的全部DRX组的下一个DRX周期的onDuration定时器，以优先保障其业务传输。
进一步的，所述在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或者全部DRX组的下一个DRX周期的onDuration定时器，包括如下任一项：
在所述WUS接收失败的情况下，启动所述至少两个DRX组的每个DRX组的下一个DRX周期的onDuration定时器；
在所述WUS接收失败的情况下，启动第三DRX组的下一个DRX周期的onDuration定时器；其中，所述第三DRX组为所述至少两个DRX组中配置有所述WUS的DRX组。
该方式中，由于WUS misdetection发生的概率不高，一种简单直接的UE行为是UE默认进行唤醒行为，即如果UE发生了WUS misdetection，则下一个DRX cycle内，UE默认全部DRX组启动onDuration定时器，同时监听PDCCH，这样可以避免错过网络侧设备的调度，提高了业务传输体验和时延，并且由于WUS misdetection的概率不高，对耗电的影响不大。
或者，为在业务传输体验、时延与耗电之间取得均衡，可以仅默认唤醒所述至少两个DRX组中配置有所述WUS的DRX组，当所述WUS配置在Primary DRX group时，可以仅唤醒Primary DRX group，例如，当UE在所述至少两个DRX组的前一个DRX周期都没有数据传输时，发生了WUS misdetection，此时UE仅唤醒Primary DRX group，以监听可能的数据调度，而在其他DRX组仍旧保持休眠省电状态。
第三种方式中，可以由UE根据所述至少两个DRX组中至少一个DRX组的状态决定其监听行为，具体地，UE在所述WUS接收失败的情况下，可以根据所述至少两个DRX组中至少一个DRX组当前为激活还是非激活状态，来确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；其中，所述至少一个DRX组可以是所述至少两个DRX组中的主要DRX组、配置有所述WUS的DRX组或当前有数据调度的DRX组，所述至少两个DRX组的部分DRX组可以是与所述至少一个DRX组对应的DRX组，也可以是所述至少两个DRX组中的主要DRX组、配置有所述WUS的DRX组或当前有数据调度的DRX组。
也就是说，可以根据所述至少两个DRX组中至少一个DRX组的状态，确定是否启动所述至少两个DRX组中部分DRX组的下一个DRX周期的onDuration定时器，例如，在所述至少两个DRX组中某部分DRX组在WUS的时域位置处于Activetime时，可以判断该部分DRX组在下一个DRX周期 有数据调度的可能性非常大，故可以启动该部分DRX组的下一个DRX周期的onDuration定时器；或者，也可以根据所述至少两个DRX组中至少一个DRX组的状态，确定是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器，例如，在所述至少两个DRX组中某部分或全部DRX组在WUS的时域位置处于Activetime时，均可以直接启动全部DRX组的下一个DRX周期的onDuration定时器。
进一步的，所述在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器，包括：
在所述WUS接收失败的情况下，若所述WUS的时域位置位于第四DRX组的激活时间，则启动所述第四DRX组的下一个DRX周期的onDuration定时器；
其中，所述第四DRX组为所述至少两个DRX组中的任一DRX组。
也就是说，在UE接收所述WUS失败的情况下，可以启动所述至少两个DRX组中激活时间与所述WUS的时域位置重叠的DRX组的下一个DRX周期的onDuration定时器，而不启动其他DRX组的下一个DRX周期的onDuration定时器。
以两个DRX group为例，可以分别根据这两个DRX group的状态，决定是否唤醒其DRX group，例如当一个DRX group在WUS时域期间处于Activetime，则认为下一个DRX周期有数据调度的可能性非常大，则该DRX group在下一个DRX周期内，UE默认启动onDuration定时器，监听PDCCH；而对于一个DRX group在WUS时域期间处于Non-Activetime，则认为下一个DRX周期休眠的可能性非常大，则该DRX group在下一个DRX周期内，UE默认不启动onDuration定时器，不监听PDCCH。
这样，在接收所述WUS失败的情况下，通过采用上述任一方案来决定所述至少两个DRX组在下一个DRX周期的监听行为，可保证UE的行为在网络侧设备可控的范围之内，且能保障终端业务的正常进行或节省终端传输资源。
可选的，第五DRX组配置有长DRX周期的参数和短DRX周期的参数， 所述长DRX周期为所述短DRX周期的整数倍，所述第五DRX组为所述至少两个DRX组中的任一DRX组；
所述方法还包括如下一项：
在所述第五DRX组工作于所述短DRX周期的情况下，若仅所述长DRX周期的onDuration之前的WUS时间窗口配置有所述WUS的时域位置，则根据所述长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内全部短DRX周期的onDuration定时器；
在所述第五DRX组工作于所述短DRX周期的情况下，若每个短DRX周期的onDuration之前的WUS时间窗口均配置有所述WUS的时域位置，则分别根据所述每个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述每个短DRX周期的onDuration定时器。
为兼顾省电和传输时延，一个DRX组可以同时配置有长DRX周期和短DRX周期，当UE数据量比较频繁或者业务对时延比较敏感时，可以使用短DRX周期，当UE数据量比较稀疏且业务对时延不敏感时，可以仅使用长DRX周期。为了便于在长DRX周期和短DRX周期之间切换，可以配置长DRX周期为短DRX周期的整数倍，这样可以保证持续监听时间对齐。
该实施方式中，在所述至少两个DRX组中第五DRX组配置有长DRX周期的参数和短DRX周期的参数，且所述第五DRX组工作于所述短DRX周期的情况下，可以根据所述WUS配置的时域位置与所述第五DRX组的长DRX周期或短DRX周期的时域位置关系，确定是否启动对应DRX周期的onDuration定时器；其中，所述第五DRX组为所述至少两个DRX组中的任一DRX组，所述长DRX周期为所述短DRX周期的整数倍。可选的，为了提高WUS监听的简便性，所述第五DRX组可以为所述至少两个DRX组中配置有所述WUS的DRX组。
在一实施方式中，为了节省传输资源，网络侧设备可能仅在所述第五DRX组的每个长DRX周期内配置一个WUS时间窗口，以通过一个WUS指示UE统一启动或不启动该长DRX周期内的所有onDuration定时器，这样，WUS只出现在每个长DRX周期的onDuration之前的WUS时间窗口，在这种情况下，UE可以在每个长DRX周期的onDuration之前的WUS时间窗口 监听WUS，并可根据监听到的WUS即接收的WUS，确定是否启动该长DRX周期范围内的全部短DRX周期的onDuration定时器。
例如，若在某长DRX周期的onDuration之前的WUS时间窗口接收的WUS指示唤醒，则可以启动位于该长DRX周期范围内的全部短DRX周期的onDuration定时器，若在某长DRX周期的onDuration之前的WUS时间窗口接收的WUS指示休眠，则可以不启动该长DRX周期范围内的全部短DRX周期的onDuration定时器。其中，若一个长DRX周期包括N个短DRX周期，则可以根据长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内的N个短DRX周期对应的N个onDuration定时器。
在另一实施方式中，为了更好地指示UE的行为，避免一些不必要的唤醒或在存在数据调度的期间指示休眠，网络侧设备可以分别在所述第五DRX组的每个短DRX周期内配置一个WUS时间窗口，以通过独立的WUS指示UE启动或不启动该短DRX周期内的onDuration定时器，这样，WUS会出现在每个短DRX周期的onDuration之前的WUS时间窗口，在这种情况下，UE可以在每个短DRX周期的onDuration之前的WUS时间窗口监听WUS，并可根据监听到的WUS即接收的WUS，确定是否启动每个短DRX周期的onDuration定时器。
例如，若在某短DRX周期的onDuration之前的WUS时间窗口接收的WUS指示唤醒，则可以启动该短DRX周期的onDuration定时器，若在某短DRX周期的onDuration之前的WUS时间窗口接收的WUS指示休眠，则可以不启动该短DRX周期的onDuration定时器。其中，若一个长DRX周期包括N个短DRX周期，则可以分别根据这N个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动对应短DRX周期的onDuration定时器。
需说明的是，前述实施方式中介绍的在各种不同情况下是否接收WUS以及接收WUS失败的情况下UE的处理行为的具体实施方案，均可以应用于本实施方式中。
其中，短DRX周期的配置，是为了在数据突发期间能够更快的进行被唤 醒和休眠之间的切换，从而在数据接续到达的阶段，能够快速的对数据进行调度。长DRX周期(即long DRX cycle)与短DRX周期(即Short DRX cycle)成整倍数关系，并且具有相同的偏移量，这样做的好处是便于在long DRX cycle和short DRX cycle之间进行切换。
例如，如图4所示，long DRX cycle为short DRX cycle的5倍，在一段期间的数据传输结束之后，如Inactivity timer超时后，UE进入short DRX cycle，其中，图中较短的突起所示位置为每个short DRX cycle中的onDuration定时器期间，short DRX cycle和long DRX cycle中的onDuration定时器长度相同，short DRX cycle配置参数中可以规定short DRX cycle的持续参数，如在进行了N个short DRX cycle之后，仍旧没有数据传输，则重新回到long DRX cycle，相应地，如果前一个long DRX cycle中没有数据调度，则UE一直处于long DRX cycle期间。而如图4所示的short DRX cycle之后，仍旧没有数据调度，UE重新进入long DRX cycle。
由于short DRX cycle是与业务相关的，只有业务需求需要短时延要求时，才配置short DRX cycle，而DRX group配置与载波相关，载波也可以与业务传输有配置绑定关系，例如，只有在Secondary DRX group上传输的业务有配置short DRX cycle的需要，此时可以针对不同的DRX group配置不同的短DRX周期参数，例如，short DRX cycle是否启动，持续短周期数目等。
当在两个DRX group里配置了相同的短DRX周期参数，或者不同的短DRX周期参数时，由于两个DRX group的数据调度情况不一致，因此短DRX周期可以按照是否启动，以及具体的参数进行分别维护。
当短DRX周期在两个DRX group独立维护时，WUS的执行可以有以下不同的方式：
方式1：当WUS只出现在long DRX cycle的onDuration之前的WUS时间窗口(WUS window)内时，即一个long DRX cyle内只有一个WUS时间窗口位置，此时WUS指示或者前述实施例介绍的各种被唤醒/休眠行为，可同时应用于该long DRX cycle中的所有可能的onDuration定时器，如图4所示，在第一个long DRX cycle之前的WUS指示on，则该long DRX cycle内的onDuration定时器(隐含在第一个较长的突起内)和4个short DRX cycle 的onDuration定时器都会启动，并监听PDCCH；而在第二个long DRX cycle的onDuration之前的WUS指示off，则第二个long DRX cycle中的全部onDuration定时器都不启动，且不监听PDCCH。
方式2：如果进入short DRX cycle之后，在每个short DRX cycle的onDuration之前也有对应的WUS配置，则每个short DRX cycle的onDuration定时器是否启动由对应的WUS指示决定。特别地，若WUS只配置在Primary DRX group内，则简单来说，Primary DRX group进入short DRX cycle后在每个short DRX cycle的onDuration之前监听WUS。
这样，在所述至少两个DRX组中的某DRX组配置有长DRX周期和短DRX周期，且该DRX组工作在短DRX周期的情况下，可以根据在各DRX周期中配置的WUS时间窗口接收WUS，并根据接收的WUS确定是否启动对应DRX周期中的onDuration定时器，从而实现有效地指示该DRX组如何进行唤醒或休眠行为。
本实施例中的唤醒信号处理方法，在终端设备配置有多个DRX组的情况下，通过接收用于指示是否启动全部DRX组的下一个DRX周期的onDuration定时器的WUS，从而终端设备可基于该WUS，决定在各DRX组的下一个DRX周期是否启动onDuration定时器。本发明实施例针对终端设备配置有多个DRX组的情况，提供了一种较为简便的WUS指示方案。
本发明实施例提供一种唤醒信号配置方法，应用于网络侧设备。参见图5，图5是本发明实施例提供的唤醒信号配置方法的流程图，如图5所示，包括以下步骤：
步骤501、在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
本实施例中，在网络侧设备为终端设备配置多个DRX组的情况下，可以为终端设备配置一个WUS，通过一个WUS来控制所述至少两个DRX组共同工作，也即通过该WUS可以指示所述至少两个DRX组中的全部DRX的下一个DRX周期的onDuration定时器均启动或均休眠。
需要说明的是，本实施例作为与图2所示的实施例中对应的网络侧设备的实施方式，其具体的实施方式可以参见图2所示的实施例中的相关说明，为避免重复说明，本实施例不再赘述。
本实施例中的唤醒信号配置方法，在为终端设备配置了至少两个DRX组的情况下，通过为所述终端设备配置用于指示是否启动全部DRX的下一个DRX周期的onDuration定时器的WUS，可使终端设备基于该WUS，确定在各DRX组的下一个DRX周期是否启动onDuration定时器，提供了一种较为简便的WUS指示方案。
可选的，所述方法还可以包括：
向所述终端设备发送第一指示；
其中，所述第一指示用于在所述WUS接收失败的情况下，指示是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
上述可选的实施方式可以参见图2所示的实施例中的相关说明，为避免重复说明，本实施例不再赘述。
参见图6，图6是本发明实施例提供的终端设备的结构图。如图6所示，终端设备600包括：
接收模块601，用于在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
可选的，终端设备600还包括：
第一确定模块，用于根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS。
可选的，所述第一确定模块具体用于如下一项：
在所述WUS的时域位置位于第一DRX组的激活时间的情况下，确定放 弃接收所述WUS，否则确定接收所述WUS；其中，所述第一DRX组为所述至少两个DRX组中配置有所述WUS的DRX组；
在所述WUS的时域位置位于所述至少两个DRX组中全部DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；
在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS。
可选的，终端设备600还包括第一启动模块，具体用于如下一项：
用于在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组中每个DRX组的下一个DRX周期的onDuration定时器；
在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组的第二DRX组的下一个DRX周期的onDuration定时器，其中，所述第二DRX组为所述至少两个DRX组中配置有所述WUS的DRX组，或者所述第二DRX组为所述至少两个DRX组中激活时间与所述WUS的时域位置存在重叠的DRX组。
可选的，终端设备600还包括：
第二确定模块，用于根据所述WUS确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器。
可选的，终端设备600还包括如下一项：
第三确定模块，用于在所述WUS接收失败的情况下，根据第一指示确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；其中，所述第一指示为协议预定义或网络侧设备配置；
第二启动模块，用于在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或者全部DRX组的下一个DRX周期的onDuration定时器；
第四确定模块，用于在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
可选的，所述第二启动模块具体用于如下一项：
在所述WUS接收失败的情况下，启动所述至少两个DRX组的每个DRX组的下一个DRX周期的onDuration定时器；
在所述WUS接收失败的情况下，启动第三DRX组的下一个DRX周期的onDuration定时器；其中，所述第三DRX组为所述至少两个DRX组中配置有所述WUS的DRX组。
可选的，所述第四确定模块具体用于在所述WUS接收失败的情况下，若所述WUS的时域位置位于第四DRX组的激活时间，则启动所述第四DRX组的下一个DRX周期的onDuration定时器；
其中，所述第四DRX组为所述至少两个DRX组中的任一DRX组。
可选的，第五DRX组配置有长DRX周期的参数和短DRX周期的参数，所述长DRX周期为所述短DRX周期的整数倍，所述第五DRX组为所述至少两个DRX组中的任一DRX组；
终端设备600还包括第五确定模块，具体用于如下一项：
在所述第五DRX组工作于所述短DRX周期的情况下，若仅所述长DRX周期的onDuration之前的WUS时间窗口配置有所述WUS的时域位置，则根据所述长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内的全部短DRX周期的onDuration定时器；
在所述第五DRX组工作于所述短DRX周期的情况下，若所述每个短DRX周期的onDuration之前的WUS时间窗口均配置有所述WUS的时域位置，则分别根据所述每个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述每个短DRX周期的onDuration定时器。
本发明实施例提供的终端设备600能够实现上述唤醒信号处理方法实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
本发明实施例的终端设备600在配置有多个DRX组的情况下，通过接收用于指示是否启动全部DRX组的下一个DRX周期的onDuration定时器的WUS，从而终端设备可基于该WUS，决定在各DRX组的下一个DRX周期是否启动onDuration定时器，为在终端设备配置有多个DRX组的情况下提供了一种较为简便的WUS指示方案。
参见图7，图7是本发明实施例提供的网络侧设备的结构图。如图7所示，网络侧设备700包括：
配置模块701，用于在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
可选的，网络侧设备700还包括：
发送模块，用于向所述终端设备发送第一指示；
其中，所述第一指示用于在所述WUS接收失败的情况下，指示是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
本发明实施例提供的网络侧设备700能够实现上述唤醒信号配置方法实施例中网络侧设备实现的各个过程，为避免重复，这里不再赘述。
本发明实施例的网络侧设备700在为终端设备配置了至少两个DRX组的情况下，通过为所述终端设备配置用于指示是否启动全部DRX的下一个DRX周期的onDuration定时器的WUS，可使终端设备基于该WUS，确定在各DRX组的下一个DRX周期是否启动onDuration定时器，为在终端设备配置有多个DRX组的情况下提供了一种较为简便的WUS指示方案。
图8是本发明实施例提供的又一种终端设备的结构图。参见图8，该终端设备800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809、处理器810、以及电源811等部件。本领域技术人员可以理解，图8中示出的终端设备结构并不构成对终端设备的限定，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本发明实施例中，终端设备包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，射频单元801，用于在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述处理器810用于：
根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS。
可选的，所述处理器810还用于如下一项：
在所述WUS的时域位置位于第一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；其中，所述第一DRX组为所述至少两个DRX组中配置有所述WUS的DRX组；
在所述WUS的时域位置位于所述至少两个DRX组中全部DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；
在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS。
可选的，所述处理器810还用于如下一项：
在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组中每个DRX组的下一个DRX周期的onDuration定时器；
在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组的第二DRX组的下一个DRX周期的onDuration定时器，其中，所述第二DRX组为所述至少两个DRX组中配置有所述WUS的DRX组，或者所述第二DRX组为所述至少两个DRX组中激活时间与所述WUS的时域位置存在重叠的DRX组。
可选的，所述处理器810还用于：
根据所述WUS确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述处理器810还用于如下一项：
在所述WUS接收失败的情况下，根据第一指示确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器； 其中，所述第一指示为协议预定义或网络侧设备配置；
在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或者全部DRX组的下一个DRX周期的onDuration定时器；
在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述处理器810还用于如下一项：
所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
可选的，所述处理器810还用于如下一项：
在所述WUS接收失败的情况下，启动所述至少两个DRX组的每个DRX组的下一个DRX周期的onDuration定时器；
在所述WUS接收失败的情况下，启动第三DRX组的下一个DRX周期的onDuration定时器；其中，所述第三DRX组为所述至少两个DRX组中配置有所述WUS的DRX组。
可选的，所述处理器810还用于：
在所述WUS接收失败的情况下，若所述WUS的时域位置位于第四DRX组的激活时间，则启动所述第四DRX组的下一个DRX周期的onDuration定时器；
其中，所述第四DRX组为所述至少两个DRX组中的任一DRX组。
可选的，第五DRX组配置有长DRX周期的参数和短DRX周期的参数，所述长DRX周期为所述短DRX周期的整数倍，所述第五DRX组为所述至少两个DRX组中的任一DRX组；
所述处理器810还用于如下一项：
在所述第五DRX组工作于所述短DRX周期的情况下，若仅所述长DRX周期的onDuration之前的WUS时间窗口配置有所述WUS的时域位置，则根据所述长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内的全部短DRX周期的onDuration定时器；
在所述第五DRX组工作于所述短DRX周期的情况下，若所述每个短DRX周期的onDuration之前的WUS时间窗口均配置有所述WUS的时域位置，则分别根据所述每个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述每个短DRX周期的onDuration定时器。
终端设备800能够实现前述实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
本发明实施例的终端设备600在配置有多个DRX组的情况下，通过接收用于指示是否启动全部DRX组的下一个DRX周期的onDuration定时器的WUS，从而终端设备可基于该WUS，决定在各DRX组的下一个DRX周期是否启动onDuration定时器。本发明实施例针对终端设备配置有多个DRX组的情况，提供了一种较为简便的WUS指示方案。
应理解的是，本发明实施例中，射频单元801可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器810处理；另外，将上行的数据发送给基站。通常，射频单元801包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元801还可以通过无线通信系统与网络和其他设备通信。
终端设备通过网络模块802为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元803可以将射频单元801或网络模块802接收的或者在存储器809中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元803还可以提供与终端设备800执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元803包括扬声器、蜂鸣器以及受话器等。
输入单元804用于接收音频或视频信号。输入单元804可以包括图形处理器(Graphics Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元806上。经图形处理器8041处理后的图像帧可以存储在存储器809(或其它存储介质)中或者经由射频单元801或网络模块802进行发送。麦克风8042可以 接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元801发送到移动通信基站的格式输出。
终端设备800还包括至少一种传感器805，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板8061的亮度，接近传感器可在终端设备800移动到耳边时，关闭显示面板8061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端设备姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器805还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元806用于显示由用户输入的信息或提供给用户的信息。显示单元806可包括显示面板8061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板8061。
用户输入单元807可用于接收输入的数字或字符信息，以及产生与终端设备的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元807包括触控面板8071以及其他输入设备8072。触控面板8071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板8071上或在触控面板8071附近的操作)。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器810，接收处理器810发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板8071。除了触控面板8071，用户输入单元807还可以包括其他输入设备8072。具体地，其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、 开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板8071可覆盖在显示面板8061上，当触控面板8071检测到在其上或附近的触摸操作后，传送给处理器810以确定触摸事件的类型，随后处理器810根据触摸事件的类型在显示面板8061上提供相应的视觉输出。虽然在图8中，触控面板8071与显示面板8061是作为两个独立的部件来实现终端设备的输入和输出功能，但是在某些实施例中，可以将触控面板8071与显示面板8061集成而实现终端设备的输入和输出功能，具体此处不做限定。
接口单元808为外部装置与终端设备800连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元808可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端设备800内的一个或多个元件或者可以用于在终端设备800和外部装置之间传输数据。
存储器809可用于存储软件程序以及各种数据。存储器809可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器809可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器810是终端设备的控制中心，利用各种接口和线路连接整个终端设备的各个部分，通过运行或执行存储在存储器809内的软件程序和/或模块，以及调用存储在存储器809内的数据，执行终端设备的各种功能和处理数据，从而对终端设备进行整体监控。处理器810可包括一个或多个处理单元；优选的，处理器810可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
终端设备800还可以包括给各个部件供电的电源811(比如电池)，优选 的，电源811可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端设备800包括一些未示出的功能模块，在此不再赘述。
优选的，本发明实施例还提供一种终端设备，包括处理器810，存储器809，存储在存储器809上并可在所述处理器810上运行的计算机程序，该计算机程序被处理器810执行时实现上述唤醒信号处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
参见图9，图9是本发明又一实施例提供的网络侧设备的结构图。如图9所示，网络侧设备900包括：处理器901、存储器902、总线接口903和收发机904，其中，处理器901、存储器902和收发机904均连接至总线接口903。
其中，在本发明实施例中，网络侧设备900还包括：存储在存储器902上并可在处理器901上运行的计算机程序，该计算机程序被处理器901执行时实现如下步骤：
在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
可选的，所述计算机程序被处理器901执行时实现如下步骤：
通过收发机904向所述终端设备发送第一指示；
其中，所述第一指示用于在所述WUS接收失败的情况下，指示是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
可选的，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
本发明实施例的网络侧设备900在为终端设备配置了至少两个DRX组的情况下，通过为所述终端设备配置用于指示是否启动全部DRX的下一个DRX周期的onDuration定时器的WUS，可使终端设备基于该WUS，确定在各DRX组的下一个DRX周期是否启动onDuration定时器。本发明实施例针对终端设 备配置有多个DRX组的情况，提供了一种较为简便的WUS指示方案。
本发明实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述唤醒信号处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本发明实施例还提供另一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述唤醒信号配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如ROM、RAM、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明各个实施例所述的方法。
上面结合附图对本发明的实施例进行了描述，但是本发明并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本发明的启示下，在不脱离本发明宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本发明的保护之内。

Claims (29)

  1. 一种唤醒信号处理方法，应用于终端设备，其特征在于，所述方法包括：
    在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
    其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
  2. 根据权利要求1所述的方法，其特征在于，在所述接收唤醒信号WUS之前，所述方法还包括：
    根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS，包括如下一项：
    在所述WUS的时域位置位于第一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；其中，所述第一DRX组为所述至少两个DRX组中配置有所述WUS的DRX组；
    在所述WUS的时域位置位于所述至少两个DRX组中全部DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；
    在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括如下一项：
    在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组中每个DRX组的下一个DRX周期的onDuration定时器；
    在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组的第二DRX组的下一个DRX周期的onDuration定时器，其中，所述第二DRX组为所述至少两个DRX组中配置有所述WUS的DRX组，或者所述第二DRX组为所述至少两个DRX组中激活时间与所述WUS的时域位置存在重叠的DRX 组。
  5. 根据权利要求1所述的方法，其特征在于，在所述接收唤醒信号WUS之后，所述方法还包括：
    根据所述WUS确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括如下一项：
    在所述WUS接收失败的情况下，根据第一指示确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；其中，所述第一指示为协议预定义或网络侧设备配置；
    在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；
    在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器。
  7. 根据权利要求6所述的方法，其特征在于，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
  8. 根据权利要求6所述的方法，其特征在于，所述在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或者全部DRX组的下一个DRX周期的onDuration定时器，包括如下一项：
    在所述WUS接收失败的情况下，启动所述至少两个DRX组的每个DRX组的下一个DRX周期的onDuration定时器；
    在所述WUS接收失败的情况下，启动第三DRX组的下一个DRX周期的onDuration定时器；其中，所述第三DRX组为所述至少两个DRX组中配置有所述WUS的DRX组。
  9. 根据权利要求6所述的方法，其特征在于，所述在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的 onDuration定时器，包括：
    在所述WUS接收失败的情况下，若所述WUS的时域位置位于第四DRX组的激活时间，则启动所述第四DRX组的下一个DRX周期的onDuration定时器；
    其中，所述第四DRX组为所述至少两个DRX组中的任一DRX组。
  10. 根据权利要求1所述的方法，其特征在于，第五DRX组配置有长DRX周期的参数和短DRX周期的参数，所述长DRX周期为所述短DRX周期的整数倍，所述第五DRX组为所述至少两个DRX组中的任一DRX组；
    所述方法还包括如下一项：
    在所述第五DRX组工作于所述短DRX周期的情况下，若仅所述长DRX周期的onDuration之前的WUS时间窗口配置有所述WUS的时域位置，则根据所述长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内的全部短DRX周期的onDuration定时器；
    在所述第五DRX组工作于所述短DRX周期的情况下，若每个短DRX周期的onDuration之前的WUS时间窗口均配置有所述WUS的时域位置，则分别根据所述每个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述每个短DRX周期的onDuration定时器。
  11. 一种唤醒信号配置方法，应用于网络侧设备，其特征在于，所述方法包括：
    在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
    其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一指示；
    其中，所述第一指示用于在所述WUS接收失败的情况下，指示是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
  13. 根据权利要求12所述的方法，其特征在于，所述第一指示包括一个 子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
  14. 一种终端设备，其特征在于，包括：
    接收模块，用于在所述终端设备配置有至少两个非连续接收DRX组的情况下，接收唤醒信号WUS；
    其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX组的下一个DRX周期的onDuration定时器。
  15. 根据权利要求14所述的终端设备，其特征在于，还包括：
    第一确定模块，用于根据所述至少两个DRX组中的部分或者全部DRX组的状态确定是否接收所述WUS。
  16. 根据权利要求15所述的终端设备，其特征在于，所述第一确定模块具体用于如下一项：
    在所述WUS的时域位置位于第一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；其中，所述第一DRX组为所述至少两个DRX组中配置有所述WUS的DRX组；
    在所述WUS的时域位置位于所述至少两个DRX组中全部DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS；
    在所述WUS的时域位置位于所述至少两个DRX组中任一DRX组的激活时间的情况下，确定放弃接收所述WUS，否则确定接收所述WUS。
  17. 根据权利要求16所述的终端设备，其特征在于，还包括第一启动模块，具体用于如下一项：
    用于在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组中每个DRX组的下一个DRX周期的onDuration定时器；
    在确定放弃接收所述WUS的情况下，启动所述至少两个DRX组的第二DRX组的下一个DRX周期的onDuration定时器，其中，所述第二DRX组为所述至少两个DRX组中配置有所述WUS的DRX组，或者所述第二DRX组为所述至少两个DRX组中激活时间与所述WUS的时域位置存在重叠的DRX组。
  18. 根据权利要求14所述的终端设备，其特征在于，还包括：
    第二确定模块，用于根据所述WUS确定是否启动所述至少两个DRX组中的全部DRX组的下一个DRX周期的onDuration定时器。
  19. 根据权利要求14所述的终端设备，其特征在于，还包括如下一项：
    第三确定模块，用于在所述WUS接收失败的情况下，根据第一指示确定是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器；其中，所述第一指示为协议预定义或网络侧设备配置；
    第二启动模块，用于在所述WUS接收失败的情况下，启动所述至少两个DRX组的部分或者全部DRX组的下一个DRX周期的onDuration定时器；
    第四确定模块，用于在所述WUS接收失败的情况下，根据所述至少两个DRX组中至少一个DRX组的状态确定是否启动所述至少两个DRX组中部分或全部DRX组的下一个DRX周期的onDuration定时器。
  20. 根据权利要求19所述的终端设备，其特征在于，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
  21. 根据权利要求19所述的终端设备，其特征在于，所述第二启动模块具体用于如下一项：
    在所述WUS接收失败的情况下，启动所述至少两个DRX组的每个DRX组的下一个DRX周期的onDuration定时器；
    在所述WUS接收失败的情况下，启动第三DRX组的下一个DRX周期的onDuration定时器；其中，所述第三DRX组为所述至少两个DRX组中配置有所述WUS的DRX组。
  22. 根据权利要求19所述的终端设备，其特征在于，所述第四确定模块具体用于在所述WUS接收失败的情况下，若所述WUS的时域位置位于第四DRX组的激活时间，则启动所述第四DRX组的下一个DRX周期的onDuration定时器；
    其中，所述第四DRX组为所述至少两个DRX组中的任一DRX组。
  23. 根据权利要求14所述的终端设备，其特征在于，第五DRX组配置 有长DRX周期的参数和短DRX周期的参数，所述长DRX周期为所述短DRX周期的整数倍，所述第五DRX组为所述至少两个DRX组中的任一DRX组；
    所述终端设备还包括第五确定模块，具体用于如下一项：
    在所述第五DRX组工作于所述短DRX周期的情况下，若仅所述长DRX周期的onDuration之前的WUS时间窗口配置有所述WUS的时域位置，则根据所述长DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述长DRX周期范围内的全部短DRX周期的onDuration定时器；
    在所述第五DRX组工作于所述短DRX周期的情况下，若所述每个短DRX周期的onDuration之前的WUS时间窗口均配置有所述WUS的时域位置，则分别根据所述每个短DRX周期的onDuration之前的WUS时间窗口接收的WUS，确定是否启动所述每个短DRX周期的onDuration定时器。
  24. 一种网络侧设备，其特征在于，包括：
    配置模块，用于在为终端设备配置了至少两个非连续接收DRX组的情况下，为所述终端设备配置唤醒信号WUS；
    其中，所述WUS用于指示是否启动所述至少两个DRX组中全部DRX的下一个DRX周期的onDuration定时器。
  25. 根据权利要求24所述的网络侧设备，其特征在于，还包括：
    发送模块，用于向所述终端设备发送第一指示；
    其中，所述第一指示用于在所述WUS接收失败的情况下，指示是否启动所述至少两个DRX组的部分或全部DRX组的下一个DRX周期的onDuration定时器。
  26. 根据权利要求25所述的网络侧设备，其特征在于，所述第一指示包括一个子指示，所述一个子指示对应于所述至少两个DRX组的全部DRX组；或者所述第一指示包括至少两个子指示，所述至少两个子指示分别与所述至少两个DRX组的不同DRX组对应。
  27. 一种终端设备，其特征在于，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10中任一项所述的唤醒信号处理方法的步骤。
  28. 一种网络侧设备，其特征在于，包括处理器、存储器及存储在所述 存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求11至13中任一项所述的唤醒信号配置方法的步骤。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的唤醒信号处理方法的步骤，或者实现如权利要求11至13中任一项所述的唤醒信号配置方法的步骤。
PCT/CN2020/137151 2019-12-24 2020-12-17 唤醒信号处理方法、唤醒信号配置方法及相关设备 WO2021129508A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20904501.2A EP4054249A4 (en) 2019-12-24 2020-12-17 METHOD FOR PROCESSING WAKE UP SIGNALS, METHOD FOR CONFIGURATION OF WAKE UP SIGNALS AND RELEVANT DEVICE
US17/737,987 US20220264696A1 (en) 2019-12-24 2022-05-05 Wake up signal processing method, wake up signal configuration method, and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911349121.6A CN113038575B (zh) 2019-12-24 2019-12-24 唤醒信号处理方法、唤醒信号配置方法及相关设备
CN201911349121.6 2019-12-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/737,987 Continuation US20220264696A1 (en) 2019-12-24 2022-05-05 Wake up signal processing method, wake up signal configuration method, and related device

Publications (1)

Publication Number Publication Date
WO2021129508A1 true WO2021129508A1 (zh) 2021-07-01

Family

ID=76451942

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/137151 WO2021129508A1 (zh) 2019-12-24 2020-12-17 唤醒信号处理方法、唤醒信号配置方法及相关设备

Country Status (4)

Country Link
US (1) US20220264696A1 (zh)
EP (1) EP4054249A4 (zh)
CN (1) CN113038575B (zh)
WO (1) WO2021129508A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11832334B2 (en) * 2020-03-20 2023-11-28 Qualcomm Incorporated Semi-independent discontinuous reception groups
US20210345247A1 (en) * 2020-04-30 2021-11-04 Qualcomm Incorporated Wakeup signal selected cell indication
WO2023201662A1 (en) * 2022-04-21 2023-10-26 Zte Corporation Wireless communication method and device thereof

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769309A (zh) * 2017-11-09 2019-05-17 中国移动通信有限公司研究院 一种非连续监听的方法、设备及计算机可读存储介质
US20190200296A1 (en) * 2017-12-21 2019-06-27 Qualcomm Incorporated Wake up signal configurations for wireless communications
CN109952789A (zh) * 2019-02-13 2019-06-28 北京小米移动软件有限公司 一种省电信号模式的使用方法、装置及终端

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116709271A (zh) * 2017-03-24 2023-09-05 苹果公司 用于机器类型通信和窄带物联网设备的唤醒信号
WO2019032009A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) SYSTEMS AND METHODS FOR ADAPTIVE MONITORING OF DOWNLINK CONTROL CHANNEL IN DISCONTINUOUS RECEPTION
US11265813B2 (en) * 2018-05-07 2022-03-01 Telefonaktiebolaget Lm Ericsson (Publ) Support for a wireless device with a wake-up receiver
US20190349856A1 (en) * 2018-05-11 2019-11-14 Qualcomm Incorporated Methods and apparatus for a group wake up signal
CN109923904B (zh) * 2019-02-11 2022-07-29 北京小米移动软件有限公司 信道监听方法及装置
WO2021007824A1 (zh) * 2019-07-17 2021-01-21 北京小米移动软件有限公司 唤醒信号处理、信息下发方法及装置、通信设备及介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769309A (zh) * 2017-11-09 2019-05-17 中国移动通信有限公司研究院 一种非连续监听的方法、设备及计算机可读存储介质
US20190200296A1 (en) * 2017-12-21 2019-06-27 Qualcomm Incorporated Wake up signal configurations for wireless communications
CN109952789A (zh) * 2019-02-13 2019-06-28 北京小米移动软件有限公司 一种省电信号模式的使用方法、装置及终端

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Email report [107bis#49][NR TEI16] cDRX enhancement for CA", 3GPP TSG-RAN2 MEETING #108 R2-1915292, 22 November 2019 (2019-11-22), XP051824768 *
See also references of EP4054249A4 *

Also Published As

Publication number Publication date
EP4054249A4 (en) 2023-01-04
EP4054249A1 (en) 2022-09-07
CN113038575B (zh) 2022-08-19
CN113038575A (zh) 2021-06-25
US20220264696A1 (en) 2022-08-18

Similar Documents

Publication Publication Date Title
WO2020156431A1 (zh) 非连续接收drx配置方法及终端
WO2021129507A1 (zh) 唤醒信号配置方法、唤醒信号处理方法及相关设备
WO2021129508A1 (zh) 唤醒信号处理方法、唤醒信号配置方法及相关设备
WO2021197378A1 (zh) 信号测量、测量间隔配置、测量上报方法、终端、网络设备及位置管理设备
US20220399976A1 (en) Method for sending, configuring, and measuring srs, positioning method, and device
WO2020253612A1 (zh) Pdcch监听方法和终端
CN112533235B (zh) 信道监听控制方法和终端
WO2021169939A1 (zh) Ps-pdcch配置方法、终端设备和网络侧设备
WO2021052420A1 (zh) 信道监听控制方法和终端
WO2021129504A1 (zh) Scell休眠指示处理方法、终端及网络设备
US20220248332A1 (en) Method for entering dormancy behavior and terminal
US20230007730A1 (en) Transmission or Reception Configuration Method and Electronic Device
US20220217634A1 (en) Method for receiving power saving signal, method for transmitting power saving signal, and related device
WO2021218842A1 (zh) 下行接收触发方法、终端和网络侧设备
WO2021218855A1 (zh) 下行接收触发方法、终端和网络侧设备
WO2021083104A1 (zh) 节能信号检测方法和终端
WO2021213265A1 (zh) 节能模式切换方法、终端及网络侧设备
WO2021197123A1 (zh) 休眠行为处理方法、指示方法、终端及网络设备
WO2021197191A1 (zh) 冲突资源确定方法和终端
WO2021164787A1 (zh) 信息上报方法、用户设备及网络侧设备
CN112543082B (zh) 监听方法、发送方法、终端及网络侧设备
WO2021036649A1 (zh) 模式切换方法、终端和网络设备
WO2021164681A1 (zh) 解码方法、解码配置方法、终端及网络侧设备
WO2020228614A1 (zh) 检测位置的确定方法、配置方法、终端及网络侧设备
US20210153289A1 (en) Information receiving method, information transmission method, terminal, and network-side device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20904501

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020904501

Country of ref document: EP

Effective date: 20220603

NENP Non-entry into the national phase

Ref country code: DE