Error handling after low power-wake up signal (LP-WUS) paging

Abstract

A method in a user equipment (UE) includes: configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier; starting a counter; and in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

Description

ERROR HANDLING AFTER LOW POWER-WAKE UP SIGNAL (LP-WUS) PAGINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority from, and the benefit of, US Provisional Application No.63 / 755069, filed February 6, 2025, the contents of which are hereby incorporated by reference in their entirety.FIELD

[0002] Various example embodiments relate to low-power wake up signals (LP-WUS) and paging and, more particularly, to configurations for receiving LP-WUS and paging on a first carrier and for responding to the paging on a second carrier.BACKGROUND

[0003] Wireless networking provides significant advantages for user mobility. A user’s ability to remain connected while on the move provides advantages not only for the user, but also provides greater efficiency and productivity for society as a whole. As expectations for connection reliability, data speed, and lower power consumption, become more demanding, technology for wireless networking must also keep pace with such expectations. Accordingly, there is continuing interest in improving wireless networking technology.SUMMARY

[0004] In accordance with aspects of the disclosure, a method in a user equipment (UE), includes: configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier; starting a counter; and in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0005] In an aspect, an indication of at least one second carrier may comprise at least one of: indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0006] In an aspect, the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0007] In an aspect, the identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0008] In an aspect, the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0009] In an aspect, the first carrier and the at least one second carrier have different frequencies.

[0010] In an aspect, the first carrier and the at least one second carrier are in different bands.

[0011] In an aspect, the first carrier is provided by a serving cell serving the UE, and the at least one second carrier is provided by at least one second cell.

[0012] In an aspect, a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0013] In an aspect, a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0014] In an aspect, the attempting to respond to the paging on at least one of the at least one second carrier occurs only while the timer is running.

[0015] In an aspect, the timer may be started based on at least one of: receiving the LP-WUS, receiving the paging addressing the UE, transmitting a message on at least one of the at least one second carrier, or upon selection of a new carrier for responding to the paging.

[0016] In an aspect, the message may be a common control channel (CCCH) message.

[0017] In an aspect, the CCCH message may comprise one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0018] In an aspect, the attempting to respond to the paging on at least one of the at least one second carrier while the timer is running may comprise at least one of: selecting a cell on at least one of the at least one second carrier, reselecting to a cell on at least one of the at least one second carrier, initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier, initiating an RRC Resume Request on at least one of the at least one second carrier, initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, or responding to the paging on at least one of the at least one second carrier.

[0019] In an aspect, the method may further comprise stopping the timer.

[0020] In an aspect, the timer may be stopped based on at least one of: a T300 timer being started, a T319 timer being started, or a T319a time being started.

[0021] In an aspect, the timer may be stopped based on at least one of: transmission of an RRCSetupRequest message, transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT), transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT, transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0022] In an aspect, the timer may be stopped based on at least one of: reception of a RRCResume message, reception of an RRCSetup message, reception of an RRCRelease with suspendConfig message, reception of a RRCReject message.

[0023] In an aspect, the timer may be stopped based on at least one of: successfully completing contention resolution in random access procedure, aborting connection establishment by upper layers, cell selection on at least one of the at least one second carrier, cell re-selection on at least one of the at least one second carrier, or determining that access is barred on the at least one second carrier.

[0024] In an aspect, the method may further comprise, after the timer is stopped, at least one of: attempting to select the first carrier, attempting to re-select the first carrier, attempting to re-select to one of configured carriers, or entering into idle mode from inactive mode .

[0025] In an aspect, the method may further comprise, after the timer is stopped, at least one of: stopping at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer, or treating, as stopped, at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer.

[0026] In an aspect, the method may further comprise, after the timer is stopped, at least one of: stopping attempting to respond to the paging, continuing attempting to respond to the paging on the first carrier, or stopping monitoring for a LP-WUS for period of time.

[0027] In an aspect, the method may further comprise, receiving, from a network apparatus, a timer end value for the timer.

[0028] In an aspect, receiving the timer end value may comprise receiving the timer end value in a dedicated signal.

[0029] In an aspect, the dedicated signal may comprise a RRCRelease message containing the timer end value.

[0030] In an aspect, the receiving the timer end value may comprise receiving the timer end value in a broadcast signal.

[0031] In an aspect, the broadcast signal may comprise a system information block (SIB) containing the timer end value.

[0032] In an aspect, the timer end value may be statically defined in a standard.

[0033] In an aspect, an apparatus includes at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to perform any one of the preceding methods.

[0034] In an aspect, a non-transitory processor-readable medium stores instructions which, when executed by at least one processor of an apparatus, causes the apparatus to perform any one of the preceding methods.

[0035] In accordance with aspects of the disclosure, a method in a network apparatus, includes: transmitting, to a user equipment (UE), a timer end value, wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier, wherein the timer end value is configured to cause the UE to run a timer for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0036] In an aspect, an indication of at least one second carrier may include at least one of: indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0037] In an aspect, the paging may be addressing the UE when a paging message of the paging includes an identifier of the UE.

[0038] In an aspect, the identifier may be S-TMSI (Temporary Mobile Subscription Identifier).

[0039] In an aspect, the identifier may be l-RNTI (Inactive Radio Network Temporary Identifier).

[0040] In an aspect, the transmitting the timer end value may comprise transmitting the timer end value in a dedicated signal.

[0041] In an aspect, the dedicated signal may comprise a RRCRelease message containing the timer end value.

[0042] In an aspect, the transmitting the timer value may comprise transmitting the time value in a broadcast signal.

[0043] In an aspect, the broadcast signal may comprise a system information block (SIB) containing the timer end value.

[0044] In an aspect, the timer end value may be statically defined in a standard..

[0045] In an aspect, the method may further comprise starting a timer based on one of: transmitting a LP-WUS to the UE, or transmitting a paging to the UE.

[0046] In an aspect, the method may further comprise waiting for a paging response from the UE on at least one of the at least one second carrier while the timer is running..

[0047] In an aspect, the method may further comprise, stopping the timer based on receiving a paging response from the UE.

[0048] In an aspect, the timer may have a same end value as the timer end value transmitted to the UE.

[0049] In an aspect, the method may further comprise: determining the timer end value based on duration for UE to wake-up, duration of paging occasion, and time allotted for paging response.

[0050] In an aspect, an apparatus includes at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to perform any one of the preceding methods.

[0051] In an aspect, a non-transitory processor-readable medium stores instructions which, when executed by at least one processor of an apparatus, causes the apparatus to perform any one of the preceding methods.

[0052] In accordance with aspects of the disclosure, a method in a user equipment (UE), comprising: configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier; starting a counter; and in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0053] In an aspect, an indication of at least one second carrier may comprise at least one of: indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0054] In an aspect, the paging may be addressing the UE when a paging message of the paging includes an identifier of the UE.

[0055] In an aspect, the identifier may be S-TMSI (Temporary Mobile Subscription Identifier).

[0056] In an aspect, the identifier may be l-RNTI (Inactive Radio Network Temporary Identifier).

[0057] In an aspect, the first carrier and the at least one second carrier have different frequencies.

[0058] In an aspect, the first carrier and the at least one second carrier are in different bands.

[0059] In an aspect, the first carrier is provided by a serving cell serving the UE, and the at least one second carrier is provided by at least one second cell.

[0060] In an aspect, a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0061] In an aspect, a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0062] In an aspect, the attempting to respond to the paging on at least one of the at least one second carrier occurs only while the timer is running.

[0063] In an aspect, the counter may be started based on at least one of: receiving the LP-WUS, receiving the paging addressing the UE, transmitting a message on at least one of the at least one second carrier, or upon selection of a new carrier for responding to the paging.

[0064] In an aspect, the message may be a common control channel (CCCH) message.

[0065] In an aspect, the CCCH message may comprise one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0066] In an aspect, the attempting to respond to the paging on at least one of the at least one second carrier while the value of the counter is below the limit value may comprise at least one of: selecting a cell on at least one of the at least one second carrier, reselecting to a cell on at least one of the at least one second carrier, initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier, initiating an RRC Resume Request on at least one of the at least one second carrier, initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, or responding to the paging on at least one of the at least one second carrier.

[0067] In an aspect, the method may further comprise stopping the counter

[0068] In an aspect, the counter may be stopped based on at least one of: transmission of an RRCSetupRequest message, transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT), transmission of an RRCResumeRequestl message whenresume procedure is not initiated for SDT, transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0069] In an aspect, the counter may be stopped based on at least one of: reception of a RRCResume message, reception of an RRCSetup message, reception of an RRCRelease with suspendConfig message, reception of a RRCReject message.

[0070] In an aspect, the counter may be stopped based on at least one of: successfully completing contention resolution in random access procedure, aborting connection establishment by upper layers, cell selection on at least one of the at least one second carrier, cell re-selection on at least one of the at least one second carrier, or determining that access is barred on the at least one second carrier.

[0071] In an aspect, the method may further comprise, after the counter is stopped, at least one of: attempting to select the first carrier, attempting to re-select the first carrier, attempting to re-select to one of configured carriers, or entering into idle mode from inactive mode .

[0072] In an aspect, the method may further comprise, after the timer is stopped, at least one of: stopping attempting to respond to the paging, continuing attempting to respond to the paging on the first carrier, or stopping monitoring for a LP-WUS for period of time.

[0073] In an aspect, the method may further comprise, receiving, from a network apparatus, a counter limit value.

