WO2022062685A1 - 一种通信方法及设备 - Google Patents
一种通信方法及设备 Download PDFInfo
- Publication number
- WO2022062685A1 WO2022062685A1 PCT/CN2021/110381 CN2021110381W WO2022062685A1 WO 2022062685 A1 WO2022062685 A1 WO 2022062685A1 CN 2021110381 W CN2021110381 W CN 2021110381W WO 2022062685 A1 WO2022062685 A1 WO 2022062685A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- dcp
- drx
- carriers
- terminal device
- group
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 202
- 238000004891 communication Methods 0.000 title claims abstract description 87
- 239000000969 carrier Substances 0.000 claims abstract description 773
- 238000012544 monitoring process Methods 0.000 claims abstract description 366
- 230000007958 sleep Effects 0.000 claims abstract description 180
- 230000004913 activation Effects 0.000 claims description 171
- 230000005059 dormancy Effects 0.000 claims description 36
- 230000015654 memory Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 11
- 125000004122 cyclic group Chemical group 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 abstract description 36
- 230000002779 inactivation Effects 0.000 description 78
- 230000000875 corresponding effect Effects 0.000 description 74
- 230000006870 function Effects 0.000 description 55
- 230000006399 behavior Effects 0.000 description 54
- 230000005540 biological transmission Effects 0.000 description 54
- 238000012545 processing Methods 0.000 description 36
- 230000008569 process Effects 0.000 description 25
- 101150087322 DCPS gene Proteins 0.000 description 16
- 101100386724 Schizosaccharomyces pombe (strain 972 / ATCC 24843) nhm1 gene Proteins 0.000 description 16
- 230000007246 mechanism Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 230000011664 signaling Effects 0.000 description 13
- 230000002618 waking effect Effects 0.000 description 10
- 230000002776 aggregation Effects 0.000 description 7
- 238000004220 aggregation Methods 0.000 description 7
- 230000009849 deactivation Effects 0.000 description 7
- 230000004622 sleep time Effects 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 108010076504 Protein Sorting Signals Proteins 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 235000019800 disodium phosphate Nutrition 0.000 description 2
- 230000002035 prolonged effect Effects 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/0241—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where no transmission is received, e.g. out of range of the transmitter
-
- 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 application relates to the field of communication technologies, and in particular, to a communication method and device.
- the indication signal is a physical downlink control channel wake-up signal (PDCCH-WUS).
- the indication signal can indicate whether the UE needs to wake up or can sleep within the subsequent DRX "activation time”.
- PDCCH-WUS is also known as downlink control information with cyclic redundancy check scrambled by using power saving radio network temporary identity (PS-RNTI) scrambled in the standard PS-radio network tempory identity, DCP), the signal form of DCP can be DCI.
- PS-RNTI power saving radio network temporary identity
- one monitoring occasion may include one or more DCP monitoring occasions (DCP occurrence(s)).
- a user equipment (user equipment, UE) in a radio resource control (radio resource control, RRC) connected (connected) state can support two discontinuous reception (discontinuous reception, DRX) configurations.
- RRC radio resource control
- DRX discontinuous reception
- the two DRX configuration technologies are not used in combination with the wake-up signal, which affects the flexibility of the base station configuration.
- the introduction of two DRX configurations is to save functions, and the purpose of the wake-up signal is also to save power consumption. If the two cannot be combined, the purpose of further reducing UE power consumption cannot be achieved.
- Embodiments of the present application provide a communication method and device for reducing power consumption of a UE.
- a first communication method is provided, and the method can be executed by a terminal device, or executed by a chip system, and the chip system can realize the functions of the terminal device.
- the terminal equipment is configured with a first group of carriers and a second group of carriers, the first group of carriers belongs to FR1, the first group of carriers includes one or more carriers configured for the terminal equipment, and the first group of carriers
- the first DRX configuration is applied to a group of carriers, the first DRX duration corresponds to the first DRX configuration, the second group of carriers belongs to FR2, and the second group of carriers includes one or more carriers configured for the terminal device.
- a second DRX configuration is applied to the second group of carriers, and the second DRX duration corresponds to the second DRX configuration.
- the method includes: when the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, determining, by the terminal device, not to monitor the DCP within the first DCP monitoring opportunity, and the first DCP monitoring opportunity configured on the first group of carriers.
- the terminal device On the first set of carriers, the terminal device wakes up within the first DRX duration associated with the first DCP listening opportunity, and on the second set of carriers, the terminal device wakes up on the first set of carriers according to the first rule Wake up or sleep within the second DRX duration associated with a DCP listening opportunity, wherein the first DRX duration corresponds to the first DRX configuration, the second DRX duration corresponds to the second DRX configuration, and the The first rule is a preset rule, or the first rule is a rule configured by configuration information from a network device; or, the time domain position of the first DCP listening opportunity is not located or partially located in the first DRX activation.
- the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, the terminal device monitors the DCP during the first DCP monitoring opportunity; the terminal device monitors the DCP according to the monitored DCP indicates that on the first set of carriers, sleep or wake up for the first DRX duration, and, on the second set of carriers, sleep or wake up for the second DRX duration.
- the two DRX configuration technologies can be used in combination with the wake-up signal, which helps to further reduce the power consumption of the terminal device.
- the behavior of the terminal equipment in the case of combination is specified.
- the monitoring situation of the terminal equipment on the DCP monitoring timing corresponding to the first group of carriers is applicable to both the first group of carriers and the second group of carriers. In this way, the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, which reduces the power consumption of the terminal equipment for monitoring the DCP.
- the monitoring situation of the terminal device on one set of carriers can be applied to the two sets of carriers, so that both sets of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two sets of carriers.
- a first communication method is provided, and the method can be executed by a terminal device, or executed by a chip system, and the chip system can realize the functions of the terminal device.
- the method includes: the terminal device determines whether to monitor the DCP in the first DCP monitoring occasion; if the terminal device determines not to monitor the DCP in the first DCP monitoring occasion, on the first group of carriers, the terminal The device wakes up within the first DRX duration associated with the first DCP listening opportunity, and, on the second set of carriers, the terminal device wakes up within the second DRX duration associated with the first DCP listening opportunity or sleep, wherein the first group of carriers includes one or more carriers configured for the terminal device, the first group of carriers applies a first DRX configuration, and the first DRX duration corresponds to the first DRX configuration , the second group of carriers includes one or more carriers configured for the terminal device, the second group of carriers applies a second DRX configuration, and the second DRX duration corresponds to the second DRX configuration.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the behavior of the terminal device in the case of combination is specified, for example, the terminal device monitors the DCP monitoring timing corresponding to the first group of carriers
- the situation is applicable to both the first group of carriers and the second group of carriers.
- the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, which reduces the power consumption of the terminal equipment for monitoring the DCP.
- the monitoring situation of the terminal device on one set of carriers can be applied to the two sets of carriers, so that both sets of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two sets of carriers.
- the first DCP listening opportunity is configured on the first group of carriers.
- the network device does not need to configure the DCP monitoring opportunity for the second group of carriers, and the terminal device only needs to monitor within the DCP monitoring opportunity on the first group of carriers, and the monitoring result can be applied to the two groups of carriers. In this way, both groups of carriers can use the DCP mechanism to reduce the power consumption of the terminal equipment. Moreover, the terminal device does not need to monitor the DCP on the second group of carriers, which further reduces the power consumption of the terminal device to monitor the DCP.
- the first DRX duration is located in the first DCP in the time domain After listening time.
- one or more DRX cycles located after the first DCP listening opportunity in the time domain can be associated with the first DCP listening opportunity.
- DRX cycles are associated with the first DCP listening opportunity, it can be determined through the protocol specified, or configured by a network device. If the first DCP listening opportunity is associated with multiple DRX cycles, the multiple DRX cycles may or may not be continuous in the time domain.
- the first DRX duration may include the duration in all or part of the DRX cycle associated with the first DCP monitoring occasion under the first DRX configuration, or in other words, the first DRX duration may include the first DCP monitoring on the first group of carriers. Duration within all or part of the DRX cycle to which the opportunity is associated.
- the terminal device determines whether to Monitor the DCP during the first DCP monitoring opportunity, including:
- the terminal device determines not to monitor the DCP during the first DCP listening opportunity; or, monitor the first DCP during the first DCP monitoring time In the case that the time domain position of the opportunity is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; wherein, the first DRX activation time is the first DRX activation time.
- the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, In the case where the maximum number of DCI sizes that can be monitored is less than the number of DCI sizes that the terminal device needs to monitor, the terminal device determines not to monitor DCPs within the first DCP monitoring opportunity; or,
- the terminal device determines to monitor the DCP within the first DCP monitoring opportunity; or, the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, and is within the size of the DCI that can be monitored at most When the number of DCIs is less than the number of DCIs that the terminal device needs to monitor, the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity; wherein, the first DRX activation time is the The DRX activation time corresponding to the first DRX configuration.
- the terminal device may determine according to the time domain position of the first DCP listening opportunity. This determination method is easy to implement for the terminal device, and is also conducive to compatibility with existing technologies. Alternatively, the terminal device may be determined according to the size budget of the DCI, which is relatively simple and reasonable. Alternatively, the terminal device may also determine by combining the two determination methods, which can make the determination result more accurate.
- the embodiments of the present application provide a variety of determination methods, and which determination method to choose can be determined by the terminal device itself, or configured by the network device, or can be defaulted, or can also be specified by a protocol.
- the method further includes: the terminal device receives configuration information from a network device, and the configuration information is used to configure: in the case that the terminal device does not monitor within the DCP monitoring opportunity, the The terminal device wakes up or sleeps within the second DRX duration associated with the DCP listening opportunity.
- whether the terminal device wakes up or sleeps within the DRX duration associated with the DCP monitoring opportunity may be a default rule, or may be specified by a protocol, or It can also be configured by a network device. If configured by the network device, the network device can configure it according to the service transmission situation of the terminal device on the second group of carriers, so that the terminal device dormancy or wake-up on the second group of carriers is more in line with the service requirements of the terminal device.
- the method further includes: if the terminal device determines to monitor the DCP in the first DCP monitoring opportunity, the terminal device monitors the DCP in the first DCP monitoring opportunity; The terminal device sleeps or wakes up for the first DRX duration on the first group of carriers according to the monitoring of the DCP, and, on the second group of carriers, on the second DRX duration time to sleep or wake up.
- the terminal device listens in the first DCP listening opportunity, then the terminal device sleeps or wakes up on the two sets of carriers according to the indication of the DCP monitored in the first DCP monitoring opportunity, that is, the terminal device is in the first DCP monitoring opportunity
- the monitoring result can guide the behavior of the terminal device on the two sets of carriers, which reduces the process of monitoring the DCP by the terminal device and saves power consumption.
- the terminal device according to the monitoring situation of the DCP, on the first group of carriers, Sleeping within the first DRX duration, and, on the second group of carriers, sleeping within the second DRX duration includes: receiving, by the terminal device, a signal from the terminal device within the first DCP listening opportunity In the case where the first DCP of the network device and the first DCP indicates dormancy, on the first group of carriers, the terminal device sleeps for the first DRX duration, and, on the On the second group of carriers, the terminal device sleeps within the second DRX duration; or, in the case that the terminal device does not receive the DCP from the network device within the first DCP listening opportunity, On the first set of carriers, the terminal device sleeps for the first DRX duration, and on the second set of carriers, the terminal device sleeps for the second DRX duration.
- the terminal device according to the monitoring situation of the DCP, on the first group of carriers, Waking up within the first DRX duration, and, on the second group of carriers, waking up within the second DRX duration includes: receiving, by the terminal device, an In the case where the first DCP of the network device and the first DCP indicates wake-up, on the first set of carriers, the terminal device wakes up within the first DRX duration, and, on the first set of carriers, the terminal device wakes up within the first DRX duration On the second group of carriers, the terminal device wakes up within the second DRX duration; or, when the terminal device receives the first DCP from the network device within the first DCP listening opportunity , on the first set of carriers, the terminal device wakes up within the first DRX duration, and on the second set of carriers, the terminal device wakes up within the second DRX duration .
- the terminal device according to the monitoring situation of the DCP, on the first group of carriers, Sleeping or waking up within the first DRX duration, and, on the second group of carriers, sleeping or waking up within the second DRX duration, including: monitoring the terminal equipment on the first DCP
- the first DCP from the network device is received within the opportunity, and the first DCP includes first indication information and second indication information; wherein the first indication information indicates wake-up, and the second indication information indicates In the case of waking up, on the first set of carriers, the terminal device wakes up within the first DRX duration, and on the second set of carriers, the terminal device wakes up on the second DRX Wake up within the duration; or, in the case that the first indication information indicates dormancy, and the second indication information indicates dormancy, on the first group of carriers, the terminal equipment continues to operate in the first DRX sleep for a period of time, and, on the second group of carriers,
- the ninth optional embodiment of the first aspect on the first group of carriers, the terminal equipment sleeps within the first DRX duration, including: the terminal equipment does not start and does not restart the first DRX duration at the start time of the first DRX duration A DRX duration timer, the first DRX duration timer corresponds to the first DRX configuration.
- the tenth optional embodiment of the first aspect on the first group of carriers, waking up the terminal device within the first DRX duration includes: the terminal device starting or restarting the first DRX at the start time of the first DRX duration A duration timer, where the first DRX duration timer corresponds to the first DRX configuration.
- the eleventh optional implementation of the first aspect In the method, on the second group of carriers, the terminal device sleeps within the second DRX duration, including: the terminal device does not start and does not restart at the start time of the second DRX duration A second DRX duration timer, where the second DRX duration timer corresponds to the second DRX configuration.
- waking up the terminal device within the second DRX duration includes: the terminal device starting or restarting the second DRX duration at the start time of the second DRX duration. Two DRX duration timers, where the second DRX duration timer corresponds to the second DRX configuration.
- the frequency range to which the first group of carriers belongs is different from the frequency range to which the second group of carriers belongs; or, the frequency corresponding to the frequency range to which the second group of carriers belongs is greater than the The frequency corresponding to the frequency range to which a group of carriers belongs; or, the length of the DRX activation time corresponding to the first group of carriers is greater than or equal to the length of the DRX activation time corresponding to the second group of carriers.
- the two groups of carriers configured for the terminal equipment belong to different frequency ranges, so that the terminal equipment can operate in a larger frequency range.
- the frequencies of the first group of carriers belong to FR1
- the frequencies of the second group of carriers belong to FR2. Since the frequency of the second group of carriers is greater than the frequency of the first group of carriers, the power consumption of the terminal device when working on the second group of carriers will be greater. Therefore, the embodiment of the present application allows the terminal device to only monitor the first group of carriers.
- the DCP does not need to monitor the DCP on the second group of carriers, thereby saving the power consumption caused by the terminal equipment working on the second group of carriers.
- the network device may send DCI on the first set of carriers, where the DCI is used to schedule data on the second set of carriers, so the terminal device may need to receive scheduling information for the second set of carriers on the first set of carriers.
- the length of the DRX activation time corresponding to the first group of carriers may be greater than or equal to the length of the DRX activation time corresponding to the second group of carriers.
- the DRX activation time corresponding to the first group of carriers may cover the second group of carriers.
- the terminal equipment can receive the scheduling information corresponding to the second group of carriers within the DRX activation time of the first group of carriers, and reduce the inability of the terminal equipment to receive scheduling information on the second group of carriers.
- the probability of receiving data or sending data reduces service transmission delay.
- a second communication method is provided, and the method can be executed by a terminal device, or executed by a chip system, and the chip system can realize the functions of the terminal device.
- the method includes: when the terminal device determines not to monitor the DCP in the first DCP monitoring occasion, the terminal device determines whether to monitor the DCP in the second DCP monitoring occasion, and the first DCP monitoring occasion is configured in the first group On the carrier, the second DCP listening opportunity is configured on a second group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, and the first group of carriers applies the first DRX configuration, The second group of carriers includes one or more carriers configured for the terminal device, and the second group of carriers applies the second DRX configuration; when the terminal device determines to monitor the DCP within the second DCP monitoring opportunity In this case, the terminal device monitors the DCP in the second DCP monitoring opportunity, and according to the monitoring situation of the DCP, on the second group of carriers, the second DRX associated with the second DCP monitoring opportunity continues. sleep
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the behavior of the terminal device in the combination is specified.
- the UE preferentially monitors the first DCP monitoring timing, and if the first DCP monitoring timing can be monitored, the UE does not need to monitor the second DCP monitoring timing, so as to save power consumption caused by the UE monitoring the DCP monitoring timing. If the UE cannot monitor the first DCP monitoring occasion, the UE may also determine whether it can monitor the second DCP monitoring occasion, so that the UE's behavior is performed under the instruction of the monitoring result as much as possible, so as to better meet the requirements of the network device.
- the network device can configure the second DCP listening timing for the second group of carriers, so that the network device has stronger control over the behavior of the UE on the second group of carriers, and also increases the flexibility of network device scheduling .
- the method further includes: the terminal device determining whether to monitor the DCP during the first DCP monitoring opportunity.
- the method further includes: determining, by the terminal device, that in the second If the DCP is not monitored within the DCP monitoring opportunity, on the second group of carriers, the terminal device wakes up within the second DRX duration.
- the behavior of the terminal device on the second group of carriers may be the default, or may also be specified by a protocol. For example, the terminal device on the second group of carriers may wake up within the second DRX duration for service transmission. Alternatively, the terminal device may also sleep on the second group of carriers for the second DRX duration, so as to reduce the power consumption of the terminal device.
- the method further Including: when the terminal device determines to monitor the DCP in the first DCP monitoring opportunity, the terminal device monitors the first DCP on the first group of carriers according to the monitoring of the DCP Sleeping or waking up within the first DRX duration associated with the opportunity, and, on the second group of carriers, sleeping or waking up within the second DRX duration, the first DRX duration corresponding to the first DRX configuration.
- the method further includes: in the case that the terminal device determines to monitor the DCP within the first DCP monitoring opportunity, on the second group of carriers, the terminal device does not 2. Monitor during the DCP monitor time.
- the terminal device may determine the behavior on the first set of carriers and determine the behavior on the second set of carriers according to the indication of the DCP monitored during the first DCP listening occasion behavior above. In this case, the terminal device does not need to monitor the second DCP monitoring timing, which reduces the power consumption of the terminal device due to monitoring the DCP.
- the method further includes: in the case that the terminal device determines not to monitor the DCP in the first DCP monitoring occasion, on the first group of carriers, the terminal device is in the Wake up within the first DRX duration associated with the first DCP listening opportunity, where the first DRX duration corresponds to the first DRX configuration.
- the behavior of the terminal device on the first group of carriers may be the default, or may also be specified by a protocol. For example, the terminal device wakes up within the first DRX duration to perform service transmission. For another example, the terminal device may also sleep within the first DRX duration to save power consumption of the terminal device.
- the terminal device determines whether to monitor the DCP in the first DCP monitoring opportunity, including: In the case where the time domain position of the first DCP listening opportunity is within the first DRX activation time, the terminal device determines not to monitor the DCP within the first DCP monitoring opportunity; or, in the first DCP monitoring opportunity In the case that the time domain position of the terminal device is not within or partially within the first DRX activation time, the terminal device determines to monitor the DCP within the first DCP listening opportunity; wherein, the first DRX activation time is the first DRX activation time The DRX activation time corresponding to the DRX configuration; or, when the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines that the The DCP is monitored within a DCP monitoring opportunity; or, in the case that the maximum number of DCI sizes that can be monitored is less than
- the terminal device may determine according to the time domain position of the first DCP listening opportunity. This determination method is easy to implement for the terminal device, and is also conducive to compatibility with existing technologies. Alternatively, the terminal device may be determined according to the size budget of the DCI, which is relatively simple and reasonable. Alternatively, the terminal device may also determine by combining the two determination methods, which can make the determination result more accurate.
- the embodiments of the present application provide a variety of determination methods, and which determination method to choose can be determined by the terminal device itself, or configured by the network device, or can be defaulted, or can also be specified by a protocol.
- the terminal device determining whether to monitor the DCP during the second DCP monitoring opportunity includes: in the case that the time domain position of the second DCP monitoring opportunity is within the second DRX activation time, the terminal device The device determines not to monitor the DCP within the first DCP listening opportunity; or, in the case that the time domain position of the second DCP listening opportunity is not within or partially within the second DRX activation time, the terminal device determines to be within the second DRX activation time.
- the DCP is monitored within the first DCP monitoring opportunity; wherein, the second DRX activation time is the DRX activation time corresponding to the second DRX configuration; or, the maximum number of DCIs that can be monitored is greater than or equal to the In the case of the number of DCI sizes that the terminal device needs to monitor, the terminal device determines to monitor the DCP within the second DCP monitoring opportunity; or, when the maximum number of DCI sizes that can be monitored is less than the terminal device In the case of the number of DCIs that the device needs to monitor, the terminal device determines not to monitor the DCP in the second DCP monitoring opportunity; or, the time domain position of the second DCP monitoring opportunity is located at the second DRX During the activation time, and when the maximum number of DCI sizes that can be monitored is greater than or equal to the number of DCI sizes that the terminal device needs to monitor, the terminal device determines that within the second DCP monitoring opportunity Monitoring the DCP; or, the time domain position of the second DCP monitoring opportunity is within the second DRX activ
- the terminal device may determine according to the time domain position of the second DCP listening opportunity. This determination method is easy to implement for the terminal device, and is also conducive to compatibility with existing technologies. Alternatively, the terminal device may be determined according to the size budget of the DCI, which is relatively simple and reasonable. Alternatively, the terminal device may also determine by combining the two determination methods, which can make the determination result more accurate.
- the embodiments of the present application provide a variety of determination methods, and which determination method to choose can be determined by the terminal device itself, or configured by the network device, or can be defaulted, or can also be specified by a protocol.
- the terminal device determines not to monitor the DCP in the first DCP monitoring opportunity, and determines to monitor the DCP in the second DCP monitoring opportunity, including: when the first DCP monitoring opportunity If the domain position is within the first DRX activation time, and the time domain position of the second DCP listening opportunity is not within or partially within the second DRX activation time, the terminal device determines that the first DCP listening opportunity is within the first DCP listening opportunity The DCP is not monitored during the period, and it is determined that the DCP is monitored within the second DCP monitoring opportunity.
- a third communication method is provided, and the method can be executed by a terminal device, or executed by a chip system, and the chip system can realize the functions of the terminal device.
- the method includes: a terminal device receives a DCI from a network device on a first carrier, the first carrier belongs to a first group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, and the The first DRX configuration is applied to the first group of carriers; the terminal equipment is determined to sleep or wake up within the second DRX duration associated with the DCI on the second group of carriers according to the second indication information included in the DCI, so
- the second DRX duration corresponds to a second DRX configuration, the second DRX configuration is applied to the second group of carriers, and the second group of carriers includes one or more carriers configured for the terminal device, wherein when all When the value of the second field included in the DCI is the first value, it is used to indicate that the DCI includes the second indication information.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the embodiment of the present application does not need to configure the DCP, but implements the DCP function through ordinary DCI, reducing the number of DCI sizes that the UE needs to monitor. number, or enable the UE to monitor more DCI size, which also simplifies the implementation of the network device and the UE.
- the network device can instruct the UE to wake up or sleep on the carrier group through the corresponding indication information, and the indication method is more flexible, which is more in line with the service transmission requirements of the UE, and also increases the flexibility of the network device scheduling.
- the embodiment of the present application also avoids that the UE wakes up on the second group of carriers within the second DRX duration by default, which can reduce the power consumption of the UE.
- the value of the second field is a second value, it is used to indicate that the DCI does not include the second indication information.
- the second field with a value of the first value may be used to indicate that the DCI also includes second indication information, and if it is not a DCI used to implement the DCP function, the value of the second field
- the value may not be the first value, such as a common value, then the terminal device can determine whether the DCI includes the second indication information according to the value of the second field, the indication is relatively clear, and there is no need to add other indication information.
- the second field includes one or more of the following fields: FDRA field, MCS field, NDI field, RV field, HARQ process number field, antenna port field, or, demodulation reference signal sequence initialization field.
- the second field may include one or more of the above fields, or the second field may include other fields in addition to the above fields, or the second field may not include the above fields but include other fields.
- the other fields are, for example, other existing fields included in the DCI except the above fields, or may also be newly added fields in the DCI.
- the method further Including: the terminal device determines, according to the first indication information included in the DCI, to sleep or wake up on the first group of carriers within the first DRX duration associated with the DCI, and the first DRX duration Corresponding to the first DRX configuration, when the value of the second field is the first value, it is further used to indicate that the DCI includes the first indication information.
- the DCI may further include the first indication information, and if the value of the second field is not the first value, the DCI does not include the first indication information.
- the network device respectively instructs the dormancy or wake-up of the two groups of carriers through the second indication information and the first indication information, so that the behavior of the UE is more explicit and more in line with service requirements.
- the method further includes: on the first group of carriers, the terminal device sleeps or wakes up within a first DRX duration associated with the DCI, where the first DRX duration corresponds to the first DRX configuration;
- the terminal device determines that it is on the second group of carriers according to the second indication information included in the DCI, and sleeps or wakes up within the second DRX duration associated with the DCI, including: When the DCP is not monitored on the group of carriers, the terminal device determines, according to the second indication information included in the DCI, to sleep or wake up on the second group of carriers within the second DRX duration associated with the DCI;
- the method further includes: on the first group of carriers, the terminal device sleeps or wakes up within a first DRX duration associated with the DCI, where the first DRX duration corresponds to the first DRX configuration.
- the DCI may not indicate the behavior of the UE on the first set of carriers, then, by default (or, as specified by the protocol), the UE wakes up on the first set of carriers within the first DRX duration associated with the DCI. Because if the second indication information indicates that the UE wakes up on the second set of carriers within the second DRX duration, and the network device needs to schedule the UE's data transmission on the second set of carriers on the first set of carriers, then if the UE Sleeping on the first group of carriers for the first DRX duration may fail to receive scheduling information from the network device, so that data transmission cannot be performed on the second group of carriers.
- the UE may sleep on the first group of carriers for the first DRX duration by default (or stipulated by the protocol), so as to reduce the probability that the UE misses the scheduling information and reduce the transmission delay of the service.
- the UE sleeps on the first group of carriers for the first DRX duration associated with the DCI, and in this way, the power consumption of the UE can be saved.
- a fourth communication method is provided.
- the method can be performed by a network device, or by a chip system capable of implementing the functions of the network device.
- the network device is an access network device.
- the access network device is a base station.
- the method includes: a network device sends a DCI to a terminal device on a first carrier, the first carrier belongs to a first group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, the The first DRX configuration is applied to the first group of carriers, wherein when the value of the second field included in the DCI is a first value, it is used to indicate that the DCI includes second indication information, and the second indication information is used for Indicates that on the second group of carriers, sleep or wake up within the second DRX duration associated with the DCI, the second DRX duration corresponds to the second DRX configuration, and the second group of carriers applies the second DRX configuration , the second group of carriers includes one or more carriers configured for the terminal device.
- the value of the second field is a second value, it is used to indicate that the DCI does not include the second indication information.
- the second field includes one or more of the following fields: FDRA field, MCS field, NDI field, RV field, HARQ process number field, antenna port field, or, demodulation reference signal sequence initialization field.
- the DCI when the value of the second field is the first value, it is further used to indicate that the DCI includes the first indication information, and the first indication information is used to indicate that on the first group of carriers, the DCI Sleep or wake up within the associated first DRX duration, where the first DRX duration corresponds to the first DRX configuration.
- a fifth communication method is provided, and the method can be executed by a terminal device, or executed by a chip system, and the chip system can realize the functions of the terminal device.
- the method includes: the terminal device receives a second DCI on a first carrier, the first carrier belongs to a first group of carriers, the second DCI is used for scheduling data on the second group of carriers, wherein the first group A first DRX configuration is applied to a carrier, a second DRX configuration is applied to the second group of carriers, the first group of carriers includes one or more carriers configured for the terminal device, and the second group of carriers includes one or more carriers configured for the terminal device One or more carriers of the terminal equipment; the terminal equipment starts or restarts the second DRX inactivity timer, and sets the duration of the second DRX inactivity timer to the DRX inactivity timer configured by the second DRX configuration. The length of time to activate the timer.
- the two DRX configuration technologies can be used in combination with the cross-carrier scheduling technology.
- the UE can receive on the first set of carriers a message for scheduling on the second set of carriers from the network device.
- the DCI of the data and the UE can also receive data or send data on the second group of carriers, so that the cross-carrier scheduling technology can be realized in the context of the two DRX configuration technologies.
- the duration of the first DRX inactive timer corresponding to the first group of carriers can be set to different durations according to different situations, so that the duration of the first DRX inactive timer is more in line with the current service transmission. It also saves the power consumption of the UE.
- starting or restarting the second DRX inactivation timer by the terminal device includes: after the terminal device finishes receiving the second DCI of the first time domain symbol, start or restart the second DRX inactivity timer.
- the time domain symbols are, for example, orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) symbols.
- the second DCI includes second indication information, and the second indication information It is used to instruct to start or restart the second DRX inactivity timer.
- the second indication information may be carried by an existing field in the second DCI, for example, if there are reserved bits in the existing field included in the second DCI, it may be carried by the reserved bits; or, a new one may be added in the second DCI or multiple bits to carry the second indication information.
- the indication is performed through the second DCI, so that the UE is more explicit about the behavior of the UE.
- the method when the terminal device is in the After receiving the second DCI on the first carrier, the method further includes: starting or restarting, by the terminal device, a first DRX inactivation timer, and setting the duration of the first DRX inactivation timer to the first DRX inactivation timer The duration of the DRX inactivity timer configured by the DRX configuration, or set to the duration of the DRX inactivity timer configured by the second DRX configuration, where the first DRX inactivity timer corresponds to the first DRX configuration.
- the subsequent network device may also schedule data on the second group of carriers by means of cross-carrier scheduling.
- the network device may also schedule data on the first group of carriers on the first group of carriers. Therefore, the DRX activation time of the UE on the first set of carriers may be extended to receive DCI for scheduling data.
- an implementation manner is to extend the first DRX inactivation timer.
- the UE may set the duration of the first DRX inactivity timer to the original duration of the first DRX inactivity timer, that is, the duration of the DRX inactivity timer configured by the first DRX configuration.
- This setting method is relatively simple, and it is also a setting that is easy for the UE to implement.
- the UE may also set the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured in the second DRX configuration. It can be understood that the UE sets the duration of the first DRX inactivity timer to The duration of the second DRX inactivity timer.
- the duration of the DRX activation time of the UE on the first group of carriers may be the same as the duration of the DRX activation time of the UE on the second group of carriers.
- the DCI used to schedule the data of the second group of carriers will not consume too much power because the DRX activation time on the first group of carriers is too long.
- the terminal device sets the duration of the first DRX inactivity timer to the In the case of the duration of the DRX inactivity timer configured by the second DRX configuration, the method further includes: before the terminal device restarts the first DRX inactivity timer, determining the first DRX inactivity timer The controller is in the running state, and it is determined that the remaining duration of the first DRX inactivity timer is shorter than the duration of the DRX inactivity timer configured by the second DRX configuration.
- the UE may not need to start or restart the first DRX inactivity timer under any circumstances, but may first determine whether to start or restart the first DRX inactivity timer. For example, before the UE starts or restarts the first DRX inactivity timer, if the first DRX inactivity timer is in the running state, the UE may determine the remaining duration of the first DRX inactivity timer and the value configured by the second DRX configuration. The size relationship between the durations of the DRX inactivity timers.
- the UE may set the duration of the first DRX inactivity timer to the duration configured by the second DRX configuration The duration of the DRX inactivation timer; or, if the remaining duration of the first DRX inactivation timer is longer than or equal to the duration of the DRX inactivation timer configured in the second DRX configuration, the UE does not need to restart the first DRX inactivation timer. Activate the timer. In this way, the duration of the first DRX inactivation timer is avoided from being long or short, and the complexity of UE processing is reduced.
- the terminal device starts or restarts the first DRX inactivation timer, and the Before the duration of a DRX inactivity timer is set to the duration of the DRX inactivity timer configured by the first DRX configuration, the method further includes: receiving, by the terminal device, a first DCI on the first group of carriers , the first DCI is used to schedule data on the first group of carriers.
- the UE may The duration of the first DRX deactivation timer is set to the duration of the DRX deactivation timer configured in the first DRX configuration, so as to meet the requirements of the UE for receiving data or sending data on the first group of carriers, and can also meet the needs of the UE in the first group of carriers. A scheduled requirement to receive data on a set of carriers corresponding to the first set of carriers.
- the second DCI includes first indication information, and the first indication information is used to indicate startup Or restart the first DRX inactivity timer.
- the second DCI may include first indication information, and the first indication information may instruct to start or restart the first DRX inactivity timer.
- the indication is performed through the second DCI, so that the UE is more explicit about the behavior of the UE.
- the first indication information is further used to indicate that the first DRX inactivation timer is deactivated.
- the timing duration is set to the duration of the DRX deactivation timer configured by the first DRX configuration, or instructs to set the timing duration of the first DRX deactivation timer to the DRX deactivation duration configured by the second DRX configuration The duration of the timer.
- the first indication information may not only instruct the UE to start or restart the first DRX inactivity timer, but also indicate how to set the duration of the first DRX inactivity timer. Then, the UE does not need to determine how to set the duration of the first DRX inactivation timer by itself, which simplifies the implementation of the UE.
- the method further Including: the terminal device extending the end time of the DRX activation time of the terminal device on the first group of carriers to be the same as the end time of the DRX activation time of the terminal device on the second group of carriers .
- the UE wants to extend the DRX activation time of the UE on the first group of carriers.
- One implementation is to extend the first DRX inactivation timer, and another implementation does not require the first DRX inactivation timer, but can Directly extending the end time of the DRX activation time on the first set of carriers, for example, extending the end time of the UE's DRX activation time on the first set of carriers to be the same as the end time of the UE's DRX activation time on the second set of carriers.
- the duration of the DRX activation time of the UE on the first set of carriers is the same as the duration of the DRX activation time of the UE on the second set of carriers, and the UE can receive both on the first set of carriers.
- the DCI used for scheduling the data of the second group of carriers will not consume too much power because the DRX activation time on the first group of carriers is too long.
- the first DRX inactive time timer is not needed, and the power consumption caused by the UE maintaining the first DRX inactive time timer is reduced.
- the second DCI is used to indicate new transmission of downlink data or new transmission of uplink data.
- a communication device may include a module for performing the method in the first aspect or any optional implementation manner of the first aspect, for example including a transceiver unit and a processing unit.
- a storage unit may also be included.
- a communication device in a seventh aspect, may comprise a module for performing the method in the second aspect or any optional implementation manner of the second aspect, for example comprising a transceiving unit and a processing unit.
- a storage unit may also be included.
- a communication device may include a module for performing the method in the third aspect or any optional implementation manner of the third aspect, for example including a transceiver unit and a processing unit.
- a storage unit may also be included.
- a communication device may include a module for performing the method in the fourth aspect or any optional implementation manner of the fourth aspect, for example including a transceiver unit and a processing unit.
- a storage unit may also be included.
- a tenth aspect provides a communication device.
- the communication apparatus may include a module for performing the method in the fifth aspect or any optional implementation manner of the fifth aspect, for example including a transceiver unit and a processing unit.
- a storage unit may also be included.
- a chip system in an eleventh aspect, includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the method provided in any one of the above aspects .
- the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the method provided in any one of the foregoing aspects.
- a twelfth aspect provides a first communication system.
- the first communication system includes the communication device described in the sixth aspect or the chip system described in the eleventh aspect (for implementing the first aspect or the method provided by any optional implementation manner of the first aspect) ).
- a thirteenth aspect provides a second communication system.
- the second communication system includes the communication device described in the seventh aspect or the chip system described in the eleventh aspect (for implementing the second aspect or the method provided by any optional implementation manner of the second aspect) ).
- a fourteenth aspect provides a third communication system.
- the second communication system includes the communication device described in the eighth aspect or the chip system described in the eleventh aspect (for implementing the third aspect or the method provided by any optional implementation manner of the third aspect) ), and including the communication device described in the ninth aspect or the chip system described in the eleventh aspect (for implementing the fourth aspect or the method provided by any optional implementation manner of the fourth aspect).
- a fifteenth aspect provides a fourth communication system.
- the second communication system includes the communication device described in the tenth aspect or the chip system described in the eleventh aspect (for implementing the method provided by the fifth aspect or any optional implementation manner of the fifth aspect) ).
- a sixteenth aspect provides a computer-readable storage medium, where the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer is made to execute any of the above-mentioned aspects. method.
- a seventeenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program runs on a computer, the computer is made to execute the method provided in any one of the above aspects .
- Fig. 1 is a kind of schematic diagram of DRX mechanism
- Fig. 2 is a kind of schematic diagram of the time domain position of DCP
- 3 is a schematic diagram of two groups of DRX configurations
- FIG. 4 is a schematic diagram of an application scenario of an embodiment of the present application.
- FIG. 5 is a flowchart of a first communication method provided by an embodiment of the present application.
- FIG. 6 is a schematic diagram illustrating that the monitoring result of the UE at the first DCP monitoring occasion can determine the behavior of the UE on two sets of carriers in an embodiment of the present application;
- FIG. 7 is a schematic diagram of cross-carrier scheduling of network equipment in an embodiment of the present application.
- FIG. 8 is a flowchart of a second communication method provided by an embodiment of the present application.
- FIG. 9 shows that the monitoring result of the UE at the first DCP monitoring occasion can determine the behavior of the UE on the first group of carriers, and the monitoring result of the UE at the second DCP monitoring occasion can determine the UE’s behavior on the second group of carriers. a schematic representation of the behavior of ;
- FIG. 10 is a flowchart of a third communication method provided by an embodiment of the present application.
- 11 is a schematic diagram of the fact that the DCI received by the UE on the first group of carriers can indicate the sleep or wake-up of the UE on the two groups of carriers in the embodiment of the present application;
- FIG. 13 is a schematic diagram illustrating that the duration of the first DRX inactive timer is greater than the duration of the second DRX inactive timer in an embodiment of the present application;
- FIG. 14 is a schematic diagram of setting the duration of the first DRX inactivity timer to the duration of the DRX inactivity timer configured by the second DRX configuration in an embodiment of the application;
- 15 is a schematic diagram of extending the DRX activation time of the UE on the first group of carriers in an embodiment of the application;
- FIG. 16 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
- FIG. 17 is a schematic block diagram of still another communication apparatus provided by an embodiment of the present application.
- a terminal device is a device with a wireless transceiver function, which may be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a wireless device (for example, a communication module or a wireless device) built into the above-mentioned device. system-on-chip, etc.).
- the terminal device is used to connect people, things, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), vehicle-to-everything (vehicle to everything, V2X), machine-to-machine/machine-type communications (M2M/MTC), Internet of things (internet of things, IoT), virtual reality (virtual reality, VR) , Augmented reality (AR), industrial control (industrial control), unmanned driving (self driving), telemedicine (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation , terminal equipment for smart city, drone, robot and other scenarios.
- cellular communication device-to-device communication
- vehicle-to-everything vehicle to everything, V2X
- M2M/MTC machine-to-machine/machine-type communications
- IoT Internet of things
- virtual reality virtual reality
- AR Augmented reality
- the terminal device may sometimes be referred to as a UE, a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment, etc.
- the terminal device is described by taking the UE as an example in the embodiments of the present application. .
- the network devices in the embodiments of the present application include, for example, access network devices and/or core network devices.
- the access network device is a device with a wireless transceiver function, and is used to communicate with the terminal device.
- the access network equipment includes but is not limited to the base station (BTS, Node B, eNodeB/eNB, or gNodeB/gNB), the transmission reception point (TRP), the third generation partnership project (3rd generation partnership project, 3GPP) subsequent evolution base station, access node in WiFi system, wireless relay node, wireless backhaul node, etc.
- the base station may be: a macro base station, a micro base station, a pico base station, a small base station, a relay station, and the like.
- the network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario.
- the network device can also be a server, a wearable device, or a vehicle-mounted device.
- a network device in a vehicle to everything (V2X) technology can be a road side unit (RSU).
- RSU road side unit
- the multiple network devices in the communication system may be base stations of the same type, or may be base stations of different types.
- the base station can communicate with the terminal equipment, and can also communicate with the terminal equipment through the relay station.
- a terminal device can communicate with multiple base stations in different access technologies.
- the core network equipment is used to implement functions such as mobility management, data processing, session management, policy and charging.
- the names of devices implementing core network functions in systems with different access technologies may be different, which are not limited in this application.
- the core network equipment may include an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF) Wait.
- the core network equipment may include a mobility management entity and the like.
- the apparatus for implementing the function of the network device may be the network device, or may be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device.
- the technical solutions provided by the embodiments of the present application are described by taking the device for realizing the function of the network device being a network device as an example.
- network equipment refers to access network equipment.
- the number of nouns means “singular nouns or plural nouns", that is, “one or more”. "At least one” means one or more, and “plurality” means two or more. "And/or”, which describes the relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, it can indicate that A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
- the character “/" generally indicates that the associated objects are an "or” relationship. For example, A/B, means: A or B.
- At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
- at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.
- ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, and timing of multiple objects , priority or importance, etc.
- the first DCI and the second DCI may be the same DCI or different DCIs, and this name does not indicate the time length, transmission order, content, priority or importance of the two DCIs etc. are different.
- the 5G new radio (NR) technology follows the discontinuous reception (DRX) mechanism in the long term evolution (LTE) technology.
- the DRX mechanism is mainly introduced to save power consumption.
- the DRX cycle configured by the base station for the UE may be a long DRX cycle or a short DRX cycle, wherein the long DRX cycle is a default configuration, and the short DRX cycle is an optional configuration. If a UE is configured with a long DRX cycle and is not configured with a short DRX cycle, the UE will use the long DRX cycle or the short DRX cycle at the same moment, that is, the UE will not use both DRX cycles at the same time.
- the UE will start the DRX short cycle timer (drx-ShortCycleTimer) when using the short DRX cycle.
- drx-ShortCycleTimer When the drx-ShortCycleTimer times out, the UE will implicitly switch to using the long DRX cycle.
- the unit of drx-ShortCycleTimer is the number of short DRX cycles.
- the DRX cycle consists of the "On Duration” part and the "DRX Opportunity (Opportunity for DRX)" part.
- the UE monitors and receives the PDCCH.
- the UE may not monitor or receive the PDCCH to reduce power consumption.
- monitoring and receiving the PDCCH can be understood as monitoring and receiving the DCI carried on the PDCCH.
- the DRX mechanism includes a DRX duration timer (drx-onDurationTimer).
- drx-onDurationTimer At the beginning of each DRX cycle (that is, the start of On Duration of each DRX cycle), the UE needs to enable the drx-onDurationTimer. When the drx-onDurationTimer times out, it means that the "On Duration" time ends, and the UE enters the "Opportunity for DRX" time in the DRX cycle.
- the DRX mechanism also includes a DRX inactivity timer (drx-InactivityTimer).
- drx-InactivityTimer DRX inactivity timer
- the DRX mechanism further includes a DRX retransmission timer (drx-RetransmissionTimer), and the drx-RetransmissionTimer is further divided into an uplink drx-RetransmissionTimer and a downlink drx-RetransmissionTimer. Since the base station may schedule the retransmission of the UE during the running time of drx-RetransmissionTimer, the UE needs to monitor and receive the PDCCH during the running time of drx-RetransmissionTimer.
- drx-RetransmissionTimer DRX retransmissionTimer
- the UE needs to monitor and receive PDCCH during the operation of drx-onDurationTimer, drx-InactivityTimer, uplink drx-RetransmissionTimer, and downlink drx-RetransmissionTimer. Therefore, the running time of these timers is considered as the DRX "activation time”.
- the UE needs to wake up and prepare to receive signaling or data within the DRX activation time.
- the UE may not need to monitor and receive the PDCCH at that time. This time is called the DRX "sleep time".
- the UE can sleep.
- the power consumption of the UE during the DRX "active time” is higher than the power consumption during the DRX “sleep time”. It should be noted that in some other functions other than the DRX mechanism, it may also be limited that the UE needs to be in the "active time” or “sleep time” in some cases, which does not conflict with the DRX mechanism, but is a combination of relation. Therefore, whether the UE is actually in the "active time” or the "sleep time” in the end also needs to be determined from the various functions of the UE as a whole.
- CA Carrier aggregation
- cross-carrier scheduling
- the carrier aggregation technology can aggregate multiple (for example, two or more) component carriers (CC) together to achieve the effect of increasing the transmission bandwidth and improving the uplink and downlink transmission rates.
- multiple CCs include one primary carrier and one or more secondary carriers.
- the primary carrier is a carrier operated by a primary cell (primary cell, PCell)
- the secondary carrier is a carrier operated by a secondary cell (secondary cell, SCell).
- the frequency range of 5G NR includes FR1 and FR2.
- FR1 is commonly referred to as the 5G Sub-6GHz (below 6GHz) frequency band
- FR2 is the frequency band greater than or equal to 6GHz, such as the 5G millimeter wave frequency band.
- a carrier configured for the UE may belong to the FR1 frequency band or the FR2 frequency band, so there is a CA scenario of FR1+FR2, that is, there is at least one FR2 CC and FR1 CC for carrier aggregation.
- FR1 may schedule FR2 across carriers, that is, DCI is received on the FR1 carrier, and the DCI schedules data to be received or transmitted on the FR2 carrier.
- UE needs to further save power consumption.
- the UE needs to monitor and receive the PDCCH during the DRX activation time, but in many cases, the UE cannot actually monitor the PDCCH used to schedule the UE during the DRX activation time, so the UE just consumes the monitoring PDCCH in vain power consumption. Therefore, it is proposed to introduce an indication signal (PDCCH-WUS), or a wake-up signal, which can indicate whether the UE needs to wake up or can sleep in the subsequent DRX activation time based on the current DRX mechanism.
- the PDCCH-WUS is also called DCP in the standard, and the signal form of the DCP may be DCI.
- the time domain position of the DCP may be: an offset (offset) position before the "On Duration" time of the DRX cycle, for which reference may be made to FIG. 2 , and the bold vertical line in FIG. 2 represents the DCP.
- the DCP is only configured on the primary carrier, but the wake-up or sleep indicated by the DCP can be applied to all carriers participating in the carrier aggregation.
- carrier and “cell” can be regarded as the same concept without considering the supplementary uplink (SUL, SUL).
- the primary carrier may also be called the primary serving cell, or the primary cell
- the secondary carrier may also be called the secondary serving cell, or the secondary cell.
- a UE in an RRC connected state can support two sets of DRX configurations. All carriers using the first set of DRX configurations belong to one frequency range (FR1), such as FR1, and all carriers using the second set of DRX configurations belong to another frequency range, such as FR2.
- the first group of DRX configurations may be considered as primary (primary) configurations, and the second group of DRX configurations may be considered as secondary (secondary) configurations.
- the second group of DRX configurations may be configured with drx-onDurationTimer and drx-InactivityTimer with shorter timing durations, for example, reference may be made to FIG. 3 .
- drx-onDurationTimer and drx-InactivityTimer with shorter timing durations
- the dotted box represents the duration of the DRX inactive time timer.
- the two sets of DRX configurations can be understood as being maintained and operated independently.
- the carriers belonging to the first frequency range share the first set of DRX configurations to maintain drx-onDurationTimer1 and drx-InactivityTimer1; the carriers belonging to the second frequency range share the first set of DRX configurations.
- other parameters configured in the first DRX configuration may be the same as corresponding parameters configured in the second DRX configuration.
- carriers belonging to the first frequency range share the first set of DRX configurations and maintain drx-RetransmissionTimer 1
- carriers belonging to the first frequency range share the second set of DRX configurations, maintaining drx-RetransmissionTimer 2, and drx-RetransmissionTimer 1 and drx-RetransmissionTimer 2 can have the same duration.
- cross-carrier scheduling, wake-up signal, and two sets of DRX configurations are currently used independently, and these technologies are not used in combination.
- two sets of DRX configurations are used in combination with a wake-up signal, or two sets of DRX configurations are used in combination with cross-carrier scheduling, etc., which are currently not supported, which will affect the flexibility of base station configuration.
- the two sets of DRX configurations are mainly used to reduce the power consumption of the UE on the carrier corresponding to the second set of DRX configurations (such as FR2). Two sets of DRX configurations are used in combination with these techniques to further reduce UE power consumption.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the behavior of the terminal device in the case of combination is specified, for example, the terminal device monitors the DCP monitoring timing corresponding to the first group of carriers
- the situation is applicable to both the first group of carriers and the second group of carriers.
- the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, which reduces the power consumption of the terminal equipment for monitoring the DCP, and also increases the flexibility of network equipment scheduling.
- the monitoring situation of the terminal device on one set of carriers can be applied to the two sets of carriers, so that both sets of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two sets of carriers.
- the technical solutions provided in the embodiments of this application can be applied to 4G systems, such as LTE systems, or can be applied to 5G systems, such as NR systems, or can also be applied to next-generation mobile communication systems or other similar communication systems.
- No restrictions. For example, when a terminal device (such as a smart phone, a smart watch, or a smart bracelet, etc.) has a demand for energy saving, for example, the battery power of the mobile phone is already lower than 20%, the mobile phone has a very strong demand for saving power consumption. In this case, after using the method provided by the embodiment of the present application, the power consumption of the terminal device can be further reduced, that is, the consumed battery power can be reduced, and the standby time of the terminal device can be prolonged.
- FIG. 4 is an application scenario of the embodiment of the present application.
- FIG. 4 includes an access network device, a core network device, and a UE, and the access network device may configure one or more carriers for the UE.
- the access network device works in the evolved Universal Mobile Telecommunications System Terrestrial Radio Access (Evolved UMTS terrestrial radio access, E-UTRA) system, or works in the NR system, or works in the next generation communication system or other communication systems middle.
- the access network device is, for example, a base station.
- the access network equipment corresponds to different equipment in different systems, for example, in a 4G system, it may correspond to an eNB, and in a 5G system, it corresponds to an access network equipment in 5G, such as a gNB.
- the technical solutions provided in the embodiments of the present application can also be applied to future mobile communication systems, so the access network devices in FIG. 4 can also correspond to network devices in future mobile communication systems.
- FIG. 4 takes the access network device being a base station as an example.
- the access network device may also be a device such as an RSU.
- the UE in FIG. 4 takes a mobile phone as an example.
- the UE in the embodiment of the present application is not limited to the mobile phone.
- each of the embodiments to be introduced later is taken as an example to be applied to the architecture shown in FIG. 4 .
- the network device described in the following embodiments is, for example, an access network device in the network architecture shown in FIG. 4
- the UE described in the following embodiments may be the network architecture shown in FIG. 4 .
- UE UE.
- FIG. 5 is a flowchart of the method.
- the UE determines whether to monitor the DCP in the first DCP monitoring opportunity, or in other words, the UE determines whether to monitor the first DCP monitoring opportunity.
- the network device sends the first DRX configuration and the second DRX configuration to the UE
- the UE is equivalent to being configured with the first DRX configuration and the second DRX configuration.
- the network device may send the first DRX configuration and the second DRX configuration to the UE through one message, or the network device may send the first DRX configuration and the second DRX configuration to the UE respectively through different messages.
- the first group of carriers applies the first DRX configuration
- the second group of carriers applies the second DRX configuration
- the first group of carriers includes one or more carriers configured with the UE
- the second group of carriers also includes one or more carriers configured with the UE. carrier.
- the first DRX configuration can configure DRX cycle, DRX duration timer, DRX inactivity timer, and DRX retransmission timer, etc.
- the second DRX configuration can also configure DRX cycle, DRX inactivation timer, and DRX retransmission timer, etc.
- the first DRX configuration and the second DRX configuration are different DRX configurations.
- the DRX duration timer configured in the first DRX configuration is different from the DRX duration timer configured in the second DRX configuration.
- the duration (or referred to as the timing duration) of the DRX duration timer configured by the DRX configuration is different from the duration of the DRX duration timer configured by the second DRX configuration.
- the DRX inactivation timer configured in the first DRX configuration is different from the DRX inactivation timer configured in the second DRX configuration, for example, the duration of the DRX inactivation timer configured in the first DRX configuration (or (referred to as timing duration) is different from the duration of the DRX inactivity timer configured by the second DRX configuration.
- Other contents configured in the first DRX configuration and the second DRX configuration except the DRX duration timer and the DRX inactivity timer, such as the DRX cycle or the DRX retransmission timer, may be the same or different.
- the first group of carriers belongs to the first frequency range
- the second group of carriers belongs to the second frequency range
- the first frequency range and the second frequency range may be different frequency ranges.
- the frequency of the second frequency range is greater than the frequency of the first frequency range
- the minimum frequency included in the second frequency range is greater than the maximum frequency included in the first frequency range
- the first frequency range is FR1
- the second frequency range is FR2.
- the network device configures the carrier for the UE, it may not distinguish which carrier belongs to which group, that is, the concepts of "first group” and "second group” may not exist.
- the descriptions of "the first group of carriers" and "the second group of carriers” are used here to distinguish carriers using different DRX configurations.
- the first DCP monitoring occasion is a DCP monitoring occasion configured on the first group of carriers, and the first DCP monitoring occasion applies the first DRX configuration.
- the DCP monitoring timing may occur multiple times.
- a DCP monitoring timing may occur before each DRX cycle starts.
- the first DCP monitoring occasion is, for example, the current monitoring occasion for the UE, for example, the first DCP monitoring occasion is located before the On Duration time of a DRX cycle under the first DRX configuration starts, or in other words, the first DCP monitoring occasion Before the On Duration time of one DRX cycle on the first set of carriers.
- the first DCP monitoring occasion may include one or more DCP monitoring occasions. It can be understood that one DCP monitoring occasion may include one or more DCP monitoring occasions, and the first DCP monitoring occasion is one DCP monitoring occasion.
- the network device may send the DCP on the first carrier, and the first carrier belongs to the first group of carriers. For example, if the network device configures DCP for one or more carriers included in the first group of carriers, then the first carrier includes the one or more carriers. For another example, if the primary carrier configured by the network device for the UE belongs to the first group of carriers, the network device can configure the DCP for the primary carrier, then the first carrier is the primary carrier of the UE, and the network device can send the DCP on the primary carrier without requiring Configure DCP on other carriers to save transmission overhead.
- the UE needs to monitor on the first group of carriers, it can monitor on all the carriers included in the first group of carriers, or on which carriers the network device sends the DCP can be pre-configured, and the UE only needs to monitor on these carriers.
- the network device does not configure the DCP for the second group of carriers, so the network device does not need to send the DCP on the second group of carriers, and the UE does not need to monitor the DCP on the second group of carriers.
- the first determination method is determined according to the time domain position of the first DCP listening opportunity.
- the UE determines whether the time domain position of the first DCP listening opportunity is within the first DRX activation time, and if the time domain position of the first DCP listening opportunity is within the first DRX activation time, it indicates that the UE is within the first DCP listening opportunity There may be data transmission on the first group of carriers (for example, the UE needs to receive data or send data on the first group of carriers), then in this case, the UE may not monitor at the first DCP monitoring opportunity, but may On the group carrier, wake up within the DRX duration associated with the first DCP listening opportunity.
- the UE may monitor at the first DCP monitoring occasion. All the time domain positions corresponding to the first DCP monitoring occasion include the time domain positions of all the DCP monitoring occasions included in the first DCP monitoring occasion. At this time, the UE may perform monitoring in all the DCP monitoring occasions included in the first DCP monitoring occasion.
- the UE may not monitor within the DCP monitoring opportunity included in the first DCP monitoring opportunity and within the first DRX activation time, and For the DCP monitoring occasions included in the first DCP monitoring occasion that are not within the first DRX activation time, the UE can still monitor. That is, in this case, the UE does not monitor in some of the DCP listening opportunities included in the first DCP listening opportunity, but monitors in the remaining DCP listening opportunities included in the first DCP monitoring opportunity, so this situation also It can be considered that the UE is monitoring in the first DCP monitoring opportunity.
- the partial time domain position corresponding to the first DCP monitoring occasion includes the time domain position of the partial DCP monitoring occasion included in the first DCP monitoring occasion.
- the first DRX activation time is the DRX activation time corresponding to the first DRX configuration, and the first DRX activation time is located on the first group of carriers.
- This determination method is relatively easy to implement for the UE.
- the second determination method Determined according to the DCI size budget.
- DCI size budget that is, the maximum number of DCI sizes that the UE can monitor is limited. For example, it is stipulated that the maximum number of DCI sizes that the UE can monitor is 4, then the UE can monitor up to 4 types of DCI sizes, and if there is a fifth type of DCI size, the UE cannot monitor.
- DCP is regarded as a DCI of size. How many DCI sizes the UE needs to monitor in total can be configured by the network device to the UE. Then the UE can determine whether it needs to The DCP is monitored during the first DCP monitoring opportunity.
- the UE can monitor the first DCP within the time. Monitoring is performed, because even if the UE monitors the DCP at this time, it can meet the requirements of the DCI size budget.
- the UE may not monitor within the first DCP monitoring opportunity, because at this time, if the UE monitors the DCP, it will exceed If the DCI size budget is exceeded, it may cause errors in the monitoring behavior of the UE.
- the maximum number of DCI sizes that the UE can monitor is 4, the number of DCI sizes that the UE needs to monitor is 3, and the DCI that the UE needs to monitor does not include DCP, then the UE can monitor the DCP in the first DCP monitoring opportunity;
- the maximum number of DCI sizes that the UE can monitor is 4, and the number of DCI sizes that the UE needs to monitor is 4, then the UE does not monitor the DCP in the first DCP monitoring opportunity.
- the UE can monitor the first DCP timing. If the maximum number of DCI sizes that the UE can monitor is less than the number of DCI sizes that the UE needs to monitor, the UE may not monitor in the first DCP monitoring opportunity.
- the maximum number of DCI sizes that the UE can monitor is 4, the number of DCI sizes that the UE needs to monitor is 4, and the DCI that the UE needs to monitor includes DCP, then the UE can monitor the DCP in the first DCP monitoring opportunity; or , the maximum number of DCI sizes that the UE can monitor is 4, the number of DCI sizes that the UE needs to monitor is 5, and the DCI that the UE needs to monitor includes DCP, then the UE does not monitor DCP in the first DCP monitoring opportunity.
- the DCI size budget is used to determine whether to monitor the first DCP monitoring timing, so that the monitoring behavior of the UE can meet the requirements of the DCI size budget, and the monitoring of the UE is more flexible.
- the third determination method determine according to the time domain position of the first DCP listening opportunity and the DCI size budget.
- the UE determines the maximum number of DCI sizes that the UE can monitor and the number of DCI sizes that the UE needs to monitor. If the maximum number of DCI sizes that the UE can monitor is greater than or equal to the number of DCI sizes that the UE needs to monitor (the DCP is regarded as the DCI that the UE needs to monitor), the UE determines whether the time domain position of the first DCP monitoring opportunity is located at within the first DRX activation time.
- the UE If the time domain position of the first DCP listening opportunity is within the first DRX activation time, the UE does not monitor the DCP within the first DCP listening opportunity, or if the time domain position of the first DCP listening Within the DRX activation time, the UE monitors the DCP in the first DCP monitoring opportunity.
- the UE may not need to determine the time domain position of the first DCP monitoring opportunity , but it can be determined that the UE does not monitor the DCP in the first DCP monitoring occasion.
- the UE determines whether the time domain position of the first DCP listening opportunity is within the first DRX activation time, and if the time domain position of the first DCP listening opportunity is not within or partially within the first DRX activation time, the UE determines that the UE has the most The number of DCI sizes that can be monitored and the number of DCI sizes that the UE needs to monitor.
- the UE monitors the DCP in the first DCP monitoring opportunity, or, If the maximum number of DCI sizes that the UE can monitor is less than the number of DCI sizes that the UE needs to monitor, the UE does not monitor DCPs in the first DCP monitoring opportunity.
- the UE may not need to determine the maximum number of DCI sizes that the UE can monitor and the number of DCI sizes that the UE needs to monitor, but It may be determined that the UE does not monitor the DCP in the first DCP monitoring occasion.
- the third determination method is equivalent to using the first determination method in combination with the second determination method, which can make the determination result more reasonable.
- the UE can determine it by itself, or it can be configured by a network device, or it can also be specified by a protocol.
- the UE may not have a process of determining whether to monitor the DCP monitoring timing. For example, for the embodiment shown in FIG. 5 , the UE may not perform S51. For example, if the time domain position of the first DCP listening opportunity is within the first DRX activation time, the UE does not monitor at the first DCP listening opportunity, or all the time domain positions corresponding to the first DCP monitoring opportunity are not located in the first DCP monitoring opportunity. In the case of the first DRX activation time, the UE monitors at the first DCP monitoring opportunity, or if the partial time domain position corresponding to the first DCP monitoring opportunity is not within the first DRX activation time, the UE is not in the first DRX activation time.
- the first DCP monitoring opportunity includes monitoring within the DCP monitoring opportunity within the first DRX activation time, while monitoring is performed within the DCP monitoring opportunity included in the first DCP monitoring opportunity that is not within the first DRX activation time.
- the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, then the UE monitors in the first DCP monitoring opportunity, and the UE can monitor the most DCI sizes. If the number of sizes is less than or equal to the number of DCI sizes that the UE needs to monitor, the UE does not monitor in the first DCP monitoring opportunity.
- various embodiments of the present application take the UE having a determination process as an example.
- S51 may be replaced with the UE determining whether the time domain position of the first DCP listening opportunity is within the first DRX activation time.
- S51 can be replaced with, the UE determines whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor.
- S51 can also be replaced correspondingly according to the third determination manner above.
- the UE determines not to monitor within the first DCP listening opportunity, the UE wakes up within the first DRX duration associated with the first DCP monitoring opportunity, and wakes up within the second DRX duration associated with the first DCP monitoring opportunity or hibernate. In other words, if the UE does not listen in the first DCP listening occasion, then on the first set of carriers, the UE wakes up within the first DRX duration associated with the first DCP listening occasion, and on the second set of carriers, the UE wakes up within the first DRX duration associated with the first DCP listening occasion. The UE wakes up or sleeps within the second DRX duration associated with the first DCP listening opportunity.
- S52 can also be replaced with, if the time domain position of the first DCP monitoring opportunity is within the first DRX activation time, the UE is in the first DCP monitoring opportunity. Wake up within the associated first DRX duration, and wake up or sleep within the second DRX duration associated with the first DCP listening opportunity.
- S52 can also be replaced with, if the number of DCI sizes that the UE can monitor at most is less than or equal to the number of DCI sizes that the UE needs to monitor, the UE is in Wake up within the first DRX duration associated with the first DCP listening opportunity, and wake up or sleep within the second DRX duration associated with the first DCP listening opportunity.
- S51 is replaced according to the third determination method above, then S52 can also be replaced accordingly.
- the first DCP listening occasion may be associated with one or more DRX cycles.
- the DRX cycle associated with the first DCP listening opportunity is later than the first DCP listening opportunity in the time domain, and if the first DCP listening opportunity is associated with multiple DRX cycles, the multiple DRX cycles may be continuous in the time domain, or not. continuous.
- the first DRX duration corresponds to the first DRX configuration, and the first DRX duration is on the first group of carriers.
- the first DRX duration may include the On Duration time in all or part of the DRX cycle associated with the first DCP listening opportunity under the first DRX configuration, or, in other words, the first DRX duration may include, on the first group of carriers, the first The On Duration time in all or part of the DRX cycle associated with a DCP listening opportunity. If the UE determines not to monitor within the first DCP monitoring opportunity, the UE does not monitor within the first DCP monitoring opportunity. In this case, in order to reduce the probability that the UE misses the PDCCH that the network device may send on the first group of carriers, the UE may wake up within the first DRX duration.
- the first DCP listening opportunity may also be associated with one or more DRX cycles. Because the first DCP listening opportunity is not configured on the second set of carriers, the association is a time-domain positional association, eg, on the second set of carriers, a time-domain later than the first DCP listening opportunity or multiple DRX cycles may be associated with the first DCP listening opportunity. In addition, if the first DCP listening opportunity is associated with multiple DRX cycles, the multiple DRX cycles may or may not be continuous in the time domain. Additionally, the second DRX duration corresponds to a second DRX configuration, and the second DRX duration is on a second set of carriers.
- the second DRX duration may include the On Duration time in all or part of the DRX cycle associated with the first DCP listening opportunity under the second DRX configuration.
- the second DRX duration may include the first DCP on the second group of carriers.
- the On Duration time in all or part of the DRX cycle associated with the listening opportunity.
- the UE can sleep within the second DRX duration associated with the first DCP listening opportunity to save the power consumption of the UE; or, By default (or, as specified by the protocol), if the UE determines not to monitor within the first DCP listening opportunity, the UE may wake up within the second DRX duration associated with the first DCP listening opportunity, so as to reduce the UE missing the network device in the second group. The probability of data that may be sent on the carrier.
- the behavior of the UE on the second group of carriers is specified by default or through a protocol, and no additional configuration of the network device is required, nor is it required for the UE to determine by other means, which can simplify the implementation of the network device and the UE.
- the UE sleeps or wakes up within the second DRX duration, which may also be instructed by the network device.
- the network device sends configuration information to the UE, and accordingly, the UE receives the configuration information from the network device, and the configuration information may be sent, for example, through an RRC message, a system message, or other messages.
- the configuration information may be sent on one or more carriers included in the first group of carriers.
- the primary carrier configured by the network device for the UE belongs to the first group of carriers, and the configuration information may be sent on the primary carrier; or, the configuration Information may also be sent on one or more carriers included in the second set of carriers.
- the configuration information can be configured: when the UE does not monitor in the DCP monitoring occasion, the UE wakes up on the second group of carriers within the DRX duration associated with the DCP monitoring occasion; or, the configuration information can be configured: in the UE In the case of not listening within the DCP listening opportunity, the UE sleeps on the second group of carriers for the DRX duration associated with the DCP listening opportunity. In this case, the network device can configure the UE to sleep or wake up on the second group of carriers through configuration information according to factors such as data transmission.
- the network device may instruct the UE to wake up through the configuration information, and if the network device does not schedule the UE to send data and data during the DRX cycle associated with the first DCP listening opportunity on the second group of carriers After receiving the data, the network device may instruct the UE to sleep through the configuration information. In this way, the sleep or wake-up of the UE can be made to meet the data transmission requirement.
- the UE determines sleep or wake-up on the first group of carriers and sleep or wake-up on the second group of carriers according to the monitoring situation.
- S53 can also be replaced with, if all or part of the time domain positions corresponding to the first DCP monitoring opportunity are not located within the first DRX activation time, the UE is in the first DRX activation time.
- the DCP is monitored in the first DCP monitoring opportunity, and according to the monitoring situation, sleep or wake-up on the first group of carriers is determined, and sleep or wake-up on the second group of carriers is determined.
- S53 can also be replaced with, if the number of DCI sizes that the UE can monitor at most is greater than the number of DCI sizes that the UE needs to monitor, the UE is in the first
- the DCP is monitored during the monitoring time of the DCP, and according to the monitoring situation, sleep or wake-up on the first group of carriers is determined, and sleep or wake-up on the second group of carriers is determined.
- S53 can also be replaced accordingly.
- the UE monitors during the first DCP monitoring opportunity, and determines the first set of carriers and the second set of carriers according to the monitoring of the DCP during the first DCP monitoring opportunity.
- Dormancy or wake-up on the UE that is, the monitoring situation of the UE in the first DCP monitoring occasion, can determine the behavior of the UE on the first group of carriers, and can also determine the behavior of the UE on the second group of carriers.
- the oblique rectangle in FIG. 6 represents the first DCP monitoring timing, and the DCP monitoring timing is not configured on FR2.
- the UE’s monitoring situation at the first DCP monitoring timing can determine whether the UE is on the first group of carriers.
- the behavior on the UE can also determine the behavior of the UE on the second group of carriers.
- the DCP is implemented in that, if the network device sends the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device does not send the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP sleep inside. For the UE, if the DCP is monitored and received, it wakes up in the DRX cycle associated with the DCP, and if it does not monitor the DCP, it sleeps in the DRX cycle associated with the DCP.
- the DCP adopts this implementation manner, then, if the UE receives the DCP from the network device within the first DCP listening opportunity, the UE is on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity Wake up, and the UE wakes up on the second group of carriers within the second DRX duration associated with the first DCP listening opportunity; and if the UE does not receive a DCP from the network device within the first DCP listening opportunity, the UE is On the first group of carriers, the UE sleeps for the first DRX duration associated with the first DCP listening opportunity, and the UE sleeps on the second group of carriers for the second DRX duration associated with the first DCP listening opportunity.
- the DCP is implemented in that the DCP includes indication information, and if the network device sends the DCP, and the indication information included in the DCP indicates wake-up, the UE is instructed to wake up within the DRX cycle associated with the DCP, If the network device sends the DCP, and the indication information included in the DCP indicates dormancy, the UE is instructed to sleep within the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, and the indication information included in the DCP indicates wake-up, the UE wakes up within the DRX cycle associated with the DCP.
- the UE sleeps within the DRX cycle associated with the DCP. If the DCP adopts this implementation manner, then, if the UE receives the DCP from the network device within the first DCP listening opportunity, and the indication information included in the DCP indicates wake-up, the UE is on the first group of carriers and the first DCP Wake up within the first DRX duration associated with the listening opportunity, and, on the second set of carriers, the UE wakes up within the second DRX duration associated with the first DCP listening opportunity; and if the UE receives within the first DCP listening opportunity
- the DCP from the network device, and the indication information included in the DCP indicates dormancy, the UE sleeps on the first group of carriers for the first DRX duration associated with the first DCP listening opportunity, and the UE sleeps on the second group of carriers , sleep within the second DRX duration associated with the first DCP listening opportunity.
- the DCP is implemented in that the DCP includes first indication information and second indication information, the first indication information corresponds to the first group of carriers, or corresponds to the first DRX configuration, and the second indication information Corresponds to the second group of carriers, or corresponds to the second DRX configuration. If the network device sends the DCP, and the first indication information included in the DCP indicates wake-up, the UE is instructed to wake up within the DRX cycle under the first DRX configuration associated with the DCP. When the indication information indicates dormancy, the UE is instructed to sleep within the DRX cycle under the first DRX configuration associated with the DCP.
- the indication manner of the second indication information is also similar.
- the UE For the UE, if the DCP is monitored and received, and the first indication information included in the DCP indicates wake-up, the UE wakes up within the DRX cycle under the first DRX configuration associated with the DCP, if the DCP is monitored and received, and the The first indication information included in the DCP indicates dormancy, and the UE sleeps within the DRX cycle under the first DRX configuration associated with the DCP.
- the UE understands the second indication information in a similar manner. If the DCP adopts this implementation manner, then, if the UE receives the DCP from the network device within the first DCP monitoring opportunity, and the first indication information included in the DCP indicates wake-up, the UE is on the first group of carriers and is on the first set of carriers.
- the UE Wake up within the first DRX duration associated with a DCP listening opportunity; and if the UE receives a DCP from the network device within the first DCP listening opportunity, and the first indication information included in the DCP indicates dormancy, the UE is in the first group On the carrier, sleep within the first DRX duration associated with the first DCP listening opportunity. Similarly, if the UE receives a DCP from the network device within the first DCP listening opportunity, and the second indication information included in the DCP indicates wake-up, then the UE is on the second group of carriers at the first DCP monitoring opportunity associated with the first DCP.
- the UE Wake up within two DRX durations; and if the UE receives a DCP from the network device within the first DCP monitoring opportunity, and the second indication information included in the DCP indicates dormancy, the UE is on the second group of carriers and the first DCP Sleep within the second DRX duration associated with the listening opportunity.
- the DCP can indicate sleep or wake-up in different DRX durations through different indication information.
- the network device can determine whether the corresponding indication information indicates wake-up or sleep according to the information transmission on the two sets of carriers. The sleep or wake-up behavior of the UE is more in line with the service transmission requirements.
- the DCP is implemented in that the two groups of carriers have corresponding DCPs, for example, a carrier group identifier may be included in the DCP to distinguish DCPs of different carrier groups, or DCPs of different carrier groups.
- the format is different. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates wake-up, the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP. The DCP corresponding to the group of carriers, and the DCP indicates dormancy, the UE is instructed to sleep on the group of carriers within the DRX cycle associated with the DCP.
- the DCP adopts this implementation, then, if the UE receives the DCP from the network device within the first DCP listening opportunity, and the DCP corresponds to the first group of carriers, if the DCP indicates wake-up, the UE is on the first group of carriers , wake up within the first DRX duration associated with the first DCP listening opportunity, or, if the DCP indicates dormancy, the UE sleeps on the first group of carriers within the first DRX duration associated with the first DCP listening opportunity .
- the operation procedures of the network device and the UE are also the same.
- the DCP is implemented in that two groups of carriers have corresponding DCPs, for example, a carrier group identifier may be included in the DCP to distinguish DCPs of different carrier groups, or DCPs of different carrier groups.
- the format is different. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP. If the network device does not send the DCP corresponding to the group of carriers, Then the UE is instructed to sleep within the DRX cycle associated with the DCP on the carrier group.
- the DCP adopts this implementation manner, then, if the UE receives the DCP from the network device in the first DCP listening opportunity, and the DCP corresponds to the first group of carriers, the UE is on the first group of carriers and the first DCP Wake up within the first DRX duration associated with the listening opportunity, or, if the UE does not receive a DCP corresponding to the first group of carriers from the network device within the first DCP listening opportunity, the UE is on the first group of Sleep within the first DRX duration associated with a DCP listening opportunity.
- the operation procedures of the network device and the UE are also the same.
- the UE sleeps within the first DRX duration, which may be implemented in the following manner: the UE neither starts nor restarts the first DRX duration timer at the start time of the first DRX duration.
- the first DRX duration timer is configured by the first DRX configuration, and the first DRX duration timer corresponds to the first group of carriers. If the first DRX duration timer is not started, the UE does not start the first DRX duration timer at the start moment of the first DRX duration, and if the first DRX duration timer is running, the UE starts at the first DRX duration timer.
- the first DRX duration timer is not restarted at the starting moment of a DRX duration, so that the UE can sleep within the first DRX duration.
- the implementation manner of the UE sleeping within the second DRX duration is also similar, for example, it is implemented in the following manner: the UE neither starts nor restarts the second DRX duration timer at the start time of the second DRX duration.
- the second DRX duration timer is configured by the second DRX configuration, and the second DRX duration timer corresponds to the second group of carriers.
- the UE wakes up within the first DRX duration, which may be implemented in the following manner: the UE starts or restarts the first DRX duration timer at the start moment of the first DRX duration. If the first DRX duration timer is not started, the UE starts the first DRX duration timer at the start moment of the first DRX duration, and if the first DRX duration timer is running, the UE starts at the first DRX duration timer The first DRX duration timer is restarted at the start time of the DRX duration, so that the UE can wake up within the first DRX duration.
- the implementation manner of the UE waking up within the second DRX duration is also similar, for example, implemented in the following manner: the UE starts or restarts the second DRX duration timer at the start time of the second DRX duration.
- the second DRX duration timer is configured by the second DRX configuration, and the second DRX duration timer corresponds to the second group of carriers.
- S52 and S53 are two parallel schemes, and the two will not be executed at the same time.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the behavior of the terminal device in the combination is specified.
- the behavior of the terminal device on the second group of carriers can be specified by default, protocol specification or network configuration;
- the monitoring of the DCP monitoring occasions corresponding to the first group of carriers by the terminal device is applicable to both the first group of carriers and the second group of carriers.
- the terminal equipment only needs to monitor the DCP on the first group of carriers, and does not need to monitor the DCP on the second group of carriers, which reduces the power consumption of the terminal equipment for monitoring the DCP, and also increases the flexibility of network equipment scheduling.
- the monitoring situation of the terminal device on one set of carriers can be applied to the two sets of carriers, so that both sets of carriers can use the DCP mechanism, which can further reduce the power consumption of the terminal device on the two sets of carriers.
- the network device does not need to configure DCP for the second group of carriers, which can also save signaling overhead.
- FIG. 8 is a flowchart of the method.
- the UE determines whether to monitor the DCP in the first DCP monitoring opportunity, or in other words, the UE determines whether to monitor the first DCP monitoring opportunity.
- S81 may also be replaced by the UE determining whether the time domain position of the first DCP listening opportunity is within the first DRX activation time.
- S81 may also be replaced by the UE determining whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor.
- S81 may also be replaced correspondingly according to the third determination manner described in the embodiment shown in FIG. 5 .
- S81 For more content of S81, such as how the UE determines whether to perform monitoring in the first DCP monitoring opportunity, reference may be made to S51 in the embodiment shown in FIG. 5 .
- the UE determines sleep or wake-up on the first group of carriers and sleep or wake-up on the second group of carriers according to the monitoring situation.
- S81 determines whether the time domain position of the first DCP listening opportunity is within the first DRX activation time
- S82 may be replaced with, if all or part of the time domain position corresponding to the first DCP listening opportunity is not within the first DRX activation time.
- the UE monitors the DCP in the first DCP monitoring opportunity, and determines sleep or wake-up on the first group of carriers and sleep or wake-up on the second group of carriers according to the monitoring situation.
- the UE determines whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor, then S82 can be replaced with, if the maximum number of DCI sizes that the UE can monitor is greater than The number of DCI sizes that the UE needs to monitor, the UE monitors the DCP in the first DCP monitoring opportunity, and determines sleep or wake-up on the first group of carriers according to the monitoring situation, and determines the sleep or wake-up on the second group of carriers. wake.
- S81 is replaced correspondingly according to the third determination manner described in the embodiment shown in FIG. 5
- S82 can also be replaced correspondingly according to S81.
- the network device may send the DCP on the first carrier, and the first carrier belongs to the first group of carriers.
- the first carrier includes the one or more carriers.
- the primary carrier configured by the network device for the UE belongs to the first group of carriers
- the network device can configure the DCP for the primary carrier, then the first carrier is the primary carrier of the UE, and the network device can send the DCP on the primary carrier without requiring Configure DCP on other carriers to save transmission overhead.
- the UE needs to monitor on the first group of carriers, it can monitor on all the carriers included in the first group of carriers, or on which carriers the network device sends the DCP can be pre-configured, and the UE only needs to monitor on these carriers.
- the network device may send the DCP on the second carrier, which belongs to the second group of carriers. For example, if the network device configures DCP for one or more carriers included in the second group of carriers, then the second carrier includes the one or more carriers. If the UE needs to monitor on the second group of carriers, it can monitor on all the carriers included in the second group of carriers, or on which carriers the network device sends the DCP can be pre-configured, and the UE only needs to monitor on these carriers. That is to say, in this embodiment of the present application, the network device is configured with DCP for the first group of carriers, and is also configured with DCP for the second group of carriers.
- the UE first determines whether to perform monitoring on the first group of carriers. If the first group of carriers can be monitored, the UE monitors on the first group of carriers. , for example, monitoring in the first DCP monitoring opportunity, and determining sleep or wake-up on the first group of carriers and the second group of carriers according to the monitoring result. In this case, the UE does not need to listen on the second set of carriers, eg, the UE does not listen during the second DCP listening occasion.
- the second DCP monitoring opportunity is the DCP monitoring opportunity configured on the second group of carriers, and the second DCP monitoring opportunity applies the second DRX configuration.
- the DCP monitoring timing may also occur multiple times. For example, a DCP monitoring timing may occur before each DRX cycle starts. Then, the second DCP monitoring occasion is, for example, the current monitoring occasion for the UE, for example, the second DCP monitoring occasion is located before the On Duration time of a DRX cycle under the second DRX configuration, or the second DCP monitoring occasion Before the start of the On Duration time of one DRX cycle on the second set of carriers. In the case that the UE can monitor on the first group of carriers, since the UE does not need to monitor on the second group of carriers, the power consumption of the UE due to the monitoring can be reduced.
- S82 For more content of S82, such as how the UE determines sleep or wake-up on the first group of carriers and the second group of carriers according to the monitoring situation, please refer to S53 in the embodiment shown in FIG. 5 .
- the time domain positions of the first DCP monitoring occasion and the second DCP monitoring occasion may be the same, or the time domain position of the first DCP monitoring occasion may be earlier than the time domain position of the second DCP monitoring occasion, so when referring to S52,
- the second DRX duration associated with the first DCP listening opportunity described in S52 may also be regarded as the DRX duration associated with the second DCP listening opportunity on the second group of carriers in this embodiment of the present application.
- the UE determines whether to monitor the DCP in the second DCP monitoring opportunity, or in other words, the UE determines whether to monitor in the second DCP monitoring opportunity.
- S81 is replaced with the UE determining whether the time domain position of the first DCP listening opportunity is within the first DRX activation time
- S83 may be replaced with, if the time domain position of the first DCP listening opportunity is within the first DRX activation time, The UE determines whether to monitor the DCP in the second DCP monitoring opportunity, or in other words, the UE determines whether to monitor the second DCP monitoring opportunity.
- S81 is replaced with the UE determining whether the maximum number of DCI sizes that the UE can monitor is greater than the number of DCI sizes that the UE needs to monitor
- S83 can be replaced with, if the maximum number of DCI sizes that the UE can monitor is less than or Equal to the number of DCI sizes that the UE needs to monitor, the UE determines whether to monitor the DCP in the second DCP monitoring opportunity, or in other words, the UE determines whether to monitor the second DCP monitoring opportunity.
- S81 is correspondingly replaced according to the third determination manner described in the embodiment shown in FIG. 5
- S83 may also be correspondingly replaced according to S81.
- the UE determines whether to perform monitoring in the second DCP monitoring opportunity, and can also perform corresponding replacement.
- the specific replacement method please refer to the introduction to the replacement method in S81.
- the manner in which the UE determines whether to perform monitoring in the second DCP monitoring occasion is similar to the manner in which the UE determines whether to perform monitoring in the first DCP monitoring occasion.
- the UE can wake up on the first group of carriers within the first DRX duration to avoid missing the PDCCH.
- the UE determines to monitor within the second DCP monitoring opportunity, the UE determines to sleep or wake up on the second group of carriers according to the monitoring situation.
- the UE determines to perform monitoring in the second DCP monitoring opportunity, and can also perform corresponding replacement.
- the specific replacement method please refer to the introduction to the replacement method of S82.
- the UE may monitor during the second DCP listening opportunity, and at this time, the monitoring result of the second DCP listening opportunity can be used to determine whether the UE sleeps or wakes up on the second group of carriers.
- the rectangular frame drawn with " ⁇ " represents the first DCP monitoring timing
- the rectangular frame drawn with "/" represents the second DCP monitoring timing.
- the UE can determine sleep or wake up on the first group of carriers and sleep or wake up on the second group of carriers according to the monitoring situation of the first DCP monitoring opportunity; if the UE If the first DCP monitoring opportunity cannot be monitored, but the second DCP monitoring opportunity can be monitored, the UE can determine whether to sleep or wake up on the second group of carriers according to the monitoring situation of the second DCP monitoring opportunity.
- the DCP is implemented in that, if the network device sends the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP, and if the network device does not send the DCP, the UE is instructed to wake up in the DRX cycle associated with the DCP sleep inside. For the UE, if the DCP is monitored and received, it wakes up in the DRX cycle associated with the DCP, and if it does not monitor the DCP, it sleeps in the DRX cycle associated with the DCP.
- the DCP adopts this implementation, then, if the UE receives the DCP from the network device within the second DCP listening opportunity, the UE is on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity Wake up; and if the UE does not receive the DCP from the network device within the second DCP listening opportunity, the UE sleeps on the second group of carriers for the second DRX duration associated with the second DCP listening opportunity.
- the DCP is implemented in that the DCP includes indication information, and if the network device sends the DCP, and the indication information included in the DCP indicates wake-up, the UE is instructed to wake up within the DRX cycle associated with the DCP, If the network device sends the DCP, and the indication information included in the DCP indicates dormancy, the UE is instructed to sleep within the DRX cycle associated with the DCP. For the UE, if the DCP is monitored and received, and the indication information included in the DCP indicates wake-up, the UE wakes up within the DRX cycle associated with the DCP.
- the UE sleeps within the DRX cycle associated with the DCP. If the DCP adopts this implementation manner, then, if the UE receives the DCP from the network device within the second DCP listening opportunity, and the indication information included in the DCP indicates wake-up, the UE is on the second group of carriers and the second DCP Wake up within the second DRX duration associated with the listening opportunity; and if the UE receives a DCP from the network device within the second DCP listening opportunity, and the DCP indicates dormancy, the UE monitors the second DCP on the second group of carriers Sleep for the second DRX duration associated with the opportunity.
- the monitoring result of the second DCP monitoring occasion is not used to determine the sleep or wake-up of the UE on the first group of carriers.
- the DCP is implemented in that the DCP includes third indication information and fourth indication information, the third indication information corresponds to the first group of carriers, or corresponds to the first DRX configuration, and the fourth indication information Corresponds to the second group of carriers, or corresponds to the second DRX configuration. If the network device sends the DCP, and the third indication information included in the DCP indicates wake-up, the UE is instructed to wake up within the DRX cycle under the first DRX configuration associated with the DCP.
- the third indication information indicates dormancy, indicating that the UE is dormant within the DRX cycle under the first DRX configuration associated with the DCP.
- the indication manner of the fourth indication information is also similar.
- the UE For the UE, if the DCP is monitored and received, and the third indication information included in the DCP indicates wake-up, the UE wakes up within the DRX cycle under the first DRX configuration associated with the DCP, if the DCP is monitored and received, and the The third indication information included in the DCP indicates dormancy, and the UE sleeps within the DRX cycle under the first DRX configuration associated with the DCP.
- the UE understands the fourth indication information in a similar manner. If the DCP adopts this implementation manner, the monitoring result of the second DCP monitoring occasion can be used to decide whether the UE sleeps or wakes up on the second group of carriers, and can also be used to decide whether the UE sleeps or wakes up on the first group of carriers.
- the UE receives a DCP from the network device within the second DCP listening opportunity, and the third indication information included in the DCP indicates wake-up, the UE is on the first group of carriers and is on the first DCP listening opportunity (or in other words, The second DCP listening opportunity) wakes up within the first DRX duration associated with On a group of carriers, sleep within the first DRX duration associated with the first DCP listening opportunity (or, in other words, the second DCP listening opportunity).
- the UE receives a DCP from the network device within the second DCP listening opportunity, and the fourth indication information included in the DCP indicates wake-up, then the UE is on the second group of carriers and is on the second DCP monitoring opportunity associated with the first DCP.
- the UE Wake up within two DRX durations; and if the UE receives the DCP from the network device within the second DCP monitoring opportunity, and the fourth indication information included in the DCP indicates dormancy, the UE is on the second group of carriers and is on the second DCP Sleep within the second DRX duration associated with the listening opportunity.
- the DCP can indicate sleep or wake-up in different DRX durations through different indication information.
- the network device can determine whether the corresponding indication information indicates wake-up or sleep according to the information transmission on the two sets of carriers. The sleep or wake-up behavior of the UE is more in line with the service transmission requirements.
- the DCP is implemented in that the two groups of carriers have corresponding DCPs, for example, a carrier group identifier may be included in the DCP to distinguish DCPs of different carrier groups, or DCPs of different carrier groups.
- the format is different. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, and the DCP indicates wake-up, the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP. The DCP corresponding to the group of carriers, and the DCP indicates dormancy, the UE is instructed to sleep on the group of carriers within the DRX cycle associated with the DCP.
- the DCP adopts this implementation, then, if the UE receives the DCP from the network device in the second DCP listening opportunity, and the DCP corresponds to the second group of carriers, if the DCP indicates wake-up, the UE is on the second group of carriers. , wake up within the second DRX duration associated with the second DCP listening opportunity, or, if the DCP indicates dormancy, the UE sleeps on the second group of carriers within the second DRX duration associated with the second DCP listening opportunity .
- the DCP is implemented in that two groups of carriers have corresponding DCPs, for example, a carrier group identifier may be included in the DCP to distinguish DCPs of different carrier groups, or DCPs of different carrier groups.
- the format is different. For a group of carriers, if the network device sends the DCP corresponding to the group of carriers, the UE is instructed to wake up on the group of carriers within the DRX cycle associated with the DCP. If the network device does not send the DCP corresponding to the group of carriers, Then the UE is instructed to sleep within the DRX cycle associated with the DCP on the carrier group.
- the DCP adopts this implementation, then, if the UE receives the DCP from the network device in the second DCP listening opportunity, and the DCP corresponds to the second group of carriers, the UE is on the second group of carriers and the second DCP Wake up within the second DRX duration associated with the listening opportunity, or, if the UE does not receive a DCP corresponding to the second group of carriers from the network device within the second DCP listening opportunity, the UE is on the second group of carriers and is on the first Sleeping within the second DRX duration associated with the two DCP listening opportunities.
- the UE determines not to perform monitoring in the second DCP monitoring occasion, the UE wakes up or sleeps on the second group of carriers within the second DRX duration associated with the second DCP monitoring occasion.
- the UE determines not to perform monitoring in the second DCP monitoring opportunity, it can also perform corresponding replacement.
- the specific replacement method please refer to the introduction to the replacement method of S83.
- the UE determines not to perform monitoring in the second DCP monitoring occasion, the UE does not perform monitoring in the second DCP monitoring occasion.
- the case of S85 is that the UE is not monitoring at the first DCP monitoring occasion nor at the second DCP monitoring occasion.
- the UE may wake up on the first group of carriers within the first DRX duration.
- the second set of carriers for example, it may be defaulted (or specified by the protocol), if the UE determines not to listen in the second DCP listening opportunity (or, if the UE determines not to listen in the first DCP listening opportunity and not listening in the second DCP listening opportunity) ), the UE on the second group of carriers can sleep within the second DRX duration associated with the second DCP listening opportunity to save the power consumption of the UE;
- the UE monitors in the second DCP listening opportunity (or, if the UE determines not to monitor in the first DCP listening opportunity and does not monitor in the second DCP listening opportunity), then the UE is on the second group of carriers and can be associated with the second DCP listening opportunity Wake up for the second DRX duration to reduce the probability that the UE misses data that the network device may send on the second set of carriers.
- the behavior of the UE on the second group of carriers is specified by default or through a protocol, and no additional configuration of the network device is required, nor is it required for the UE to determine by other means, which can simplify the implementation of the network device and the UE.
- the sleep or wake-up of the UE within the second DRX duration on the second group of carriers may also be instructed by the network device.
- the network device sends configuration information to the UE, and accordingly, the UE receives the configuration information from the network device, and the configuration information may be sent, for example, through an RRC message, a system message, or other messages.
- the configuration information may be sent on one or more carriers included in the first group of carriers.
- the primary carrier configured by the network device for the UE belongs to the first group of carriers, and the configuration information may be sent on the primary carrier; or, the configuration Information may also be sent on one or more carriers included in the second set of carriers.
- the configuration information may configure: in the case where the UE does not monitor within the DCP listening opportunity, the UE wakes up on the second group of carriers within the DRX duration associated with the DCP listening opportunity; or, the configuration information may configure: when the UE is not in the DRX duration In the case of monitoring within the DCP monitoring occasion, the UE sleeps on the second group of carriers for the DRX duration associated with the DCP monitoring occasion. In this case, the network device can configure the UE to sleep or wake up on the second group of carriers through configuration information according to factors such as data transmission.
- the network device may instruct the UE to wake up through the configuration information, and if the network device does not schedule the UE to send data and data during the DRX cycle associated with the second DCP listening opportunity on the second group of carriers After receiving the data, the network device may instruct the UE to sleep through the configuration information. In this way, the sleep or wake-up of the UE can be made to meet the data transmission requirement.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the behavior of the terminal device in the combination is specified.
- the UE preferentially monitors the first DCP monitoring timing, and if the first DCP monitoring timing can be monitored, the UE does not need to monitor the second DCP monitoring timing, so as to save power consumption caused by the UE monitoring the DCP monitoring timing. If the UE cannot monitor the first DCP monitoring occasion, the UE may also determine whether it can monitor the second DCP monitoring occasion, so that the UE's behavior is performed under the instruction of the monitoring result as much as possible, so as to better meet the requirements of the network device.
- the network device can configure the second DCP listening timing for the second group of carriers, so that the network device has stronger control over the behavior of the UE on the second group of carriers, and also increases the flexibility of network device scheduling .
- This embodiment of the present application provides a third communication method. Please refer to FIG. 10 , which is a flowchart of the method.
- the network device sends the DCI to the UE on the first carrier, and correspondingly, the UE receives the DCI from the network device on the first carrier.
- the first carrier may include one or more carriers, and the first carrier may belong to the first group of carriers, or may belong to the second group of carriers.
- the first group of carriers applies the first DRX configuration, and the second group of carriers applies the second DRX configuration.
- the DCP is also a kind of DCI, and it is also limited by the DCI size budget.
- the network device does not need to configure the DCP for the UE, or in other words, the network device does not need to send the DCP, but implements the functions of the DCP through other DCIs other than the DCP.
- the size of the DCP is generally different from the size of other ordinary DCIs. According to the DCI size budget of the UE, the DCP occupies one size, which reduces the types of DCIs that the UE can receive.
- the network device does not need to send DCP, but sends ordinary DCI, so the DCP does not occupy the overhead of the DCI size, so that the UE can receive more types of DCI.
- the network device may also configure the DCP for the UE, for example, the network device configures the DCP for the first group of carriers.
- the UE cannot monitor the DCP.
- the network device can also implement the DCP function by sending other DCIs.
- the first group of carriers, the second group of carriers, the first DRX configuration, the second DRX configuration, and the DRX activation time please refer to the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 .
- the network device can send the DCI with the DCP function in the DCP monitoring opportunity.
- the DCI with the DCP function is sent within a DCP listening opportunity, and the UE may receive the DCI with the DCP function within the first DCP listening opportunity.
- the network device may not send the DCI with the DCP function in the DCP listening opportunity, but send the DCI with the DCP function at other times.
- the network device sends the DCI with the DCP function within the On Duration time of the DRX cycle.
- the UE may determine whether to monitor the DCP in the first DCP monitoring opportunity, if the UE determines that the first DCP If the DCP is monitored during the monitoring opportunity, the UE may monitor the DCP during the first DCP monitoring opportunity, or monitor the DCI with the DCP function.
- the UE may monitor the DCP during the first DCP monitoring opportunity, or monitor the DCI with the DCP function.
- S51 in the embodiment shown in FIG. 5 .
- the first determination method is to determine according to the time domain position of the first DCP listening opportunity; for example, the second determination method is to determine according to the DCI size budget; for example, the third determination method is to determine according to the time domain position of the first DCP listening opportunity Location and DCI size budget determination, etc., may be described with reference to S51 of the embodiment shown in FIG. 5 .
- the DCI may indicate that the DCI is used to implement the DCP function through the second field included in the DCI.
- the second field includes, for example, one or more of the following fields: frequency domain resource assignment (FDRA) field, modulation and coding scheme (MCS) field, new data indicator (NDI) ) field, redundancy version (RV) field, hybrid automatic repeat request process number (hybrid automatic repeat request process number), antenna port (antenna port(s)), or, demodulation reference signal sequence initialization ( demodulation reference signal sequence initialization) field.
- FDRA frequency domain resource assignment
- MCS modulation and coding scheme
- NDI new data indicator
- RV redundancy version
- hybrid automatic repeat request process number hybrid automatic repeat request process number
- antenna port antenna port
- demodulation reference signal sequence initialization demodulation reference signal sequence initialization
- the MCS field occupies 5 bits
- the NDI field occupies 1 bit
- the RV field occupies 2 bits
- the HARQ process number field occupies 4 bits
- the antenna port field occupies at least 4 bits
- the DMRS sequence number initialization field occupies 1 bit.
- the second field is the FDRA field; alternatively, the second field is the MCS field; alternatively, the second field includes the MCS field and the NDI field; alternatively, the second field includes the FDRA field, the MCS field, and the RV field, and so on.
- the values of the above fields included in the DCI are related to the scheduled data, for example, the value of the MCS field may indicate the MCS of the scheduled data.
- the value of the second field may be the first value, and the first value may be specified by the protocol, or may be defaulted, or may be configured by the network device. For example, the first value is all 0s, or all 1s, etc. Through this value, the UE can be made clear that the current DCI is used to implement the DCP function.
- the DCI may further include second indication information, and if the value of the second field is not the first value, the DCI does not include the second indication information.
- the value of the second field is not the first value, but the normal value of the second field.
- the DCI is not used to implement the DCP function, but to implement the normal functions of the DCI, such as scheduling data, etc., Then naturally the DCI does not need to include the second indication information. Therefore, if the value of the second field is the first value, it can be indicated that the DCI further includes second indication information.
- the second indication information may indicate that on the second group of carriers, sleep within the second DRX duration associated with the DCI, or indicate that on the second group of carriers, wake up within the second DRX duration associated with the DCI.
- the DCI for implementing the DCP function may be associated with one or more DRX cycles. If the DCI is configured on the first group of carriers and is not configured on the second group of carriers, the association is a time-domain positional association, for example, on the second group of carriers, the time-domain later than this One or more DRX cycles of the DCI can be associated with the DCI.
- the multiple DRX cycles may be continuous or discontinuous in the time domain.
- the second DRX duration corresponds to a second DRX configuration, and the second DRX duration is on the second set of carriers.
- the second DRX duration may include the On Duration time in all or part of the DRX cycle associated with the DCI under the second DRX configuration, or in other words, the second DRX duration may include all the Or the On Duration time in a partial DRX cycle.
- the second indication information may occupy one or more bits. Taking the second indication information occupying 1 bit as an example, for example, if the value of this bit is "1", it indicates that on the second group of carriers, wake up within the second DRX duration associated with the DCI; if this bit The value of is "0", indicating that on the second group of carriers, sleep within the second DRX duration associated with the DCI. Alternatively, if the second indication information occupies more bits, there may be other indication manners.
- the second indication information included in the DCI instructs the UE to sleep or wake up on the second group of carriers, and the UE does not need to monitor the DCP, which reduces the number of DCI sizes that the UE needs to monitor.
- the network equipment instructs the UE to sleep or wake up on the second group of carriers, the network equipment can instruct the UE according to the services of the UE on the second group of carriers, so that the behavior of the UE to sleep or wake up on the second group of carriers is more efficient. Meet the service requirements of the UE.
- the UE wakes up on the first group of carriers within the first DRX duration associated with the DCI. Because if the second indication information indicates that the UE wakes up on the second set of carriers within the second DRX duration, and the network device needs to schedule the UE's data transmission on the second set of carriers on the first set of carriers, then if the UE Sleeping on the first group of carriers for the first DRX duration may fail to receive scheduling information from the network device, so that data transmission cannot be performed on the second group of carriers.
- the UE may wake up on the first group of carriers within the first DRX duration by default (or stipulated in the protocol), so as to reduce the probability that the UE misses the scheduling information and reduce the transmission delay of the service.
- the UE sleeps on the first group of carriers for the first DRX duration associated with the DCI. In this way, the power consumption of the UE can be saved.
- the first carrier may belong to the first group of carriers or to the second group of carriers, that is, the network device may send the DCI on the first group of carriers or send the DCI on the second group of carriers.
- the DCI for implementing the DCP function may be associated with one or more DRX cycles.
- one or more DRX cycles that are later than the DCI in the time domain can be associated with the DCI.
- the multiple DRX cycles may be continuous or discontinuous in the time domain.
- the first DRX duration corresponds to the first DRX configuration, and the first DRX duration is on the first group of carriers.
- the first DRX duration may include the On Duration time in all or part of the DRX cycle associated with the DCI under the first DRX configuration, or in other words, the first DRX duration may include all the Or the On Duration time in a partial DRX cycle.
- the DCI only needs to include the second indication information, and does not need to include the indication information for indicating the wake-up or dormancy of the first group of carriers, which helps to save signaling overhead.
- the DCI may further include the first indication information, and if the value of the second field is not the first value, or if If the value of the second field is the second value, the DCI does not include the first indication information.
- the second value may be any value of the second field except the first value.
- the value of the second field is not the first value, but the common value of the second field.
- the DCI is not used to implement the DCP function, but to implement the normal functions of the DCI, such as scheduling data, etc., then the DCI Naturally, it is not necessary to include the first indication information.
- the DCI further includes the first indication information.
- the first indication information may indicate that on the first group of carriers, sleep within the first DRX duration associated with the DCI, or indicate that on the first group of carriers, wake up within the first DRX duration associated with the DCI.
- FIG. 11 it is taken as an example that DCI is configured on the first group of carriers, the first group of carriers belongs to FR1, and the second group of carriers belongs to FR2.
- the DCI received by the UE on FR1 can indicate the sleep or wake-up of the UE on the second group of carriers, and optionally, can also indicate the sleep or wake-up of the UE on the first group of carriers.
- the first carrier may belong to the first group of carriers or to the second group of carriers, that is, the network device may send the DCI on the first group of carriers or send the DCI on the second group of carriers.
- the first indication information may occupy one or more bits. Taking the first indication information occupying 1 bit as an example, for example, if the value of this bit is "1", it indicates that on the first group of carriers, wake up within the first DRX duration associated with the DCI; The value of is "0", indicating that on the first group of carriers, sleep within the first DRX duration associated with the DCI. Alternatively, if the first indication information occupies more bits, there may be other indication manners.
- the first indication information included in the DCI instructs the UE to sleep or wake up on the first group of carriers. The UE does not need to monitor the DCP, which reduces the number of DCI sizes that the UE needs to monitor. hibernate or wakeup is regulated.
- the network equipment can instruct the UE according to the services of the UE on the first group of carriers, so that the behavior of the UE to sleep or wake up on the first group of carriers is more efficient. Meet the service requirements of the UE.
- the network device respectively instructs the dormancy or wake-up of the two groups of carriers through the second indication information and the first indication information, so that the behavior of the UE is more explicit and more in line with service requirements.
- the second indication information may indicate the behavior of the UE on the first group of carriers in addition to indicating the behavior of the UE on the second group of carriers. That is, the second indication information may indicate that on the second group of carriers, sleep or wake up within the second DRX duration associated with the DCI, and indicate that on the first group of carriers, within the first DRX duration associated with the DCI Sleep or wake up. Or, the second indication information indicates to sleep or wake up within the DRX duration associated with the DCI.
- the first carrier may belong to the first group of carriers or to the second group of carriers, that is, the network device may send the DCI on the first group of carriers or send the DCI on the second group of carriers.
- the second indication information occupies one or more bits. Taking the second indication information occupying 1 bit as an example, if the value of this bit is "1", it indicates that on the first group of carriers, wake up within the first DRX duration associated with the DCI, and indicate that the second group of On the carrier, wake up within the second DRX duration associated with the DCI; if the value of this bit is "0", it indicates that on the first group of carriers, sleep within the first DRX duration associated with the DCI, and Indicates that on the second set of carriers, sleep for the second DRX duration associated with the DCI. Or, taking 2 bits for the second indication information as an example, the 2 bits respectively indicate the first group of carriers and the second group of carriers.
- the high-order bits of the 2 bits indicate the first group of carriers, and the low-order bits indicate the second group of carriers. If the value of the high-order bit in these 2 bits is "1", it indicates that on the first group of carriers, wake up within the first DRX duration associated with the DCI; if the value of the high-order bit in these 2 bits is the value of "0" indicates that on the first group of carriers, sleep for the first DRX duration associated with the DCI.
- the lower-order bits of these 2 bits also indicate the behavior of the UE on the second group of carriers in a similar manner.
- the network device can indicate the behavior of the UE on the first group of carriers and the second group of carriers through the second indication information, no more indication information is needed, the signaling overhead can be saved, and the behavior of the UE is improved. to be clear.
- the first carrier may include at least two carriers, and the at least two carriers include both the carriers belonging to the first group of carriers and the carriers belonging to the second group of carriers.
- the first carrier includes a second carrier and a third carrier, the second carrier belongs to the first group of carriers, and the third carrier belongs to the second group of carriers.
- the network device sends both the DCI on the first group of carriers and the DCI on the second group of carriers, then the DCI may also include at least two, and the DCI includes the first DCI and the second DCI. Take DCI as an example, the first DCI is sent on the second carrier, and the second DCI is sent on the third carrier.
- the first DCI may indicate the behavior of the UE on the first set of carriers
- the second DCI may indicate the behavior of the UE on the second set of carriers.
- the first DCI may indicate sleep on the first set of carriers for the first DRX duration associated with the DCI, or may indicate wake-up on the first set of carriers within the first DRX duration associated with the DCI.
- the second DCI may indicate sleep on the second set of carriers for the second DRX duration associated with the DCI, or may indicate wake-up on the second set of carriers within the second DRX duration associated with the DCI.
- the first DCI includes the first indication information
- the second DCI includes the second indication information.
- the second DCI may include the second field, and the first DCI may also include the first field.
- the second DCI may further include the second indication information, and if the value of the second field is not the first value, the second DCI does not include the second indication information.
- the first DCI may further include the first indication information, and if the value of the first field is not the third value, the first DCI does not include the first indication information.
- the network device can respectively indicate the behavior of the UE on different carriers through the DCI carried on different carriers, and the indication is more explicit.
- S102 The UE determines, according to the second indication information included in the DCI, that on the second group of carriers, sleep or wake up within the second DRX duration associated with the DCI.
- S102 may also be replaced by, according to the second indication information included in the DCI, the UE sleeps or wakes up on the second group of carriers within the second DRX duration associated with the DCI.
- S102 may be replaced by: the UE determines according to the second indication information included in the second DCI, on the second group of carriers, on the second DCI Sleep or wake up for the associated second DRX duration.
- the UE determines that the DCI includes second indication information. Then, if the second indication information indicates that on the second group of carriers, the UE sleeps within the second DRX duration associated with the DCI, the UE determines to sleep on the second group of carriers within the second DRX duration associated with the DCI , then the UE sleeps within the second DRX duration on the second set of carriers; or, if the second indication information indicates that on the second set of carriers, the UE wakes up within the second DRX duration associated with the DCI, the UE determines On the second set of carriers, the UE wakes up within the second DRX duration associated with the DCI, then the UE sleeps on the first set of carriers for the first DRX duration.
- S103 The UE determines to sleep or wake up on the first group of carriers within the first DRX duration associated with the DCI. Alternatively, there may be no deterministic process. For example, S103 may also be replaced by, on the first group of carriers, the UE sleeps or wakes up within the first DRX duration associated with the DCI. Alternatively, according to the introduction in S101, if the DCI includes the first DCI and the second DCI, then S103 may be replaced by the UE determining to sleep or wake up on the first group of carriers within the first DRX duration associated with the first DCI .
- the UE wakes up on the first group of carriers within the first DRX duration associated with the DCI, then if the network device does not configure DCP, the UE will wake up on the first group of carriers in the first DRX duration. Wake up within a DRX duration; or, if the network device is configured with DCP, then if the UE does not monitor DCP on the first set of carriers, the UE wakes up on the first set of carriers within the first DRX duration.
- the UE sleeps on the first set of carriers for the first DRX duration associated with the DCI, then if the network device does not configure DCP, the UE will sleep on the first set of carriers.
- the DCI further includes the first indication information
- the first indication information indicates that the first group of carriers is on the carrier
- the DCI includes the first indication information
- the UE sleeps for the first DRX duration on the first group of carriers; or, if the DCI does not include the first indication information, the UE sleeps on the first group of carriers Sleep for the first DRX duration.
- the UE wakes up within the first DRX duration associated with the DCI, then the UE wakes up on the first group of carriers within the first DRX duration; or , if the first indication information included in the DCI indicates that on the first set of carriers, the UE sleeps within the first DRX duration associated with the DCI, then the UE sleeps on the first set of carriers within the first DRX duration.
- the second indication information indicates both the behavior of the UE on the first group of carriers and the behavior of the UE on the second group of carriers, then, if the second indication information indicates dormancy for the DRX duration associated with the DCI, then the UE sleeps for the first DRX duration on the first set of carriers and sleeps for the second DRX duration on the second set of carriers; or, if the second indication information indicates that the DCI is associated with the DRX duration wakes up, the UE wakes up for the first DRX duration on the first set of carriers and wakes up for the second DRX duration on the second set of carriers.
- the DCI includes a first DCI and a second DCI
- the first DCI includes first indication information
- the second DCI includes second indication information
- the second indication information indicates the behavior of the UE on the second group of carriers
- the first The indication information indicates the behavior of the UE on the first set of carriers.
- the UE Wake up; or, if the first indication information included in the first DCI indicates that on the first group of carriers, the UE will sleep within the first DRX duration associated with the first DCI, then the UE continues on the first DRX on the first group of carriers time to sleep. If the second indication information included in the second DCI indicates that on the second set of carriers, the UE wakes up within the second DRX duration associated with the second DCI, then the UE wakes up on the second set of carriers within the second DRX duration; Alternatively, if the second indication information included in the second DCI indicates that on the second group of carriers, the UE sleeps within the second DRX duration associated with the second DCI, then the UE is on the second group of carriers for the second DRX duration. hibernate.
- the network device For the network device, if the DCP is not configured, the network device does not need to send the DCP, and the UE does not need to monitor the DCP. If DCP is configured, for example, DCP is configured for the first group of carriers, the network device can normally send DCP on the first group of carriers, and, in order to prevent the UE from sometimes being unable to monitor the DCP, the network device also sends the DCI capable of implementing the DCP function. .
- the UE can determine whether the DCP can be monitored on the first group of carriers, and if the UE can monitor the DCP, the UE can determine whether to sleep or wake up on the first group of carriers according to the monitoring result of the DCP without needing to Dormancy or wake-up on the first group of carriers is determined by a default (or protocol-specified) rule, the second indication information, or the first indication information. Alternatively, if the UE cannot monitor the DCP, the UE may determine to sleep or wake up on the first group of carriers according to a default (or protocol-specified) rule or according to the first indication information.
- the two DRX configuration technologies can be used in combination with the wake-up signal, and the embodiment of the present application does not need to configure DCP, but implements the function of DCP through ordinary DCI, reducing the number of DCI sizes that the UE needs to monitor. number, or enable the UE to monitor more DCI size, which also simplifies the implementation of the network device and the UE.
- the network device can instruct the UE to wake up or sleep on the carrier group through the corresponding indication information, and the indication method is more flexible, which is more in line with the service transmission requirements of the UE, and also increases the flexibility of the network device scheduling.
- the embodiment of the present application also avoids that the UE wakes up on the second group of carriers within the second DRX duration by default, which can reduce the power consumption of the UE.
- FIG. 5 , FIG. 7 or FIG. 10 mainly considers the problem of combining two sets of DRX configurations with the wake-up signal.
- cross-carrier scheduling and two sets of DRX configurations are not currently used in combination.
- a fourth communication method is provided below, so as to use the cross-carrier scheduling in combination with the two sets of DRX configurations, so as to further reduce the power consumption of the UE.
- FIG. 12 is a flowchart of the method.
- the network device sends the second DCI on the first carrier, and accordingly, the UE receives the second DCI from the network device on the first carrier.
- the first carrier belongs to a first group of carriers, the first group of carriers includes one or more carriers configured for the UE, and the first carrier is, for example, some or all of the carriers included in the first group of carriers.
- the primary carrier configured by the network device for the UE belongs to the first group of carriers
- the first carrier may be the primary carrier of the UE, and the network device may send the second DCI on the primary carrier.
- the second DCI may be used to schedule data on the second group of carriers.
- the second DCI schedules new transmission data, or the second DCI may indicate new transmission of downlink data, or the second DCI may indicate new transmission of uplink data.
- the second DCI may schedule the UE to receive data or transmit data on the second group of carriers, that is, the second DCI implements cross-carrier scheduling.
- the first group of carriers and the second group of carriers reference may be made to the embodiments shown in any one of FIG. 5 , FIG. 7 or FIG. 10 .
- the UE starts or restarts the second DRX inactivity timer, and sets the duration of the second DRX inactivity timer to the duration of the DRX inactivity timer configured in the second DRX configuration.
- the second DCI schedules data on the second group of carriers, data may be transmitted on the second group of carriers in the future. Therefore, it is necessary to extend the DRX activation time of the UE on the second group of carriers to ensure that the UE is on the second group of carriers. It can receive data or send data on the uplink, and it can also ensure that the UE performs corresponding actions within the DRX activation time, such as sending periodic uplink sounding reference signals (SRS), or reporting channel status information (channel status information) through PUCCH. , CSI), or reporting semi-periodic channel status information (channel status information, CSI) through the PUSCH, and so on.
- SRS periodic uplink sounding reference signals
- CSI channel status information
- CSI semi-periodic channel status information
- an implementation manner is to start or restart the second DRX inactivation timer.
- the UE may start or restart the second DRX inactivity timer in the first time domain symbol after the second DCI is received.
- the UE starts the second DRX inactive timer; or, in the first time after the second DCI has been received Time domain symbol, if the second DRX inactivation timer is in the running state, the UE restarts the second DRX inactivation timer.
- a second DRX configuration is applied to the second group of carriers, and the second DRX configuration may be configured with a DRX cycle, a DRX inactivation timer, and a DRX retransmission timer.
- the second DRX inactivation timer corresponds to the second group of carriers, or corresponds to the second DRX configuration. It can be understood that the DRX inactivation timer configured in the second DRX configuration is the second DRX inactivation timer.
- the UE may set the duration of the second inactivity timer to the original duration of the second DRX inactivity timer, that is, the duration of the DRX inactivity timer configured in the second DRX configuration.
- the UE starts or restarts the second DRX inactivity timer.
- An implementation manner is that the UE defaults (or stipulated in the protocol) and starts or restarts the second DRX inactivity timer after receiving the second DCI. This method does not require additional notification by the network device, which can save signaling overhead.
- the UE starts or restarts the second DRX inactivation timer, and another implementation manner is that it is instructed by the network device.
- the second DCI may include second indication information, and the second indication information may instruct to start or restart the second DRX inactivity timer. If this is the way, then there may be two cases. In one case, if the second DCI includes the second indication information, it is instructed to start or restart the second DRX inactivity timer, and the UE starts or restarts the second DRX inactivity timer; and if the second DCI does not include the second indication information, it indicates that the second DRX inactivation timer is neither started nor restarted, and the UE neither starts nor restarts the second DRX inactivity timer.
- the second DCI may include the second indication information or may not include the second indication information, which can save the signaling overhead of the second DCI.
- the second indication information included in the second DCI indicates to start or restart the second DRX inactivation timer, the UE starts or restarts the second DRX inactivation timer;
- the second indication information indicates that the second DRX inactivation timer is neither started nor restarted, and the UE neither starts nor restarts the second DRX inactivity timer.
- the indication is performed through the second DCI, so that the UE is more explicit about the behavior of the UE.
- the second indication information may be carried by an existing field in the second DCI. For example, if there are reserved bits in an existing field included in the second DCI, it may be carried by the reserved bits; or, it may be carried in the second DCI. One or more bits are added to the DCI to carry the second indication information.
- S123 The UE extends the DRX activation time of the UE on the first group of carriers.
- the subsequent network device may also schedule data on the second group of carriers by means of cross-carrier scheduling. Additionally, the network device may also schedule data on the first set of carriers on the first set of carriers. Therefore, the DRX activation time of the UE on the first set of carriers may be extended to receive DCI for scheduling data.
- the UE For the UE to extend the DRX activation time of the UE on the first group of carriers, there may be different implementations, and the following examples are introduced.
- the first way extend the DRX activation time of the UE on the first group of carriers through the first DRX inactivation timer.
- the first DRX configuration is applied to the first group of carriers, and the first DRX configuration may be configured with a DRX cycle, a DRX inactivation timer, and a DRX retransmission timer.
- the first DRX inactivation timer corresponds to the first group of carriers, or corresponds to the first DRX configuration. It can be understood that the DRX inactivation timer configured in the first DRX configuration is the first DRX inactivation timer.
- the UE may start or restart the first DRX inactivation timer. In this way, the DRX activation time of the UE on the first group of carriers can be extended, so that the UE can receive DCI on the first group of carriers.
- the UE also needs to set the duration of the first DRX inactivity timer.
- the UE may set the duration of the first DRX inactivity timer to the original duration of the first DRX inactivity timer, that is, the duration of the DRX inactivity timer configured in the first DRX configuration.
- This setting method is relatively simple, and it is also a setting that is easy for the UE to implement.
- the UE may work more on the first group of carriers.
- the duration of the DRX inactivity timer configured by a DRX configuration may be relatively long.
- the duration of the first DRX inactivation timer is set to the duration of the DRX inactivation timer configured in the first DRX configuration
- the DRX activation time of the UE on the first group of carriers may be prolonged too long, for example, network equipment
- the data of the second group of carriers may no longer be scheduled, and the UE may have entered the DRX inactive time on the second group of carriers, but the UE is still in the DRX active time on the first group of carriers, which may cause the UE to be in the first group of carriers. Power consumption on the carrier increases. Referring to FIG.
- the running time of the first DRX inactivation timer corresponding to FR1 is longer than the running time of the second DRX inactivation timer corresponding to FR2, after the second DRX inactivation timer has stopped running, the UE Still in DRX activation time on FR1.
- the network device may send the first signaling, and the first signaling may instruct the UE to stop the first DRX inactivity timer. After receiving the first signaling, the UE may stop running the first DRX inactivation timer.
- the first signaling is, for example, DCI, or may also be radio resource control (radio resource control, RRC) signaling, or the like. But this needs to consume extra signaling.
- the UE when the UE needs to set the duration of the first DRX inactivation timer, for example, when starting the first DRX inactivation timer, or when starting the first DRX inactivation timer Before activating the timer, instead of setting the duration of the first DRX inactivation timer to the duration of the DRX inactivation timer configured in the first DRX configuration, set the duration of the first DRX inactivation timer to the second DRX Configure the duration of the configured DRX inactivity timer.
- the UE sets the duration of the first DRX inactivation timer to the second DRX inactivation timer The duration of the inactive timer. If this method is adopted, the duration of the DRX activation time of the UE on the first group of carriers may be the same as the duration of the DRX activation time of the UE on the second group of carriers. The DCI used to schedule the data of the second group of carriers will not consume too much power because the DRX activation time on the first group of carriers is too long. Referring to FIG. 14 , the operation time of the first DRX inactivity timer corresponding to FR1 is the same as the operation time of the second DRX inactivity timer corresponding to FR2.
- What duration the UE sets the duration of the first DRX inactivation timer to can be set by default or specified by a protocol. Alternatively, the UE may also determine what duration to set the duration of the first DRX inactivation timer to according to a corresponding situation.
- the UE receives the first DCI on the first set of carriers before starting or restarting the first DRX inactivity timer, and the first DCI is used to schedule the UE to receive data or transmit data on the first set of carriers
- the UE The duration of the first DRX inactivity timer can be set to the duration of the DRX inactivity timer configured by the first DRX configuration, so as to meet the needs of the UE for receiving data or sending data on the first group of carriers, and can also meet the needs of the UE A scheduled requirement to receive data corresponding to the first set of carriers on the first set of carriers.
- the UE does not need to start or restart the first DRX inactivity timer under any circumstances, but may first determine whether to start or restart the first DRX inactivity timer.
- the UE may determine the remaining duration of the first DRX inactivity timer and the value configured by the second DRX configuration. The size relationship between the durations of the DRX inactivity timers.
- the UE may set the duration of the first DRX inactivity timer to the duration configured by the second DRX configuration The duration of the DRX inactivation timer; or, if the remaining duration of the first DRX inactivation timer is longer than or equal to the duration of the DRX inactivation timer configured in the second DRX configuration, the UE does not need to restart the first DRX inactivation timer. Activate the timer.
- the UE does not restart the first DRX inactivity timer, since the first DRX inactivity timer is in the running state, and the remaining duration of the first DRX inactivity timer is longer than or equal to the second DRX inactivity timer
- Configuring the duration of the configured DRX inactivation timer indicates that the DRX activation time of the UE on the first group of carriers does not need to be extended additionally, but can already meet the requirements.
- Whether the UE wants to start the first DRX inactivation timer can be determined by default or specified by a protocol.
- the protocol stipulates that if the UE receives the DCI for scheduling data on the second set of carriers on the first set of carriers, the UE starts the first DRX inactivity timer.
- whether the UE wants to start the first DRX inactivation timer can also be configured by the network device.
- the second DCI may include first indication information, and the first indication information may instruct to start or restart the first DRX inactivity timer. If this is the way, then there may be two cases.
- the second DCI includes the first indication information, it is instructed to start or restart the first DRX inactivity timer, and the UE starts or restarts the first DRX inactivity timer; and if the second DCI does not include the first indication information, it indicates that the first DRX inactivity timer is neither started nor restarted, and the UE neither starts nor restarts the first DRX inactivity timer.
- the second DCI may include the first indication information or may not include the first indication information, which can save signaling overhead of the second DCI.
- the UE starts or restarts the first DRX inactivity timer; If the indication information indicates that the first DRX inactivity timer is neither to be started nor restarted, the UE neither starts nor restarts the first DRX inactivity timer.
- the indication is performed through the second DCI, so that the UE is more explicit about the behavior of the UE.
- the first indication information may not only instruct the UE to start or restart the first DRX inactivity timer, but also indicate how to set the duration of the first DRX inactivity timer.
- the first indication information may indicate that the timing duration of the first DRX inactivity timer is set to the duration of the DRX deactivation timer configured by the first DRX configuration, or the timing duration of the first DRX deactivation timer may be set to The duration of the configured DRX inactivity timer for the second DRX configuration, the UE may set the duration of the first DRX inactivity timer according to the first indication information.
- the second DCI may also use other information to indicate how to set the duration of the first DRX inactivation timer.
- the second DCI may further include third indication information, and the third indication information may indicate that the first DRX inactivation timer is to be set.
- the timing duration of the first DRX configuration is set to the duration of the DRX inactivation timer configured by the first DRX configuration, or it is instructed to set the timing duration of the first DRX inactivation timer to the duration of the DRX inactivation timer configured by the second DRX configuration.
- the UE By indicating the setting method of the duration of the first DRX inactivation timer by the corresponding indication information, the UE does not need to determine how to set the duration of the first DRX inactivation timer by itself, which simplifies the implementation of the UE.
- the UE does not need to rely on the first DRX inactivation timer, because the UE knows the end time of the second DRX inactivation timer, or in other words, the UE knows the DRX activation time of the UE on the second group of carriers Therefore, the UE can extend the DRX activation time of the UE on the first group of carriers, for example, extend the end time of the UE's DRX activation time on the first group of carriers to the same time as the UE's DRX activation time on the second group of carriers. The end of the activation time is the same.
- the duration of the DRX activation time of the UE on the first set of carriers is the same as the duration of the DRX activation time of the UE on the second set of carriers, and the UE can receive both on the first set of carriers.
- the DCI used for scheduling the data of the second group of carriers will not consume too much power because the DRX activation time on the first group of carriers is too long.
- the first DRX inactive time timer is not needed, and the power consumption caused by the UE maintaining the first DRX inactive time timer is reduced.
- the UE extends the DRX activation time of the UE on the first group of carriers (the dashed box in FIG. 15 represents the extended time), so that the running time of the first DRX inactivation timer corresponding to FR1 is the same as that of the first DRX inactivation timer corresponding to FR1.
- the running time of the second DRX inactivity timer of FR2 is the same.
- the DRX activation time on the first group of carriers (that is, the DRX activation time of the first DRX configuration) is defined as the DRX activation time corresponding to the first DRX configuration on the first group of carriers and the second The union of the DRX activation times corresponding to the second DRX configuration on the group carrier.
- S122 and S123 may be executed simultaneously, or S122 may be executed before S123, or S122 may be executed after S123.
- the two DRX configuration technologies can be used in combination with the cross-carrier scheduling technology.
- the UE can receive on the first set of carriers a message for scheduling on the second set of carriers from the network device.
- the DCI of the data and the UE can also receive data or send data on the second group of carriers, so that the cross-carrier scheduling technology can be realized in the context of the two DRX configuration technologies.
- the duration of the first DRX inactive timer corresponding to the first group of carriers can be set to different durations according to different situations, so that the duration of the first DRX inactive timer is more in line with the current service transmission. It also saves the power consumption of the UE.
- the UE can send energy saving capability information or an energy saving indication to the network device, where the energy saving capability information indicates that the UE supports the first solution, and the energy saving indication is used for Indicates that the UE needs to save energy, or instructs the UE to request the application of the first solution.
- the UE may also send the energy saving capability information or the energy saving indication to the network device.
- the first solution is the solution provided by the embodiment shown in any one of FIG. 5 , FIG. 8 , FIG. 10 or FIG. 12 .
- the network device After the network device receives the energy-saving capability information or the energy-saving indication from the UE, if the network device has configured the UE with the first DRX configuration, the second DRX configuration, and the DCP (or DCI), the network device determines that the UE applies the first DRX configuration, the second DRX configuration, and the DCP (or DCI). a plan.
- the network device may send energy saving permission information or configuration information related to the first solution to the UE, to indicate that the UE is allowed to save energy, or to indicate that the UE is allowed to apply the first solution.
- the UE After the UE receives the energy saving permission information from the network device or the configuration information related to the first solution, the UE can apply the first solution.
- the network device may send the second DRX configuration to the UE.
- the UE After the UE receives the second DRX configuration, it can apply the first solution. After applying the first solution, the UE can further reduce power consumption, that is, reduce the consumed battery power and prolong the standby time of the UE.
- the time length of the first DRX activation time is greater than or equal to the time length of the second DRX activation time.
- the first group of carriers corresponds to the first DRX activation time
- the first DRX activation time includes, for example, all or part of the DRX activation time of the UE on the first group of carriers under the first DRX configuration.
- the second group of carriers corresponds to the second DRX activation time
- the second DRX activation time includes, for example, all or part of the DRX activation time of the UE on the second group of carriers under the second DRX configuration.
- the network device may schedule the UE to receive data or transmit data on the second set of carriers on the first set of carriers, the UE needs to receive scheduling information corresponding to the second set of carriers on the first set of carriers.
- the scheduling information is carried, for example, in In the DCI sent through the PDCCH. Then, if the time length of the first DRX activation time is less than the time length of the second DRX activation time, there may be a situation that the UE enters the sleep state on the first group of carriers, but the network device is on the first group of carriers.
- the DCI used to schedule data transmission on the second group of carriers is sent. At this time, the UE may not be able to receive the DCI due to dormancy, so that the UE cannot transmit data on the second group of carriers.
- the embodiment of the present application proposes to make the time length of the first DRX activation time greater than or equal to the time length of the second DRX activation time.
- the first DRX activation time may also be set in the time domain
- the second DRX activation time can be covered, for example, the second DRX activation time is located within the first DRX activation time in the time domain, or the second DRX activation time is overlapped with the first DRX activation time in the time domain, so that the UE can Scheduling information from the network device is received on the first set of carriers.
- the time length of the first DRX activation time be greater than or equal to the time length of the second DRX activation time, for example, an implementation manner is that the time length of all or part of the timers configured in the first DRX configuration is greater than or equal to the second DRX configuration.
- the duration of the corresponding timer configured. For example, let the duration of the first DRX duration timer be greater than or equal to the duration of the second DRX duration timer, the first DRX duration timer is configured by the first DRX configuration, and the second DRX duration timer is the first DRX duration timer. Two DRX configuration is configured.
- the duration of the first DRX duration timer be greater than or equal to the duration of the second DRX duration timer
- the duration of the first DRX inactivity timer be greater than or equal to the duration of the second DRX inactivity timer
- the first DRX inactivation timer is configured by the first DRX configuration
- the second DRX inactive timer is configured by the second DRX configuration.
- the duration of the first DRX duration timer be greater than or equal to the duration of the second DRX duration timer
- the duration of the first DRX inactivity timer is greater than or equal to the duration of the second DRX inactivity timer
- the duration of the first DRX retransmission timer be greater than or equal to the duration of the second DRX retransmission timer
- the first DRX retransmission timer is configured by the first DRX configuration
- the second DRX retransmission timer is the second DRX retransmission timer Configured by the DRX configuration.
- Rule 1 may be specified by a protocol, or may be default, or may be configured by a network device.
- Rule 2 Configure DCI on the first group of carriers to schedule data transmission on the second group of carriers, but not configure DCI on the second group of carriers to schedule data transmission on the first group of carriers.
- the frequencies of the second frequency range are greater than the frequencies of the first frequency range, for example, the frequencies of the second group of carriers belong to FR2, and the frequencies of the first group of carriers belong to FR1. Since the frequency of FR2 is higher than the frequency of FR1, the UE consumes more power when working on the carrier of FR2. Therefore, optionally, if cross-carrier scheduling is configured in this embodiment of the present application, it may be configured to schedule the second carrier through the first group of carriers.
- a group of carriers that is, configuring the DCI on the first group of carriers to schedule data transmissions on the second group of carriers, and not configuring the DCI on the second group of carriers to schedule data transmissions on the first group of carriers.
- Rule 2 may be specified by a protocol, or may be default, or may be configured by a network device.
- Rule 3 The data transmission time on the second group of carriers scheduled on the first group of carriers is within the DRX activation time of the UE on the second group of carriers.
- the transmission time of the data on the second group of carriers scheduled by the DCI sent by the network device on the first group of carriers may be at the time when the UE is on the first group of carriers.
- DRX inactive time on two groups of carriers For example, referring to FIG. 7 , the network device sends DCI on the carrier of FR1, and the DCI schedules data transmission on the carrier of FR2.
- the UE receives the DCI within the On Duration time in a DRX cycle, and the data transmission time scheduled by the DCI is, for example, time T1 in FIG. 7 .
- the UE is on the second group of carriers.
- the DRX inactivity timer on the UE has expired, so T1 is within the UE's DRX inactivity time on the second set of carriers. If this is the case, the UE still needs to receive the PUSCH or PDSCH during the DRX inactive time, which will bring extra power consumption to the UE. Therefore, optionally, the embodiment of the present application stipulates that the data transmission time on the second group of carriers scheduled by the network device on the first group of carriers needs to be within the DRX activation time of the UE on the second group of carriers.
- Rule 3 may be specified by a protocol, or may be default, or may be configured by a network device.
- the above three rules can be applied in combination with the embodiment shown in FIG. 5 , or can be applied in combination with the embodiment shown in FIG. 8 , or can be applied in combination with the embodiment shown in FIG. 10 , or can be applied in combination with the embodiment shown in FIG. 12 . Examples of combined applications. Alternatively, the above three rules may also be applied independently without being combined with any of the foregoing method embodiments. In addition, when applied alone, one or more of the above rules can be applied, that is, any two or three of the above three rules can be applied in combination, or, the above three rules can also not be combined, but Apply separately.
- rule 1 may apply without rules 2 and 3; alternatively, rule 2 may apply without rules 1 and 3; alternatively, rule 3 may apply without rules 1 and 2; alternatively, rules may apply 1 and rule 2 without applying rule 3; alternatively, rules 1 and 3 may apply without applying rule 2; alternatively, rules 2 and 3 may apply without applying rule 1; alternatively, rules 1, 2 and Rule 3.
- FIG. 16 is a schematic block diagram of a communication apparatus 1600 according to an embodiment of the present application.
- the communication apparatus 1600 is, for example, a terminal device or a network device.
- the communication apparatus 1600 can implement the functions of the UE described in the embodiment shown in FIG. 5 , the embodiment shown in FIG. 8 , the embodiment shown in FIG. 10 , or the embodiment shown in FIG. 12 .
- the communication apparatus 1600 can implement the function of the network device described in the embodiment shown in FIG. 10 .
- the communication device 1600 includes a transceiver unit 1620 and a processing unit 1610 .
- the communication apparatus 1600 may further include a storage unit, and the storage unit can communicate with the processing unit 1610, which is not shown in FIG. 16 .
- the communication device 1600 may not include a storage unit, and the storage unit may also be located outside the communication device 1600 .
- the communication apparatus 1600 may be a UE, or may be a chip applied in the UE or other combined devices, components, etc. having the above-mentioned UE functions, or the communication apparatus 1600 may be a network device, or may be applied to a network device. The chip or other combined devices, components, etc. with the functions of the above-mentioned network equipment.
- the processing unit 1610 may include a processor, such as a baseband processor, and the baseband processor may include one or more central processing units (CPUs); the transceiver unit 1620 may be Transceivers, transceivers may include antennas and radio frequency circuits, among others.
- the transceiver may include a transmitter and a receiver, and the transceiver may implement the functions of the transmitter and the receiver, or the transmitter and the receiver may also be two function modules deployed separately, but the embodiment of the present application uses these two functions. These functional modules are collectively referred to as transceivers.
- the transceiver unit 1620 may be a radio frequency unit, and the processing unit 1610 may be a processor, such as a baseband processor.
- the transceiver unit 1620 may be an input/output interface of a chip (eg, a baseband chip), and the processing unit 1610 may be a processor of the chip system, which may include one or more central processing units.
- the processing unit 1610 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component, and the transceiver unit 1620 may be implemented by a transceiver or a transceiver-related circuit component.
- the processing unit 1610 may be used to perform the functions other than those performed by the UE in the embodiment shown in FIG. 5 . All operations other than transceiving operations, eg, S51-S53, and/or other processes used to support the techniques described herein.
- Transceiver unit 1620 may be configured to perform all receive and transmit operations performed by the UE in the embodiment shown in FIG. 5 , such as operations to monitor DCP, and/or other processes for supporting the techniques described herein.
- the processing unit 1610 may be used to perform the functions other than those performed by the UE in the embodiment shown in FIG. 8 . All operations other than transceiving operations, eg, S81-S85, and/or other processes used to support the techniques described herein.
- Transceiver unit 1620 may be configured to perform all receive and transmit operations performed by the UE in the embodiment shown in FIG. 8 , such as operations to monitor DCP, and/or other processes for supporting the techniques described herein.
- the processing unit 1610 may be used to perform the functions other than those performed by the UE in the embodiment shown in FIG. 10 . All operations other than transceiving operations, such as S102-S103, and/or other processes used to support the techniques described herein.
- Transceiver unit 1620 may be configured to perform all receive and transmit operations performed by the UE in the embodiment shown in FIG. 10 , eg, S101 , and/or other processes for supporting the techniques described herein.
- the processing unit 1610 may be used to execute the network device in the embodiment shown in FIG. 10 . All operations other than transceiving operations, and/or other processes used to support the techniques described herein.
- the transceiver unit 1620 may be configured to perform all receive operations and transmit operations performed by the network device in the embodiment shown in FIG. 10 , such as S101 , and/or other processes for supporting the techniques described herein.
- the processing unit 1610 may be used to perform the functions other than those performed by the UE in the embodiment shown in FIG. 12 . All operations other than transceiving operations, eg, S122-S123, and/or other processes used to support the techniques described herein.
- Transceiver unit 1620 may be configured to perform all receive and transmit operations performed by the UE in the embodiment shown in FIG. 12 , such as S121 , and/or other processes for supporting the techniques described herein.
- the transceiver unit 1620 may be a functional module, and the function module can perform both sending and receiving operations.
- the transceiver unit 1620 may be used to execute the embodiment shown in FIG. 5 or the embodiment or diagram shown in FIG. 8 . All sending operations and receiving operations performed by the first terminal device or network device (eg, core network device or access network device) in the embodiment shown in FIG. 10 or in the embodiment shown in FIG. 12 .
- the transceiving unit 1620 when performing a receiving operation, can be considered as a receiving unit, and when performing a transmitting operation, the transceiving unit 1620 can be considered as a transmitting unit.
- the transceiver unit 1620 can also be two functional modules, and the transceiver unit 1620 can be regarded as a general term for the two functional modules.
- the two functional modules include a receiving unit and a sending unit.
- the sending unit is used to complete the sending operation.
- the sending unit It can be used to perform all sending operations performed by the first terminal device or the network device in the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG. 12 ;
- the receiving unit is used to complete the receiving operation, for example, the receiving unit may be used to execute the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG. All receive operations performed by a terminal device or network device.
- processing unit 1610 and the transceiver unit 1620 can implement, refer to the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG.
- the processing unit 1610 and the transceiver unit 1620 can implement, refer to the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG.
- the terminal device or referring to the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG.
- the introduction of the operations performed by the network access device or core network device will not be repeated here.
- An embodiment of the present application further provides a communication apparatus, where the communication apparatus may be a terminal device or a circuit.
- the communication apparatus may be configured to perform the actions performed by the terminal device in each of the foregoing method embodiments.
- FIG. 17 shows a schematic structural diagram of a simplified terminal device.
- the terminal device takes a mobile phone as an example.
- the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device.
- the processor is mainly used to process communication protocols and communication data, control terminal equipment, execute software programs, and process data of software programs.
- the memory is mainly used to store software programs and data.
- the radio frequency circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal.
- Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
- Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal equipment may not have input and output devices.
- the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
- the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves.
- the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
- FIG. 17 only one memory and processor are shown in FIG. 17 . In an actual end device product, there may be one or more processors and one or more memories.
- the memory may also be referred to as a storage medium or a storage device or the like.
- the memory may be set independently of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.
- the antenna and the radio frequency circuit with the transceiver function may be regarded as the transceiver unit of the terminal device (the transceiver unit may be a functional unit, and the function unit can realize the sending function and the receiving function; alternatively, the transceiver unit may also be It includes two functional units, namely a receiving unit capable of realizing a receiving function and a transmitting unit capable of realizing a transmitting function), and a processor with a processing function is regarded as a processing unit of the terminal device. As shown in FIG. 17 , the terminal device includes a transceiver unit 1710 and a processing unit 1720 .
- the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like.
- the processing unit may also be referred to as a processor, a processing single board, a processing module, a processing device, and the like.
- the device for implementing the receiving function in the transceiver unit 1710 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 1710 may be regarded as a transmitting unit, that is, the transceiver unit 1710 includes a receiving unit and a transmitting unit.
- the transceiver unit may also sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit.
- the receiving unit may also sometimes be referred to as a receiver, receiver, or receiving circuit, or the like.
- the transmitting unit may also sometimes be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.
- the transceiver unit 1710 is configured to perform the sending operation and receiving on the terminal device side in the embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG. 12 .
- the processing unit 1720 is configured to perform the above-mentioned embodiment shown in FIG. 5 or the embodiment shown in FIG. 8 or the embodiment shown in FIG. 10 or the embodiment shown in FIG. other operations.
- the device may include a transceiver unit and a processing unit.
- the transceiver unit may be an input/output circuit and/or a communication interface;
- the processing unit may be an integrated processor, a microprocessor or an integrated circuit.
- processors mentioned in the embodiments of the present application may be a CPU, and may also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), ready-made Field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
- DSPs digital signal processors
- ASICs application specific integrated circuits
- FPGA Field programmable gate array
- a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
- the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
- the memory storage module
- memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
- the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
- the disclosed system, apparatus and method may be implemented in other manners.
- the apparatus embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
- the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
- the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
- the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
- the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer.
- the computer-readable medium may include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), Erasable programmable read only memory (erasable PROM, EPROM), electrically erasable programmable read only memory (electrically erasable programmable read only memory, EEPROM), compact disc read-only memory (compact disc read-only memory, CD- ROM), universal serial bus flash disk, removable hard disk, or other optical disk storage, magnetic disk storage medium, or other magnetic storage device, or capable of carrying or storing desired data in the form of instructions or data structures program code and any other medium that can be accessed by a computer.
- RAM random access memory
- ROM read-only memory
- PROM programmable read-only memory
- EPROM Erasable programmable read only memory
- EEPROM electrically erasable programmable read only memory
- compact disc read-only memory compact disc read-only memory
- CD- ROM compact disc read-only memory
- universal serial bus flash disk removable hard disk,
- RAM static random access memory
- DRAM dynamic random access memory
- SDRAM synchronous dynamic random access memory
- double data rate SDRAM double data rate SDRAM
- DDR SDRAM double data rate SDRAM
- ESDRAM enhanced synchronous dynamic random access memory
- SLDRAM synchronous link dynamic random access memory
- direct rambus RAM direct rambus RAM
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
本申请涉及一种通信方法及设备。在终端设备确定在第一DCP监听时机内不监听DCP的情况下,在第一组载波上,终端设备在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第二组载波上,终端设备在第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠。第一组载波包括配置给终端设备的一个或多个载波,第一组载波应用第一DRX配置,第一DRX持续时间对应第一DRX配置,第二组载波包括配置给终端设备的一个或多个载波,第二组载波应用第二DRX配置,第二DRX持续时间对应第二DRX配置。两种DRX配置的技术能够与唤醒信号结合使用,有助于进一步减小终端设备的功耗。
Description
相关申请的交叉引用
本申请要求在2020年09月27日提交中国国家知识产权局、申请号为202011032366.9、申请名称为“一种DCP监听方法、终端及网络设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中;本申请要求在2020年11月06日提交中国国家知识产权局、申请号为202011231197.1、申请名称为“一种通信方法及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种通信方法及设备。
在第五代移动通信技术(the 5th generation,5G)技术中,用户设备(user equipment,UE)需要进一步节省功耗。为此,在目前的非连续接收(discontinuous reception,DRX)机制下又引入一个指示信号,该指示信号为物理下行控制信道唤醒信号(physical downlink control channel wake-up signal,PDCCH-WUS)。该指示信号能够指示后续的DRX“激活时间”内UE是否需要唤醒、或者是否可以休眠。PDCCH-WUS在标准中又称为使用节能无线网络临时标识(power saving radio network tempory identity,PS-RNTI)加扰的带循环冗余校验的下行控制信息(downlink control information with cyclic redundancy check scrambled by PS-radio network tempory identity,DCP),DCP的信号形式可以为DCI。目前规定,在一次监听时机到来时,如果本次监听时机所包括的所有DCP监听时机(DCP occasion(s))均位于DRX激活时间(active time)内,则UE不在本次监听时机内进行监听,UE在本次监听时机所关联的DRX周期内的持续(On Duration)时间内默认唤醒;而如果本次监听时机所包括的至少一个DCP监听时机是位于DRX非激活时间(non-active time)内,则UE在位于DRX非激活时间内的DCP监听时机内进行监听。其中,一次监听时机可以包括一个或多个DCP监听时机(DCP occasion(s))。
目前,处于无线资源控制(radio resource control,RRC)连接(connected)态的用户设备(user equipment,UE)可以支持两种非连续接收(discontinuous reception,DRX)配置。但是目前并未将两种DRX配置的技术与唤醒信号结合使用,这影响了基站配置的灵活度。而且引入两种DRX配置是为了节省功能,唤醒信号的目的也是为了节省功耗,如果二者不能结合,则无法实现进一步降低UE功耗的目的。
发明内容
本申请实施例提供一种通信方法及设备,用于减小UE的功耗。
第一方面,提供第一种通信方法,该方法可由终端设备执行,或由芯片***执行,该芯片***能够实现终端设备的功能。其中,所述终端设备配置有第一组载波和第二组载波,所述第一组载波属于FR1,所述第一组载波包括配置给所述终端设备的一个或多个载波, 所述第一组载波应用第一DRX配置,所述第一DRX持续时间对应所述第一DRX配置,所述第二组载波属于FR2,所述第二组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波应用第二DRX配置,所述第二DRX持续时间对应第二DRX配置。该方法包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,所述终端设备确定在第一DCP监听时机内不监听DCP,所述第一DCP监听时机配置在所述第一组载波上。在第一组载波上,所述终端设备在所述第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第二组载波上,所述终端设备根据第一规则在所述第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠,其中,所述第一DRX持续时间对应所述第一DRX配置,所述第二DRX持续时间对应所述第二DRX配置,所述第一规则为预先设置的规则,或所述第一规则为来自网络设备的配置信息所配置的规则;或者,在所述第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP,则,所述终端设备在所述第一DCP监听时机内监听DCP;所述终端设备根据监听到的DCP的指示,在所述第一组载波上,在所述第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,有助于进一步减小终端设备的功耗。且规定了在结合的情况下的终端设备的行为,例如,终端设备对第一组载波对应的DCP监听时机的监听情况,既适用于第一组载波,也适用于第二组载波。这样,终端设备只需在第一组载波上监听DCP,无需在第二组载波上监听DCP,减小了终端设备监听DCP的功耗。而且终端设备在一组载波上的监听情况能够适用于两组载波,使得两组载波都能使用DCP机制,能够进一步减小终端设备在两组载波上的功耗。
第一方面,提供第一种通信方法,该方法可由终端设备执行,或由芯片***执行,该芯片***能够实现终端设备的功能。该方法包括:终端设备确定在第一DCP监听时机内是否监听DCP;在所述终端设备确定在所述第一DCP监听时机内不监听DCP的情况下,在第一组载波上,所述终端设备在所述第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第二组载波上,所述终端设备在所述第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠,其中,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一DRX配置,所述第一DRX持续时间对应所述第一DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波应用第二DRX配置,所述第二DRX持续时间对应所述第二DRX配置。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,并规定了在结合的情况下的终端设备的行为,例如,终端设备对第一组载波对应的DCP监听时机的监听情况,既适用于第一组载波,也适用于第二组载波。这样,终端设备只需在第一组载波上监听DCP,无需在第二组载波上监听DCP,减小了终端设备监听DCP的功耗。而且终端设备在一组载波上的监听情况能够适用于两组载波,使得两组载波都能使用DCP机制,能够进一步减小终端设备在两组载波上的功耗。
结合第二方面,在第二方面的第一种可选的实施方式中,所述第一DCP监听时机配置在所述第一组载波上。
网络设备可不必为第二组载波配置DCP监听时机,终端设备只需在第一组载波上的DCP监听时机内监听,该监听结果能够适用于两组载波。这样,两组载波都能使用DCP 机制,减小终端设备的功耗。而且终端设备无需在第二组载波上监听DCP,进一步减小了终端设备监听DCP的功耗。
结合第二方面或第二方面的第一种可选的实施方式,在第二方面的第二种可选的实施方式中,所述第一DRX持续时间在时域上位于所述第一DCP监听时机之后。
在第一组载波上,在时域上位于第一DCP监听时机之后的一个或多个DRX周期都可以与第一DCP监听时机关联,至于第一DCP监听时机究竟关联哪些DRX周期,可以通过协议规定,或者由网络设备配置。第一DCP监听时机如果关联多个DRX周期,这多个DRX周期在时域上可以连续,也可以不连续。第一DRX持续时间可包括第一DRX配置下第一DCP监听时机所关联的全部或部分DRX周期内的持续时间,或者说,第一DRX持续时间可包括第一组载波上,第一DCP监听时机所关联的全部或部分DRX周期内的持续时间。
结合第二方面或第二方面的第一种可选的实施方式或第二方面的第二种可选的实施方式,在第二方面的第三种可选的实施方式中,终端设备确定是否在第一DCP监听时机内监听DCP,包括:
在所述第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间;或,
在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或,
在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间。
终端设备要确定是否在第一DCP监听时机内监听DCP,可以有不同的确定方式。例如终端设备可以根据第一DCP监听时机的时域位置确定,这种确定方式对于终端设备来说易于实现,而且也有利于与已有的技术兼容。或者,终端设备可根据DCI的大小预算来确定,这种确定方式较为简单,也较为合理。或者,终端设备也可以结合这两种确定方式来一并确定,可以使得确定结果更为准确。本申请实施例提供了多种确定方式,究竟选择哪种确定方式,可由终端设备自行决策,或者由网络设备配置,或者也可以默认,或者也可以通过协议规定等。
结合第一方面或第一方面的第一种可选的实施方式至第一方面的第三种可选的实施方式中的任一种可选的实施方式,在第一方面的第四种可选的实施方式中,所述方法还包括:所述终端设备接收来自网络设备的配置信息,所述配置信息用于配置:在所述终端设 备在DCP监听时机内不监听的情况下,所述终端设备在所述DCP监听时机关联的所述第二DRX持续时间内唤醒或休眠。
如果终端设备在第一组载波上的一个DCP监听时机内不监听,则终端设备在该DCP监听时机所关联的DRX持续时间内唤醒还是休眠,可以是默认规则,或者也可以通过协议规定,或者也可以由网络设备配置。如果由网络设备配置,则网络设备可以根据终端设备在第二组载波上的业务传输情况来配置,使得终端设备在第二组载波上的休眠或唤醒更为符合终端设备的业务需求。
结合第一方面或第一方面的第一种可选的实施方式至第一方面的第四种可选的实施方式中的任一种可选的实施方式,在第一方面的第五种可选的实施方式中,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,所述终端设备在所述第一DCP监听时机内监听DCP;所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒。
如果终端设备在第一DCP监听时机内监听,那么终端设备根据在第一DCP监听时机内监听到的DCP的指示,在两组载波上休眠或唤醒,即,终端设备在第一DCP监听时机内的监听结果能够指导终端设备在两组载波上的行为,减少了终端设备监听DCP的过程,节省功耗。
结合第一方面的第五种可选的实施方式,在第一方面的第六种可选的实施方式中,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP、且所述第一DCP指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述终端设备在所述第一DCP监听时机内未接收来自所述网络设备的DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠。
结合第一方面的第五种可选的实施方式,在第一方面的第七种可选的实施方式中,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内唤醒,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP、且所述第一DCP指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒;或,在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒。
结合第一方面的第五种可选的实施方式,在第一方面的第八种可选的实施方式中,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP,且所述第一DCP包括第一指示信息和第二指示信息;其中,在所述第一指示信息指示唤醒, 以及所述第二指示信息指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒;或,在所述第一指示信息指示休眠,以及所述第二指示信息指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述第一指示信息指示唤醒,以及所述第二指示信息指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述第一指示信息指示休眠,以及所述第二指示信息指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒。
结合第一方面的第五种可选的实施方式至第一方面的第八种可选的实施方式中的任一种可选的实施方式,在第一方面的第九种可选的实施方式中,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,包括:所述终端设备在所述第一DRX持续时间的起始时刻不启动以及不重启第一DRX持续时间定时器,所述第一DRX持续时间定时器对应所述第一DRX配置。
结合第一方面的第五种可选的实施方式至第一方面的第九种可选的实施方式中的任一种可选的实施方式,在第一方面的第十种可选的实施方式中,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,包括:所述终端设备在所述第一DRX持续时间的起始时刻启动或重启第一DRX持续时间定时器,所述第一DRX持续时间定时器对应所述第一DRX配置。
结合第一方面的第五种可选的实施方式至第一方面的第十种可选的实施方式中的任一种可选的实施方式,在第一方面的第十一种可选的实施方式中,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠,包括:所述终端设备在所述第二DRX持续时间的起始时刻不启动以及不重启第二DRX持续时间定时器,所述第二DRX持续时间定时器对应所述第二DRX配置。
结合第一方面的第五种可选的实施方式至第一方面的第十一种可选的实施方式中的任一种可选的实施方式,在第一方面的第十二种可选的实施方式中,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒,包括:所述终端设备在所述第二DRX持续时间的起始时刻启动或重启第二DRX持续时间定时器,所述第二DRX持续时间定时器对应所述第二DRX配置。
通过如上的方案,提供了终端设备在DRX持续时间内唤醒或休眠的一种实现方式。
结合第一方面或第一方面的第一种可选的实施方式至第一方面的第十二种可选的实施方式中的任一种可选的实施方式,在第一方面的第十三种可选的实施方式中,所述第一组载波所属的频率范围与所述第二组载波所属的频率范围不同;或,所述第二组载波所属的频率范围对应的频率大于所述第一组载波所属的频率范围对应的频率;或,所述第一组载波对应的DRX激活时间的长度大于或等于所述第二组载波对应的DRX激活时间的长度。
例如,为终端设备配置的两组载波所属的频率范围不同,从而使得终端设备能够工作在更大的频率范围下。例如,第一组载波的频率属于FR1,第二组载波的频率属于FR2。由于第二组载波的频率大于第一组载波的频率,则终端设备在第二组载波上工作时功耗会更大,因此本申请实施例可以让终端设备只需在第一组载波上监听DCP,无需在第二组载 波上监听DCP,从而节省终端设备在第二组载波上工作所带来的功耗。另外,网络设备可能在第一组载波上发送DCI,该DCI用于调度第二组载波上的数据,因此终端设备可能需要在第一组载波上接收对于第二组载波的调度信息。为此,可以使得第一组载波对应的DRX激活时间的长度大于或等于第二组载波对应的DRX激活时间的长度,可选的,第一组载波对应的DRX激活时间可以覆盖第二组载波对应的DRX激活时间,从而使得终端设备在第一组载波的DRX激活时间内能够接收对应于第二组载波的调度信息,减小终端设备因无法接收调度信息而导致无法在第二组载波上接收数据或发送数据的概率,减小业务传输时延。
第二方面,提供第二种通信方法,该方法可由终端设备执行,或由芯片***执行,该芯片***能够实现终端设备的功能。该方法包括:在终端设备确定在第一DCP监听时机内不监听DCP的情况下,所述终端设备确定在第二DCP监听时机内是否监听DCP,所述第一DCP监听时机配置在第一组载波上,所述第二DCP监听时机配置在第二组载波上,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波应用第二DRX配置;在所述终端设备确定在所述第二DCP监听时机内监听DCP的情况下,所述终端设备在所述第二DCP监听时机内监听DCP,并根据对DCP的监听情况,在所述第二组载波上,在所述第二DCP监听时机关联的第二DRX持续时间内休眠或唤醒,所述第二DRX持续时间对应所述第二DRX配置。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,并规定了在结合的情况下的终端设备的行为。例如,UE优先监听第一DCP监听时机,如果能够监听第一DCP监听时机,则UE无需监听第二DCP监听时机,以节省UE监听DCP监听时机所带来的功耗。如果UE不能监听第一DCP监听时机,则UE还可以确定是否能够监听第二DCP监听时机,使得UE的行为尽量在监听结果的指示下进行,以更为符合网络设备的要求。在本申请实施例中,网络设备可以为第二组载波配置第二DCP监听时机,使得网络设备对于UE在第二组载波上的行为的控制力更强,也增加了网络设备调度的灵活性。
结合第二方面,在第二方面的第一种可选的实施方式中,所述方法还包括:所述终端设备确定在所述第一DCP监听时机内是否监听DCP。
结合第二方面或第二方面的第一种可选的实施方式,在第二方面的第二种可选的实施方式中,所述方法还包括:在所述终端设备确定在所述第二DCP监听时机内不监听DCP的情况下,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒。
如果终端设备在第二DCP监听时机内也不监听DCP,那么终端设备在第二组载波上的行为可以是默认的,或者也可以通过协议规定。例如,终端设备在第二组载波上可以在第二DRX持续时间内唤醒,以进行业务传输。或者,终端设备在第二组载波上也可以在第二DRX持续时间内休眠,以减小终端设备的功耗。
结合第二方面或第二方面的第一种可选的实施方式或第二方面的第二种可选的实施方式,在第二方面的第三种可选的实施方式中,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DCP监听时机关联的第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第三种可选的实施方式中的任一种可选的实施方式,在第二方面的第四种可选的实施方式中,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,在所述第二组载波上,所述终端设备不在所述第二DCP监听时机内进行监听。
如果终端设备能够在第一DCP监听时机内监听DCP,则终端设备可根据在第一DCP监听时机内监听到的DCP的指示,确定在第一组载波上的行为,以及确定在第二组载波上的行为。在这种情况下,终端设备无需监听第二DCP监听时机,减小了终端设备由于监听DCP所带来的功耗。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第四种可选的实施方式中的任一种可选的实施方式,在第二方面的第五种可选的实施方式中,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内不监听DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DCP监听时机关联的第一DRX持续时间内唤醒,所述第一DRX持续时间对应所述第一DRX配置。
如果终端设备在第一DCP监听时机内不监听DCP,那么终端设备在第一组载波上的行为可以是默认的,或者也可以通过协议规定。例如终端设备在第一DRX持续时间内唤醒,以进行业务传输。又例如,终端设备在第一DRX持续时间内也可以休眠,以节省终端设备的功耗。
结合第二方面的第一种可选的实施方式,在第二方面的第六种可选的实施方式中,所述终端设备确定在所述第一DCP监听时机内是否监听DCP,包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间;或,在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间。
终端设备要确定是否在第一DCP监听时机内监听DCP,可以有不同的确定方式。例如终端设备可以根据第一DCP监听时机的时域位置确定,这种确定方式对于终端设备来说易于实现,而且也有利于与已有的技术兼容。或者,终端设备可根据DCI的大小预算来确定,这种确定方式较为简单,也较为合理。或者,终端设备也可以结合这两种确定方式来一并确定,可以使得确定结果更为准确。本申请实施例提供了多种确定方式,究竟选择哪种确定方式,可由终端设备自行决策,或者由网络设备配置,或者也可以默认,或者也可以通过协议规定等。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第六种可选的实施方式中的任一种可选的实施方式,在第二方面的第七种可选的实施方式中,所述终端设备确定在第二DCP监听时机内是否监听DCP,包括:在所述第二DCP监听时机的时域位置位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第二DCP监听时机的时域位置没有位于或部分位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第二DRX激活时间为所述第二DRX配置对应的DRX激活时间;或,在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内不监听DCP;或,在所述第二DCP监听时机的时域位置位于第二DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内监听DCP;或者,在所述第二DCP监听时机的时域位置位于第二DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内不监听DCP。
终端设备要确定是否在第二DCP监听时机内监听DCP,可以有不同的确定方式。例如终端设备可以根据第二DCP监听时机的时域位置确定,这种确定方式对于终端设备来说易于实现,而且也有利于与已有的技术兼容。或者,终端设备可根据DCI的大小预算来确定,这种确定方式较为简单,也较为合理。或者,终端设备也可以结合这两种确定方式来一并确定,可以使得确定结果更为准确。本申请实施例提供了多种确定方式,究竟选择哪种确定方式,可由终端设备自行决策,或者由网络设备配置,或者也可以默认,或者也可以通过协议规定等。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第七种可选的实施方式中的任一种可选的实施方式,在第二方面的第八种可选的实施方式中,所述终端设备确定在所述第一DCP监听时机内不监听DCP,且确定在所述第二DCP监听时机内监听DCP,包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且所述第二DCP监听时机的时域位置没有位于或部分位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP,以及,确定在所述第二DCP监听时机内监听DCP。
第三方面,提供第三种通信方法,该方法可由终端设备执行,或由芯片***执行,该芯片***能够实现终端设备的功能。该方法包括:终端设备在第一载波上接收来自网络设备的DCI,所述第一载波属于第一组载波,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一DRX配置;所述终端设备根据所述DCI包括的第二指示信息确定在第二组载波上,在所述DCI关联的第二DRX持续时间内休眠或唤醒,所述第二DRX持续时间对应第二DRX配置,所述第二组载波应用所述第二DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波,其中,当所述DCI包括的第二字段的取值为第一值时,用于指示所述DCI包括所述第二指示信息。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,而且本申请实施例无需配置DCP,而是通过普通的DCI实现DCP的功能,减少了UE需要监听的DCI size 的个数,或者使得UE能够监听更多的DCI size,也简化了网络设备和UE的实现。而且可由网络设备通过相应的指示信息指示UE在载波组上的唤醒或休眠,指示方式更为灵活,更符合UE的业务传输需求,也增加了网络设备调度的灵活性。另外,本申请实施例也避免了通过默认方式规定UE在第二组载波上在第二DRX持续时间内唤醒,能够降低UE的功耗。
结合第三方面,在第三方面的第一种可选的实施方式中,当所述第二字段的取值为第二值时,用于指示所述DCI不包括所述第二指示信息。
如果是用于实现DCP功能的DCI,可以通过取值为第一值的第二字段来指示该DCI还包括第二指示信息,而如果不是用于实现DCP功能的DCI,则第二字段的取值可以不是第一值,例如为普通取值,则终端设备根据第二字段的取值就能确定该DCI是否包括第二指示信息,指示较为明确,而且也无需额外添加其他的指示信息,有助于与已有的技术兼容。
结合第三方面或第三方面的第一种可选的实施方式,在第三方面的第一种可选的实施方式中,所述第二字段包括如下的一个或多个字段:FDRA字段、MCS字段、NDI字段、RV字段、HARQ进程号字段、天线端口字段、或、解调参考信号序列初始化字段。
第二字段可以包括如上的一个或多个字段,或者第二字段除了包括如上字段外还可以包括其他字段,或者第二字段也可以不包括如上字段,而是包括其他字段。所述其他字段例如为DCI所包括的除了如上字段外的其他的已有的字段,或者也可以是在DCI中新增的字段。
结合第三方面或第三方面的第一种可选的实施方式或第三方面的第二种可选的实施方式,在第三方面的第三种可选的实施方式中,所述方法还包括:所述终端设备根据所述DCI包括的第一指示信息,确定在所述第一组载波上,在所述DCI关联的第一DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置,其中,当所述第二字段的取值为所述第一值时,还用于指示所述DCI包括所述第一指示信息。
如果第二字段的取值为第一值,那么该DCI还可以包括第一指示信息,而如果第二字段的取值不是第一值,则该DCI不包括第一指示信息。在这种实施方式下,网络设备通过第二指示信息和第一指示信息分别指示了两组载波的休眠或唤醒,使得UE的行为更为明确,也更为符合业务需求。
结合第三方面或第三方面的第一种可选的实施方式或第三方面的第二种可选的实施方式,在第三方面的第四种可选的实施方式中,
所述方法还包括:所述终端设备在所述第一组载波上,在所述DCI关联的第一DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置;
或,
所述终端设备根据所述DCI包括的第二指示信息确定在第二组载波上,在所述DCI关联的第二DRX持续时间内休眠或唤醒,包括:所述终端设备确定在所述第一组载波上不监听DCP时,所述终端设备根据所述DCI包括的第二指示信息确定在所述第二组载波上,在所述DCI关联的所述第二DRX持续时间内休眠或唤醒;
所述方法还包括:所述终端设备在所述第一组载波上,在所述DCI关联的第一DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置。
DCI可以不对UE在第一组载波上的行为进行指示,那么,可以默认(或者,协议规 定),UE在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒。因为如果第二指示信息指示UE在第二组载波上在第二DRX持续时间内唤醒,且网络设备又需要在第一组载波上调度该UE在第二组载波上的数据传输,那么如果UE在第一组载波上在第一DRX持续时间内休眠,就可能无法接收来自网络设备的调度信息,从而无法在第二组载波上进行数据传输。因此可以默认(或者,协议规定)UE在第一组载波上在第一DRX持续时间内休眠,以减少UE错过调度信息的概率,减小业务的传输时延。或者,可以默认(或者,协议规定),UE在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,通过这种方式能够节省UE的功耗。
第四方面,提供第四种通信方法。该方法可由网络设备执行,或由芯片***执行,该芯片***能够实现网络设备的功能。示例性地,网络设备为接入网设备。示例性地,接入网设备为基站。该方法包括:网络设备在第一载波上向终端设备发送DCI,所述第一载波属于第一组载波,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一DRX配置,其中,当所述DCI包括的第二字段的取值为第一值时,用于指示所述DCI包括第二指示信息,所述第二指示信息用于指示在第二组载波上,在所述DCI关联的第二DRX持续时间内休眠或唤醒,所述第二DRX持续时间对应第二DRX配置,所述第二组载波应用所述第二DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波。
结合第四方面,在第四方面的第一种可选的实施方式中,当所述第二字段的取值为第二值时,用于指示所述DCI不包括所述第二指示信息。
结合第四方面或第四方面的第一种可选的实施方式,在第四方面的第二种可选的实施方式中,所述第二字段包括如下的一个或多个字段:FDRA字段、MCS字段、NDI字段、RV字段、HARQ进程号字段、天线端口字段、或、解调参考信号序列初始化字段。
结合第四方面或第四方面的第一种可选的实施方式或第四方面的第二种可选的实施方式,在第四方面的第三种可选的实施方式中,当所述第二字段的取值为所述第一值时,还用于指示所述DCI包括所述第一指示信息,所述第一指示信息用于指示在所述第一组载波上,在所述DCI关联的第一DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置。
关于第四方面或第四方面的各种可选的实施方式所带来的技术效果,可参考对于第三方面或相应的实施方式的技术效果的介绍。
第五方面,提供第五种通信方法,该方法可由终端设备执行,或由芯片***执行,该芯片***能够实现终端设备的功能。该方法包括:终端设备在第一载波上接收第二DCI,所述第一载波属于第一组载波,所述第二DCI用于调度第二组载波上的数据,其中,所述第一组载波应用第一DRX配置,所述第二组载波应用第二DRX配置,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波包括配置给所述终端设备的一个或多个载波;所述终端设备启动或重启第二DRX非激活定时器,并将所述第二DRX非激活定时器的时长设置为所述第二DRX配置所配置的DRX非激活定时器的时长。
在本申请实施例中,两种DRX配置的技术能够与跨载波调度技术结合使用,在实现跨载波调度时,UE在第一组载波上能够接收来自网络设备的用于调度第二组载波上的数据的DCI,以及UE在第二组载波上也能接收数据或发送数据,使得在两种DRX配置技术的背景下,跨载波调度技术得以实现。而且本申请实施例可以根据不同的情况将对应于第 一组载波的第一DRX非激活定时器的时长设置为不同的时长,使得第一DRX非激活定时器的时长更为符合当前的业务传输需求,也更节省UE的功耗。
结合第五方面,在第五方面的第一种可选的实施方式中,所述终端设备启动或重启第二DRX非激活定时器,包括:所述终端设备在所述第二DCI接收完毕后的第一个时域符号,启动或重启所述第二DRX非激活定时器。
时域符号例如为正交频分复用(orthogonal frequency division multiplexing,OFDM)符号。
结合第五方面或第五方面的第一种可选的实施方式,在第五方面的第二种可选的实施方式中,所述第二DCI包括第二指示信息,所述第二指示信息用于指示启动或重启所述第二DRX非激活定时器。
第二指示信息可通过第二DCI中的已有字段承载,例如第二DCI包括的已有字段中有预留比特,则可以通过预留比特承载;或者,可以在第二DCI中新增一个或多个比特,以承载第二指示信息。通过第二DCI进行指示,使得UE更为明确UE的行为。
结合第五方面或第五方面的第一种可选的实施方式或第五方面的第二种可选的实施方式,在第五方面的第三种可选的实施方式中,在终端设备在第一载波上接收第二DCI之后,所述方法还包括:所述终端设备启动或重启第一DRX非激活定时器,并将所述第一DRX非激活定时器的时长设置为所述第一DRX配置所配置的DRX非激活定时器的时长,或设置为所述第二DRX配置所配置的DRX非激活定时器的时长,所述第一DRX非激活定时器对应所述第一DRX配置。
由于第二组载波上有数据传输,而第二DCI是跨载波调度,那么后续网络设备还可能通过跨载波调度的方式来调度第二组载波上的数据。另外,网络设备也可能在第一组载波上调度第一组载波上的数据。因此,可以延长UE在第一组载波上的DRX激活时间,以接收用于调度数据的DCI。UE要延长UE在第一组载波上的DRX激活时间,一种实现方式为,通过第一DRX非激活定时器来延长。例如,UE可将第一DRX非激活定时器的时长设置为第一DRX非激活定时器原本的时长,即第一DRX配置所配置的DRX非激活定时器的时长。这种设置方式较为简单,也是UE容易实现的设置。又例如,UE也可将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长,可理解为,UE将第一DRX非激活定时器的时长设置为第二DRX非激活定时器的时长。如果采用这种方式,则UE在第一组载波上的DRX激活时间的持续时间与UE在第二组载波上的DRX激活时间的持续时间可能是一致的,UE在第一组载波上既能接收用于调度第二组载波的数据的DCI,也不会因为在第一组载波上的DRX激活时间过长而导致过于耗电。
结合第五方面的第三种可选的实施方式,在第五方面的第四种可选的实施方式中,在所述终端设备将所述第一DRX非激活定时器的时长设置为所述第二DRX配置所配置的DRX非激活定时器的时长的情况下,所述方法还包括:在所述终端设备重启所述第一DRX非激活定时器之前,确定所述第一DRX非激活定时器处于运行状态,且确定所述第一DRX非激活定时器的剩余时长要短于所述第二DRX配置所配置的DRX非激活定时器的时长。
UE可以不必在任何情况下均启动或重启第一DRX非激活定时器,而是可以先确定是否需要启动或重启第一DRX非激活定时器。例如,UE在启动或重启第一DRX非激活定时器之前,如果第一DRX非激活定时器处于运行状态,则UE可以确定第一DRX非激活定时器的剩余时长与第二DRX配置所配置的DRX非激活定时器的时长之间的大小关系。 如果第一DRX非激活定时器的剩余时长要短于第二DRX配置所配置的DRX非激活定时器的时长,那么UE可以将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长;或者,如果第一DRX非激活定时器的剩余时长要长于或等于第二DRX配置所配置的DRX非激活定时器的时长,那么UE可以不必重启第一DRX非激活定时器。通过这种方式,避免第一DRX非激活定时器的时长忽长忽短,减小UE处理的复杂度。
结合第五方面的第三种可选的实施方式,在第五方面的第五种可选的实施方式中,在所述终端设备启动或重启第一DRX非激活定时器,并将所述第一DRX非激活定时器的时长设置为所述第一DRX配置所配置的DRX非激活定时器的时长之前,所述方法还包括:所述终端设备在所述第一组载波上接收第一DCI,所述第一DCI用于调度所述第一组载波上的数据。
如果UE在启动或重启第一DRX非激活定时器之前在第一组载波上接收了第一DCI,且第一DCI用于调度UE在第一组载波上接收数据或发送数据,那么UE可以将第一DRX非激活定时器的时长设置为第一DRX配置所配置的DRX非激活定时器的时长,以满足UE在第一组载波上的接收数据或发送数据的需求,也能满足UE在第一组载波上接收对应于第一组载波的数据的调度的需求。
结合第五方面的第三种可选的实施方式,在第五方面的第六种可选的实施方式中,所述第二DCI包括第一指示信息,所述第一指示信息用于指示启动或重启所述第一DRX非激活定时器。
UE究竟是否要启动第一DRX非激活定时器,可以默认,或者通过协议规定,或者也可以由网络设备指示。例如,第二DCI可以包括第一指示信息,第一指示信息可以指示启动或重启第一DRX非激活定时器。通过第二DCI进行指示,使得UE更为明确UE的行为。
结合第五方面的第六种可选的实施方式,在第五方面的第七种可选的实施方式中,所述第一指示信息还用于指示将所述第一DRX非激活定时器的定时时长设置为所述第一DRX配置所配置的DRX非激活定时器的时长,或指示将所述第一DRX非激活定时器的定时时长设置为所述第二DRX配置所配置的DRX非激活定时器的时长。
如果第二DCI包括第一指示信息,那么第一指示信息除了可以指示UE启动或重启第一DRX非激活定时器外,还可以指示如何设置第一DRX非激活定时器的时长。则UE无需自行确定第一DRX非激活定时器的时长应该如何设置,简化UE的实现。
结合第五方面或第五方面的第一种可选的实施方式或第五方面的第二种可选的实施方式,在第五方面的第八种可选的实施方式中,所述方法还包括:所述终端设备将所述终端设备在所述第一组载波上的DRX激活时间的结束时刻,延长到与所述终端设备在所述第二组载波上的DRX激活时间的结束时刻相同。
UE要延长UE在第一组载波上的DRX激活时间,一种实现方式为通过第一DRX非激活定时器来延长,而另一种实现方式无需借助第一DRX非激活定时器,而是可以直接延长第一组载波上的DRX激活时间的结束时刻,例如将UE在第一组载波上的DRX激活时间的结束时刻延长到与UE在第二组载波上的DRX激活时间的结束时刻相同。如果采用这种方式,则UE在第一组载波上的DRX激活时间的持续时间与UE在第二组载波上的DRX激活时间的持续时间是一致的,UE在第一组载波上既能接收用于调度第二组载波的 数据的DCI,也不会因为在第一组载波上的DRX激活时间过长而导致过于耗电。而且这种方式也无需借助于第一DRX非激活时间定时器,减少了UE维护第一DRX非激活时间定时器所带来的功耗。
结合第五方面或第五方面的第一种可选的实施方式至第五方面的第八种可选的实施方式,在第五方面的第九种可选的实施方式中,所述第二DCI用于指示下行数据的新传或上行数据的新传。
第六方面,提供一种通信装置。所述通信装置可以包括用于执行第一方面或第一方面的任一可选的实施方式中的方法的模块,例如包括收发单元和处理单元。可选的,还可以包括存储单元。
第七方面,提供一种通信装置。所述通信装置可以包括用于执行第二方面或第二方面的任一可选的实施方式中的方法的模块,例如包括收发单元和处理单元。可选的,还可以包括存储单元。
第八方面,提供一种通信装置。所述通信装置可以包括用于执行第三方面或第三方面的任一可选的实施方式中的方法的模块,例如包括收发单元和处理单元。可选的,还可以包括存储单元。
第九方面,提供一种通信装置。所述通信装置可以包括用于执行第四方面或第四方面的任一可选的实施方式中的方法的模块,例如包括收发单元和处理单元。可选的,还可以包括存储单元。
第十方面,提供一种通信装置。所述通信装置可以包括用于执行第五方面或第五方面的任一可选的实施方式中的方法的模块,例如包括收发单元和处理单元。可选的,还可以包括存储单元。
第十一方面,提供一种芯片***,所述芯片***包括一个或多个处理器,以及包括通信接口,所述处理器与所述通信接口耦合,用于实现上述任意一个方面所提供的方法。可选的,所述芯片***还可以包括存储器,例如,所述处理器可以读取并执行所述存储器所存储的软件程序,以实现上述任意一个方面所提供的方法。
第十二方面,提供第一通信***。所述第一通信***包括第六方面所述的通信装置或第十一方面所述的芯片***(用于实现上述第一方面或第一方面的任一种可选的实施方式所提供的方法)。
第十三方面,提供第二通信***。所述第二通信***包括第七方面所述的通信装置或第十一方面所述的芯片***(用于实现上述第二方面或第二方面的任一种可选的实施方式所提供的方法)。
第十四方面,提供第三通信***。所述第二通信***包括第八方面所述的通信装置或第十一方面所述的芯片***(用于实现上述第三方面或第三方面的任一种可选的实施方式所提供的方法),以及包括第九方面所述的通信装置或第十一方面所述的芯片***(用于实现上述第四方面或第四方面的任一种可选的实施方式所提供的方法)。
第十五方面,提供第四通信***。所述第二通信***包括第十方面所述的通信装置或第十一方面所述的芯片***(用于实现上述第五方面或第五方面的任一种可选的实施方式所提供的方法)。
第十六方面,提供一种计算机可读存储介质,所述计算机可读存储介质用于存储计算机程序,当所述计算机程序在计算机上运行时,使得所述计算机执行上述任意一个方面所 提供的方法。
第十七方面,提供一种包含指令的计算机程序产品,所述计算机程序产品用于存储计算机程序,当所述计算机程序在计算机上运行时,使得所述计算机执行上述任意一个方面所提供的方法。
图1为DRX机制的一种示意图;
图2为DCP的时域位置的一种示意图;
图3为两组DRX配置的一种示意图;
图4为本申请实施例的一种应用场景的示意图;
图5为本申请实施例提供的第一种通信方法的流程图;
图6为本申请实施例中UE在第一DCP监听时机的监听结果能够决定UE在两组载波上的行为的一种示意图;
图7为本申请实施例中网络设备跨载波调度的示意图;
图8为本申请实施例提供的第二种通信方法的流程图;
图9为本申请实施例中UE在第一DCP监听时机的监听结果能够决定UE在第一组载波上的行为,以及UE在第二DCP监听时机的监听结果能够决定UE在第二组载波上的行为的一种示意图;
图10为本申请实施例提供的第三种通信方法的流程图;
图11本申请实施例中UE在第一组载波上接收的DCI能够指示UE在两组载波上的休眠或唤醒的一种示意图;
图12为本申请实施例提供的第四种通信方法的流程图;
图13为本申请实施例中第一DRX非激活定时器的时长大于第二DRX非激活定时器的时长的一种示意图;
图14为本申请实施例中将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长的一种示意图;
图15为本申请实施例中延长UE在第一组载波上的DRX激活时间的一种示意图;
图16为本申请实施例提供的一种通信装置的一种示意性框图;
图17为本申请实施例提供的又一种通信装置的一种示意性框图。
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。
以下,对本申请实施例中的部分用语进行解释说明,以便于本领域技术人员理解。
本申请实施例中,终端设备是一种具有无线收发功能的设备,可以是固定设备,移动设备、手持设备、穿戴设备、车载设备,或内置于上述设备中的无线装置(例如,通信模块或芯片***等)。所述终端设备用于连接人,物,机器等,可广泛用于各种场景,例如包括但不限于以下场景:蜂窝通信、设备到设备通信(device-to-device,D2D)、车到一切(vehicle to everything,V2X)、机器到机器/机器类通信(machine-to-machine/machine-type communications,M2M/MTC)、物联网(internet of things,IoT)、虚拟现实(virtual reality,VR)、增强现实(augmented reality,AR)、工业控制(industrial control)、无人驾驶(self driving)、远程医疗(remote medical)、智能电网(smart grid)、智能家具、智能办公、智能穿戴、智能交通,智慧城市(smart city)、无人机、机器人等场景的终端设备。所述终端设备有时可称为UE、终端、接入站、UE站、远方站、无线通信设备、或用户装置等等,为描述方便,本申请实施例中将终端设备以UE为例进行说明。
本申请实施例中的网络设备,例如包括接入网设备,和/或核心网设备。所述接入网设备为具有无线收发功能的设备,用于与所述终端设备进行通信。所述接入网设备包括但不限于上述通信***中的基站(BTS,Node B,eNodeB/eNB,或gNodeB/gNB)、收发点(transmission reception point,TRP),第三代合作伙伴计划(3rd generation partnership project,3GPP)后续演进的基站,WiFi***中的接入节点,无线中继节点,无线回传节点等。所述基站可以是:宏基站,微基站,微微基站,小站,中继站等。多个基站可以支持上述提及的同一种接入技术的网络,也可以支持上述提及的不同接入技术的网络。基站可以包含一个或多个共站或非共站的传输接收点。网络设备还可以是云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器、集中单元(centralized unit,CU),和/或分布单元(distributed unit,DU)。网络设备还可以是服务器,可穿戴设备,或车载设备等。例如,车到一切(vehicle to everything,V2X)技术中的网络设备可以为路侧单元(road side unit,RSU)。以下对接入网设备以为基站为例进行说明。所述通信***中的多个网络设备可以为同一类型的基站,也可以为不同类型的基站。基站可以与终端设备进行通信,也可以通过中继站与终端设备进行通信。终端设备可以与不同接入技术中的多个基站进行通信。所述核心网设备用于实现移动管理,数据处理,会话管理,策略和计费等功能。不同接入技术的***中实现核心网功能的设备名称可以不同,本申请并不对此进行限定。以5G***为例,所述核心网设备可包括访问和移动管理功能(access and mobility management function,AMF)、会话管理功能(session management function,SMF)、或用户面功能(user plane function,UPF)等。以4G***为例,所述核心网设备可包括移动性管理实体(mobility management entity)等。
本申请实施例中,用于实现网络设备的功能的装置可以是网络设备,也可以是能够支持网络设备实现该功能的装置,例如芯片***,该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中,以用于实现网络设备的功能的装置是网络设备为例,描述本申请实施例提供的技术方案。
另外,因为本申请实施例更多地是涉及到接入网设备,因此如无特殊说明,则后文所述的“网络设备”均是指接入网设备。
本申请实施例中,对于名词的数目,除非特别说明,表示“单数名词或复数名词”,即"一个或多个”。“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。例如,A/B,表示:A或B。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),表示:a,b,c,a和b,a和c,b和c,或a和b和c,其中a,b,c可以是单个,也可以是多个。
以及,除非有相反的说明,本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分,不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如,第一DCI和第二DCI,可以是同一个DCI,也可以是不同的DCI,且,这种名称也并不是表示这两个DCI的时间长度、发送顺序、内容、优先级或者重要程度等的不同。
为了更好地理解本申请实施例的技术方案,下面介绍本申请实施例涉及的一些技术特征。
1、DRX。
5G新空口(new radio,NR)技术沿用了长期演进技术(long term evolution,LTE)中的非连续接收(Discontinuous Reception,DRX)机制,DRX机制主要是为节省功耗而引入。其中,基站为UE配置的DRX周期可以是长DRX周期,也可以是短DRX周期,其中长DRX周期是默认配置,而短DRX周期是可选配置。如果一个UE被配置了长DRX周期而未被配置短DRX周期,则UE在同一个时刻会使用长DRX周期或使用短DRX周期,即,UE不会同时使用两种DRX周期。UE会在使用短DRX周期时开启DRX短周期定时器(drx-ShortCycleTimer),当drx-ShortCycleTimer超时时,则UE隐式转换为使用长DRX周期。其中,drx-ShortCycleTimer的单位为短DRX周期的个数。
DRX周期由“On Duration”部分和“DRX时机(Opportunity for DRX)”部分组成。在“On Duration”时间内,UE监听(monitor)并接收PDCCH,在“Opportunity for DRX”时间内,UE可以不监听或不接收PDCCH,以减小功耗,对此可参考图1。其中,监听并接收PDCCH,可以理解为监听并接收承载在PDCCH上的DCI。DRX机制包括DRX持续时间定时器(drx-onDurationTimer),在每个DRX周期开始(即每个DRX周期的On Duration开始)时,UE需要开启drx-onDurationTimer。当drx-onDurationTimer超时,则表示“On Duration”时间结束,此时UE进入该DRX周期内的“Opportunity for DRX”时间。
DRX机制还包括DRX非激活定时器(drx-InactivityTimer),当UE接收到用于指示数据初传(new transmission)的PDCCH,由于UE很可能在接下来的时间内继续被基站调度,则UE需要开启drx-InactivityTimer,在drx-InactivityTimer运行时间内,UE需要监听并接收PDCCH。
DRX机制还包括DRX重传定时器(drx-RetransmissionTimer),drx-RetransmissionTimer具体还分为上行drx-RetransmissionTimer和下行drx-RetransmissionTimer。由于基站可能在drx-RetransmissionTimer运行时间内调度UE的重传,因此在drx-RetransmissionTimer运行时间内UE需要监听并接收PDCCH。
综上分析,UE需要在drx-onDurationTimer、drx-InactivityTimer、上行drx-RetransmissionTimer、以及下行drx-RetransmissionTimer运行过程中监听并接收PDCCH,因此这些定时器的运行时间均认为是DRX“激活时间”,在DRX激活时间内UE需要醒来准备接收信令或数据。而除了上述所有定时器的运行时间外,如果在某个时刻上述定时器均未运行,则UE在该时刻可能可以不需要监听并接收PDCCH,这种时间就称为DRX“休眠时间”,在DRX休眠时间内,UE可以休眠。一般来说,UE在DRX“激活时间”的功耗高于在DRX“休眠时间”的功耗。需要注意的是,在DRX机制之外的其他一些功能中,也可能限定某些情况下UE需要处于“激活时间”或“休眠时间”,这与DRX机制并不冲突,而是取并集的关系。因此,UE最终实际处于“激活时间”还是“休眠时间”,还需要从UE的各个功能整体地确定。
2、载波聚合(carrier aggregation,CA)和跨载波调度(cross-carrier scheduling)。
载波聚合技术可以将多个(例如,两个或两个以上)成员载波(component carrier,CC)聚合在一起,实现增加传输带宽、提高上下行传输速率的效果。在载波聚合场景下,多个CC中包括一个主载波,以及包括一个或多个辅载波。其中,主载波是主小区(primary cell,PCell)所工作的载波,辅载波是辅小区(secondary cell,SCell)所工作的载波。UE接入网络后,UE在一个基站下将一直保持在主载波上的通信,同时基站可以根据业务情况为该UE添加一个或多个辅载波。
5G NR的频率范围包括FR1与FR2。FR1即通常所讲的5G Sub-6GHz(6GHz以下)频段,FR2则是大于或等于6GHz的频段,例如5G毫米波频段。为UE配置的一个载波可以属于FR1频段或FR2频段,因此存在FR1+FR2的CA场景,即,存在至少一个FR2CC与FR1CC做载波聚合。
在载波聚合场景,有同载波调度和跨载波调度。基站通过在PDCCH上发送DCI来调度UE接收数据或发送数据,即,在DCI中指示用于调度数据接收的物理下行共享信道(physical downlink shared channel,PDSCH),或,在DCI中指示用于调度数据发送的物理上行共享信道(physical uplink shared channel,PUSCH)。若接收DCI的载波和数据接收(或,发送)的载波为同一个载波,即为同载波调度;若接收DCI的载波和数据接收(或,发送)的载波为不同的载波,即为跨载波调度。对于FR1+FR2的CA场景,可以由FR1跨载波调度FR2,即,在FR1载波上接收DCI,该DCI调度在FR2载波上接收数据或发送数据。
3、唤醒信号。
在5G技术中,UE需要进一步节省功耗。对于当前的DRX机制,UE需要在DRX激活时间监听并接收PDCCH,但很多情况下,UE在DRX激活时间内实际上并不能监听到用于调度该UE的PDCCH,则UE只是白白消耗了监听PDCCH的功耗。因此,提出引入一个指示信号(PDCCH-WUS),或者称为唤醒信号,该指示信号能够基于当前DRX机制指示出后续的DRX激活时间内UE是否需要唤醒、或者是否可以休眠。该PDCCH-WUS在标准中又称为DCP,DCP的信号形式可以为DCI。DCP的时域位置可以是:DRX周期的“On Duration”时间之前的一个偏移(offset)的位置,对此可参考图2,图2中加粗的竖线表示DCP。在载波聚合场景,DCP只配置在主载波,但DCP所指示的唤醒或休眠可作用于参与载波聚合的所有载波。
需要注意的是,在本申请实施例中,“载波”和“小区”,在不考虑补充上行链路(supplementary uplink,SUL,)的情况下,这两个概念可以认为是同一概念,二者可以互换。例如,主载波也可以称为主服务小区,或者称为主小区;辅载波也可以称为辅服务小区,或者称为辅小区。
4、两组DRX。
目前,处于RRC连接态的UE可以支持两组DRX配置。所有使用第一组DRX配置的载波都属于一个频率范围(frequency range,FR),如FR1,所有使用第二组DRX配置的载波都属于另一个频率范围,如FR2。第一组DRX配置可以认为是主(primary)配置,第二组DRX配置可以认为是辅(secondary)配置。第二组DRX配置相比第一组DRX配置来说,可以配置定时时长更短的drx-onDurationTimer和drx-InactivityTimer,例如可参考图3。图3中,虚线框表示DRX非激活时间定时器的时长。两组DRX配置可以理解为是 单独维护并操作的,属于第一个频率范围的载波共同使用第一组DRX配置,维护drx-onDurationTimer1和drx-InactivityTimer1;属于第二个频率范围的载波共同使用第二组DRX配置,维护drx-onDurationTimer2和drx-InactivityTimer2。可选的,除了drx-onDurationTimer和drx-InactivityTimer外,第一DRX配置所配置的其他参数与第二DRX配置所配置的相应的参数可以相同。例如,属于第一个频率范围的载波共同使用第一组DRX配置,维护drx-RetransmissionTimer 1,属于第一个频率范围的载波共同使用第二组DRX配置,维护drx-RetransmissionTimer 2,而drx-RetransmissionTimer 1和drx-RetransmissionTimer 2的时长可以相同。
对于如上的跨载波调度、唤醒信号以及两组DRX配置等几种技术,目前都是单独使用的,并未将这些技术结合使用。例如两组DRX配置与唤醒信号结合使用、或两组DRX配置与跨载波调度结合使用等,目前都是不支持的,而这会影响基站配置的灵活度。另外,采用两组DRX配置主要为了降低UE在第二组DRX配置对应的载波(如FR2)上的功耗,而跨载波调度或唤醒信号本身是对UE功耗降低有帮助的,如果能够将两组DRX配置与这些技术结合使用,则可以进一步降低UE功耗。
鉴于此,提供本申请实施例的技术方案。在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,并规定了在结合的情况下的终端设备的行为,例如,终端设备对第一组载波对应的DCP监听时机的监听情况,既适用于第一组载波,也适用于第二组载波。这样,终端设备只需在第一组载波上监听DCP,无需在第二组载波上监听DCP,减小了终端设备监听DCP的功耗,也增加了网络设备调度的灵活性。而且终端设备在一组载波上的监听情况能够适用于两组载波,使得两组载波都能使用DCP机制,能够进一步减小终端设备在两组载波上的功耗。
本申请实施例提供的技术方案可以应用于4G***中,例如LTE***,或可以应用于5G***中,例如NR***,或者还可以应用于下一代移动通信***或其他类似的通信***,具体的不做限制。例如,当终端设备(如智能手机、智能手表或智能手环等)有节能需求时,例如手机电量已经低于20%,则该手机有非常强烈的节省功耗的需求。在这种情况下,采用本申请实施例提供的方法后,能够进一步降低终端设备的功耗,即减少消耗的电池电量,延长终端设备的待机时间。
请参见图4,为本申请实施例的一种应用场景。图4包括接入网设备、核心网设备和UE,接入网设备可以为该UE配置一个或多个载波。该接入网设备例如工作在演进的通用移动通信***陆地无线接入(evolved UMTS terrestrial radio access,E-UTRA)***中,或者工作在NR***中,或者工作在下一代通信***或其他通信***中。该接入网设备例如为基站。其中,接入网设备在不同的***对应不同的设备,例如在4G***中可以对应eNB,在5G***中对应5G中的接入网设备,例如gNB。当然本申请实施例所提供的技术方案也可以应用于未来的移动通信***中,因此图4中的接入网设备也可以对应未来的移动通信***中的网络设备。图4以接入网设备是基站为例,实际上参考前文的介绍,接入网设备还可以是RSU等设备。另外,图4中的UE以手机为例,实际上根据前文对于UE的介绍可知,本申请实施例的UE不限于手机。
另外,为了便于介绍,后文将要介绍的各个实施例均以应用在图4所示的架构为例。例如,后文的各个实施例所述的网络设备例如为图4所示的网络架构中的接入网设备,后文的各个实施例所述的UE可以是图4所示的网络架构中的UE。
下面结合附图介绍本申请实施例所提供的方法。在本申请的各个实施例对应的附图中,凡是用虚线表示的步骤均为可选的步骤。
本申请实施例提供第一种通信方法,请参考图5,为该方法的流程图。
S51、UE确定在第一DCP监听时机内是否监听DCP,或者说,UE确定在第一DCP监听时机内是否进行监听。
例如,网络设备向该UE发送第一DRX配置和第二DRX配置,则该UE就相当于被配置了第一DRX配置和第二DRX配置。例如网络设备可通过一条消息向该UE发送第一DRX配置和第二DRX配置,或者,网络设备也可以通过不同的消息分别向该UE发送第一DRX配置和第二DRX配置。其中,第一组载波应用第一DRX配置,第二组载波应用第二DRX配置,第一组载波包括UE被配置的一个或多个载波,第二组载波也包括UE被配置的一个或多个载波。第一DRX配置可以配置DRX周期、DRX持续时间定时器、DRX非激活定时器以及DRX重传定时器等,第二DRX配置也可以配置DRX周期、DRX非激活定时器以及DRX重传定时器等。第一DRX配置和第二DRX配置是不同的DRX配置,例如,第一DRX配置所配置的DRX持续时间定时器与第二DRX配置所配置的DRX持续时间定时器不同,例如表现为,第一DRX配置所配置的DRX持续时间定时器的时长(或者称为定时时长)与第二DRX配置所配置的DRX持续时间定时器的时长不同。又例如,第一DRX配置所配置的DRX非激活定时器与第二DRX配置所配置的DRX非激活定时器不同,例如表现为,第一DRX配置所配置的DRX非激活定时器的时长(或者称为定时时长)与第二DRX配置所配置的DRX非激活定时器的时长不同。而第一DRX配置与第二DRX配置所配置的除了DRX持续时间定时器以及DRX非激活定时器外的其他内容,例如DRX周期或DRX重传定时器等,可以相同,也可以不同。
例如第一组载波属于第一频率范围,第二组载波属于第二频率范围,第一频率范围与第二频率范围可以是不同的频率范围。作为一种可选的实施方式,例如第二频率范围的频率大于第一频率范围的频率,对此可理解为,第二频率范围所包括的最小频率大于第一频率范围所包括的最大频率,例如第一频率范围为FR1,第二频率范围为FR2。实际上网络设备在为UE配置载波时,可能并未区分哪个载波属于哪个分组,即,“第一组”和“第二组”的概念可能是不存在的。这里使用“第一组载波”与“第二组载波”这样的描述方式,是为了对使用不同DRX配置的载波加以区分。
第一DCP监听时机是配置在第一组载波上的DCP监听时机,第一DCP监听时机应用的是第一DRX配置。在第一DRX配置下,存在多个On Duration时间,那么DCP监听时机也可能会出现多次,例如可能每个DRX周期开始之前都出现一次DCP监听时机。那么,第一DCP监听时机例如为对于UE来说的当前的监听时机,例如第一DCP监听时机位于第一DRX配置下的一个DRX周期的On Duration时间开始之前,或者说,第一DCP监听时机位于第一组载波上的一个DRX周期的On Duration时间开始之前。第一DCP监听时机可以包括一个或多个DCP监听时机,可以理解为,一次DCP监听时机可以包括一个或多个DCP监听时机,而第一DCP监听时机就是一次DCP监听时机。
在本申请实施例中,网络设备可以在第一载波上发送DCP,第一载波属于第一组载波。例如,网络设备为第一组载波所包括的一个或多个载波配置了DCP,那么第一载波包括这一个或多个载波。又例如,网络设备为UE配置的主载波属于第一组载波,则网络设备可以为主载波配置DCP,则第一载波就是该UE的主载波,网络设备可以在主载波上发送 DCP,而无需在其他载波上配置DCP,以节省传输开销。UE如果需要在第一组载波上监听,可以在第一组载波所包括的全部载波上监听,或者网络设备究竟在哪些载波上发送DCP可以预先配置,则UE只需在这些载波上监听。而网络设备并未给第二组载波配置DCP,因此网络设备不必在第二组载波上发送DCP,UE也不必在第二组载波上监听DCP。
UE要确定在第一DCP监听时机内是否进行监听,确定方式有多种,下面举例介绍。
第一种确定方式:根据第一DCP监听时机的时域位置确定。
例如,UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内,如果第一DCP监听时机的时域位置位于第一DRX激活时间内,则表明UE在第一DCP监听时机内在第一组载波上可能有数据传输(例如UE在第一组载波上需要接收数据或发送数据),那么在这种情况下,UE可不在第一DCP监听时机进行监听,而是可以在第一组载波上,在第一DCP监听时机所关联的DRX持续时间内唤醒。
或者,如果第一DCP监听时机对应的全部时域位置没有位于第一DRX激活时间内,则UE可在第一DCP监听时机进行监听。第一DCP监听时机对应的全部时域位置,包括第一DCP监听时机包括的全部DCP监听时机的时域位置。此时,UE可以在第一DCP监听时机所包括的全部DCP监听时机内进行监听。
或者,如果第一DCP监听时机对应的部分时域位置没有位于第一DRX激活时间内,则UE可不在第一DCP监听时机包括的位于第一DRX激活时间内的DCP监听时机内进行监听,而对于第一DCP监听时机包括的没有位于第一DRX激活时间内的DCP监听时机,UE还是可以监听。即,这种情况下,UE是不在第一DCP监听时机所包括的部分DCP监听时机内进行监听,而在第一DCP监听时机所包括的剩余的DCP监听时机内进行监听,因此这种情况也可视为UE在第一DCP监听时机内监听。第一DCP监听时机对应的部分时域位置,包括第一DCP监听时机包括的部分DCP监听时机的时域位置。第一DRX激活时间是第一DRX配置对应的DRX激活时间,第一DRX激活时间位于第一组载波上。
这种确定方式对于UE来说较为容易实现。
第二种确定方式:根据DCI大小预算(DCI size budget)确定。
对于UE来说,是有DCI大小预算的,即,UE最多能够监听的DCI size的个数是有限制的。例如规定UE最多能够监听的DCI size的个数为4,那么UE最多能够监听4种size的DCI,如果再有第五种size的DCI,UE就无法监听。DCP视为一种size的DCI。而UE共需要监听多少种size的DCI,是可以由网络设备配置给UE的,那么UE可以根据最多能够监听的DCI size的个数,以及UE需要监听的DCI size的个数,确定是否需要在第一DCP监听时机内监听DCP。
例如,如果不将DCP视为UE需要监听的DCI,那么,如果UE最多能够监听的DCI size的个数大于该UE需要监听的DCI size的个数,那么UE就可以在第一DCP监听时机内进行监听,因为此时即使UE监听DCP,也能够符合DCI大小预算的要求。而如果UE最多能够监听的DCI size的个数小于或等于该UE需要监听的DCI size的个数,那么UE就可以不在第一DCP监听时机内进行监听,因为此时如果UE监听DCP,就超出了DCI大小预算,可能导致UE的监听行为出错。例如,UE最多能够监听的DCI size的个数为4,UE需要监听的DCI size的个数为3,UE需要监听的DCI不包括DCP,那么UE就可以在第一DCP监听时机内监听DCP;或者,UE最多能够监听的DCI size的个数为4,UE需要监听的DCI size的个数为4,那么UE就不在第一DCP监听时机内监听DCP。
或者,如果将DCP视为UE需要监听的DCI,那么,如果UE最多能够监听的DCI size的个数大于或等于该UE需要监听的DCI size的个数,那么UE就可以在第一DCP监听时机内进行监听,而如果UE最多能够监听的DCI size的个数小于该UE需要监听的DCI size的个数,那么UE就可以不在第一DCP监听时机内进行监听。例如,UE最多能够监听的DCI size的个数为4,UE需要监听的DCI size的个数为4,UE需要监听的DCI包括DCP,那么UE就可以在第一DCP监听时机内监听DCP;或者,UE最多能够监听的DCI size的个数为4,UE需要监听的DCI size的个数为5,UE需要监听的DCI包括DCP,那么UE就不在第一DCP监听时机内监听DCP。
采用DCI大小预算来确定是否监听第一DCP监听时机,使得UE的监听行为能够符合DCI大小预算的要求,而且也使得UE的监听更为灵活。
第三种确定方式:根据第一DCP监听时机的时域位置以及DCI大小预算确定。
例如,UE确定该UE最多能够监听的DCI size的个数和该UE需要监听的DCI size的个数。如果UE最多能够监听的DCI size的个数大于或等于该UE需要监听的DCI size的个数(将DCP视为UE需要监听的DCI),则UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内。如果第一DCP监听时机的时域位置位于第一DRX激活时间内,则UE在第一DCP监听时机内不监听DCP,或者,如果第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内,则UE在第一DCP监听时机内监听DCP。
或者,如果UE最多能够监听的DCI size的个数小于该UE需要监听的DCI size的个数(将DCP视为UE需要监听的DCI),则UE可以无需确定第一DCP监听时机的时域位置,而是可以确定UE在第一DCP监听时机内不监听DCP。
又例如,UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内,如果第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内,UE确定该UE最多能够监听的DCI size的个数和该UE需要监听的DCI size的个数。如果UE最多能够监听的DCI size的个数大于或等于该UE需要监听的DCI size的个数(将DCP视为UE需要监听的DCI),则UE在第一DCP监听时机内监听DCP,或者,如果UE最多能够监听的DCI size的个数小于该UE需要监听的DCI size的个数,则UE在第一DCP监听时机内不监听DCP。
或者,如果第一DCP监听时机的时域位置位于第一DRX激活时间内,则UE可以无需确定该UE最多能够监听的DCI size的个数和该UE需要监听的DCI size的个数,而是可以确定UE在第一DCP监听时机内不监听DCP。
第三种确定方式相当于将第一种确定方式和第二种确定方式结合使用,可以使得确定结果更为合理。
至于UE究竟采用如上三种方式中的哪种方式来确定是否在第一DCP监听时机内监听,可由UE自行确定,或者由网络设备配置,或者也可以通过协议规定等。
可选的,在本申请的各个实施例中,UE也可以没有确定是否需要监听DCP监听时机的过程,例如对于图5所示的实施例来说,UE也可不执行S51。例如,在第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,则UE不在第一DCP监听时机进行监听,或者,在第一DCP监听时机对应的全部时域位置没有位于第一DRX激活时间内的情况下,则UE在第一DCP监听时机进行监听,或者,在第一DCP监听时机对应的部分时域位置没有位于第一DRX激活时间内的情况下,则UE不在第一DCP监听时机包括的 位于第一DRX激活时间内的DCP监听时机内进行监听,而在第一DCP监听时机包括的没有位于第一DRX激活时间内的DCP监听时机内监听。又例如,在UE最多能够监听的DCI size的个数大于该UE需要监听的DCI size的个数的情况下,那么UE就在第一DCP监听时机内进行监听,而在UE最多能够监听的DCI size的个数小于或等于该UE需要监听的DCI size的个数的情况下,那么UE就不在第一DCP监听时机内进行监听。为了方便理解,本申请的各个实施例都以UE有确定过程为例。
可选的,根据如上的第一种确定方式,可将S51替换为,UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内。
或者,根据如上的第一种确定方式,可将S51替换为,UE确定UE最多能够监听的DCI size的个数是否大于该UE需要监听的DCI size的个数。
或者,还可以根据如上的第三种确定方式相应替换S51。
S52、如果UE确定不在第一DCP监听时机内监听,该UE在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠。或者说,如果UE不在第一DCP监听时机内监听,则在第一组载波上,该UE在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第二组载波上,该UE在第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠。
可选的,如果根据如上的第一种确定方式替换了S51,那么S52也可以替换为,如果第一DCP监听时机的时域位置位于第一DRX激活时间内,该UE在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠。
或者,如果根据如上的第一种确定方式替换了S51,那么S52也可以替换为,如果UE最多能够监听的DCI size的个数小于或等于该UE需要监听的DCI size的个数,该UE在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,在第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠。
或者,如果根据如上的第三种确定方式替换了S51,那么S52也可进行相应替换。
在第一组载波上,按照第一DRX配置,第一DCP监听时机可以关联一个或多个DRX周期。第一DCP监听时机关联的DRX周期,在时域上晚于第一DCP监听时机,且第一DCP监听时机如果关联多个DRX周期,这多个DRX周期在时域上可以连续,也可以不连续。另外,第一DRX持续时间对应于第一DRX配置,第一DRX持续时间位于第一组载波上。例如,第一DRX持续时间可包括第一DRX配置下第一DCP监听时机所关联的全部或部分DRX周期内的On Duration时间,或者说,第一DRX持续时间可包括第一组载波上,第一DCP监听时机所关联的全部或部分DRX周期内的On Duration时间。如果UE确定不在第一DCP监听时机内监听,则UE在第一DCP监听时机内不进行监听。在这种情况下,为了减少UE错过网络设备在第一组载波上可能发送的PDCCH的概率,则UE可以在第一DRX持续时间内唤醒。
在第二组载波上,按照第二DRX配置,第一DCP监听时机也可以关联一个或多个DRX周期。因为第一DCP监听时机并没有配置在第二组载波上,因此这种关联是时域位置上的关联,例如,在第二组载波上,在时域上晚于第一DCP监听时机的一个或多个DRX周期,都可以与第一DCP监听时机关联。且第一DCP监听时机如果关联多个DRX周期,这多个DRX周期在时域上可以连续,也可以不连续。另外,第二DRX持续时间对应于第 二DRX配置,第二DRX持续时间位于第二组载波上。第二DRX持续时间可包括第二DRX配置下第一DCP监听时机所关联的全部或部分DRX周期内的On Duration时间,或者说,第二DRX持续时间可包括第二组载波上,第一DCP监听时机所关联的全部或部分DRX周期内的On Duration时间。例如可以默认(或者,协议规定),如果UE确定不在第一DCP监听时机内监听,则UE可以在第一DCP监听时机关联的第二DRX持续时间内休眠,以节省UE的功耗;或者,可以默认(或者,协议规定),如果UE确定不在第一DCP监听时机内监听,则UE可以在第一DCP监听时机关联的第二DRX持续时间内唤醒,以减少UE错过网络设备在第二组载波上可能发送的数据的概率。在这种情况下,UE在第二组载波上的行为是默认或通过协议规定的,无需网络设备额外配置,也无需UE通过其他方式确定,能够简化网络设备和UE的实现。
或者,UE在第二DRX持续时间内休眠或唤醒,也可以由网络设备指示。例如,网络设备向UE发送配置信息,相应的,UE接收来自网络设备的配置信息,该配置信息例如可以通过RRC消息、***消息或其他消息发送。该配置信息可以在第一组载波所包括的一个或多个载波上发送,例如网络设备为UE配置的主载波属于第一组载波,则该配置信息可以在主载波上发送;或者,该配置信息也可以在第二组载波所包括的一个或多个载波上发送。该配置信息可以配置:在UE不在DCP监听时机内监听的情况下,该UE在第二组载波上,在该DCP监听时机关联的DRX持续时间内唤醒;或者,该配置信息可以配置:在UE不在DCP监听时机内监听的情况下,该UE在第二组载波上,在该DCP监听时机关联的DRX持续时间内休眠。在这种情况下,网络设备可以根据数据传输等因素,通过配置信息配置UE在第二组载波上休眠或唤醒,例如,如果网络设备在第二组载波上会在第一DCP监听时机关联的DRX周期内调度UE发送数据或接收数据,则网络设备可通过配置信息指示UE唤醒,而如果网络设备在第二组载波上不会在第一DCP监听时机关联的DRX周期内调度UE发送数据和接收数据,则网络设备可通过配置信息指示UE休眠。通过这种方式,可以使得UE的休眠或唤醒能够符合数据传输需求。
S53、如果UE确定在第一DCP监听时机内监听,则UE根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
可选的,如果根据如上的第一种确定方式替换了S51,那么S53也可以替换为,如果第一DCP监听时机对应的全部或部分时域位置没有位于第一DRX激活时间内,该UE在第一DCP监听时机内监听DCP,并根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
或者,如果根据如上的第二种确定方式替换了S51,那么S53也可以替换为,如果UE最多能够监听的DCI size的个数大于该UE需要监听的DCI size的个数,该UE在第一DCP监听时机内监听DCP,并根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
或者,如果根据如上的第三种确定方式替换了S51,那么S53也可以进行相应替换。
如果UE需要在第一DCP监听时机内监听,则UE在第一DCP监听时机内进行监听,并根据在第一DCP监听时机内对DCP的监听情况,确定在第一组载波和第二组载波上的休眠或唤醒,即,UE在第一DCP监听时机内的监听情况,能够决定UE在第一组载波上的行为,也能决定在第二组载波上的行为。例如可参考图6,图6中画斜线的矩形框表示第一DCP监听时机,FR2上没有配置DCP监听时机,UE在第一DCP监听时机的监听情 况,既能决定UE在第一组载波上的行为,也能决定UE在第二组载波上的行为。
作为一种可选的实施方式,DCP的实现方式为,如果网络设备发送了DCP,则指示UE在DCP关联的DRX周期内唤醒,如果网络设备未发送DCP,则指示UE在DCP关联的DRX周期内休眠。对于UE来说,如果监听并接收了DCP,就在DCP关联的DRX周期内唤醒,如果未监听到DCP,就在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,UE在第二组载波上,在第一DCP监听时机关联的第二DRX持续时间内唤醒;而如果UE在第一DCP监听时机内未接收到来自网络设备的DCP,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内休眠,以及,UE在第二组载波上,在第一DCP监听时机关联的第二DRX持续时间内休眠。
作为另一种可选的实施方式,DCP的实现方式为,DCP包括指示信息,如果网络设备发送了DCP,且该DCP包括的指示信息指示唤醒,则指示UE在DCP关联的DRX周期内唤醒,如果网络设备发送了DCP,且该DCP包括的指示信息指示休眠,则指示UE在DCP关联的DRX周期内休眠。对于UE来说,如果监听并接收到了DCP,且该DCP包括的指示信息指示唤醒,UE就在DCP关联的DRX周期内唤醒,如果监听并接收到了DCP,且该DCP包括的指示信息指示休眠,UE就在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的指示信息指示唤醒,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内唤醒,以及,UE在第二组载波上,在第一DCP监听时机关联的第二DRX持续时间内唤醒;而如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的指示信息指示休眠,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内休眠,以及,UE在第二组载波上,在第一DCP监听时机关联的第二DRX持续时间内休眠。
作为又一种可选的实施方式,DCP的实现方式为,DCP包括第一指示信息和第二指示信息,第一指示信息对应第一组载波,或者说对应第一DRX配置,第二指示信息对应第二组载波,或者说对应第二DRX配置。如果网络设备发送了DCP,且该DCP包括的第一指示信息指示唤醒,则指示UE在DCP关联的第一DRX配置下的DRX周期内唤醒,如果网络设备发送了DCP,且该DCP包括的第一指示信息指示休眠,则指示UE在DCP关联的第一DRX配置下的DRX周期内休眠。第二指示信息的指示方式也是类似的。对于UE来说,如果监听并接收到了DCP,且该DCP包括的第一指示信息指示唤醒,UE就在DCP关联的第一DRX配置下的DRX周期内唤醒,如果监听并接收到了DCP,且该DCP包括的第一指示信息指示休眠,UE就在DCP关联的第一DRX配置下的DRX周期内休眠。UE对于第二指示信息的理解方式也是类似的。如果DCP采用这种实现方式,那么,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第一指示信息指示唤醒,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内唤醒;而如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第一指示信息指示休眠,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内休眠。同理,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第二指示信息指示唤醒,则UE在第二组载波上,在第一DCP监听时机关联的 第二DRX持续时间内唤醒;而如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第二指示信息指示休眠,则UE在第二组载波上,在第一DCP监听时机关联的第二DRX持续时间内休眠。在这种方式下,DCP可以通过不同的指示信息分别指示不同的DRX持续时间内的休眠或唤醒,例如网络设备可以根据两组载波上的信息传输情况确定相应的指示信息究竟指示唤醒还是休眠,使得UE的休眠或唤醒行为更为符合业务传输需求。
作为又一种可选的实施方式,DCP的实现方式为,两组载波分别有对应的DCP,例如DCP内可包括载波组的标识,以区分不同载波组的DCP,或者不同载波组的DCP的格式不同。对于一组载波来说,如果网络设备发送了该组载波对应的DCP,且该DCP指示唤醒,则指示UE在该组载波上,在该DCP关联的DRX周期内唤醒,如果网络设备发送了该组载波对应的DCP,且该DCP指示休眠,则指示UE在该组载波上,在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP对应于第一组载波,如果该DCP指示唤醒,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内唤醒,或者,如果该DCP指示休眠,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内休眠。对于第二组载波来说,网络设备和UE的操作过程也是同样的。
作为再一种可选的实施方式,DCP的实现方式为,两组载波分别有对应的DCP,例如DCP内可包括载波组的标识,以区分不同载波组的DCP,或者不同载波组的DCP的格式不同。对于一组载波来说,如果网络设备发送了该组载波对应的DCP,则指示UE在该组载波上,在该DCP关联的DRX周期内唤醒,如果网络设备未发送该组载波对应的DCP,则指示UE在该组载波上,在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第一DCP监听时机内接收到来自网络设备的DCP,且该DCP对应于第一组载波,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内唤醒,或者,如果UE在第一DCP监听时机内未接收到来自网络设备的对应于第一组载波的DCP,则UE在第一组载波上,在第一DCP监听时机关联的第一DRX持续时间内休眠。对于第二组载波来说,网络设备和UE的操作过程也是同样的。
在本申请实施例中,UE在第一DRX持续时间内休眠,可以通过如下方式实现:UE在第一DRX持续时间的起始时刻不启动也不重启第一DRX持续时间定时器。第一DRX持续时间定时器是由第一DRX配置所配置的,第一DRX持续时间定时器对应第一组载波。如果第一DRX持续时间定时器未启动,则UE在第一DRX持续时间的起始时刻不启动第一DRX持续时间定时器,而如果第一DRX持续时间定时器处于运行状态,则UE在第一DRX持续时间的起始时刻不重启第一DRX持续时间定时器,这样都能使得UE在第一DRX持续时间内休眠。UE在第二DRX持续时间内休眠的实现方式也是类似的,例如通过如下方式实现:UE在第二DRX持续时间的起始时刻不启动也不重启第二DRX持续时间定时器。第二DRX持续时间定时器是由第二DRX配置所配置的,第二DRX持续时间定时器对应第二组载波。
UE在第一DRX持续时间内唤醒,可以通过如下方式实现:UE在第一DRX持续时间的起始时刻启动或重启第一DRX持续时间定时器。如果第一DRX持续时间定时器未启动,则UE在第一DRX持续时间的起始时刻启动第一DRX持续时间定时器,而如果第一DRX持续时间定时器处于运行状态,则UE在第一DRX持续时间的起始时刻重启第一DRX持 续时间定时器,这样都能使得UE在第一DRX持续时间内唤醒。UE在第二DRX持续时间内唤醒的实现方式也是类似的,例如通过如下方式实现:UE在第二DRX持续时间的起始时刻启动或重启第二DRX持续时间定时器。第二DRX持续时间定时器是由第二DRX配置所配置的,第二DRX持续时间定时器对应第二组载波。
S52和S53是并列的两种方案,二者不会同时执行。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,并规定了在结合的情况下的终端设备的行为。例如,在终端设备不对第一组载波对应的DCP监听时机进行监听的情况下,可以通过默认、协议规定或网络配置等方式规定终端设备在第二组载波上的行为;而在终端设备对第一组载波对应的DCP监听时机进行监听的情况下,终端设备对第一组载波对应的DCP监听时机的监听情况,既适用于第一组载波,也适用于第二组载波。通过这种方式,终端设备只需在第一组载波上监听DCP,无需在第二组载波上监听DCP,减小了终端设备监听DCP的功耗,也增加了网络设备调度的灵活性。终端设备在一组载波上的监听情况能够适用于两组载波,使得两组载波都能使用DCP机制,能够进一步减小终端设备在两组载波上的功耗。而且网络设备无需为第二组载波配置DCP,也能够节省信令开销。
本申请实施例提供第二种通信方法,请参考图8,为该方法的流程图。
S81、UE确定在第一DCP监听时机内是否监听DCP,或者说,UE确定在第一DCP监听时机内是否进行监听。
可选的,S81也可以替换为,UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内。
或者,S81也可以替换为,UE确定UE最多能够监听的DCI size的个数是否大于该UE需要监听的DCI size的个数。或者,S81也可以根据图5所示的实施例所述的第三种确定方式进行相应替换。
关于S81的更多内容,例如UE如何确定是否在第一DCP监听时机内进行监听等,可参考图5所示的实施例中的S51。
S82、如果UE确定在第一DCP监听时机内监听,则UE根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
或者,如果S81替换为,UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内,那么S82可以替换为,如果第一DCP监听时机对应的全部或部分时域位置没有位于第一DRX激活时间内,该UE在第一DCP监听时机内监听DCP,并根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
或者,如果S81替换为,UE确定UE最多能够监听的DCI size的个数是否大于该UE需要监听的DCI size的个数,那么S82可以替换为,如果UE最多能够监听的DCI size的个数大于该UE需要监听的DCI size的个数,该UE在第一DCP监听时机内监听DCP,并根据监听情况确定在第一组载波上的休眠或唤醒,以及确定在第二组载波上的休眠或唤醒。
或者,如果S81根据图5所示的实施例所述的第三种确定方式进行了相应替换,那么S82也可以根据S81进行相应替换。
在本申请实施例中,网络设备可以在第一载波上发送DCP,第一载波属于第一组载波。例如,网络设备为第一组载波所包括的一个或多个载波配置了DCP,那么第一载波包括这一个或多个载波。又例如,网络设备为UE配置的主载波属于第一组载波,则网络设备可 以为主载波配置DCP,则第一载波就是该UE的主载波,网络设备可以在主载波上发送DCP,而无需在其他载波上配置DCP,以节省传输开销。UE如果需要在第一组载波上监听,可以在第一组载波所包括的全部载波上监听,或者网络设备究竟在哪些载波上发送DCP可以预先配置,则UE只需在这些载波上监听。
网络设备可以在第二载波上发送DCP,第二载波属于第二组载波。例如,网络设备为第二组载波所包括的一个或多个载波配置了DCP,那么第二载波包括这一个或多个载波。UE如果需要在第二组载波上监听,可以在第二组载波所包括的全部载波上监听,或者网络设备究竟在哪些载波上发送DCP可以预先配置,则UE只需在这些载波上监听。也就是说,本申请实施例中,网络设备为第一组载波配置了DCP,也为第二组载波配置了DCP。
虽然为第一组载波和第二组载波都配置了DCP,但UE先确定是否要在第一组载波上进行监听,如果能够在第一组载波上监听,则UE在第一组载波上监听,例如在第一DCP监听时机内监听,并根据监听结果确定在第一组载波和第二组载波上的休眠或唤醒。在这种情况下,UE而无需在第二组载波上监听,例如,UE不在第二DCP监听时机内监听。第二DCP监听时机是配置在第二组载波上的DCP监听时机,第二DCP监听时机应用的是第二DRX配置。在第二DRX配置下,存在多个On Duration时间,那么DCP监听时机也可能会出现多次,例如可能每个DRX周期开始之前都出现一次DCP监听时机。那么,第二DCP监听时机例如为对于UE来说的当前的监听时机,例如第二DCP监听时机位于第二DRX配置下的一个DRX周期的On Duration时间开始之前,或者说,第二DCP监听时机位于第二组载波上的一个DRX周期的On Duration时间开始之前。在UE能够在第一组载波上监听的情况下,由于UE无需在第二组载波上监听,由此可以减小UE由于监听所带来的功耗。
关于S82的更多内容,例如UE如何根据监听情况确定在第一组载波和第二组载波上的休眠或唤醒等,可参考图5所示的实施例中的S53。
需要注意的是,关于第一DCP监听时机关联的第一DRX持续时间等内容的介绍,可参考图5所示的实施例中的S52。另外,第一DCP监听时机和第二DCP监听时机的时域位置可能是相同的,或者第一DCP监听的时域位置可能早于第二DCP监听时机的时域位置,因此在参考S52时,对于S52中所述的第一DCP监听时机关联的第二DRX持续时间,在本申请实施例中也可以认为是第二DCP监听时机在第二组载波上关联的DRX持续时间。
S83、如果UE确定不在第一DCP监听时机内监听,UE确定在第二DCP监听时机内是否监听DCP,或者说,UE确定在第二DCP监听时机内是否进行监听。
或者,如果S81替换为UE确定第一DCP监听时机的时域位置是否位于第一DRX激活时间内,那么S83可以替换为,如果第一DCP监听时机的时域位置位于第一DRX激活时间内,UE确定在第二DCP监听时机内是否监听DCP,或者说,UE确定在第二DCP监听时机内是否进行监听。
或者,如果S81替换为UE确定UE最多能够监听的DCI size的个数是否大于该UE需要监听的DCI size的个数,那么S83可以替换为,如果UE最多能够监听的DCI size的个数小于或等于该UE需要监听的DCI size的个数,UE确定在第二DCP监听时机内是否监听DCP,或者说,UE确定在第二DCP监听时机内是否进行监听。
或者,如果S81根据图5所示的实施例所述的第三种确定方式进行了相应替换,那么S83也可以根据S81进行相应替换。
另外,对于S83所述的,UE确定在第二DCP监听时机内是否进行监听,也可以进行相应替换,具体的替换方式可参考对于S81的替换方式的介绍。
UE确定在第二DCP监听时机内是否进行监听的方式,与UE确定在第一DCP监听时机内是否进行监听的方式是类似的,可参考本申请实施例前文的介绍,或可参考图5所示的实施例中的S51。
另外,如果UE不在第一DCP监听时机内监听,那么可选的,UE在第一组载波上,可在第一DRX持续时间内唤醒,以避免错过PDCCH。
S84、如果UE确定在第二DCP监听时机内监听,则UE根据监听情况确定在第二组载波上的休眠或唤醒。对于S84所述的,UE确定在第二DCP监听时机内进行监听,也可以进行相应替换,具体的替换方式可参考对于S82的替换方式的介绍。
如果UE确定在第二DCP监听时机内监听,则UE可在第二DCP监听时机内监听,此时,第二DCP监听时机的监听结果可用于决定UE在第二组载波上的休眠或唤醒。例如可参考图9,图9中画“\”的矩形框表示第一DCP监听时机,画“/”的矩形框表示第二DCP监听时机。如果UE能够监听第一DCP监听时机,则UE根据第一DCP监听时机的监听情况可以确定在第一组载波上的休眠或唤醒,以及能确定在第二组载波上的休眠或唤醒;如果UE不能监听第一DCP监听时机,但能监听第二DCP监听时机,则UE根据第二DCP监听时机的监听情况可以确定在第二组载波上的休眠或唤醒。
作为一种可选的实施方式,DCP的实现方式为,如果网络设备发送了DCP,则指示UE在DCP关联的DRX周期内唤醒,如果网络设备未发送DCP,则指示UE在DCP关联的DRX周期内休眠。对于UE来说,如果监听并接收了DCP,就在DCP关联的DRX周期内唤醒,如果未监听到DCP,就在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒;而如果UE在第二DCP监听时机内未接收到来自网络设备的DCP,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内休眠。
作为另一种可选的实施方式,DCP的实现方式为,DCP包括指示信息,如果网络设备发送了DCP,且该DCP包括的指示信息指示唤醒,则指示UE在DCP关联的DRX周期内唤醒,如果网络设备发送了DCP,且该DCP包括的指示信息指示休眠,则指示UE在DCP关联的DRX周期内休眠。对于UE来说,如果监听并接收到了DCP,且该DCP包括的指示信息指示唤醒,UE就在DCP关联的DRX周期内唤醒,如果监听并接收到了DCP,且该DCP包括的指示信息指示休眠,UE就在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的指示信息指示唤醒,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒;而如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP指示休眠,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内休眠。
在如上两种实施方式中,第二DCP监听时机的监听结果不用于决定UE在第一组载波上的休眠或唤醒。
作为又一种可选的实施方式,DCP的实现方式为,DCP包括第三指示信息和第四指示信息,第三指示信息对应第一组载波,或者说对应第一DRX配置,第四指示信息对应第 二组载波,或者说对应第二DRX配置。如果网络设备发送了DCP,且该DCP包括的第三指示信息指示唤醒,则指示UE在DCP关联的第一DRX配置下的DRX周期内唤醒,如果网络设备发送了DCP,且该DCP包括的第三指示信息指示休眠,则指示UE在DCP关联的第一DRX配置下的DRX周期内休眠。第四指示信息的指示方式也是类似的。对于UE来说,如果监听并接收到了DCP,且该DCP包括的第三指示信息指示唤醒,UE就在DCP关联的第一DRX配置下的DRX周期内唤醒,如果监听并接收到了DCP,且该DCP包括的第三指示信息指示休眠,UE就在DCP关联的第一DRX配置下的DRX周期内休眠。UE对于第四指示信息的理解方式也是类似的。如果DCP采用这种实现方式,则第二DCP监听时机的监听结果可用于决定UE在第二组载波上的休眠或唤醒,也可以用于决定UE在第一组载波上的休眠或唤醒。例如,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第三指示信息指示唤醒,则UE在第一组载波上,在第一DCP监听时机(或者说,第二DCP监听时机)关联的第一DRX持续时间内唤醒;而如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第三指示信息指示休眠,则UE在第一组载波上,在第一DCP监听时机(或者说,第二DCP监听时机)关联的第一DRX持续时间内休眠。同理,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第四指示信息指示唤醒,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒;而如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP包括的第四指示信息指示休眠,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内休眠。
在这种方式下,DCP可以通过不同的指示信息分别指示不同的DRX持续时间内的休眠或唤醒,例如网络设备可以根据两组载波上的信息传输情况确定相应的指示信息究竟指示唤醒还是休眠,使得UE的休眠或唤醒行为更为符合业务传输需求。
作为又一种可选的实施方式,DCP的实现方式为,两组载波分别有对应的DCP,例如DCP内可包括载波组的标识,以区分不同载波组的DCP,或者不同载波组的DCP的格式不同。对于一组载波来说,如果网络设备发送了该组载波对应的DCP,且该DCP指示唤醒,则指示UE在该组载波上,在该DCP关联的DRX周期内唤醒,如果网络设备发送了该组载波对应的DCP,且该DCP指示休眠,则指示UE在该组载波上,在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP对应于第二组载波,如果该DCP指示唤醒,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒,或者,如果该DCP指示休眠,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内休眠。
作为再一种可选的实施方式,DCP的实现方式为,两组载波分别有对应的DCP,例如DCP内可包括载波组的标识,以区分不同载波组的DCP,或者不同载波组的DCP的格式不同。对于一组载波来说,如果网络设备发送了该组载波对应的DCP,则指示UE在该组载波上,在该DCP关联的DRX周期内唤醒,如果网络设备未发送该组载波对应的DCP,则指示UE在该组载波上,在DCP关联的DRX周期内休眠。如果DCP采用这种实现方式,那么,如果UE在第二DCP监听时机内接收到来自网络设备的DCP,且该DCP对应于第二组载波,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒,或者,如果UE在第二DCP监听时机内未接收到来自网络设备的对应于第二组载波的 DCP,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内休眠。
S85、如果UE确定在第二DCP监听时机内不进行监听,则UE在第二组载波上,在第二DCP监听时机关联的第二DRX持续时间内唤醒或休眠。对于S85所述的,UE确定在第二DCP监听时机内不进行监听,也可以进行相应替换,具体的替换方式可参考对于S83的替换方式的介绍。
如果UE确定在第二DCP监听时机内不进行监听,则UE在第二DCP监听时机内不进行监听。S85的情况为,UE既不在第一DCP监听时机监听,也不在第二DCP监听时机监听。在这种情况下,为了减少UE错过网络设备在第一组载波上可能发送的PDCCH的概率,则UE在第一组载波上,可以在第一DRX持续时间内唤醒。
对于第二组载波,例如可以默认(或者,协议规定),如果UE确定不在第二DCP监听时机内监听(或者,如果UE确定不在第一DCP监听时机内监听以及不在第二DCP监听时机内监听),则UE在第二组载波上,可以在第二DCP监听时机关联的第二DRX持续时间内休眠,以节省UE的功耗;或者,可以默认(或者,协议规定),如果UE确定不在第二DCP监听时机内监听(或者,如果UE确定不在第一DCP监听时机内监听以及不在第二DCP监听时机内监听),则UE在第二组载波上,可以在第二DCP监听时机关联的第二DRX持续时间内唤醒,以减少UE错过网络设备在第二组载波上可能发送的数据的概率。在这种情况下,UE在第二组载波上的行为是默认或通过协议规定的,无需网络设备额外配置,也无需UE通过其他方式确定,能够简化网络设备和UE的实现。
或者,UE在第二组载波上在第二DRX持续时间内的休眠或唤醒,也可以由网络设备指示。例如,网络设备向UE发送配置信息,相应的,UE接收来自网络设备的配置信息,该配置信息例如可以通过RRC消息、***消息或其他消息发送。该配置信息可以在第一组载波所包括的一个或多个载波上发送,例如网络设备为UE配置的主载波属于第一组载波,则该配置信息可以在主载波上发送;或者,该配置信息也可以在第二组载波所包括的一个或多个载波上发送。该配置信息可以配置:在UE不在DCP监听时机内监听的情况下,该UE在第二组载波上在该DCP监听时机关联的DRX持续时间内唤醒;或者,该配置信息可以配置:在UE不在DCP监听时机内监听的情况下,该UE在第二组载波上在该DCP监听时机关联的DRX持续时间内休眠。在这种情况下,网络设备可以根据数据传输等因素,通过配置信息配置UE在第二组载波上休眠或唤醒,例如,如果网络设备在第二组载波上会在第二DCP监听时机关联的DRX周期内调度UE发送数据或接收数据,则网络设备可通过配置信息指示UE唤醒,而如果网络设备在第二组载波上不会在第二DCP监听时机关联的DRX周期内调度UE发送数据和接收数据,则网络设备可通过配置信息指示UE休眠。通过这种方式,可以使得UE的休眠或唤醒能够符合数据传输需求。
关于其他内容,例如UE在DRX持续时间内休眠应如何实现,或者UE在DRX持续时间内唤醒应如何实现等,均可参考图5所示的实施例的相关介绍。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,并规定了在结合的情况下的终端设备的行为。例如,UE优先监听第一DCP监听时机,如果能够监听第一DCP监听时机,则UE无需监听第二DCP监听时机,以节省UE监听DCP监听时机所带来的功耗。如果UE不能监听第一DCP监听时机,则UE还可以确定是否能够监听第二DCP监听时机,使得UE的行为尽量在监听结果的指示下进行,以更为符合网络设备的要求。在本申请实施例中,网络设备可以为第二组载波配置第二DCP监听时机,使得网络设 备对于UE在第二组载波上的行为的控制力更强,也增加了网络设备调度的灵活性。
本申请实施例提供第三种通信方法,请参考图10,为该方法的流程图。
S101、网络设备在第一载波上向UE发送DCI,相应的,UE在第一载波上接收来自网络设备的DCI。第一载波可以包括一个或多个载波,第一载波可以属于第一组载波,或者属于第二组载波。第一组载波应用第一DRX配置,第二组载波应用第二DRX配置。
DCP也是一种DCI,也要受到DCI大小预算的限制。在本申请实施例中,网络设备无需为UE配置DCP,或者说,网络设备无需发送DCP,而是通过除DCP外的其他的DCI来实现DCP的功能。DCP的size一般与其他普通的DCI的size不同,根据UE的DCI大小预算,DCP就占用了一种size,这使得UE能够接收的DCI的种类变少。但是在本申请实施例中,网络设备无需发送DCP,而是发送普通的DCI,则DCP不会占用DCI size的开销,使得UE能够接收更多种类的DCI。
或者,在本申请实施例中,网络设备也可以为UE配置DCP,例如网络设备为第一组载波配置DCP。但在某些情况下,UE无法监听DCP,例如由于DCI大小预算的限制,UE确定不监听DCP,或者,由于相应的DCP监听时机位于DRX激活时间内,则UE确定不监听DCP,那么在这些情况下,网络设备也可以通过发送其他DCI来实现DCP的功能。关于第一组载波、第二组载波、第一DRX配置、第二DRX配置、以及DRX激活时间等内容的介绍,可参考图5所示的实施例或图8所示的实施例。
可选的,在本申请实施例中,无论网络设备是否配置DCP,或者说,无论网络设备是否发送DCP,网络设备都可以在DCP监听时机内发送具有DCP功能的DCI,例如网络设备可以在第一DCP监听时机内发送具有DCP功能的DCI,UE可以在第一DCP监听时机内接收具有DCP功能的DCI。关于第一DCP监听时机等内容,可参考图5所示的实施例的介绍。或者,网络设备也可以不在DCP监听时机内发送具有DCP功能的DCI,而是在其他时间发送具有DCP功能的DCI。例如,网络设备在DRX周期的On Duration时间内发送具有DCP功能的DCI。
示例性的,如果网络设备配置了DCP,或者,网络设备会在DCP监听时机内发送具有DCP功能的DCI,那么UE可以确定在第一DCP监听时机内是否监听DCP,如果UE确定在第一DCP监听时机内监听DCP,则UE可以在第一DCP监听时机内监听DCP,或监听具有DCP功能的DCI。关于UE确定在第一DCP监听时机内是否监听DCP的方式,可参考图5所示的实施例中的S51。例如第一种确定方式为,根据第一DCP监听时机的时域位置确定;例如第二种确定方式为根据DCI大小预算确定;例如第三种确定方式为,根据第一DCP监听时机的时域位置以及DCI大小预算确定,等等,对此可参考图5所示的实施例的S51描述。
如果该DCI用于实现DCP的功能,那么可选的,该DCI可以通过该DCI包括的第二字段来指示该DCI用于实现DCP功能。第二字段例如包括如下的一个或多个字段:频域资源分配(frequency domain resource assignment,FDRA)字段,调制与编码方案(modulation and coding scheme,MCS)字段,新数据指示(new data indicator,NDI)字段,冗余版本(redundancy version,RV)字段,混合自动重传请求进程号(hybrid automatic repeat request process number),天线端口(a ntenna port(s)),或,解调参考信号序列初始化(demodulation reference signal sequence initialization)字段。在DCI中,MCS字段占用5比特(bit),NDI字段占用1比特,RV字段占用2比特,HARQ进程号字段占用4比特,天线端口字段占 用至少4比特,DMRS序列号初始化字段占用1比特。例如,第二字段为FDRA字段;或者,第二字段为MCS字段;或者,第二字段包括MCS字段和NDI字段;或者,第二字段包括FDRA字段、MCS字段和RV字段,等等。
如果DCI用于正常调度数据,而不用于实现DCP功能,那么DCI所包括的如上的字段的取值与所调度的数据有关,例如MCS字段的取值可以指示所调度的数据的MCS。而如果DCI用于实现DCP功能,那么第二字段的取值可以为第一值,第一值可以通过协议规定,或者可以默认,或者也可以由网络设备配置。例如第一值为全0,或者为全1等。通过这种取值,就能让UE明确,当前的DCI是用于实现DCP功能的。
如果第二字段的取值为第一值,那么该DCI还可以包括第二指示信息,而如果第二字段的取值不是第一值,则该DCI不包括第二指示信息。例如,第二字段的取值不是第一值,而是第二字段的普通(normal)取值,此时该DCI不用于实现DCP功能,而是实现该DCI的正常功能,例如调度数据等,那么该DCI自然无需包括第二指示信息。因此,如果第二字段的取值为第一值,则可以指示该DCI还包括第二指示信息。第二指示信息可以指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠,或者指示在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒。其中,在第二组载波上,按照第二DRX配置,用于实现DCP功能的DCI可以关联一个或多个DRX周期。如果该DCI是配置在第一组载波上,并没有配置在第二组载波上,则这种关联是时域位置上的关联,例如,在第二组载波上,在时域上晚于该DCI的一个或多个DRX周期,都可以与该DCI关联。且该DCI如果关联多个DRX周期,这多个DRX周期在时域上可以连续,也可以不连续。另外,第二DRX持续时间对应于第二DRX配置,第二DRX持续时间位于第二组载波上。第二DRX持续时间可包括第二DRX配置下该DCI所关联的全部或部分DRX周期内的On Duration时间,或者说,第二DRX持续时间可包括第二组载波上,该DCI所关联的全部或部分DRX周期内的On Duration时间。
例如,第二指示信息可以占用1个或多个比特。以第二指示信息占用1个比特为例,例如,如果该比特的取值为“1”,则指示在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒;如果该比特的取值为“0”,则指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠。或者,如果第二指示信息占用更多的比特,则还可以有其他的指示方式。通过DCI包括的第二指示信息就指示了UE在第二组载波上的休眠或唤醒,UE无需监听DCP,减少了UE需要监听的DCI size的个数,也对于UE在第二组载波上的休眠或唤醒进行了规范。而且由网络设备指示UE在第二组载波上的休眠或唤醒,则网络设备可根据UE在第二组载波上的业务进行指示,使得UE在第二组载波上的休眠或唤醒等行为更为符合UE的业务需求。
对于UE在第一组载波上的休眠或唤醒,有不同的实现方式,下面举例介绍。
作为一种可选的实施方式,可以默认(或者,协议规定),UE在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒。因为如果第二指示信息指示UE在第二组载波上在第二DRX持续时间内唤醒,且网络设备又需要在第一组载波上调度该UE在第二组载波上的数据传输,那么如果UE在第一组载波上在第一DRX持续时间内休眠,就可能无法接收来自网络设备的调度信息,从而无法在第二组载波上进行数据传输。因此可以默认(或者,协议规定)UE在第一组载波上在第一DRX持续时间内唤醒,以减少UE错过调度信息的概率,减小业务的传输时延。或者,可以默认(或者,协议规定),UE在第一组载波上, 在该DCI关联的第一DRX持续时间内休眠,通过这种方式能够节省UE的功耗。在这种方式下,第一载波可以属于第一组载波,或者属于第二组载波,即,网络设备可以在第一组载波上发送该DCI,或者在第二组载波上发送该DCI。
其中,在第一组载波上,按照第一DRX配置,用于实现DCP功能的DCI可以关联一个或多个DRX周期。例如,在第一组载波上,在时域上晚于该DCI的一个或多个DRX周期,都可以与该DCI关联。且该DCI如果关联多个DRX周期,这多个DRX周期在时域上可以连续,也可以不连续。另外,第一DRX持续时间对应于第一DRX配置,第一DRX持续时间位于第一组载波上。第一DRX持续时间可包括第一DRX配置下该DCI所关联的全部或部分DRX周期内的On Duration时间,或者说,第一DRX持续时间可包括第一组载波上,该DCI所关联的全部或部分DRX周期内的On Duration时间。
在这种情况下,该DCI只需包括第二指示信息,无需包括用于指示第一组载波的唤醒或休眠的指示信息,有助于节省信令开销。
作为另一种可选的实施方式,如果第二字段的取值为第一值,那么该DCI还可以包括第一指示信息,而如果第二字段的取值不是第一值,或者说,如果第二字段的取值为第二值,则该DCI不包括第一指示信息。第二值可以是第二字段除了第一值之外的任意取值。例如,第二字段的取值不是第一值,而是第二字段的普通取值,此时该DCI不用于实现DCP功能,而是实现该DCI的正常功能,例如调度数据等,那么该DCI自然无需包括第一指示信息。因此,如果第二字段的取值为第一值,则可以指示该DCI还包括第一指示信息。第一指示信息可以指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,或者指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒。可参考图11,以DCI配置在第一组载波上、第一组载波属于FR1、第二组载波属于FR2为例。UE在FR1上接收的DCI,能够指示UE在第二组载波上的休眠或唤醒,可选的,也能指示UE在第一组载波上的休眠或唤醒。其中,虚线箭头表示可选过程。在这种方式下,第一载波可以属于第一组载波,或者属于第二组载波,即,网络设备可以在第一组载波上发送该DCI,或者在第二组载波上发送该DCI。
例如,第一指示信息可以占用1个或多个比特。以第一指示信息占用1个比特为例,例如,如果该比特的取值为“1”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒;如果该比特的取值为“0”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠。或者,如果第一指示信息占用更多的比特,则还可以有其他的指示方式。通过DCI包括的第一指示信息就指示了UE在第一组载波上的休眠或唤醒,UE无需监听DCP,减少了UE需要监听的DCI size的个数,也对于UE在第一组载波上的休眠或唤醒进行了规范。而且由网络设备指示UE在第一组载波上的休眠或唤醒,则网络设备可根据UE在第一组载波上的业务进行指示,使得UE在第一组载波上的休眠或唤醒等行为更为符合UE的业务需求。
在这种实施方式下,网络设备通过第二指示信息和第一指示信息分别指示了两组载波的休眠或唤醒,使得UE的行为更为明确,也更为符合业务需求。
作为又一种可选的实施方式,如果DCI包括第二指示信息,则第二指示信息除了指示UE在第二组载波上的行为,也可以指示UE在第一组载波上的行为。即,第二指示信息可以指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠或唤醒,以及指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠或唤醒。或者,第二指示信息 指示在该DCI关联的DRX持续时间内休眠或唤醒。在这种方式下,第一载波可以属于第一组载波,或者属于第二组载波,即,网络设备可以在第一组载波上发送该DCI,或者在第二组载波上发送该DCI。
例如,第二指示信息占用一个或多个比特。以第二指示信息占用1比特为例,如果该比特的取值为“1”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒,以及指示在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒;如果该比特的取值为“0”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,以及指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠。或者,以第二指示信息占用2比特为例,则这2比特分别指示第一组载波和第二组载波。例如,这2比特中的高位比特指示第一组载波,低位比特指示第二组载波。如果这2比特中的高位比特的取值为“1”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒;如果这2比特中的高位比特的取值为“0”,则指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠。这2比特中的低位比特对于UE在第二组载波上的行为的指示方式也是类似的。
在这种方式下,网络设备通过第二指示信息就能指示UE在第一组载波和第二组载波上的行为,无需更多的指示信息,能够节省信令开销,而且使得UE的行为更为明确。
作为再一种可选的实施方式,第一载波可以包括至少两个载波,至少两个载波中,既包括属于第一组载波的载波,也包括属于第二组载波的载波。例如,第一载波包括第二载波和第三载波,第二载波属于第一组载波,第三载波属于第二组载波。这种情况可以理解为,网络设备既在第一组载波上发送DCI,也在第二组载波上发送DCI,那么所述的DCI也可以包括至少两个,以DCI包括第一DCI和第二DCI为例,第一DCI在第二载波上发送,第二DCI在第三载波上发送。那么,第一DCI可以指示UE在第一组载波上的行为,第二DCI可以指示UE在第二组载波上的行为。例如,第一DCI可以指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,或者指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒。第二DCI可以指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠,或者指示在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒。在这种情况下也可以认为,第一DCI包括第一指示信息,第二DCI包括第二指示信息。那么,第二DCI可以包括第二字段,第一DCI也可以包括第一字段。例如,如果第二字段的取值为第一值,那么第二DCI还可以包括第二指示信息,而如果第二字段的取值不是第一值,则第二DCI不包括第二指示信息。如果第一字段的取值为第三值,那么第一DCI还可以包括第一指示信息,而如果第一字段的取值不是第三值,则第一DCI不包括第一指示信息。对此实现方式的介绍,可参考前文。另外,关于第二指示信息对于UE在第二组载波上的行为的指示方式,以及第一指示信息对于UE在第一组载波上的行为的指示方式,也可参考前文的介绍。
在这种方式下,网络设备通过不同的载波上承载的DCI,可以分别指示UE在不同的载波上的行为,指示更为明确。
S102、UE根据DCI包括的第二指示信息确定,在第二组载波上,在该DCI关联的第二DRX持续时间内休眠或唤醒。或者也可以没有确定的过程,例如S102也可以替换为,UE根据DCI包括的第二指示信息,在第二组载波上,在该DCI关联的第二DRX持续时间内休眠或唤醒。或者,根据S101中的介绍,如果该DCI包括第一DCI和第二DCI,那么S102可以替换为,UE根据第二DCI包括的第二指示信息确定,在第二组载波上,在第 二DCI关联的第二DRX持续时间内休眠或唤醒。
如果该DCI包括的第二字段的取值为第一值,则UE确定该DCI包括第二指示信息。那么,如果第二指示信息指示在第二组载波上,在该DCI关联的第二DRX持续时间内休眠,则UE确定在第二组载波上,在该DCI关联的第二DRX持续时间内休眠,那么UE在第二组载波上就在第二DRX持续时间内休眠;或者,如果第二指示信息指示在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒,则UE确定在第二组载波上,在该DCI关联的第二DRX持续时间内唤醒,那么UE在第一组载波上就在第一DRX持续时间内休眠。
S103、UE确定在第一组载波上,在该DCI关联的第一DRX持续时间内休眠或唤醒。或者也可以没有确定的过程,例如S103也可以替换为,UE在第一组载波上,在该DCI关联的第一DRX持续时间内休眠或唤醒。或者,根据S101中的介绍,如果该DCI包括第一DCI和第二DCI,那么S103可以替换为,UE确定在第一组载波上,在第一DCI关联的第一DRX持续时间内休眠或唤醒。
如果默认(或者,协议规定),UE在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒,那么,如果网络设备未配置DCP,则UE在第一组载波上就在第一DRX持续时间内唤醒;或者,如果网络设备配置了DCP,那么,如果UE在第一组载波上不监听DCP,则UE在第一组载波上就在第一DRX持续时间内唤醒。或者,如果默认(或者,协议规定),UE在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,那么,如果网络设备未配置DCP,则UE在第一组载波上就在第一DRX持续时间内休眠;或者,如果网络设备配置了DCP,那么,如果UE在第一组载波上不监听DCP,则UE在第一组载波上就在第一DRX持续时间内唤醒。关于UE在何种情况下在第一组载波上不监听DCP,可参考图5所示的实施例的介绍。
或者,如果DCI还包括第一指示信息,且第一指示信息指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠。那么,如果DCI包括了第一指示信息,则UE在第一组载波上就在第一DRX持续时间内休眠;或者,如果DCI不包括第一指示信息,则UE在第一组载波上就在第一DRX持续时间内休眠。或者,如果DCI包括的第一指示信息指示在第一组载波上,在该DCI关联的第一DRX持续时间内唤醒,那么UE在第一组载波上就在第一DRX持续时间内唤醒;或者,如果DCI包括的第一指示信息指示在第一组载波上,在该DCI关联的第一DRX持续时间内休眠,那么UE在第一组载波上就在第一DRX持续时间内休眠。
或者,如果第二指示信息既指示UE在第一组载波上的行为,也指示UE在第二组载波上的行为,那么,如果第二指示信息指示在该DCI关联的DRX持续时间内休眠,则UE在第一组载波上在第一DRX持续时间内休眠,以及在第二组载波上在第二DRX持续时间内休眠;或者,如果第二指示信息指示在该DCI关联的DRX持续时间内唤醒,则UE在第一组载波上在第一DRX持续时间内唤醒,以及在第二组载波上在第二DRX持续时间内唤醒。
或者,如果所述DCI包括第一DCI和第二DCI,第一DCI包括第一指示信息,第二DCI包括第二指示信息,第二指示信息指示UE在第二组载波上的行为,第一指示信息指示UE在第一组载波上的行为。那么,如果第一DCI包括的第一指示信息指示在第一组载波上,在第一DCI关联的第一DRX持续时间内唤醒,那么UE在第一组载波上就在第一 DRX持续时间内唤醒;或者,如果第一DCI包括的第一指示信息指示在第一组载波上,在第一DCI关联的第一DRX持续时间内休眠,那么UE在第一组载波上就在第一DRX持续时间内休眠。如果第二DCI包括的第二指示信息指示在第二组载波上,在第二DCI关联的第二DRX持续时间内唤醒,那么UE在第二组载波上就在第二DRX持续时间内唤醒;或者,如果第二DCI包括的第二指示信息指示在第二组载波上,在第二DCI关联的第二DRX持续时间内休眠,那么UE在第二组载波上就在第二DRX持续时间内休眠。
对于网络设备来说,如果未配置DCP,则网络设备不必发送DCP,UE也无需监听DCP。而如果配置了DCP,例如为第一组载波配置了DCP,那么网络设备在第一组载波上可以正常发送DCP,以及,为了避免UE有时无法监听DCP,网络设备也发送能够实现DCP功能的DCI。如果是这种情况,则UE可以确定在第一组载波上是否能监听DCP,如果UE能够监听DCP,则UE可根据DCP的监听结果确定在第一组载波上的休眠或唤醒,而无需根据默认(或协议规定)的规则、第二指示信息、或第一指示信息等方式确定在第一组载波上的休眠或唤醒。或者,如果UE不能监听DCP,则UE可根据默认(或协议规定)的规则或根据第一指示信息确定在第一组载波上的休眠或唤醒。
关于其他内容,例如UE在DRX持续时间内休眠应如何实现,或者UE在DRX持续时间内唤醒应如何实现等,均可参考图5所示的实施例的相关介绍。
在本申请实施例中,两种DRX配置的技术能够与唤醒信号结合使用,而且本申请实施例无需配置DCP,而是通过普通的DCI实现DCP的功能,减少了UE需要监听的DCI size的个数,或者使得UE能够监听更多的DCI size,也简化了网络设备和UE的实现。而且可由网络设备通过相应的指示信息指示UE在载波组上的唤醒或休眠,指示方式更为灵活,更符合UE的业务传输需求,也增加了网络设备调度的灵活性。另外,本申请实施例也避免了通过默认方式规定UE在第二组载波上在第二DRX持续时间内唤醒,能够降低UE的功耗。
图5、图7或图10中的任一个附图所示的实施例,主要是考虑到将两组DRX配置与唤醒信号相结合的问题。而根据前文的介绍可知,对于跨载波调度和两组DRX配置,目前也没有结合使用。那么下面再提供第四种通信方法,以将跨载波调度和两组DRX配置结合使用,从而进一步降低UE的功耗。
请参考图12,为该方法的流程图。
S121、网络设备在第一载波上发送第二DCI,相应的,UE在第一载波上接收来自网络设备的第二DCI。
第一载波属于第一组载波,第一组载波包括为该UE配置的一个或多个载波,第一载波例如为第一组载波所包括的部分载波或全部载波。例如,网络设备为UE配置的主载波属于第一组载波,则第一载波可以是该UE的主载波,网络设备可以在主载波上发送第二DCI。
第二DCI可用于调度第二组载波上的数据,例如第二DCI调度的是新传数据,或者说,第二DCI可指示下行数据的新传,或者第二DCI可指示上行数据的新传。第二DCI可调度UE在第二组载波上接收数据或发送数据,也就是说,第二DCI实现的是跨载波调度。关于第一组载波和第二组载波等概念的介绍,可参考图5、图7或图10中的任一个附图所示的实施例。
S122、UE启动或重启第二DRX非激活定时器,并将第二DRX非激活定时器的时长 设置为第二DRX配置所配置的DRX非激活定时器的时长。
由于第二DCI调度了第二组载波上的数据,则后续可能有数据在第二组载波上传输,因此需要延长UE在第二组载波上的DRX激活时间,以保证UE在第二组载波上能够接收数据或发送数据,另外还能保证UE执行DRX激活时间内的相应行为,例如发送周期性的上行探测参考信号(sounding reference signal,SRS),或通过PUCCH上报信道状态信息(channel status information,CSI),或通过PUSCH上报半周期的报信道状态信息(channel status information,CSI),等等。
要延长UE在第二组载波上的DRX激活时间,一种实现方式是,启动或重启第二DRX非激活定时器。例如,UE可在第二DCI接收完毕后的第一个时域符号,启动或重启第二DRX非激活定时器。其中,在第二DCI接收完毕的第一个时域符号,如果第二DRX非激活定时器未运行,则UE启动第二DRX非激活定时器;或者,在第二DCI接收完毕的第一个时域符号,如果第二DRX非激活定时器处于运行状态,则UE重启第二DRX非激活定时器。
第二组载波应用的是第二DRX配置,第二DRX配置可以配置DRX周期、DRX非激活定时器以及DRX重传定时器等。第二DRX非激活定时器对应于第二组载波,或者说对应于第二DRX配置,可以理解为,第二DRX配置所配置的DRX非激活定时器就是第二DRX非激活定时器。那么在S122中,UE可将第二非激活定时器的时长设置为第二DRX非激活定时器原本的时长,即第二DRX配置所配置的DRX非激活定时器的时长。通过启动或重启第二DRX非激活定时器,就延长了UE在第二组载波上的DRX激活时间,使得UE在第二组载波上能够接收数据或发送数据。
UE启动或重启第二DRX非激活定时器,一种实现方式为,UE默认(或者,协议规定),在接收第二DCI后就启动或重启第二DRX非激活定时器。这种方式无需网络设备额外通知,能够节省信令开销。
或者,UE启动或重启第二DRX非激活定时器,另一种实现方式为,由网络设备指示。例如,第二DCI可以包括第二指示信息,第二指示信息可指示启动或重启第二DRX非激活定时器。如果是这种方式,那么可能有两种情况。一种情况为,如果第二DCI包括第二指示信息,则指示启动或重启第二DRX非激活定时器,UE启动或重启第二DRX非激活定时器;而如果第二DCI不包括第二指示信息,则指示不启动也不重启第二DRX非激活定时器,UE不启动也不重启第二DRX非激活定时器。在这种情况下,第二DCI可能包括第二指示信息也可能不包括第二指示信息,能够节省第二DCI的信令开销。或者,另一种情况为,如果第二DCI包括的第二指示信息指示启动或重启第二DRX非激活定时器,UE启动或重启第二DRX非激活定时器;而如果第二DCI包括的第二指示信息指示不启动也不重启第二DRX非激活定时器,则UE不启动也不重启第二DRX非激活定时器。通过第二DCI进行指示,使得UE更为明确UE的行为。
其中,第二指示信息可通过第二DCI中的已有字段承载,例如第二DCI包括的已有字段中有预留(reserved)比特,则可以通过预留比特承载;或者,可以在第二DCI中新增一个或多个比特,以承载第二指示信息。
S123、UE延长UE在第一组载波上的DRX激活时间。
由于第二组载波上有数据传输,而第二DCI是跨载波调度,那么后续网络设备还可能通过跨载波调度的方式来调度第二组载波上的数据。另外,网络设备也可能在第一组载波 上调度第一组载波上的数据。因此,可以延长UE在第一组载波上的DRX激活时间,以接收用于调度数据的DCI。
UE要延长UE在第一组载波上的DRX激活时间,可以有不同的实现方式,下面举例介绍。
1、第一种方式:通过第一DRX非激活定时器延长UE在第一组载波上的DRX激活时间。
第一组载波应用的是第一DRX配置,第一DRX配置可以配置DRX周期、DRX非激活定时器以及DRX重传定时器等。第一DRX非激活定时器对应于第一组载波,或者说对应于第一DRX配置,可以理解为,第一DRX配置所配置的DRX非激活定时器就是第一DRX非激活定时器。那么在S123中,UE可启动或重启第一DRX非激活定时器,通过这种方式,可以延长UE在第一组载波上的DRX激活时间,使得UE在第一组载波上能够接收DCI。
UE还需要设置第一DRX非激活定时器的时长。作为一种可选的实施方式,UE可将第一DRX非激活定时器的时长设置为第一DRX非激活定时器原本的时长,即第一DRX配置所配置的DRX非激活定时器的时长。这种设置方式较为简单,也是UE容易实现的设置。
以第一组载波的频率属于FR1、第二组载波的频率属于FR2为例,由于UE工作在FR2时功耗较大,因此UE可能更多地会工作在第一组载波上,因此,第一DRX配置所配置的DRX非激活定时器的时长可能比较长。如果将第一DRX非激活定时器的时长设置为第一DRX配置所配置的DRX非激活定时器的时长,可能导致UE在第一组载波上的DRX激活时间被延长的过长,例如网络设备可能已不再调度第二组载波的数据,UE在第二组载波上可能已经进入了DRX非激活时间,但UE在第一组载波上还处于DRX激活时间,这可能导致UE在第一组载波上的功耗增大。可参考图13,对应于FR1的第一DRX非激活定时器的运行时间要长于对应于FR2的第二DRX非激活定时器的运行时间,在第二DRX非激活定时器已停止运行后,UE在FR1上还处于DRX激活时间。对此有一种解决方式,网络设备可以发送第一信令,第一信令可指示UE停止第一DRX非激活定时器。UE接收第一信令后可以停止运行第一DRX非激活定时器。第一信令例如为DCI,或者也可以是无线资源控制(radio resource control,RRC)信令等。但这需要消耗额外的信令。
为了解决如上的问题,作为另一种可选的实施方式,UE在需要设置第一DRX非激活定时器的时长时,例如在启动第一DRX非激活定时器时,或者在启动第一DRX非激活定时器之前,不将第一DRX非激活定时器的时长设置为第一DRX配置所配置的DRX非激活定时器的时长,而是将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长。对于UE将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长,也可理解为,UE将第一DRX非激活定时器的时长设置为第二DRX非激活定时器的时长。如果采用这种方式,则UE在第一组载波上的DRX激活时间的持续时间与UE在第二组载波上的DRX激活时间的持续时间可能是一致的,UE在第一组载波上既能接收用于调度第二组载波的数据的DCI,也不会因为在第一组载波上的DRX激活时间过长而导致过于耗电。可参考图14,对应于FR1的第一DRX非激活定时器的运行时间与对应于FR2的第二DRX非激活定时器的运行时间相同。
UE究竟将第一DRX非激活定时器的时长设置为何种时长,可以默认,或者通过协议 规定。或者,UE也可以根据相应的情况确定究竟将第一DRX非激活定时器的时长设置为何种时长。例如,如果UE在启动或重启第一DRX非激活定时器之前在第一组载波上接收了第一DCI,且第一DCI用于调度UE在第一组载波上接收数据或发送数据,那么UE可以将第一DRX非激活定时器的时长设置为第一DRX配置所配置的DRX非激活定时器的时长,以满足UE在第一组载波上的接收数据或发送数据的需求,也能满足UE在第一组载波上接收对应于第一组载波的数据的调度的需求。
考虑一个问题,UE在启动或重启第一DRX非激活定时器之前,如果第一DRX非激活定时器处于运行状态,且如果第一DRX非激活定时器的剩余时长要长于第二DRX配置所配置的DRX非激活定时器的时长,则如果UE重启第一DRX非激活定时器,就会使得第一DRX非激活定时器的时长忽长忽短,增加UE处理的复杂度。因此,作为一种可选的实施方式,UE也不必在任何情况下均启动或重启第一DRX非激活定时器,而是可以先确定是否需要启动或重启第一DRX非激活定时器。例如,UE在启动或重启第一DRX非激活定时器之前,如果第一DRX非激活定时器处于运行状态,则UE可以确定第一DRX非激活定时器的剩余时长与第二DRX配置所配置的DRX非激活定时器的时长之间的大小关系。如果第一DRX非激活定时器的剩余时长要短于第二DRX配置所配置的DRX非激活定时器的时长,那么UE可以将第一DRX非激活定时器的时长设置为第二DRX配置所配置的DRX非激活定时器的时长;或者,如果第一DRX非激活定时器的剩余时长要长于或等于第二DRX配置所配置的DRX非激活定时器的时长,那么UE可以不必重启第一DRX非激活定时器。在这种情况下,虽然UE并没有重启第一DRX非激活定时器,但由于第一DRX非激活定时器处于运行状态,且第一DRX非激活定时器的剩余时长要长于或等于第二DRX配置所配置的DRX非激活定时器的时长,表明UE在第一组载波上的DRX激活时间无需额外延长,而是已经能够满足需求。
UE究竟是否要启动第一DRX非激活定时器,可以默认,或者通过协议规定。例如协议规定,如果UE在第一组载波上接收了用于调度第二组载波上的数据的DCI,则UE启动第一DRX非激活定时器。或者,UE究竟是否要启动第一DRX非激活定时器,也可以由网络设备配置。例如,第二DCI可以包括第一指示信息,第一指示信息可以指示启动或重启第一DRX非激活定时器。如果是这种方式,那么可能有两种情况。一种情况为,如果第二DCI包括第一指示信息,则指示启动或重启第一DRX非激活定时器,UE启动或重启第一DRX非激活定时器;而如果第二DCI不包括第一指示信息,则指示不启动也不重启第一DRX非激活定时器,UE不启动也不重启第一DRX非激活定时器。在这种情况下,第二DCI可能包括第一指示信息也可能不包括第一指示信息,能够节省第二DCI的信令开销。或者,另一种情况为,如果第二DCI包括的第一指示信息指示启动或重启第一DRX非激活定时器,UE启动或重启第一DRX非激活定时器;而如果第二DCI包括的第一指示信息指示不启动也不重启第一DRX非激活定时器,则UE不启动也不重启第一DRX非激活定时器。通过第二DCI进行指示,使得UE更为明确UE的行为。
可选的,如果第二DCI包括第一指示信息,那么第一指示信息除了可以指示UE启动或重启第一DRX非激活定时器外,还可以指示如何设置第一DRX非激活定时器的时长。例如,第一指示信息可以指示将第一DRX非激活定时器的定时时长设置为第一DRX配置所配置的DRX非激活定时器的时长,或指示将第一DRX非激活定时器的定时时长设置为第二DRX配置所配置的DRX非激活定时器的时长,则UE可以根据第一指示信息设置第 一DRX非激活定时器的时长。或者,第二DCI也可以通过其他信息来指示如何设置第一DRX非激活定时器的时长,例如第二DCI还可以包括第三指示信息,第三指示信息可以指示将第一DRX非激活定时器的定时时长设置为第一DRX配置所配置的DRX非激活定时器的时长,或指示将第一DRX非激活定时器的定时时长设置为第二DRX配置所配置的DRX非激活定时器的时长。通过相应的指示信息指示第一DRX非激活定时器的时长的设置方式,UE无需自行确定第一DRX非激活定时器的时长应该如何设置,简化UE的实现。
2、第二种方式:UE延长UE在第一组载波上的DRX激活时间。
在第二种方式下,无需借助于第一DRX非激活定时器,UE由于已知第二DRX非激活定时器的结束时刻,或者说,UE已知UE在第二组载波上的DRX激活时间的结束时刻,因此UE可将UE在第一组载波上的DRX激活时间进行延长,例如将UE在第一组载波上的DRX激活时间的结束时刻延长到与UE在第二组载波上的DRX激活时间的结束时刻相同。如果采用这种方式,则UE在第一组载波上的DRX激活时间的持续时间与UE在第二组载波上的DRX激活时间的持续时间是一致的,UE在第一组载波上既能接收用于调度第二组载波的数据的DCI,也不会因为在第一组载波上的DRX激活时间过长而导致过于耗电。而且这种方式也无需借助于第一DRX非激活时间定时器,减少了UE维护第一DRX非激活时间定时器所带来的功耗。
可参考图15,UE延长了UE在第一组载波上的DRX激活时间(图15中的虚线框表示延长的时间),使得对应于FR1的第一DRX非激活定时器的运行时间与对应于FR2的第二DRX非激活定时器的运行时间相同。可理解为,本申请实施例将第一组载波上的DRX激活时间(即第一DRX配置的DRX激活时间)定义为,是第一组载波上第一DRX配置对应的DRX激活时间与第二组载波上第二DRX配置对应的DRX激活时间的并集。
其中,S122与S123可以同时执行,或者S122可以在S123之前执行,或者S122可以在S123之后执行。
在本申请实施例中,两种DRX配置的技术能够与跨载波调度技术结合使用,在实现跨载波调度时,UE在第一组载波上能够接收来自网络设备的用于调度第二组载波上的数据的DCI,以及UE在第二组载波上也能接收数据或发送数据,使得在两种DRX配置技术的背景下,跨载波调度技术得以实现。而且本申请实施例可以根据不同的情况将对应于第一组载波的第一DRX非激活定时器的时长设置为不同的时长,使得第一DRX非激活定时器的时长更为符合当前的业务传输需求,也更节省UE的功耗。
例如,如果UE(如智能手机、智能手表或智能手环等)有节能需求,UE可以向网络设备发送节能能力信息或节能指示,该节能能力信息指示UE支持第一方案,该节能指示用于指示UE有节能需求,或者指示UE请求应用第一方案。或者,如果UE请求应用能够节能的第一方案,UE也可以向网络设备发送所述节能能力信息或所述节能指示。其中,所述第一方案为图5、图8、图10或图12中的任一个附图所示的实施例提供的方案。网络设备接收来自UE的所述节能能力信息或所述节能指示后,如果网络设备已经为UE配置了第一DRX配置、第二DRX配置以及DCP(或,DCI),则网络设备确定UE应用第一方案。可选的,网络设备可以向UE发送节能允许信息或与第一方案相关的配置信息,以指示允许该UE节能,或者指示允许该UE应用第一方案。UE接收来自网络设备的节能允许信息或与第一方案相关的配置信息后,就能够应用第一方案。或者,网络设备接收来自UE的所述节能能力信息或所述节能指示后,如果网络设备仅为该UE配置了第一DRX配 置,则网络设备可以向该UE发送第二DRX配置。UE接收第二DRX配置后,就能够应用第一方案。UE在应用第一方案后,能够进一步降低功耗,即减少消耗的电池电量,延长UE的待机时间。
另外,介绍如下三种规则。
规则1、第一DRX激活时间的时间长度大于或等于第二DRX激活时间的时间长度。
可选的,第一组载波对应第一DRX激活时间,第一DRX激活时间例如包括UE在第一组载波上,在第一DRX配置下的全部或部分DRX激活时间。第二组载波对应第二DRX激活时间,第二DRX激活时间例如包括UE在第二组载波上,在第二DRX配置下的全部或部分DRX激活时间。考虑到网络设备可能在第一组载波上调度UE在第二组载波上接收数据或发送数据,因此UE需要在第一组载波上接收对应于第二组载波的调度信息,调度信息例如承载在通过PDCCH发送的DCI中。那么,如果第一DRX激活时间的时间长度小于第二DRX激活时间的时间长度,可能会出现一种情况,UE在第一组载波上进入了休眠状态,但网络设备又在第一组载波上发送了用于调度第二组载波上的数据传输的DCI,此时UE可能因为休眠而无法接收该DCI,导致UE无法在第二组载波上传输数据。为了减少这种情况出现的概率,本申请实施例提出,令第一DRX激活时间的时间长度大于或等于第二DRX激活时间的时间长度,另外,还可以令第一DRX激活时间在时域上能够覆盖第二DRX激活时间,例如使得第二DRX激活时间在时域上位于第一DRX激活时间内,或者令第二DRX激活时间在时域上与第一DRX激活时间重合,使得UE能够在第一组载波上接收来自网络设备的调度信息。
令第一DRX激活时间的时间长度大于或等于第二DRX激活时间的时间长度,例如一种实现方式为,令第一DRX配置所配置的全部或部分定时器的时长大于或等于第二DRX配置所配置的相应定时器的时长。例如,令第一DRX持续时间定时器的时长大于或等于第二DRX持续时间定时器的时长,第一DRX持续时间定时器是第一DRX配置所配置的,第二DRX持续时间定时器是第二DRX配置所配置的。又例如,令第一DRX持续时间定时器的时长大于或等于第二DRX持续时间定时器的时长,以及,令第一DRX非激活定时器的时长大于或等于第二DRX非激活定时器的时长,第一DRX非激活定时器是第一DRX配置所配置的,第二DRX非激活定时器是第二DRX配置所配置的。再例如,令第一DRX持续时间定时器的时长大于或等于第二DRX持续时间定时器的时长,令第一DRX非激活定时器的时长大于或等于第二DRX非激活定时器的时长,以及,令第一DRX重传定时器的时长大于或等于第二DRX重传定时器的时长,第一DRX重传定时器是第一DRX配置所配置的,第二DRX重传定时器是第二DRX配置所配置的。
规则1可以通过协议规定,或者可以默认,或者可以由网络设备配置。
规则2、配置第一组载波上的DCI调度第二组载波的数据传输,而不配置第二组载波上的DCI调度第一组载波的数据传输。
其中第二频率范围的频率大于第一频率范围的频率,例如第二组载波的频率属于FR2,第一组载波的频率属于FR1。由于FR2的频率大于FR1的频率,UE在FR2的载波上工作时功耗会更大,因此可选的,本申请实施例中如果配置跨载波调度,那么可以配置通过第一组载波调度第二组载波,即,配置第一组载波上的DCI调度第二组载波的数据传输,而不配置第二组载波上的DCI调度第一组载波的数据传输。这样UE只需在第一组载波上监听DCI就能完成在第二组载波上的数据传输,无需在第二组载波上监听DCI,节省UE的 功耗。规则2可以通过协议规定,或者可以默认,或者可以由网络设备配置。
规则3、在第一组载波上所调度的第二组载波上的数据传输时间,位于UE在第二组载波上的DRX激活时间内。
如果支持跨载波调度,那么还可能出现一种情况。例如配置了第一组载波上的DCI调度第二组载波的数据传输,那么网络设备在第一组载波上发送的DCI所调度的第二组载波上的数据的传输时间,可能位于UE在第二组载波上的DRX非激活时间内。例如可参考图7,网络设备在FR1的载波上发送了DCI,该DCI调度FR2的载波上的数据传输。UE在第一组载波上,在一个DRX周期内的On Duration时间内接收了该DCI,该DCI所调度的数据传输时间例如为图7中的T1时间,在T1时间,UE在第二组载波上的DRX非激活定时器已超时,因此T1位于UE在第二组载波上的DRX非激活时间内。如果是这种情况,UE在DRX非激活时间内还需要接收PUSCH或PDSCH,这会给UE带来额外的功耗。因此可选的,本申请实施例规定,网络设备在第一组载波上所调度的第二组载波上的数据传输时间,需要位于UE在第二组载波上的DRX激活时间内,这样,UE在第二组载波上无需在DRX非激活时间内再接收PUSCH或PDSCH,而是可以进入休眠状态,以节省功耗。规则3可以通过协议规定,或者可以默认,或者可以由网络设备配置。
如上的三种规则可以与图5所示的实施例结合应用,或者可以与图8所示的实施例结合应用,或者可以与图10所示的实施例结合应用,或者可以与图12所示的实施例结合应用。或者,如上的三种规则也可以单独应用,不与前述的任一方法实施例相结合。另外,在单独应用时,可以应用如上的一种或多种规则,即,如上三种规则中的任意两种或三种可以结合应用,或者,如上的三种规则也可以不结合,而是分别单独应用。例如,可以应用规则1而不应用规则2和规则3;或者,可以应用规则2而不应用规则1和规则3;或者,可以应用规则3而不应用规则1和规则2;或者,可以应用规则1和规则2而不应用规则3;或者,可以应用规则1和规则3而不应用规则2;或者,可以应用规则2和规则3而不应用规则1;或者,可以应用规则1、规则2和规则3。
下面结合附图介绍本申请实施例中用来实现上述方法的装置。因此,上文中的内容均可以用于后续实施例中,重复的内容不再赘述。
图16为本申请实施例提供的通信装置1600的示意性框图。示例性地,通信装置1600例如为终端设备,或者为网络设备。示例性地,通信装置1600能够实现图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例所述的UE的功能。或者,通信装置1600能够实现图10所示的实施例所述的网络设备的功能。
通信装置1600包括收发单元1620和处理单元1610。可选地,通信装置1600还可以包括存储单元,存储单元能够与处理单元1610通信,在图16中并未表示出来。或者,通信装置1600也可以不包括存储单元,存储单元也可以位于通信装置1600外部。示例性地,通信装置1600可以是UE,也可以是应用于UE中的芯片或者其他具有上述UE功能的组合器件、部件等,或者,通信装置1600可以是网络设备,也可以是应用于网络设备中的芯片或者其他具有上述网络设备功能的组合器件、部件等。当通信装置1600是UE或网络设备时,处理单元1610可以包括处理器,例如基带处理器,基带处理器中可以包括一个或多个中央处理单元(central processing unit,CPU);收发单元1620可以是收发器,收发器可以包括天线和射频电路等。其中,收发器可包括发射器和接收器,收发器可实现发射器和接收器的功能,或者,发射器和接收器也可以是单独部署的两个功能模块,只是本申 请实施例将这两个功能模块统称为收发器。当通信装置1600是具有上述UE或网络设备功能的部件时,收发单元1620可以是射频单元,处理单元1610可以是处理器,例如基带处理器。当通信装置1600是芯片***时,收发单元1620可以是芯片(例如基带芯片)的输入输出接口、处理单元1610可以是芯片***的处理器,可以包括一个或多个中央处理单元。应理解,本申请实施例中的处理单元1610可以由处理器或处理器相关电路组件实现,收发单元1620可以由收发器或收发器相关电路组件实现。
在一种实施方式中,当通信装置1600用于实现图5所示的实施例所述的UE的功能时,处理单元1610可以用于执行图5所示的实施例中由UE所执行的除了收发操作之外的全部操作,例如S51~S53,和/或用于支持本文所描述的技术的其它过程。收发单元1620可以用于执行图5所示的实施例中由UE所执行的全部接收操作和发送操作,例如监听DCP的操作,和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中,当通信装置1600用于实现图8所示的实施例所述的UE的功能时,处理单元1610可以用于执行图8所示的实施例中由UE所执行的除了收发操作之外的全部操作,例如S81~S85,和/或用于支持本文所描述的技术的其它过程。收发单元1620可以用于执行图8所示的实施例中由UE所执行的全部接收操作和发送操作,例如监听DCP的操作,和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中,当通信装置1600用于实现图10所示的实施例所述的UE的功能时,处理单元1610可以用于执行图10所示的实施例中由UE所执行的除了收发操作之外的全部操作,例如S102~S103,和/或用于支持本文所描述的技术的其它过程。收发单元1620可以用于执行图10所示的实施例中由UE所执行的全部接收操作和发送操作,例如S101,和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中,当通信装置1600用于实现图10所示的实施例所述的网络设备的功能时,处理单元1610可以用于执行图10所示的实施例中由网络设备所执行的除了收发操作之外的全部操作,和/或用于支持本文所描述的技术的其它过程。收发单元1620可以用于执行图10所示的实施例中由网络设备所执行的全部接收操作和发送操作,例如S101,和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中,当通信装置1600用于实现图12所示的实施例所述的UE的功能时,处理单元1610可以用于执行图12所示的实施例中由UE所执行的除了收发操作之外的全部操作,例如S122~S123,和/或用于支持本文所描述的技术的其它过程。收发单元1620可以用于执行图12所示的实施例中由UE所执行的全部接收操作和发送操作,例如S121,和/或用于支持本文所描述的技术的其它过程。
另外,收发单元1620可以是一个功能模块,该功能模块既能完成发送操作也能完成接收操作,例如收发单元1620可以用于执行图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中由第一终端设备或网络设备(例如,核心网设备或接入网设备)所执行的全部发送操作和接收操作。例如,在执行接收操作时,可以认为收发单元1620是接收单元,而在执行发送操作时,可以认为收发单元1620是发送单元。或者,收发单元1620也可以是两个功能模块,收发单元1620可以视为这两个功能模块的统称,这两个功能模块包括接收单元和发送单元,发送单元用于完成发送操作,例如发送单元可以用于执行图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中由第一终端设备或网络设备所执行的全部发送操作;接收单元用于完成接收 操作,例如接收单元可以用于执行图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中由第一终端设备或网络设备所执行的全部接收操作。
关于处理单元1610和收发单元1620所具体能够实现的功能,可参考图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中对于终端设备所执行的操作的介绍,或者参考图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中对于网络设备(例如,接入网设备或核心网设备)所执行的操作的介绍,不多赘述。
本申请实施例还提供一种通信装置,该通信装置可以是终端设备也可以是电路。该通信装置可以用于执行上述各个方法实施例中由终端设备所执行的动作。
当该通信装置为终端设备时,图17示出了一种简化的终端设备的结构示意图。便于理解和图示方便,图17中,终端设备以手机作为例子。如图17所示,终端设备包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理,以及对终端设备进行控制,执行软件程序,处理软件程序的数据等。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置,例如触摸屏、显示屏,键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是,有些种类的终端设备可以不具有输入输出装置。
当需要发送数据时,处理器对待发送的数据进行基带处理后,输出基带信号至射频电路,射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时,射频电路通过天线接收到射频信号,将射频信号转换为基带信号,并将基带信号输出至处理器,处理器将基带信号转换为数据并对该数据进行处理。为便于说明,图17中仅示出了一个存储器和处理器。在实际的终端设备产品中,可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置,也可以是与处理器集成在一起,本申请实施例对此不做限制。
在本申请实施例中,可以将具有收发功能的天线和射频电路视为终端设备的收发单元(收发单元可以是一个功能单元,该功能单元能够实现发送功能和接收功能;或者,收发单元也可以包括两个功能单元,分别为能够实现接收功能的接收单元和能够实现发送功能的发送单元),将具有处理功能的处理器视为终端设备的处理单元。如图17所示,终端设备包括收发单元1710和处理单元1720。收发单元也可以称为收发器、收发机、收发装置等。处理单元也可以称为处理器,处理单板,处理模块、处理装置等。可选的,可以将收发单元1710中用于实现接收功能的器件视为接收单元,将收发单元1710中用于实现发送功能的器件视为发送单元,即收发单元1710包括接收单元和发送单元。收发单元有时也可以称为收发机、收发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
应理解,收发单元1710用于执行上述图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中终端设备侧的发送操作和接收操作,处理单元1720用于执行上述图5所示的实施例或图8所示的实施例或图10所示的实施例或图12所示的实施例中第一终端设备侧除了收发操作之外的其他操作。
当该通信装置为芯片类的装置或者电路时,该装置可以包括收发单元和处理单元。其 中,所述收发单元可以是输入输出电路和/或通信接口;处理单元为集成的处理器或者微处理器或者集成电路。
应理解,本申请实施例中提及的处理器可以是CPU,还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
需要说明的是,当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时,存储器(存储模块)集成在处理器中。
应注意,本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中,应该理解到,所揭露的***、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的计算机可读存储介质,可以是计算机能够存取的任何可用介质。以此为例但不限于:计算机可读介质可以包括随机存取存储器(random access memory,RAM)、只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦可编程只读存储器(electrically erasable programmable read only memory,EEPROM)、紧凑型光盘只读存储器(compact disc read-only memory,CD-ROM)、通用串行总线闪存盘(universal serial bus flash disk)、移动 硬盘、或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。另外,通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)或直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
以上所述,仅为本申请的具体实施方式,但本申请实施例的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请实施例的保护范围之内。因此,本申请实施例的保护范围应所述以权利要求的保护范围为准。
Claims (26)
- 一种通信方法,其特征在于,包括:终端设备确定在第一使用节能无线网络临时标识加扰的带循环冗余校验的下行控制信息DCP监听时机内是否监听DCP;在所述终端设备确定在所述第一DCP监听时机内不监听DCP的情况下,在第一组载波上,所述终端设备在所述第一DCP监听时机关联的第一非连续接收DRX持续时间内唤醒,以及,在第二组载波上,所述终端设备在所述第一DCP监听时机关联的第二DRX持续时间内唤醒或休眠,其中,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一DRX配置,所述第一DRX持续时间对应所述第一DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波应用第二DRX配置,所述第二DRX持续时间对应所述第二DRX配置。
- 根据权利要求1所述的方法,其特征在于,所述第一DCP监听时机配置在所述第一组载波上。
- 根据权利要求1或2所述的方法,其特征在于,所述第一DRX持续时间在时域上位于所述第一DCP监听时机之后。
- 根据权利要求1~3任一项所述的方法,其特征在于,终端设备确定是否在第一DCP监听时机内监听DCP,包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间;或,在最多能够监听的下行控制信息DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间。
- 根据权利要求1~4任一项所述的方法,其特征在于,所述方法还包括:所述终端设备接收来自网络设备的配置信息,所述配置信息用于配置:在所述终端设备在DCP监听时机内不监听的情况下,所述终端设备在所述DCP监听时机关联的所述第二DRX持续时间内唤醒或休眠。
- 根据权利要求1~5任一项所述的方法,其特征在于,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,所述终端设备 在所述第一DCP监听时机内监听DCP;所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒。
- 根据权利要求6所述的方法,其特征在于,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP、且所述第一DCP指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述终端设备在所述第一DCP监听时机内未接收来自所述网络设备的DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠。
- 根据权利要求6所述的方法,其特征在于,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内唤醒,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP、且所述第一DCP指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒;或,在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒。
- 根据权利要求6所述的方法,其特征在于,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒,包括:在所述终端设备在所述第一DCP监听时机内接收来自所述网络设备的第一DCP,且所述第一DCP包括第一指示信息和第二指示信息;其中,在所述第一指示信息指示唤醒,以及所述第二指示信息指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒;或,在所述第一指示信息指示休眠,以及所述第二指示信息指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述第一指示信息指示唤醒,以及所述第二指示信息指示休眠的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,以及,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠;或,在所述第一指示信息指示休眠,以及所述第二指示信息指示唤醒的情况下,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,以及,在所述第二组载波 上,所述终端设备在所述第二DRX持续时间内唤醒。
- 根据权利要求6~9任一项所述的方法,其特征在于,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内休眠,包括:所述终端设备在所述第一DRX持续时间的起始时刻不启动以及不重启第一DRX持续时间定时器,所述第一DRX持续时间定时器对应所述第一DRX配置。
- 根据权利要求6~10任一项所述的方法,其特征在于,在所述第一组载波上,所述终端设备在所述第一DRX持续时间内唤醒,包括:所述终端设备在所述第一DRX持续时间的起始时刻启动或重启第一DRX持续时间定时器,所述第一DRX持续时间定时器对应所述第一DRX配置。
- 根据权利要求6~11任一项所述的方法,其特征在于,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内休眠,包括:所述终端设备在所述第二DRX持续时间的起始时刻不启动以及不重启第二DRX持续时间定时器,所述第二DRX持续时间定时器对应所述第二DRX配置。
- 根据权利要求6~12任一项所述的方法,其特征在于,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒,包括:所述终端设备在所述第二DRX持续时间的起始时刻启动或重启第二DRX持续时间定时器,所述第二DRX持续时间定时器对应所述第二DRX配置。
- 根据权利要求1~13任一项所述的方法,其特征在于,所述第一组载波所属的频率范围与所述第二组载波所属的频率范围不同;或,所述第二组载波所属的频率范围对应的频率大于所述第一组载波所属的频率范围对应的频率;或,所述第一组载波对应的DRX激活时间的长度大于或等于所述第二组载波对应的DRX激活时间的长度。
- 一种通信方法,其特征在于,包括:在终端设备确定在第一使用节能无线网络临时标识加扰的带循环冗余校验的下行控制信息DCP监听时机内不监听DCP的情况下,所述终端设备确定在第二DCP监听时机内是否监听DCP,所述第一DCP监听时机配置在第一组载波上,所述第二DCP监听时机配置在第二组载波上,所述第一组载波包括配置给所述终端设备的一个或多个载波,所述第一组载波应用第一非连续接收DRX配置,所述第二组载波包括配置给所述终端设备的一个或多个载波,所述第二组载波应用第二DRX配置;在所述终端设备确定在所述第二DCP监听时机内监听DCP的情况下,所述终端设备在所述第二DCP监听时机内监听DCP,并根据对DCP的监听情况,在所述第二组载波上,在所述第二DCP监听时机关联的第二DRX持续时间内休眠或唤醒,所述第二DRX持续时间对应所述第二DRX配置。
- 根据权利要求15所述的方法,其特征在于,所述方法还包括:所述终端设备确定在所述第一DCP监听时机内是否监听DCP。
- 根据权利要求15或16所述的方法,其特征在于,所述方法还包括:在所述终端设备确定在所述第二DCP监听时机内不监听DCP的情况下,在所述第二组载波上,所述终端设备在所述第二DRX持续时间内唤醒。
- 根据权利要求15~17任一项所述的方法,其特征在于,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,所述终端设备根据对DCP的监听情况,在所述第一组载波上,在所述第一DCP监听时机关联的第一DRX持续时间内休眠或唤醒,以及,在所述第二组载波上,在所述第二DRX持续时间内休眠或唤醒,所述第一DRX持续时间对应所述第一DRX配置。
- 根据权利要求15~18任一项所述的方法,其特征在于,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内监听DCP的情况下,在所述第二组载波上,所述终端设备不在所述第二DCP监听时机内进行监听。
- 根据权利要求15~19任一项所述的方法,其特征在于,所述方法还包括:在所述终端设备确定在所述第一DCP监听时机内不监听DCP的情况下,在所述第一组载波上,所述终端设备在所述第一DCP监听时机关联的第一DRX持续时间内唤醒,所述第一DRX持续时间对应所述第一DRX配置。
- 根据权利要求16所述的方法,其特征在于,所述终端设备确定在所述第一DCP监听时机内是否监听DCP,包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第一DCP监听时机的时域位置没有位于或部分位于第一DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间;或,在最多能够监听的下行控制信息DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;或者,在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;其中,所述第一DRX激活时间为所述第一DRX配置对应的DRX激活时间。
- 根据权利要求15~21任一项所述的方法,其特征在于,所述终端设备确定在第二DCP监听时机内是否监听DCP,包括:在所述第二DCP监听时机的时域位置位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP;或者,在所述第二DCP监听时机的时域位置没有位于或部分位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内监听DCP;其中,所述第二DRX激活时间为所述第二DRX配置对应的DRX激活时间;或,在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内监听DCP;或者,在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内不监听DCP;或,在所述第二DCP监听时机的时域位置位于第二DRX激活时间内,且在最多能够监听的DCI的大小的个数大于或等于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内监听DCP;或者,在所述第二DCP监听时机的时域位置位于第二DRX激活时间内,且在最多能够监听的DCI的大小的个数小于所述终端设备需要监听的DCI的大小的个数的情况下,所述终端设备确定在所述第二DCP监听时机内不监听DCP。
- 根据权利要求15~22任一项所述的方法,其特征在于,所述终端设备确定在所述第一DCP监听时机内不监听DCP,且确定在所述第二DCP监听时机内监听DCP,包括:在所述第一DCP监听时机的时域位置位于第一DRX激活时间内,且所述第二DCP监听时机的时域位置没有位于或部分位于第二DRX激活时间内的情况下,所述终端设备确定在所述第一DCP监听时机内不监听DCP,以及,确定在所述第二DCP监听时机内监听DCP。
- 一种终端设备,其特征在于,包括:一个或多个处理器;一个或多个存储器;以及一个或多个计算机程序,其中所述一个或多个计算机程序被存储在所述一个或多个存储器中,所述一个或多个计算机程序包括指令,当所述指令被所述终端设备的一个或多个处理器执行时,使得所述终端设备执行如权利要求1~14中任一项所述的由终端设备所执行的方法,或使得所述终端设备执行如权利要求15~23中任一项所述的由终端设备所执行的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质用于存储计算机程序,当所述计算机程序在计算机上运行时,使得所述计算机执行如权利要求1~14中任一项所述的由终端设备所执行的方法,或者使得所述计算机执行如权利要求15~23中任一项所述的由终端设备所执行的方法。
- 一种芯片,其特征在于,包括一个或多个处理器和通信接口,所述一个或多个处理器用于读取指令,以执行如权利要求1~14中任一项所述的由终端设备所执行的方法,或者执行如权利要求15~23中任一项所述的由终端设备所执行的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP21871062.2A EP4207884A4 (en) | 2020-09-27 | 2021-08-03 | COMMUNICATION METHOD AND DEVICE |
US18/246,641 US20230371118A1 (en) | 2020-09-27 | 2021-08-03 | Communication method and device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011032366 | 2020-09-27 | ||
CN202011032366.9 | 2020-09-27 | ||
CN202011231197.1 | 2020-11-06 | ||
CN202011231197.1A CN114286429B (zh) | 2020-09-27 | 2020-11-06 | 一种通信方法及设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022062685A1 true WO2022062685A1 (zh) | 2022-03-31 |
Family
ID=80844822
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/110381 WO2022062685A1 (zh) | 2020-09-27 | 2021-08-03 | 一种通信方法及设备 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20230371118A1 (zh) |
EP (1) | EP4207884A4 (zh) |
WO (1) | WO2022062685A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023197961A1 (zh) * | 2022-04-11 | 2023-10-19 | 维沃移动通信有限公司 | 信息传输方法、装置及通信设备 |
WO2024092475A1 (zh) * | 2022-10-31 | 2024-05-10 | 北京小米移动软件有限公司 | 载波监听方法、装置、存储介质及通信*** |
WO2024108433A1 (en) * | 2022-11-23 | 2024-05-30 | Qualcomm Incorporated | Connected mode discontinuous reception (c-drx) enhancement with wakeup signal for sidelink communication |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200045768A1 (en) * | 2018-07-31 | 2020-02-06 | Qualcomm Incorporated | Drx groups for carrier aggregation |
-
2021
- 2021-08-03 US US18/246,641 patent/US20230371118A1/en active Pending
- 2021-08-03 EP EP21871062.2A patent/EP4207884A4/en active Pending
- 2021-08-03 WO PCT/CN2021/110381 patent/WO2022062685A1/zh unknown
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200045768A1 (en) * | 2018-07-31 | 2020-02-06 | Qualcomm Incorporated | Drx groups for carrier aggregation |
Non-Patent Citations (4)
Title |
---|
INTEL CORPORATION: "Potential enhancements to NR DL signals and channels for unlicensed operation", 3GPP DRAFT; R1-1806542, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051441744 * |
QUALCOMM INC, SAMSUNG: "Further discussions on DRX group", 3GPP DRAFT; R2-2001482, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Elbonia; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051849782 * |
QUALCOMM INCORPORATED: "Remaining issues for PDCCH-based power saving channel design", 3GPP DRAFT; R1-2002555, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200424, 11 April 2020 (2020-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051875669 * |
See also references of EP4207884A4 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023197961A1 (zh) * | 2022-04-11 | 2023-10-19 | 维沃移动通信有限公司 | 信息传输方法、装置及通信设备 |
WO2024092475A1 (zh) * | 2022-10-31 | 2024-05-10 | 北京小米移动软件有限公司 | 载波监听方法、装置、存储介质及通信*** |
WO2024108433A1 (en) * | 2022-11-23 | 2024-05-30 | Qualcomm Incorporated | Connected mode discontinuous reception (c-drx) enhancement with wakeup signal for sidelink communication |
Also Published As
Publication number | Publication date |
---|---|
EP4207884A4 (en) | 2024-03-13 |
EP4207884A1 (en) | 2023-07-05 |
US20230371118A1 (en) | 2023-11-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111345050B (zh) | 对无线通信设备能力的临时处理 | |
WO2019192342A1 (zh) | 非连续接收的通信方法、装置、通信设备和通信*** | |
WO2022062685A1 (zh) | 一种通信方法及设备 | |
EP2443899B1 (en) | Method and system for discontinuous reception operation for long term evolution advanced carrier aggregation | |
JP7462053B2 (ja) | 不連続受信drxパラメーター構成方法及び装置 | |
WO2021204215A1 (zh) | 一种drx控制方法及装置 | |
WO2020038334A1 (zh) | 信息发送、接收方法与通信设备 | |
WO2020224552A1 (zh) | 唤醒终端设备的方法、装置、网络设备和终端设备 | |
WO2021147424A1 (zh) | 无线通信方法、终端设备和网络设备 | |
WO2021062612A1 (zh) | 通信方法及装置 | |
WO2020063896A1 (zh) | 信号处理的方法和装置 | |
WO2021082012A1 (zh) | 用于确定非连续接收持续定时器的启动状态的方法及设备 | |
CN114286429B (zh) | 一种通信方法及设备 | |
TW202021391A (zh) | 非連續傳輸的方法和設備 | |
WO2020228647A1 (zh) | 一种通信方法及设备 | |
US20220039013A1 (en) | Method and device for discontinuous reception | |
WO2021016958A1 (zh) | 省电信号的参数动态变更方法、装置、终端和介质 | |
WO2021128341A1 (zh) | 非连续接收控制方法、设备及存储介质 | |
WO2020181943A1 (zh) | 一种请求***信息的方法及设备 | |
WO2022083418A1 (zh) | 一种节能信号传输方法及装置 | |
WO2023123241A1 (zh) | 无线通信方法、终端设备和网络设备 | |
WO2024007882A1 (zh) | 一种通信方法以及通信装置 | |
WO2022206363A1 (zh) | 一种通信方法及装置 | |
CN114902748B (zh) | 辅助载波的睡眠指示方法、装置、终端及存储介质 | |
WO2022152045A1 (zh) | 信息传输方法和信息传输装置 |
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: 21871062 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2021871062 Country of ref document: EP Effective date: 20230328 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |