Power saving method for mobile stations

Abstract

The present disclosure relates to a wireless communication method that reduces power usage in a mobile station caused by monitoring a physical downlink control channel (PDCCH). The mobile station can implement a PDCCH monitoring skipping behavior that includes skipping monitoring of the PDCCH for a skipping period.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 202080096241.4, filed on February 14, 2020, entitled “Power Saving Method for Mobile Station”. TECHNICAL FIELD

[0002] The present disclosure is generally directed to methods for power saving in a mobile station. BACKGROUND

[0003] With the development of wireless communication technology, the transmission rate, delay, throughput, reliability and other performance indicators of wireless communication systems have been greatly improved by using high frequency bands, large bandwidths, multi-antenna arrangements and other technologies. On the other hand, in order to achieve high-performance wireless transmission, terminals (such as mobile stations) need to perform more complex processing to meet performance requirements, such as monitoring larger control channel bandwidths, and encoding and decoding processing of more complex control information and data information. The power consumption of the mobile station affects the user experience. Therefore, it is necessary to provide power saving solutions for mobile stations within a wireless communication system. SUMMARY

[0004] In one embodiment, a wireless communication method includes a mobile station determining whether to perform physical downlink control channel (PDCCH) monitoring skipping according to at least one of occurrence of a skipping trigger event or predefined information. In response to determining to perform PDCCH monitoring skipping, the mobile station performs PDCCH monitoring skipping, which includes skipping, by the mobile station, monitoring of a PDCCH for a duration of a skipping period of a first number of units.

[0005] In another embodiment, another method of communication between a wireless access node and a mobile station includes determining, by the wireless access node, indication information according to at least one of high layer signaling or predefined information. The indication information includes an indication for the mobile station to perform physical downlink control channel (PDCCH) monitoring skipping, an index of a PDCCH monitoring skipping period, or

[0006] at least one of a definition of the PDCCH monitoring skipping period. The method further includes the wireless access node transmitting the indication information to the mobile station.

[0007] Other aspects and alternatives of the above embodiments and implementations thereof are described in more detail in the following drawings, description and claims. BRIEF DESCRIPTION OF DRAWINGS

[0008] Figure 1 An example system diagram including a mobile station and a wireless access node according to various embodiments is shown.

[0009] Figure 2 An example time diagram illustrating example PDCCH monitoring behavior according to various embodiments is shown.

[0010] Figure 3 Another example time diagram illustrating example PDCCH monitoring behavior according to various embodiments is shown.

[0011] Figure 4 Another example time diagram illustrating various embodiments is shown.

[0012] Figure 5 An example flow diagram illustrating a method performed by a mobile station according to various embodiments is provided.

[0013] Figure 6 An example flow diagram illustrating a method of communicating between a wireless access node and a mobile station according to various embodiments is provided.

[0014] Figure 7 An example time diagram illustrating various aspects of a default cycle according to various embodiments is shown. DETAILED DESCRIPTION

[0015] Wireless access networks provide network connectivity between mobile stations and information or data networks, such as voice communication networks or the Internet. Example wireless access networks can be based on cellular technology, which can be further based on, for example, 4G, Long Term Evolution (LTE), 5G, New Radio (NR), and / or New Radio Unlicensed (NR-U) technology and / or formats.

[0016] Figure 1 An example system diagram including a mobile station 102 and a wireless access node 104 according to various embodiments is shown. The mobile station 102 can include a user equipment (UE), which can also include, but is not limited to, a mobile phone, a smart phone, a tablet, a laptop, or other mobile device capable of wireless communication over a network. The mobile station 102 can include a transceiver circuit 106 coupled to an antenna 108 to enable wireless communication with the wireless access node 104. The transceiver circuit 106 can also be coupled to a processor 110, which can also be coupled to a memory 112 or other storage device. The memory 112 can store therein instructions or code, which when read and executed by the processor 110, cause the processor 110 to implement the various methods described herein.

[0017] Similarly, the wireless access node 104 can comprise a base station or other wireless network access point capable of wirelessly communicating with one or more mobile stations over a network. For example, in various embodiments, the wireless access node 104 can comprise a 4G LTE base station, a 5G NR base station, a 5G central unit base station, a 5G distributed unit base station, or a next generation Node B (gNB), an enhanced Node B (eNB), or other base station. The wireless access node 104 can include transceiver circuitry 114 coupled to an antenna 116, which can include an antenna tower 118 in various ways to enable wireless communication with the mobile station 102. The transceiver circuitry 114 can also be coupled to one or more processors 120, which can also be coupled to a memory 122 or other storage device. The memory 122 can store therein instructions or code that, when read and executed by the processor 120, cause the processor 120 to implement the various methods described herein.

[0018] The wireless access network can provide or employ various transport formats and protocols for wireless message transmission between the mobile station 102 and the wireless access node 104. In existing Long Term Evolution (LTE) and 5G New Radio (NR) access technology communication systems, the mobile station 102 (e.g., user equipment (UE)) needs to know the uplink scheduling grant information for transmitting a physical uplink shared channel (PUSCH) and the downlink scheduling assignment information for receiving a physical downlink shared channel (PDSCH). This information is included in downlink control information (DCI) and transmitted by the wireless access node (e.g., base station or gNB) to the mobile station (e.g., UE) on a physical downlink control channel (PDCCH) in different DCI formats. Thus, the mobile station should first monitor the PDCCH.

[0019] The UE needs to keep monitoring the PDCCH at the PDCCH monitoring occasions to avoid missing any data scheduling information. The PDCCH monitoring occasions are determined by parameters such as a periodicity ks, a duration Ts in the periodicity, and an offset Os associated with the starting position of the periodicity. These parameters are configured in the SearchSpace information element (IE) in the radio resource control (RRC) signaling and can at least partially define a search space set. Figure 2 A time diagram illustrating an example PDCCH monitoring behavior with ks= 2 slots, Ts= 1 slot, and Os= 0 is shown. According to the example PDCCH monitoring behavior, PDCCH monitoring occasions 202 are shown separated by slots in which no monitoring occurs.

[0020] In various examples, as also Figure 3As shown in the middle, the mobile station can implement a discontinuous reception (DRX) mode to achieve power saving. The basic mechanism of DRX is to configure the mobile station with a DRX cycle. The drx-ondurationTimer starts the DRX cycle, where the mobile station is in a "DRX on" state and continues to monitor the PDCCH during the DRX cycle. If the mobile station successfully decodes the downlink control information (DCI), the mobile station stays in the wake-up state (in the "DRX on" state) and starts the inactivity timer drx-inactivityTimer. The mobile station can go back to the sleep state (in the "DRX off" state) after the drx-ondurationTimer or the drx-inactivityTimer expires. In the "DRX off" state, the mobile station does not monitor the PDCCH and thus reduces the power consumption. However, according to the prior solutions, during the "DRX on", the mobile station continuously monitors the PDCCH throughout the "DRX on" time, which does not save power. The PDCCH monitoring behavior of the mobile station during the "DRX on" still consumes a lot of unnecessary power. For example, in a sparse traffic model, especially for longer DRX cycle configuration, more power is wasted for monitoring the PDCCH.

[0021] Other power saving solutions have been proposed. For example, during the "DRX on", the mobile station can be configured with at least one minimum applicable scheduling offset (i.e., K0min and / or K2min) and the DCI can indicate the index of the configured value. If the indicated value of K0min and / or K2min is greater than 0, the power consumption of PDCCH monitoring in the time slot can be reduced and additional power saving can be achieved by the mobile station. However, these solutions are still not optimal.

[0022] The method provided in the current disclosure describes a power saving method where the mobile station performs PDCCH monitoring skipping, e.g., during the "DRX on". By doing so, the mobile station can not monitor the PDCCH for a period of time (or duration) even during the "DRX on", which reduces the number of time slots that the mobile station needs to monitor to achieve further power saving. For example, if one or more PDCCH monitoring occasions are within the time of the PDCCH skipping period, the mobile station 102 does not monitor the PDCCH monitoring occasion(s).

