Systems and methods for control channel reception in power saving mode

Abstract

An access node implementation method includes: the access node transmitting a wake-up signal (WUS) before a control channel appears during an associated discontinuous reception (DRX) ON period, wherein the WUS is transmitted using a first beam; the access node transmitting the control channel during the associated DRX ON period, wherein the control channel is transmitted using a second beam in a control resource set (CORESET), wherein the first beam and the second beam share a common quasi-colocated (QCL) source.

Description

Technical Field

[0001] The present invention generally relates to a system and method for digital communication, and in a particular embodiment, to a system and method for controlling channel reception in a power-saving mode. Background Technology

[0002] One possible deployment scenario for fifth-generation (5G) new radio (NR) system architecture is to use high-frequency (HF) operating frequencies (6 GHz and higher, such as millimeter wavelengths, mmWave) to achieve greater usable bandwidth than at congested lower frequencies and to reduce interference. However, path loss is a significant issue. Beamforming can be used to overcome high path loss.

[0003] However, beams are susceptible to blocking. Therefore, the beam being used for communication may be blocked and rendered ineffective, causing the communication equipment to disconnect. Consequently, there is a need for systems and methods for control channel reception with discontinuous reception characteristics to further reduce power consumption. Summary of the Invention

[0004] In a first aspect, a method for implementing an access node is provided. The method includes: the access node transmitting a wake-up signal (WUS) before a control channel appears during an associated discontinuous reception (DRX) ON period, wherein the WUS is transmitted using a first beam; the access node transmitting the control channel during the associated DRX ON period, wherein the control channel is transmitted using a second beam in a control resource set (CORESET), wherein the first beam and the second beam share a common quasi-colocated (QCL) source.

[0005] According to the first aspect, in a first implementation of the method, the WUS is sent before the associated DRX ON period.

[0006] According to the first aspect or any of the foregoing implementations of the first aspect, in a second implementation of the method, the CORESET is one of a plurality of CORESETs associated with the DRX ON period, and wherein all CORESETs of the plurality of CORESETs share the common QCL source.

[0007] According to the first aspect or any of the aforementioned implementations of the first aspect, in a third implementation of the method, the CORESET is one of a plurality of CORESETs associated with the DRX ON period, and wherein the CORESET is a predetermined CORESET.

[0008] According to the first aspect or any of the foregoing implementations of the first aspect, in the fourth implementation of the method, the CORESET includes one of the following: the first CORESET of the associated DRX ON period, the CORESET with a specified identifier, the CORESET with the lowest identifier among the plurality of CORESETs, the CORESET with the highest identifier among the plurality of CORESETs, the CORESET most recently successfully received by the user equipment (UE), the CORESET associated with a UE-specific search space, the CORESET associated with a specified public search space, or the CORESET associated with a search space scheduled during the associated DRX ON period.

[0009] According to the first aspect or any of the foregoing implementations of the first aspect, in a fifth implementation of the method, the WUS indicates the search space in which the control channel will reside or the CORESET in which the control channel will transmit.

[0010] According to the first aspect or any of the foregoing implementations of the first aspect, in a sixth implementation of the method, the WUS indicates that the control channel will be transmitted in CORESET.

[0011] According to the first aspect or any of the aforementioned implementations of the first aspect, in the seventh implementation of the method, the access node further includes configuring a transmission configuration indication (TCI) state for each of the plurality of CORESETs.

[0012] According to the first aspect or any of the aforementioned implementations of the first aspect, in the eighth implementation of the method, the access node further includes configuring a TCI state for the WUS, wherein the TCI state of the WUS is the same as the TCI state of the CORESET.

[0013] According to the first aspect or any of the aforementioned implementations of the first aspect, in a second implementation of the method, all CORESETs of the plurality of CORESETs are configured with the same TCI state.

[0014] Secondly, a method for implementation by a UE is provided. The method includes: the UE receiving a first WUS using a first beam, wherein the first WUS is associated with a first DRX ON period, the UE receiving a first control channel during the associated first DRX ON period, wherein the first control channel is received using a second beam in a first CORESET, and wherein the first WUS and the first control channel share a common QCL source.

[0015] According to the second aspect, in a first implementation of the method, the first CORESET is one of a plurality of first CORESETs associated with the first DRX ON period, and wherein all of the plurality of first CORESETs share the common QCL source.

[0016] According to the second aspect or any of the foregoing implementations of the second aspect, in a second implementation of the method, the first CORESET is one of a plurality of first CORESETs associated with the first DRX ON period, and wherein the first CORESET is a predetermined first CORESET.

[0017] According to the second aspect or any of the foregoing implementations of the second aspect, in a third implementation of the method, the first CORESET includes one of the following: the first CORESET that appears in the associated first DRX ON period, the first CORESET with a specified identifier, the first CORESET with the lowest identifier among the plurality of first CORESETs, the first CORESET with the highest identifier among the plurality of first CORESETs, the first CORESET that the UE most recently successfully received, the first CORESET associated with a UE-specific search space, the first CORESET associated with a specified public search space, or the first CORESET associated with a search space scheduled within the associated first DRX ON period.

[0018] According to the second aspect or any of the foregoing implementations of the second aspect, in a fourth implementation of the method, the WUS indicates the search space in which the first control channel will reside or the first CORESET in which the control channel will transmit.

[0019] According to the second aspect or any of the foregoing implementations of the second aspect, in a fifth implementation of the method, the WUS instructs the control channel to be transmitted in the first CORESET.

[0020] According to the second aspect or any of the foregoing implementations of the second aspect, in a sixth implementation of the method, the UE further includes receiving the TCI state of each of the plurality of first CORESETs.

[0021] According to the second aspect or any of the foregoing implementations of the second aspect, in the seventh implementation of the method, the UE further includes receiving the TCI state of the WUS, wherein the TCI state of the WUS is the same as the TCI state of the first CORESET.

[0022] According to the second aspect or any of the foregoing implementations of the second aspect, in the eighth implementation of the method, all the first CORESETs of the plurality of first CORESETs are configured with the same TCI state.

[0023] According to the second aspect or any of the foregoing implementations of the second aspect, in a ninth implementation of the method, the method further includes: the UE receiving a second WUS using a third beam, wherein the second WUS is associated with a second DRX ON period; the UE failing to successfully receive a second control channel during the associated second DRX ON period; and the UE sending a data packet to indicate a request for a beam update procedure.

[0024] According to the second aspect or any of the foregoing implementations of the second aspect, in the tenth implementation of the method, sending the data packet includes: the UE selecting a random access preamble; the UE sending the random access preamble in the data packet.

[0025] According to the second aspect or any of the foregoing implementations of the second aspect, in the eleventh implementation of the method, sending the data packet includes: the UE sending a random access preamble allocated in the data packet to indicate a control channel failure.

[0026] According to the second aspect or any of the foregoing implementations of the second aspect, in the twelfth implementation of the method, the data packet is transmitted using the third beam.

[0027] According to the second aspect or any of the foregoing implementations of the second aspect, in the thirteenth implementation of the method, the method further includes: the UE determining that the MAC entity is in an active state during a scheduling time associated with the third DRX ON period, and based on this, the UE deactivating WUS reception during the scheduling time.

[0028] According to the second aspect or any of the foregoing implementations of the second aspect, in the fourteenth implementation of the method, the method further includes: the UE identifying that the second CORESET was not scheduled during the third DRX ON period; and the UE deactivating WUS reception in the second CORESET.

[0029] Thirdly, an access node is provided. The access node includes a non-transient memory and one or more processors, the non-transient memory including instructions, and the one or more processors communicating with the memory. The one or more processors execute the instructions to: transmit a WUS before a control channel appears during an associated DRX ON period, wherein the WUS is transmitted using a first beam; and transmit the control channel during the associated DRX ON period, wherein the control channel is transmitted in a CORESET using a second beam, wherein the first beam and the second beam share a common QCL source.

[0030] According to the third aspect, in the first implementation of the access node, the WUS is transmitted before the associated DRX ON period.

[0031] According to the third aspect or any of the foregoing implementations of the third aspect, in the second implementation of the access node, the CORESET is one of a plurality of CORESETs associated with the DRX ON period, and wherein all CORESETs of the plurality of CORESETs share the common QCL source.

[0032] According to the third aspect or any of the foregoing implementations of the third aspect, in the third implementation of the access node, the CORESET is one of a plurality of CORESETs associated with the DRX ON period, and wherein the CORESET is a predetermined CORESET.

[0033] According to the third aspect or any of the foregoing implementations of the third aspect, in the fourth implementation of the access node, the CORESET includes one of the following: the first CORESET of the associated DRX ON period, the CORESET with a specified identifier, the CORESET with the lowest identifier among the plurality of CORESETs, the CORESET with the highest identifier among the plurality of CORESETs, the CORESET most recently successfully received by the UE, the CORESET associated with a UE-specific search space, the CORESET associated with a specified public search space, or the CORESET associated with a search space scheduled during the associated DRX ON period.

[0034] According to the third aspect or any of the foregoing implementations of the third aspect, in the fifth implementation of the access node, the WUS indicates the search space in which the control channel will reside or the CORESET in which the control channel will transmit.

[0035] According to the third aspect or any of the foregoing implementations of the third aspect, in the sixth implementation of the access node, the WUS indicates that the control channel will be transmitted in CORESET.

[0036] According to the third aspect or any of the foregoing implementations of the third aspect, in the seventh implementation of the access node, the one or more processors further execute the instructions to configure the TCI state for each of the plurality of CORESETs.

