Communication equipment and methods

Abstract

Embodiments of the present disclosure relate to communication devices and methods. In one embodiment, when a terminal device receives LPWUS from a network device in a first mode, it performs PDCCH monitoring in a second mode. If no data-related information is received in the second mode, the terminal device performs LPWUS monitoring in the first mode. In this way, a fallback to LPWUS mode from PDCCH monitoring may be achieved, and unnecessary power consumption for PDCCH monitoring may be reduced.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to methods, devices, and computer storage media for communication for a Low-Power Wake-Up Signal (LPWUS).

Background Art

[0002] Currently, it has been proposed to use a main radio to describe a normal communication device operating in a normal Radio Resource Control (RRC) state, and further design an LPWUS receiver to monitor the LPWUS for turning on the main radio. When the terminal device is not receiving services, the terminal device may enter the LPWUS mode in which the main radio is turned off and the LPWUS receiver is turned on to monitor the LPWUS. When the LPWUS is received, the terminal device may turn on the main radio and turn off the LPWUS receiver. However, the LPWUS mechanism is still incomplete and needs further development.

Summary of the Invention

[0003] Generally, embodiments of the present disclosure provide a method, a device, and a computer storage medium for communication for an LPWUS.

[0004] In a first aspect, a terminal device is provided. The terminal device includes a processor configured to cause the terminal device to receive an LPWUS from a network device in a first mode, perform physical downlink control channel (PDCCH) monitoring in a second mode, and perform LPWUS monitoring in the first mode according to a determination that no data-related information is received in the second mode.

[0005] In a second embodiment, a terminal device is provided. The terminal device includes a processor configured to perform the following: receiving LPWUS from a network device in a first mode; initiating a random access procedure in a second mode, wherein the random access procedure indicates that the random access procedure is initiated by the reception of LPWUS; and performing LPWUS monitoring in the first mode based on the response from the network device to the random access procedure.

[0006] In a third embodiment, a network device is provided. The network device includes a processor configured to perform the following: in a first mode, transmit an LPWUS to a terminal device; in a second mode, execute a random access procedure initiated by the terminal device, wherein the random access procedure indicates that it is initiated upon receipt of the LPWUS; and determine a response to the random access procedure.

[0007] In a fourth embodiment, a communication method is provided. The method includes, in a terminal device, receiving LPWUS from a network device in a first mode, performing PDCCH monitoring in a second mode, and, in accordance with the determination in the second mode that no data-related information has been received, performing LPWUS monitoring in the first mode.

[0008] In a fifth aspect, a communication method is provided. The method includes, in a terminal device, receiving LPWUS from a network device in a first mode; in a second mode, initiating a random access procedure, the random access procedure indicating that it is initiated by the reception of LPWUS; and, in the first mode, performing LPWUS monitoring based on the network device's response to the random access procedure.

[0009] In a sixth aspect, a communication method is provided. The method includes a network device transmitting an LPWUS to a terminal device in a first mode, executing a random access procedure initiated by the terminal device in a second mode, the random access procedure indicating that it is initiated upon receipt of the LPWUS, and determining a response to the random access procedure.

[0010] In the seventh aspect, a computer-readable medium on which instructions are stored is provided. When the instructions are executed on at least one processor, the at least one processor is caused to perform a method according to any of the fourth to sixth aspects of the present disclosure.

[0011] Other features of this disclosure will be readily apparent through the following description. [Brief explanation of the drawing]

[0012] The above and other purposes, features, and advantages of this disclosure will become more apparent through a more detailed description of some embodiments of this disclosure in the attached drawings.

[0013] [Figure 1A] This document illustrates an exemplary communication network that can implement several embodiments of this disclosure.

[0014] [Figure 1B] This document shows an exemplary structure of a terminal device that can implement some embodiments of this disclosure.

[0015] [Figure 1C] This figure shows exemplary application scenarios of an LPWUS mechanism in a connected state, in which some embodiments of the present disclosure can be implemented.

[0016] [Figure 1D]A diagram showing an exemplary application scenario of the LPWUS mechanism in an idle state or an inactive state where some embodiments of the present disclosure can be implemented.

[0017] [Figure 2] A schematic diagram showing the communication process according to an embodiment of the present disclosure.

[0018] [Figure 3A] A schematic diagram showing an exemplary fallback of the LPWUS mode based on the active time of a discontinuous reception (DRX) cycle according to an embodiment of the present disclosure.

[0019] [Figure 3B] A schematic diagram showing an exemplary fallback of the LPWUS mode based on downlink control information with cyclic redundancy check scrambled by a power saving - radio network temporary identifier (DCP) according to an embodiment of the present disclosure.

[0020] [Figure 3C] A schematic diagram showing an exemplary fallback of the LPWUS mode based on a timer according to an embodiment of the present disclosure.

[0021] [Figure 4] A schematic diagram showing another communication process according to an embodiment of the present disclosure.

[0022] [Figure 5] Shows an exemplary method of communication implemented by a terminal device according to some embodiments of the present disclosure.

[0023] [Figure 6] Shows another exemplary method of communication implemented by a terminal device according to some embodiments of the present disclosure.

[0024] [Figure 7] Further exemplary methods of communication performed by network devices according to some embodiments of this disclosure are shown.

[0025] [Figure 8] This is a simplified block diagram of an apparatus suitable for carrying out embodiments of the present disclosure.

[0026] Throughout the drawing, identical or similar reference numbers represent identical or similar elements. [Modes for carrying out the invention]

[0027] The principles of this disclosure will now be described with reference to several embodiments. These embodiments are provided for illustrative purposes only and should be understood as helpful to those skilled in the art in understanding and implementing this disclosure, without implying any limitation on the scope of this disclosure. The disclosures described herein can be implemented in various ways other than those described below.

[0028] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art to which this disclosure belongs.

[0029] As used herein, the term “terminal device” refers to any device equipped with wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDA), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Ultra-Reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, Machine Type Communication (MTC) devices, vehicle-mounted devices for V2X communication (where X represents pedestrians, vehicles, or infrastructure / networks), Integrated Access and Backhaul (IAB) devices, spacecraft or aerial vehicles within non-terrestrial networks (NTN) including high-altitude platforms (HAP) with satellites and unmanned aircraft systems (UAS), Augmented Reality (AR), and Mixed Reality (MR). Examples include, but are not limited to, extended reality (XR) devices, which include various types of reality such as reality and virtual reality (VR); unmanned aerial vehicles (UAVs), which are aircraft without human pilot intervention, commonly known as drones; equipment mounted on high-speed trains (HSTs); image capture devices such as digital cameras, sensors, game consoles, and music storage and playback devices; and internet equipment that enables wireless or wired internet access and browsing.The “terminal device” may also have “multicast / broadcast” capabilities and support public safety and mission-critical, V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, radio services, software distribution over the radio, group communications, and IoT applications. It may also incorporate one or more Subscriber Identity Modules (SIMs), known as multi-SIMs. The term “terminal device” can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or radio device.

[0030] As used herein, the term “network device” refers to a device that can provide or host a cell or coverage on which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmission reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), IAB node, low-power nodes such as femtonodes, piconodes, and reconfigurable intelligent surface (RIS).

[0031] Terminal devices or network devices may be equipped with artificial intelligence (AI) or machine learning capabilities. These typically include models trained on large amounts of collected data for specific functions and usable to predict certain information.

[0032] Terminal or network devices may operate in multiple frequency ranges, including FR1 (410 MHz to 7125 MHz), FR2 (24.25 GHz to 71 GHz), frequency bands above 100 GHz, and terahertz (THz). Furthermore, they can operate in licensed / unlicensed / shared spectrum. In multi-radio dual connectivity (MR-DC) application scenarios, terminal devices may have multiple connections to network devices. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-split-duplex modes.

[0033] Embodiments of the present disclosure may be performed using test equipment such as signal generators, signal analyzers, spectrum analyzers, network analyzers, test terminal devices, test network devices, and channel emulators.

[0034] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node, and the other may be a secondary node. The first and second network devices may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be transmitted to the terminal device from at least one of the first or second network devices. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted directly from the second network device to the terminal device or via the first network device. In one embodiment, information regarding the configuration set for the terminal device by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration set for the terminal device by the second network device may be transmitted directly from the second network device to the terminal device, or transmitted via the first network device.

[0035] Where used herein, the singular forms “a / an” and “the” are intended to include the plural unless explicitly indicated otherwise in the context. The term “including” and its variations are interpreted as an open term meaning “including, but not limited to.” The term “based on” is interpreted as “at least partially based on.” The terms “one embodiment” and “a certain embodiment” are interpreted as “at least one embodiment.” The term “another embodiment” is interpreted as “at least one other embodiment.” The terms “first,” “second,” etc., may refer to different or the same subject. The following may include other explicit and implicit definitions.

[0036] In some examples, values, procedures, or devices are referred to as “best,” “worst,” “highest,” “minimum,” “maximum,” etc. Such descriptions are intended to show that a choice can be made from among many functional options being used, and it will be understood that such a choice does not need to be better, smaller, higher, or more preferable than the other options.

[0037] In the context of this disclosure, the term “connected state” may be used interchangeably with “RRC_CONNECTED state,” the term “idle state” may be used interchangeably with “RRC_IDLE state,” and the term “inactive state” may be used interchangeably with “RRC_INACTIVE state.”