[0074] In an aspect, receiving the counter limit value may comprise receiving the counter limit value in a dedicated signal.

[0075] In an aspect, the dedicated signal may comprise a RRCRelease message containing the counter limit value.

[0076] In an aspect, the receiving the counter limit value may comprise receiving the counter limit value in a broadcast signal.

[0077] In an aspect, the broadcast signal may comprise a system information block (SIB) containing the counter limit value.

[0078] In an aspect, the counter limit value may be statically defined in a standard.

[0079] In an aspect, the counter may count at least one of: number of random access procedure attempts for which a random access response was not received, number of random access procedure attempts for which a random access response was not received on at least one of the at least one second carrier, failed contention resolutions for random access procedure, or number of carriers used for attempted paging responses.

[0080] In an aspect, the at least one second carrier may comprise a plurality of carriers, and each of the plurality of carriers may have different random access channel (RACH) configurations.

[0081] In an aspect, the different RACH configurations may comprise different numbers of RACH occasions for a time.

[0082] In an aspect, the method may further comprise, counting paging occasions in at least one of the at least one second carrier by incrementing the counter for each paging occasion in the at least one of the at least one second carrier.

[0083] In an aspect, an apparatus includes at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to perform any one of the preceding methods.

[0084] In an aspect, a non-transitory processor-readable medium stores instructions which, when executed by at least one processor of an apparatus, causes the apparatus to perform any one of the preceding methods.

[0085] In accordance with aspects of the disclosure, a method in a network apparatus, comprising: transmitting, to a user equipment (UE), a counter limit value, wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier, wherein the counter limit value is configured to cause the UE to run a counter for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0086] In an aspect, an indication of at least one second carrier may comprise at least one of: indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0087] In an aspect, the paging may be addressing the UE when a paging message of the paging includes an identifier of the UE.

[0088] In an aspect, the identifier may be S-TMSI (Temporary Mobile Subscription Identifier).

[0089] In an aspect, the identifier may be l-RNTI (Inactive Radio Network Temporary Identifier).

[0090] In an aspect, the transmitting the counter limit value may comprise transmitting the counter limit value in a dedicated signal.

[0091] In an aspect, the dedicated signal may comprise a RRCRelease message containing the counter limit value.

[0092] In an aspect, the transmitting the counter limit value may comprise transmitting the counter limit value in a broadcast signal.

[0093] In an aspect, the broadcast signal may comprise a system information block (SIB) containing the counter limit value.

[0094] In an aspect, the counter limit value may be statically defined in a standard..

[0095] In an aspect, the method may further comprise starting a counter based on one of: transmitting a LP-WUS to the UE, or transmitting a paging to the UE.

[0096] In an aspect, the method may further comprise waiting for a paging response from the UE on at least one of the at least one second carrier while the counter is running.

[0097] In an aspect, the method may further comprise, stopping the counter based on receiving a paging response from the UE.

[0098] In an aspect, the counter may have a same limit value as the counter limit value transmitted to the UE.

[0099] In an aspect, an apparatus includes at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to perform any one of the preceding methods.

[0100] In an aspect, a non-transitory processor-readable medium stores instructions which, when executed by at least one processor of an apparatus, causes the apparatus to perform any one of the preceding methods.

[0101] According to some aspects, there is provided the subject matter of the independent claims and of the Examples. Some further aspects are defined in the dependent claims and in the Examples.BRIEF DESCRIPTION OF THE DRAWINGS

[0102] Some example embodiments will now be described with reference to the accompanying drawings.

[0103] FIG. 1 is a diagram of an example embodiment ofwireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0104] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0105] FIG. 3 is a diagram of an example embodimentof a contention-based random access procedure, according to one illustrated aspect of the disclosure;

[0106] FIG. 4 is a diagram of an example embodiment of a main radio and a low-power wake-up receiver of a UE, according to one illustrated aspect of the disclosure;

[0107] FIG. 5 is a diagram of an example of operations for receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier, according to one illustrated aspect of the disclosure;

[0108] FIG. 6 is a diagram of an example of operations for receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier where the attempt is successful, according to one illustrated aspect of the disclosure;

[0109] FIG. 7 is a diagram including a example of operations receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier where the attempt is unsuccessful, according to one illustrated aspect of the disclosure; and

[0110] FIG. 8 is a diagram of an example of components of a user equipment or of a network apparatus, according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0111] The present disclosure relates to configurations for receiving a low-power wake up signal (LP-WUS) and paging on a first carrier and for responding to the paging on a second carrier.

[0112] Wireless systems (e.g., 5G systems) are designed and developed for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, user equipment (UE) energy efficiency is also important to such systems. Currently, user equipment may have to be recharged per week or day, depending on individual’s usage time. In general, UEs consume tens of milliwatts in RRC idle / inactive state and hundreds of milliwatts in radio resource control (RRC) connected state. Designs to prolong battery life are important for improving energy efficiency as well as for better user experience.

[0113] Energy efficiency is even more important for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators can be deployed extensively for monitoring, measuring, and / or charging, etc. Generally, their batteries are not rechargeable and are expected to last at least a few years, as described in 3rd Generation Partnership Project (3GPP) Technical Report (TR) 38.875. Wearable UEs include smartwatches, rings, eHealth related devices, and medical monitoring devices, among others. With typical battery capacity, it is challenging to sustain such UEs up to 1-2 weeks.

[0114] The power consumption depends in part on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, long eDRX (extended discontinuous reception) cycle may be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment use case, fire shutters shall be closed and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, and long eDRX cycle cannot meet such requirements. Thus, eDRX is apparently not suitable for latency-critical use cases.

[0115] In RRC IDLE / INACTIVE modes, significant UE power saving gain (up to more than 90%) is obtained by using LP-WUS (received by a low-power wake up receiver (LP-WUR) to trigger a UE’s main radio (MR) paging monitoring, compared with idle mode DRX (l-DRX) operation (with and without paging early indication (PEI)), if sufficient relaxation to MR radio resource management (RRM) measurement is applied. As used herein the term “relaxation” with respect to measurements means and refers to taking measurements less frequently than would normally occur. Further, compared with existing eDRX operation, significant paging latency reduction and moderate UE power saving gain is achieved, if LP-WUS monitoringand the corresponding paging monitoring after MR wake-up is performed not restricted within existing paging time window (PTW) of eDRX.

[0116] In RRC CONNECTED mode, moderate UE power saving gain (up to more than 10%) can be obtained with marginal impact to capacity by using LP-WUS / WUR to trigger UE MR physical downlink control channel (PDCCH) monitoring, compared with UE power saving techniques, across different types of extended reality (XR) traffic and system load scenarios. Significant UE power saving gain (up to more than 60%) and moderate user perceived throughput (UPT) improvement (up to more than 10%) is obtained for file transfer protocol (FTP) and instant messaging (IM) traffic, when the UE MR enters deep sleep state during LP-WUS monitoring. Furthermore, 3GPP Rel-18 study indicated the feasibility of serving cell RRM measurement offloading from UE MR to LP-WUR by reasonable evaluation methodology. Thus, it is proposed to specify LP-WUS / WUR in 3GPP Rel-19.

[0117] In aspects, the present disclosure enables use of a low-power wake-up receiver (LP-WUR) at the UE, instead of using the main radio (MR), in certain situations, so that UE can reduce power consumption.

[0118] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0119] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0120] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.11ax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0121] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit toward,” “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may notinvolve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0122] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0123] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0124] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0125] A gNB supports various protocol layers, e.g., Layer 1 (L1) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0126] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.:o The physical layer offers to the MAC sublayer transport channels;o The MAC sublayer offers to the RLC sublayer logical channels;o The RLC sublayer offers to the PDCP sublayer RLC channels;o The PDCP sublayer offers to the SDAP sublayer radio bearers;o The SDAP sublayer offers to 5GC quality of service (QoS) flows;o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0127] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0128] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the F1 interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0129] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0130] A gNB-CU-Control Plane (gNB-CU-CP) includes, e.g., a logical node hosting, e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the E1 interface connected with the gNB-CU-User Plane (gNB-CU-UP) and the F1-C interface connected with the gNB-DU.

[0131] A gNB-CU-User Plane (gNB-CU-UP) includes, e.g., a logical node hosting, e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1, which is hereby incorporated by reference herein.

[0132] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, or a gNB-CU-UP, or any combination of them.

[0133] A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 8 below.

[0134] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof.Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0135] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0136] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 6. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0137] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0138] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0139] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”,and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0140] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0141] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility management function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0142] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0143] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0144] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0145] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0146] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user(e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0147] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0148] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0149] A procedure for a UE to establish communications with a target cell is referred to as random access procedure. Random access procedure may be used for initial access, small data transmissions in inactive and transition from RRCJnactive to RRC_Connected, as well as in beam failure recovery, connection re-establishment, handover, and cell addition, among other procedures which persons skilled in the art will recognize.

[0150] Two types of random access procedures include contention-based random access (CBRA) and contention-free random access (CFRA). FIG. 3 is a diagram of an example of a contention-based random access (CBRA) procedure. In the illustrated example, the signals include a random access preamble (MSG1) transmitted by the UE 350 towards the network node 310 (e.g., gNodeB, or part thereof), a random access response (MSG2) transmitted from the network node 310 towards the UE 350, a schedule transmission (MSG3) transmitted from the UE 350 towards the network node 310, and a contention resolution (MSG4) transmitted from the network node 310 towards the UE 350.