[0023] Figure 4An example time diagram illustrating various aspects of the present disclosure is shown. A series of units, such as slots or times, are shown. After a skip trigger event occurs or in response to predefined information, a skip period of a first number of units (e.g., slots, times, etc.) of duration can perform PDCCH monitoring skipping. Optionally, an application delay can be applied after the skip trigger event and before the PDCCH monitoring skipping is performed in the skip period, during which the mobile station 102 continues to monitor the PDCCH. In some embodiments, after the PDCCH monitoring is skipped, the mobile station 102 can resume normal monitoring of the PDCCH. In other embodiments, after the PDCCH monitoring is skipped, the mobile station 102 can monitor the PDCCH using a new search space set. For example, in the new search space set, the periodicity can be greater than the periodicity of the old search space set, and / or the duration can be less than the duration of the old search space set.

[0024] Figure 5 An example flowchart illustrating a method 500 performed by a mobile station 102 according to various embodiments is provided. At step 502, the mobile station 102 determines whether to perform PDCCH monitoring skipping according to at least one of occurrence of a skip trigger event or predefined information. At step 504, in response to the mobile station 102 determining to perform PDCCH monitoring skipping in step 502, the mobile station performs PDCCH monitoring skipping. As shown at 506, the PDCCH monitoring skipping includes skipping, by the mobile station 102, monitoring of the PDCCH for a skip period of a first number of units of duration.

[0025] The PDCCH skip period is the number of units (or time) in which the mobile station does not monitor the PDCCH. It can be an integer greater than or equal to 0 (e.g., 1). The units can include slots, PDCCH monitoring occasions, PDCCH monitoring periodicity, or (sub)frames, or milliseconds, or PDCCH monitoring duration.

[0026] The disclosed solutions relate to at least the following: skip trigger methods (how to instruct the mobile station to perform or not perform PDCCH monitoring skipping); application delay (how to determine, convey, and / or implement the application delay); and PDCCH skip period (how to determine, convey, and / or implement the skip period).

[0027] The mobile station 102 is triggered to perform PDCCH monitoring skipping by various methods, each of which is discussed below. In various embodiments, the mobile station 102 can be triggered to perform PDCCH monitoring skipping by predefined signaling, by detection of predefined signaling, by predefined information, and / or by a default method.

[0028] Triggering by predefined signaling The mobile station 102 is triggered to perform PDCCH monitoring skipping by various methods, each of which is discussed below. In various embodiments, the mobile station 102 can be triggered to perform PDCCH monitoring skipping by predefined signaling, by detection of predefined signaling, by predefined information, and / or by a default method.

[0029] The wireless access node 104 can send predefined signaling and / or higher layer signaling (e.g., radio resource control (RRC) signaling) to the mobile station 102. The predefined signaling can indicate at least one of whether to perform PDCCH monitoring skipping, an index of a PDCCH skipping period to be used, or a description of a PDCCH skipping period (e.g., a number of units to skip). The higher layer signaling can configure at least one PDCCH skipping period candidate. In some methods, the higher layer signaling can include a PDCCH monitoring duration and / or a PDCCH skipping period.

[0030] Figure 6 An example flowchart illustrating a method 600 of communicating between a wireless access node 104 and a mobile station 102 is provided in accordance with various embodiments. At step 602, the wireless access node 104 determines indication information in accordance with at least one of higher layer signaling or predefined information, where the indication information includes at least one of an indication that a mobile station perform physical downlink control channel (PDCCH) monitoring skipping, an index of a PDCCH monitoring skipping period, or a description of a PDCCH monitoring skipping period. At step 604, the wireless access node 104 sends the indication information to the mobile station 102. In some embodiments, the indication information is sent in predefined signaling.

[0031] The mobile station receives the indication information sent by the wireless access node 104 (e.g., within the predefined signaling), determines a PDCCH skipping period in accordance with the predefined signaling and / or higher layer signaling, and performs PDCCH monitoring skipping by not monitoring a PDCCH during the PDCCH skipping period. The mobile station can perform the PDCCH monitoring skipping after applying a delay, such as 1 time slot after receiving the predefined signaling.

[0032] Thus, in an example method performed by the mobile station 102, the skipping trigger event can include receiving indication information from the wireless access node 104 indicating that the mobile station perform PDCCH monitoring skipping. In various embodiments, the indication information can be received within or as part of predefined signaling. As described above, the indication information can include at least one of an instruction or indication to perform or not perform PDCCH monitoring skipping, an index of a skipping period to be used, and / or a description of a duration of a first number of time slots of a skipping period. The mobile station 102 can then determine to perform or not perform PDCCH monitoring skipping in accordance with the received indication information and / or in accordance with higher layer signaling.

[0033] In various approaches, the mobile station 102 can not perform PDCCH monitoring skipping if the radio access node 104 does not send high layer signaling configuring at least one PDCCH skipping period candidate for the mobile station 102. Otherwise, the mobile station 102 can determine to perform or not perform PDCCH monitoring skipping according to the received indication information.

[0034] In some approaches, if the mobile station 102 receives a first predefined signal triggering PDCCH monitoring skipping and before the mobile station 102 completes a previous PDCCH skipping, the mobile station 102 receives a second predefined signal indicating not to perform PDCCH monitoring skipping, the mobile station 102 will monitor PDCCH normally after another application delay. In one particular example, the first predefined signal can be a downlink control information (DCI) and the second predefined signal can be a medium access control (MAC) control element (CE). In one example, the mobile device 102 will monitor PDCCH normally at the beginning of the next PDCCH monitoring duration. In another example, if the mobile station receives a first predefined signal triggering PDCCH monitoring skipping and before the mobile station completes a previous PDCCH skipping, the mobile station 102 receives a second predefined signal also triggering PDCCH monitoring skipping, the mobile station 102 will perform another PDCCH monitoring skipping after the previous PDCCH skipping.

[0035] In various approaches, the predefined signaling (e.g., which includes indication information) is sent by the radio access node 104 to the mobile station 102 as at least one of: a downlink control information (DCI), a medium access control (MAC) control element (CE), and / or a radio resource control (RRC) signaling. In some embodiments, the predefined signaling is a MAC CE. The MAC CE can be used at least to stop PDCCH monitoring skipping. That is, if the mobile station 102 receives a MAC CE indicating to stop PDCCH monitoring skipping, the mobile station 102 can continue to monitor PDCCH, e.g., after an application delay.

[0036] In some embodiments, the predefined signaling (e.g., which includes the indication information) is a DCI. The DCI can be used to indicate whether the mobile station 102 performs PDCCH monitoring skipping, or provide an index or description of a PDCCH skipping period according to an information field in the DCI. The information field can include at least one of an indication to perform PDCCH monitoring skipping, an index of a skipping period, and / or a description of a duration of a first number of units of a skipping period. The field can be X bits, where X can be an integer greater than 0 and less than 10. In some embodiments, the DCI is a DCI format 0_1 or 1_1 or 2_0. In some embodiments, the field in the DCI is a dedicated field used to indicate the PDCCH skipping information. In other embodiments, the field in the DCI is a repurposed existing information field, such as, for example, a minimum applicable scheduling offset indication field (e.g., K0min and / or K2min). Repurposing the existing field can involve using at least a portion of the existing field, and repurposing information included within the field for the purpose of at least PDCCH monitoring skipping indication information.

[0037] In various approaches, a field in a DCI format 0_1 or 1_1 is used to indicate a minimum applicable scheduling offset (or minimum applicable scheduling offset limit) K0min and / or K2min. The field can also be used to indicate the performance of PDCCH monitoring skipping, e.g., if a PDCCH skipping period has been configured. In one example, if there is only one configured PDCCH skipping period, a “0” in the field indicates triggering performance of PDCCH monitoring skipping within the PDCCH skipping period (e.g., after applying a delay), and a “1” in the field indicates not performing PDCCH skipping. In other examples, if there are two configured PDCCH skipping periods, a “0” in the field can indicate triggering PDCCH monitoring skipping within the PDCCH skipping period of lower index (e.g., after applying a delay), and a “1” in the field can indicate triggering PDCCH monitoring skipping within the PDCCH skipping period of higher index (e.g., after applying a delay). In other examples, if there is no configured PDCCH skipping period, a “0” in the field indicates triggering performance of PDCCH monitoring skipping within the PDCCH skipping period (e.g., after applying a delay), and a “1” in the field indicates not performing PDCCH skipping, which can be the same as the minimum applicable scheduling offset (e.g., K0min). The application delay can be the same as the application delay of the minimum applicable scheduling offset limit. In some examples, the field is present only when the minimum applicable scheduling offset or PDCCH skipping period is configured by RRC.

