Patent Description:
With development of communication systems, more and more technologies have been proposed. The technology named "wake up signal (WUS)" is under discussion in the power saving work item and discontinuous reception (DRX) has been supported for power saving. WUS is designed to allow the terminal device to skip physical downlink control channel (PDCCH) monitoring for OnDurations when there is no data transmission to be done. If the network device intends to schedule the terminal device, it needs to send wake up signalling to the terminal device during the WUS occasion(s) to wake up the terminal device first, the terminal device will then monitor normal PDCCH for scheduling data at the coming OnDuration. Documents <NPL>, and <NPL>, discuss wake up signaling.

Generally, embodiments of the present disclosure relate to a method for uplink information based on wake-up signals and corresponding devices.

According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. The embodiments that do not fall under the scope of the claims are to be interpreted as examples useful for understanding the disclosure.

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, Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

As discussed above, the WUS is designed to allow the terminal device to skip physical downlink control channel (PDCCH) monitoring for OnDurations when there is no data transmission to be done. If the network device intends to schedule the terminal device, it needs to send wake up signalling to the terminal device during the WUS occasion(s) to wake up the terminal device first, the terminal device will then monitor normal PDCCH for scheduling data at the coming OnDuration. WUS is called DCP (downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by power saving radio network temporary identity (PS-RNTI)) in the third generation partnership project (3GPP). The network device can configure if the terminal device sends periodic channel state information (CSI) feedback and/or L1-reference signal received power (RSRP) feedback even in case drx-onDurationTimer is not started by the WUS/DCP, for instance, when the UE does not detect any WUS/DCP that would require the UE to wake up and start the drx-onDurationtimer.

The PDCCH monitoring activity of the terminal device in radio resource control (RRC) connected mode is governed by DRX, bandwidth adaption (BA), and DCP. <FIG> illustrates a schematic diagram of a discontinuous reception (DRX) cycle according to conventional technologies. As shown in <FIG>, there are an OnDuration <NUM> and a duration <NUM> for opportunity for DRX in one DRX cycle <NUM>. Detailed explanation of <FIG> is described below.

When DRX is configured, the terminal device does not have to continuously monitor PDCCH. DRX is characterized by the following:.

When BA is configured, the UE only has to monitor PDCCH on the one active BWP i.e. it does not have to monitor PDCCH on the entire downlink (DL) frequency of the cell. A BWP inactivity timer (independent from the DRX inactivity-timer described above) is used to switch the active BWP to the default one: the timer is restarted upon successful PDCCH decoding and the switch to the default BWP takes place when it expires.

In addition, the UE may be indicated, when configured accordingly, whether it is required to monitor or not the PDCCH during the next occurrence of the on-duration by a DCP received on the active BWP. By default, if it does not detect a DCP on the active BWP, the UE does not monitor the PDCCH during the next occurrence of the on-duration. However, it can also be configured to have the opposite behavior in this case, i.e. monitor the PDCCH during the next occurrence of the on-duration.

A UE can only be configured to monitor DCP when connected mode DRX is configured, and at occasion(s) at a configured offset before the on-duration. More than one monitoring occasion can be configured before the on-duration. The UE does not monitor DCP on occasions occurring during active-time, measurement gaps, or BWP switching, in which case it monitors the PDCCH during the next on-duration. If no DCP is configured in the active BWP, UE follows normal DRX operation.

When CA is configured, DCP is only configured on the PCell or PSCell (Primary Secondary Cell). One DCP can be configured to control PDCCH monitoring during on-duration for one or more UEs independently. Power saving in RRC_IDLE and RRC_INACTIVE can also be achieved by UE relaxing neighbor cells RRM measurements when it meets the criteria determining it is in low mobility or not at cell edge.

UE power saving may be enabled by adapting the DL maximum number of MIMO layers by BWP switching. Power saving is also enabled during active-time via cross-slot scheduling, which facilitates UE to achieve power saving with the assumption that it won't be scheduled to receive PDSCH, triggered to receive A-CSI or transmit a PUSCH scheduled by the PDCCH until the minimum scheduling offsets K0 and K2. Dynamic adaptation of the minimum scheduling offsets K0 and K2 is controlled by PDCCH.

In some situation, for instance, when the network device ends the terminal device's active time, the network device does not know the exact time when the terminal device decoded the medium access control (MAC) control element (CE) (e.g., DRX command MAC CE) and applied it. This means that there is ambiguity in the network device whether the terminal device would be decoding DCP/WUS in case DCP/WUS occasion(s) happen during the ambiguity time between the terminal device and network device. Furthermore, this ambiguity time may overlap with part of the DCP occasions or all of them.