[0151] For MSG1, the UE 350 selects a usable random access preamble based on information elements in a signal synchronization block (SSB). The UE 350 sends the random access preamble (MSG1) towards the network node 310 using a specific time and frequency resource known as random access occasion (RO). The UE 350 also provides an identity, called random access radio network temporary identity (RA-RNTI), to the network so that the network can address it in the next step.

[0152] For MSG2, the network node 310 detects the preamble, calculates various quantities, and sends a physical uplink shared channel (PUSCH) uplink (UL) grant towards the UE 350. This is called the randomaccess response (RAR), which is sent as MSG2 addressed to the UE 350 with the relevant RA-RNTI and indicates to the UE 350 where in frequency and when in time it can transmit MSG3 on the PUSCH.

[0153] For MSG3, in response to receiving the MSG2 from the network node 310, the UE 350 sends MSG3 using the UL grant provided in the RAR. Because the RAR provides a time resource allocation, the UE 350 sends MSG3 towards the network node 310 at a timing specified by the time resource allocation and is a scheduled transmission. This MSG3 may be called a radio resource control (RRC) connection request message.

[0154] For MSG4, the network node 310 may send MSG4 towards the UE 350 for contention resolution. Contention resolution may operate in the manner specified by 3GPP for 5G NR. After the random access procedure, assuming contention resolution is resolved favorably, the UE 350 becomes connected to the network node 310. After establishing a connection, various procedures would be handled by a gNB-CU in accordance with the CU-DU split. Other aspects of contention-based random access (CBRA) will be understood by persons skilled in the art.

[0155] Another type of random access procedure is contention-free random access (CFRA) (not shown). In CFRA (not shown), the network node 310 transmits an allocated random access preamble towards the UE 350. The UE 350 receives the allocated random access preamble and sends the random access preamble to the network node 310 in a random access request as MSG1. Then, MSG2 and MSG3 are similar to those described in connection with CBRA. No conflict resolution is needed in CFRA based on use of an allocated random access preamble. Other aspects of contention-free random access (CFRA) will be understood by persons skilled in the art.

[0156] As mentioned above, in accordance with aspects of the present disclosure, the present disclosure relates to configurations for receiving a low-power wake up signal (LP-WUS) and paging on a first carrier and for responding to the paging on a second carrier.

[0157] Referring now to FIG. 4, there is shown a block diagram of a UE that includes a main radio 410 and a low-power wake up receiver 420. In aspects of the present disclosure, the main radio (MR) 410 of the UE can be in a sleep mode or deep sleep mode or powered off, for power saving, and can be activated only upon the LP-WUR 420 receiving a wake-up signal from the network. The network may trigger the UE to wake-up the main radio 410, when needed, in an event-driven manner by transmitting a wake-up signal to the UE, which monitors for the LP-WUS by using the LP-WUR 420. When the UE receives the LP-WUS, the LP-WUR 420 can trigger the wake-up of the MR transceiver, and communication using the MR can start. Thus, the LP-WUR 420 wakes up the main radio 410, but otherwise, the main radio 410 may be OFF or kept in a deep sleep mode, as shown in FIG. 4.

[0158] In aspects, possible transition times for moving the MR 410 from deep sleep to ON may be in the range of 400ms - 800ms, or even longer. Hence, in some embodiments, MR ramp-up time from deep sleep state can be quite long. In embodiments, other time durations are contemplated.

[0159] In aspects, the low-power wake-up receiver can be operated in an always “on” manner with very low power consumption. In embodiments, by using a simple wake-up signal and by using specialized hardware for its monitoring, which is able to receive the WUS, the LP-WUR 420 can consume significantly less power compared to the MR 410.

[0001] Different types of LP-WUR 420 may include envelope detectors and sequence detectors. An envelope detector is capable of detecting ON / OFF keying, has no IQ branch to perform coherent / sequence detection, and can receive LP-WUS and a low-power synchronization signal (LP-SS). A sequence detector uses IQ branches to perform coherent detection, consumes more power due to the better accuracy of crystal oscillators (XO) used to drive the phase locked loops (PLL), and can receive also system synchronization blocks (SSB) in addition to LP-WUS. In embodiments, different types of LP-WUR 420 may include orthogonal frequency division multiplexing (OFDM) based LP-WUR capable of detecting and measuring PSS / SSS signal. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0160] In embodiments, the MR 410 and the LP-WUR 420 may be the same physical receiver but may be logically different. In embodiments, the LP-WUR 420 can be implemented as a separate receiver. In embodiments, the LP-WUR 420 may be implemented as a low power mode of the MR 410. For example, when the LP-WUR 420 is capable of detecting and measuring SSS and / or PSS / SSS, the LP-WUR 420 and the MR 410 may measure the same reference signal. Implementing LP-WUR 420 as a low power mode of the MR 410 reduces the implementation complexity and allows UE to share easily information between MR and LP-WUR, as they are implemented within the same receiver / module. This may, for example, reduce the wakeup / synchronization time of the UE and increase LP-WUR accuracy (e.g. as better components may be used).

[0161] The combination of a main radio 410 and a LP-WUR 420 may be beneficial in other ways. For example, in embodiments, serving cell evaluations could be offloaded from the MR 410 to the LP-WUR 420 to enable large power saving. The LP-WUR 420 can carry the serving cell evaluation related measurements based on a low-power synchronization signal (LP-SS) or based on SSB, depending on the type of LP-WUR, as described above. In embodiments, only serving cell evaluations are offloaded to the LP-WUR 420, as the coverage of the LP-SS and the LP-SUR 420 are limited.

[0162] FIG. 4 and the description above provide merely an example, and variations are contemplated to be within the scope of the present disclosure.

[0163] FIG. 5 shows an example of operations for receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier.

[0164] The diagram assumes that the UE has a main radio and a LP-WUR, as shown in FIG. 4, and is configured to monitor for a LP-WUS and a paging on a first carrier and configured to attempt to respond to the paging on a second carrier. In embodiments, the first carrier and the second carrier have differentfrequencies. In embodiments, the first carrier and the second carrier may be in different bands. In embodiments, the first carrier may be provided by a serving cell serving the UE, and the second carrier may be provided a second cell different from the serving cell. In embodiments, the cell providing the first carrier and the cell providing the second carrier are provided by different base stations. In embodiments, the cell providing the first carrier and the cell providing the second carrier are in different bands.

[0165] In a first time period 510, the MR is in deep sleep, and the LP-WUR monitors for a LP-WUS and detects a LP-WUS. After the LP-WUR detects a LP-WUS, the LP-WUR triggers the MR to wake up, e.g., as shown in FIG. 4. At time period 522, the MR turns on and performs synchronization for the first carrier. Then, at time period 524, the MR monitors for a paging which is addressed to the UE, on the first carrier, and detects a paging. In embodiments, the network initiates the paging procedure by transmitting a paging message at the UE's paging occasion (PO). The network may address multiple UEs within a paging message by including one PagingRecord for each UE of the multiple UEs.

[0166] After the MR detects a paging addressed to the UE on the first carrier, the UE, as configured, attempts to respond to the paging, received on the first carrier, on the second carrier. At time period 532, the UE, using the main radio, performs cell (re)selection and synchronization on the second carrier. At time period 534, the UE, using the main radio, receives system information block 1 (SIB1), on the second carrier. At time period 536, the UE, using the main radio, performs random access procedure on the second carrier, e.g., transmits a random access preamble. There is a possibility that the random access procedure may fail, for example, because channel conditions for the second carrier may be poor or due to congestion, among other reasons. Such issues are addressed in the description below in connection with FIG. 6.

[0167] FIG. 5 and the description above are merely examples, and variations are contemplated to be within the scope of the present disclosure.

[0168] With regard to the operation of FIG. 5, a potential issue is that the coverage of the first carrier and the coverage of the second carrier may be different, and there may be delay after paging since the UE needs to select the second carrier for responding to the paging.

[0169] Additional issues may result from the UE not being knowledgeable about the second carrier’s conditions, e.g., if the UE is not measuring the second carrier. For example, the radio condition of the (last used) cell in second carrier may not be good enough anymore for providing access. Hence, the transmission of the paging response is not possible or transmission of the paging response may fail or RRC connection establishment or RRC resume fails. Also, if the UE is not able to detect any cell on the second carrier, then an issue is how long the UE should attempt to respond to the paging. Other issues exist, as well.

[0170] Various solutions are described below in connection with FIG. 6 and FIG. 7, which describe using a timer or a counter to determine when a UE should still attempt to respond to paging on the second carrier, and when the UE should take another action, instead. In embodiments, various operations may include oneor more timers. Examples of timers are described in 3GPP TS 3GPP TS 38.331 , which is hereby incorporated by reference herein, and include:

[0171] FIG. 6 is a flow diagram of an example of operations for receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier, where the attempt is successful. The operations are performed by the components shown at the top of FIG. 6, which, in the illustrated example, include a user equipment (UE), a RAN node (e.g., gNB) operating in band 1, and the RAN node (e.g., gNB) operating in band 2. Such components may be, for example, the same components described in connection with FIG. 1 and FIG. 2 or otherwise described above. The components are merely examples, and there may be two different RAN nodes (e.g., gNB and gNB2) instead of only a single RAN node (e.g. gNB).

[0172] FIG. 6 assumes that the UE has a main radio and a LP-WUR, as shown in FIG. 4.

[0173] At operation 601 , the UE is in RRC-idle mode or RRC-inactive mode and is served by the RAN node (e.g., gNB) using band 1.