[0038] In the context of this disclosure, the term “turn on” may be used interchangeably with “activate,” “wake up / start,” “switch on,” “state transition,” or “warm up.” In the context of this disclosure, the term “turn off” may be used interchangeably with “deactivate,” “sleep,” “switch off,” “state transition,” or “warm down.” In the context of this disclosure, the term “always-on monitoring” may be used interchangeably with “continuous monitoring,” and the term “duty cycle monitoring” may be used interchangeably with “periodic monitoring.” In the context of this disclosure, the term “DCP” may also be referred to as “downlink control information for power saving.”

[0039] In the context of this disclosure, in the case of an inactive or idle state, the term “LPWUS mode” may mean that the UE monitors LPWUS in an inactive or idle state while the main radio is in ultra-deep sleep, inactive, or turned off. In the case of a connected state, the term “LPWUS mode” may mean that the UE monitors LPWUS in a connected state while the main radio is in light sleep, micro sleep, inactive, or turned off. The term “LPWUS mode” may be used interchangeably with “LPWUS state” or any other appropriate name.

[0040] Generally, during LPWUS mode, the main radio may remain in sleep mode. Terminal devices may still remain in any RRC state (e.g., idle, inactive, or connected), but they do not need to perform normal operations in those RRC states. Terminal devices may only need to monitor LPWUS, or only need to perform some actions related to LPWUS mode, such as synchronization and / or measurements in LPWUS mode.

[0041] In the context of this disclosure, the term "LPWUS" is used to describe a signal transmitted by a network in LPWUS mode and monitored by a low-power receiver of a terminal device. The term "LPWUS" may be used interchangeably with "ultra-low-power wake-up signal," "wake-up signal," or any other appropriate name.

[0042] In the context of this disclosure, the term “DRX cycle active time” may also be referred to as “DRX active time” or “active time window.” When a terminal device is in DRX active time, the terminal device begins performing PDCCH monitoring. The term “DRX cycle inactive time” may also be referred to as “DRX inactive time,” “sleep time,” or “sleep time window.” Compared to DRX active time, DRX inactive time means that the terminal device operates in sleep mode and does not need to perform PDCCH monitoring.

[0043] When DRX is configured, the active time for serving cells within a DRX group includes the time when drx-onDurationTimer is active, drx-InactivityTimer is active, drx-RetransmissionTimerDL is active, drx-RetransmissionTimerUL is active, or ra-ContentionResultionTimer is active.

[0044] Fifth-generation (5G) equipment consumes tens of milliwatts in idle or inactive states and hundreds of milliwatts in connected states. Designing for extended battery life is essential for improving energy efficiency and user experience. To meet battery life requirements, it is expected that enhanced discontinuous reception (eDRX) cycles with large values ​​will be used. However, eDRX cycles can introduce high latency, making them unsuitable for services that require both long battery life and low latency. For example, in fire detection and firefighting use cases, long eDRX cycles cannot meet the latency requirements. In short, eDRX does not appear to be suitable for latency-critical use cases. Therefore, research into ultra-low-power mechanisms that can support low latency, such as latency lower than eDRX latency, is expected.

[0045] As described above, the LPWUS mechanism has been proposed. In the LPWUS mechanism, the main radio is used to describe a normal communication device performing the normal RRC state, and the LPWUS receiver is further designed to monitor the LPWUS for the turn-on of the main radio. If a terminal device is not receiving service, the terminal device may enter LPWUS mode, in which case the main radio is turned off and the LPWUS receiver is turned on to monitor the LPWUS. Another objective of the LPWUS mechanism is power saving for the terminal device.

[0046] However, the low complexity makes it difficult to implement UE-specific LPWUS designs. This means that multiple UEs need to monitor the same LPWUS for any incoming data.

[0047] In some scenarios where LPWUS is applied to a UE in a connected state, when receiving LPWUS, the UE may monitor the PDCCH using the DRX cycle in the normally or activated connected state. In this case, if LPWUS is not intended for this UE (for example, LPWUS transmits notifications for other UEs), a false alarm problem occurs. This results in unnecessary power consumption (i.e., unnecessary monitoring) for this UE.

[0048] In some scenarios where LPWUS is applied to a UE while it is idle or inactive, upon receiving LPWUS, the UE may directly initiate random access to establish or resume RRC connectivity. This may avoid paging or Paging Early Indication (PEI) procedures for better latency, power saving, etc. In this case, if LPWUS is not intended for this UE (for example, if LPWUS is transmitting a notification for another UE), a false alarm problem arises. This also results in unnecessary power consumption (i.e., unnecessary random access) for this UE.

[0049] With this in mind, embodiments of the present disclosure provide a communication solution for achieving fallback to LPWUS mode and reducing unnecessary power consumption. In one embodiment, when receiving LPWUS from a network device in a first mode, the terminal device may perform PDCCH monitoring in a second mode. If no data-related information is received in the second mode, the terminal device may perform LPWUS monitoring in the first mode. In this way, fallback to LPWUS mode from PDCCH monitoring may be achieved, and unnecessary power consumption for PDCCH monitoring may be reduced.

[0050] In another embodiment, when the terminal device receives an LPWUS from the network device in the first mode, it may initiate a random access procedure in the second mode and indicate that the random access procedure is initiated by the reception of the LPWUS. This allows the network device to determine whether a false alarm problem has occurred and then decide how to respond to the random access procedure. Based on the response to the random access procedure from the network device, the terminal device may perform LPWUS monitoring in the first mode. In this way, a fallback to the LPWUS mode from the random access procedure may be achieved, and unnecessary power consumption for random access may be reduced.

[0051] The principles and embodiments of this disclosure are described in detail below with reference to the drawings. <Example of a communication network>

[0052] Figure 1A shows a schematic diagram of an exemplary communication network 100A that can implement several embodiments of the present disclosure. As shown in Figure 1A, the communication network 100A may include terminal devices 110 and network devices 120. The network devices 120 may provide a serving cell (also referred to herein as a cell) 121 that provides services to one or more terminal devices. In this example, the terminal device 110 is shown as being located within the cell 121 and being serviced by the network devices 120.

[0053] As shown in Figure 1A, the terminal device 110 and the network device 120 may communicate with each other via a channel such as a wireless communication channel. Communication in the communication network 100A may conform to any appropriate standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), and Machine-Type Communication (MTC). Embodiments of this disclosure may be implemented in accordance with any generation of communication protocols that are currently known or will be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G-Advanced Network, or sixth-generation (6G) networks.

[0054] The number of devices or cells in Figure 1A should be understood to be for illustrative purposes only and without implying any limitation to this disclosure. The communication network 100A may include any appropriate number of network devices and / or terminal devices and / or cells suitable for implementing the disclosure.

[0055] Figure 1B is a diagram showing an exemplary structure of a terminal device that can carry out several embodiments of the present disclosure. For convenience, Figure 1B will be described in relation to the terminal device 110 of Figure 1A.

[0056] As shown in Figure 1B, the terminal device 110 may include an LPWUS receiver 141 and a main radio 142. The LPWUS receiver 141 is configured to monitor the LPWUS. The main radio 142 is configured as a normal communications device performing normal RRC conditions. It should be understood that the LPWUS receiver and the main radio may have any other appropriate names.

[0057] In some embodiments, the LPWUS receiver 141 may detect an LPWUS indicating the turn-off of the main radio 142 and trigger the main radio 142 to enter a turn-off or deep sleep state. In the turn-off or deep sleep state, the terminal device 110 does not need to process RRC idle or inactive or connected state procedures. In some embodiments, the LPWUS receiver 141 may detect an LPWUS indicating the turn-on of the main radio 142 and trigger the main radio 142 to enter a turn-on state. In the turn-on state, the main radio 142 may perform PDCCH monitoring, or paging monitoring, or directly initiate a Random Access (RA) procedure.

[0058] Figure 1C is an exemplary application scenario of an LPWUS mechanism in a connected state in which several embodiments of the present disclosure can be implemented. In this example, the DRX cycle may be configured for PDCCH monitoring, and the DRX cycle may include an active time and a sleep time.

[0059] As shown in Figure 1C, in scenario 150, periodic monitoring of LPWUS may be configured. As shown in the figure, if LPWUS is received in LPWUS monitoring occasion 151, PDCCH monitoring may be performed during active time 152. If LPWUS is not received in LPWUS monitoring occasion 153, PDCCH monitoring may not be performed during active time 154.

[0060] In scenario 150', periodic monitoring of LPWUS may be configured. As shown in the figure, if LPWUS is received in LPWUS monitoring occasion 151', DCP monitoring may be performed. If a DCP indicating the start of PDCCH monitoring is received (e.g., including a wake-up indicator bit where DCP is 1), PDCCH monitoring may be performed during active time 152'. If LPWUS is not received in LPWUS monitoring occasion 153', DCP monitoring does not have to be performed before active time 154', and PDCCH monitoring does not have to be performed during active time 154'.

[0061] In Scenario 160, LPWUS may be configured for always-on monitoring. As shown in the figure, LPWUS may be monitored continuously until an LPWUS signal is received. In this example, LPWUS is received at timing A. PDCCH monitoring is skipped until timing A. That is, PDCCH monitoring is performed after timing A during active time 161.

[0062] In these scenarios, false alarms occur if LPWUS does not target the current UE (for example, if LPWUS transmits notifications for another UE). This may result in unnecessary power consumption for PDCCH monitoring for that UE.