This makes it difficult for the network device to know if the terminal device will report CSI based on the configuration given for the situation when drx-onDurationTimer is not started by DCP or if the terminal device will report the CSI based on the case when drx-onDurationTimer is started by DCP or by the conditions where DCP occasion(s) overlaps with active time.

Based on conventional technologies, the ambiguity period is only applicable to determine possible uplink transmission, but it is not applicable to PDCCH reception, which means the terminal device needs to continue PDCCH reception during the ambiguity period while it does not if the network device wants to stop the active time. It would not be possible also to do that for DCP since the terminal device is not required to be able to simultaneously receive DCP and other PDCCH for scheduling.

According to embodiments of the present disclosure, the terminal device determines based on transmission information at a first time point whether a predetermined number of the one or more occasions overlaps with active time of the terminal device. The terminal device defines or generates the configuration for transmitting the uplink information based on the determination. In this way, ambiguity has been reduced and the flexibility of the network is improved.

<FIG> illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented. The communication system <NUM>, which is a part of a communication network, comprises a device <NUM>-<NUM> , a device <NUM>-<NUM>,. , a device <NUM>-N, which can be collectively referred to as "first device(s) <NUM>. " The communication system <NUM> further comprises a second device <NUM>. One or more devices are associated with and covered by a cell. It is to be understood that the number of devices and cells shown in <FIG> is given for the purpose of illustration without suggesting any limitations. The communication system <NUM> may comprise any suitable number of devices and cells. In the communication system <NUM>, the first device <NUM> and the second device <NUM> can communicate data and control information to each other. In the case that the first device <NUM> is the terminal device and the second device <NUM> is the network device, a link from the second device <NUM> to the first device <NUM> is referred to as a downlink (DL), while a link from the first device <NUM> to the second device <NUM> is referred to as an uplink (UL). The number of devices shown in <FIG> is given for the purpose of illustration without suggesting any limitations. The second device <NUM> and the third device <NUM> are interchangeable.

Communications in the communication system <NUM> may be implemented according to any proper communication protocol(s), comprising, 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, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.

<FIG> illustrates a schematic diagram of interactions <NUM> among devices in accordance with some embodiments of the present disclosure. The interactions <NUM> may be implemented at any suitable devices. Only for the purpose of illustrations, the interactions <NUM> are described to be implemented at the first device <NUM>-<NUM> and the second device <NUM>.

The second device <NUM> determines <NUM> one or more occasions configured for detection of physical downlink control channel (PDCCH) transmission carrying a wake-up indication. In an embodiment there is only one occasion. In an embodiment, there are plurality of occasions. The PDCCH transmission may be addressed to a specific radio network temporary identifier. In some embodiments, the PDCCH transmission may be addressed to a power saving radio network temporary identifier (PS-RNTI). As shown in <FIG>, the second device <NUM> may determine the plurality of occasions comprising the occasion <NUM>-<NUM>, the occasion <NUM>-<NUM> and the occasion <NUM>-<NUM>. It should be noted that the number of occasions for monitoring the wake-up signals can be any suitable number. In an example embodiment, the second device <NUM> and the first device <NUM>-<NUM> may be configured with a short DRX cycle. Alternatively or in addition, the second device <NUM> and the first device <NUM>-<NUM> may be configured with a long DRX cycle.

The second device <NUM> transmits <NUM> the information indicating the one or more occasions to the first device <NUM>-<NUM>. In some embodiments, the information may be transmitted via physical layer (PHY) signaling. Alternatively or in addition, the information may be transmitted via MAC signaling. In other embodiments, the information may be transmitted via RRC signaling. In some embodiments, the information indicating the one or more occasions may also comprise a predetermined time duration <NUM> or <NUM> of <FIG>. Detailed description of the time duration will be discussed later.

The second device <NUM> may determine <NUM> further information indicating whether a predetermined number of the one or more occasions <NUM> is within the time duration. In one example embodiment, the second device <NUM> may configure or specify whether the first device <NUM>-<NUM> shall take into account all the occasions or only subset of them, i.e. determine what the predetermined number of the one or more occasions is. This may depend e.g. on whether the information in the occasions is the same or whether it may be different, for example. As shown in <FIG>, the plurality of occasions <NUM> are out of the time duration <NUM> but within the time duration <NUM>.

The first device <NUM>-<NUM> determines <NUM>, based on transmission information available at a first time point, whether the predetermined number of the one or more occasions overlaps with active time of the first device <NUM>-<NUM>. The predetermined number can be any suitable integer number, for example, <NUM>, <NUM>,. , or the total number of the one or more occasions. In some embodiments, the predetermined number of the one or more occasions may be determined based on a configuration from the second device <NUM>. Alternatively or in addition, the predetermined number of the one or more occasions may be determined based on whether the information transmitted in the one or more occasions is the same or may be different. In other embodiments, the predetermined number of the one or more occasions may be a pre-determined value.