[0038] In some embodiments, each DCI received by the mobile station 102 with the field indicating PDCCH skipping information will trigger PDCCH monitoring skipping. In some embodiments, only DCI indicating a change in the indication of PDCCH monitoring skipping information or K0min or K2min will trigger PDCCH monitoring skipping. In some embodiments, the PDCCH monitoring skipping information includes a PDCCH skipping period.

[0039] In some embodiments, the field is present if at least one of the following two parameters is configured: the minimum applicable scheduling offset (e.g., K0min or K2min), or the PDCCH skipping period (or another PDCCH skipping parameter). If the minimum applicable scheduling offset is not configured by RRC, the field can be used to indicate, trigger, and / or control PDCCH monitoring skipping only.

[0040] Triggering by detection of predefined signaling

[0041] In a slightly different method from the above method, the radio access node 104 can send predefined signaling and / or higher layer signaling to the mobile station 102. The mobile station 102 then detects the predefined signaling as a skipping trigger event, providing the mobile station 102 with an indication to perform PDCCH monitoring skipping. If the mobile station 102 receives the predefined signaling sent by the radio access node 104, the mobile station 102 performs PDCCH monitoring skipping after applying a delay. However, if the mobile station 102 does not receive any such predefined signaling, the mobile station 102 will continue to monitor the PDCCH.

[0042] In some embodiments, the predefined signaling can be monitored by the mobile station 102 when the drx-InactivityTimer is running. In some embodiments, the predefined signaling can be monitored by the mobile station 102 when the mobile station 102 is in "DRX on" mode.

[0043] In some embodiments, the predefined signaling is DCI. A field in the DCI can be used to indicate whether the DCI is used for PDCCH skipping. For example, if the field is set to “1”, the DCI is used to trigger PDCCH monitoring skipping. But if the field is set to “0”, the DCI is not used for PDCCH skipping indication. In some embodiments, if the field is set to “1”, one or more other fields in the DCI can be used to indicate the PDCCH skipping period. In one example, the one or more other fields in the DCI can indicate the PDCCH skipping period according to a bitmap. The bitmap can indicate whether to monitor PDCCH in a number of units (e.g., slots). In another example, the one or more other fields in the DCI used to indicate the PDCCH skipping period indicate a value (e.g., description) or index of the PDCCH skipping period. Triggering by predefined information

[0044] In some embodiments, the mobile station 102 uses the predefined information to determine whether to monitor PDCCH in the PDCCH skipping period after the delay. In various examples, the predefined information can be at least one of: a timer, a bandwidth part (BWP), a maximum MIMO layer, a frequency range (FR) type, a type of mobile station, a mobile station (UE) capability, UE assistance information, or a subcarrier spacing (SCS). In some embodiments, the predefined information can be a higher layer signaling (e.g., RRC signaling). In various approaches, the PDCCH skipping period is indicated according to at least one of: a higher layer signaling, a predefined value, a DCI, a MAC CE, or a minimum applicable scheduling offset.

[0045] In some embodiments, the predefined information is a timer, wherein the occurrence of a skip trigger event includes the expiration of the timer. That is, if the timer expires, mobile station 102 does not monitor the PDCCH during the PDCCH skip period following the application delay. In some methods, radio access node 104 sets and / or determines a timer value and sends it to the mobile station. Radio access node 104 may set or determine the timer value based on at least one of the bandwidth portion (BWP) or carrier component (CC). In some embodiments, mobile station 102 starts or restarts the timer after receiving a downlink (DL) allocation or uplink (UL) grant, or after receiving a DCI indicating a new transmission. In some embodiments, the timer is started or restarted after a PDCCH monitoring skip, or in other words, at the first slot where mobile station 102 (re)starts monitoring the PDCCH. In some embodiments, mobile station 102 starts or restarts the timer after receiving RRC signaling configuring parameters for the PDCCH skip period. In some embodiments, mobile station 102 starts or restarts the timer after a BWP handover. In some embodiments, timers are configured by BWP (timer configuration is at the BWP level). In some embodiments, timers are configured by mobile station or by carrier component (CC) (timer configuration is at the cell level).

[0046] In other embodiments, the predefined information is the BWP. For example, in some BWPs, mobile station 102 can trigger PDCCH monitoring skipping via DCI or a timer. However, in other BWPs, mobile station 102 cannot trigger PDCCH monitoring skipping via DCI or a timer. For example, in BWP 1, mobile station 102 cannot perform PDCCH monitoring.

[0047] Skip, while mobile station 102 can perform PDCCH monitoring skip in other BWPs. In another example, if the BWP bandwidth is greater than M... BWP MHz (for example, where M BWP If the value is an integer greater than 20, then mobile station 102 can trigger PDCCH monitoring skipping; otherwise, mobile station 102 can stop PDCCH skipping. In another example, if the BWP bandwidth is less than or equal to M... BWP MHz (for example, where M BWP If the value is an integer greater than 20, then mobile station 102 can trigger PDCCH monitoring skip; otherwise, mobile station 102 can stop PDCCH skipping.

[0048] In some embodiments, mobile station 102 may trigger PDCCH monitoring skipping for a total of M cycles. For example, a cycle may involve mobile station 102 skipping (not monitoring) PDCCH for a duration (e.g., a PDCCH skipping period of a first number of units of duration), and then monitoring PDCCH for another duration (e.g., a monitoring period of a second number of units of duration). M may be an integer greater than 0 and, for example, less than 10.

[0049] In some embodiments, the predefined information may be the maximum MIMO layer. For example, if the maximum MIMO layer is greater than 2, mobile station 102 may trigger PDCCH monitoring skip; otherwise, mobile station 102 may stop or not trigger PDCCH monitoring skip. In another example, if the maximum MIMO layer is not greater than 2, mobile station 102 may trigger PDCCH monitoring skip; otherwise, mobile station 102 may stop or not trigger PDCCH monitoring skip.

[0050] In some embodiments, predefined information is associated with frequency range (FR) types. For example, mobile station 102 may trigger PDCCH monitoring skipping via DCI or a timer in FR2, while it may not trigger PDCCH monitoring skipping in FR1. In another example, mobile station 102 may not trigger PDCCH monitoring skipping via DCI or a timer in FR2, while it may trigger PDCCH monitoring skipping in FR1.

[0051] In some embodiments, the predefined information is UE assistance information. For example, mobile station 102 sends UE assistance information with a desired PDCCH skip period to radio access node 104. Radio access node 104 may send an acknowledgment signaling. Mobile station 102 may receive the acknowledgment signaling and, based on the occurrence of a skip triggering event or predefined information, trigger a PDCCH monitoring skip within the desired PDCCH skip period. The acknowledgment signaling may include an index or description of the skip period corresponding to the desired skip period.

[0052] In some embodiments, predefined information is related to mobile station type (e.g., UE type) or mobile station capability (e.g., UE capability). For example, the mobile station type or capability may not support PDCCH monitoring skipping. In various methods, if mobile station 102, which does not support PDCCH monitoring skipping, receives a PDCCH skipping indication (e.g., a DCI with the indication), then mobile station 102 may ignore the PDCCH skipping indication information. Similarly, in various methods, if mobile station 102 does not support PDCCH monitoring skipping, then radio access node 104 may not send the PDCCH skipping indication information to the UE.

[0053] In various embodiments, the mobile station 102 will perform PDCCH monitoring skipping only when the mobile station is in a DRX active time (e.g., a "DRX on" mode).

[0054] Triggering default PDCCH monitoring skipping behavior

[0055] In some embodiments, performing PDCCH monitoring skipping includes performing default PDCCH monitoring skipping. In certain approaches, default PDCCH monitoring skipping includes, by the mobile station 102, monitoring the PDCCH for a monitoring period of a second number of units of time after the skipped monitoring of the PDCCH for the skipping period. In some embodiments, if the at least one PDCCH skipping period candidate is configured by higher layer signaling and the mobile station 102 does not receive the DCI triggering PDCCH monitoring skipping, the mobile station 102 can perform default PDCCH monitoring skipping.

[0056] In one example, default PDCCH monitoring skipping includes the mobile station 102 performing PDCCH monitoring skipping according to a default PDCCH skipping period (e.g., of a first number of units of time). The default PDCCH skipping period can be a PDCCH skipping period candidate configured by higher layer signaling. Thereafter, the mobile station 102 can monitor the PDCCH for a monitoring period of a second number of units of time. In some embodiments, the second number of units is determined according to a time in which the UE monitors the entire duration of each search space set. In certain embodiments, the mobile station can repeat the cycle of skipping and monitoring as part of the default. In further embodiments, the mobile station 102 can repeat the cycle of skipping and monitoring for M cycles. M can be an integer greater than 0 and less than 50 (e.g., 1). In various examples, the cycle can begin after the mobile station 102 monitors the PDCCH for the entire duration of at least one search space set.

[0057] Figure 7An example time diagram illustrating various aspects of the default cycle discussed above is shown. For example, a series of units (e.g., slots) is shown. Two example search space sets are shown within the slots. The first example search space set 1 is shown with a periodicity of ks= 5 and a duration of Ts= 2. The second example search space set 2 is shown with a periodicity of ks= 3 and a duration of Ts= 1. For each DL BWP configured for a UE in a serving cell, the mobile station 102 can be provided by higher layers with S < 10 search space sets, where for each search space set from the S search space sets, the following is provided to the UE by SearchSpace: a search space set index; a PDCCH monitoring periodicity and a PDCCH monitoring offset of Os slots represented by monitoringSlotPeriodicityAndOffset; and a duration of the search space set S in the number of slots indicated by a duration of Ts < ks slots.

[0058] A default PDCCH skipping mode cycle is shown, including a first number of units of duration of PDCCH skipping periods of five slots, and a second number of units of duration of monitoring periods also of five slots. The shaded slots indicate that the mobile station 102 performs PDCCH monitoring skipping, in which it does not monitor PDCCH in the shaded slots.

[0059] In some embodiments, the mobile station 102 can perform a default PDCCH monitoring behavior if at least one of the following predefined conditions is met (e.g., as an occurrence of a skipping trigger event): 1) one or more PDCCH skipping periods are configured, and the mobile station 102 does not receive a PDCCH that triggers PDCCH monitoring skipping, or 2) a BWP switch occurs (e.g., a timer-based BWP switch).