[0063] Figure 1D is an exemplary application scenario of the LPWUS mechanism in an idle or inactive state, in which several embodiments of the present disclosure can be implemented. As shown in Figure 1D, in scenario 170, if LPWUS is received, paging monitoring in the Paging Occasion (PO) may be performed. Optionally, synchronization signal, physical broadcast channel block (SSB) measurement, and synchronization may be performed before paging monitoring. If paging to the current UE is received in the PO, the current UE may initiate the RA procedure by sending a preamble on the Physical Random Access Channel (PRACH). Optionally, SSB measurement and synchronization may also be performed before the RA procedure.

[0064] In Scenario 180, if LPWUS is received, PEI monitoring may be performed. Optionally, SSB measurement and synchronization may be performed before PEI monitoring. If PEI indicating the activation of paging monitoring is received, paging monitoring may be performed at PO. If paging to the current UE is received at PO, the current UE may initiate the RA procedure by sending a preamble on PRACH. Optionally, SSB measurement and synchronization may also be performed before the RA procedure.

[0065] In Scenario 190, if LPWUS is received, the current UE may initiate the RA procedure by directly sending the preamble over PRACH. Optionally, SSB measurement and synchronization may be performed before the RA procedure.

[0066] In these scenarios, if the LPWUS does not target the current UE (for example, the LPWUS transmits a notification for another UE), a false alarm problem occurs. This may cause unnecessary power consumption for RA for this UE.

[0067] Considering this, embodiments of the present disclosure provide communication solutions for implementing fallback in the LPWUS mode and reducing unnecessary power consumption. These solutions will be described below with reference to FIGS. 2 to 4. <Example implementation of fallback from PDCCH monitoring>

[0068] FIG. 2 is a schematic diagram showing a communication process 200 according to an embodiment of the present disclosure. For the sake of explanation, the process 200 will be described with reference to FIGS. 1A and 1B. The process 200 may involve a terminal device 110 and a network device 120 as shown in FIG. 1A. It should be understood that the steps and the order of the steps in FIG. 2 are for illustrative purposes only and are not limiting. For example, the order of the steps may be changed. Some steps may be omitted or any other appropriate additional steps may be added.

[0069] As shown in FIG. 2, the network device 120 may transmit an LPWUS configuration to the terminal device 110 (210). In some embodiments, the network device 120 may transmit the LPWUS configuration in system information (SI: System Information) or any other appropriate method. In some embodiments, the LPWUS configuration may indicate one or more occasions for LPWUS monitoring. In some embodiments, periodic monitoring may be configured for LPWUS monitoring. In some embodiments, always-on monitoring may be configured for LPWUS monitoring. It should be understood that the LPWUS configuration may also include any other appropriate information and may be transmitted in any other appropriate method.

[0070] The terminal device 110 may perform LPWUS monitoring in a first mode based on the LPWUS configuration (220). In the first mode, the main radio 142 of the terminal device 110 is turned off, and the LPWUS receiver 141 of the terminal device 110 is turned on. In the context of this disclosure, the first mode may also be called LPWUS mode or state, sleep mode or state, or ultra-deep sleep mode or state.

[0071] Continuing to refer to Figure 2, the network device 120 may transmit LPWUS to the terminal device 110 in LPWUS mode (230). Upon receiving LPWUS, the terminal device 110 may perform PDCCH monitoring in a second mode (235) (for example, by activating the main radio 142). In the second mode, the main radio 142 of the terminal device 110 is turned on, and the LPWUS receiver 141 of the terminal device 110 is turned off. In some embodiments, the second mode may be a connected state.

[0072] If data-related information is not received in the second mode, the terminal device 110 may perform LPWUS monitoring in the first mode (240). In some embodiments, the data-related information may include PDCCH transmissions. In some embodiments, the data-related information may include Downlink Control Information (DCI). In some embodiments, the data-related information may include downlink assignments. In some embodiments, the data-related information may include Medium Access Control (MAC) protocol data units (PDUs) or MAC service data units (SDUs). In some embodiments, the data-related information may include transport blocks (TBs). In some embodiments, the data-related information may include Physical Downlink Shared Channel (PDSCH) transmissions. It should be understood that any other data-related information is also possible.

[0073] In other words, if no data-related information is received, the terminal device 110 may fall back to LPWUS mode (for example, by deactivating the main radio 142) and monitor LPWUS again. If data-related information is received, the terminal device 110 may maintain the second mode and perform the relevant operations. In this way, unnecessary PDCCH monitoring may be reduced and power consumption may be saved.

[0074] For illustrative purposes, several exemplary embodiments are described below in relation to Embodiments 1 to 4. <Embodiment 1>

[0075] In this embodiment, the terminal device 110 may perform PDCCH monitoring based on the DRX cycle. Referring to Figure 2, if data-related information is not received within the active time window of a predetermined number of DRX cycles, the terminal device 110 may determine that data-related information has not been received (241) and enter the first mode to perform LPWUS monitoring.

[0076] In some embodiments, if data-related information has not been received within a predetermined number of DRX cycle active time windows, the terminal device 110 may temporarily suspend or stop using DRX cycles for PDCCH monitoring.

[0077] In some embodiments, the predetermined number may be 1. That is, if data-related information is not received within the active time of the DRX cycle, the terminal device 110 may enter a first mode to monitor the LPWUS. It should be understood that the predetermined number may be any appropriate number. In some embodiments, the predetermined number may be set by the network device 120. In some embodiments, the predetermined number may be predefined.

[0078] Figure 3A is a schematic diagram 300A illustrating an exemplary fallback of the LPWUS mode based on the active time of the DRX cycle according to an embodiment of the present disclosure. As shown in Figure 3A, when receiving LPWUS at timing B, the main radio 142 may warm up and perform PDCCH monitoring based on the DRX cycle. In some embodiments where a predetermined number is 1, if no data-related information is received during the active time window 311, the terminal device 110 may enter LPWUS mode (for example, by deactivating the main radio 142) and monitor LPWUS.

[0079] In some embodiments where the predetermined number is 2, if no data-related information is received during the active time window 311, the terminal device 110 continues to perform PDCCH monitoring during the active time window 312. If no data-related information is received during the active time window 312, the terminal device 110 may enter LPWUS mode and monitor LPWUS.

[0080] For illustrative purposes, the example procedure may be described as follows: When detecting LPWUS, the UE performs the following: 1>When LPWUS is received and this UE is instructed to begin monitoring the PDCCH (or operating on the DRX): 2> Monitor PDCCH using DRX. When DRX is configured or used, the MAC entity (of this UE) performs the following: 1>If the DRX group is active: 2> Monitor PDCCH on the serving cell within this DRX group; 2>When PDCCH indicates DL (Downlink) transmission: 2>If LPWUS is configured for this UE (or if the UE monitors PDCCH by LPWUS detection during this DRX active time), and the active time (e.g., drx-onDurationTimer) expires: 3>If PDCCH, downlink assignment, or MAC PDU is not received within this active time: 4> Pause or stop using DRX; 4> Do not monitor PDCCH on the serving cell; 4> Enter LPWUS mode (i.e., monitor LPWUS again).

[0081] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0082] In this way, the terminal device may determine, based on the DRX active time, that data-related information has not yet arrived at the terminal device. Therefore, the terminal device no longer needs to remain connected and may fall back to LPWUS mode for power saving purposes. <Embodiment 2>

[0083] In this embodiment, DCP monitoring is configured for terminal device 110. Terminal device 110 may perform DCP monitoring before PDCCH monitoring, and if a DCP indicating the start of PDCCH monitoring is received, it may perform PDCCH monitoring based on the DRX cycle. In some embodiments, if a DCP indicates the start of the DRX on duration timer, the start of PDCCH monitoring is indicated by the DCP. That is, if a DCP indicating the start of the DRX on duration timer is received, terminal device 110 may perform PDCCH monitoring based on the DRX cycle.

[0084] Referring to Figure 2, if a DCP indicating the start of PDCCH monitoring has not been received, the terminal device 110 may determine that no data-related information has been received (242) and enter the first mode to perform LPWUS monitoring.

[0085] In some embodiments, if a DCP is received a predetermined number of times and the DCP indicates that the timer for the active time window of the DRX cycle has not been started (for example, the DCP includes a wake-up instruction bit of 0), the terminal device 110 may determine that no data-related information has been received and enter a first mode to perform LPWUS monitoring. In some embodiments, if a DCP is not received, the terminal device 110 may determine that no data-related information has been received and enter a first mode to perform LPWUS monitoring. In these embodiments, the terminal device 110 may pause or stop the use of the DRX cycle for PDCCH monitoring.

[0086] In some embodiments, the predetermined number of times may be 1. That is, if a DCP containing a wake-up instruction bit of 0 is received, the terminal device 110 may enter a first mode and monitor the LPWUS. It should be understood that the predetermined number of times may be any appropriate number. In some embodiments, the predetermined number of times may be set by the network device 120. In some embodiments, the predetermined number of times may be predefined.

[0087] Figure 3B is a schematic diagram 300B illustrating an exemplary fallback of the LPWUS mode based on DCP according to an embodiment of the present disclosure. As shown in the reference signal 320 in Figure 3B, when LPWUS is received at timing C, the main radio 142 may warm up and perform DCP monitoring.