The active time comprises at least one of: Active Time associated a discontinuous reception (DRX) cycle, a bandwidth part switch gap, or a measurement gap. For example, as shown in <FIG>, if the first device <NUM>-<NUM> would like to determine whether the first device <NUM>-<NUM> is expected to monitor the plurality of occasion before/at the time point t3, the first device <NUM> may make the determination at the time point <NUM>. As shown in <FIG>, the time point t1 is the time duration <NUM> ahead of the time point t3. As another example, as shown in <FIG>, if the first device <NUM>-<NUM> would like to determine whether the first device <NUM>-<NUM> is able to monitor the plurality of occasion before/at the time point t4, the first device <NUM> may make the determination at the time point t2. As shown in <FIG>, the time point t2 is the time duration <NUM> ahead of the time point t4. As mentioned above, the time duration may be configured by the second device <NUM>. Alternatively or in addition, the time duration may be predefined and be, e.g., <NUM> milliseconds. This time duration may correspond to the ambiguity period discussed earlier. In an embodiment, the time duration may be determined to start at the reception of the signaling that indicates the first device to end the active time of the first device.

In some embodiments, the transmission information available at the first time point (or second time point in the other non-limiting example) comprises at least one of the following: a grant (or an uplink grant), an assignment (or a downlink assignment), a DRX command MAC CE, a long DRX command MAC CE, and a scheduling request.

In an example embodiment, the first device <NUM>-<NUM> may determine whether the first device <NUM>-<NUM> is in active time based the transmission information available at the first time point. For example, the first device <NUM>-<NUM> may be in DRX active time. For example, the first device <NUM>-<NUM> may be in a measurement gap. Alternatively or in addition, the first device <NUM>-<NUM> may in a BWP switching gap.

If the first device <NUM>-<NUM> is in active time, the first device <NUM>-<NUM> may determine to skip monitoring the plurality of occasions <NUM>. Alternatively, if the first device <NUM>-<NUM> is not in active time, the first device <NUM>-<NUM> may determine to monitor the plurality of occasions <NUM>.

The second device <NUM> may determine <NUM> other information indicating that whether the information transmitted in the one or more occasions is the same. The second device <NUM> may transmit <NUM> the other information to the first device <NUM>-<NUM>. In some embodiments, the other information may be transmitted via PHY signaling. For example, the PHY signaling may be downlink control information or the wake-up signal. Alternatively or in addition, the information may be transmitted via MAC signaling, for example, MAC CE. In other embodiments, the information may be transmitted via RRC signaling, for example, RRCReconfiguration or system information. The second device <NUM> may transmit the wake-up signals to the first device <NUM>-<NUM>.

The second device <NUM> determines <NUM> whether the first device is expected to monitor a predetermined number of the one or more occasions between a first time point and another time point (for example, the time points t1 and t3). The determination <NUM> is based on transmission information associated with the first device and available at the first time point. The time point t1 (or t2, depending on the embodiment) may be seen as the decision point on how to determine uplink reporting for the next DRX onDuration. For example, the first device <NUM>-<NUM> may determine at this point how many, if any, of the DCP occasions are configured to take place before time point t3, which is ending the ambiguous activity time of the first device.

The first device <NUM>-<NUM> generates <NUM> the configuration for transmitting an uplink information based on the determination <NUM>. The first device <NUM>-<NUM> transmits <NUM> the uplink information to the second device <NUM>, for example, in the drx-onDuration timer duration <NUM>. The further time point may be, for example, during the DRX on duration timer running or in next DRX cycle. Thus, the further time point may be a predetermined time interval that takes place after the ambiguity period, i.e. after any overlapping occasion(s). For example, the uplink information may be a CSI report. Alternatively or in addition, the uplink information may be a sounding reference signal (SRS). It should be noted that the uplink information can be any kinds of suitable uplink information.

In some embodiments, if the first device is in active time or BWP switching gap when the DCP occasions take place, the first device <NUM>-<NUM> may determine a first configuration associated with the discontinuous transmission on duration timer is running. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration. As shown in <FIG>, in the drx-onDuration timer duration <NUM>, the occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> are configured for the transmitting uplink information when on duration timer is running.

In some embodiments, if the ambiguity period is over when the DCP occasions take place, the first device <NUM>-<NUM> may try to monitor the one or more occasions. If the first device <NUM>-<NUM> cannot detect wake-up signal/indication (i.e. cannot detect PDCCH transmission on the non-overlapping occasions), the first device <NUM>-<NUM> may determine a second configuration associated with the discontinuous reception on duration timer not being running. The first device <NUM>-<NUM> may transmit the uplink information based on the second configuration. As shown in <FIG>, in the drx-onDuration timer duration <NUM>, the occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> are configured for the uplink information when on duration timer is not running.

