Patent Description:
Discontinuous reception (DRX) is designed to reduce power consumption by allowing a communication device to discontinuously receive information from another communication device. For example, when the DRX is enabled, user equipment (UE) may be configured with one or more DRX cycles, each comprising a DRX on-duration for monitoring a downlink control channel from a network device. As such, the UE only needs to discontinuously monitor the downlink channel. Otherwise, the UE needs to continuously monitor the downlink channel. 3GPP drafts R1-<NUM>, R1-<NUM>, and R1-<NUM> discuss Physical Downlink Control Channel (PDCCH) based power saving, and PDCCH based skipping and switching of PDCCH monitoring periodicity.

Wake up signaling (WUS) is designed to allow the UE to skip monitoring the downlink channel when there is no transmission to be done, such that the power consumption can be further reduced. For example, if the network device intends to schedule the UE, it needs to send WUS to the UE during one or more WUS occasions so as to wake up the UE first. The UE will then monitor the control channel for scheduling information during a coming DRX on-duration. Further, the PDCCH skipping has been proposed in order to save UE power. The network devices may indicate the UE to skip a number of PDCCH monitoring occasions.

In general, example embodiments of the present disclosure provide a solution for handling PDCCH skipping and wake up signaling.

In a first aspect, there is provided a first device according to claim <NUM>.

In a second aspect, there is provided a second device according to claim <NUM>.

In a third aspect, there is provided a method according to claim <NUM>.

In a fourth aspect, there is provided a method according to claim <NUM>.

In a fifth aspect, there is provided a computer-readable storage medium according to claim <NUM>.

In a sixth aspect, there is provided a computer-readable storage medium according to claim <NUM>.

Further aspects are provided by the dependent claims.

Further, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

As used herein, the term "communication network" refers to a network following any suitable communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), New Radio (NR) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (<NUM>), the second generation (<NUM>), <NUM>, <NUM>, the third generation (<NUM>), the fourth generation (<NUM>), <NUM>, the future fifth generation (<NUM>) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

Although functionalities described herein can be performed, in various example embodiments, in a fixed and/or a wireless network node may, in other example embodiments, functionalities may be implemented in a user equipment apparatus (such as a cell phone or tablet computer or laptop computer or desktop computer or mobile IOT device or fixed IOT device). This user equipment apparatus can, for example, be furnished with corresponding capabilities as described in connection with the fixed and/or the wireless network node(s), as appropriate. The user equipment apparatus may be the user equipment and/or or a control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functionalities include the bootstrapping server function and/or the home subscriber server, which may be implemented in the user equipment apparatus by providing the user equipment apparatus with software configured to cause the user equipment apparatus to perform from the point of view of these functions/nodes.

<FIG> illustrates a schematic diagram of a communication system <NUM> in which embodiments of the present disclosure can be implemented. The communication system <NUM>, which is a part of a communication network, comprises devices <NUM>-<NUM>, <NUM>-<NUM>,. , <NUM>-N (collectively referred to as "device(s) <NUM>" where N is an integer number). The communication system <NUM> comprises one or more devices, for example, a device <NUM>. It should be understood that the communication system <NUM> may also comprise other elements which are omitted for the purpose of clarity. It is to be understood that the numbers of devices in <FIG> are given for the purpose of illustration without suggesting any limitations. The device <NUM> may communicate with the device <NUM>.