[0088] In some embodiments where the predetermined number of times is 1, if a DCP containing a wake-up instruction bit of 0 is received at timing D, the terminal device 110 may enter LPWUS mode (for example, by deactivating the main radio 142) and monitor LPWUS, and PDCCH monitoring is canceled during the active time 321.

[0089] In some embodiments where the predetermined number of times is 2, if a DCP containing a wake-up instruction bit of 0 is received at timing D, the terminal device 110 may cancel PDCCH monitoring during active time 321 and continue to perform DCP monitoring in the connected state. If a DCP containing a wake-up instruction bit of 0 is received again at timing E, the terminal device 110 may enter LPWUS mode and monitor LPWUS. PDCCH monitoring during active time 322 may also be canceled.

[0090] As shown in the reference signal 320' in Figure 3B, when receiving LPWUS, the main radio 142 may warm up and perform DCP monitoring. If DCP is not received, the terminal device 110 may cancel PDCCH monitoring during the active time 321' and enter LPWUS mode to monitor LPWUS.

[0091] For illustrative purposes, the example procedure may be described as follows: When detecting LPWUS, the UE performs the following: 1>When LPWUS is received and this UE is instructed to begin monitoring the PDCCH (or operating on the DRX): 2> Monitor PDCCH using DRX. When DRX is configured or used, the MAC entity (of this UE) performs the following: 1>When a long DRX cycle is used for a DRX group, and [(SFN × 10) + subframe number] modulo (drx - LongCycle) = drx - StartOffset: 2>If DCP monitoring is configured for active DL BWP: 3> If a DCP instruction associated with the current DRX cycle received from a lower layer instructs the drx-onDurationTimer to start; or 3> If all DCP occasions in the time domain associated with the current DRX cycle occur during the active time, taking into account... or 3>If ps-Wakeup is set to true and no DCP instruction associated with the current DRX cycle has been received from a lower layer: 4> Start drx-onDurationTimer after drx-SlotOffset from the start of the subframe. 3> If LPWUS is configured for this UE (or if the UE uses DRX due to LPWUS detection), and the DCP instruction associated with the current DRX cycle received from the lower layer instructs not to start the drx-onDurationTimer (i.e., value "0"); or 3>If LPWUS is configured for this UE (or the UE uses DRX due to LPWUS detection), and no DCP instruction associated with the current DRX cycle has been received from the lower layer: 4> Pause or stop using DRX; 4> Do not monitor PDCCH on the serving cell; 4> Enter LPWUS mode (i.e., monitor LPWUS again); 2>Otherwise: 3> After the subframe starts and after drx-SlotOffset, start drx-onDurationTimer for this DRX group.

[0092] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0093] In this way, the terminal device may determine, based on the DCP, that no data-related information has arrived at the terminal device. Therefore, the terminal device no longer needs to remain connected and may fall back to LPWUS mode for power saving. <Embodiment 3>

[0094] In this embodiment, when LPWUS is received or the main radio 142 of the terminal device 110 is turned on (for example, fully warmed up), the terminal device 110 may start a timer. Continuing to refer to Figure 2, when the timer expires, the terminal device 110 may determine that no data-related information has been received (243) and enter a first mode to monitor LPWUS.

[0095] In some embodiments, when LPWUS is received, the terminal device 110 may enter a second mode based on the DRX cycle to perform PDCCH monitoring. In some embodiments, when data-related information is received in the second mode, the terminal device 110 may stop the timer.

[0096] In some embodiments, the network device 120 may configure a timer on the terminal device 110. For example, the timer (denoted as DataInactivityTimer) may be configured as follows: TIFF2026528701000002.tif5156 This is merely an example, and it should be understood that the timer may be any suitable existing or future-developed timer. In some alternative embodiments, the timer may be predefined.

[0097] Figure 3C is a schematic diagram 300C illustrating an exemplary fallback for a timer-based LPWUS mode according to an embodiment of the present disclosure. As shown by reference symbol 330 in Figure 3C, when receiving LPWUS, the main radio 142 may warm up and perform PDCCH monitoring based on the DRX cycle. The DataInactivityTimer is started when the main radio 142 is fully warmed up. As shown in the figure, no data-related information is received during the active time window 331. When the DataInactivityTimer expires, the terminal device 110 may enter LPWUS mode (for example, by deactivating the main radio 142) and monitor LPWUS. In this example, the DataInactivityTimer is started when the main radio 142 is fully warmed up, but in some other examples, the DataInactivityTimer may be started when receiving LPWUS.

[0098] As shown by reference symbol 330' in Figure 3C, when receiving LPWUS, the main radio 142 may warm up and perform PDCCH monitoring based on the DRX cycle. The DataInactivityTimer is started when the main radio 142 is fully warmed up. As shown in the figure, data-related information is received at timing F during the active time window 332. Therefore, the DataInactivityTimer is stopped. The terminal device 110 may continue to perform related operations in the connected state.

[0099] For illustrative purposes, the example procedure may be described as follows: When detecting LPWUS, the UE performs the following: 1> Monitor the PDCCH on the serving cell when MR (Main Radio) is activated; 1> If configured for LPWUS fallback purposes, start dataInactivityTimer; When dataInactivityTimer (for LPWUS) is configured, the UE in the RRC_CONNECTED state performs the following: 1> When any MAC entity receives a MAC SDU for a DTCH (Dedicated Traffic Channel) logical channel, a DCCH (Dedicated Control Channel) logical channel, a CCCH (Common Control Channel) logical channel, or a multicast MTCH (Multicast Traffic Channel) logical channel; or 1>When any MAC entity sends a MAC SDU to a DTCH logical channel or DCCH logical channel: 2>Stop dataInactivityTimer. 1>When dataInactivityTimer expires: 2> Indicates the expiration of dataInactivityTimer to the higher layer (RRC).

[0100] For illustrative purposes, another example procedure may be described as follows: While in RRC_CONNECTED state, when the UE receives an expired DataInactivityTimer from a lower layer for LPWUS fallback purposes, it does the following: 1> Perform an action to monitor LPWUS when entering / transitioning to LPWUS mode (deactivating MR).

[0101] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0102] In this way, the terminal device may determine, based on a timer, that no data-related information has arrived at the terminal device. Therefore, the terminal device no longer needs to remain connected and may fall back to LPWUS mode for power saving. <Embodiment 4>

[0103] In this embodiment, referring to Figure 2, when an LPWUS is received, the terminal device 110 may send a notification to the network device 120 that the terminal device 110 has entered a second mode due to the reception of the LPWUS (referred to herein as an LPWUS_trigger notification) (244).

[0104] In some embodiments, notifications may be transmitted via Uplink Control Information (UCI). In some embodiments, notifications may be transmitted via a Media Access Control (MAC) Control Element (CE). In some embodiments, notifications may be transmitted via RRC signaling. It should be understood that any other suitable method is also feasible.

[0105] The network device 120 may determine, based on the notification, whether a false alarm problem has occurred. In some embodiments, if a false alarm problem has occurred, the network device 120 may send an instruction to the terminal device 110 to enter a first mode (referred to herein as the LPWUS_fallback instruction) (245). Based on the instruction, the terminal device 110 may determine that no data-related information has been received and enter the first mode to monitor the LPWUS.

[0106] In some embodiments, instructions may be transmitted via Downlink Control Information (DCI). In some embodiments, instructions may be transmitted via MAC CE. In some embodiments, instructions may be transmitted via RRC signaling (e.g., RRC release messages or RRC rejection messages). It should be understood that any other suitable method is also feasible.

[0107] In some embodiments, when sending a notification, the terminal device 110 may start a timer (referred to herein as the LPWUS_notification timer). In some embodiments, when the timer expires, the terminal device 110 may determine that no data-related information has been received and enter a first mode to monitor the LPWUS. In some embodiments, when data-related information is received from the network device 120 (i.e., no false alarm problem occurs), the terminal device 110 may stop the timer. In some embodiments, when an instruction to enter a first mode is received from the network device 120 (i.e., a false alarm problem occurs), the terminal device 110 may also stop the timer.

[0108] In some embodiments, the timer may be configured. In some alternative embodiments, the timer may be predefined.

[0109] For illustrative purposes, the example procedure may be described as follows: When detecting LPWUS, the UE performs the following: 1> Monitor PDCCH on the serving cell when MR is activated; 1>If configured to provide LPWUS_trigger notification information: 2>Start the LPWUS_notification timer; 2> Start sending LPWUS_trigger notifications to the network (or submit the LPWUS_trigger notification message to the lower layer for transmission); or 2> Instruct the multiplexing and assembly procedures to generate an LPWUS_trigger notification MAC CE; or 2>UE sends a PUCCH for LPWUS_trigger notification. 1>When the LPWUS_notification timer expires: 2> Perform an action to monitor LPWUS when entering / transitioning to LPWUS mode (deactivating MR); 1>When the LPWUS_fallback instruction is received from the network via DCI / MAC CE / RRC: 2>Stop the LPWUS_notification timer; 2> Perform an action to monitor LPWUS when entering / transitioning to LPWUS mode (deactivating MR).

[0110] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0111] In this way, the network device may determine, based on the UE notification, whether a false alarm problem has occurred and then provide a corresponding response to the notification. Based on the response from the network device, the terminal device may fall back to LPWUS mode for power saving or continue to maintain the connection state for communication.