In an example embodiment, if the information <NUM> indicates that the one or more occasions <NUM> is within a time duration between the first time point and a further time point (for example, t3), the first device <NUM>-<NUM> may determine the first configuration associated with the discontinuous transmission on duration timer is running. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration. In some embodiments, the first device <NUM>-<NUM> may determine to start the on duration timer.

In an example embodiment, if the information transmitted in the one or more occasions is allowed to be different and that the predetermined number of the plurality of occasions <NUM> overlap with active time, the first device <NUM>-<NUM> may determine a first configuration associated with the discontinuous reception on duration timer is running. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration.

In some embodiments, if the first device <NUM>-<NUM> is expected to monitor the predetermined number of the one or more occasions, the first device <NUM>-<NUM> may detect the wake-up signals during the predetermined number of the plurality of occasions <NUM>. If the first device <NUM>-<NUM> is able to decode the detected wake-up signal, the first device <NUM>-<NUM> may transmit the uplink information based on the wake-up signals. For example, the first device <NUM>-<NUM> may not be in active time/measurement gap/BWP switching and cannot receive further scheduling (for example, DRX command MAC CE is received by the first device <NUM>-<NUM>), the first device <NUM> may transmit the uplink information based on the DCP decoding itself.

In other embodiments, if the predetermined number of the one or more occasions does not overlap with active time of the first device <NUM>-<NUM>, the first device <NUM>-<NUM> may detect PDCCH transmission carrying the wake-up indication/the wake-up signals during the predetermined number of the one or more occasion. The first device <NUM>-<NUM> may detect wake-up signals during the at least one occasion and may transmit the uplink information to the second device based on the detected wake-up signals. In some embodiments, if the first device <NUM>-<NUM> is unable to decode the wake-up signal/the wake-up indication in PDCCH transmission, the first device <NUM>-<NUM> may determine to start a DRX on duration timer and transmit the uplink information based on the first configuration associated with a DRX on duration timer being running.

Alternatively or in addition, if the information transmitted in the predetermined number of the one or more occasions is the same and that at least one of the plurality of occasions is out of a time duration between the first time point and another time point (e.g. t3 shown in <FIG>), i.e. outside the ambiguous active time of the first device <NUM>-<NUM>), meaning that the at least one of the plurality of occasions are not overlapping with the active time, the first device <NUM>-<NUM> may detect the non-overlapping wake-up signals after the ambiguity period and before the DRX onDuration. The first device <NUM>-<NUM> may decode the detected wake-up signals during the at least one occasion and may transmit the uplink information to the second device based on the wake-up signals.

Table <NUM> below shows an example proposal for the MAC running CR on power saving. It should be noted that the proposal shown in Table <NUM> is only an example.

For example, if the first device <NUM>-<NUM> is active at point t1 and receives from the second device, for instance, a DRX command MAC CE to end the active time, the ambiguity period may last until the time point t3 (e.g. <NUM>). The configuration information received in step <NUM> may show that all or a subset (e.g. a predetermined number) of occasions may overlap this ambiguity period. As such, the second device <NUM> cannot be sure if the first device <NUM>-<NUM> will monitor the overlapping occasions. To be on the safe side, both devices may assume that the overlapping occasions are not monitored.

In one embodiment, if all the occasions overlap the ambiguity period (also called active time of the first device, expected activity time of the first device, or ambiguous activity time of the first device), then the first device <NUM>-<NUM> may determine to skip monitoring the overlapping occasions and determine to start the DRX onDurationTimer and report CSI (or other uplink signaling) according to a certain configuration (e.g. a first configuration).

On the other hand, if none of the occasions overlap with the ambiguity period, then the first device <NUM>-<NUM> may monitor the occasions. If the first device <NUM>-<NUM> detects a wake-up signal on the occasion(s), then the first device <NUM>-<NUM> may determine to start the DRX onDurationTimer and report CSI (or other uplink signaling) according to the certain configuration (e.g. the first configuration). If the first device <NUM>-<NUM> does not detect a wake-up signal on the occasion(s), then the first device <NUM>-<NUM> may refrain from starting the drx onDurationTimer and report CSI (or other uplink signaling) according to a different configuration (e.g. a second configuration).