[0060] In certain approaches, the default behavior includes the mobile station 102 performing PDCCH monitoring skipping, where the PDCCH skipping period is a default PDCCH skipping period. In other approaches, the default behavior includes the mobile station 102 performing PDCCH monitoring skipping for M cycles, where a cycle involves the mobile station 102 not monitoring PDCCH during a default PDCCH skipping period, and subsequently monitoring PDCCH for a second period of time (e.g., a second number of units). The mobile station 102 will continue to perform the cycle (e.g., for M) as long as it does not receive a DL assignment, a UL grant, or a new transmission indication. However, if the mobile station 102 receives a DL assignment, or a UL grant, or a new transmission indication, or a medium access control (MAC) control element (CE) indicating to stop PDCCH monitoring skipping, the mobile station 102 stops performing PDCCH monitoring skipping, and continues to monitor PDCCH or follow the behavior indicated by the trigger of the DCI.

[0061] In various embodiments, the second time period (e.g., the second number of units) can be an entire PDCCH monitoring duration, a PDCCH monitoring occasion, a plurality of PDCCH monitoring periods, a plurality of slots, or a plurality of milliseconds. In certain approaches, the monitoring period (e.g., the second number of units) can correspond to a period of a search space set. Similarly, in certain approaches, the skipping period (e.g., the first number of units) can correspond to at least one of an integer multiple of a period of a search space, or a default number of units.

[0062] Fallback behavior

[0063] Some events can trigger the mobile station 102 to operate according to a fallback behavior. In various embodiments, the triggering events can include:

[0064] 1) triggering a physical random access procedure, e.g., triggered by higher layers, or by a PDCCH order, or due to beam failure recovery;

[0065] 2) radio link failure;

[0066] 3) handover command;

[0067] 4) BWP switching, e.g., timer-based BWP switching; and / or

[0068] 5) the mobile station 102 enters DRX idle mode, e.g., due to expiration of drx- OnDurationTimer or drx-inactivityTimer.

[0069] The fallback behavior can include the mobile station 102 stopping PDCCH monitoring skipping. That is, if the mobile station 102 is in a PDCCH skipping period and is not monitoring PDCCH, if one of the above events occurs, then the mobile station 102 can start monitoring PDCCH if the UE is in active time. Active time includes the total duration of time that the mobile station 102 monitors PDCCH. This can include the DRX cycle’s “on-duration,” which is the time when the inactivity timer drx-inactivityTimer has not expired that the mobile station 102 performs continuous reception, and the time when the UE is performing continuous reception while waiting for a retransmission opportunity.

[0070] In some embodiments, the default PDCCH skip period (X_default) is related to the PDCCH monitoring duration. In one example, X_default = A * PDCCH monitoring duration, where A is an integer greater than 0 (e.g., 1). In some embodiments, the default PDCCH skip period (X_default) is related to the PDCCH monitoring period. In one example, X_default = A1 * PDCCH monitoring period, where A1 is an integer greater than 0 (e.g., 1). In other embodiments, the default PDCCH time skip period (X_default) is related to the K0min, K2min, or Zμ value.

[0071] Combined triggering methods

[0072] In some embodiments, the radio access node 104 sends predefined signaling and / or higher-layer signaling to the mobile station 102. The mobile station 102 receives the predefined signaling from the radio access node 104 and determines a PDCCH skip period based on the predefined signaling and / or higher-layer signaling. The mobile station 102 then skips monitoring of the PDCCH during the PDCCH skip period following the application delay. In various embodiments, the predefined signaling is a DCI. The higher-layer signaling may indicate at least one PDCCH skip period.

[0073] If mobile station 102 is configured by higher-layer signaling to have at least one PDCCH skip period and has not received a DCI that triggers a PDCCH monitoring skip, mobile station 102 may start a timer. The timer may be restarted after receiving a new data schedule or performing a PDCCH monitoring skip. After the timer expires, mobile station 102 may perform a PDCCH monitoring skip after a first application delay (e.g., 0 or 1 time slots) and may restart the timer after performing the PDCCH monitoring skip. If mobile station 102 receives a DCI that triggers a PDCCH monitoring skip, mobile station 102 may perform a PDCCH skip after a second application delay (e.g., an application delay related to the minimum applicable schedule offset limit) and may restart the timer after performing the PDCCH monitoring skip. In some embodiments, the first application delay is different from the second application delay.

[0074] Determining the application delay

[0075] As discussed above, in some embodiments, the wireless access node 104 transmits predefined signaling and / or higher layer signaling to the mobile station 102. The predefined signaling includes indication information indicating at least one of whether to perform PDCCH monitoring skipping, an index of a PDCCH skipping period, or a description of a PDCCH skipping period. The indication information will be valid after an application delay. Thus, the PDCCH monitoring skipping further includes waiting for an application delay before starting skipping monitoring of PDCCHs in the skipping period, the application delay including a second number of units after occurrence of a skipping trigger event (e.g., reception of the indication information).

[0076] The application delay can be determined based on at least one of an application delay of a minimum scheduling offset limit, a minimum applicable scheduling offset, a subcarrier spacing (SCS), a frequency range (FR) type, a value associated with the SCS (Zμ), K0, K2, a physical downlink shared channel (PDSCH) processing time, a bandwidth part (BWP), a PDCCH skipping period, a radio resource control (RRC) signal, or a fixed value.

[0077] Zμis a fixed value associated with the SCS. For example, Zμis one of 1, 1, 2, or 2, each value mapping to an SCS of 15 kHz, 30 kHz, 60 kHz, or 120 kHz. That is, if the SCS is 15 kHz, then Zμequals 1; if the SCS is 60 kHz, then Zμequals 2. K0is a slot offset quantity between a DCI and a physical downlink shared channel (PDSCH) scheduled by the DCI. K2is a slot offset quantity between a DCI and a physical uplink shared channel (PUSCH) scheduled by the DCI. The FR type can include FR1 (frequency range 1, including 410 MHz - 7125 MHz) and FR2 (24250 MHz - 52600 MHz).