[0112] So far, the fallback of the LPWUS mode from PDCCH monitoring has been described. By process 200, unnecessary PDCCH monitoring may be reduced, and power saving in the terminal device may be achieved. <Implementation Example of Fallback from RA Procedure>

[0113] FIG. 4 is a schematic diagram showing another process 400 of communication according to an embodiment of the present disclosure. For the sake of explanation, process 400 will be described with reference to FIGS. 1A and 1B. In process 400, there may be cases where the terminal device 110 and the network device 120 as shown in FIG. 1A are involved. It should be understood that the steps and the order of the steps in FIG. 4 are for mere explanation and are not limiting. For example, the order of the steps may be changed. Some steps may be omitted, or any other appropriate additional steps may be added.

[0114] As shown in FIG. 4, the network device 120 may transmit the LPWUS configuration to the terminal device 110 (410). In some embodiments, the network device 120 may transmit the LPWUS configuration by SI or any other appropriate method. In some embodiments, the LPWUS configuration may indicate one or more occasions for LPWUS monitoring. In some embodiments, periodic monitoring may be configured for LPWUS monitoring. In some embodiments, always-on monitoring may be configured for LPWUS monitoring. It should be understood that the LPWUS configuration may also include any other appropriate information and may be transmitted in any other appropriate manner.

[0115] The terminal device 110 may perform LPWUS monitoring in the first mode based on the LPWUS configuration (420). In the first mode, the main radio 142 of the terminal device 110 is turned off, and the LPWUS receiver 141 of the terminal device 110 is turned on. In the context of the present disclosure, the first mode may also be referred to as the LPWUS mode or state, the sleep mode or state, or the ultra-deep sleep mode or state.

[0116] Continuing to refer to Figure 4, the network device 120 may transmit LPWUS to the terminal device 110 in LPWUS mode (430). Upon receiving LPWUS, the terminal device 110 may initiate an RA procedure in a second mode (440) (for example, by activating the main radio 142). The RA procedure indicates that the RA procedure is initiated upon receipt of LPWUS. In the second mode, the main radio 142 of the terminal device 110 is turned on, and the LPWUS receiver 141 of the terminal device 110 is turned off. In some embodiments, the second mode may be an idle or inactive state. In some embodiments, the second mode may be a connected state.

[0117] The network device 120 may know whether a false alarm problem occurs based on the reasons for the RA procedure. In some embodiments where incorrect or unnecessary paging is performed to the terminal device 110, the network device 120 may send a response indicating that the terminal device 110 is entering a first mode. Alternatively, the network device 120 may not send a response to the RA procedure.

[0118] Continuing to refer to Figure 4, the terminal device 110 may perform LPWUS monitoring in the first mode based on the response from the network device 120 (450).

[0119] For illustrative purposes, several exemplary embodiments are described below in relation to Embodiments 5 and 6. <Embodiment 5>

[0120] In this embodiment, terminal device 110 may initiate an RA procedure based on Contention Based Random Access (CBRA). Upon receiving an LPWUS, terminal device 110 may send a preamble to network device 120 using a contention-based preamble resource. Network device 120 may send a Random Access Response (RAR) to terminal device 110 that includes a Timing Advance (TA), an Uplink Grant, or a Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).

[0121] In some embodiments, upon receiving a RAR, terminal device 110 may send a request to establish or resume the RRC connection between terminal device 110 and network device 120. The request includes a first instruction that the request is sent upon receipt of LPWUS. In some embodiments, the first instruction may be included in the request as the cause of the request.

[0122] In some embodiments, the terminal device 110 may send an RRC setting request message that transmits a first instruction as the establishment cause. For illustrative purposes, exemplary establishment causes may be described as follows: In this example (TIFF2026528701000003.tif10156), if the RRC configuration request is initiated by the reception of LPWUS, the establishment cause may indicate "lpwus-triggered".

[0123] In some embodiments, the terminal device 110 may send an RRC restart request message that transmits a first instruction as the restart cause. For illustrative purposes, an exemplary restart cause may be described as follows: In this example (TIFF2026528701000004.tif8156), if the RRC restart request is initiated by the reception of LPWUS, the restart cause may indicate "lpwus-triggered".

[0124] The network device 120 may determine whether a false alarm problem occurs based on the cause of "lpwus-triggered". If a false alarm problem occurs, the network device 120 may send a response to the terminal device 110 that includes a second instruction to enter a first mode. In some embodiments, the network device 120 may send a response with an RRC release message. In some embodiments, the network device 120 may send a response with an RRC reject message.

[0125] The terminal device 110 may, based on the second instruction, enter the first mode (for example, by deactivating the main radio 142) and monitor the LPWUS.

[0126] In some embodiments, the terminal device 110 may initiate an RA procedure each time data is buffered into a logical channel of the Common Control Channel (CCCH). In some embodiments, if the network device 120 determines that no false alarm problem has occurred, the network device 120 may send an RRC setup message or an RRC restart message to the terminal device 110. In this way, the terminal device 110 may remain connected.

[0127] For illustrative purposes, the example procedure may be described as follows: When LPWUS is detected, the UE may initiate the RRC connection establishment / restart procedure; Step 1. The UE selects a contention-based preamble and executes the random access preamble transmission procedure. Step 2. The UE receives a downlink assignment (Msg2-MAC RAR) on the PDCCH for RA-RNTI (RA-RNTI: Random Access-Radio Network Temporary Identifier). Step 3. Process MAC RAR-Timing Advance Commands, Power Ramping, UL Grant, and TC-RNTI. After performing the above steps, the UE sends Msg3-UL transmission by including a UL-CCCH SDU (i.e., RRCSetupRequest / RRCResumeRequest) with the instruction (cause)-LPWUS_trigger. When Msg3 is sent, the MAC entity does the following: 1>When notification of the reception of a SpCell PDCCH transmission is received from a lower layer: 2>If the MAC PDU is decoded correctly: 3> Stop the ContentionResolutionTimer; 3> If the MAC PDU contains the UE contention resolution identifier MAC CE; and 3>If the UE contention resolution identifier in MAC CE matches the CCCH SDU sent in Msg3: 4> This contention resolution is considered successful, and the MAC PDU disassembly and demultiplexing are completed.

[0128] For illustrative purposes, another example procedure may be described as follows: When the UE receives an RRCRelease / RRCReject, the UE does the following: 1>Instruction (Cause) - If an RRCRelease / RRCReject message containing LPWUS_fallback is received in response to an RRCSetupRequest or RRCResumeRequest: 2> (You can first enter RRC_INACTIVE / IDLE) Enter LPWUS mode (while in RRC_IDLE / INACTIVE); 2> Deactivate MR and monitor LPWUS.

[0129] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0130] In this way, the network device may reject random access from a terminal device if it detects that the access is a false alarm. <Embodiment 6>

[0131] In this embodiment, the terminal device 110 may initiate the RA procedure based on Contention-Free Random Access (CFRA). In some embodiments, the network device 120 may configure a resource (also referred to herein as an RA resource) dedicated to LPWUS for the terminal device 110. In other words, if the terminal device 110 initiates the RA procedure upon receiving LPWUS, the terminal device 110 may initiate the RA procedure based on the RA resource dedicated to LPWUS. That is, the RA resource indicates that the RA procedure is initiated upon receiving LPWUS.

[0132] For illustrative purposes, an example configuration of RA resources may be described as follows: In this example, TIFF2026528701000005.tif65156, the information element "RACH-ConfigDedicatedForLpwus" indicates an RA resource dedicated to LPWUS.

[0133] In some embodiments, upon receiving an LPWUS, the terminal device 110 may use an RA resource to send a preamble to the network device 120. Based on the RA resource, the network device 120 may know that the reception of the LPWUS will initiate an RA procedure. The network device 120 may determine whether a false alarm problem has occurred and then decide whether to respond to the RA procedure.

[0134] In some embodiments, if a false alarm problem occurs (e.g., incorrect or unnecessary paging is performed to terminal device 110), the network device 120 does not have to send any response to terminal device 110. For example, the network device 120 does not have to send a RAR to terminal device 110. In some embodiments, if a false alarm problem does not occur (e.g., incorrect or unnecessary paging is not performed to terminal device 110), the network device 120 may send a RAR containing the preamble index to terminal device 110 within the RAR window. In some embodiments, if a false alarm problem does not occur (e.g., incorrect or unnecessary paging is not performed to terminal device 110), the network device 120 may send a PDCCH transmission to terminal device 110 addressed to a Cell-Radio Network Temporary Identifier (C-RNTI) specific to terminal device 110 within the RAR window.

[0135] In some embodiments, when transmitting a preamble, the terminal device 110 may initiate a RAR window and monitor for responses from the network device 120. In some embodiments, the terminal device 110 may monitor the PDCCH for MAC RAR based on a Random Access Radio Network Temporary Identifier (RA-RNTI) to check whether a preamble index exists in the MAC RAR that matches a preamble index selected by the terminal device 110. In some embodiments, if the RAR is received within a RAR window and the preamble index contained in the RAR does not match the index in the preamble, the terminal device 110 may determine that the response has not been successfully received from the network device 120. In some embodiments, if the RAR is not received within a RAR window, the terminal device 110 may determine that the response has not been successfully received from the network device 120.