In one embodiment, if a subset of the occasions overlap with the ambiguity time and if the information comprised in the occasions is the same, then the first device <NUM>-<NUM> may monitor the non-overlapping occasion(s). If the first device <NUM>-<NUM> detects a wake-up signal on the non-overlapping occasion(s), then the first device <NUM>-<NUM> may determine to start the DRX onDurationTimer and report CSI (or other uplink signaling) according to the certain configuration (e.g. the first configuration). If the first device <NUM>-<NUM> does not detect a wake-up signal on the non-overlapping occasion(s), then the first device <NUM>-<NUM> may refrain from starting the drx onDurationTimer and report CSI (or other uplink signaling) according to the different configuration (e.g. the second configuration).

In one embodiment, if a subset of the occasions overlap with the ambiguity time and if the information comprised in the occasions may be different (need not be but can be), then the first device <NUM>-<NUM> may determine to skip monitoring of all occasions (the overlapping and non-overlapping), and the first device <NUM>-<NUM> may determine to start the DRX onDurationTimer and report CSI (or other uplink signaling) according to the certain configuration (e.g. the first configuration).

It may also be possible that the first device <NUM>-<NUM> is configured to perform differently based on the detection of the wake-up signal. For example, the first device may, if it does not detect any wake-up signals on non-overlapping occasion(s), determine to start the DRX onDurationTimer and report CSI (or other uplink signaling) according to the certain configuration (e.g. the first configuration).

In an embodiment, the first device <NUM>-<NUM> may make a determination a time_offset (=ambiguity time) before the DCP occasion(s) that the first device <NUM>-<NUM> cannot decode the DCP occasions, in which case the first device <NUM>-<NUM> may start drx-onDurationTimer and base the CSI reporting on the rules when drx-onDurationTimer is started/running.

In an embodiment, the first device <NUM>-<NUM> may make a determination a time_offset (i.e., ambiguity time) before the DCP occasion(s) that the first device <NUM>-<NUM> will not be in active time/measurement gap/BWP switching/etc. preventing to decode the DCP occasion(s). However, the first device <NUM>-<NUM> cannot at this point know if such assumption will hold (e.g., the second device <NUM> may schedule the first device <NUM>-<NUM> after this point). In this case, the first device <NUM>-<NUM> may assume not to start drx-onDurationTimer and base the CSI reporting on the rules when drx-onDurationTimer is not started/running. In alternative embodiment, the first device <NUM>-<NUM> may assume to start drx-onDurationTimer and base the CSI reporting on the rules when drx-onDurationTimer is started/running.

In an embodiment, the first device <NUM>-<NUM> makes a determination a time offset (i.e., ambiguity time) before the DCP occasion(s) that the first device <NUM>-<NUM> will not be in active time/measurement gap/BWP switching/etc. preventing to decode DCP occasion(s) and cannot receive further scheduling (e.g., DRX command MAC CE is received by the first device <NUM>-<NUM>). In this case the first device <NUM>-<NUM> may base the CSI reporting on the DCP decoding itself, i.e., whether the DCP will start drx-onDurationTimer or not.

<FIG> illustrates a flow chart of method <NUM> according to embodiments of the present disclosure. The method <NUM> can be implemented at any suitable devices. For example, the method may be implemented at the first device <NUM>-<NUM>.

At block <NUM>, the first device <NUM>-<NUM> receives the information indicating one or more of occasions for detection of PDCCH transmission carrying a wake-up indication from the second device <NUM>. In some embodiments, the information may be transmitted via PHY signaling. Alternatively or in addition, the information may be transmitted via MAC signaling. In other embodiments, the information may be transmitted via RRC signaling.

At block <NUM>, the first device <NUM>-<NUM> determines based on transmission information available at a first time point, whether a predetermined number of the one or more occasions overlaps with active time of the first device (active time may also be called ambiguous active time or ambiguity time, e,g. between time points t1 and t3, or time point t2 and t4, or between t1 and t4, for example). In some embodiments, the transmission information at the first time point comprises at least one of the following: a grant, an assignment, a received DRX command MAC CE, Long DRX command MAC CE and a scheduling request.

In an example embodiment, the first device <NUM>-<NUM> may determine whether the first device <NUM>-<NUM> is in active time at the first time point based the transmission information. For example, the first device <NUM>-<NUM> may be in a measurement gap. Alternatively or in addition, the first device <NUM>-<NUM> may be in a BWP switching gap.

At block <NUM>, the first device <NUM>-<NUM> generates the configuration for transmitting an uplink information based on the determination at block <NUM>. For example, the uplink information may be a CSI report. Alternatively or in addition, the uplink information may be a SRS. It should be noted that the uplink information can be any kinds of suitable uplink information.