[0174] After operation 602, the UE is configured to monitor for a LP-WUS and for a paging on a first carrier and to respond to a paging, received on the first carrier, on a second carrier, e.g., in band 2 of the RAN node.

[0175] In connection with operations 603-613, the UE and / or the network may start and / or stop a timer and / or increment a counter, to determine when a UE should still attempt to respond to paging on the second carrier, and when the UE should take another action, instead. The various aspects relating to a timer and / or a counter will be described farther below.

[0176] At operation 603, the UE monitors for a LP-WUS on the first carrier, e.g., using a LP-WUR (e.g., 420, FIG. 4).

[0177] At operation 604, the RAN node transmits a LP-WUS to the UE, and the UE receives the LP-WUS from the RAN node. In embodiments, as described in connection with FIG. 4, the LP-WUS is received by the LP-WUR.

[0178] At operation 605, the LP-WUS triggers the MR of the UE to wake up and to monitor for paging on the first carrier.

[0179] At operation 606, the RAN node transmits to the UE a paging addressing the UE, and the UE receives the paging from the first RAN node. In embodiments, the paging addresses the UE by a paging message including a UE identifier that addresses the UE. In embodiments, the UE identifier may be a temporary mobile subscription identifier (S-TMSI). In embodiments, the UE identifier may be an inactive radio network temporary identifier (l-RNTI).

[0180] At operation 607, the UE determines to respond to the paging, received on the first carrier, on the second carrier, which the UE was configured to do in operation 602.

[0181] At operation 608, the UE evaluates cell selection or cell reselection conditions for the second carrier. In the illustrated embodiment, the UE evaluates the conditions for the second carrier of the RAN node (in band 2). The UE determines that cell selection or reselection conditions for the second carrier (e.g., gNB2, band 2) are satisfied.

[0182] At operation 609, the UE initiates attempting to respond to the paging, received on the first carrier, on the second carrier (e.g., gNB2, band 2). In the illustrated embodiment, the UE initiates RRC Setup Request or RRC Resume procedure.

[0183] At operation 610, the UE transmits an RRC Setup or Resume Request message to the RAN node on the second carrier (e.g., gNB2, band 2), and the RAN node receives the message from the UE.

[0184] At operation 611 , the RAN node transmits a RRC Setup or Resume message to the UE, and the UE receives the RRC Setup or Resume message from the RAN node.

[0185] At operation 612, the UE transmits an RRC Setup or Resume Complete message to the RAN node (e.g., gNB2, band 2), and the RAN node receives the message from the UE.

[0186] At operation 613, the UE transmits an paging response (e.g., non-access-stratum (NAS) message) to the RAN node (e.g., gNB2, band 2), and the RAN node receives the paging response from the UE.

[0187] Various embodiments relating to a timer will now be described.

[0188] In embodiments, a UE timer (e.g., T3XX) is started when the UE is configured to respond to paging on another carrier (condition to start T3XX) than where the UE is camped, and one or more of:■ LP-WUS is received (e.g., operation 604);■ paging addressing the UE is received (e.g., operation 605); and / or■ upon first transmitting a message (for example, the common control channel (CCCH) message (e.g., RRC Setup Request or RRC Resume Request)) on the second carrier (e.g., operation 610).

[0189] In embodiments, while a UE timer (e.g., T3XX) is running, the UE may attempt to perform one or more of:■ Select a cell on another carrier / frequency / band (e.g., operation 608);■ Reselect to a cell on another carrier / frequency / band (e.g., operation 608);■ Initiate RRC Setup Request on another carrier / frequency / band / cell (e.g., operation 609);■ Initiate RRC Resume Request on another carrier / frequency / band / cell (e.g., operation 609);■ Initiate RRC Resume Request for SDT on another carrier / frequency / band / cell (e.g., operation 609); and / or■ Respond to paging on another carrier / frequency / band / cell (e.g., operation 613).

[0190] In embodiments, a UE timer (e.g., T3XX) can be stopped based on one or more of:■ Upon timer T300 or T319 or T319a being started;■ Upon transmission of RRCSetupRequest (e.g., operation 610);■ Upon transmission of RRCResumeRequest or RRCResumeRequestl when the resume procedure is not initiated for SDT (e.g., operation 610);■ Upon transmission of RRCResumeRequest or RRCResumeRequestl when the resume procedure is initiated for SDT (e.g., operation 610);■ Upon transmission of the paging response (NAS message) (e.g., operation 613);■ Upon reception of the RRCResume (e.g., operation 611);■ Upon reception of the RRC Setup (e.g., operation 611);■ RRCRelease with suspendConfig;■ RRCReject;■ Random access contention resolution is successfully completed;■ Upon aborting of connection establishment by upper layers;■ Upon cell selection or re-selection on another carrier / frequency / band / cell (e.g., operation 608); and / or■ Upon determination that access is barred on the selected or re-selected carrier / frequency / band / cell.

[0191] In embodiments, when a UE timer (e.g., T3XX) is stopped / expired, the UE may perform one or more of the following:■ UE attempts to select or re-select back cell / carrier / band / frequency where LP-WUS / Paging was received (e.g., first carrier);■ UE goes to RRC-idle mode from RRC-inactive mode;■ UE stops (or considers stopped) timer T300, T319 or T319a or T302;■ UE stops attempting to respond the paging;■ UE continues attempting to respond to the paging on other cell / carrier / band / frequency;and / or■ UE does not monitor for LP-WUS for a period of time.

[0192] In embodiments, the UE may receive (and the network may transmit) a timer end value in a dedicated signal, such as in a RRC release message received by the UE.

[0193] In embodiments, the UE may receive (and the network may transmit) the timer end value in a broadcast signal, such as in a system information block (SIB).

[0194] In embodiments, the timer end value may be statically defined in a specification.

[0195] In embodiments, the timer end value may be expressed in milliseconds, seconds, or minutes.

[0196] In embodiments, the network may maintain a network timer, which can be initiated upon transmitting a LP-WUS or a paging message.

[0197] Upon starting the network timer, the network may initiates a wait procedure on the second carrier for paging response. The timer end value of the network timer may be defined statically or based on specified values.

[0198] The network timer may expire when the network receives a paging response messages from the UE.

[0199] The network timer may expire when a time is reach when the UE is supposed to connect to the network. For example, the timer end value can be determined based on duration for UE wake up + duration of paging occasion + duration paging response. If the paging is the starting point for the timer, then duration for paging occasion = Oms.

[0200] In embodiments, the network timer can be set to a same timer end value as the timer (e.g., T3XX timer) on the UE, and the network timer may follows similar triggers as UE (described above), but on message transmission side.

[0201] Various embodiments relating to a counter will now be described.

[0202] In embodiments, a counter is introduced to stop the timer and / or process.

[0203] In embodiments, the counter can be defined for and can count number of random access procedure (RACH) attempts for which a random access response (RAR) was not received, failed random access contention resolutions, and / or number of attempted carriers for responding to paging.

[0204] In embodiments, a counter can be considered in scenarios where the UE has multiple carriers to select from for the RACH transmission, and these carriers could have different RACH configurations (e.g., less / more RACH occasions for a time).

[0205] In embodiments, the counter can count paging occasions on another carrier / band / frequency as the LP-WUS was received, e.g., count paging occasions on the second carrier. For example, if paging was not received at a paging occasion according to paging configurations (e.g. consecutive, every second), then the value of the counter is increased (e.g., by 1).

[0206] In embodiments, when the number of counted paging occasions reaches a counter limit value, the UE may perform fallback behavior. For example, the UE may fall back to LP-WUS frequency (e.g., first carrier) and monitor for paging on the first carrier, or the UE may initiate RACH procedure, or the UE may stop monitoring for LP-WUS.

[0207] In embodiments, the counter is associated with different carrier / band / frequency as the LP-WUS signal is received, e.g., the counter is associated with the second carrier. For example, the counter may count RACH attempts on another frequency as the LP-WUS, e.g., the counter may count RACH attempts on the second carrier. If the counter limit value is reached, the UE may perform RACH on the same carrier where LP-WUS was received, e.g., perform RACH on the first carrier.

[0208] The operations of FIG. 6 will now be described from various perspectives.

[0209] From the perspective of a UE, the operations include: configuring to monitor for a low-power wake-up signal (LP-WUS) and for paging on a first carrier and to respond to the paging on at least one second carrier (e.g., operation 602); starting a timer (e.g., various operations as described); and in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while the timer is running (e.g., operation 613).

[0210] From the perspective of a UE, the operations include: configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier (e.g., operation 602); starting a counter (e.g., various operations as described); and in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value (e.g., operation 613).

[0211] From the perspective of a RAN node, the operations include: transmitting, to a user equipment (UE), a timer end value (e.g., during operation 601 ), wherein the UE is configured to monitor for a low-powerwake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier, wherein the timer end value is configured to cause the UE to run a timer for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0212] From the perspective of a RAN node, the operations include: transmitting, to a user equipment (UE), a counter limit value (e.g., during operation 601), wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier, wherein the counter limit value is configured to cause the UE to run a counter for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0213] FIG. 6 and the description above are merely examples, and variations are contemplated to be within the scope of the present disclosure.

[0214] FIG. 7 is a flow diagram of an example of operations for receiving a LP-WUS and a paging on a first carrier and for attempting to respond to the paging on a second carrier, where the attempt is unsuccessful. The operations are performed by the components shown at the top of FIG. 7, which, in the illustrated example, include a user equipment (UE), a RAN node (e.g., gNB) operating in band 1, and the RAN node (e.g., gNB) operating in band 2. Such components may be, for example, the same components described in connection with FIG. 1 and FIG. 2 or otherwise described above. The components are merely examples, and there may be two different RAN nodes (e.g., gNB and gNB2) instead of only a single RAN node (e.g. gNB).