[0078] In some embodiments, the application delay of PDCCH skipping (X_skip) is determined based on an application delay of a minimum scheduling offset limit. When a UE is scheduled with DCI format 0_1 or 1_1 with a “minimum applicable scheduling offset indicator” field, the K0minand K2minvalues to be applied can be determined, and the previously applied K0minand K2minvalues are applied until the new values take effect after the application delay. K0minis a minimum slot offset quantity between a DCI and a physical downlink shared channel (PDSCH) scheduled by the DCI. K2minis a minimum slot offset quantity between a DCI and a physical uplink shared channel (PUSCH) scheduled by the DCI.

[0079] For example, if the minimum applicable scheduling offset is configured by higher layer signaling, or K0min and / or K2min is applied, the value of the application delay X_skip is determined by the following when the DCI with the field that can indicate PDCCH monitoring skipping is received within the first three symbols of a slot,

[0080]

[0081] where K 0minOld is the current applied K0min value of the active DL BWP in the scheduled cell, and Zμ is determined by the subcarrier spacing (SCS) of the active DL BWP in the scheduled cell (e.g., given in Table 1 below), and μPDCCH and μPDSCH are the subcarrier spacing (SCS) configurations for PDCCH and PDSCH, respectively. K0min is the minimum applicable value of K0. When the DCI with the field that can indicate PDCCH monitoring skipping is received outside of the first three symbols of a slot, the value of Zμ (from Table 1) is incremented by one before determining the application delay X_skip.

[0082] kHz μ Z μ ]]> 15 0 1 30 1 1 60 2 2 120 3 2

[0083] Table 1

[0084] In some embodiments, the application delay (X_skip) is determined based on a fixed value. For example, if the BWP is not configured with K0min and / or K2min, X_skip can be equal to a fixed value M. M can be an integer greater than or equal to 0 and less than 20 (e.g., 1).

[0085] In some embodiments, the application delay (X_skip) is determined based on the minimum applicable scheduling offset (K0min) on the scheduled cell where the DCI is received. For example, X_skip = K0min.

[0086] In some embodiments, the application delay (X_skip) is determined according to the SCS. For example, for a BWP with SCS = 15, 30kHZ, X_skip = 2 slots, and for a BWP with SCS = 60, 120kHZ, X_skip = 4 slots.

[0087] In some embodiments, the application delay (X_skip) is determined by RRC signaling.

[0088] In some embodiments, the application delay (X_skip) is determined based on the PDCCH skipping period. For example, X_skip can be equal to a default PDCCH skipping period, where the default PDCCH skipping period is the PDCCH skipping period configured by RRC.

[0089] In some embodiments, the application delay (X_skip) is determined based on a parameter of delta (Δ). Δ is determined based on a number of symbols of PDCCH SCS counting from the end of the last symbol of the received PDCCH to the beginning of the first symbol of the corresponding received PDSCH, quantized (using the granularity of PDSCH slot duration) to the next PDSCH slot boundary. For example, X_skip can be greater than or equal to delta (Δ).

[0090] In some embodiments, the application delay (X_skip) is determined based on PDSCH processing time. For example, X_skip can be equal to PDSCH processing time.

[0091] In some embodiments, the application delay (X_skip) is determined based on Zμ. For example, X_skip = Zμ.

[0092] In some embodiments, the application delay (X_skip) is determined based on K0. For example, X_skip = K0. In some embodiments, the application delay (X_skip) is determined based on K2. For example, X_skip = K2.

[0093] In some embodiments, if the DCI indicates a PDCCH skipping period, the mobile station 102 will not monitor PDCCH after successfully decoding PDSCH or sending an acknowledgement (ACK).

[0094] In some embodiments, the application delay (X_skip) is determined according to PDCCH monitoring duration. For example, if the DCI indicates a PDCCH skipping period, the mobile station 102 will not monitor PDCCH from the next PDCCH monitoring duration.

[0095] In some embodiments, the mobile station 102 can be indicated PDCCH skipping information according to DCI and timer, where the configuration of application delay triggered by DCI and timer can be different from each other. In some embodiments, the mobile station 102 can be indicated PDCCH skipping information according to DCI and timer and MAC CE, where the configuration of application delay triggered by DCI and timer and MAC CE are different from each other.

[0096] In some embodiments, the application delay (X_skip) is determined according to the application delay of the minimum applicable scheduling offset limit (X_min) and a fixed value (A). For example, if the mobile station 102 is configured with the minimum applicable scheduling offset in the active BWP, X_skip = X_min, otherwise, X_skip = A.

[0097] In some embodiments, the application delay (X_skip) is different in different cases. For example, if the mobile station 102 is configured with a minimum applicable scheduling offset in the active BWP, then X_skip = A, where A is a value associated with the application delay of the minimum applicable scheduling offset restriction. If the DCI that schedules across BWPs triggers PDCCH monitoring skipping, then X_skip = B, where B is a value associated with the BWP switching delay. In other words, the mobile station 102 can perform PDCCH skipping after a BWP switch. In another case, X_skip = C, where C is a fixed value (e.g., 1).

[0098] In some embodiments, the application delay can be different if the mobile station 102 can perform PDCCH monitoring skipping by different methods. For example, if the mobile station 102 performs PDCCH skipping by the default method (discussed above), then the application delay X_skip can be equal to 0 or 1 slot. If the mobile station 102 performs PDCCH monitoring skipping triggered by DCI, then the application delay (X_skip) can be related to the minimum applicable scheduling offset (K0min), and in some embodiments, X_skip = K0min.

[0099] In other embodiments, if the scheduling DCI is used to indicate PDCCH skipping, then the mobile station 102 can not monitor PDCCH after successfully decoding the PDSCH or transmitting an acknowledgement (ACK) or transmitting PUSCH.

[0100] Determining the skipping period

[0101] The PDCCH skipping period is the number of units (or time) in which the mobile station does not monitor PDCCH. It can be an integer greater than or equal to 0 (e.g., 1). The units can include slots, PDCCH monitoring occasions, PDCCH monitoring periods, or (sub)frames, or milliseconds, or PDCCH monitoring durations.

[0102] In various embodiments, the skip period is configured for the mobile station 102 or indicated to the mobile station 102 through at least one of a downlink control information (DCI), a medium access control (MAC) control element (CE), or a radio resource control (RRC) message. In various embodiments, the skip period is determined (e.g., by the wireless access node 104) based on at least one of a minimum applicable scheduling offset, a subcarrier spacing (SCS), a frequency range (FR) type, a discontinuous reception (DRX) mode on duration timer, a DRX inactivity timer, a bandwidth part (BWP) inactivity timer, a SCell deactivation timer, a subcarrier spacing (SCS), a periodicity of a search space set corresponding to an assigned monitoring slot (ks), a monitoring duration of a search space set (Ts), or a fixed value.

[0103] Maximum configurable value of PDCCH skipping period value

[0104] The skip period can be limited to a maximum configurable skip period. The maximum configurable skip period can correspond to at least one of a discontinuous reception (DRX) mode on duration timer, a DRX inactivity timer, a bandwidth part (BWP) inactivity timer, a SCell deactivation timer, a subcarrier spacing (SCS), a periodicity of a search space set (ks), a monitoring duration of a search space set (Ts), or a fixed value. For example, a maximum configurable value of a PDCCH skip period can be associated with one of: a drx-onDurationTimer, a drx-InactivityTimer, a bwp-InactivityTimer, a SCellDeactivationTimer, a SCS, a PDCCH monitoring periodicity, a PDCCH monitoring duration, a fixed value, or a UE assistance information.

[0105] In some embodiments, a maximum configurable value of a PDCCH skip period (Max_period) can be associated with a drx-onDurationTimer. For example, Max_period can be less than or equal to the drx-onDurationTimer. In another example, Max_period = A*drx-onDurationTimer, where A is greater than or equal to 1 and less than, for example, 10. In another example, Max_period = drx-onDurationTimer - B, where B is greater than 0 and less than the drx-onDurationTimer. The drx-onDurationTimer is a duration at the beginning of a DRX cycle.