[0136] In some embodiments, terminal device 110 may monitor PDCCH for MAC RAR based on C-RNTI specific to terminal device 110 to check whether a PDCCH addressed to C-RNTI exists. In some embodiments, network device 120 may provide C-RNTI to terminal device 110, and terminal device 110 may store C-RNTI during LPWUS mode. In some embodiments, if a PDCCH addressed to C-RNTI specific to terminal device 110 is not received within the RAR window, terminal device 110 may determine that the response has not been successfully received from network device 120.

[0137] In some embodiments, if a response is not successfully received from the network device 120 within the RAR window, the terminal device 110 may enter a first mode (for example, by deactivating the main radio 142) and monitor the LPWUS. In some embodiments, if a RAR containing the preamble index or a PDCCH transmission addressed to C-RNTI specific to the terminal device 110 is received, the terminal device 110 may remain connected.

[0138] For illustrative purposes, an example procedure for RA-RNTI may be described as follows: When a random access preamble is sent (for LPWUS), regardless of the possibility of measurement gaps occurring, the MAC entity performs the following: 1> In the first PDCCH occasion, after the random access preamble transmission is complete, the ra-ResponseWindow configured with RACH-ConfignDedicatedForLpwus is started. 1> While the ra-ResponseWindow is active, monitor the serving cell's PDCCH for random access responses identified by RA-RNTI. 1>If a downlink assignment is received on the PDCCH for RA-RNTI and the received TB is successfully decoded: 2> If the random access response includes a MAC subPDU with a random access preamble identifier corresponding to the sent PREAMBLE_INDEX: 3> This random access response is considered to have been received successfully. 2> If the receipt of a random access response is considered successful: 3> When the random access procedure is initiated for LPWUS trigger notification (i.e., enters normal / activated RRC_CONNECTED upon LPWUS reception): 2> Confirm LPWUS reception and maintain the RRC_CONNECTED state. 1>If the ra-ResponseWindow configured with RACH-ConfignDedicatedForLpwus expires and a random access response containing a random access preamble identifier matching the sent PREAMBLE_INDEX has not been received: 2> Assume that the random access response was not received successfully; 2> If the random access procedure is initiated for LPWUS trigger notification: 2> Enter LPWUS mode (deactivate MR) and monitor LPWUS.

[0139] For illustrative purposes, an example procedure for C-RNTI may be described as follows: When a random access preamble is sent, regardless of the possibility of measurement gaps occurring, the MAC entity performs the following: 1>When a contention-free random access preamble for LPWUS trigger notification is sent by the MAC entity: 2> In the first PDCCH occasion, after the random access preamble transmission is complete, the ra-ResponseWindow configured with RACH-ConfignDedicatedForLpwus is started. 2> While the ra-ResponseWindow is active, monitor the PDCCH transmission identified by C-RNTI. 1> When a notification of receipt of a PDCCH transmission is received from a lower layer on the serving cell from which the preamble was sent; and 1>If the PDCCH transmission is addressed to C-RNTI; and 1>If a contention-free random access preamble for LPWUS is sent by a MAC entity: 2> The random access procedure is considered to have completed successfully. 2> Confirm LPWUS reception and maintain the RRC_CONNECTED state. 1>When the ra-ResponseWindow configured with RACH-ConfignDedicatedForLpwus expires, and the PDCCH transmission addressed to C-RNTI has not been received on the serving cell from which the preamble was sent; 2> Assume that the random access response was not received successfully; 2> If the random access procedure is initiated for LPWUS trigger notification: 3> Enter LPWUS mode (deactivate MR) and monitor LPWUS.

[0140] Please understand that the example procedures described above are for illustrative purposes only and are not intended to be limiting.

[0141] In this way, the network device may reject random access from a terminal device if it detects that the access is a false alarm.

[0142] We have so far described the fallback to LPWUS mode from the RA procedure. Process 400 may reduce unnecessary RAs and may also achieve power savings in terminal devices.

[0143] It should be understood that the operations in processes 200 and 400 may be performed separately or in any appropriate combination. <Example of implementation of the method>

[0144] In accordance with the processes described above, embodiments of this disclosure provide communication methods implemented in terminal devices and network devices. These methods are described below with reference to Figures 5 to 7.

[0145] Figure 5 shows an exemplary method 500 of communication implemented in a terminal device according to several embodiments of the present disclosure. For example, method 500 may be implemented in a terminal device 110 as shown in Figure 1A. For illustrative purposes, method 500 will be described below with reference to Figure 1A. Method 500 may include additional blocks not shown, and / or some of the illustrated blocks may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect.

[0146] In block 510, the terminal device 110 receives LPWUS from the network device 120 in the first mode. In some embodiments, in the first mode, the main radio of the terminal device 110 is turned off and the LPWUS receiver of the terminal device 110 is turned on.

[0147] In block 520, the terminal device 110 performs PDCCH monitoring in a second mode. In some embodiments, in the second mode, the main radio of the terminal device 110 is turned on and the LPWUS receiver of the terminal device 110 is turned off.

[0148] In block 530, the terminal device 110 determines whether data-related information is received in the second mode. If data-related information is not received in the second mode, method 500 proceeds to block 540.

[0149] In block 540, the terminal device 110 performs LPWUS monitoring in the first mode.

[0150] In some embodiments, the terminal device 110 may perform PDCCH monitoring based on DRX cycles. If data-related information is not received within a predetermined number of DRX cycle active time windows, the terminal device 110 may determine that data-related information has not been received.

[0151] In some embodiments where DCP monitoring is configured, if a DCP has been received a predetermined number of times and the DCP indicates that the timer for the active time window of the DRX cycle has not been started, the terminal device 110 may determine that no data-related information has been received. In some embodiments, if no DCP has been received, the terminal device 110 may determine that no data-related information has been received.

[0152] In some embodiments where data-related information is not received, the terminal device 110 may suspend or stop using the DRX cycle for PDCCH monitoring. In some embodiments where data-related information is not received, the terminal device 110 may enter a first mode to monitor LPWUS.

[0153] In some embodiments, the terminal device 110 may start a timer when LPWUS is received or the main radio of the terminal device 110 is turned on. When the timer expires, the terminal device 110 may determine that no data-related information has been received. In some embodiments, the terminal device 110 may stop the timer when data-related information is received in the second mode.

[0154] In some embodiments, when LPWUS is received, terminal device 110 may send a notification to network device 120 indicating that terminal device 110 has entered a second mode due to the reception of LPWUS. In some embodiments, when an instruction to enter a first mode is received from network device 120, terminal device 110 may determine that no data-related information has been received. In some embodiments, when a notification is sent, terminal device 110 may start a timer. In some embodiments, when the timer expires, terminal device 110 may determine that no data-related information has been received. In some embodiments, when data-related information or an instruction is received from network device 120, terminal device 110 may stop the timer.

[0155] In some embodiments, data-related information may include at least one of the following: PDCCH transmission, DCI, downlink assignment, MAC PDU, TB, or PDSCH transmission.

[0156] In some embodiments, if the terminal device 110 determines that data-related information has been received in block 530, the terminal device 110 may maintain the second mode and perform the related operation.

[0157] Method 500 may enable fallback to LPWUS mode from PDCCH monitoring and reduce unnecessary power consumption for PDCCH monitoring.

[0158] Figure 6 shows another exemplary method 600 of communication implemented in a terminal device according to some embodiments of the present disclosure. For example, method 600 may be implemented in a terminal device 110 as shown in Figure 1A. For illustrative purposes, method 600 will be described below with reference to Figure 1A. Method 600 may include additional blocks not shown, and / or some blocks shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect.

[0159] In block 610, the terminal device 110 receives LPWUS from the network device 120 in the first mode. In some embodiments, in the first mode, the main radio of the terminal device 110 is turned off and the LPWUS receiver of the terminal device 110 is turned on.

[0160] In block 620, the terminal device 110 initiates the RA procedure in the second mode, which indicates that the RA procedure is initiated by the reception of LPWUS. In some embodiments, in the second mode, the main radio of the terminal device 110 is turned on and the LPWUS receiver of the terminal device 110 is turned off.

[0161] In some embodiments, terminal device 110 may send a request to network device 120 to establish or resume an RRC connection between terminal device 110 and network device 120, the request including a first instruction that the request is sent upon receipt of LPWUS. In some embodiments, the first instruction may be included in the request as the cause of the request.

[0162] In some embodiments, the terminal device 110 may send a preamble to the network device 120 based on a resource, where the resource indicates that the RA procedure will be initiated upon receipt of the LPWUS.

[0163] In block 630, the terminal device 110 performs LPWUS monitoring in a first mode based on its response to the RA procedure from the network device 120.

[0164] In some embodiments, the terminal device 110 may receive a response from the network device 120 that includes a second instruction to enter a first mode, and based on the second instruction, perform LPWUS monitoring in the first mode. In some embodiments, the response including the second instruction may be transmitted in an RRC release message or an RRC rejection message.

[0165] In some embodiments, if a response is not successfully received from the network device within the RAR window, the terminal device 110 may perform LPWUS monitoring in the first mode. In some embodiments, if a RAR is received within the RAR window and the preamble index included in the RAR does not match the index in the preamble, the terminal device 110 may determine that a response has not been successfully received from the network device 120. In some embodiments, if a RAR is not received within the RAR window, the terminal device 110 may determine that a response has not been successfully received from the network device 120. In some embodiments, if a PDCCH transmission addressed to C-RNTI specific to the terminal device 110 is not received within the RAR window, the terminal device 110 may determine that a response has not been successfully received from the network device 120.