At block <NUM>, the first device <NUM>-<NUM> transmits the uplink information to the second device <NUM> based on the configuration (wherein the second time point may be a time interval comprising DRX onduration of a DRX cycle). In some embodiments, if the one or more occasions overlap with the active time of the first device <NUM>-<NUM> (i.e., ambiguity time), the first device <NUM>-<NUM> may determine a first configuration associated with the discontinuous transmission on duration timer is running. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration. As shown in <FIG>, in the drx-onDuration timer duration <NUM>, the occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> are configured for transmitting the uplink information when onDuration Timer is running/started.

In some embodiments, if the predetermined number of the one or more occasions are not overlapping with active time, the first device <NUM>-<NUM> may monitor wake-up signals during the one or more occasions. If the first device <NUM>-<NUM> cannot detect wake-up signal, the first device <NUM>-<NUM> may not determine to start the DRX timer and determine a second configuration associated with the discontinuous transmission on duration timer is not running/started. The first device <NUM>-<NUM> may transmit the uplink information based on the second configuration. As shown in <FIG>, during the drx-onDuration timer occasion <NUM>, the occasions <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> and <NUM>-<NUM> are configured for transmitting the uplink information when onDuration Timer is not started.

In an example embodiment, if the other information indicates that the predetermined number of the one or more occasions <NUM> are within a time duration between the first time point and another time point, the first device <NUM>-<NUM> may determine the first configuration associated with the discontinuous transmission on duration timer is started. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration.

In an example embodiment, if the information transmitted in the predetermined number of the one or more occasion may be different and that the predetermined number of the plurality of occasions <NUM> are overlapping with the active time of the first device <NUM>-<NUM>, the first device <NUM>-<NUM> may determine a first configuration associated with the discontinuous transmission on duration timer is started. The first device <NUM>-<NUM> may transmit the uplink information based on the first configuration.

In some embodiments, if the first device <NUM>-<NUM> is expected to monitor the plurality of occasions, the first device <NUM>-<NUM> may monitor the wake-up signals during the predetermined number of the one or more occasions <NUM>. If the first device <NUM>-<NUM> is able to detect wake-up signal, the first device <NUM>-<NUM> may transmit the uplink information based on the wake-up signals. For example, the first device <NUM>-<NUM> may not be in active time/measurement gap/BWP switching and cannot receive further scheduling (for example, DRX command MAC CE is received by the first device <NUM>-<NUM>), the first device <NUM> may transmit the uplink information based on the DCP decoding itself.

In other embodiments, if the predetermined number of the one or more occasions does not overlap with the active time, the first device <NUM>-<NUM> may monitor the wake-up signals during the predetermined number of the one or more occasions. The first device <NUM>-<NUM> may detect wake-up signals during the at least one occasion and may transmit the uplink information to the second device based on the wake-up signals.

Alternatively or in addition, if the information transmitted in the one or more occasions is the same and that at least one of the one or more occasions does not overlap with the active time, the first device <NUM>-<NUM> may detect the wake-up signals during the at least one non-overlapping occasions. The first device <NUM>-<NUM> may decode the detected wake-up signals during the at least one non-overlapping occasion and may transmit the uplink information to the second device based on the wake-up signals.

<FIG> illustrates a flow chart of method <NUM>. The method <NUM> can be implemented at any suitable devices. For example, the method may be implemented at the network device <NUM>.

At block <NUM>, the second device <NUM> determines one or more occasions configured for detection of PDCCH transmission carrying a wake-up indication. In an example embodiment, the second device <NUM> and the first device <NUM>-<NUM> may be configured with a short DRX cycle. Alternatively or in addition, the second device <NUM> and the first device <NUM>-<NUM> may be configured with a long DRX cycle.

At block <NUM>, the second device <NUM> transmits the information to the first device <NUM>-<NUM>. In some embodiments, the information may be transmitted via PHY signaling. Alternatively or in addition, the information may be transmitted via MAC signaling. In other embodiments, the information may be transmitted via RRC signaling. In some embodiments, the information may also comprise a predetermined time duration.

In some embodiments, the second device <NUM> may determine further information indicating whether the one or more occasions <NUM> are within the time duration and may transmit the further information to the first device <NUM>-<NUM>. In one example embodiment, the second device <NUM> may configure or specify whether the first device <NUM>-<NUM> shall take into account all the occasions or only subset of them.

At block <NUM>, the second device <NUM> determines whether the first device is expected to monitor a predetermined number of the one or more occasions. The determining is based on transmission information associated with the first device at the first time point. In some embodiments, the second device <NUM> may determine other information indicating that whether information in one or more occasions is the same for the plurality of occasions. The second device <NUM> may transmit the other information to the first device <NUM>-<NUM>. In some embodiments, the other information may be transmitted via PHY signaling. For example, the PHY signaling may be downlink control information or the wake-up signal. Alternatively or in addition, the information may be transmitted via MAC signaling, for example, MAC CE. In other embodiments, the information may be transmitted via RRC signaling, for example, RRCReconfiguration or system information.