[0106] In some embodiments, the maximum configurable value of PDCCH skipping period (Max_period) can be associated with drx-InactivityTimer. For example, Max_period can be less than drx-InactivityTimer. In another example, Max_period = A * drx-InactivityTimer, where A is greater than 0 and less than 1. In another example, Max_period = drx-InactivityTimer - B, where B is greater than 0 and less than drx-InactivityTimer. drx-InactivityTimer is the duration after a PDCCH occasion in which PDCCH indicates a new UL or DL transmission for the MAC entity.

[0107] In some embodiments, the maximum configurable value of PDCCH skipping period (Max_period) can be associated with bwp-InactivityTimer. For example, Max_period can be less than bwp-InactivityTimer. In another example, Max_period = A * bwp-InactivityTimer, where A is greater than 0 and less than 1. In another example, Max_period = bwp-InactivityTimer - B, where B is greater than 0 and less than bwp-InactivityTimer. bwp-InactivityTimer is the duration in milliseconds after which the UE falls back to the default bandwidth part (BWP). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP.

[0108] In some embodiments, the maximum configurable value of PDCCH skipping period (Max_period) can be associated with SCellDeactivationTimer. For example, Max_period can be less than SCellDeactivationTimer. In another example, Max_period = A * SCellDeactivationTimer, where A is greater than 0 and less than 1. In another example, Max_period = SCellDeactivationTimer - B, where B is greater than 0 and less than SCellDeactivationTimer. If sCellDeactivationTimer expires, the UE will deactivate the SCell.

[0109] In some embodiments, the maximum configurable value of the PDCCH skipping period (Max_period) can be associated with the SCS. Different SCSs can be associated with the same or different Max_period. A larger SCS can not be associated with a smaller Max_period, but rather with the Max_period of a smaller SCS.

[0110] In some embodiments, the maximum configurable value of the PDCCH skipping period (Max_period) can be associated with the PDCCH monitoring periodicity (ks). For example, Max_period = C*ks, where C is greater than or equal to 1 and less than, for example, 50.

[0111] In some embodiments, the maximum configurable value of the PDCCH skipping period (Max_period) can be associated with the PDCCH monitoring duration (Ts). For example, Max_period = C1*Ts, where C1 is greater than or equal to 1 and less than, for example, 50.

[0112] In some embodiments, the maximum configurable value of the PDCCH skipping period (Max_period) is a fixed value M1, where M1 is greater than 0 and less than, for example, 50 (e.g., 10).

[0113] In some embodiments, if the mobile station 102 detects a DCI with a DL assignment, it will trigger the drx-HARQ-RTT-Timer. If the drx-HARQ-RTT-Timer expires and the mobile station 102 does not successfully decode the corresponding PDSCH, the drx-RetransmissionTimer will be triggered. If the drx-RetransmissionTimer expires, the radio access node 104 will send a DCI indicating a retransmission. So as not to impact the reception of the retransmission, in some embodiments, if the scheduling DCI is used to indicate or trigger PDCCH monitoring skipping, the time of the PDCCH skipping period should not be greater than the drx-RetransmissionTimer + drx-HARQ-RTT-Timer.

[0114] PDCCH skipping period configuration

[0115] The one or more PDCCH skipping periods can be configured according to at least one of: higher layer signaling, DCI, a fixed value, K0min, K2min, a duration timer of a discontinuous reception (DRX) mode on, a DRX inactivity timer, or a SCS. In these various embodiments, the PDCCH skipping periods are configured by higher layer signaling (e.g., RRC signaling). In some embodiments, the higher layer signaling includes at least one PDCCH skipping period. In one example, each PDCCH skipping period is used for applying PDCCH monitoring skipping for all search space sets. Table 2 below provides such an example, where A and B are integers greater than or equal to zero units (e.g., slots).

[0116] Index PDCCH skipping period 0 A (e.g., 1) 1 B (e.g., 4)

[0117] Table 2

[0118] In some embodiments, the higher layer configuration signaling includes at least one set of PDCCH skipping periods. Each set of PDCCH skipping periods includes a PDCCH skipping period for each search space set. Table 3 below provides such an example, where Al, A2, A3, Bl, B2, and B3 are integers greater than or equal to zero units (e.g., slots) and less than, for example, 50 units (e.g., slots).

[0119]

[0120] Table 3

[0121] In some embodiments, the PDCCH skipping periods are configured by DCI. For example, a field in the DCI can indicate the PDCCH skipping period configuration. For example, the field in the DCI is set to “1001”, which means the PDCCH skipping period is nine slots. The bit width for this field is determined as log2(Max_period) bits, where Max_period is the maximum configurable value of the PDCCH skipping period.

[0122] In another example, a field in the DCI uses a bitmap to indicate the PDCCH skipping period, where “0” can indicate to monitor PDCCH in the corresponding slot, and where “1” can indicate to not monitor PDCCH in the corresponding slot. In one example, the field in the DCI is set to “1111111100”, which indicates the PDCCH skipping period is eight slots.

[0123] In some embodiments, if the mobile station 102 is configured with K0min or K2min, the PDCCH skip period is implicitly configured according to K0min or K2min. That is, PDCCH skip period = K0min, or PDCCH skip period = K2min. In some embodiments, the PDCCH skip period is a predefined fixed value (e.g., 10). In some embodiments, the PDCCH skip period is configured to be associated with SCS or FR type. The mobile station 102 can be configured with more than one PDCCH skip period candidate, one of the PDCCH skip period is indicated to be applied according to at least one of DCI, MAC CE, or minimum applicable scheduling offset indication.

[0124] In some embodiments, the PDCCH skip period (skip_period) can be associated with the drx-onDurationTimer. For example, the skip_period can be less than or equal to the drx-onDurationTimer. In another example, the skip_period = A*drx-onDurationTimer, where A is greater than or equal to 1 and less than, for example, 10. In another example, the skip_period = drx-onDurationTimer - B, where B is greater than 0 and less than the drx-onDurationTimer.

[0125] In some embodiments, the PDCCH skip period (skip_period) can be associated with the drx-InactivityTimer. For example, the skip_period can be less than the drx-InactivityTimer. In another example, the skip_period = A*drx-InactivityTimer, where A is greater than 0 and less than 1. In another example, the skip_period = drx-InactivityTimer - B, where B is greater than 0 and less than the drx-InactivityTimer.

[0126] In some embodiments, the PDCCH skip period (skip_period) can be associated with SCS. Different SCSs can be associated with the same or different skip_period. A larger SCS can not be associated with a smaller skip_period, but rather be associated with a skip_period with a smaller SCS.

[0127] In various examples, the PDCCH skipping period is configured per BWP, per carrier component (CC), or per UE. In various embodiments, the mobile station 102 sends a desired skipping period to the radio access node 104. The radio access node 104 can determine that the desired skipping period is acceptable and can responsively send a confirmation signal. The mobile station 102 can then receive from the radio access node a description of the skipping period corresponding to the desired skipping period.

[0128] Example cases for PDCCH monitoring skipping

[0129] There can be instances or cases where PDCCH monitoring skipping cannot be applied. Whether the mobile station 102 can apply PDCCH monitoring skipping can be determined in association with or according to predefined information. The predefined information can be at least one of: a DCI format, an RNTI (Radio Network Temporary Identifier), a search space set, a CORESET (Control Resource Set), a UE capability, a TDRA (Time Domain Resource Allocation) table, a higher layer configuration information, a higher layer signaling, a BWP, or a cell identifier (Cell ID).

[0130] The PDCCH monitoring skipping behavior can be specific to each UE, so the PDCCH skipping can be applied at least to a UE-specific DCI format or search space set. The mobile station can be able to perform PDCCH monitoring skipping in at least one of the following cases:

[0131] Monitoring DCI format 0_1 and / or DCI format 1 1,

[0132] Monitoring PDCCH with CRC scrambled with C-RNTI or CS-RNTI or MCS-C-RNTI,

[0133] Monitoring PDCCH in at least USS (UE-specific search space),

[0134] Monitoring PDCCH with DCI scheduling PDSCH when a dedicated TDRA table is applied. The dedicated TDRA table is pdsch-TimeDomainAllocationList configured in pdsch-Config.

[0135] The mobile station 102 can not be able to perform PDCCH monitoring skipping if the DCI or case is for more than one UE (e.g., for all UEs in one cell). The mobile station 102 can not be able to perform PDCCH monitoring skipping in at least one of the following cases:

[0136] Monitoring PDCCH with DCI format 2_0 and / or 2_1 and / or 26,

[0137] monitor PDCCH with DCI format 1_0 with CRC scrambled with P-RNTI or SI-RNTI or RA-RNTI or TC-RNTI or PS-RNTI or SFI-RNTI or INT-RNTI,

[0138] monitor PDCCH in at least one of the following search space sets: type0-PDCCH search space or type0A-PDCCH search space or type1-PDDCH search space or type2-PDCCH search space or type3-PDCCH search space,

[0139] monitor PDCCH scheduling PDSCH when the default TDRA table or the higher layer configured pdsch-TimeDomainAllocationList-ForDCIFormatl_2 is applied,

[0140] monitor PDCCH with DCI format 1_0 with CRC scrambled with C-RNTI or MCS-C-RNTI in the search space provided by recoverySearchSpaceId,

[0141] within a window configured by BeamFailureRecoveryConfig,

[0142] monitor PDCCH in ra-ResponseWindow.

[0143] In some embodiments, the mobile station 102 is configured with K0min and / or K2min indicated to be greater than 0, where the mobile station 102 will continue to monitor PDCCH (PDCCH monitoring skipping is not applied) when PDSCH transmission is scheduled with C-RNTI, CS-RNTI or MCS-C-RNTI in common search space associated with CORESET0 and default PDSCH time domain resource allocation is used, or when PDSCH transmission is scheduled with SI-RNTI or RA-RNTI.

[0144] PDCCH monitoring skipping used in cross-BWP scheduling or cross-carrier scheduling

[0145] In some embodiments, cross-BWP DCI can not indicate or trigger PDCCH monitoring skipping. Cross-BWP DCI refers to DCI indicating data transmission in a BWP that is not the active BWP in the serving cell. That is, DCI with a bandwidth part indicator field used to indicate a change of bandwidth part value. In certain methods, if the cross-BWP DCI has a field used to indicate PDCCH monitoring skipping, the mobile station 102 ignores the field value.

[0146] In some embodiments, the cross-BWP DCI can indicate or trigger PDCCH monitoring skipping. The mobile station 102 can apply the PDCCH monitoring skipping after it completes the BWP switching. In some embodiments, the mobile station 102 can apply the PDCCH monitoring skipping after it receives the PDSCH, after it transmits the PUSCH, and / or after applying a delay.

[0147] If the unit of the application delay (X_delay) is slots, and if the cross-BWP DCI indicates or triggers PDCCH monitoring skipping, and the SCS of the new BWP and the SCS of the old BWP are not the same, then the mobile station 102 can start performing the skipping after X slots, where X is related to the application delay and the SCS. For example,

[0148]

[0149] where μOldBWP is the numerology of the old BWP, and where μNewBWP is the numerology of the new BWP.

[0150] If the unit of the application delay (X_delay) is slots, and if the cross-BWP DCI indicates or triggers PDCCH monitoring skipping, and the SCS of the new BWP and the SCS of the old BWP are not the same, in some embodiments, the application delay follows the SCS before the BWP switching (or the BWP where the DCI is received). In some embodiments, the application delay follows the SCS after the BWP switching (or the BWP where the PDSCH is received or the PUSCH is transmitted). In some embodiments, the application delay is related to the BWP switching delay (e.g., the application delay is equal to the BWP switching delay). In some embodiments, the mobile station 102 does not monitor PDCCH after receiving the PDSCH or transmitting the PUSCH.

[0151] Cross-carrier scheduling occurs when a UE can receive DCI in a scheduling cell and transmit or receive data in a scheduled cell. The scheduling cell and the scheduled cell can be the same cell or different cells. In some embodiments, in cross-carrier scheduling, if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, but the scheduled data is not transmitted or received on the scheduling cell, the mobile station 102 can ignore the field and continue monitoring PDCCH. If the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, and the scheduled data is on the scheduling cell, the mobile station 102 can determine whether to monitor PDCCH on the scheduling cell based on the indication of the field in the DCI.

[0152] In some embodiments, in cross-carrier scheduling, if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, but the scheduled data is on a scheduled cell (which is not the scheduling cell), the mobile station 102 can determine whether to monitor the PDCCH of the scheduled cell on the scheduling cell based on the indication of the field in the DCI. If the UE receives a DCI with a field indicating or triggering PDCCH monitoring skipping, and the scheduled data is on the scheduling cell, the mobile station 102 can determine whether to monitor the PDCCH on the scheduling cell based on the indication of the field in the DCI.

[0153] In some embodiments, in cross-carrier scheduling, if the UE receives a DCI with a field indicating or triggering PDCCH monitoring skipping, but the scheduled data is on a scheduled cell (which is not the scheduling cell), the mobile station 102 can determine whether to monitor the PDCCH of the scheduled cell on the scheduling cell based on the indication of the field in the DCI. If the UE receives a DCI with a field indicating or triggering PDCCH monitoring skipping, but the scheduled data is on the scheduling cell, the mobile station 102 can ignore the field and continue to monitor the PDCCH.

[0154] In some embodiments, in cross-carrier scheduling, if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, the mobile station 102 can determine whether to monitor the PDCCH on the scheduling cell based on the indication of the field in the DCI.

[0155] In some embodiments, in cross-carrier scheduling, the unit of the applied delay (X_delay) is slots, and if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, in some embodiments, the mobile station 102 can start to perform the skipping after X slots, where X is related to the applied delay and the SCS. For example,

[0156]

[0157] where μScheduledis the numerology of the scheduled cell, and μSchedulingis the numerology of the scheduling cell.

[0158] In some embodiments, in cross-carrier scheduling, where the unit of the applied delay (X_delay) is slots, and if the mobile station receives a DCI with a field indicating or triggering PDCCH monitoring skipping. In some embodiments, the applied delay follows the SCS of the scheduling cell. In some embodiments, the applied delay follows the SCS of the scheduled cell.

[0159] In some embodiments, in cross-carrier scheduling, if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, the application delay can be related to at least one of the following: delta, fixed value, K0min, or Zμ. In this example, the unit can be in milliseconds or slots.

[0160] For the case that the search space of the scheduling cell and the scheduled cell are the same search space, if the mobile station 102 receives a DCI with a field indicating or triggering PDCCH monitoring skipping, in some embodiments, the mobile station 102 determines whether to monitor PDCCH on the scheduling cell based on the indication of the field in the DCI. In some embodiments, the mobile station 102 ignores the field.

[0161] Other settings

[0162] In some embodiments, if the mobile station 102 is triggered to perform PDCCH monitoring skipping, the mobile station 102 does not monitor PDCCH for all PDCCH monitoring durations within the PDCCH skipping period. That is, if a part of the PDCCH monitoring duration is outside the PDCCH skipping period, the mobile station 102 will continue to monitor PDCCH within the PDCCH monitoring duration.

[0163] In some embodiments, if a PDCCH monitoring occasion for DCI format 2_0 is within the PDCCH skipping period, it will be considered by the UE as no detection of DCI format 2_0 at that PDCCH monitoring occasion.

[0164] In some embodiments, if the PDCCH monitoring occasion(s) is / are within the PDCCH skipping period, the PDCCH monitoring occasion(s) will be set as invalid PDCCH monitoring occasion(s). And the mobile station will not monitor PDCCH in the invalid PDCCH monitoring occasion(s).

[0165] In various embodiments, as Figure 1As shown in FIG. 1, the mobile station 102 includes a processor 110 and a memory 112, where the processor 110 is configured to read computer code from the memory 112 to implement any of the above-disclosed methods and embodiments related to operation of the mobile station 102. Similarly, the wireless access node 104 includes a processor 120 and a memory 122, where the processor 120 is configured to read computer code from the memory 122 to implement any of the above-disclosed methods and embodiments related to operation of the wireless access node 104. Additionally, in various embodiments, a computer program product includes a non-transitory computer-readable program medium (e.g., the memory 112 or 122) having computer code stored thereon. The computer code, when executed by a processor (e.g., the processor 110 or 120), causes the processor to implement a method corresponding to any of the above-disclosed embodiments.