[0215] FIG. 7 also assumes that the UE has a main radio and a LP-WUR, as shown in FIG. 4.

[0216] At operation 701 , the UE is in RRC-idle mode or RRC-inactive mode and is served by the RAN node (e.g., gNB) using band 1.

[0217] After operation 702, the UE is configured to monitor for a LP-WUS and for a paging on a first carrier and to respond to a paging, received on the first carrier, on a second carrier, e.g., in band 2 of the RAN node.

[0218] In connection with operations 703-711, the UE and / or the network may start and / or stop a timer and / or increment a counter, in the same manner described in connection with FIG. 6. Such description relating to a timer and / or a counter is incorporated by reference into this section as though applied to the operations of FIG. 7.

[0219] At operation 703, the UE monitors for a LP-WUS on the first carrier, e.g., using a LP-WUR (e.g., 420, FIG. 4).

[0220] At operation 704, the RAN node transmits a LP-WUS to the UE, and the UE receives the LP-WUS from the RAN node. In embodiments, as described in connection with FIG. 4, the LP-WUS is received by the LP-WUR.

[0221] At operation 705, the LP-WUS triggers the MR of the UE to wake up and to monitor for paging on the first carrier.

[0222] At operation 706, the RAN node transmits to the UE a paging addressing the UE, and the UE receives the paging from the first RAN node. In embodiments, the paging addresses the UE by a paging message including a UE identifier that addresses the UE. In embodiments, the UE identifier may be a temporary mobile subscription identifier (S-TMSI). In embodiments, the UE identifier may be an inactive radio network temporary identifier (l-RNTI).

[0223] At operation 707, the UE determines to respond to the paging, received on the first carrier, on the second carrier, which the UE was configured to do in operation 702.

[0224] At operation 708, the UE attempts cell selection or cell reselection conditions for the second carrier. The UE can evaluate the conditions for the second carrier of the RAN node (in band 2) and determines that cell selection or reselection conditions for the second carrier (e.g., gNB2, band 2) are satisfied.

[0225] At operation 709, the UE determines that the timer has expired or that the counter has reached a limit value.

[0226] At operation 710, upon or after the timer has expired or the counter has reached a limit value, the UE performs one or more of the following: the UE can attempt to select or reselect the first carrier, where the LP-WUS and the paging were received; or the UE goes into RRC-idle mode from RRC-inactive mode, or the UE stops the timer or the counter, or the UE stops attempting to respond to the paging, or the UE continues attempting to respond to the paging on the second carrier.

[0227] The operations of FIG. 7 are merely examples, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include others not illustrated in FIG. 7. In embodiments, the operations may be performed by different blocks than those illustrated in FIG. 7 and / or by other blocks not illustrated in FIG. 7. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0228] Referring now to FIG. 8, there is shown a block diagram of example components of a UE or a network apparatus. The apparatus includes an electronic storage (e.g., non-transitory processor-readable medium) 810, a processor 820, a memory 850, and a network interface 840. The various components may be communicatively coupled with each other. The processor 820 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 850 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 850 includes processor-readable instructions that are executable by the processor 820 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations of FIGS.3-7.

[0229] The electronic storage 810 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, and / or optical disc, among other types of electronic storage. The electronic storage 810 stores processor-readable instructions for causing the apparatus to perform its operations and stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 840 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[0230] The components shown in FIG. 8 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may include multiples of any of the illustrated components. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0231] Further embodiments of the present disclosure include the following examples. In the following, any “means” may be implemented by at least one processor and processor-executable instructions, unless the context indicates otherwise. Any “means” for receiving or transmitting may be implemented by a transceiver. The notation Example n.x refers to any Example having a value for n and a value for x.

[0232] Example 1.1. A method in a user equipment (UE), comprising:configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier;starting a counter; andin response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0233] Example 1.2. The method of Example 1.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0234] Example 1.3. The method of Example 1.1 or 1.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0235] Example 1.4. The method of Example 1.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0236] Example 1.5. The method of Example 1.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0237] Example 1.6. The method of any one of Examples 1.1-1.5, wherein the first carrier and the at least one second carrier have different frequencies.

[0238] Example 1.7. The method of any one of Examples 1.1-1.6, wherein the first carrier and the at least one second carrier are in different bands.

[0239] Example 1.8. The method of any one of Examples 1.1-1.7,wherein the first carrier is provided by a serving cell serving the UE, andwherein the at least one second carrier is provided by at least one second cell.

[0240] Example 1.9. The method of any one of Examples 1.1-1.8, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0241] Example 1.10. The method of any one of Examples 1.1-1.9, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0242] Example 1.11. The method of any one of Examples 1.1-1.10, wherein the attempting to respond to the paging on at least one of the at least one second carrier occurs only while the timer is running.

[0243] Example 1.12. The method of any one of Examples 1.1-1.11, wherein the timer is started based on at least one of:receiving the LP-WUS,receiving the paging addressing the UE,transmitting a message on at least one of the at least one second carrier, orupon selection of a new carrier for responding to the paging.

[0244] Example 1.13. The method of Example 1.12, wherein the message is a common control channel (CCCH) message.

[0245] Example 1.14. The method of Example 1.13, wherein the CCCH message comprises one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0246] Example 1.15. The method of any one of Examples 1.1-1.14, wherein the attempting to respond to the paging on at least one of the at least one second carrier while the timer is running comprises at least one of:selecting a cell on at least one of the at least one second carrier,reselecting to a cell on at least one of the at least one second carrier,initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier,initiating an RRC Resume Request on at least one of the at least one second carrier,initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, orresponding to the paging on at least one of the at least one second carrier.

[0247] Example 1.16. The method of any one of Examples 1.1-1.15, further comprising stopping the timer.

[0248] Example 1.17. The method of Example 1.16, wherein the timer is stopped based on at least one of:a T300 timer being started,a T319 timer being started, ora T319a time being started.

[0249] Example 1.18. The method of Example 1.16, wherein the timer is stopped based on at least one of:transmission of an RRCSetupRequest message,transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT),transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT,transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0250] Example 1.19. The method of Example 1.16, wherein the timer is stopped based on at least one of:reception of a RRCResume message,reception of an RRCSetup message,reception of an RRCRelease with suspendConfig message,reception of a RRCReject message.

[0251] Example 1.20. The method of Example 1.16, wherein the timer is stopped based on at least one of:successfully completing contention resolution in random access procedure,aborting connection establishment by upper layers,cell selection on at least one of the at least one second carrier,cell re-selection on at least one of the at least one second carrier, ordetermining that access is barred on the at least one second carrier.

[0252] Example 1.21. The method of any one of Examples 1.16-1.20, further comprising, after the timer is stopped, at least one of:attempting to select the first carrier,attempting to re-select the first carrier,attempting to re-select to one of configured carriers, orentering into idle mode from inactive mode .

[0253] Example 1.22. The method of any one of Examples 1.16-1.20, further comprising, after the timer is stopped, at least one of:stopping at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer, ortreating, as stopped, at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer.

[0254] Example 1.23. The method of any one of Examples 1.16-1.20, further comprising, after the timer is stopped, at least one of:stopping attempting to respond to the paging,continuing attempting to respond to the paging on the first carrier, orstopping monitoring for a LP-WUS for period of time.

[0255] Example 1.24. The method of any one of Examples 1.1-1.23, further comprising:receiving, from a network apparatus, a timer end value for the timer.

[0256] Example 1.25. The method of Example 1.24, wherein the receiving the timer end value comprises receiving the timer end value in a dedicated signal.

[0257] Example 1.26. The method of Example 1.25, wherein the dedicated signal comprises a RRCRelease message containing the timer end value.

[0258] Example 1.27. The method of Example 1.24, wherein the receiving the timer end value comprises receiving the timer end value in a broadcast signal.

[0259] Example 1.28. The method of Example 1.27, wherein the broadcast signal comprises a system information block (SIB) containing the timer end value.

[0260] Example 1.29. The method of Example 1.24, wherein the timer end value is statically defined in a standard.

[0261] Example 1.30. An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of Examples 1.1-1.29.

[0262] Example 1.31. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of Examples 1.1-1.29.

[0263] Example 2.1. A user equipment (UE), comprising:means for configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier;means for starting a counter; andmeans for, in response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0264] Example 2.2. The user equipment (UE) of Example 2.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0265] Example 2.3. The user equipment (UE) of Example 2.1 or 2.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0266] Example 2.4. The user equipment (UE) of Example 2.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0267] Example 2.5. The user equipment (UE) of Example 2.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0268] Example 2.6. The user equipment (UE) of any one of Examples 2.1-2.5, wherein the first carrier and the at least one second carrier have different frequencies.

[0269] Example 2.7. The user equipment (UE) of any one of Examples 2.1-2.6, wherein the first carrier and the at least one second carrier are in different bands.

[0270] Example 2.8. The user equipment (UE) of any one of Examples 2.1-2.7,wherein the first carrier is provided by a serving cell serving the UE, andwherein the at least one second carrier is provided by at least one second cell.