At block <NUM>, the second device <NUM> receives the uplink information from the first device <NUM>-<NUM>. For example, the uplink information may be the CSI report. Alternatively or in addition, the uplink information may be the SRS. It should be noted that the uplink information can be any kinds of suitable uplink information.

In some embodiments, if the first device is not expected to monitor the plurality of occasions, the second device <NUM> may receive the uplink information based on the first configuration. In an example embodiment, if the further information indicates that the plurality of occasions overlaps with the active time of the first device <NUM>-<NUM>, the second device <NUM> may receive the uplink information based on the first configuration.

In some embodiments, if the first device <NUM>-<NUM> is able to monitor the plurality of occasions and cannot decode the detected wake-up signal, the second device <NUM> may receive the uplink information based on the second configuration associated with the absence of the discontinuous transmission timer.

In an example embodiment, if the information transmitted in the predetermined number of occasions may be different and that the predetermined number of occasions overlap with the ambiguity period, the second device <NUM> may receive the uplink information based on the first configuration. This may be because if the first device cannot detect all of the wake up signals having different contents, then the first device cannot reliably know how to act during the next on-period merely based on those wake up signals that are after the active time (i.e. ambiguity period).

In some embodiments, if the first device <NUM>-<NUM> is expected to monitor the plurality of occasions and is able to decode the detected wake-up signal, the second device <NUM> may receive the uplink information based on the decoded wake-up signals.

In other embodiments, if at least one of the plurality of occasions is out of active time and the first device <NUM>-<NUM> may decode the detected wake-up signals during the at least one occasion, the second device <NUM> may receive the uplink information based on the decoded wake-up signals.

Alternatively or in addition, if the wake-up signals are the same and that at least one of the plurality of occasions is out of active time, the first device <NUM>-<NUM> may decode the detected wake-up signals during the at least one occasion after the active time, in which case the second device <NUM> may receive the uplink information based on the detected wake-up signals. This may be because even if the first device cannot detect all of the wake up signals, it may be sufficient for the first device to decode the one(s) that is/are after the active time and based on that reliably know how to act during the next on-period.

In embodiments, an apparatus for performing the method <NUM> (for example, the first device <NUM>-<NUM> ) may comprise respective means for performing the corresponding steps in the method <NUM>. These means may be implemented in any suitable manners. For example, it can be implemented by circuitry or software modules.

In some embodiments, the apparatus comprises means for receiving, at a first device and from a second device, information indicating one or more occasions configured for detection of physical downlink control channel (PDCCH) transmission carrying a wake-up indication; means for determining, based on transmission information available at a first time point, whether a predetermined number of the one or more occasions overlap with active time; means for generating a configuration for transmitting uplink information based on the determination; and means for transmitting the uplink information to the second device based on the configuration.

In some embodiments, the transmission information available at the first time point comprises at least one of the following: a grant, an assignment, a discontinuous reception (DRX) command medium access control (MAC) control element (CE), a long DRX command MAC CE, and a scheduling request.

In some embodiments, the PDCCH transmission is addressed to a power saving radio network temporary identifier.

In some embodiments, the apparatus further comprises: means for determining at the first time point whether the first device is/will be in active time at the time of the predetermined number of the one or more occasions; means for in accordance with a determination that the first device is/will be in active time, determining to skip monitoring the predetermined number of the one or more occasions; or means for in accordance with a determination that the first device is not/will not be in active time, determining to monitor the predetermined number of the one or more occasions.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with the determination that the predetermined number of the one or more occasions overlap with the active time of the first device, transmitting the uplink information based on a first configuration associated with a discontinuous reception on duration timer being running.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with the determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device, transmitting the uplink information based on a second configuration associated with a discontinuous reception on duration timer not being running.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with the determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device, monitoring the PDCCH transmission during the predetermined number of the one or more occasions; means for in accordance with a determination that the first device does not detect the PDCCH transmission carrying the wake-up indication, transmitting the uplink information based on a second configuration associated with a discontinuous reception on duration timer not being running; and means for in accordance with a determination that the first device detects the PDCCH transmission, transmitting the uplink information based on the wake-up indication.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with the determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device, monitoring the PDCCH transmission during the predetermined number of the one or more occasions; means for in accordance with a determination that the first device is does not detect the PDCCH transmission, determining to start a discontinuous reception on duration timer; means for transmitting the uplink information based on a first configuration associated with a discontinuous reception on duration timer being running; and means for in accordance with a determination that the first device detects the PDCCH transmission the wake-up signal, transmitting the uplink information based on the wake-up indication.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with a determination that information transmitted in the one or more occasions is the same and that at least one of the one or more occasions does not overlap with the active time of the first device, detecting at least one PDCCH transmission during the at least one non-overlapping occasion; and means for transmitting the uplink information to the second device based on the PDCCH transmission.