[0166] According to the various methods and embodiments disclosed above, various technical advantages are realized. Primarily, additional power savings are achieved by reducing the amount of time required for the mobile station 102 to monitor the PDCCH.

[0167] The above description and drawings provide specific examples of particular embodiments and implementations. However, the described subject matter can be embodied in various different forms and, therefore, the

[0168] The described subject matter is intended to be illustrative, and not restrictive, of the scope of the claimed subject matter. The subject matter is therefore not limited to the specific embodiments and implementations described herein. Rather, the scope of the subject matter is to be determined solely by the appended claims, along with the full scope of equivalents to which such claims are entitled. Among other things, the subject matter can be embodied as methods, devices, components, systems, or non-transitory computer-readable media for storing computer code. Accordingly, embodiments can be embodied as hardware, software, firmware, storage media, or any combination thereof. For example, the above-described method embodiments can be implemented by a component, device, or system including a memory and a processor, executing computer code stored in the memory.

[0169] Throughout the specification and claims, the term "may" can convey the possible alternatives, as opposed to mandating such alternatives, in the context of recitations. Also, the use of the phrase "in one embodiment / implementation" does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" does not necessarily refer to a different embodiment. For example, it is intended that the claimed subject matter include combinations of all or portions of the example embodiments.

[0170] Generally, terminology can be understood at least in part from an understanding of how various terminology is conventionally and / or historically used in the relevant art. For example, terms such as "and", "or", or "and / or" as used herein can include a variety of meanings that can depend at least in part upon the context in which such terms are used. Typically, "or" if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term "one or more" as used herein can be used to describe any feature, structure, or characteristic in the singular or can be used to describe combinations of features, structures or characteristics. Similarly, terms such as "a", "an", or "the" again are understood to convey a singular usage or are understood to convey a plural usage, at least depending on the context in which such terms are used. Additionally, the term "based on" can be understood as not necessarily intended to convey an exclusive set of factors, but rather can allow for additional factors to be present, again, depending on the context in which the term is used.

[0171] Reference throughout this specification to features, advantages, or similar language does not mean that all of the features and advantages that can be achieved in accordance with the present solutions should be or are in any single embodiment of the application. Rather, languages

[0172] Further, the described features, advantages, and characteristics of the present solutions can be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize, in light of the description herein, that the solutions can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages can be recognized in certain embodiments that can not be present in all embodiments of the solutions.

Claims

1. A method performed by a mobile station, the method comprising: The mobile station receives predefined signaling and higher-layer signaling from the radio access node, wherein the higher-layer signaling configures at least one physical downlink control channel (PDCCH) skip period; The mobile station determines whether to perform PDCCH monitoring skipping based on the predefined signaling, wherein the predefined signaling indicates the PDCCH skipping period to be used during the at least one PDCCH skipping period; as well as One time slot after receiving the predefined signaling, the PDCCH monitoring skip is performed; The PDCCH monitoring skip is not performed in the random access response window; as well as The PDCCH monitoring skipping is stopped in response to one or more of the following: Bandwidth portion (BWP) switching based on timers, or The mobile station enters DRX idle mode.

2. The method according to claim 1, The predefined signaling includes downlink control information (DCI), which includes an indication that the mobile station should perform the PDCCH monitoring skip.

3. The method according to claim 2, The indicated information is included in the DCI, which has an information field, the information field including: At least one of the following: the index of the PDCCH skipping period or the description of the duration of a first number of time slots of the PDCCH skipping period.

4. The method according to claim 1, The predefined signaling includes: At least one of the following: Bandwidth Part (BWP), Maximum MIMO Layer, Frequency Range (FR) Type, Mobile Station Type, Higher Layer Signaling, or Mobile Station Capability.

5. The method according to claim 1, further comprising: After skipping monitoring of the PDCCH during the PDCCH skipping period: The monitoring of the PDCCH is resumed by the mobile station during the monitoring period of the second number of time slots; and Repeat the skip and monitoring loop.

6. The method according to claim 1, further comprising: The mobile station receives at least one of the following: downlink (DL) allocation, uplink (UL) grant, PDCCH indicating a previously presented transmission, media access control (MAC) control element (CE) indicating to stop PDCCH monitoring skipping, or radio resource control (RRC) signaling configuring parameters for PDCCH skipping. as well as The PDCCH monitoring is terminated in response.

7. The method according to claim 1, The PDCCH skip period corresponds to at least one of the period of the search space set or the default number of time slots.

8. The method according to claim 1, The PDCCH monitoring skipping mentioned above also includes: Before initiating the skipping of the PDCCH monitoring skip within the PDCCH skipping period, an application delay is waited for, which includes a second number of time slots after the occurrence of the skip triggering event.

9. The method according to claim 8, The occurrence of the skip trigger event includes the expiration of a timer.

10. The method according to claim 8, The application latency is determined based on at least one of the following: Application latency of minimum scheduling offset limit Minimum applicable scheduling offset Subcarrier spacing (SCS), Frequency Range (FR) type, The value associated with SCS (Z) μ ), K0， K2， Physical Downlink Shared Channel (PDSCH) processing time. Bandwidth component (BWP), The PDCCH skipping period. Radio Resource Control (RRC) signals, or Fixed value.

11. The method according to claim 1, The PDCCH skip period is subject to a maximum configurable skip period, which corresponds to at least one of the following: Discontinuous Receive (DRX) mode enable duration timer, DRX inactivity timer, Bandwidth Part (BWP) inactivity timer, SCell deactivation timer, subcarrier spacing (SCS), search space set period (ks), search space set monitoring duration (Ts), or a fixed value.

12. The method according to claim 1, further comprising: The mobile station sends the desired skip period to the wireless access node; as well as The mobile station receives from the radio access node a description of the PDCCH skip period corresponding to the desired skip period.

13. The method according to claim 1, wherein, If the mobile station is in a PDCCH skipping period and is not monitoring the PDCCH, then in response to the timer-based BWP handover, the mobile station begins monitoring the PDCCH.

14. A method for communication between a wireless access node and a mobile station, the method comprising: The radio access node determines higher-layer signaling and predefined signaling, wherein the higher-layer signaling configures at least one physical downlink control channel (PDCCH) skip period, and wherein the predefined signaling indicates a PDCCH skip period within the at least one PDCCH skip period; as well as The radio access node sends the predefined signaling and the higher-layer signaling to the mobile station, wherein the mobile station is configured to perform PDCCH monitoring skipping one time slot after receiving the predefined signaling, wherein the mobile station is configured not to perform the PDCCH monitoring skipping within the random access response window, and wherein the mobile station is configured to stop the PDCCH monitoring skipping in response to one or more of the following: Bandwidth portion (BWP) switching based on timers, or The mobile station enters DRX idle mode.

15. The method according to claim 14, The indication information in the predefined signaling is included in the downlink control information (DCI) with an information field, which includes: At least one of the following: the index of the PDCCH skipping period or the description of the duration of a first number of time slots of the PDCCH skipping period.

16. The method according to claim 14, The predefined signaling includes at least one of the following: Bandwidth Part (BWP), Maximum MIMO Layer, Frequency Range (FR) Type, or Mobile Station Type, Higher Layer Signaling, or Mobile Station Capability.

17. The method of claim 14, further comprising: The timer value is determined by the wireless access node, and the expiration of the timer value triggers the mobile station to perform the PDCCH monitoring skip. as well as The timer value is sent from the wireless access node to the mobile station.

18. The method according to claim 14, The PDCCH skip period is subject to a maximum configurable skip period, which corresponds to at least one of the following: Discontinuous Receive (DRX) mode enable duration timer, DRX inactivity timer, Bandwidth Part (BWP) inactivity timer, SCell deactivation timer, subcarrier spacing (SCS), period (ks) of the search space set corresponding to the assigned monitoring slot, monitoring duration (Ts) of the search space set, or a fixed value.

19. A mobile station comprising a processor and a memory, wherein the processor is configured to read computer code from the memory to implement the method of any one of claims 1 to 13.

20. A wireless access node comprising a processor and a memory, wherein the processor is configured to read computer code from the memory to implement the method of any one of claims 14 to 18.

21. A computer-readable storage medium having stored thereon computer instructions that, when executed, cause the method of any one of claims 1 to 18 to be performed.

Images