Communications in the communication system <NUM> may be implemented according to any proper communication protocol(s), including, but not limited to, cellular communication protocols of the first generation (<NUM>), the second generation (<NUM>), the third generation (<NUM>), the fourth generation (<NUM>) and the fifth generation (<NUM>) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) <NUM> and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, including but not limited to: Code Divided Multiple Address (CDMA), Frequency Divided Multiple Address (FDMA), Time Divided Multiple Address (TDMA), Frequency Divided Duplexer (FDD), Time Divided Duplexer (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.

In the communication network <NUM>, the device <NUM> and the device <NUM> can communicate data and control information to each other. In the case that the device <NUM> is the terminal device and the device <NUM> is the network device, a link from the device <NUM> to the device <NUM> is referred to as a downlink (DL), while a link from the device <NUM> to the device <NUM> is referred to as an uplink (UL).

The device <NUM> and the device <NUM> may be configured with discontinuous communication for the purpose of power saving. The discontinuous communication may include discontinuous reception (DRX) and/or discontinuous transmission (DTX). Either or both of the device <NUM> and device120 can be configured with DRX and/or DTX. For example, when the DRX is configured, the first device <NUM> discontinuously monitors information/data (for example, downlink information/data) transmitted from the device <NUM>. When the DTX is configured, the first device <NUM> discontinuously transmits information/data (for example, uplink information/data) to the device <NUM>. Similarly, the device <NUM> may also be possibly configured with DRX or DTX.

When DRX is configured, to receive data, a device (for example, the first device <NUM>) may first awake to monitor control information which indicates whether the device is scheduled to receive data and how the data can be received. A DRX cycle specifies the periodic repetition of the DRX on-duration followed by a possible period of inactivity. The DRX cycle includes an on-duration (also referred to "DRX on-duration") and an off-duration (also referred to "DRX off-duration"). The DRX on-duration is an active time during which a device (for example, the device <NUM>) monitors transmissions from a further device (for example, the device <NUM>) within a DRX cycle. The information may include control information transmitted via a physical downlink control channel (PDCCH).

To further reduce the power consumption, in some example embodiments, a device (for example, the device <NUM>) configured with DRX may be also configured with one or more WUS occasions for monitoring WUS from a further device (for example, the device <NUM>). If WUS is detected on at least one WUS occasion to wake up the UE, the device may monitor transmissions from the further device during a DRX on-duration following the at least one WUS occasion. However, if no WUS is detected or WUS indicating not to wake up is received, the device may not monitor transmissions from the further device during a coming DRX on-duration. As such, the power consumption can be further reduced.

As discussed above, technologies of WUS and PDCCH skipping have been proposed to save power. With PDCCH skipping, downlink control information is used to indicate the UE to skip PDCCH monitoring for certain period. With DRX, the UE is configured with DRX cycles that keeps the UE awake periodically during OnDuration in case there is some data transmission needed, and the active time can be extended by scheduling the UE with inactivity timer when there is data transmission ongoing. While with WUS, WUS occasion(s) can be configured before each OnDuration with a certain offset and the UE only monitors the n OnDuration if there is a WUS indicates the UE to monitor.

However, it is possible that the WUS and the PDCCH skipping may be configured at the same time. The potential impacts on the WUS and the PDCCH skipping are not discussed. In this case, how to handle WUS occasions during the PDCCH skipping needs to be specified.

According to example embodiments of the present disclosure, there is provided a solution for handling WUS occasions and the PDCCH skipping. In this solution, the device may determine whether to skip monitoring the PDCCH and determine whether to skip monitoring the WUS based on the type of PDCCH. The device may also determine when to transmit the WUS based on the type of the PDCCH. In this way, the WUS and the PDCCH skipping can be configured simultaneously and the power can be further saved.

Reference is now made to <FIG>, which illustrates a flowchart of an example method <NUM> in accordance with some example embodiments of the present disclosure. The method <NUM> will be described from the perspective of the device <NUM> with reference to <FIG>. It would be appreciated that the method <NUM> may also be implemented at the device <NUM> in <FIG>. Only for the purpose of illustrations, the method <NUM> is described to be implemented at the device <NUM>-<NUM>.

At block <NUM>, the device <NUM>-<NUM> receives first information from the device <NUM>. The first information indicates that one or more target occasions for monitoring the PDCCH which can be skipped by the device <NUM>-<NUM>. <FIG> illustrates an example diagram of PDCCH skipping. As shown in <FIG>, the monitoring occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> can be used for monitoring the PDCCH. The first information may indicate that the candidate monitoring occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> may be skipped. It should be noted that the number of monitoring occasions shown in <FIG> is only as an example, not a limitation.

At block <NUM>, the device <NUM>-<NUM> determines a target occasion from the candidate occasions based on second information about a PDCCH which is applicable to skipping monitoring. In some embodiments, the second information may be received from the device <NUM> on radio resource signaling. Alternatively or in addition, the second information may be transmitted in a medium access control (MAC) control element from the device <NUM>. In a further embodiment, the second information may be pre-defined. In some embodiments, the second information may also be transmitted in the first information from the device <NUM>. In this way, the PDCCH skipping and the WUS are able to be configured at the same time, thereby saving power of the terminal device.

In some embodiments, the second information may indicate that the PDCCH skipping is applicable to a PDCCH which is addressed to a cell radio network temporary identifier (C-RNTI) for DL assignment or UL grant. Alternatively, the second information may indicate that the PDCCH skipping is applicable to a PDCCH which is addressed to a configured scheduling radio network temporary identifier (CS-RNTI) for DL assignment. For example, if the monitoring occasion <NUM>-<NUM> is not for monitoring the PDCCH which is addressed to the C-RNTI, the device <NUM>-<NUM> may not select the monitoring occasion <NUM>-<NUM> to be the target monitoring occasion, which means the device <NUM>-<NUM> may monitor the PDCCH on the monitoring occasion <NUM>-<NUM>. If the monitoring occasion <NUM>-<NUM> is for monitoring the PDCCH which is addressed to the C-RNTI, the device <NUM>-<NUM> may select the monitoring occasion <NUM>-<NUM> to be the target monitoring occasion, which means the device <NUM>-<NUM> may skip monitoring the PDCCH on the monitoring occasion <NUM>-<NUM>.

Alternatively, the second information indicates that the PDCCH skipping is applicable to a PDCCH with a specific downlink control information (DCI) format, e.g. the DCI format for DL assignment or UL grant. For example, if the monitoring occasion <NUM>-<NUM> is for monitoring the PDCCH with the DCI format, the device <NUM>-<NUM> selects the monitoring occasion <NUM>-<NUM> to be the target monitoring occasion, which means the device <NUM>-<NUM> skips monitoring the PDCCH on the monitoring occasion <NUM>-<NUM>.

In a further embodiment, the second information indicates that the PDCCH skipping is applicable to a PDCCH without the DCI for WUS, which means the PDCCH skipping does not apply to the WUS occasions. For example, if the monitoring occasion <NUM>-<NUM> is used for monitoring the DCI for WUS, the device <NUM>-<NUM> does not select the monitoring occasion <NUM>-<NUM> to be the target monitoring occasion, which means the device <NUM>-<NUM> monitors the PDCCH on the monitoring occasion <NUM>-<NUM>. If the monitoring occasion <NUM>-<NUM> is used for monitoring the PDCCH without the DCI for WUS, the device <NUM>-<NUM> selects the monitoring occasion <NUM>-<NUM> to be the target monitoring occasion, which means the device <NUM>-<NUM> skips monitoring the PDCCH on the monitoring occasion <NUM>-<NUM>.

In another embodiments, the second information may indicate that the PDCCH skipping is applicable to all PDCCHs. That is to say, all the candidate monitoring occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> indicated in the first information may be selected to be the target occasions. Alternatively, the skip command may indicate to which PDCCH the command is applicable.

At block <NUM>, the device <NUM>-<NUM> skips monitoring the WUS if the period for monitoring the WUS overlaps with the target monitoring occasion for the PDCCH. <FIG> illustrates an example diagram of WUS monitoring. <FIG> shows three DRX cycles <NUM>, <NUM> and <NUM>. For example, the DRX cycle <NUM> comprises a DRX on-duration <NUM>. The DRX cycle <NUM> comprises a DRX on-duration <NUM>. The DRX cycle <NUM> comprises a DRX on-duration <NUM>. <FIG> also show a plurality of durations <NUM>, <NUM> and <NUM> for monitoring WUS. For example, as shown in <FIG>, the WUS durations before the DRX on-duration <NUM> comprise three occasions. The WUS duration <NUM> before the DRX on-duration <NUM> comprise three occasions. The WUS duration <NUM> before the DRX on-duration <NUM> comprise three occasions. It would be appreciated that the number of the WUS occasions before each DRX on-duration is shown only for the purpose of illustration, without suggesting any limitation to the present disclosure. In some embodiments, there may be only one WUS occasion before each DRX on-duration. Alternatively, or in addition, in some embodiments, the numbers of WUS occasions before different DRX on-durations may be different.

In some embodiment, for example, since the monitoring occasion <NUM>-<NUM> is not for monitoring the PDCCH which is addressed to the C-RNTI, the device <NUM>-<NUM> may monitor the PDCCH on the monitoring occasion <NUM>-<NUM>. As shown in <FIG>, the device <NUM>-<NUM> may monitor the WUS on the WUS duration <NUM>. In some embodiments, for example, since the monitoring occasion <NUM>-<NUM> is used for monitoring the DCI for WUS, the device <NUM>-<NUM> may monitor the PDCCH on the monitoring occasion <NUM>-<NUM>. As shown in <FIG>, the device <NUM>-<NUM> may monitor the WUS on the WUS duration <NUM>.

Only for the purpose of illustrations, if the monitoring occasions <NUM>-<NUM> and <NUM>-<NUM> are selected to be the target monitoring occasions, the device <NUM>-<NUM> may skip monitoring the PDCCH on the monitoring occasions <NUM>-<NUM> and <NUM>-<NUM>. As shown in <FIG>, the WUS duration <NUM> overlap with the monitoring occasions <NUM>-<NUM> and <NUM>-<NUM>. In this situation, the device <NUM>-<NUM> may skip monitoring the WUS on the WUS duration <NUM>. For the following OnDuration <NUM> where the device <NUM>-<NUM> misses the WUS occasions, the device <NUM>-<NUM> does not monitor PDCCH as if no WUS is received. In some embodiments, if all the monitoring occasions are determined to be the target monitoring occasions, the device <NUM>-<NUM> may skip the WUS durations <NUM>, <NUM> and <NUM>.

In some embodiments, the device <NUM>-<NUM> may receive a skipping indication as to whether the device <NUM>-<NUM> monitors the WUS and/or the PDCCH after the skip period. If the skipping indication indicates the device <NUM>-<NUM> to monitor the WUS and/or the PDCCH, the device <NUM>-<NUM> may perform the monitoring. If the skipping indication indicates the device <NUM>-<NUM> not to monitor the WUS and/or the PDCCH, the device <NUM>-<NUM> may skip the monitoring. In other embodiments, the device <NUM>-<NUM> may receive a skipping indication as to whether the device <NUM>-<NUM> monitors the WUS and/or the PDCCH during the skip period. If the skipping indication indicates the device <NUM>-<NUM> to monitor the WUS and/or the PDCCH, the device <NUM>-<NUM> may perform the monitoring. If the skipping indication indicates the device <NUM>-<NUM> not to monitor the WUS and/or the PDCCH, the device <NUM>-<NUM> may skip the monitoring.

<FIG> illustrates a flowchart of an example method <NUM> in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the device <NUM> with reference to <FIG>. It would be appreciated that the method <NUM> may also be implemented at the device <NUM> in <FIG>.

At block <NUM>, the device <NUM> transmits first information to the device <NUM>-<NUM>. The first information indicates that one or more target occasions for monitoring the PDCCH which can be skipped by the device <NUM>-<NUM>. As shown in <FIG>, the monitoring occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> can be used for monitoring the PDCCH. The first information may indicate that the candidate monitoring occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> may be skipped. It should be noted that the number of monitoring occasions shown in <FIG> is only as an example, not a limitation.

At block <NUM>, the device <NUM> determines a target duration for transmitting the WUS based on second information about a PDCCH which is applicable to skipping monitoring. In this way, the device <NUM> may be able to avoid transmitting the WUS on the occasions which may be skipped.

In some embodiments, the second information may indicate that the PDCCH skipping is applicable to a PDCCH which is addressed to a cell radio network temporary identifier (C-RNTI) for UL grant. Alternatively, the second information may indicate that the PDCCH skipping is applicable to a PDCCH which is addressed to a configured scheduling radio network temporary identifier (CS-RNTI) for DL assignment. For example, if the monitoring occasion <NUM>-<NUM> is not for monitoring the PDCCH which is addressed to the C-RNTI, the device <NUM> may select the duration <NUM> for transmitting the WUS which may overlap with the monitoring occasion <NUM>-<NUM>. If the monitoring occasion <NUM>-<NUM> is for monitoring the PDCCH which is addressed to the C-RNTI, the device <NUM> may transmit the WUS on the duration which does not overlap with the monitoring occasion <NUM>-<NUM>.

Alternatively, the second information may indicate that the PDCCH skipping is applicable to a PDCCH with a specific downlink control information (DCI) format, e.g. the DCI format for DL assignment or UL grant. For example, if the monitoring occasion <NUM>-<NUM> is for monitoring the PDCCH with the DCI format, the device <NUM>-<NUM> may select the duration which is not overlapping with the monitoring occasion <NUM>-<NUM>.

In a further embodiment, the second information may indicate that the PDCCH skipping is applicable to a PDCCH without the DCI for WUS. For example, if the monitoring occasion <NUM>-<NUM> is used for monitoring the DCI for WUS, the device <NUM> may select the duration for transmitting the WUS which may overlap with the monitoring occasion <NUM>-<NUM>.

In another embodiments, the second information may indicate that the PDCCH skipping is applicable to all PDCCHs. The device <NUM> may transmit the WUS on the duration which does not overlap with any of the monitoring occasions shown in <FIG>.

In some embodiments, the second information may be received from the device <NUM> on radio resource signaling. Alternatively or in addition, the second information may be transmitted in a medium access control (MAC) control element from the device <NUM>. In a further embodiment, the second information may be pre-defined. In some embodiments, the second information may also be transmitted in the first information from the device <NUM>.

At block <NUM>, the device <NUM> may transmit the WUSP on the determined duration. In some embodiments, the device <NUM> may generate a skipping indication as to whether the device <NUM>-<NUM> monitors the WUS and/or the PDCCH after the period on which the PDCCH monitoring is skipped. In other embodiments, the device <NUM> may generate a skipping indication as to whether the device <NUM>-<NUM> monitors the WUS and/or the PDCCH during the period on which the PDCCH monitoring is skipped. The device <NUM> may transmit the skipping indication to the device.

In some example embodiments, an apparatus capable of performing the method <NUM> (for example, the device <NUM> or the device <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the apparatus comprises means for receiving, at a first device and from a second device, first information indicating that candidate occasions are to be skipped for monitoring physical downlink control channel; means for determining a target occasion from the candidate occasions based on second information about a physical downlink control channel which is applicable to skipping monitoring; and means for in response to the target occasion overlapping with a duration for monitoring wake up signaling, skipping monitoring the wake up signaling on the period.

In some example embodiments, the means for determining the target occasion comprises: means for in response to the second information indicating a physical downlink control channel which is addressed to a cell radio network temporary identifier is applicable to skipping monitoring, determining, as the target occasion, one of the candidate occasions addressed to the cell radio network temporary identifier.

In some example embodiments, the means for determining the target occasion comprises means for in response to the second information indicating a physical downlink control channel with a downlink control information format for scheduling downlink assignment or uplink grant is applicable to skipping monitoring, determining, as the target occasion, one of the candidate occasions with the downlink control information format for scheduling downlink assignment or uplink grant.

In some example embodiments, the means for determining the target occasion comprises: means for in response to the second information indicating downlink control information for the wake up signaling is inapplicable to skipping monitoring, determining, as the target occasion, one of the candidate occasions without the downlink control information for the wake up signaling.

In some example embodiments, the means for determining the target occasion comprises: means for in response to the second information indicating all the physical downlink control channels are applicable to skipping monitoring, determining all the candidate occasions to be the target occasion.

In some example embodiments, the apparatus further comprises: means for receiving the second information via at least one of radio resource control signaling and a MAC control element.

In some example embodiments, the second information is pre-defined.

In some example embodiments, the apparatus further comprises means for receiving a skipping indication as to whether the first device monitors at least one of the wake up signaling and the physical downlink control channel after the duration; and means for monitoring, based on the skipping indication, the at least one of the wake up signaling and the physical downlink control channel after the duration.

In some example embodiments, the apparatus further comprises means for receiving a skipping indication as to whether the first device monitors at least one of the wake up signaling and the physical downlink control channel in the duration; and means for monitoring, based on the skipping indication, the at least one of the wake up signaling and the physical downlink control channel in the duration.

In some example embodiments, the apparatus further comprises wherein the first device is a terminal device and the second device is a network device.

In some example embodiments, the apparatus comprises means for transmitting, to a first device, first information indicating that candidate occasions are to be skipped for monitoring physical downlink control channel; means for determining a target duration for transmitting a wake up signaling based on second information about a physical downlink control channel which is applicable to skipping monitoring; and means for transmitting the wake up signaling on the target duration.

In some example embodiments, the means for determining the target duration comprises: means for in response to the second information indicating a physical downlink control channel which is addressed to a cell radio network temporary identifier is applicable to skipping monitoring, determining a duration which is non-overlapping with the candidate occasions addressed to the cell radio network temporary identifier to be the target duration.

In some example embodiments, the means for determining the target duration comprises means for in response to the second information indicating a physical downlink control channel with a downlink control information format for scheduling downlink assignment or uplink grant is applicable to skipping monitoring, determining a duration which is non-overlapping with the candidate occasions with the downlink control information format to be the target duration.

In some example embodiments, the means for determining the target duration comprises: means for in response to the second information indicating downlink control information for the wake up signaling is inapplicable to skipping monitoring, determining a duration with the downlink control information to be the target duration.

In some example embodiments, the means for determining the target duration comprises: means for in response to the second information indicating all the physical downlink control channels are applicable to skipping monitoring, determining a duration which is non-overlapping with all the candidate occasions to be the target duration.

In some example embodiments, the apparatus further comprises means for transmitting the second information via at least one of radio resource control signaling and a MAC control element.

In some example embodiments, the apparatus further comprises: means for generating a skipping indication as to whether the first device monitors at least one of the wake up signaling and the physical downlink control channel after a period which is skipped for monitoring the physical downlink control channel; and means for transmitting the skipping indication to the first device.

In some example embodiments, the apparatus further comprises: means for generating a skipping indication as to whether the first device monitors at least one of the wake up signaling and the physical downlink control channel during a period which is skipped for monitoring the physical downlink control channel; and means for transmitting the skipping indication to the first device.

In some example embodiments, the first device is a terminal device and the second device is a network device.

<FIG> is a simplified block diagram of a device <NUM> that is suitable for implementing embodiments of the present disclosure. The device <NUM> may be provided to implement the communication device, for example the device <NUM>, or the device <NUM> as shown in <FIG>. As shown, the device <NUM> includes one or more processors <NUM>, one or more memories <NUM> coupled to the processor <NUM>, and one or more communication modules <NUM> coupled to the processor <NUM>.

The embodiments of the present disclosure may be implemented by means of the program <NUM> so that the device <NUM> may perform any process of the disclosure as discussed with reference to <FIG> and <FIG>.

It should be appreciated that future networks may utilize network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean node operations to be carried out, at least partly, in a central/centralized unit, CU, (e.g. server, host or node) operationally coupled to distributed unit, DU, (e.g. a radio head/node). It should also be understood that the distribution of labour between core network operations and base station operations may vary depending on implementation.

In an embodiment, the server may generate a virtual network through which the server communicates with the distributed unit. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head/node. In practice, any digital signal processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.

Therefore, in an embodiment, a CU-DU architecture is implemented. In such case the apparatus <NUM> may be comprised in a central unit (e.g. a control unit, an edge cloud server, a server) operatively coupled (e.g. via a wireless or wired network) to a distributed unit (e.g. a remote radio head/node). That is, the central unit (e.g. an edge cloud server) and the distributed unit may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection. Alternatively, they may be in a same entity communicating via a wired connection, etc. The edge cloud or edge cloud server may serve a plurality of distributed units or a radio access networks. In an embodiment, at least some of the described processes may be performed by the central unit. In another embodiment, the apparatus <NUM> may be instead comprised in the distributed unit, and at least some of the described processes may be performed by the distributed unit.

In an embodiment, the execution of at least some of the functionalities of the apparatus <NUM> may be shared between two physically separate devices (DU and CU) forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes. In an embodiment, such CU-DU architecture may provide flexible distribution of operations between the CU and the DU. In practice, any digital signal processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation. In an embodiment, the apparatus <NUM> controls the execution of the processes, regardless of the location of the apparatus and regardless of where the processes/functions are carried out.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method <NUM> as described above with reference to <FIG>. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Claim 1:
A first device comprising:
means for receiving (<NUM>), at the first device and from a second device, first information indicating that candidate occasions are to be skipped for monitoring physical downlink control channel;
means for determining (<NUM>) a target occasion from the candidate occasions based on second information indicating that skipping monitoring is applicable to a physical downlink control channel with a downlink control information format for scheduling downlink assignment or uplink grant, wherein the skipping monitoring does not apply to wake up signaling occasions; and
wherein the first device is configured to skip monitoring the physical downlink control channel on the target occasion.