[0271] Example 2.9. The user equipment (UE) of any one of Examples 2.1-2.8, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0272] Example 2.10. The user equipment (UE) of any one of Examples 2.1-2.9, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0273] Example 2.11. The user equipment (UE) of any one of Examples 2.1-2.10, wherein the means for attempting to respond to the paging on at least one of the at least one second carrier occurs only while the timer is running.

[0274] Example 2.12. The user equipment (UE) of any one of Examples 2.1-2.11, wherein the timer is started based on at least one of:receiving the LP-WUS,receiving the paging addressing the UE,transmitting a message on at least one of the at least one second carrier, orupon selection of a new carrier for responding to the paging.

[0275] Example 2.13. The user equipment (UE) of Example 2.12, wherein the message is a common control channel (CCCH) message.

[0276] Example 2.14. The user equipment (UE) of Example 2.13, wherein the CCCH message comprises one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0277] Example 2.15. The user equipment (UE) of any one of Examples 2.1-2.14, wherein the means for attempting to respond to the paging on at least one of the at least one second carrier while the timer is running comprises at least one of:means for selecting a cell on at least one of the at least one second carrier,means for reselecting to a cell on at least one of the at least one second carrier,means for initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier,means for initiating an RRC Resume Request on at least one of the at least one second carrier, means for initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, ormeans for responding to the paging on at least one of the at least one second carrier.

[0278] Example 2.16. The user equipment (UE) of any one of Examples 2.1-2.15, further comprising means for stopping the timer.

[0279] Example 2.17. The user equipment (UE) of Example 2.16, wherein the timer is stopped based on at least one of:a T300 timer being started,a T319 timer being started, ora T319a time being started.

[0280] Example 2.18. The user equipment (UE) of Example 2.16, wherein the timer is stopped based on at least one of:transmission of an RRCSetupRequest message,transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT),transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT,transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0281] Example 2.19. The user equipment (UE) of Example 2.16, wherein the timer is stopped based on at least one of:reception of a RRCResume message,reception of an RRCSetup message,reception of an RRCRelease with suspendConfig message,reception of a RRCReject message.

[0282] Example 2.20. The user equipment (UE) of Example 2.16, wherein the timer is stopped based on at least one of:successfully completing contention resolution in random access procedure,aborting connection establishment by upper layers,cell selection on at least one of the at least one second carrier,cell re-selection on at least one of the at least one second carrier, ordetermining that access is barred on the at least one second carrier.

[0283] Example 2.21. The user equipment (UE) of any one of Examples 2.16-2.20, further comprising, after the timer is stopped, at least one of:means for attempting to select the first carrier,means for attempting to re-select the first carrier,means for attempting to re-select to one of configured carriers, ormeans for entering into idle mode from inactive mode .

[0284] Example 2.22. The user equipment (UE) of any one of Examples 2.16-2.20, further comprising, after the timer is stopped, at least one of:means for stopping at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer, or means for treating, as stopped, at least one of: a T300 timer, a T319 timer, a T319a timer, or a T302 timer.

[0285] Example 2.23. The user equipment (UE) of any one of Examples 2.16-2.20, further comprising, after the timer is stopped, at least one of:means for stopping attempting to respond to the paging,means for continuing attempting to respond to the paging on the first carrier, ormeans for stopping monitoring for a LP-WUS for period of time.

[0286] Example 2.24. The user equipment (UE) of any one of Examples 2.1-2.23, further comprising:means for receiving, from a network apparatus, a timer end value for the timer.

[0287] Example 2.25. The user equipment (UE) of Example 2.24, wherein the receiving the timer end value comprises means for receiving the timer end value in a dedicated signal.

[0288] Example 2.26. The user equipment (UE) of Example 2.25, wherein the dedicated signal comprises a RRCRelease message containing the timer end value.

[0289] Example 2.27. The user equipment (UE) of Example 2.24, wherein the receiving the timer end value comprises receiving the timer end value in a broadcast signal.

[0290] Example 2.28. The user equipment (UE) of Example 2.27, wherein the broadcast signal comprises a system information block (SIB) containing the timer end value.

[0291] Example 2.29. The user equipment (UE) of Example 2.24, wherein the timer end value is statically defined in a standard.

[0292] Example 3.1. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a timer end value,wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier,wherein the timer end value is configured to cause the UE to run a timer for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0293] Example 3.2. The method of Example 3.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0294] Example 3.3 The method of Example 3.1 or 3.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0295] Example 3.4 The method of Example 3.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0296] Example 3.5 The method of Example 3.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0297] Example 3.6 The method of any one of Examples 3.1-3.5, wherein the transmitting the timer end value comprises transmitting the timer end value in a dedicated signal.

[0298] Example 3.7 The method of Example 3.6, wherein the dedicated signal comprises a RRCRelease message containing the timer end value.

[0299] Example 3.8. The method of any one of Examples 3.1-3.5, wherein the transmitting the timer value comprises transmitting the time value in a broadcast signal.

[0300] Example 3.9. The method of Example 3.8, wherein the broadcast signal comprises a system information block (SIB) containing the timer end value.

[0301] Example 3.10. The method of any one of Examples 3.1-3.9, wherein the timer end value is statically defined in a standard.

[0302] Example 3.11. The method of any one of Examples 3.1-3.10, further comprising: starting a timer based on one of:transmitting a LP-WUS to the UE, ortransmitting a paging to the UE.

[0303] Example 3.12. The method of Example 3.11, further comprising:waiting for a paging response from the UE on at least one of the at least one second carrier while the timer is running.

[0304] Example 3.13. The method of Example 3.11 or 3.12, further comprising:stopping the timer based on receiving a paging response from the UE.

[0305] Example 3.14. The method of any one of Examples 3.11-3.13, wherein the timer has a same end value as the timer end value transmitted to the UE.

[0306] Example 3.15. The method of any one of Examples 3.1-3.14, further comprising:determining the timer end value based on duration for UE to wake-up, duration of paging occasion, and time allotted for paging response.

[0307] Example 3.16 An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of Examples 3.1-3.15.

[0308] Example 3.17. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of Examples 3.1-3.15.

[0309] Example 4.1. A network apparatus, comprising:means for transmitting, to a user equipment (UE), a timer end value,wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a means for paging on a first carrier and to respond to the paging on at least one second carrier, wherein the timer end value is configured to cause the UE to run a timer for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0310] Example 4.2. The network apparatus of Example 4.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0311] Example 4.3 The network apparatus of Example 4.1 or 4.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0312] Example 4.4 The network apparatus of Example 4.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0313] Example 4.5 The network apparatus of Example 4.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0314] Example 4.6 The network apparatus of any one of Examples 4.1-4.5, wherein the means for transmitting the timer end value comprises means for transmitting the timer end value in a dedicated signal.

[0315] Example 4.7 The network apparatus of Example 4.6, wherein the dedicated signal comprises a RRCRelease message containing the timer end value.

[0316] Example 4.8. The network apparatus of any one of Examples 4.1-4.5, wherein the transmitting the timer value comprises means for transmitting the time value in a broadcast signal.

[0317] Example 4.9. The network apparatus of Example 4.8, wherein the broadcast signal comprises a system information block (SIB) containing the timer end value.

[0318] Example 4.10. The network apparatus of any one of Examples 4.1-4.9, wherein the timer end value is statically defined in a standard.

[0319] Example 4.11. The network apparatus of any one of Examples 4.1-4.10, further comprising: starting a timer based on one of:means for transmitting a LP-WUS to the UE, ormeans for transmitting a paging to the UE.

[0320] Example 4.12. The network apparatus of Example 4.11, further comprising:means for waiting for a paging response from the UE on at least one of the at least one second carrier while the timer is running.

[0321] Example 4.14. The network apparatus of Example 4.11 or 4.12, further comprising:means for stopping the timer based on receiving a paging response from the UE.

[0322] Example 4.14. The network apparatus of any one of Examples 4.11-4.13, wherein the timer has a same end value as the timer end value transmitted to the UE.

[0323] Example 4.15. The network apparatus of any one of Examples 4.1-4.14, further comprising:means for determining the timer end value based on duration for UE to wake-up, duration of paging occasion, and time allotted for paging response.

[0324] Example 5.1. A method in a user equipment (UE), comprising:configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier;starting a counter; andin response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0325] Example 5.2. The method of Example 5.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging,indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0326] Example 5.3. The method of Example 5.1 or 5.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0327] Example 5.4. The method of Example 5.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0328] Example 5.5. The method of Example 5.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0329] Example 5.6. The method of any one of Examples 5.1-5.5, wherein the first carrier and the at least one second carrier have different frequencies.

[0330] Example 5.7. The method of any one of Examples 5.1-5.6, wherein the first carrier and the at least one second carrier are in different bands.

[0331] Example 5.8. The method of any one of Examples 5.1-5.7,wherein the first carrier is provided by a serving cell serving the UE, andwherein the at least one second carrier is provided by at least one second cell.

[0332] Example 5.9. The method of any one of Examples 5.1-5.8, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0333] Example 5.10. The method of any one of Examples 5.1-5.9, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0334] Example 5.11. The method of any one of Examples 5.1-5.10, wherein the attempting to respond to the paging on at least one of the at least one second carrier occurs only after the counter is started.

[0335] Example 5.12. The method of any one of Examples 5.1-5.11, wherein the counter is started based on at least one of:receiving the LP-WUS,receiving the paging addressing the UE,transmitting a message on at least one of the at least one second carrier,upon selecting a new carrier for responding to the paging.

[0336] Example 5.13. The method of Example 5.12, wherein the message is a common control channel (CCCH) message.