[0037] According to the third aspect or any of the foregoing implementations of the third aspect, in the eighth implementation of the access node, the one or more processors further execute the instructions to configure the TCI state for the WUS, wherein the TCI state of the WUS is the same as the TCI state of the CORESET.

[0038] According to the third aspect or any of the foregoing implementations of the third aspect, in the ninth implementation of the access node, all CORESETs of the plurality of CORESETs are configured with the same TCI state.

[0039] Fourthly, a UE is provided. The UE includes a non-transient memory and one or more processors, the non-transient memory including instructions, and the one or more processors communicating with the memory. The one or more processors execute the instructions to: receive a first WUS using a first beam, wherein the first WUS is associated with a first DRX ON period; and receive a first control channel during the associated first DRX ON period, wherein the first control channel is received using a second beam in a first CORESET, wherein the first WUS and the first control channel share a common QCL source.

[0040] According to the fourth aspect, in the first implementation of the UE, the first CORESET is one of a plurality of first CORESETs associated with the first DRX ON period, and wherein all the first CORESETs in the plurality of first CORESETs share the common QCL source.

[0041] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the second implementation of the UE, the first CORESET is one of a plurality of first CORESETs associated with the first DRX ON period, and wherein the first CORESET is a predetermined first CORESET.

[0042] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the third implementation of the UE, the first CORESET includes one of the following: the first CORESET that appears in the associated first DRX ON period, the first CORESET with a specified identifier, the first CORESET with the lowest identifier among the plurality of first CORESETs, the first CORESET with the highest identifier among the plurality of first CORESETs, the first CORESET that the UE has most recently successfully received, the first CORESET associated with a UE-specific search space, the first CORESET associated with a specified public search space, or the first CORESET associated with a search space scheduled during the associated first DRX ON period.

[0043] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the fourth implementation of the UE, the WUS indicates the search space in which the first control channel will be located or the first CORESET in which the control channel will transmit.

[0044] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the fifth implementation of the UE, the WUS indicates that the control channel will be transmitted in the first CORESET.

[0045] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in a sixth implementation of the UE, the one or more processors further execute the instructions to receive the TCI state of each of the plurality of first CORESETs.

[0046] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the seventh implementation of the UE, the one or more processors further execute the instruction to receive the TCI state of the WUS, wherein the TCI state of the WUS is the same as the TCI state of the first CORESET.

[0047] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the eighth implementation of the UE, all the first CORESETs of the plurality of first CORESETs are configured with the same TCI state.

[0048] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the ninth implementation of the UE, the one or more processors further execute the instructions to receive the second WUS using the third beam, wherein the second WUS is associated with a second DRX ON period; the second control channel is not successfully received during the associated second DRX ON period; and a data packet is sent to indicate a request for a beam update procedure.

[0049] In a tenth implementation of the UE, according to the fourth aspect or any of the foregoing implementations of the fourth aspect, the one or more processors further execute the instructions to select a random access preamble and send the random access preamble in the data packet.

[0050] In an eleventh implementation of the UE, according to the fourth aspect or any of the foregoing implementations of the fourth aspect, the one or more processors further execute the instructions to send a random access preamble allocated in the data packet to indicate a control channel fault.

[0051] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the twelfth implementation of the UE, the data packet is transmitted using the third beam.

[0052] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the thirteenth implementation of the UE, the one or more processors further execute the instructions to determine that the MAC entity is in an active state during a scheduling time associated with the third DRX ON period, and based on this, deactivate WUS reception during the scheduling time.

[0053] According to the fourth aspect or any of the foregoing implementations of the fourth aspect, in the fourteenth implementation of the UE, the one or more processors further execute the instructions to identify that the second CORESET was not scheduled during the third DRX ON period and deactivate WUS reception in the second CORESET.

[0054] The advantage of the preferred embodiment is that the receiving device can maintain the same spatial quasi-co-addressable source between the wake-up signal and the control resource set during associated discontinuous reception activation periods. Maintaining the same spatial quasi-co-addressable source enables determination of whether the transmitting device has transmitted a control channel.

[0055] Another advantage of the preferred embodiment is that sending the wake-up signal and control resource set through the same quasi-co-located source increases the probability of detecting the control channel. Attached Figure Description

[0056] To gain a more complete understanding of the invention and its advantages, please refer to the following description in conjunction with the accompanying drawings.

[0057] Figure 1 An exemplary communication system is shown.

[0058] Figure 2 A communication system is illustrated, with a focus on an exemplary channel structure between the access node and the UE.

[0059] Figure 3 A wireless communication system is shown, with a focus on beam failure and beam failure recovery.

[0060] Figure 4A The diagram shows a first example of DRX operation, where only a Long DRX cycle (drx-LongCycle) is configured, and the service access node does not send PDCCH during the DRX ON duration.

[0061] Figure 4B A diagram showing a second example of DRX operation is provided, in which only a Long DRX cycle (drx-LongCycle) is configured, and the service access node sends a PDCCH during the DRX ON duration.

[0062] Figure 5 A diagram illustrating an exemplary operation of a PDCCH beam that is blocked during DRX operation is shown.

[0063] Figure 6 A diagram illustrating a first exemplary operation of QCL indication for each DRX cycle of a UE according to the exemplary embodiments presented herein.

[0064] Figure 7 A diagram illustrating a second exemplary operation of QCL indication for each DRX cycle of a UE, according to an exemplary embodiment presented herein.

[0065] Figure 8 A diagram illustrating exemplary operation of the CORESET indication in WUS for each DRX cycle of a UE, according to the exemplary embodiments presented herein.

[0066] Figure 9A A flowchart of a first DRX operation occurring in an access node according to an exemplary embodiment described herein is shown.

[0067] Figure 9B A flowchart of a second DRX operation occurring in a UE according to an exemplary embodiment described herein is shown.

[0068] Figure 10 A flowchart of a third DRX operation occurring in an access node according to an exemplary embodiment described herein is shown.

[0069] Figure 11An exemplary communication system according to the exemplary embodiments presented herein is shown.

[0070] Figure 12A and Figure 12B An exemplary device is shown that can implement the methods and teachings according to the present invention.

[0071] Figure 13 A block diagram of a computing system that can be used to implement the devices and methods disclosed herein is shown.

[0072] Figure 14 A diagram of a network for transmitting data is shown according to an exemplary embodiment presented herein.

[0073] Figure 15 A block diagram of another exemplary processing system 1500 for performing the methods described herein is shown.

[0074] Figure 16 A block diagram of a transceiver according to an exemplary embodiment presented herein is shown, the transceiver being used to send and receive instructions over a telecommunications network. Detailed Implementation

[0075] The following discusses in detail the fabrication and use of embodiments of the present invention. However, it should be understood that many applicable inventive concepts provided by the present invention can be implemented in a wide variety of specific environments. The specific embodiments discussed are merely illustrative of specific ways of making and using the embodiments and do not limit the scope of the invention.

[0076] Figure 1An exemplary communication system 100 is illustrated. The communication system 100 includes an access node 105 serving a user equipment (UE) 115. In a first operating mode, communication with the UE 115 passes through the access node 105. In a second operating mode, communication with the UE 115 does not pass through the access node 105; however, the access node 105 typically allocates resources for the UE 115 to communicate. Access nodes are also commonly referred to as Node B, evolved Node B (eNB), next generation (NG) Node B (gNB), master eNB (MeNB), secondary eNB (SeNB), master gNB (MgNB), secondary gNB (SgNB), network controller, control node, base station, access point, transmission point (TP), transmission-reception point (TRP), cell, carrier, macro cell, femtocell, picocell, etc., while UEs are also commonly referred to as mobile stations, mobile terminals, terminals, users, subscribers, stations, etc. Access nodes can provide wireless access according to one or more wireless communication protocols, such as the Third Generation Partnership Project (3GPP), Long Term Evolution (LTE), LTE Advanced (LTE-A), 5G, 5G LTE, 5G NR, High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac / ad / ax / ay, etc. While it is understood that a communication system can use multiple eNBs capable of communicating with multiple UEs, for simplicity, only one eNB and one UE are shown.

[0077] As discussed earlier, communication systems operating at high frequencies (HF) (6 GHz and higher, such as millimeter wavelengths, mmWave) experience high path loss, which can be overcome using beamforming. Figure 1As shown, both access node 105 and UE 115 use beamforming for transmission and reception. For example, access node 105 uses multiple communication beams including beams 110 and 112 for communication, while UE 115 uses multiple communication beams including beams 120 and 122 for communication.

[0078] A beam can be a set of predefined beamforming weights within a codebook-based precoding context, or a dynamically defined set of beamforming weights within a non-codebook-based precoding context (e.g., feature-based beamforming (EBB)). A beam can also be a set of predefined phase-shift preprocessors that combine signals from the antenna array in the radio frequency (RF) domain. It should be understood that a UE can rely on codebook-based precoding to transmit uplink signals and receive downlink signals, while a TRP can rely on non-codebook-based precoding to form certain radiation patterns for transmitting downlink signals or receiving uplink signals.