[0166] Method 600 may enable fallback to LPWUS mode from RA and reduce unnecessary power consumption for RA.

[0167] Figure 7 shows an exemplary method 700 of communication implemented in a network device according to some embodiments of the present disclosure. For example, method 700 may be implemented in a network device 120 as shown in Figure 1A. For illustrative purposes, method 700 will be described below with reference to Figure 1A. Method 700 may include additional blocks not shown, and / or some of the illustrated blocks may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect.

[0168] In block 710, the network device 120 transmits LPWUS to the terminal device 110 in the first mode.

[0169] In block 720, the network device 120 executes the RA procedure initiated by the terminal device 110 in a second mode. The RA procedure is initiated by the reception of LPWUS.

[0170] In some embodiments, the network device 120 may receive a request from the terminal device 110 to establish or resume an RRC connection between the terminal device 110 and the network device 120. The request may include a first instruction that the request is sent upon receipt of an LPWUS. In some embodiments, the first instruction may be included in the request as the cause of the request.

[0171] In some embodiments, the network device 120 may receive a preamble from a terminal device on the resource, and the resource indicates that the random access procedure will be initiated upon receiving the LPWUS.

[0172] In block 730, the network device 120 determines its response to the RA procedure. In some embodiments, if incorrect or unnecessary paging occurs to the terminal device 110, the network device 120 may send a response to the terminal device 110 that includes a second instruction to enter a first mode. In some embodiments, the response including the second instruction may be transmitted in an RRC release message or an RRC rejection message.

[0173] In some embodiments, if incorrect or unnecessary paging occurs to terminal device 110, network device 120 may not send a response to the RA procedure to terminal device 110. In some embodiments, if incorrect or unnecessary paging does not occur to terminal device 110, network device 120 may send to terminal device 110 within the RAR window an RAR containing the preamble index, or a PDCCH transmission to terminal device 110 that is specific to C-RNTI.

[0174] Method 700 may enable fallback to LPWUS mode from the RA procedure and reduce unnecessary power consumption for RA.

[0175] Please understand that the operation of Methods 500 to 700 corresponds to the processes described in relation to Figures 2 to 4, and other details have been omitted here for the sake of brevity. <Example of device implementation>

[0176] Figure 8 is a simplified block diagram of an apparatus 800 suitable for carrying out embodiments of the present disclosure. Apparatus 800 can be considered as a further embodiment of a terminal device 110 or network device 120 as shown in Figure 1A. Thus, apparatus 800 can be implemented in or as part of a terminal device 110 or network device 120.

[0177] As shown in the figure, the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a suitable transceiver 840 coupled to the processor 810, and a communication interface coupled to the transceiver 840. The memory 810 stores at least a portion of the program 830. The transceiver 840 may be for bidirectional or unidirectional communication as required. The transceiver 840 may include at least one of a transmitter 842 or a receiver 844. The transmitter 842 and receiver 844 may be functional modules or physical entities. The transceiver 840 has at least one antenna to facilitate communication, but in practice, the access node referred to in this application may have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between Mobility Management Entities (MMEs) / Access and Mobility Management Functions (AMFs) / Serving Gateways (SGWs) / User Plane Functions (UPFs) and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and Relay Nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal devices.

[0178] Program 830 is assumed to include program instructions that, when executed by the associated processor 810, enable the device 800 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 1A to 7. Embodiments of the present disclosure may be implemented by computer software executable by the processor 810 of the device 800, by hardware, or by a combination of software and hardware. The processor 810 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 810 and memory 820 may form processing means 850 adapted to implement various embodiments of the present disclosure.

[0179] Memory 820 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including but not limited to non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. Although only one memory 820 is shown in device 800, device 800 may contain multiple physically different memory modules. Processor 810 may be of any type suitable for a local technology network and may include, but not limited to, one or more of the following: general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 800 may contain multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock synchronized with the main processor.

[0180] In some embodiments, the terminal device includes a circuit configured to receive LPWUS from a network device in a first mode, perform PDCCH monitoring in a second mode, and, in accordance with the determination that no data-related information has been received in the second mode, perform LPWUS monitoring in the first mode.

[0181] In some embodiments, the terminal device includes a circuit configured to perform the following: receive LPWUS from a network device in a first mode; initiate a random access procedure in a second mode, wherein the random access procedure indicates that the random access procedure is initiated by the reception of LPWUS; and perform LPWUS monitoring in the first mode based on the response from the network device to the random access procedure.

[0182] In some embodiments, the network device includes a circuit configured to transmit an LPWUS to a terminal device in a first mode, and to execute a random access procedure initiated by the terminal device in a second mode, wherein the random access procedure indicates that the random access procedure is initiated upon receipt of the LPWUS, and to determine a response to the random access procedure.

[0183] As used herein, the term “circuit” may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuits and software / firmware. As a further example, a circuit may be any part of a software-equipped hardware processor, such as a digital signal processor, software, and memory, which work together to enable a device such as a terminal or network device to perform various functions. In yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware for operation but may not have software when not needed for operation. As used herein, the term “circuit” also encompasses implementations of hardware circuits or processors alone, or implementations of hardware circuits or parts of processors, as well as implementations of software and / or firmware associated with them.

[0184] In summary, embodiments of this disclosure provide the following solutions:

[0185] One solution includes a processor configured to cause the terminal device to receive a low-power wake-up signal (LPWUS) from a network device in a first mode, perform physical downlink control channel (PDCCH) monitoring in a second mode, and, in the second mode, determine that no data-related information has been received, perform LPWUS monitoring in the first mode.

[0186] In some embodiments, the terminal device is configured to perform PDCCH monitoring by performing PDCCH monitoring based on discontinuous reception (DRX) cycles, and the terminal device is further configured to determine that data-related information has not been received based on the determination that data-related information has not been received within an active time window of a predetermined number of DRX cycles.

[0187] In some embodiments, the terminal device is configured to perform PDCCH monitoring by performing PDCCH monitoring based on discontinuous reception (DRX) cycles, and the terminal device is further configured to determine that data-related information has not been received according to a determination that downlink control information with cyclic redundancy checks scrambled by a low-power wireless network temporary identifier (DCP) has been received a predetermined number of times and the DCP indicates that the timer for the active time window of the DRX cycle has not been started, or to determine that data-related information has not been received according to a determination that the DCP has not been received.

[0188] In some embodiments, the terminal device is further configured to perform at least one of the following: pausing or stopping the use of the DRX cycle for PDCCH monitoring, or entering a first mode.

[0189] In some embodiments, the terminal device is further configured to start a timer upon determination that LPWUS is received or the terminal device's main radio is turned on, and to determine that no data-related information has been received upon determination that the timer has expired.

[0190] In some embodiments, the terminal device further stops the timer upon determination that data-related information is received in the second mode.

[0191] In some embodiments, the terminal device is further configured to send a notification to the network device that, upon determination that an LPWUS has been received, the terminal device has entered a second mode due to the reception of an LPWUS.

[0192] In some embodiments, the terminal device is further configured to perform at least one of the following: determining that no data-related information has been received in accordance with the determination that an instruction to enter a first mode has been received from the network device; starting a timer in accordance with the determination that a notification has been sent; determining that no data-related information has been received in accordance with the determination that the timer has expired; or stopping the timer in accordance with the determination that data-related information or instructions have been received from the network device.

[0193] In some embodiments, in a first mode, the main radio of the terminal device is turned off and the LPWUS receiver of the terminal device is turned on, and in a second mode, the main radio of the terminal device is turned on and the LPWUS receiver of the terminal device is turned off.

[0194] In some embodiments, data-related information includes at least one of the following: PDCCH transmission, downlink control information (DCI), downlink assignment, media access control (MAC) protocol data unit (PDU), transport block (TB), or physical downlink shared channel (PDSCH) transmission.

[0195] In another solution, the terminal device includes a processor configured to cause the terminal device to: receive a low-power wake-up signal (LPWUS) from a network device in a first mode; initiate a random access procedure in a second mode, the random access procedure indicating that the random access procedure is initiated by the reception of the LPWUS; and perform LPWUS monitoring in the first mode based on the response from the network device to the random access procedure.

[0196] In some embodiments, the terminal device is configured to initiate a random access procedure by sending a request to the network device for establishing or resuming a radio resource control (RRC) connection between the terminal device and the network device, the request including a first instruction that the request is sent upon receipt of LPWUS.

[0197] In some embodiments, the first instruction is included in the request as the cause of the request.

[0198] In some embodiments, the terminal device is configured to perform LPWUS monitoring by receiving a response from the network device that includes a second instruction to enter a first mode, and then performing LPWUS monitoring in the first mode based on the second instruction.

[0199] In some embodiments, the response, including the second instruction, is transmitted in an RRC release message or an RRC rejection message.

[0200] In some embodiments, the terminal device is configured to initiate a random access procedure by sending a preamble to the network device based on a resource, and the resource indicates that the random access procedure will be initiated upon receipt of LPWUS.

[0201] In some embodiments, the terminal device is configured to perform LPWUS monitoring by performing LPWUS monitoring in a first mode based on the determination that a response has not been successfully received from the network device within a Random Access Response (RAR) window.