[0337] Example 5.14. The method of Example 5.13, wherein the CCCH message comprises one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0338] Example 5.15. The method of any one of Examples 5.1-5.14, wherein the attempting to respond to the paging on at least one of the at least one second carrier while the value of the counter is below the limit value comprises at least one of:selecting a cell on at least one of the at least one second carrier,reselecting to a cell on at least one of the at least one second carrier,initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier,initiating an RRC Resume Request on at least one of the at least one second carrier,initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, orresponding to the paging on at least one of the at least one second carrier.

[0339] Example 5.16. The method of any one of Examples 5.1-5.15, further comprising stopping the counter.

[0340] Example 5.17. The method of Example 5.16, wherein the counter is stopped based on at least one of:transmission of an RRCSetupRequest message,transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT),transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT, transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0341] Example 5.18. The method of Example 5.16, wherein the counter is stopped based on at least one of:reception of a RRCResume message,reception of an RRCSetup message,reception of an RRCRelease with suspendConfig message,reception of a RRCReject message.

[0342] Example 5.19. The method of Example 5.16, wherein the counter is stopped based on at least one of:successfully completing contention resolution in random access procedure,aborting connection establishment by upper layers,cell selection on at least one of the at least one second carrier,cell re-selection on at least one of the at least one second carrier, ordetermining that access is barred on the at least one second carrier.

[0343] Example 5.20. The method of any one of Examples 5.16-5.19, further comprising, after the counter is stopped, at least one of:attempting to select the first carrier,attempting to re-select the first carrier, orentering into idle mode from inactive mode.

[0344] Example 5.21. The method of any one of Examples 5.16-5.19, further comprising, after the counter is stopped, at least one of:stopping attempting to respond to the paging,continuing attempting to respond to the paging on the first carrier, orstopping monitoring for a LP-WUS for period of time.

[0345] Example 5.22. The method of any one of Examples 5.1-5.21, further comprising:receiving, from a network apparatus, the counter limit value

[0346] Example 5.23. The method of Example 5.22, wherein the receiving the counter limit value comprises receiving the counter limit value in a dedicated signal.

[0347] Example 5.24. The method of Example 5.23, wherein the dedicated signal comprises a RRCRelease message containing the counter limit value.

[0348] Example 5.25. The method of Example 5.22, wherein the receiving the counter limit value comprises receiving the counter limit value in a broadcast signal.

[0349] Example 5.26. The method of Example 5.25, wherein the broadcast signal comprises a system information block (SIB) containing the counter limit value.

[0350] Example 5.27. The method of any one of Examples 5.1-5.23, wherein the counter limit value is statically defined in a standard.

[0351] Example 5.28. The method of any one of Examples 5.1-5.27, wherein the counter counts at least one of:number of random access procedure attempts for which a random access response was not received,number of random access procedure attempts for which a random access response was not received on at least one of the at least one second carrier,failed contention resolutions for random access procedure, ornumber of carriers used for attempted paging responses.

[0352] Example 5.29. The method of any one of Examples 5.1-5.28,wherein the at least one second carrier comprises a plurality of carriers,wherein each of the plurality of carriers have different random access channel (RACH) configurations.

[0353] Example 5.30. The method of Example 5.29, wherein the different RACH configurations comprise different numbers of RACH occasions for a time.

[0354] Example 5.31. The method of any one of Examples 5.1-5.30, further comprising:counting paging occasions in at least one of the at least one second carrier by incrementing the counter for each paging occasion in the at least one of the at least one second carrier.

[0355] Example 5.32. An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of Examples 1-31.

[0356] Example 5.33. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of Examples 1-31.

[0357] Example 6.1. A user equipment (UE), comprising:means for configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier;means for starting a counter; andin response to receiving a LP-WUS and a paging on the first carrier, means for attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

[0358] Example 6.2. The user equipment (UE) of Example 6.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0359] Example 6.3. The user equipment (UE) of Example 6.1 or 6.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0360] Example 6.4. The user equipment (UE) of Example 6.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0361] Example 6.5. The user equipment (UE) of Example 6.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0362] Example 6.6. The user equipment (UE) of any one of Examples 6.1-6.5, wherein the first carrier and the at least one second carrier have different frequencies.

[0363] Example 6.7. The user equipment (UE) of any one of Examples 6.1-6.6, wherein the first carrier and the at least one second carrier are in different bands.

[0364] Example 6.8. The user equipment (UE) of any one of Examples 6.1-6.7,wherein the first carrier is provided by a serving cell serving the UE, andwherein the at least one second carrier is provided by at least one second cell.

[0365] Example 6.9. The user equipment (UE) of any one of Examples 6.1-6.8, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

[0366] Example 6.10. The user equipment (UE) of any one of Examples 6.1-6.9, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

[0367] Example 6.11. The user equipment (UE) of any one of Examples 6.1-6.10, wherein the means for attempting to respond to the paging on at least one of the at least one second carrier occurs only after the counter is started.

[0368] Example 6.12. The user equipment (UE) of any one of Examples 6.1-6.11, wherein the counter is started based on at least one of:receiving the LP-WUS,receiving the paging addressing the UE,transmitting a message on at least one of the at least one second carrier,upon selecting a new carrier for responding to the paging.

[0369] Example 6.13. The user equipment (UE) of Example 6.12, wherein the message is a common control channel (CCCH) message.

[0370] Example 6.14. The user equipment (UE) of Example 6.13, wherein the CCCH message comprises one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

[0371] Example 6.15. The user equipment (UE) of any one of Examples 6.1-6.14, wherein the means for attempting to respond to the paging on at least one of the at least one second carrier while the value of the counter is below the limit value comprises at least one of:means for selecting a cell on at least one of the at least one second carrier,means for reselecting to a cell on at least one of the at least one second carrier,means for initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier,means for initiating an RRC Resume Request on at least one of the at least one second carrier, means for initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, ormeans for responding to the paging on at least one of the at least one second carrier.

[0372] Example 6.16. The user equipment (UE) of any one of Examples 6.1-6.15, further comprising means for stopping the counter.

[0373] Example 6.17. The user equipment (UE) of Example 6.16, wherein the counter is stopped based on at least one of:transmission of an RRCSetupRequest message,transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT),transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT, transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

[0374] Example 6.18. The user equipment (UE) of Example 6.16, wherein the counter is stopped based on at least one of:reception of a RRCResume message,reception of an RRCSetup message,reception of an RRCRelease with suspendConfig message,reception of a RRCReject message.

[0375] Example 6.19. The user equipment (UE) of Example 6.16, wherein the counter is stopped based on at least one of:successfully completing contention resolution in random access procedure,aborting connection establishment by upper layers,cell selection on at least one of the at least one second carrier,cell re-selection on at least one of the at least one second carrier, ordetermining that access is barred on the at least one second carrier.

[0376] Example 6.20. The user equipment (UE) of any one of Examples 6.16-6.19, further comprising, after the counter is stopped, at least one of:means for attempting to select the first carrier,means for attempting to re-select the first carrier, ormeans for entering into idle mode from inactive mode.

[0377] Example 6.21. The user equipment (UE) of any one of Examples 6.16-6.19, further comprising, after the counter is stopped, at least one of:means for stopping attempting to respond to the paging,means for continuing attempting to respond to the paging on the first carrier, ormeans for stopping monitoring for a LP-WUS for period of time.

[0378] Example 6.22. The user equipment (UE) of any one of Examples 6.1-6.21, further comprising:means for receiving, from a network apparatus, the counter limit value

[0379] Example 6.23. The user equipment (UE) of Example 6.22, wherein the means for receiving the counter limit value comprises receiving the counter limit value in a dedicated signal.

[0380] Example 6.24. The user equipment (UE) of Example 6.23, wherein the dedicated signal comprises a RRCRelease message containing the counter limit value.

[0381] Example 6.26. The user equipment (UE) of Example 6.22, wherein the means for receiving the counter limit value comprises receiving the counter limit value in a broadcast signal.

[0382] Example 6.25. The user equipment (UE) of Example 6.25, wherein the broadcast signal comprises a system information block (SIB) containing the counter limit value.

[0383] Example 6.27. The user equipment (UE) of any one of Examples 6.1-6.23, wherein the counter limit value is statically defined in a standard.

[0384] Example 6.28. The user equipment (UE) of any one of Examples 6.1-6.27, wherein the counter counts at least one of:number of random access procedure attempts for which a random access response was not received,number of random access procedure attempts for which a random access response was not received on at least one of the at least one second carrier,failed contention resolutions for random access procedure, ornumber of carriers used for attempted paging responses.

[0385] Example 6.29. The user equipment (UE) of any one of Examples 6.1-6.28, wherein the at least one second carrier comprises a plurality of carriers,wherein each of the plurality of carriers have different random access channel (RACH) configurations.

[0386] Example 6.30. The user equipment (UE) of Example 6.29, wherein the different RACH configurations comprise different numbers of RACH occasions for a time.

[0387] Example 6.31. The user equipment (UE) of any one of Examples 6.1-6.30, further comprising:means for counting paging occasions in at least one of the at least one second carrier by incrementing the counter for each paging occasion in the at least one of the at least one second carrier.

[0388] Example 7.1. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a counter limit value,wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier,wherein the counter limit value is configured to cause the UE to run a counter for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0389] Example 7.2. The method of Example 7.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging,indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0390] Example 7.3. The method of Example 7.1 or 7.2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