[0079] Figure 2 A communication system 200 is illustrated, with a focus on an exemplary channel structure between access node 205 and UE 210. In a bidirectional communication implementation, a downlink channel 220 and an uplink channel 230 exist between access node 205 and UE 210. The downlink channel 220 and uplink channel 230 may each comprise multiple unidirectional channels. Figure 2 As shown, downlink channel 220 includes a physical downlink shared channel (PDSCH) 222 and a physical downlink control channel (PDCCH) 224, while uplink channel 230 includes a physical uplink control channel (PUCCH) 232, a physical uplink shared channel (PUSCH) 234, and a physical random access channel (PRACH) 236. Other channels may exist in downlink channel 220 or uplink channel 230, but are not specified in the provided text. Figure 2 As shown in the image.

[0080] Figure 3 A wireless communication system 300 is illustrated, with a focus on beam failure and beam failure recovery. The communication system 300 includes an access node 305 serving a UE 315. (As shown...) Figure 3As shown, both access node 305 and UE 315 use beamforming for transmission and reception. For example, access node 305 uses multiple communication beams, including beams 310 and 312, for communication, while UE 315 uses multiple communication beams, including beams 320 and 322, for communication.

[0081] Initially, access node 305 and UE 315 communicate via beam pair link (BPL) 325, which includes beams 310 and 322. However, BPL 325 fails due to congestion or UE mobility. For example, UE 315 detects candidate beam 312 from access node 305 to replace the failed beam 310. UE 315 initiates beam failure recovery by sending a beam failure recovery request (BFRQ) to access node 305. After beam failure recovery is complete, BPL 330 (including beams 312 and 320) is established.

[0082] Two or more reference signals, data signals, or resources are said to have a quasicollocated (QCL) relationship, or they are QCL, when they are correlated in a way that allows them to be considered to have similar characteristics. A QCL relationship can refer to the time, frequency, code, or spatial relationship between two or more reference signals, data signals, or resources, while spatial QCL refers only to the spatial relationship between two or more reference signals, data signals, or resources. Spatial QCL information can include associations between signals and resources (e.g., between a channel status information-reference signal (CSI-RS) resource and a wideband reference signal (WBRS)), associations between individual WBRSs, or associations between a CSI-RS resource and a beamformed random access channel (BRACH). For example, in a one-to-one association, each CSI-RS signal is associated with a WBRS such that the transmit precoder of the CSI-RS signal is the same as the transmit precoder of the WBRS. For example, each CSI-RS signal may be associated with a WBRS such that the transmit precoder of the CSI-RS signal is the same as the transmit precoder of the WBRS. Similarly, a first WBRS may be associated with a second WBRS such that the transmit precoder of the second WBRS is the same as the transmit precoder of the first WBRS. Multiple CSI-RS signals can be associated with a single WBRS, or vice versa. Spatial QCL information can be stored in tabular form or in the device's memory. The spatial QCL information includes the associations between CSI-RS and WBRS. For example, the UE can use spatial QCL information to determine the CSI-RS beam index from the WBRS beam index, or vice versa. For example, in a one-to-one association, each CSI-RS signal is associated with a WBRS. Multiple CSI-RS signals can be associated with a single WBRS, or vice versa.

[0083] It should be noted that, as used in the discussion presented herein, the term QCL can generally refer to both QCL and spatial QCL. In cases where such usage would cause confusion, spatial QCL will be used as appropriate.

[0084] At the 3GPP RAN1AdHoc NR #3 meeting, a mechanism for sharing QCL information in the downlink physical channel was discussed. Several agreements were reached at the meeting, including:

[0085] - At least for the purpose of sharing QCL information, the UE is configured using radio resource control (RRC) messages, which have a list of up to M candidate transmission configuration indication (TCI) states;

[0086] Whether -M is equal to or greater than 2N needs further investigation, where N is the size of the downlink control information (DCI) field of PDSCH;

[0087] - Each TCI state can be configured with at least one set of reference signals (RS);

[0088] - At least for the purpose of the spatial QCL in the RS set, each identifier (ID) for the downlink RS and the details of the ID for further study may refer to one of the following downlink RS types: synchronization signal block (SSB), periodic channel state information reference signal (CSI-RS), aperiodic CSI-RS, or semi-static CSI-RS.

[0089] - In the RS set, other RSs, such as the tracking reference signal (TRS) and the phase-tracking reference signal (PTRS), depend on the discussion results of the QCL agenda items;

[0090] The mechanism for initializing or updating one or more downlink RS IDs in the RS set for (at least) spatial QCL purposes requires further investigation;

[0091] - At least the following two mechanisms need further research: (1) Explicitly indicating the downlink RS ID and the corresponding TCI state to the UE; (2) Implicitly associating the downlink RS ID with the TCI state based on UE measurements;

[0092] - The mechanisms used by different RS types require further research;

[0093] Whether the TCI status includes other parameters (e.g., for PDSCH rate matching) requires further investigation.

[0094] The possible values ​​of -N (N can be at most 3 bits) require further investigation.

[0095] Further details regarding the specifications for multiple demodulation reference signal (DMRS) port groups and multiple RS sets per TCI are pending.

[0096] The following were also agreed upon at the 3GPP RAN1 AdHoc NR #3 meeting:

[0097] - The QCL configuration of the PDCCH includes information that provides a reference to the TCI state.

[0098] - Alternative 1: QCL configuration or its representation is based on each CORESET, and the UE applies QCL assumptions to the associated CORESET monitoring timing. All search spaces within a CORESET use the same QCL;

[0099] - Alternative 2: QCL configuration or its representation is based on each search space, and the UE applies QCL assumptions to the associated search spaces. This potentially means that, in the case of multiple search spaces with a CORESET, the UE can configure different QCL assumptions for different search spaces.

[0100] QCL configuration is shared between RRC or the medium access control (MAC) control element (CE). Shared QCL configuration between DCI and MAC requires further investigation. The above assumptions serve as input for the discussion of the control channel.

[0101] It was also agreed that:

[0102] - Shared PDSCH QCL configuration:

[0103] - When using the TCI state-sharing QCL configuration, the UE receives an N-bit TCI field in the DCI.

[0104] - The UE assumes that the downlink RS in the set of RSs corresponding to the PDSCH DMRS and the indicated TCI state is QCL. For further investigation, it is necessary to determine whether the QCL type is configured and the configuration details.

[0105] Whether the TCI field always exists in a given downlink-related DCI requires further investigation.

[0106] Whether the -TCI field is in the same DCI as the field that includes PDSCH scheduling allocation needs further investigation;

[0107] - For further investigation, timing is performed between the time when the UE receives the QCL configuration or its representation and the first time when the QCL is assumed to be available for demodulation of PDSCH or PDCCH.

[0108] At the 3GPP RAN1 #90bis meeting, a downlink physical channel QCL configuration sharing mechanism was discussed, and the following agreement was reached:

[0109] - At least the initialization or update of the identifier of the downlink RS in the RS set of the space QCL is performed by explicit indication. Explicit indication using RRC or RRC + MAC CE is supported.

[0110] - Implicit updates based on the implicit association between downlink RS ID and TCI state through UE measurements require further research.

[0111] The following was also agreed upon at the 3GPP RAN1 #90bis meeting:

[0112] - With at least the configured or transport space QCL, support higher-layer UE-specific configurations for the presence or absence of the TCI field in the downlink-related DCI.

[0113] - If the TCI field is not present, dynamic transmission of the PDSCH QCL parameters is not provided in the downlink related DCI. For PDSCH, except in the case of beam management without beam-related information, the UE uses a higher-layer indication or its representation of the QCL parameters to determine the QCL parameters (details to be further investigated), where the higher-layer indication is not used to configure the spatial QCL parameters.

[0114] -If the TCI field exists

[0115] - The associated DCI always contains the TCI field, which is used for PDSCH scheduling, whether it is simultaneous time-slot scheduling or cross-time-slot scheduling.

[0116] - If the scheduling offset is less than the threshold K, the PDSCH uses pre-configured, predefined, or rule-based spatial assumptions (details require further investigation). Furthermore, for further investigation, other QCL parameters are still obtained from the DCI's N-bit TCI state field, and how to update the pre-configured or predefined spatial assumptions (if applicable). The threshold K can be based on UE capabilities only when multiple candidate values ​​of K are supported.

[0117] - If the scheduling offset is greater than or equal to the threshold K, the PDSCH uses the beam (spatial QCL parameter) transmitted by the N-bit TCI field in the assigned DCI.

[0118] The proposed candidate solutions should consider downlink beam-related operations (with and without beam information) or downlink beam management (with and without beam information) below or above 6 GHz.

[0119] However, this does not apply to beam management scenarios without beam-related information.

[0120] In the 3GPP fifth-generation (5G) NR standardization activities, discontinuous reception (DRX) operation mode was proposed to reduce power consumption on the UE side. DRX operation mode is sometimes also called connected mode discontinuous reception (C-DRX) operation mode. In DRX operation mode, the UE periodically wakes up and receives PDCCH during the DRX ON period; if the UE does not indicate any further action during the DRX ON period, the UE enters sleep mode during the DRX OFF period.

[0121] DRX's basic MAC layer operations use the following parameters:

[0122] drx-onDurationTimer Duration at the start of a DRX cycle; drx-SlotOffset : drx- onDurationTimer Delay before startup; drx-InactivityTimer : PDCCH indicates the duration following the PDCCH timing of a new UL or DL ​​transmission by a MAC entity; drx-RetransmissionTimerDL (For each DLHARQ process other than the broadcast process): the maximum duration before receiving a DL retransmission; drx-RetransmissionTimerUL (Per UL HARQ process): Maximum time before receiving UL retransmission authorization; drx-LongCycleStartOffset Long DRX cycle and drx-StartOffset It defines the starting subframe of the long Short DRX period. drx-ShortCycle (Optional): ShortDRX cycle; drx-ShortCycleTimer (Optional): The UE should follow the duration of the Short DRX cycle; drx-HARQ-RTT- TimerDL (For each DL HARQ process other than the broadcast process): the minimum time before the MAC entity expects the DL allocation for HARQ retransmission; drx-HARQ-RTT-TimerUL (Per UL HARQ process): The minimum time that the MAC entity expects before UL HARQ retransmission authorization.

[0123] When a DRX cycle is configured, the activation period includes the following times:

[0124] drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer Run; or

[0125] The scheduling request is sent on the PUCCH and is in a pending state; or

[0126] If, after successfully receiving the random access response of the random access preamble, no new transmission time is received as indicated by the PDCCH addressed by the cell-radio network temporary identifier (C-RNTI) of the MAC entity, the random access preamble is not selected by the MAC entity in a contention-based random access preamble.

[0127] DRX's basic MAC layer operations include:

[0128] 1> If a MAC protocol data unit (PDU) is received in the configured downlink allocation:

[0129] 2> Start the corresponding HARQ process on the first symbol after the end of the transmission carrying the DL HARQ feedback. drx-HARQ-RTT-TimerDL ;

[0130] 2> Stop the corresponding HARQ process drx-RetransmissionTimerDL .

[0131] 1> If the MAC PDU is sent in the configured uplink grant:

[0132] 2> Start the corresponding Hybrid Automatic Repeat Request (HARQ) process on the first symbol after the first retransmission of the corresponding PUSCH transmission. drx-HARQ-RTT-TimerUL ;

[0133] 2> Stop the corresponding HARQ process drx-RetransmissionTimerUL .

[0134] 1> If drx-HARQ-RTT-TimerDL time out:

[0135] 2> If the data in the corresponding HARQ process is not successfully decoded:

[0136] 3> In drx-HARQ-RTT-TimerDL The corresponding HARQ process is started on the first symbol after the timeout. drx-RetransmissionTimerDL .

[0137] 1> If drx-HARQ-RTT-TimerUL time out:

[0138] 2> In drx-HARQ-RTT-TimerUL The corresponding HARQ process is started on the first symbol after the timeout. drx-RetransmissionTimerUL .

[0139] 1> If you receive a DRX Command MAC CE or a Long DRX Command MAC CE:

[0140] 2>Stop drx-onDurationTimer ;

[0141] 2>Stop drx-InactivityTimer .

[0142] 1> If drx-InactivityTimer Timeout or DRX Command MAC CE received:

[0143] 2> If Short DRX cycle is configured:

[0144] 3> In drx-InactivityTimer Boot or reboot on the first symbol after the timeout, or on the first symbol after the DRX Command MAC CE receive ends. drx-ShortCycleTimer ;

[0145] 3> Use Short DRX cycle.

[0146] 2> Otherwise:

[0147] 3> Use Long DRX cycles.

[0148] 1> If drx-ShortCycleTimer time out:

[0149] 2> Use Long DRX cycles.

[0150] 1> If a Long DRX Command MAC CE is received:

[0151] 2>Stop drx-ShortCycleTimer ;

[0152] 2> Use Long DRX cycles.