In some embodiments, the means for transmitting the uplink information to the second device comprises: means for in accordance with a determination that the information transmitted in the one or more occasions is allowed to be different and that the predetermined number of the one or more occasions overlaps with the active time of the first device, transmitting the uplink information based on a first configuration associated with a discontinuous reception on duration timer being running.

In some embodiments, the active time comprises at least one of: Active Time associated a discontinuous reception (DRX) cycle, a bandwidth part switch gap, or a measurement gap.

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

In embodiments, an apparatus for performing the method <NUM> (for example, the second device <NUM> ) may comprise respective means for performing the corresponding steps in the method <NUM>. These means may be implemented in any suitable manners. For example, it can be implemented by circuitry or software modules.

In some embodiments, the apparatus comprises mean for determining, at a second device, one or more occasions configured for detection of physical downlink control channel (PDCCH) transmission carrying a wake-up indication; means for transmitting to a first device information indicating the one or more occasions; means for determining whether the first device is expected to monitor a predetermined number of the one or more occasions based on transmission information available at the first device at a first time point, wherein the predetermined number of the one or more occasions are after the first time point; and means for receiving uplink information from the first device based on a configuration which is determined based on whether the first device is expected to monitor the predetermined number of the at least one occasion.

In some embodiments, the means for receiving the uplink information from the first device comprises: means for in accordance with a determination that the predetermined number of the one or more occasions overlap with the active time of the first device, receiving the uplink information based on a first configuration associated with a discontinuous reception on duration timer being running.

In some embodiments, the means for receiving the uplink information from the first device comprises: means for in accordance with a determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device, receiving the uplink information from the first device based on the non-overlapping occasions.

In some embodiments, the means for receiving the uplink information from the first device comprises: means for in accordance with a determination that information transmitted in the one or more occasions is the same and that at least one of the one or more occasions are not overlapping with the active time of the first device, receiving the uplink information from the first device based on the non-overlapping at least one occasion.

In some embodiments, the means for receiving the uplink information from the first device comprises: means for in accordance with a determination that information transmitted in the one or more occasions is allowed to be different and that the predetermined number of the one or more occasions overlaps with the active time of the first device, receiving the uplink information based on a first configuration associated with a discontinuous reception on duration timer being running.

In some embodiments, the means for receiving the uplink information comprises: means for in accordance with the determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device, receiving the uplink information based on a second configuration associated with a discontinuous reception on duration timer not being running.

In some embodiments, the means for receiving the uplink information comprises: means for in accordance with the determination that the predetermined number of the one or more occasions are not overlapping with the active time of the first device and a determination that the first device does not detect the PDCCH transmission on the non-overlapping occasions, receiving the uplink information based on a second configuration associated with a discontinuous reception on duration timer not being running; and means for in accordance with a determination that the first device detects at least one PDCCH transmission on the non-overlapping occasions, receiving the uplink information based on the detected at least one PDCCH transmission.

In some embodiments, the active time comprises at least one of: Active Time associated a discontinuous reception (DRX) cycle, a bandwidth part switch gap, or a measurement gap. In some embodiments, the first device comprises a terminal device and the second device comprises 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 first device <NUM>, the second device <NUM> , or the third 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 labor 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 device <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 device <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 device <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 device <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 methods <NUM>-<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 terminal device (<NUM>-<NUM>) comprising:
means (<NUM>) for receiving, from a network device (<NUM>), information indicating one or more occasions configured for detection of physical downlink control channel, PDCCH, transmission carrying a wake-up indication;
means (<NUM>) for determining, based on transmission information available at a first time point (t2), whether a predetermined number of the one or more occasions (<NUM>) overlap with an active time of the terminal device (<NUM>-<NUM>), wherein the first time point (t2) is <NUM> prior to start of a last occasion of the one or more occasions configured for detection of PDCCH transmission carrying the wake-up indication, wherein the predetermined number of the one or more occasions (<NUM>) are after the first time point (t2), and the transmission information available at the first time point (t2) comprises at least one of the following: a grant, an assignment, a discontinuous reception command medium access control (MAC) control element (CE), a long discontinuous reception command MAC CE, and a scheduling request;
means (<NUM>) for determining a configuration for transmitting uplink information based on a determination by the means (<NUM>) for determining whether the predetermined number of the one or more occasions (<NUM>) overlap with the active time of the terminal device (<NUM>-<NUM>); and
means (<NUM>) for transmitting the uplink information to the network device (<NUM>) based on the configuration.