[0391] Example 7.4. The method of Example 7.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0392] Example 7.5. The method of Example 7.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0393] Example 7.6. The method of any one of Examples 7.1-7.5, wherein the transmitting the counter limit value comprises transmitting the counter limit value in a dedicated signal.

[0394] Example 7.7. The method of Example 7.6, wherein the dedicated signal comprises a RRCRelease message containing the counter limit value.

[0395] Example 7.8. The method of any one of Examples 7.1-7.5, wherein the transmitting the counter limit value comprises transmitting the counter limit value in a broadcast signal.

[0396] Example 7.9. The method of Example 7.8, wherein the broadcast signal comprises a system information block (SIB) containing the counter limit value.

[0397] Example 7.10. The method of any one of Examples 7.1-7.5, wherein the counter limit value is statically defined in a standard.

[0398] Example 7.11. The method of any one of Examples 7.1-7.10, further comprising: starting the counter based on one of:transmitting a LP-WUS to the UE, ortransmitting a paging to the UE.

[0399] Example 7.12. The method of Example 7.11, further comprising:waiting for a paging response from the UE on at least one of the at least one second carrier while the counter is running.

[0400] Example 7.13. The method of Example 7.11 or Example 7.12, further comprising:stopping the counter based on receiving a paging response from the UE.

[0401] Example 7.14. The method of any one of Examples 7.11-7.13, wherein the counter has a same limit value as the counter limit value transmitted to the UE.

[0402] Example 7.15. An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of Examples 7.1-7.14.

[0403] Example 7.16. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of Examples 7.1-7.14.

[0404] Example 8.1. A network apparatus, comprising:means for transmitting, to a user equipment (UE), a counter limit value,wherein the UE is configured to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier,wherein the counter limit value is configured to cause the UE to run a counter for means for attempting to respond to a paging, received on the first carrier, on at least one of the at least one second carrier.

[0405] Example 8.2. The network apparatus of Example 8.1, wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

[0406] Example 8.3. The network apparatus of Example 8.1 or 8.2, wherein the paging is means for addressing the UE when a paging message of the paging includes an identifier of the UE.

[0407] Example 8.4. The network apparatus of Example 8.3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

[0408] Example 8.5. The network apparatus of Example 8.3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

[0409] Example 8.6. The network apparatus of any one of Examples 8.1-8.5, wherein the transmitting the counter limit value comprises means for transmitting the counter limit value in a dedicated signal.

[0410] Example 8.7. The network apparatus of Example 8.6, wherein the dedicated signal comprises a RRCRelease message containing the counter limit value.

[0411] Example 8.8. The network apparatus of any one of Examples 8.1-8.5, wherein the transmitting the counter limit value comprises means for transmitting the counter limit value in a broadcast signal.

[0412] Example 8.9. The network apparatus of Example 8.8, wherein the broadcast signal comprises a system information block (SIB) containing the counter limit value.

[0413] Example 8.10. The network apparatus of any one of Examples 8.1-8.5, wherein the counter limit value is statically defined in a standard.

[0414] Example 8.11. The network apparatus of any one of Examples 8.1-8.10, further comprising: means for starting the counter based on one of:means for transmitting a LP-WUS to the UE, ormeans for transmitting a paging to the UE.

[0415] Example 8.12. The network apparatus of Example 8.11, further comprising:means for waiting for a paging response from the UE on at least one of the at least one second carrier while the counter is running.

[0416] Example 8.13. The network apparatus of Example 8.11 or Example 8.12, further comprising:means for stopping the counter based on receiving a paging response from the UE.

[0417] Example 8.14. The network apparatus of any one of Examples 8.11-8.13, wherein the counter has a same limit value as the counter limit value transmitted to the UE.

[0418] Example 8.15. An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of Examples 8.1-8.14.

[0419] Example 8.16. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of Examples 8.1-8.14.

[0420] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0421] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0422] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[0423] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer,and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0424] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

1. WHAT IS CLAIMED IS:

1. A method in a user equipment (UE), comprising:configuring to monitor for a low-power wake-up signal (LP-WUS) and for a paging on a first carrier and to respond to the paging on at least one second carrier;starting a counter; andin response to receiving a LP-WUS and a paging on the first carrier, attempting to respond to the paging on at least one of the at least one second carrier while a value of the counter is below a limit value.

2. The method of claim 1 , wherein an indication of at least one second carrier comprises at least one of:indication of at least one cell where the UE should attempt responding to the paging, indication of at least one band where the UE should attempt responding to the paging, or indication of at least one frequency where the UE should attempt responding to the paging.

3. The method of claim 1 or claim 2, wherein the paging is addressing the UE when a paging message of the paging includes an identifier of the UE.

4. The method of claim 3, wherein identifier is S-TMSI (Temporary Mobile Subscription Identifier).

5. The method of claim 3, wherein the identifier is l-RNTI (Inactive Radio Network Temporary Identifier).

6. The method of any one of claims 1-5, wherein the first carrier and the at least one second carrier have different frequencies.

7. The method of any one of claims 1-6, wherein the first carrier and the at least one second carrier are in different bands.

8. The method of any one of claims 1-7,wherein the first carrier is provided by a serving cell serving the UE, andwherein the at least one second carrier is provided by at least one second cell.

9. The method of any one of claims 1-8, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are provided by different base stations.

10. The method of any one of claims 1-9, wherein a cell providing the first carrier and at least one cell providing the at least one second carrier are in different bands.

11. The method of any one of claims 1-10, wherein the attempting to respond to the paging on at least one of the at least one second carrier occurs only after the counter is started.

12. The method of any one of claims 1-11, wherein the counter is started based on at least one of: receiving the LP-WUS,receiving the paging addressing the UE,transmitting a message on at least one of the at least one second carrier,upon selecting a new carrier for responding to the paging.

13. The method of claim 12, wherein the message is a common control channel (CCCH) message.

14. The method of claim 13, wherein the CCCH message comprises one of: a radio resource control (RRC) Setup Request, or an RRC Resume Request.

15. The method of any one of claims 1-14, wherein the attempting to respond to the paging on at least one of the at least one second carrier while the value of the counter is below the limit value comprises at least one of:selecting a cell on at least one of the at least one second carrier,reselecting to a cell on at least one of the at least one second carrier,initiating a radio resource control (RRC) Setup Request on at least one of the at least one second carrier,initiating an RRC Resume Request on at least one of the at least one second carrier,initiating an RRC Resume Request for small data transmission (SDT) on at least one of the at least one second carrier, orresponding to the paging on at least one of the at least one second carrier.

16. The method of any one of claims 1-15, further comprising stopping the counter.

17. The method of claim 16, wherein the counter is stopped based on at least one of: transmission of an RRCSetupRequest message,transmission of an RRCResumeRequest message when resume procedure is not initiated for small data transmission (SDT),transmission of an RRCResumeRequestl message when resume procedure is not initiated for SDT,transmission of an RRCResumeRequest message when resume procedure is initiated for SDT, transmission of an RRCResumeRequestl message when resume procedure is initiated for SDT, or transmission of a paging response.

18. The method of claim 16, wherein the counter is stopped based on at least one of: reception of a RRCResume message,reception of an RRCSetup message,reception of an RRCRelease with suspendConfig message,reception of a RRCReject message.

19. The method of claim 16, wherein the counter is stopped based on at least one of: successfully completing contention resolution in random access procedure,aborting connection establishment by upper layers,cell selection on at least one of the at least one second carrier,cell re-selection on at least one of the at least one second carrier, ordetermining that access is barred on the at least one second carrier.

20. The method of any one of claims 16-19, further comprising, after the counter is stopped, at least one of:attempting to select the first carrier,attempting to re-select the first carrier, orentering into idle mode from inactive mode.

21. The method of any one of claims 16-19, further comprising, after the counter is stopped, at least one of:stopping attempting to respond to the paging,continuing attempting to respond to the paging on the first carrier, orstopping monitoring for a LP-WUS for period of time.

22. The method of any one of claims 1-21, further comprising:receiving, from a network apparatus, the counter limit value23. The method of claim 22, wherein the receiving the counter limit value comprises receiving the counter limit value in a dedicated signal.

24. The method of claim 23, wherein the dedicated signal comprises a RRCRelease message containing the counter limit value.

25. The method of claim 22, wherein the receiving the counter limit value comprises receiving the counter limit value in a broadcast signal.

26. The method of claim 25, wherein the broadcast signal comprises a system information block (SIB) containing the counter limit value.

27. The method of any one of claims 1-23, wherein the counter limit value is statically defined in a standard.

28. The method of any one of claims 1-27, wherein the counter counts at least one of: number of random access procedure attempts for which a random access response was not received,number of random access procedure attempts for which a random access response was not received on at least one of the at least one second carrier,failed contention resolutions for random access procedure, ornumber of carriers used for attempted paging responses.

29. The method of any one of claims 1-28,wherein the at least one second carrier comprises a plurality of carriers,wherein each of the plurality of carriers have different random access channel (RACH) configurations.

30. The method of claim 29, wherein the different RACH configurations comprise different numbers of RACH occasions for a time.

31. The method of any one of claims 1-30, further comprising:counting paging occasions in at least one of the at least one second carrier by incrementing the counter for each paging occasion in the at least one of the at least one second carrier.

32. An apparatus comprising:at least one processor; andat least one memory having stored thereon instructions which, when executed by the at least one processor, cause the apparatus to perform a method as in any one of claims 1-31.

33. A non-transitory processor-readable medium having stored thereon instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform a method as in any one of claims 1-31.

Images