[0153] 1> If using a Short DRX cycle, and [(SFN × 10) + subframe number] modulo( drx-ShortCycle ) = ( drx-StartOffset modulo ( drx-ShortCycle );or

[0154] 1> If using a Long DRX cycle, and [(SFN × 10) + subframe number] modulo ( drx- LongCycle ) = drx-StartOffset :

[0155] 2> Starting from the subframe, in drx-SlotOffset Start after drx-onDurationTimer .

[0156] 1> If the MAC entity is in the active period:

[0157] 2> Monitor PDCCH;

[0158] 2> If the PDCCH indicates a DL transfer:

[0159] 3> Start the corresponding HARQ process on the first symbol after the end of the transmission carrying the DL HARQ feedback. drx-HARQ-RTT-TimerDL ;

[0160] 3> Stop the corresponding HARQ process drx-RetransmissionTimerDL .

[0161] 2> If the PDCCH indicates UL transmission:

[0162] 3> Start the corresponding HARQ process on the first symbol after the first retransmission of the corresponding PUSCH transmission. drx-HARQ-RTT-TimerUL ;

[0163] 3> Stop the corresponding HARQ process drx-RetransmissionTimerUL .

[0164] 2> If the PDCCH indicates a new transmission (DL or UL):

[0165] 3> Start or restart on the first symbol after the PDCCH reception ends. drx-InactivityTimer .

[0166] 1> In the current symbol n, when evaluating all DRX activation conditions as specified, considering the grant / assignment / DRX Command MAC CE / Long DRX Command MAC CE received and the scheduling request sent 4ms before symbol n, if the MAC entity is not in the activation period, then,

[0167] 2> Do not send periodic SRS and semi-static SRS as defined in TS 38.214, which are incorporated herein by reference.

[0168] 1> If a higher layer has CSI masking configured:

[0169] 2> In the current symbol n, when evaluating all DRX activation period conditions as specified, taking into account the grant / assignment / DRX Command MAC CE / Long DRX Command MAC CE received 4ms prior to symbol n, if onDurationTimer If it does not run, then:

[0170] 3> Do not report CSI on PUCCH.

[0171] 1> Otherwise:

[0172] 2> In the current symbol n, when evaluating all DRX activation conditions as specified, taking into account the grant / assignment / DRX Command MAC CE / Long DRX Command MAC CE received 4ms before symbol n and the scheduling requests sent, if the MAC entity is not in the activation period, then:

[0173] 3> Do not report CSI on PUCCH and semi-static CSI on PUSCH.

[0174] Figure 4A Figure 400 illustrates a first example of DRX operation, where only a Long DRX cycle (drx-LongCycle) is configured, and the serving access node does not transmit the PDCCH during the DRX ON duration. The UE switches between DRX ON and DRX OFF states based on the access node configuration. When the UE is in the DRX ON state, it monitors the radio channel for frame exchange. However, when the UE is in the DRX OFF state, based on the assumption that the serving access node will not initiate data transmission during the DRX OFF state, the UE does not need to monitor the radio channel. For each Long DRX cycle T1 414 and 416, the UE monitors the PDCCH during T0 410 and 412 until the timer expires. drx-onDurationTimer Timeout. After T0 410 and 412, when... drx- onDurationTimer Upon timeout, the UE re-enters the DRX OFF state and ceases monitoring the radio channel. Therefore, during LongDRX cycles T1 414 and 416, the UE only monitors the radio channel during T0 410 and 412, which reduces UE power consumption.

[0175] Figure 4B Figure 450 shows a second example of DRX operation, where only Long DRX cycles are configured ( drx- LongCycleThe serving access node sends the PDCCH during the DRX ON duration. For each Long DRX cycle T1484 and 486, the UE monitors the PDCCH during T0 480 and 482 until... drx-onDurationTimer Timeout. If in drx- onDurationTimer If PDCCH 490 is detected before the timeout, the UE will continue to monitor the radio channel during T2 488 until another timer times out. drx-InactivityTimer ), to check for any subsequent DL transfers. When drx- InactivityTimer If the timeout occurs and no further data exchange occurs, the UE will re-enter the DRX OFF state and will no longer monitor the radio channel.

[0176] The discussion of the exemplary embodiments presented herein focuses on the Long DRX cycle case of DRX operation. Typically, there are at least two DRX operation cases, including Long DRX cycles (as described herein) and Short DRX cycles. The exemplary embodiments presented herein can operate with Long DRX cycles, Short DRX cycles, or both. Therefore, the focus on Long DRX cycle operation should not be construed as limiting the scope or spirit of the exemplary embodiments.

[0177] By using DRX operating mode, the UE can avoid continuous monitoring of the PDCCH, thereby reducing power consumption. However, in 5G NR operating scenarios, especially when high-frequency bands (e.g., above 6 GHz) are used for 5G NR communication, the radio channel or beam may be blocked for various reasons when the UE is not monitoring the PDCCH (i.e., when the UE is sleeping during the DRX OFF period). For example, if the UE moves or changes its direction while not monitoring the PDCCH, or if an object enters between the UE and the access node, the transmit or receive beam may not be maintained because the radio channel has changed.

[0178] Figure 5 Figure 500 illustrates an exemplary operation of a PDCCH beam that is blocked during DRX operation. Figure 5 In the exemplary operation shown, the UE is only configured with a Long DRX period ( drx-LongCycle The UE monitors the PDCCH during the DRX ON period. For each DRX cycle T1 518, 520, and 522, the UE monitors the PDCCH during T0 510, 512, and 514 (T0 516 appears in subsequent DRX cycles), until... drx-onDurationTimerTimeout. In this example, when the UE is in DRX OFF state, at time T2 530, the current beam used for PDCCH reception is blocked, where the UE is in sleep state and does not recognize that the current beam used for PDCCH reception has been blocked.

[0179] Because the UE did not recognize that its current beam used for PDCCH reception was blocked, it continued to use the current beam to monitor PDCCH during the upcoming DRX ON periods of T0512, 514, and 516. In this example, the serving access node transmits a series of PDCCHs at T3540, T4542, and T5544 within the duration of T0512-516. However, because the UE's current beam used for PDCCH reception was blocked before the PDCCH was transmitted from the serving access node, but the UE continued to use the current beam for PDCCH monitoring during the T0512-516 period, the UE is likely unable to successfully decode the PDCCHs transmitted by the serving access node at T3540, T4542, and T5544.

[0180] Since the UE failed to decode its PDCCH during T0 512-516, the UE returned to the DRX OFF state and stopped monitoring the PDCCH. In this case, due to the blocking instance of the beam currently used for PDCCH reception, the UE did not receive any PDCCH during the DRX operation.

[0181] When the UE does not correctly receive any PDCCH during the DRX ON period, in order to prevent Figure 5 As shown in the diagram, the UE needs to know whether the access node sent a PDCCH during the DRX ON period. If the access node sent a PDCCH but the UE did not receive it correctly, it means the UE needs to update its current serving beam to receive the PDCCH. However, if the access node did not send a PDCCH, and therefore the UE did not receive the PDCCH (because the PDCCH does not exist), the UE only needs to enter a sleep state until the next scheduled DRX ON period.

[0182] Therefore, to expedite the synchronization process when the UE wakes up before the start of the DRX ON period, the concept of a wake-up signal (WUS) can be considered. Sending the WUS before the start of the DRX ON period further reduces power consumption. Furthermore, the WUS can be sent within the DRX ON period as long as it is sent before the transmission of the PDCCH associated with it. Such a DRX ON period is referred to as associated with a specific WUS. The DRX ON period can also be called the expected DRX ON period for a specific WUS. Since the WUS is sent within a predetermined time window, it can help the UE achieve rapid synchronization for PDCCH reception before the start of the associated DRX ON period or before the transmission of the PDCCH associated with that WUS. The WUS can further indicate whether PDCCH transmission is expected during the associated DRX ON period. Additionally, based on the signal quality of the received WUS, the UE can identify whether the current serving beam for PDCCH reception is in good condition.

[0183] When a UE does not correctly receive any PDCCH during a DRX ON period, the UE can identify whether the access node is sending PDCCH during the DRX ON period by estimating the signal quality of the WUS sent before the start of the DRX ON period (or during the DRX ON period). That is, if the WUS signal quality is good, but the UE does not correctly receive the PDCCH, it means the access node is not sending the PDCCH. However, if the WUS signal quality is poor, and the UE does not correctly receive the PDCCH, it means the UE needs to update the current serving beam of the PDCCH. Therefore, the WUS and PDCCH need to use the same beam, or the WUS and PDCCH need to be QCL-compliant, or the WUS and PDCCH need to have the same QCL source.

[0184] Some reference signals, such as CSI-RS, synchronization signals (SS), physical broadcast channels (PBCH), or simply SS blocks (SSB), can be used as WUS. Other reference signals can also be used as WUS. It should also be noted that different terms can be used to refer to WUS, which may include, but are not limited to, power save / saving channels, power save / saving signals, power save / saving reference signals, etc.

[0185] For UE PDCCH reception, one or more search spaces and associated control resource sets (CORESETs) can be configured for the UE. Furthermore, different CORESETs can be configured with different TCI states for QCL sources. Then, if the UE has configured multiple CORESETs with different TCI states, there is a problem with WUS configuring QCL sources. For example, since each CORESET can have its own period, different CORESETs with different QCL sources can be scheduled in different DRX ON periods. Furthermore, multiple CORESETs with different QCL sources can be scheduled during a single DRX ON period. Then, if the QCL source of the WUS is explicitly configured, for example via RRC or MAC CE indication, since different CORESETs with different QCL sources can be scheduled in different DRX ON periods, and the WUS should appear at or before the start of each DRX ON period or before the PDCCH transmission timing, the QCL source cannot be explicitly configured using RRC or MAC CE indication unless the access node adjusts the QCL source for each DRX ON period.

[0186] According to an exemplary embodiment, the spatial QCL source of the WUS is the same as the spatial QCL source of at least one CORESET scheduled during the associated (or desired) DRX ON period. The common spatial QCL source of the WUS and the at least one CORESET scheduled during the associated DRX ON period make it easier for the UE to determine whether the access node should transmit the PDCCH. Furthermore, the common spatial QCL source increases the probability of detecting the PDCCH. The requirement for a common spatial QCL source does not necessitate using the same beam for transmitting the WUS and at least one CORESET. Instead, different beams can be used, provided that the beam used has a common spatial QCL source.

[0187] In order for the UE to estimate which coreset was scheduled during the associated DRX ON period, the UE needs to know the start and end times of the associated DRX ON period. However, since the actual DRX ON period varies depending on the presence (if any) of PDCCH and any accompanying PDSCH reception, and since the UE does not know whether a PDCCH will be received during the DRX ON period prior to the start of the DRX ON period, the UE cannot accurately estimate which coreset was scheduled during the associated DRX ON period. Therefore, a desired DRX ON period can be used instead. For example, a desired DRX ON period starts from a DRX ON period and lasts for a predetermined duration. One example of a predetermined duration is the value of the configured drx-onDurationTimer. Another example of a predetermined duration is the DRX ON duration during which no PDCCH is received during the DRX ON period.

[0188] According to an exemplary embodiment, all CORESETs scheduled during the associated (desired) DRX ON period have the same QCL source, and the QCL source of the WUS is the same as the QCL source of the CORESET during the associated (desired) DRX ON period. For this purpose, the access node and the UE may have explicit or implicit indications of the QCL source. In one embodiment, when configuring DRX operation for the UE, the QCL source of the CORESET configured by the access node for the UE is the same for all CORESETs configured for the UE. Alternatively, when configuring DRX operation for the UE, the access node indicates the same TCI state value for all CORESETs configured for the UE. In another embodiment, when configuring DRX operation for the UE, regardless of the TCI state value configured for each CORESET, the QCL source of the CORESET is changed to a predetermined value such that the QCL source of all CORESETs is the same. The selection of the predetermined value can vary. Some examples (but not limited to these examples) are shown below:

[0189] - The first CORESET QCL source to arrive during the DRX ON period

[0190] - QCL sources for CORESET with a specific ID (such as the lowest ID),

[0191] - The QCL source of the CORESET that the UE most recently successfully received.

[0192] - The QCL source of CORESET associated with the UE-specific search space.

[0193] - QCL sources of CORESET associated with a specific public search space (e.g., the Type0-PDCCH public search space).

[0194] -SSB or CSI-RS resources associated with PRACH resources,

[0195] - If only one search space is scheduled during the associated DRX ON period, then the CORESET is associated with the only search space scheduled during the associated DRX ON period, or

[0196] -The combination mentioned above.

[0197] Figure 6 Figure 600 illustrates a first exemplary operation of QCL indication for each DRX cycle of a UE. In this example, for the associated (desired) DRX ON period 601 in DRX cycle 602, three different CORESETs are expected at three different times: T0 610, T1 612, and T2 614. Furthermore, at a predetermined time before the start of DRX ON period 601 or at some time before the PDCCH transmission timing (e.g., within the CORESETs of times T0 610, T1 612, and T2 614), WUS 616 is sent by the access node. In this example, the QCL source for WUS 616, the CORESET in T0 610, the CORESET in T1 612, and the CORESET in T2 614 is the same. Or, similarly, the QCLs for WUS 616, the CORESET in T0 610, the CORESET in T1 612, and the CORESET in T2 614 are all QCLed together. Alternatively, the beam (or beam pair link (BPL) or QCL source) 630 used for WUS 616, the beam (or BPL or QCL source) 632 used for CORESET in T0 610, the beam (or BPL or QCL source) 634 used for CORESET in T1 612, and the beam (or BPL or QCL source) 636 used for CORESET in T2 614 are the same. Therefore, if the UE correctly receives WUS 616, assuming no significant changes in conditions, the UE can correctly receive the PDCCH during T0 610, T1 612, and T2 614.

[0198] According to an exemplary embodiment, the access node transmits a WUS sometime before the associated (desired) DRX ON period of the UE or before the PDCCH transmission timing, and during the associated (desired) DRX ON period. The access node also transmits a PDCCH in one or more CORESETs, which have the same QCL source as the associated WUS. Furthermore, it is not expected that the UE will monitor CORESETs with different QCL sources than the associated WUS. The access node may explicitly indicate the QCL source of the WUS. Additionally, during the associated (desired) DRX ON period, the QCL source of the WUS may be the same as the QCL source of a predetermined CORESET. The selection of a predetermined CORESET can vary. Some examples of predetermined CORESETs (but not limited to these examples) are shown below:

[0199] - The first CORESET to enter the DRX ON period

[0200] -CORESET has a specific ID (such as the lowest ID).

[0201] - The CORESET that the UE recently successfully received

[0202] - CORESET associated with the UE-specific search space,

[0203] - CORESET associated with a specific public search space (e.g., the Type0-PDCCH public search space),

[0204] - If only one search space is scheduled during the associated DRX ON period, then the CORESET is the one associated with the only search space scheduled during the associated DRX ON period, or

[0205] -The combination mentioned above.

[0206] In one embodiment, the access node does not send PDCCH in a CORESET different from the predetermined CORESET during the associated DRX ON period.

[0207] Figure 7Figure 700 illustrates a second exemplary operation of QCL indication for each DRX cycle of a UE. In this example, for the associated (desired) DRX ON period 701 within DRX cycle 702, three different CORESETs are expected at three different times: T0 710, T1 712, and T2 714. At a predetermined time before the start of DRX ON period 701 or some time before the PDCCH transmission timing, the access node sends WUS 716. In this example, the QCL source 730 of WUS 716 is the same as the QCL source 732 of the CORESET in T0 710, but the QCL sources 734 of the CORESET in T1 712 and 736 of the CORESET in T2 714 are both different from the QCL source 730 of WUS 716. Therefore, it is only expected that the UE will monitor PDCCH reception during T0 710, since its QCL source 732 is the same as the QCL source 730 of WUS 716, and it is not expected that the UE will monitor PDCCH reception during T1 712 and T2 714. Figure 7 The QCL sources 734 and 736 are marked with an X to indicate that the UE does not monitor the PDCCH during these time periods. Therefore, if the UE correctly receives WUS 716, assuming no significant changes in the conditions, the UE can correctly receive the PDCCH during T0 710.

[0208] According to one exemplary embodiment, the WUS indicates whether it is expected that the access node will perform PDCCH transmission in a specific core set within the associated (expected) DRX ON period. When the UE receives the WUS at a time before the start of the associated (expected) DRX ON period or before the PDCCH transmission timing, the UE can identify the core set for which it needs to monitor PDCCH reception during the (expected) DRX ON period, and the core set for which it can skip monitoring PDCCH reception during the (expected) DRX ON period. In one example, the WUS may indicate or include an information bitmap, wherein each bit of the information bitmap corresponds to a core set in a predetermined order of core sets, and the setting of each bit of the information bitmap indicates to the UE whether it is expected that the access node will perform PDCCH transmission in the corresponding core set. In another example, the WUS consists of one or more sequences, and different sequences are used to indicate whether it is expected that the access node will perform PDCCH transmission in the corresponding core set (i.e., the core set corresponding to the sequence sent as the WUS). In another example, WUS is a DCI transmitted in PDCCH, the content of which includes an indicator indicating whether access nodes are expected to transmit PDCCH in a specific CORESET during the associated (desired) DRX ON period.

[0209] Figure 8 Figure 800 illustrates an exemplary operation of the CORESET indication in the WUS for each DRX cycle of the UE. In this example, for the associated (desired) DRX ON period 801 in DRX cycle 802, three different CORESETs are expected at three different times: T0 810, T1 812, and T2 814. At a predetermined time before the start of DRX ON period 801 or some time before the PDCCH transmission opportunity, the access node sends WUS 816. In this example, WUS 816 indicates that the access node is expected to perform PDCCH transmission in the CORESET in T0 810 and the CORESET in T1 812. Then, since the UE knows the QCL source of the CORESET in T0 810 and the QCL source of the CORESET in T1 812, the UE can monitor the PDCCH during T0 810 and T1 812. If the UE does not receive any PDCCH during T0 810 or T1 812, since the access node has indicated that there is PDCCH transmission during these time periods (by WUS 716), this means that the current beam associated with the CORESET for which the UE did not receive PDCCH correctly needs to be updated.

[0210] According to an exemplary embodiment, WUS indicates that during the associated (desired) DRX ON period (desired to be non-zero) drx-onDurationTimer The search space or CORESET for which access nodes are expected to perform PDCCH transmissions during the specified duration. For example, if two search spaces or CORESETs (referred to as C#0 and C#1 in this document) are scheduled during the associated DRX ON period, WUS may include the following information (but is not limited to these examples):

[0211] - PDCCH is not expected in C#0 and C#1

[0212] -Expected PDCCH in C#0

[0213] -Expected PDCCH in C#1

[0214] - Expected PDCCH in C#0 and C#1.

[0215] According to one exemplary embodiment, the WUS indicates whether PDCCH transmission is expected during the associated (expected) DRX ON period. If the UE correctly receives the WUS, and the WUS indicates that PDCCH transmission is expected during the associated (expected) DRX ON period, but the UE does not receive any PDCCH during the associated (expected) DRX ON period, the UE sends an indication to the access node that the UE needs to update the current beam (or beam-to-link). In one embodiment, this indication is made when the QCL source of the WUS is different from the QCL source of the CORESET scheduled during the associated (expected) DRX ON period. In one example, the indication that the UE needs to update the current beam initiates a beam refinement procedure between the UE and the access node. In another example, the indication that the UE needs to update the current beam initiates a beam failure recovery procedure. In yet another example, the SSB or CSI-RS is associated with PRACH resources, and if the UE receives a WUS indicating that PDCCH is scheduled during the (expected) DRX ON period, but the UE does not correctly receive any PDCCH, the UE may send PRACH resources. In other words, if the UE fails to receive any PDCCH correctly, the UE can transmit a resource. The PRACH resource can indicate to the UE that it needs to update the current beam. In yet another example, the WUS is associated with an SSB or CSI-RS, which is also associated with a PRACH resource; the PRACH resource itself can indicate to the UE that it needs to update the current beam. In such an example, if the UE does not receive any PDCCH correctly, the transmission of the PRACH resource serves as an indicator that the UE needs to update the current beam.

[0216] When transmitting PRACH resources, the UE sends a request to perform a beam update procedure. In one example, sending the request to perform a beam update procedure involves the UE selecting a random access preamble from multiple random access preambles and transmitting the selected random access preamble in the random access resource. In another example, sending the request to perform a beam update procedure involves the UE transmitting an assigned random access preamble in the random access resource, wherein the assigned random access preamble is assigned to indicate a control channel (e.g., PDCCH) failure. In one embodiment, the request to perform a beam update procedure is sent in a beam different from the beam associated with the WUS, although these beams may have a common QCL source.

[0217] According to an exemplary embodiment, if no search space or coreset is scheduled during the associated (desired) DRX ON period of the UE, the access node will not transmit WUS at some time before the start of the associated (desired) DRX ON period or before the PDCCH transmission timing. Therefore, if no search space or coreset is scheduled during the associated (desired) DRX ON period, the UE is not expected to receive WUS at some time before the start of the (desired) DRX ON period or before the PDCCH transmission timing. The UE can determine the absence of a search space or coreset by checking the scheduling of coresets and determining (e.g., identifying) that no search space or coreset is scheduled during the associated (desired) DRX ON period. When the UE is not expected to receive WUS, the UE can deactivate WUS reception, which may include stopping WUS monitoring, stopping blind detection of WUS, stopping WUS decoding, etc. In one embodiment, in this case, the access node may transmit other signals during the expected transmission time of WUS. In another embodiment, if no search space or CORESET is scheduled during the associated (desired) DRX ON period, the UE remains in sleep mode and does not monitor PDCCH reception during the associated DRX period. The drx-onDurationTimer is duration-dependent and can be used in a manner equivalent to the DRX ON period.

[0218] According to an exemplary embodiment, if the UE is already active during the expected transmission time of its WUS, the access node will not transmit WUS sometime before the start of the associated (expected) DRX ON period or before the PDCCH transmission timing. Therefore, if the UE's MAC entity is active during the expected transmission time of its WUS, it is not expected that the UE will receive WUS before the start of the associated (expected) DRX ON period. When the UE is not expected to receive WUS, it can deactivate WUS reception, which may include stopping WUS monitoring, stopping blind WUS detection, stopping WUS decoding, etc.

[0219] Figure 9AA flowchart 900 illustrating a first DRX operation occurring in an access node according to an exemplary embodiment described herein is shown. In this example, the access node configures one or more CORESETs for the UE to use during the DRX operation and sets the TCI state of all CORESETs in the one or more CORESETs to a first value (box 905). Typically, the access node can configure one or more CORESETs for the UE, and if the UE is operating in DRX mode, one or more CORESETs may occur during the DRX ON period. In other words, one or more CORESETs configured for the UE may be configured individually or not individually for use during the DRX operation. The access node also configures the DRX operation for the UE (box 907). For the DRX operation, the access node configures WUS transmission sometime before the start of the associated (desired) DRX ON period or before the PDCCH transmission timing, and the access node configures the TCI state of the WUS to a first value (box 909). Then, since the UE is operating in DRX mode, the access node uses a first beam to transmit the WUS at the expected transmission time before the associated (desired) DRX ON period (or some time before the PDCCH transmission timing), where the first beam corresponds to the first TCI state value (box 911). During the associated (desired) DRX ON period, the access node uses the first beam to transmit the PDCCH in the CORESET (box 913). Therefore, if the UE successfully receives the WUS, the UE is able to correctly receive the PDCCH using the correct beam.

[0220] Figure 9BA flowchart 950 illustrates a second DRX operation occurring in a UE according to an exemplary embodiment described herein. In this example, for the UE, the QCL source of the WUS is used to apply a first reference signal (RS) using a first beam for DRX operation (box 955). Furthermore, for the UE, the QCL source of the CORESET is used to apply a second RS using a second beam (box 957). Under this configuration, when DRX operation is configured for the UE, the UE receives the WUS at some point before the start of the DRX ON period or before the PDCCH transmission timing (box 959). Then, if the CORESET is scheduled during the associated (desired) DRX ON period (box 961), the UE checks whether the first beam and the second beam are the same (box 963). If the first beam and the second beam are the same, or in other words, if the first RS and the second RS are the same, or if the QCL source is the same (box 963), the UE monitors the PDCCH in the CORESET (box 965). If CORESET is not scheduled during the associated (expected) DRX ON period (box 961), or if the first beam and the second beam are not the same (box 963), then the UE does not monitor CORESET (box 967).

[0221] Figure 10 A flowchart 1000 illustrating a third DRX operation occurring in an access node according to an exemplary embodiment described herein is shown. In this example, the access node configures multiple CORESETs for the UE to use during DRX operation, and the TCI states of the CORESETs are set to different values ​​(box 1005). In other words, more than one of the multiple CORESETs can be assigned the same TCI state or the same set of TCI states. The access node also configures DRX operation for the UE (box 1007). For DRX operation, the access node configures WUS transmission before the start of the associated (desired) DRX ON period, and the access node configures the TCI state of the WUS to a value associated with a predetermined CORESET for the associated (desired) DRX ON period (box 1009). Then, since the UE is operating in DRX mode, the access node transmits the WUS using a first beam at the desired transmission time of the WUS before the associated (desired) DRX ON period, where the first beam corresponds to the TCI state value (box 1011). During the associated (desired) DRX ON period, the access node transmits the PDCCH in the predetermined CORESET using the first beam (box 1013). Therefore, if the UE successfully receives the WUS, the UE is able to correctly receive the PDCCH using the correct beam.

[0222] Figure 11An exemplary communication system 1100 is illustrated. Typically, system 1100 enables multiple wireless or wired users to send and receive data and other content. System 1100 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0223] In this example, the communication system 1100 includes electronic devices (EDs) 1110a-1110c, radio access networks (RANs) 1120a-1120b, a core network 1130, a public switched telephone network (PSTN) 1140, the Internet 1150, and other networks 1160. Although Figure 11 A certain number of these components or elements are shown, but the system 1100 may include any number of these components or elements.

[0224] ED 1110a-1110c are used for operation or communication within system 1100. For example, ED 1110a-1110c are used for transmitting or receiving via wireless or wired communication channels. Each ED 1110a-1110c represents any suitable user-end equipment and may include (or be referred to as) devices such as: user equipment (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, personal digital assistant (PDA), smartphone, laptop computer, computer, touchpad, wireless sensor, or consumer electronics device.

[0225] RAN 1120a-1120b here includes base stations 1170a-1170b. Each base station 1170a-1170b is used to connect wirelessly with one or more of ED 1110a-1110c to enable access to the core network 1130, PSTN 1140, Internet 1150, or other networks 1160. For example, base stations 1170a-1170b may include (or may be) one or more of several known devices, such as base transceiver stations (BTS), Node-B (NodeB), evolved NodeB (eNodeB), next-generation (NG) NodeB (gNB), home NodeB, home eNodeB, site controller, access point (AP), or wireless router. ED 1110a-1110c is used to connect and communicate with Internet 1150 and can access the core network 1130, PSTN 1140, or other networks 1160.

[0226] exist Figure 11 In the illustrated embodiment, base station 1170a constitutes part of RAN 1120a, which may include other base stations, components, or devices. Similarly, base station 1170b constitutes part of RAN 1120b, which may include other base stations, components, or devices. Each base station 1170a-1170b is used to transmit or receive radio signals within a specific geographical area (sometimes referred to as a "cell"). In some embodiments, multiple-input multiple-output (MIMO) technology may be used, with each cell having multiple transceivers.

[0227] Base stations 1170a-1170b communicate with one or more of ED 1110a-1110c via one or more air interfaces 1190 using a wireless communication link. Air interface 1190 can use any suitable wireless access technology.

[0228] System 1100 is expected to use multi-channel access capabilities, including the schemes described above. In specific embodiments, the base station and ED implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and radio protocols can also be used.

[0229] RANs 1120a-1120b communicate with the core network 1130 to provide voice, data, application, voice over internet protocol (VoIP), or other services to EDs 1110a-1110c. It should be understood that RANs 1120a-1120b or the core network 1130 can communicate directly or indirectly with one or more other RANs (not shown). The core network 1130 can also act as a gateway to other networks (such as PSTN 1140, Internet 1150, and other networks 1160). Furthermore, all or part of EDs 1110a-1110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies or protocols. Instead of wireless communication (or other than wireless communication), EDs can communicate with service providers or switches (not shown) and Internet 1150 via wired communication channels.

[0230] although Figure 11 An example of a communication system is shown, but it is possible to... Figure 11 Various modifications can be made. For example, the communication system 1100 may include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0231] Figure 12A and Figure 12B Exemplary devices are shown that can implement the methods and teachings according to the present invention. In particular, Figure 12A An exemplary ED 1210 is shown. Figure 12B An exemplary base station 1270 is shown. These components can be used in system 1100 or any other suitable system.

[0232] like Figure 12A As shown, ED 1210 includes at least one processing unit 1200. The processing unit 1200 implements various processing operations of ED 1210. For example, the processing unit 1200 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 1210 to operate within system 1100. The processing unit 1200 also supports the methods and teachings described in detail above. Each processing unit 1200 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 1200 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0233] ED 1210 also includes at least one transceiver 1202. Transceiver 1202 is used to modulate data or other content for transmission via at least one antenna or network interface controller (NIC) 1204. Transceiver 1202 is also used to demodulate data or other content received by at least one antenna 1204. Each transceiver 1202 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or wiredly. Each antenna 1204 includes any suitable structure for transmitting or receiving wireless or wired signals. One or more transceivers 1202 and one or more antennas 1204 may be used in ED 1210. Although shown as a single functional unit, transceiver 1202 may also be implemented using at least one transmitter and at least one separate receiver.

[0234] ED 1210 also includes one or more input / output devices 1206 or interfaces (e.g., a wired interface to the Internet 1150). Input / output devices 1206 facilitate interaction with users or other devices on the network (network communication). Each input / output device 1206 includes any suitable structure for providing or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network communication.

[0235] In addition, ED 1210 includes at least one memory 1208. Memory 1208 stores instructions and data used, generated, or collected by ED 1210. For example, memory 1208 may store software or firmware instructions to be executed by processing unit 1200, as well as data for reducing or eliminating interference in incoming signals. Each memory 1208 includes any suitable volatile or non-volatile storage and retrieval device. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc.

[0236] like Figure 12BAs shown, base station 1270 includes at least one processing unit 1250, at least one transceiver 1252 (which includes transmitter and receiver functions), one or more antennas 1256, at least one memory 1258, and one or more input / output devices or interfaces 1266. Those skilled in the art will understand that a scheduler is coupled to processing unit 1250. The scheduler may be included within base station 1270 or operate independently of base station 1270. Processing unit 1250 implements various processing operations of base station 1270, such as signal encoding, data processing, power control, input / output processing, or any other functions. Processing unit 1250 may also implement the methods and teachings described in detail above. Each processing unit 1250 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 1250 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0237] Each transceiver 1252 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1252 also includes any suitable structure for processing signals wirelessly or wiredly received from one or more EDs or other devices. Although shown as a combination of transceiver 1252, the transmitter and receiver may be separate components. Each antenna 1256 includes any suitable structure for transmitting or receiving wireless or wired signals. Although a common antenna 1256 is shown herein coupled to transceiver 1252, one or more antennas 1256 may be coupled to transceiver 1252, allowing separate antennas 1256 to be coupled to the transmitter and receiver if they are used as separate components. Each memory 1258 includes any suitable volatile or non-volatile storage and retrieval device. Each input / output device 1266 facilitates interaction with users or other devices in the network (network communication). Each input / output device 1266 includes any suitable structure for providing information to or receiving information from a user, including network interface communication.