[0202] In some embodiments, the terminal device is further configured to perform at least one of the following: determine that a response has not been successfully received from the network device based on the determination that a RAR was received within a RAR window and the preamble index included in the RAR does not match the index in the preamble; determine that a response has not been successfully received from the network device based on the determination that a RAR was not received within a RAR window; or determine that a response has not been successfully received from the network device based on the determination that a physical downlink control channel transmission addressed to a terminal device-specific cell radio network temporary identifier (C-RNTI) was not received within a RAR window.

[0203] In some embodiments, in a first mode, the main radio of the terminal device is turned off and the LPWUS receiver of the terminal device is turned on, and in a second mode, the main radio of the terminal device is turned on and the LPWUS receiver of the terminal device is turned off.

[0204] In another solution, the network device includes a processor configured to cause the network device to: transmit a low-power wake-up signal (LPWUS) to a terminal device in a first mode; execute a random access procedure initiated by the terminal device in a second mode, wherein the random access procedure indicates that the random access procedure is initiated upon receipt of the LPWUS; and determine a response to the random access procedure.

[0205] In some embodiments, the network device is configured to perform a random access procedure by receiving a request from a terminal device to establish or resume a radio resource control (RRC) connection between the terminal device and the network device, the request including a first instruction that the request is transmitted upon receipt of LPWUS.

[0206] In some embodiments, the first instruction is included in the request as the cause of the request.

[0207] In some embodiments, the network device is configured to determine a response to a random access procedure by sending a response to the terminal device that includes a second instruction to enter a first mode, in accordance with the determination that incorrect or unnecessary paging is being performed to the terminal device.

[0208] In some embodiments, the response, including the second instruction, is transmitted in an RRC release message or an RRC rejection message.

[0209] In some embodiments, a network device is configured to perform a random access procedure on a resource by receiving a preamble from a terminal device, and the resource indicates that the random access procedure is initiated upon receiving an LPWUS.

[0210] In some embodiments, the network device is configured to determine whether to respond to a random access procedure by, in accordance with the determination that incorrect or unnecessary paging is being performed to the terminal device, not sending a response to the random access procedure to the terminal device, or, in accordance with the determination that incorrect or unnecessary paging is not being performed to the terminal device, sending the terminal device a physical downlink control channel transmission to the terminal device within the random access response (RAR) window, which includes an index of the preamble, or to the terminal device's unique cell radio network temporary identifier (C-RNTI).

[0211] In some embodiments, in a first mode, the main radio of the terminal device is turned off and the LPWUS receiver of the terminal device is turned on, and in a second mode, the main radio of the terminal device is turned on and the LPWUS receiver of the terminal device is turned off.

[0212] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Various embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or some other graphical representations, but it will be understood that any block, apparatus, system, technique, or method described herein may be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controller, or other computing device, or some combination thereof.

[0213] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed on a device on a target real or virtual processor, and perform the processes or methods described above with reference to Figures 1A to 7. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functions of program modules may be combined or separated as needed in various embodiments. The machine-executable instructions for a program module may be executed in a local or distributed device. In a distributed device, the program module may reside on both local and remote storage media.

[0214] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagrams will be performed. The program codes may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0215] The above program code may be embodied in a machine-readable medium, which may be any tangible medium capable of containing or storing a program used by an instruction execution system, device, or apparatus, or a program used in conjunction with such a system or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any suitable combination thereof. More specific examples of machine-readable storage media include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0216] Furthermore, although the operations are presented in a specific order, it should not be understood that such operations must be performed in the specific order shown, sequentially, or all shown operations in order to obtain the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, the above description includes some specific implementation details, but these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented individually or in any suitable combination of sub-features in multiple embodiments.

[0217] While this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that this disclosure, as defined in the appended claims, is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, The aforementioned terminal device, In the first mode, a Low-Power Wake-Up Signal (LPWUS) is received from the network device. In the second mode, monitoring of the Physical Downlink Control Channel (PDCCH) is performed, and In the second mode, based on the determination that no data-related information has been received, LPWUS monitoring is performed in the first mode. Including a processor configured as follows: Terminal device.

2. The terminal device is configured to perform PDCCH monitoring by performing PDCCH monitoring based on a discontinuous reception (DRX) cycle, and the terminal device is further configured to perform PDCCH monitoring by performing PDCCH monitoring based on a discontinuous reception (DRX) cycle, and the terminal device is further configured to perform PDCCH monitoring by performing PDCCH monitoring based on a discontinuous reception (DRX) cycle, The system is configured to determine that data-related information has not been received, based on the determination that data-related information has not been received within a predetermined number of DRX cycles' active time window. The terminal device according to claim 1.

3. The terminal device is configured to perform PDCCH monitoring by performing PDCCH monitoring based on discontinuous reception (DRX) cycles, and the terminal device is further configured If downlink control information accompanied by cyclic redundancy checks scrambled by a Power Saving-Radio Network Temporary Identifier (DCP) is received a predetermined number of times, and the DCP indicates that the timer for the active time window of the DRX cycle has not been started, then it is determined that no data-related information has been received, or The system is configured to determine that data-related information has not been received, based on the determination that DCP has not been received. The terminal device according to claim 1.

4. The aforementioned terminal device further includes the following: To temporarily suspend or stop the use of the DRX cycle for monitoring the PDCCH, or Configured to perform at least one of the following: entering the first mode, The terminal device according to claim 2 or 3.

5. The aforementioned terminal device further, The timer is started according to the determination that the LPWUS is received or the main wireless of the terminal device is turned on, and The system is configured such that, upon determining that the timer has expired, it is determined that no data-related information has been received. The terminal device according to claim 1.

6. The aforementioned terminal device further, The timer is configured to stop in accordance with the determination that data-related information is received in the second mode. The terminal device according to claim 5.

7. The aforementioned terminal device further, In accordance with the determination that the LPWUS has been received, the terminal device is configured to send a notification to the network device indicating that it has entered the second mode due to the reception of the LPWUS. The terminal device according to claim 1.

8. The aforementioned terminal device further includes the following: In accordance with the determination that an instruction to enter the first mode is received from the network device, it is determined that no data-related information has been received. In accordance with the determination that the aforementioned notification has been sent, the timer is started. In accordance with the determination that the timer has expired, it is determined that no data-related information has been received, or The system is configured to perform at least one of the following: stopping the timer in accordance with a determination that data-related information or the instruction is received from the network device. The terminal device according to claim 7.

9. In the first mode described above, the main radio of the terminal device is turned off, the LPWUS receiver of the terminal device is turned on, and In the second mode, the main radio of the terminal device is turned on, and the LPWUS receiver of the terminal device is turned off. The terminal device according to claim 1.

10. The aforementioned data-related information is as follows: PDCCH transmission, Downlink Control Information (DCI) Downlink allocation, Medium Access Control (MAC) Protocol Data Unit (PDU) Transport Block (TB), or Physical Downlink Shared Channel (PDSCH) transmission, including at least one of the following: The terminal device according to claim 1.

11. A terminal device, The aforementioned terminal device, In the first mode, a low-power wake-up signal (LPWUS) is received from the network device, In the second mode, a random access procedure is initiated, wherein the random access procedure is indicated by the reception of the LPWUS. Based on the response from the network device to the random access procedure, LPWUS monitoring is performed in the first mode, Includes a processor configured to perform the following: Terminal device.

12. The aforementioned terminal device is The random access procedure is initiated by transmitting a request to the network device for establishing or resuming a Radio Resource Control (RRC) connection between the terminal device and the network device, wherein the request includes a first instruction that the request is transmitted upon reception by the LPWUS. The terminal device according to claim 11.

13. The terminal device according to claim 12, wherein the first instruction is included in the request as the cause of the request.

14. The aforementioned terminal device is Receiving the response from the network device, which includes a second instruction to enter the first mode, The system is configured to perform the LPWUS monitoring in the first mode based on the second instruction, The terminal device according to claim 12.

15. The terminal device according to claim 14, wherein the response including the second instruction is transmitted in an RRC release message or an RRC rejection message.

16. The aforementioned terminal device is The random access procedure is initiated by transmitting a preamble to the network device based on a resource, and the resource indicates that the random access procedure is initiated upon receipt of the LPWUS. The terminal device according to claim 11.

17. The aforementioned terminal device is The LPWUS monitoring is performed in the first mode by determining that the response has not been successfully received from the network device within the Random Access Response (RAR) window. The terminal device according to claim 16.

18. The aforementioned terminal device further includes the following: The determination that the response was not properly received from the network device is made based on the determination that the RAR was received within the RAR window and that the preamble index included in the RAR does not match the index of the preamble. In accordance with the determination that RAR was not received within the RAR window, it is determined that the response was not properly received from the network device, or The system is configured to perform at least one of the following: determining that a physical downlink control channel transmission addressed to a Cell-Radio Network Temporary Identifier (C-RNTI) unique to the terminal device has not been received within the RAR window, and determining that a response has not been successfully received from the network device. The terminal device according to claim 17.

19. In the first mode described above, the main radio of the terminal device is turned off, the LPWUS receiver of the terminal device is turned on, and In the second mode, the main radio of the terminal device is turned on, and the LPWUS receiver of the terminal device is turned off. The terminal device according to claim 11.

20. Network device, The aforementioned network device, In the first mode, a low-power wake-up signal (LPWUS) is transmitted to the terminal device, Executing a random access procedure initiated by the terminal device in a second mode, wherein the random access procedure indicates that it is initiated by the reception of the LPWUS, Determining the response to the aforementioned random access procedure, Includes a processor configured to perform the following: Network device.

Images