[0238] Figure 13The diagram illustrates a computing system 1300, which can be used to implement the devices and methods disclosed herein. For example, the computing system can be any entity such as a UE, access node (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). A particular device may use all of the components shown or only a subset of those components, and the degree of integration between devices may vary. Furthermore, a device may include multiple instances of components, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1300 includes a processing unit 1302. The processing unit includes a central processing unit (CPU) 1314, memory 1308, and may also include a mass storage device 1304, a video adapter 1310, and an I / O interface 1312 connected to a bus 1320.

[0239] Bus 1320 can be one or more of any type of bus architecture, including a memory bus or memory controller, a peripheral bus, or a video bus. CPU 1314 can include any type of electronic data processor. Memory 1308 can include any type of non-transitory system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1308 can include ROM used at power-on and DRAM used to store programs and data during program execution.

[0240] Mass storage device 1304 may include any type of non-transitory storage device for storing data, programs, and other information, and making the data, programs, and other information accessible via bus 1320. For example, mass storage device 1304 may include one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive.

[0241] Video adapter 1310 and I / O interface 1312 provide interfaces to couple external input and output devices to processing unit 1302. Examples of input and output devices, as shown, include a display 1318 coupled to video adapter 1310 and a mouse, keyboard, or printer 1316 coupled to I / O interface 1312. Other devices may be coupled to processing unit 1302, and more or fewer interface cards may be used. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices.

[0242] The processing unit 1302 also includes one or more network interfaces 1306, which may include wired links such as Ethernet cables or wireless links to access nodes or different networks. The network interface 1306 allows the processing unit 1302 to communicate with remote units via a network. For example, the network interface 1306 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In one embodiment, the processing unit 1302 is coupled to a local area network 1322 or a wide area network for data processing and communication with other processing units, the Internet, or remote devices such as remote storage facilities.

[0243] Figure 14This is a schematic diagram of a network 1400 used for data transmission. Network 1400 includes a base station 1410 with a coverage area 1401, multiple UEs 1420, and a backhaul network 1430. As shown, base station 1410 establishes uplink (dashed line) and / or downlink (dotted line) connections with UEs 1420 for transmitting data from UEs 1420 to base station 1410 and vice versa. Data transmitted via uplink / downlink connections may include data transmitted between UEs 1420 and data transmitted to / from a remote location (not shown) via backhaul network 1430. As used herein, a base station refers to any network-side device used to provide wireless access to the network, such as an enhanced Node B, gNB, transmit / receive point (TRP), macro cell, femtocell, Wi-Fi access point, and other wireless-enabled devices. The base station can provide wireless access according to one or more wireless communication protocols, such as 5th generation new radio (5GNR), LTE, LTE advanced (LTE-A), high-speed message access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. As used herein, UE refers to any user-side device used to access the network by establishing a wireless connection with the base station, such as mobile devices, mobile stations, vehicles, and other wirelessly enabled devices. In some embodiments, network 1400 may include various other wireless devices, such as repeaters, low-power nodes, etc. It is understood that the communication system can use multiple access nodes capable of communicating with multiple UEs; for simplicity, only one base station 1410 and two UEs 1420 are shown.

[0244] Figure 15 A block diagram of another exemplary processing system 1500 for performing the methods described herein is shown, which may be installed in a host device. As shown, the processing system 1500 includes a processor 1502, a memory 1504, and interfaces 1506, 1508, 1510, which may (or may not) be as described Figure 15The processor 1502 may be any component or collection of components for performing computational and / or other processing-related tasks, and the memory 1504 may be any component or collection of components for storing programming and / or instructions for execution by the processor 1502. In one embodiment, the memory 1504 includes a non-transitory computer-readable medium. Interfaces 1506, 1508, and 1510 may be any component or collection of components that allow the processing system 1500 to communicate with other devices / components and / or users. In one embodiment, one or more of interfaces 1506, 1508, and 1510 may be used to transmit data, control, or management messages from the processor 1502 to an application installed on a host device and / or a remote device. In another embodiment, one or more of interfaces 1506, 1508, and 1510 may be used to allow a user or user device (e.g., a personal computer (PC)) to interact / communicate with the processing system 1500. The processing system 1500 may include... Figure 15 Additional components not shown, such as long-term storage devices (e.g., non-volatile memory, etc.).

[0245] In some embodiments, the processing system 1500 is included in a network device that accesses or otherwise becomes part of a telecommunications network. In one embodiment, the processing system 1500 is located in a network-side device of a wireless or wired telecommunications network, such as a base station, relay station, scheduler, controller, gateway, router, application server, or any other device within the telecommunications network. In other embodiments, the processing system 1500 is located in a user-side device accessing a wireless or wired telecommunications network, such as a mobile station, user equipment (UE), personal computer (PC), tablet computer, wearable communication device (e.g., smartwatch), wireless-enabled vehicle, wireless-enabled pedestrian, wireless-enabled infrastructure element, or any other device for accessing the telecommunications network.

[0246] In some embodiments, one or more of interfaces 1506, 1508, and 1510 connect the processing system 1500 to a transceiver for sending and receiving instructions over a telecommunications network. Figure 16A block diagram of a transceiver 1600 for sending and receiving indications over a telecommunications network is shown. The transceiver 1600 can be installed in a host device. As shown, the transceiver 1600 includes a network-side interface 1602, a coupler 1604, a transmitter 1606, a receiver 1608, a signal processor 1610, and a device-side interface 1612. The network-side interface 1602 may include any component or set of components for sending or receiving indications over a wireless or wired telecommunications network. The coupler 1604 may include any component or set of components for facilitating bidirectional communication over the network-side interface 1602. The transmitter 1606 may include any component or set of components (e.g., an up-converter, a power amplifier, etc.) for converting a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface 1602. The receiver 1608 may include any component or set of components (e.g., a down-converter, a low-noise amplifier, etc.) for converting a carrier signal received through the network-side interface 1602 into a baseband signal. Signal processor 1610 may include any component or set of components for converting baseband signals into data signals suitable for communication via device-side interface 1612, and vice versa. Device-side interface 1612 may include any component or set of components for transmitting data signals between signal processor 1610 and components within a host device (e.g., processing system 1500, local area network (LAN) port).

[0247] Transceiver 1600 can send and receive indications via any type of communication medium. In some embodiments, transceiver 1600 sends and receives indications via a wireless medium. In some embodiments, transceiver 1600 may be a wireless transceiver for communicating according to a wireless communication protocol, such as a cellular protocol (e.g., Long-Term Evolution, LTE, etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, Near Field Communication, NFC, etc.). In these embodiments, network-side interface 1602 includes one or more antenna / radiating elements. In some embodiments, network-side interface 1602 may include a single antenna, multiple independent antennas, or a multi-antenna array for multi-layer communication, such as single-input multiple-output (SIMO), multiple-input single-output (MISO), multiple-input multiple-output (MIMO), etc. In other embodiments, transceiver 1600 transmits and receives instructions via a wired medium (e.g., twisted-pair cable, coaxial cable, optical fiber, etc.). A particular processing system and / or transceiver may use all of the components shown or only a subset of those components, and the degree of integration between the devices may vary.

[0248] It should be understood that one or more steps of the exemplary methods provided herein can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmitting unit or transmitting module. A signal can be received by a receiving unit or receiving module. A signal can be processed by a processing unit or processing module. Other steps can be performed by a configuration unit or module, or a determination unit or module. Each unit or module can be hardware, software, or a combination thereof. For example, one or more of the units or modules can be integrated circuits, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0249] Although the invention and its advantages have been described in detail, it should be understood that various changes, substitutions and modifications may be made to the invention without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A communication method applied to a user equipment (UE), characterized in that, The method includes: If the predetermined time window of the first wake-up signal WUS is within the activation time, then WUS will not be monitored within the predetermined time window of the first WUS. The first WUS indicates whether the physical downlink control channel (PDCCH) is received during the associated first discontinuous reception DRX ON period. The first DRX ON period is the first DRX ON period after a predetermined time window of the first WUS, and the predetermined time window is used to transmit the first WUS.

2. The method according to claim 1, characterized in that, The method further includes: If the predetermined time window of the first WUS is not within the activation time, then the WUS is monitored within the predetermined time window of the first WUS.

3. The method according to claim 2, characterized in that, The method further includes: If the first WUS is received within the predetermined time window of the first WUS, then the PDCCH is monitored during the first DRX ON period.

4. The method according to claim 2, characterized in that, The method further includes: If the first WUS is not received within the predetermined time window of the first WUS, then the PDCCH will not be monitored during the first DRX ON period.

5. The method according to any one of claims 1-4, characterized in that, The activation time includes at least one of the following: The time period during which at least one of the following timers is running: DRX ON timer, DRX inactive timer, DRX downlink retransmission timer, DRX uplink retransmission timer, or random access contention resolution timer.

6. The method according to any one of claims 1-4, characterized in that, The activation time includes the time during which the scheduling request has been sent on the Physical Uplink Control Channel (PUCCH) and the scheduling is in a pending state.

7. The method according to any one of claims 1-4, characterized in that, The activation time includes: The time after the UE successfully receives the random access response of the random access preamble, but has not yet received the new transmission indicated by the PDCCH addressed by the cell radio network temporary identifier C-RNTI of the MAC entity; Wherein, the random access preamble is not selected by the MAC entity in a contention-based random access preamble.

8. A user equipment (UE), characterized in that, include: Non-transitory memory, including instructions; One or more processors communicate with the non-transient memory, wherein the one or more processors execute the instructions to perform the method as described in any one of claims 1-7.

9. A communication method applied to an access node, characterized in that, The method includes: If the predetermined time window of the first wake-up signal WUS is within the activation time, then the first WUS will not be sent within the predetermined time window of the first WUS. The first WUS indicates whether the physical downlink control channel (PDCCH) is transmitted during the associated first DRX ON period. The first DRX ON period is the first DRX ON period after a predetermined time window of the first WUS, and the predetermined time window is used to transmit the first WUS.

10. The method according to claim 9, characterized in that, The method further includes: If the predetermined time window of the first WUS is not within the activation time, then the first WUS is sent within the predetermined time window of the first WUS.

11. The method according to claim 10, characterized in that, The method further includes: If the first WUS is sent within the predetermined time window of the first WUS, then the PDCCH is sent during the first DRX ON period.

12. The method according to claim 10, characterized in that, The method further includes: If the first WUS is not sent within the predetermined time window of the first WUS, then the PDCCH will not be sent during the first DRX ON period.

13. The method according to any one of claims 9-12, characterized in that, The activation time includes at least one of the following: The time period during which at least one of the following timers is running: DRX ON timer, DRX inactive timer, DRX downlink retransmission timer, DRX uplink retransmission timer, or random access contention resolution timer.

14. The method according to any one of claims 9-12, characterized in that, The activation time includes the time during which the scheduling request has been sent on the Physical Uplink Control Channel (PUCCH) and the scheduling is in a pending state.

15. The method according to any one of claims 9-12, characterized in that, The activation time includes: The time after the UE successfully receives the random access response of the random access preamble, but has not yet received the new transmission indicated by the PDCCH addressed by the cell radio network temporary identifier C-RNTI of the MAC entity; Wherein, the random access preamble is not selected by the MAC entity in a contention-based random access preamble.

16. An access node, characterized in that, include: Non-transitory memory, including instructions; One or more processors communicate with the non-transient memory, wherein the one or more processors execute the instructions to perform the method as described in any one of claims 9-15.

17. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed, cause the method described in any one of claims 1-7 to be performed.

18. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed, cause the method described in any one of claims 9-15 to be performed.

Images