Communication method and device, and computer storage medium

Abstract

The embodiment of the invention relates to a communication method, equipment and a computer readable medium. The terminal device determines whether to apply a low power mode during which wake-up signal monitoring is performed. Based on the determination that the low power mode is applied, the terminal device performs an operation associated with the low power mode. In this way, notification of LP mode transition may be achieved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular, to methods, devices, and computer storage media for communicating during a low power mode that performs wake-up signal (WUS) monitoring. Background Art

[0002] At present, it has been proposed to use the primary radio to describe a conventional communication device that performs a normal radio resource control (RRC) state, and additionally design a wake-up signal (WUS) receiver to monitor the WUS to turn on the primary radio. When the terminal device is not receiving a service, the terminal device can enter a low power (LP) mode during which WUS monitoring is performed, for example, the primary radio is turned off and the WUS receiver is turned on to monitor the WUS. However, it is still unclear how to notify the transition of the LP mode. Summary of the invention

[0003] Generally speaking, embodiments of the present disclosure provide communication methods, devices, and computer storage media for notifying a transition of an LP mode.

[0004] In a first aspect, a communication method is provided, which includes: determining at a terminal device whether to apply a low power mode, performing wake-up signal monitoring during the low power mode; and performing an operation associated with the low power mode based on the determination of applying the low power mode.

[0005] In a second aspect, a communication method is provided. The method includes: determining at a terminal device whether to apply a low power mode, performing wake-up signal monitoring during the low power mode; and sending a request for applying the low power mode based on the determination to apply the low power mode.

[0006] In a third aspect, a communication method is provided, which includes: sending information to apply a low power mode at a network device, and performing wake-up signal monitoring during the low power mode.

[0007] In a fourth aspect, a communication method is provided. The method includes receiving, at a network device, a request to apply a low power mode, during which a main radio of a terminal device is turned off and a wake-up signal receiver of the terminal device is turned on.

[0008] In a fifth aspect, a communication device is provided, wherein the device comprises a processor, wherein the processor is configured to cause the device to execute a method according to any one of the first to fourth aspects of the present disclosure.

[0009] In a sixth aspect, a computer readable medium having instructions stored thereon is provided. When executed on at least one processor, the instructions cause the at least one processor to perform a method according to any one of the first to fourth aspects of the present disclosure.

[0010] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0012] Figure 1A shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0013] Figure 1B shows an example structure of a terminal device in which some embodiments of the present disclosure may be implemented;

[0014] Figure 1C shows a diagram illustrating a LP WUS mechanism in which some embodiments of the present disclosure may be implemented;

[0015] Figure 2 A schematic diagram illustrating a communication process according to an embodiment of the present disclosure is shown;

[0016] Figure 3A A schematic diagram showing a time window of a low power control channel (LPCCH) according to an embodiment of the present disclosure is shown;

[0017] Figure 3B A schematic diagram showing LPCCH scheduling according to an embodiment of the present disclosure is shown;

[0018] Figure 4 A schematic diagram illustrating another communication process according to an embodiment of the present disclosure is shown;

[0019] Figure 5 An example method of communication implemented at a terminal device according to some embodiments of the present disclosure is shown;

[0020] Figure 6 An example method of further communication implemented at a terminal device according to some embodiments of the present disclosure is shown;

[0021] Figure 7 An example method of communication implemented at a network device according to some embodiments of the present disclosure is shown;

[0022] Figure 8 illustrates an example method of further communications implemented at a network device according to some embodiments of the present disclosure; and

[0023] Fig. 9 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0024] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0025] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes, and to help those skilled in the art understand and implement the present disclosure, without implying any limitation to the scope of the disclosure. The disclosure described herein can be implemented in various ways different from the modes described below.

[0026] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0027] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs), 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 communications (MTC) devices, vehicle-mounted devices for V2X communications (where X represents pedestrians, vehicles, or infrastructure / network), devices for integrated access and backhaul (IAB), space-borne vehicles or airborne vehicles in non-terrestrial networks (NTNs) (including satellites and high altitude platforms (HAPs) including unmanned aerial systems (UAS)), extended reality (XR) devices (including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)), unmanned aerial vehicles (UAVs) (commonly referred to as drones, are aircraft without any human pilots), devices on high-speed trains (HSTs), or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback devices, or Internet appliances that enable wireless or wired Internet access and browsing, etc. The "terminal device" may also have "multicast / broadcast" capabilities to support public safety and mission-critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, Smart TV, radio services, wireless software delivery, group communications, and IoT applications. It may also contain one or more subscriber identity modules (SIMs), known as multi-SIMs. The term "terminal device" may be used interchangeably with UE, mobile station, user station, mobile terminal, user terminal, or wireless device.

[0028] The term "network equipment" refers to equipment that is capable of providing or hosting a cell or coverage with which a terminal device can communicate. Examples of network equipment include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a transmission reception point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS), etc.

[0029] The terminal device or network device may have artificial intelligence (AI) or machine learning capabilities, which generally include a model that has been trained for a specific function from a large amount of collected data and can be used to predict some information.

[0030] The terminal or network device can operate on several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), bands greater than 100GHz, and terahertz (THz). It can also operate on licensed / unlicensed / shared spectrum. In the case of multi-radio dual connectivity (MR-DC) applications, the terminal device can have more than one connection with the network device. The terminal device or network device can operate in full-duplex, flexible duplex, and cross-division duplex modes.

[0031] The embodiments of the present disclosure may be executed in a test device, such as a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal device, a test network device, and a channel emulator.

[0032] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a primary node, and the other may be a secondary node. The first network device and the second network device 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 sent to the terminal device from at least one of the first network device or the second network device. In one embodiment, the first information may be sent from the first network device to the terminal device, and the second information may be sent directly or via the first network device from the second network device to the terminal device. In one embodiment, information related to the configuration of the terminal device configured by the second network device may be sent from the second network device via the first network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent directly or via the first network device from the second network device to the terminal device.

[0033] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations are to be interpreted as open-ended terms, which mean "including but not limited to". The term "based on" is to be interpreted as "based at least in part on". The terms "one embodiment" and "embodiment" are to be interpreted as "at least one embodiment". The term "further embodiment" is to be interpreted as "at least one other embodiment". The terms "first", "second", etc. may refer to different or identical objects. Other explicit and implicit definitions may be included below.

[0034] In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and that such selection is not necessarily better, lesser, higher, or otherwise preferred over other selections.

[0035] In the context of the present 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”.

[0036] In the context of the present disclosure, the term "LP mode" may be used interchangeably with "LP WUS mode" or "LP WUS mechanism" or any other suitable term with similar functionality. The term "WUS" may be used interchangeably with "LP WUS" or any other suitable term with similar functionality. The term "LPCCH" may be used interchangeably with any other suitable term with similar functionality.

[0037] In the context of the present disclosure, the term "applying LP mode" may refer to at least one of the following:

[0038] 1. Turn off the main radio and turn on the LP-WUS receiver;

[0039] 2. Stop performing actions related to RRC_IDLE / INACTIVE, such as reception of SSB, SI, and paging;

[0040] 3. Exit RRC_IDLE / INACTIVE / CONNECTED and enter LP-WUS state; or

[0041] 4. Apply LP-WUS related configuration and monitor LP-WUS signal.

[0042] Typically, fifth generation (5G) devices consume tens of milliwatts in RRC idle or inactive states and hundreds of milliwatts in RRC connected states. Designing for extended battery life is necessary for improved energy efficiency and better user experience.

[0043] In order to meet the battery life requirements, it is expected to use an enhanced discontinuous reception (eDRX) cycle with a large value. The eDRX cycle may result in high latency and is therefore not suitable for services with both long battery life and low latency requirements. For example, in fire detection and fire extinguishing use cases, long eDRX cycles cannot meet the latency requirements. That is, eDRX is clearly not suitable for latency-critical use cases. Therefore, it is expected to study ultra-low power mechanisms that can support low latency (e.g., lower than the eDRX latency). In addition, it is expected to study and evaluate the layer 1 (L1) procedures and higher layer protocol changes required to support WUS.

[0044] As mentioned above, an LP mode is proposed during which WUS monitoring is performed. For example, during the LP mode, the main radio is turned off and the WUS receiver is turned on to monitor the main radio of the WUS. However, it is still unclear how to notify the transition of the LP mode. For example, it is unclear how the network notifies the terminal device or how the terminal device notifies the network to apply the LP mode.

[0045] In view of this, embodiments of the present disclosure provide communication solutions to overcome the above and other potential problems. In one aspect, a terminal device determines whether to apply LP mode. Based on the determination to apply LP mode, the terminal device can perform operations associated with LP mode. In this way, the network can trigger the terminal device to apply LP mode.

[0046] In another aspect, the terminal device determines whether to apply the LP mode. Based on the determination to apply the LP mode, the terminal device can send a request to apply the LP mode. In this way, the terminal device can request the network to apply the LP mode.

[0047] The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0048] Example of a communication network

[0049] Figure 1A 1 shows a schematic diagram of an example communication network 100A in which some embodiments of the present disclosure may be implemented. Figure 1AAs shown, the communication network 100A may include terminal devices 110, 111, and 112 and a network device 120. In some embodiments, the network device 120 may provide a service cell (also referred to herein as a cell) 121 to serve one or more terminal devices. In this example, the terminal devices 110, 111, and 112 are shown as being located in the cell 121 and being served by the network device 120.

[0050] It should be understood that Figure 1A The number of devices or cells in the communication network 100A is given for illustrative purposes and does not imply any limitation to the present disclosure. The communication network 100A may include any suitable number of network devices and / or terminal devices and / or cells suitable for implementing the present disclosure.

[0051] like Figure 1A As shown, each of the terminal devices 110, 111 and 112 can communicate with the network device 120 via a channel such as a wireless communication channel. The communication in the communication network 100A can comply with any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, Advanced LTE (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. The embodiments of the present disclosure can be performed according to any generation of communication protocols currently known or 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 networks or sixth generation (6G) networks.

[0052] Figure 1B A diagram 100B is shown illustrating a terminal device in which some embodiments of the present disclosure may be implemented. Figure 1A Description of terminal device 110 Figure 1B It should be understood that the terminal devices 111 and 112 may also have this structure 100B.

[0053] like Figure 1B As shown, the terminal device 110 may include a WUS receiver 131 and a main radio 132. The WUS receiver 131 is configured to monitor the WUS. The main radio 132 is configured as a conventional communication device that performs a normal radio resource control (RRC) state. In some embodiments, the WUS receiver 131 and the main radio 132 may be implemented in the same physical entity. In some embodiments, the WUS receiver 131 and the main radio 132 may be implemented in separate physical entities.

[0054] In some embodiments, the WUS receiver 131 can detect a WUS indicating that the primary radio 132 is turned off and trigger the primary radio 132 to enter an off or deep sleep state. In the off or deep sleep state, the terminal device 110 does not need to process the RRC idle or inactive or connected state process. In some embodiments, the WUS receiver 131 can detect a WUS indicating that the primary radio 132 is turned on and trigger the primary radio 132 to enter an on state. In the on state, the primary radio 132 can monitor the paging occasion (PO). Figure 1C Describe in more detail.

[0055] Figure 1C A diagram 100C is shown illustrating a LP WUS mechanism in which some embodiments of the present disclosure may be implemented. Figure 1B describe Figure 1C .like Figure 1C As shown, when the terminal device 110 enters the LP mode, the WUS receiver 131 may be turned on, and the main radio 132 may not monitor the PO. When the WUS receiver 131 detects a WUS indicating that the main radio 132 is turned on (e.g., WUS=1), the WUS receiver 131 triggers the main radio 132 to turn on and the WUS receiver 131 turns off. In this case, the main radio 132 may start monitoring the PO141.

[0056] Compared with the eDRX mechanism, the LP WUS mechanism can reduce both power consumption and latency. Although the WUS receiver is turned on in LP mode, the power consumption in LP mode may be 100 times smaller than the main radio because the WUS receiver only receives simple signals (e.g., OOK).

[0057] The network may need to trigger the terminal device to apply the LP mode. A terminal device in an idle state, an inactive state, or a connected state may apply the LP mode. However, the network cannot reach a terminal device in an idle or inactive state through a signal from each UE.

[0058] In view of this, the embodiments of the present disclosure provide a communication solution for notifying the conversion of the LP mode. Figures 2 to 4 Describe in detail.

[0059] Example implementation of LP mode network notification

[0060] In some embodiments, the terminal device 110 determines whether to apply the LP mode and performs WUS monitoring during the LP mode. In some embodiments, the terminal device 110 may determine to apply the LP mode based on receiving an indication from the network device 120. In some embodiments, the terminal device 110 may determine to apply the LP mode based on signal measurement.

[0061] If the terminal device 110 determines to apply the LP mode, the terminal device 110 performs operations associated with the LP mode. In some embodiments, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may indicate the reason for applying the low power mode from the lower layer of the terminal device 110 to the upper layer. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of a synchronization signal block (SSB), system information (SI), or a paging message. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0062] For illustration, the following will be combined with Examples 1 to 5 and Figure 2 Some example embodiments are described. Figure 2 A schematic diagram illustrating a communication process 200 according to an embodiment of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1A Process 200 is described. Process 200 may include the following: Figure 1A The terminal device 110 and the network device 120 are shown. It should be understood that Figure 2 The steps and order of steps in the embodiment are for illustration only and are not intended to be limiting. For example, the order of the steps may be changed, some steps may be omitted, or any other suitable additional steps may be added.

[0063] Example 1

[0064] In this embodiment, the information of the LP mode may be introduced into the RRC release message, so that the network may notify the terminal device in the connected state to apply the LP mode.

[0065] refer to Figure 2 In some embodiments, the network device 120 may send 211 an RRC release message including information of the LP mode (also referred to herein as first information for convenience) to the terminal device 110. In some embodiments, the information of the LP mode may include an indication of the LP mode. The indication of the LP mode may be performed in any suitable manner.

[0066] In some embodiments, the information of the LP mode may include a configuration for the LP mode. In some embodiments, the configuration for the LP mode may include a time domain configuration indicating where the terminal device 110 should monitor the LP WUS from a time domain view. In some embodiments, the configuration for the LP mode may include a frequency domain configuration indicating where the terminal device 110 should monitor the LP WUS from a frequency domain view. In some embodiments, the configuration for the LP mode may include an LP WUS sequence configuration indicating the LP WUS mode. In some embodiments, the configuration for the LP mode may include an LP WUS group configuration indicating which LP WUS UE group the terminal device 110 should monitor. It should be understood that the configuration for the LP mode may include any combination of the above configurations and any other suitable configurations.

[0067] In some embodiments, the information of the LP mode may include a timer for the LP mode. It should be understood that the information of the LP mode may include any combination of the above information and any other suitable information.

[0068] For example, the RRC release message may be configured as follows.

[0069]

[0070] In this example, an information element (IE) "indicationLP-WUS" is included in the RRC release message. The IE "indicationLP-WUS" includes a time domain configuration (timeDomainConfig), a frequency domain configuration (frequencyDomainConfig), a LP-WUS sequence configuration (sequenceConfig), and a LP-WUS group configuration (groupConfig).

[0071] In another example, the RRC release message may be configured as follows.

[0072]

[0073] In this example, IE "indicationLP-WUS" is included in the RRC release message. IE "indicationLP-WUS" includes a timer (lp-wusTimer), a time domain configuration (timeDomainConfig), a frequency domain configuration (frequencyDomainConfig), a LP-WUS sequence configuration (sequenceConfig), and a LP WUS group configuration (groupConfig) for LP mode.

[0074] It should be understood that the above RRC release message is merely an example and is not intended to be limiting.

[0075] After receiving the RRC release message including the LP mode information, the terminal device 110 may determine to apply the LP mode. In some embodiments, if the RRC release message is received, the terminal device 110 may start a timer. If the timer expires, the terminal device 110 may determine to apply the LP mode.

[0076] In some embodiments where the terminal device 110 supports mobility in low power mode, the terminal device 110 may restart the timer if a cell reselection condition is met while the timer is running. In some embodiments, if the terminal device 110 performs a small data transfer (SDT) procedure and the timer is running, the terminal device 110 may restart the timer. In some embodiments, if the terminal device 110 receives a multicast and broadcast service (MBS) and the timer is running, the terminal device 110 may restart the timer.

[0077] In some embodiments where the terminal device 110 does not support mobility in low power mode, the terminal device 110 may stop the timer if a cell reselection condition is met while the timer is running. In some embodiments, if the terminal device 110 enters a connected state and the timer is running, the terminal device 110 may stop the timer.

[0078] After determining to apply the LP mode, the terminal device 110 may perform 212 operations associated with the LP mode. In some embodiments, the terminal device 110 may indicate the release reason "apply LP mode" from the RRC layer to the layer of the non-access layer (NAS). It should be understood that the release reason may take any other form with similar functions.

[0079] In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of SSB, SI, or paging messages. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0080] To illustrate, an example process may be described as follows.

[0081] After receiving RRCRelease, the UE shall:

[0082] 1> If RRCRelease includes Indicationlp-WUS:

[0083] 2> If the LP-WUS timer is included:

[0084] 3> Start a timer with the timer value set to lp-wusTimer; (now UE will perform actions related to RRC_IDLE / INACTIVE)

[0085] 2> Otherwise:

[0086] 3> Indicate the reason "Apply LP-WUS" to the upper layer (i.e. UE NAS) (if supported);

[0087] 3> (optionally) stop performing actions related to RRC_IDLE / INACTIVE (e.g., reception of SSB, SI, paging);

[0088] 3> Apply the received LP-WUS related configuration for LP-WUS monitoring;

[0089] 3>Monitor LP-WUS signal;

[0090] While the LP-WUS timer is running, the UE shall continue cell reselection related measurements and cell reselection evaluation.

[0091] 1> If the cell reselection conditions are met when the LP-WUS timer is running:

[0092] (Option 1 for LP-WUS mobility capable UE)

[0093] 2>Restart the LP-WUS timer;

[0094] (Option 2 for non-LP-WUS mobility capable UE)

[0095] 2>Stop the LP-WUS timer.

[0096] For example, another example process may be described as follows.

[0097] The UE shall:

[0098] 1> If the LP-WUS timer expires:

[0099] 2> Indicate the reason "Apply LP-WUS" to the upper layer (i.e. UE NAS) (if supported);

[0100] 2> (optionally) stop performing actions related to RRC_IDLE / INACTIVE (e.g., reception of SSB, SI, paging);

[0101] 2> Apply the received LP-WUS related configuration for LP-WUS monitoring;

[0102] 2>Monitor the LP-WUS signal.

[0103] For example, another example process may be described as follows.

[0104] When the UE enters RRC_CONNECTED, the UE shall stop the LP-WUS timer if it is running.

[0105] When the UE performs the SDT procedure, the UE shall restart the LP-WUS timer if it is running.

[0106] When the UE receives an MBS session, the UE shall restart the LP-WUS timer if it is running.

[0107] Example 2

[0108] In this embodiment, the information of the LP mode may be introduced into the paging message, so that the network can inform the terminal equipment in the idle or inactive state to apply the LP mode.

[0109] Continue to refer Figure 2 In some embodiments, the network device 120 may send 213 a paging message to the terminal device 110, the paging message including information of the LP mode (also referred to herein as second information for convenience). In some embodiments, the information of the LP mode may include a set of identifiers of the terminal device. It should be understood that the information of the LP mode may include any other suitable information.

[0110] In some embodiments, the identifiers in the identifier set may be radio network temporary identifiers (RNTIs). For example, inactive radio network temporary identifiers (I-RNTIs) or any other suitable form of RNTIs. In some embodiments, the identifiers in the identifier set may be temporary mobile station identifiers (TMSIs). For example, 5G-S-TMSIs or any other suitable form of TMSIs. It should be understood that the identifiers may take any other suitable form.

[0111] To illustrate, an example paging message may be configured as follows.

[0112]

[0113] In this example, the paging message includes an IE “Paging-v1800-IE” and the IE “Paging-v1800-IE” includes an IE “PagingNotificationList.” The IE “PagingNotificationList” includes a UE identity “PagingUE-Identity.” It should be understood that this paging message is merely an example and is not intended to be limiting.

[0114] In some embodiments, the network device 120 may also send downlink control information (DCI) scheduling the reception of a paging message and including only an indication of the LP mode to the terminal device 110. In other words, a configuration for a short message indicator may be introduced in the paging DCI. For example, an example short message indicator may be configured as shown in Table 1.

[0115] Table 1

[0116] Bit Field Short message indicator 00 There is only LP-WUS information for paging in DCI 01 There is only scheduling information for paging in DCI 10 Only short messages exist in DCI 11 There are at least two types of the above messages in DCI

[0117] In this example, the bit field "00" in the short message indicator may be used to indicate that there is only information of the LP mode in the paging DCI.

[0118] After receiving the paging message including the LP mode information, if the identifier in the paging message (e.g., in the IE "PagingNotificationList") matches the identifier of the terminal device 110, the terminal device 110 may determine to apply the LP mode. After determining to apply the LP mode, the terminal device 110 may perform 214 operations associated with the LP mode. In some embodiments, the terminal device 110 may indicate the paging cause "apply LP mode" from the RRC layer to the NAS layer. It should be understood that the paging cause may take any other form with similar functions.

[0119] In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of SSB, SI, or paging messages. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0120] To illustrate, an example process may be described as follows.

[0121] After receiving the paging message, the UE shall:

[0122] 1> If in RRC_IDLE, for each of the PagingNotifications (if any) included in the Paging Message:

[0123] 2> If the ue-Identity included in the PaingNotification matches the UE identity assigned by the upper layer (i.e., 5G-S-TMSI):

[0124] 3>Forward reason "Apply LP-WUS" (if supported) to the upper layer;

[0125] 3> (optionally) stop performing actions related to RRC_IDLE (e.g., reception of SSB, SI, paging);

[0126] 3>Monitor LP-WUS signal.

[0127] 1> If in RRC_INACTIVE, for each of the PagingNotifications (if any) included in the Paging Message:

[0128] 2> If the ue-Identity included in the PagingNotification matches the UE's stored fullI-RNTI, or

[0129] 2> If the ue-Identity contained in the PagingNotification matches the UE identity assigned by the upper layer:

[0130] 3>Forward reason "Apply LP-WUS" (if supported) to the upper layer;

[0131] 3> (optionally) stop performing actions related to RRC_INACTVE (e.g., reception of SSB, SI, paging);

[0132] 3>Monitor LP-WUS signal.

[0133] Example 3

[0134] In this embodiment, the paging cause of the LP mode can be introduced into the paging message. In this way, the network can also notify the terminal equipment in the idle or inactive state to apply the LP mode.

[0135] In some embodiments, both the radio access network (RAN) and the core network (CN) may initiate a paging cause. In this way, the RAN or the CN may use a paging method carrying a paging cause to notify the terminal device to apply the LP mode.

[0136] Continue to refer Figure 2In some embodiments, the terminal device 110 may receive 215 a paging message including a set of identifiers of the terminal device and a set of paging causes corresponding to the set of identifiers. In other words, one identifier corresponds to one paging cause. In some embodiments, the identifiers in the set of identifiers may be RNTIs, such as I-RNTIs or any other suitable form of RNTIs. In some embodiments, the identifiers in the set of identifiers may be TMSIs. For example, 5G-S-TMSIs or any other suitable form of TMSIs. It should be understood that the identifiers may take any other suitable form.

[0137] To illustrate, an example paging message may be configured as follows.

[0138]

[0139] In this example, the paging message includes a paging record set (PagingRecordList). Each paging record includes a UE identity (PagingUE-Identity) and a corresponding paging cause (pagingCause-r17). The paging cause may indicate an LP mode (lp-wus). It should be understood that the paging message is merely an example and is not intended to be limiting.

[0140] In some embodiments, if an identifier in the identifier set matches the identifier of the terminal device 110, the terminal device 110 may determine whether the paging cause corresponding to the identifier of the terminal device 110 indicates a low power mode. If the paging cause indicates a low power mode, the terminal device 110 may determine to apply the low power mode.

[0141] After determining to apply the LP mode, the terminal device 110 may perform 216 operations associated with the LP mode. In some embodiments, the terminal device 110 may indicate the paging cause "apply LP mode" from the RRC layer to the NAS layer. It should be understood that the paging cause may take any other form with similar functions.

[0142] In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of SSB, SI, or paging messages. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0143] To illustrate, an example process may be described as follows.

[0144] After receiving the paging message, the UE shall:

[0145] 1> If in RRC_IDLE, for each PagingRecord (if any) included in the Paging Message:

[0146] 2> If the ue-Identity included in the PagingRecord matches the UE identity assigned by the upper layer:

[0147] 3> If paging cause is included and paging cause is set to "lp-wus":

[0148] 4> Forward ue-Identity and paging reason to the upper layer;

[0149] 4> (optionally) stop performing actions related to RRC_IDLE / INACTIVE (such as SSB / SI / paging);

[0150] 4>Monitor LP-WUS signal.

[0151] 1> If in RRC_INACTIVE, for each PagingRecord (if any) included in the Paging Message:

[0152] 2> If the ue-Identity included in the PagingRecord matches the UE's stored fullI-RNTI, or

[0153] 2> If the ue-Identity included in the PagingRecord matches the UE identity assigned by the upper layer:

[0154] 3> If paging cause is included and paging cause is set to "lp-wus":

[0155] 4> Forward ue-Identity and paging reason to the upper layer;

[0156] 4> (optionally) stop performing actions related to RRC_IDLE / INACTIVE (such as SSB / SI / paging);

[0157] 4>Monitor LP-WUS signal.

[0158] Example 4

[0159] In this embodiment, a channel may be introduced to provide configuration and notification of the terminal device application for the LP mode. In other words, the channel is dedicated to the notification of the LP mode. The channel may be called a low power control channel (LPCCH) or any other name. In this way, the network can also notify the terminal device in an idle or inactive state to apply the LP mode.

[0160] Continue to refer Figure 2 In some embodiments, the terminal device 110 may obtain 217 channel information from the SI. For example, a system information block (SIB) may be configured to provide information about a channel. The information about a channel may be about how to obtain a channel. It should be understood that the SIB may be any SIB that is existing or to be developed. In some embodiments, the information about a channel may include at least one of: the length and offset of a channel repetition period; the starting time slot of a transmission window of a channel; or the duration of a transmission window. For example, an example SIB (SIBX-r18) may be configured as follows.

[0161]

[0162] In this example, the LPCCH configuration (lpcch-Config) is provided in the SIB. The LPCCH configuration includes: the length and offset of the repetition period of the channel (lpcch-RepetitionEeriodAndOffset), the starting time slot of the transmission window of the channel (for convenience, also referred to as the LPCCH window in this document) (lpcch-windowStartSlot), and the duration of the transmission window (lpcch-windowDuration). It should be understood that this is only an example and is not intended to be limiting.

[0163] In some embodiments, the terminal device 110 may obtain the search space and control resource set (CORESET) for LPCCH-PDCCH monitoring from SIB1 (eg, PDCCHConfig).

[0164] Based on the information of the channel and the search space and the CORESET for LPCCH-PDCCH monitoring, the terminal device 110 may determine 218 a set of opportunities for monitoring the channel. The set of opportunities is associated with a synchronization signal block set (SSB).

[0165] In some embodiments, the channel may be scheduled in a set of radio frames for which equation (1) is true.

[0166] N mod L = O (1)

[0167] Wherein, N represents the system frame number (SFN) of the radio frame, L represents the length of the repetition period, and O represents the offset of the repetition period.

[0168] Figure 3A A schematic diagram 300A of a time window of an LPCCH according to an embodiment of the present disclosure is shown. In this example, it is assumed that the subcarrier spacing (SCS) = 30 KHz, the repetition period = 2 radio frames, the offset of the repetition period = 1 radio frame, the starting time slot = 2 time slots, and the duration = 4 time slots. Based on equation (1), it can be concluded that the LPCCH windows 301, 302 at SFN = 1, 3 will be scheduled for LPCCH. It should be understood that this is merely an example and is not intended to be limiting.

[0169] In some embodiments, the terminal device 110 may determine a candidate timing set that does not overlap with an uplink symbol as a timing set based on the search space for the channel and the information of the channel. The terminal device 110 may also determine the mapping between the timing set and the SSB set based on the index of the timing, the index of the SSB, the number of timings in the transmission window, and the number of SSBs actually transmitted. For example, the [x×N+K]th PDCCH monitoring timing of the LPCCH message in the LPCCH window corresponds to the Kth SSB transmitted, where x=0,1,...X-1,K=1,2,...N, N represents the number of SSBs actually transmitted determined according to ssb-PositionsInBurst in SIB1 and X=CEIL (the number of PDCCH monitoring opportunities in the LPCCH window / N). It should be understood that this is merely an example, and any other suitable method for determining the mapping is also feasible.

[0170] In some embodiments, the terminal device 110 assumes that in the LPCCH window, the PDCCH for the LPCCH message is transmitted in at least one PDCCH monitoring opportunity corresponding to each transmitted SSB, so the selection of the SSB for receiving the LPCCH message depends on the UE implementation.

[0171] Figure 3B FIG. 300B shows a schematic diagram of LPCCH scheduling according to an embodiment of the present disclosure. Figure 3B As shown, there are 8 available LPCCH-PDCCH opportunities (depending on the search space of LPCCH) in one LPCCH window 310, and opportunity 311 overlaps with uplink symbols and is therefore skipped when numbering opportunities. There are 4 SSB transmissions in one SSB burst 320 (depending on ssb-PositionsInBurst).

[0172] As mentioned above, the [x×N+K]th PDCCH monitoring opportunity of the LPCCH message in the LPCCH window corresponds to the Kth transmitted SSB, where x=0,1,...X-1, K=1,2,...N, and N represents the number of SSBs actually transmitted determined according to ssb-PositionsInBurst in SIB1 and X=CEIL (the number of PDCCH monitoring opportunities in the LPCCH window / N). It can be concluded that opportunities 1 and 5 correspond to SSB1, opportunities 2 and 6 correspond to SSB2, opportunities 3 and 7 correspond to SSB3, and opportunities 4 and 8 correspond to SSB4. The same content can be sent at opportunities 1 to 8. It should be understood that this is merely an example and is not intended to be limiting.

[0173] After determining the opportunity set associated with the SSB set, the terminal device 110 can monitor 219 the channel on the opportunity set. The network device 120 can send a message through the channel. In some embodiments, the message can include a list of terminal device identifiers. In this way, it can be notified which terminal device should apply the LP mode.

[0174] In some embodiments, the identifier in the identifier list may be an RNTI, for example, an I-RNTI or any other suitable form of an RNTI. In some embodiments, the identifier in the identifier list may be a TMSI, for example, a 5G-S-TMSI or any other suitable form of a TMSI. It should be understood that the identifier may be in any other suitable form.

[0175] In some embodiments, the message may include a configuration for the LP mode. For example, a time domain configuration, a frequency domain configuration, a LP-WUS sequence configuration, a LP-WUS group configuration, or any combination of the above configurations and any other suitable configuration. It should be noted that the message may include any combination of the above information and any other suitable information.

[0176] In some embodiments, network device 120 may specify a fixed RNTI for descrambling the LPCCH-PDCCH. For example, network device 120 may use any reserved RNTI value (eg, 0xFFF3-0xFFFC) as the fixed RNTI.

[0177] For example, the sample message may be configured as follows.

[0178]

[0179] In this example, the message includes an identification list of terminal devices (lp-wusIndicationList) and a configuration for LP mode (lp-wusConfiguration). This is merely an example and is not intended to be limiting.

[0180] After receiving the message from the channel, if the identification included in the message matches the identification of the terminal device 110, the terminal device 110 may determine to apply the low power mode.

[0181] After determining to apply the LP mode, the terminal device 110 may perform 220 operations associated with the LP mode. In some embodiments, the terminal device 110 may indicate the cause "apply LP mode" from the RRC layer to the NAS layer. It should be understood that the cause may take any other form with similar functions.

[0182] In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of SSB, SI, or paging messages. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0183] To illustrate, an example process may be described as follows.

[0184] Part 1 SIBx

[0185] A UE with LP-WUS functionality shall:

[0186] 1> If the UE enters a cell that broadcasts SIBx:

[0187] 2> Get LPCCH information based on the specified SIBx configuration and formula (e.g., indication / LP-WUS configuration).

[0188] Part 2 LPCCH-PDCCH Scheduling

[0189] LPCCH information is sent periodically within the configured transmission window using a configurable repetition period. LPCCH transmissions are indicated via a PDCCH addressed to the LPCCH-RNTI. The PDCCH monitoring timings for LPCCH transmissions are determined based on the common search space indicated by searchspaceLPCCH. If searchspaceLPCCH is set to zero, the PDCCH monitoring timings for LPCCH message reception in the MCCH transmission window are the same as the PDCCH monitoring timings for SIB1. If searchspaceLPCCH is not set to zero, the PDCCH monitoring timings for LPCCH messages are determined based on the search space indicated by searchspaceLPCCH. The PDCCH monitoring timings for LPCCH messages that do not overlap with UL symbols are numbered sequentially from the LPCCH transmission window. The [x×N+K]th PDCCH monitoring opportunity of the LPCCH message in the LPCCH transmission window corresponds to the Kth transmitted SSB, where x=0,1,...X-1,K=1,2,...N, N is the number of SSBs actually transmitted determined according to ssb-PositionsInBurst in SIB1, and X is equal to CEIL(number of PDCCH monitoring opportunities in the LPCCH transmission window / N). The UE assumes that in the LPCCH transmission window, the PDCCH of the LPCCH message is transmitted in at least one PDCCH monitoring opportunity corresponding to each transmitted SSB, and therefore the selection of the SSB for receiving the MCCH message depends on the UE implementation.

[0190] Part 3 LPCCH Message

[0191] After receiving the LPCCH message, the UE shall:

[0192] 1> For each in LP-WUSIndication, if the ue-Identity included in the LP-WUSIndication matches the UE identity (i.e. 5G-S-TMSI) or fullI-RNTI assigned by upper layers:

[0193] 2> Apply the received LP-WUS configuration (e.g., time-frequency domain configuration / group configuration / sequence configuration);

[0194] 2> (optionally) stop performing actions related to RRC_IDLE / INACTVE (e.g., reception of SSB, SI, paging);

[0195] 2>Monitor the LP-WUS signal.

[0196] Example 5

[0197] In this embodiment, the terminal device 110 may decide on its own to apply LP based on the configuration from the network device 120. In this way, flexible control of LP-WUS monitoring may be performed by the terminal device.

[0198] Continue to refer Figure 2 In some embodiments, the terminal device 110 may receive 221 a configuration for the LP mode. The configuration may include a set of measurement criteria. In some embodiments, the terminal device 110 may receive an RRC release message including a configuration for the LP mode. In some embodiments, the terminal device 110 may receive an SI including a configuration for the LP mode. It should be understood that the terminal device 110 may receive a configuration for the LP mode in any other suitable manner.

[0199] In some embodiments, the measurement criteria set may include measurement criteria for terminal devices with low mobility or fixed. For example, an exemplary measurement criteria for terminal devices with low mobility may be configured as follows.

[0200]

[0201] It should be understood that any other suitable manner is also possible.

[0202] In some embodiments, the set of measurement criteria may include measurement criteria for terminal devices that are not at a cell edge.

[0203]

[0204]

[0205] It should be understood that any other suitable manner is also feasible. The measurement standard set may include any other suitable standards and is not limited to the above examples.

[0206] In some embodiments, the configuration for the LP mode may also include a time domain configuration indicating where the terminal device 110 should monitor the LP WUS from a time domain view. In some embodiments, the configuration for the LP mode may include a frequency domain configuration indicating where the terminal device 110 should monitor the LP WUS from a frequency domain view. In some embodiments, the configuration for the LP mode may include an LP WUS sequence configuration indicating an LP WUS mode. In some embodiments, the configuration for the LP mode may include an LP WUS group configuration indicating which LP WUS UE group the terminal device 110 should monitor. It should be understood that the configuration for the LP mode may include any combination of the above configurations and any other suitable configurations.

[0207] The terminal device 110 may perform 222 signal measurements based on the set of measurement criteria. If the set of measurement criteria is met, the terminal device 110 may determine to apply a low power mode.

[0208] After determining to apply the LP mode, the terminal device 110 may perform 223 operations associated with the LP mode. In some embodiments, the terminal device 110 may indicate the cause "apply LP mode" from the medium access control (MAC) layer to the RRC layer. It should be understood that the cause may take any other form with similar functions.

[0209] In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132. In some embodiments, the terminal device 110 may turn on the WUS receiver 131. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. For example, the terminal device 110 may stop receiving at least one of SSB, SI, or paging messages. In some embodiments, the terminal device 110 may apply a configuration for a low power mode. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that the operations associated with the LP mode may include any combination of the above operations and any other suitable operations.

[0210] To illustrate, an example process may be described as follows.

[0211] Part 1RRCRelease

[0212] After receiving RRCRelease, the UE with LP-WUS function shall:

[0213] 1> If RRCRelease includes LP-WUS related configuration:

[0214] 2> If the LP-WUS measurement standard is included:

[0215] 3>Store LP-WUS related configuration; (meaning that the UE will temporarily perform actions related to RRC_IDLE / INACTVE)

[0216] 3> Perform measurements based on the LP-WUS measurement standard.

[0217] Part 1a SI

[0218] A UE with LP-WUS capability shall:

[0219] 1> If the UE enters a cell broadcasting SIBx containing LP-WUS related configuration and LP-WUS measurement criteria:

[0220] 2> Perform measurements based on the LP-WUS measurement standard.

[0221] Part 2 IDLE / INACTIVE Process

[0222] If the UE supports LP-WUS capability and the LP-WUS measurement criteria is provided by RRCRelease / SI, the UE shall evaluate the LP-WUS measurement criteria.

[0223] 1> If the LP-WUS measurement criteria are met (can be mobility and / or not at the cell edge):

[0224] 2> Stop executing actions related to RRC_IDLE / INACTIVE;

[0225] 2> Monitor the LP-WUS signal based on this configuration.

[0226] So far, a solution for notifying a terminal device of a network to apply LP mode has been described. In this way, notification of LP mode switching can be supported.

[0227] Example implementation of a request for LP mode

[0228] In some embodiments, the terminal device 110 determines whether to apply the LP mode and performs WUS monitoring during the LP mode. The determination may be performed in any suitable manner, and the present disclosure is not limited thereto.

[0229] If the terminal device 110 determines to apply the LP mode, the terminal device 110 sends a request to apply the LP mode. Figure 4 Some example embodiments are described. Figure 4 A schematic diagram illustrating a communication process 400 according to an embodiment of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1A Process 400 is described. Process 400 may include the following: Figure 1A The terminal device 110 and the network device 120 are shown. It should be understood that Figure 4 The steps and order of steps in the embodiment are for illustration only and are not intended to be limiting. For example, the order of the steps may be changed, some steps may be omitted, or any other suitable additional steps may be added.

[0230] Example 6

[0231] In this embodiment, the terminal device 110 may send a request through auxiliary information. In this way, the terminal device in the connected state may apply the LP mode by sending a request.

[0232] refer to Figure 4In some embodiments, the network device 120 may send 411 a configuration for transmission of auxiliary information. In some embodiments, the configuration for transmission of auxiliary information may include a timer (also referred to herein as an additional timer or a prohibition timer for convenience). For example, the IE OtherConfig may include the following configuration for transmission of auxiliary information (lp-wusAssistanceConfig).

[0233]

[0234] In this example, the IE OtherConfig may indicate a prohibit timer (lp-wusProhibitTimer).

[0235] When the terminal device 110 determines to apply the LP mode, the terminal device 110 may send 412 the assistance information based on the configuration for the transmission of the assistance information. In some embodiments, the terminal device 110 may send the assistance information via a UE Assistance Information (UAI) message. It should be understood that any other suitable message is also feasible.

[0236] In some embodiments, the assistance information may include a preference for applying the LP mode. In some embodiments, the assistance information may include a preference for a timer for the LP mode. It should be understood that the assistance information may include any combination of the above information and any other suitable information.

[0237] In some embodiments where the terminal device 110 is capable of providing auxiliary information for LP mode in a connected state, the terminal device 110 may initiate a UAI process if the terminal device 110 provides a preference for applying the LP mode or an LP mode timer or when the above information changes.

[0238] For example, an example UAI message may be configured as follows.

[0239]

[0240] In this example, the UAI message may include IE LP-WUSAssistance, and the IE LP-WUSAssistance may include a preference for applying LP mode (applyLP-WUSMode) and a preference for a timer for LP mode (preferredLP-WUSTimer). It should be understood that this is merely an example and is not intended to be limiting.

[0241] In some embodiments where the configuration for the transmission of auxiliary information includes an additional timer (i.e., an inhibit timer), if no auxiliary information has been sent since the configuration was received, or if the auxiliary information is different from the previous auxiliary information indicated in the previous transmission of the auxiliary information and the additional timer is not running, the terminal device 110 may start the additional timer and initiate the transmission of the auxiliary information. In some embodiments, if the additional timer is running, the terminal device 110 may not send the additional auxiliary information. In this way, frequent transmission of auxiliary information is avoided.

[0242] To illustrate, an example process may be described as follows.

[0243] Part 1 UAI Initiation

[0244] 1> If configured to provide LP-WUS assistance information:

[0245] 2> If the UE does not send a UEAssistanceInformation message with LP-WUSAssistance because it is configured to provide applyLP-WUSMode or preferredLP-WUSTimer, or

[0246] 2> If the current LP-WUSAssistance information is different from the information indicated in the last transmission of the UEAssistanceInformation message including LP-WUSAssistance and LP-WUSProhibitTimer, then do not run:

[0247] 3>Start LP-WUSProhibitTimer with the timer value set to lp-wusProhibitTimer;

[0248] 3> Initiate the transmission of UEAssistanceInformation message according to LP-WUS assistance.

[0249] Part 2 UAI Transmission

[0250] 1> If the transmission of the UEAssistanceInformation message is initiated to provide LP-WUS assistance information:

[0251] 2> Include applyLP-WUSMode in LP-WUSAssistanceIE (if present);

[0252] 2> Include preferredLP-WUSTimer in LP-WUSAssistanceIE (if it exists);

[0253] 1> Submit UEAssistanceInformation message to the lower layer for transmission.

[0254] Example 7

[0255] In this embodiment, the terminal device 110 may send a request through a random access (RA) procedure for the LP mode. In this way, an opportunity to request application of the LP mode may be provided to a terminal device in an idle or inactive state.

[0256] Continue to refer Figure 4 In some embodiments, the terminal device 110 may obtain 413 from the SI a configuration of a requested contention-free random access (CFRA) resource. In other words, a type of CFRA resource may be introduced in the SIB for a terminal device in an idle or inactive state to request application of the LP mode by performing CFRA.

[0257] In some embodiments, the configuration may include a preamble index for the RA procedure (denoted as ra-PreambleStartIndex). For example, a dedicated preamble index may be selected to perform CFRA preamble transmission for the request.

[0258] To illustrate, an example configuration of CFRA resources may be configured as follows.

[0259]

[0260] In some embodiments, the configuration of the CFRA resources may further include timing information of the RA process. In some embodiments, the timing information of the RA process may include at least one of the following: a mapping between SSBs and ROs (e.g., ssb-perRACH-Occasion), the number of association periods between SSBs and PRACH resources (e.g., lp-wusRequestPeriod), an index of which association period should be used (e.g., ra-AssociationPeriodIndex), and which RO should be used when one SSB index corresponds to multiple ROs (e.g., ra-ssb-OcasionMaskIndex). It should be understood that any other suitable information may also be feasible.

[0261] The terminal device 110 may select 414 an RA preamble corresponding to the selected SSB from a set of RA preambles determined based on the preamble index. In some embodiments, if N SSB indices of the i-th SSB (i=0, ..., N-1) are associated with an RA opportunity (RO), where N>=1, then a preamble with a preamble index=ra-PreambleStartIndex+i is used for the request; for N<1, a preamble with a preamble index=ra-PreambleStartIndex is used for the request.

[0262] The terminal device 110 may then perform 415 preamble transmission based on the RA preamble and the timing information. In some embodiments, if a random access response (RAR) is received and the RAR includes a MAC sub-protocol data unit (subPDU) having a RA preamble identifier corresponding to the RA preamble, the terminal device 110 may determine that reception of the RAR is successful.

[0263] If the RAR includes a MAC subPDU with only a random access preamble identifier (RAPID), the terminal device 110 may perform 416 operations associated with the LP mode. In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132 of the terminal device 110. In some embodiments, the terminal device 110 may turn on the WUS receiver 131 of the terminal device 110. In some embodiments, the terminal device 110 may indicate from a lower layer of the terminal device 110 to an upper layer that an acknowledgment of the request is received. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that any other suitable operations associated with the LP mode are also feasible.

[0264] To illustrate, an example CFRA process may be described as follows.

[0265] The MAC entity shall:

[0266] 1> If a random access procedure is initiated for a LP-WUS request; and

[0267] 1> If the random access resources for the LP-WUS request have been explicitly provided by the network (i.e. LP-WUSRequestConfig):

[0268] 2> If at least one of the SSBs with SS-RSRP higher than rsrp-ThresholdSSB is available:

[0269] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0270] 2> Otherwise:

[0271] 3>Select Any SSB.

[0272] 2> Select the random access preamble corresponding to the selected SSB from the random access preambles determined according to ra-PreambleStartIndex;

[0273] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0274] 1>Execute the random access preamble code transmission process.

[0275] Once the Random Access Preamble has been sent and regardless of the possible occurrence of Measurement Gaps, the MAC entity shall:

[0276] 1> If a downlink allocation has been received on the PDCCH for RA-RNTI and the received TB is successfully decoded:

[0277] 2> If the Random Access Response contains a MAC subPDU with a Random Access Preamble identifier corresponding to the sent PREAMBLE_INDEX:

[0278] 3> The random access response is considered to be received successfully.

[0279] 2> If the random access response reception is considered successful:

[0280] 3> If the Random Access Response includes a MAC subPDU with only RAPID:

[0281] 4> The random access process is considered to be successfully completed;

[0282] 4> Indicate to the upper layer (i.e., UERRC) the receipt of the confirmation of the LP WUS request;

[0283] (RRC part)

[0284] 4> (Optional) Stop performing actions related to RRC_IDLE / INACTVE.

[0285] 4>Monitor LP-WUS signal.

[0286] Example 8

[0287] In this embodiment, in the uplink common control channel 1 (UL-CCCH1), the type of RRC message can be introduced for the terminal device in the idle or inactive state to request the application of the LP mode by performing contention-based random access (CBRA) in message 3 (Msg3). In this way, the terminal device in the idle or inactive state can also be provided with the opportunity to request the application of the LP mode.

[0288] Continue to refer Figure 4 In some embodiments, if a contention-based preamble is selected to perform the RA procedure, the terminal device 110 may send 417 message 3 by causing a message dedicated to the LP mode to be included in a service data unit (SDU) for the UL-CCCH (e.g., UL-CCCH1). In some embodiments, the message dedicated to the LP mode may include at least an identification of the terminal device 110.

[0289] In some embodiments, the identifier may be an RNTI, such as an I-RNTI or any other suitable form of an RNTI. In some embodiments, the identifier may be a TMSI, such as a 5G-S-TMSI or any other suitable form of a TMSI. It should be understood that the identifier may be in any other suitable form.

[0290] To illustrate, an example UL-CCCH1 may be configured as follows.

[0291]

[0292] In this example, UL-CCCH1 may be configured with a message (rrcLP-WUSRequest) dedicated to LP mode. It should be understood that this is merely an example and is not intended to be limiting.

[0293] In some embodiments, the terminal device 110 may determine that contention resolution is successful if a contention resolution indicator in a medium access control element (MAC CE) of the MAC PDU matches the SDU. In some embodiments, the MAC PDU may include a configuration for LP mode.

[0294] After determining that the contention resolution is successful, the terminal device 110 may perform 418 operations associated with the LP mode. In some embodiments in which the terminal device 110 enters the LP mode, the terminal device 110 may turn off the main radio 132 of the terminal device 110. In some embodiments, the terminal device 110 may turn on the WUS receiver 131 of the terminal device 110. In some embodiments, the terminal device 110 may indicate the receipt of an acknowledgment of the request from the lower layer of the terminal device 110 to the upper layer. In some embodiments, the terminal device 110 may stop performing operations in an idle or inactive state. In some embodiments, the terminal device 110 may perform WUS monitoring. It should be understood that any other suitable operations associated with the LP mode are also feasible.

[0295] To illustrate, an example CBRA process may be described as including at least the following.

[0296] Step 1. (If there is no LP-WUSRequestConfig) UE selects a contention-based preamble to perform the random access preamble transmission procedure.

[0297] Step 2. The UE receives a downlink assignment (Msg2 / RAR MAC PDU) on the PDCCH for RA-RNTI.

[0298] Step 3. (If not RAPID-only) Process timing advance command, power ramping, UL Grant, and TC-RNTI.

[0299] After performing the above process, the UE sends Msg3 with the rrcLP-WUSRequest message including the UL-CCCH1 SDU.

[0300] Upon sending Msg3, the MAC entity shall:

[0301] 1> If notification of receipt of a PDCCH transmission for SpCell is received from a lower layer:

[0302] 2> If the MAC PDU is successfully decoded:

[0303] 3>Stop ra-ContentionResolutionTimer;

[0304] 3> If the MAC PDU contains the UE contention resolution identifier MAC CE; and 3> If the UE contention resolution identifier in the MAC CE matches the CCCH SDU sent in Msg3:

[0305] 4> The contention resolution is considered successful and the disassembly and demultiplexing of MAC PDU is completed;

[0306] 4> If a random access procedure is initiated for a LP-WUS request:

[0307] 5> Indicate to the upper layer (i.e. UE RRC) the receipt of the confirmation of the LP-WUS request;

[0308] (RRC)

[0309] 5> (Optional) Stop performing actions related to RRC_IDLE / INACTVE.

[0310] 5>Monitor LP-WUS signal.

[0311] So far, a solution for a terminal device to request LP mode from the network has been described. In this way, notification of LP mode switching can also be supported.

[0312] Example implementation of LP mode exit

[0313] When the terminal device is monitoring the LP WUS signal, if the terminal device receives the LP WUS signal, the terminal device will exit the LP mode. It is necessary to specify the process after exiting the LP mode. Some example embodiments will be described in conjunction with embodiments 9 to 10.

[0314] Example 9

[0315] In this embodiment, after exiting the LP mode, the terminal device 110 may perform operations in an idle or inactive state. In this way, a process after exiting the LP mode may be specified.

[0316] In some embodiments, the terminal device 110 may stop WUS monitoring. In some embodiments, the terminal device 110 may perform a cell selection process. In some embodiments, if the terminal device 110 is camped on a cell, the terminal device 110 may monitor at least one of a paging channel, a short message or an SI from the cell.

[0317] In some embodiments, if a short message is received, the terminal device 110 may perform an operation associated with the short message, stop operating in an idle or inactive state, and perform WUS monitoring. In some embodiments, if the identifier included in the paging message does not match the identifier of the terminal device 110, the terminal device 110 may stop operating in an idle or inactive state, and perform WUS monitoring.

[0318] In some embodiments, this embodiment may respond to those terminal devices applying LP mode from an idle or inactive state. It should be understood that this embodiment may also be applied to any other situation.

[0319] For example, an example process may be described as follows.

[0320] After receiving the LP-WUS signal, the UE shall:

[0321] 1>Stop LP-WUS monitoring;

[0322] 1> Perform cell selection as specified in TS38.304 (once a suitable cell is found, it should be selected).

[0323] When camping on a cell normally, the UE shall perform the following tasks:

[0324] -Monitor the cell's paging channel based on the information broadcast in SIB1;

[0325] - monitor short messages sent on DCI with P-RNTI;

[0326] -Monitor relevant system information;

[0327] - Perform necessary measurements for the cell reselection evaluation process;

[0328] -The cell reselection evaluation process is performed at the following times / triggers:

[0329] After receiving the paging, the UE shall:

[0330] 1> If the UE receives a short message, the UE shall:

[0331] 2> Process actions related to short message information (such as SI / PTW...);

[0332] 2> Stop actions related to RRC_IDLE / INACTIVE;

[0333] 2>Re-monitor the LP-WUS signal.

[0334] 1> If the UE receives a paging message, the UE shall:

[0335] 2> If the UE identity included in the paging message does not match the UE identity or I-RNTI allocated by upper layers:

[0336] 3> Stop actions related to RRC_IDLE / INACTIVE;

[0337] 3>Re-monitor the LP-WUS signal.

[0338] 2> Otherwise:

[0339] 3>Perform actions related to the paging process.

[0340] Example 10

[0341] In this embodiment, after exiting the LP mode, the terminal device 110 can perform operations in a connected state. In this way, the process after exiting the LP mode can also be specified.

[0342] In some embodiments, the terminal device 110 may stop WUS monitoring. In some embodiments, the terminal device 110 may perform a cell selection process. In some embodiments, if the terminal device 110 is camped on a cell, the terminal device 110 may monitor SI from the cell. In some embodiments, the terminal device 110 may initiate a RA process.

[0343] In some embodiments, the embodiment may respond to those terminal devices applying the LP mode from the connected state. It should be understood that the embodiment may also be applied to any other situations.

[0344] For example, the example process may be described as follows.

[0345] After receiving the LP-WUS signal, the UE shall:

[0346] 1>Stop LP-WUS monitoring;

[0347] 1> Perform cell selection as specified in TS38.304 (once a suitable cell is found, it should be selected).

[0348] When camping on a cell normally, the UE shall perform the following tasks:

[0349] -Monitor relevant system information (for acquiring RA resources and synchronization);

[0350] 1> Initiate a random access procedure immediately after acquiring RA resources and synchronization.

[0351] So far, the process after exiting LP mode has been described. In this way, the UE behavior after exiting LP mode can be specified.

[0352] It should be understood that the solutions in Examples 1 to 10 may be used alone or in any suitable combination.

[0353] Example implementation of method

[0354] Corresponding to the above process, the embodiment of the present disclosure provides a communication method implemented at a terminal device and a network device. Figures 5 to 8 Describe these methods.

[0355] Figure 5 An example method 500 of communication implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 500 may be implemented in a Figure 1AFor the purpose of discussion, reference will be made to Figure 1A Method 500 is described. It should be understood that method 500 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0356] At block 510 , the terminal device 110 determines whether an LP mode is applied, during which WUS monitoring is performed.

[0357] In some embodiments, if an RRC release message including first information of LP mode is received, the terminal device 110 may determine to apply LP mode. In some embodiments, the first information of LP mode may include at least one of the following: an indication of LP mode, a configuration for LP mode, or a timer for LP mode.

[0358] In some embodiments, if the RRC release message is received, the terminal device 110 may start a timer. If the timer expires, the terminal device 110 may determine to apply the LP mode.

[0359] In some embodiments, if the cell reselection condition is met while the timer is running and the terminal device 110 supports mobility in LP mode, the terminal device 110 may restart the timer. In some embodiments, if the terminal device 110 performs an SDT process and the timer is running, the terminal device 110 restarts the timer. In some embodiments, if the terminal device 110 receives an MBS and the timer is running, the terminal device 110 may restart the timer. In some embodiments, if the cell reselection condition is met while the timer is running and the terminal device 110 does not support mobility in LP mode, the terminal device 110 may stop the timer. In some embodiments, if the terminal device 110 enters a connected state and the timer is running, the terminal device 110 may stop the timer.

[0360] In some embodiments, the terminal device 110 may receive a paging message including second information of the LP mode, the second information indicating a set of identifiers of the terminal device. If the identifier in the set matches the identifier of the terminal device, the terminal device 110 may determine to apply the LP mode. In some embodiments, the terminal device 110 may also receive a DCI that schedules the reception of the paging message and includes only an indication of the LP mode.

[0361] In some embodiments, the terminal device 110 may receive a paging message including an identifier set of the terminal device and a paging cause set corresponding to the identifier set. If an identifier in the identifier set matches an identifier of the terminal device 110, the terminal device 110 may determine whether the paging cause corresponding to the identifier of the terminal device indicates an LP mode. If the paging cause indicates an LP mode, the terminal device 110 may determine to apply the LP mode.

[0362] In some embodiments, the terminal device 110 can obtain information of a channel dedicated to notification of the LP mode from system information; determine a set of timings for monitoring the channel, which is associated with a set of synchronization signal blocks; if a message from the channel is received based on the set of timings and the set of synchronization signal blocks and an identifier included in the message matches an identifier of the terminal device 110, the terminal device 110 can determine to apply the LP mode.

[0363] In some embodiments, the information of the channel includes at least one of: the length and offset of a channel repetition period; the starting time slot of a transmission window of the channel; or the duration of the transmission window.

[0364] In some embodiments, the terminal device 110 may determine a candidate opportunity set that does not overlap with an uplink symbol as the opportunity set based on the search space for the channel and the information of the channel; and determine a mapping between the opportunity set and the synchronization signal block set based on the index of the opportunity, the index of the SSB, the number of opportunities in the transmission window, and the number of SSBs actually sent. In some embodiments, the message may include at least one of the following: an identification list of the terminal device or a configuration for the LP mode.

[0365] In some embodiments, the terminal device 110 may receive a configuration for the LP mode, the configuration including a set of measurement criteria, and perform signal measurement based on the set of measurement criteria. If the set of measurement criteria is met, the terminal device 110 may determine to apply the LP mode.

[0366] In some embodiments, the terminal device 110 may receive an RRC release message including a configuration for the LP mode. In some embodiments, the terminal device 110 may receive system information including a configuration for the LP mode.

[0367] In some embodiments, the set of measurement criteria may include at least one of: a measurement criterion for a terminal device with low mobility, a measurement criterion for a terminal device with stationary state, or a measurement criterion for a terminal device that is not at a cell edge.

[0368] If the terminal device 110 determines to apply the LP mode, the method 500 proceeds to block 520. At block 520, based on the determination to apply the LP mode, the terminal device 110 performs operations associated with the LP mode.

[0369] In some embodiments, the terminal device 110 may perform operations associated with the LP mode by at least one of: turning off the main radio 132 of the terminal device 110; turning on the WUS receiver 131 of the terminal device 110; indicating the reason for applying the LP mode from the lower layer of the terminal device 110 to the upper layer; stopping performing operations in an idle or inactive state; applying a configuration for the LP mode; or performing WUS monitoring.

[0370] In some embodiments, if a WUS is received, the terminal device 110 may perform operations in an idle or inactive state. In some embodiments, the terminal device 110 may perform operations in an idle or inactive state by at least one of: stopping wake-up signal monitoring; performing a cell selection process; or if the terminal device is camped on a cell, monitoring at least one of a paging channel, a short message, or system information from the cell.

[0371] In some embodiments, if a short message is received, the terminal device 110 may perform an operation associated with the short message; stop operating in an idle or inactive state; and perform WUS monitoring. In some embodiments, if the identifier included in the paging message does not match the identifier of the terminal device 110, the terminal device 110 may stop operating in an idle or inactive state and perform WUS monitoring.

[0372] In some embodiments, if a WUS is received, the terminal device 110 may perform operations in a connected state. In some embodiments, the terminal device 110 may perform operations in a connected state by at least one of: stopping WUS monitoring; performing a cell selection process; if the terminal device 110 is camped in a cell, monitoring system information from the cell; or initiating a RA process.

[0373] Using method 500, the network can notify the terminal device to apply the LP mode.

[0374] Figure 6 Another example method 600 of communication implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 600 may be implemented in a Figure 1A For the purpose of discussion, reference will be made to Figure 1A Method 600 is described. It should be understood that method 600 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0375] At block 610 , the terminal device 110 determines whether to apply an LP mode during which WUS monitoring is performed. If the terminal device 110 determines to apply the LP mode, the method 600 proceeds to block 620 .

[0376] At block 620, based on the determination to apply the LP mode, the terminal device 110 sends a request to apply the LP mode. In some embodiments, the terminal device 110 may send the request via auxiliary information. In some embodiments, the terminal device 110 may send the request via a RA procedure for the LP mode.

[0377] In some embodiments, the terminal device 110 may receive a configuration for transmission of auxiliary information and send the auxiliary information, which includes at least one of: a preference for applying the LP mode, or a preference for a timer for the LP mode.

[0378] In some embodiments where the configuration for the transmission of the auxiliary information includes an additional timer, the terminal device 110 may start the additional timer and initiate the transmission of the auxiliary information if no auxiliary information has been sent since the configuration was received, or if the auxiliary information is different from the previous auxiliary information indicated in the previous transmission of the auxiliary information and the additional timer is not running. In some embodiments, the terminal device 110 may not send the additional auxiliary information if the additional timer is running.

[0379] In some embodiments, the terminal device 110 may obtain a configuration of the requested CFRA resource from the SI, the configuration including at least one of a preamble index for the RA process or timing information for the RA process. The terminal device 110 may select an RA preamble corresponding to the selected SSB from a set of RA preambles determined based on the preamble index. In some embodiments, the terminal device 110 may perform preamble transmission based on the RA preamble and the timing information.

[0380] In some embodiments, if the RAR is received and the RAR includes a MAC sub-PDU with an RA preamble identifier corresponding to the RA preamble, the terminal device 110 may determine that the reception of the RA response is successful. If the RAR includes a MAC sub-PDU with only the RA preamble identifier, the terminal device 110 may perform operations associated with the LP mode.

[0381] In some embodiments, if a contention-based preamble is selected to perform the RA procedure, the terminal device 110 may transmit the message 3 by causing a message dedicated to the LP mode to be included in the SDU of the UL-CCCH.

[0382] In some embodiments, if the contention resolution indicator in the MAC CE of the MAC PDU matches the SDU, the terminal device 110 may determine that contention resolution is successful and perform operations associated with the LP mode. In some embodiments, the MAC PDU includes a configuration for the LP mode.

[0383] In some embodiments, the terminal device 110 can perform operations associated with the LP mode, including at least one of the following operations: turning off the main radio 132 of the terminal device 110; turning on the WUS receiver 131 of the terminal device 110; indicating receipt of an acknowledgment of the request from the lower layer of the terminal device 110 to the upper layer; ceasing to perform operations in an idle or inactive state; or performing WUS monitoring.

[0384] In some embodiments, if a WUS is received, the terminal device 110 may perform operations in an idle or inactive state. In some embodiments, the terminal device 110 may perform operations in an idle or inactive state by at least one of: stopping wake-up signal monitoring; performing a cell selection process; or if the terminal device is camped on a cell, monitoring at least one of a paging channel, a short message, or system information from the cell.

[0385] In some embodiments, if a short message is received, the terminal device 110 may perform an operation associated with the short message; stop operating in an idle or inactive state; and perform WUS monitoring. In some embodiments, if the identifier included in the paging message does not match the identifier of the terminal device 110, the terminal device 110 may stop operating in an idle or inactive state and perform WUS monitoring.

[0386] In some embodiments, if a WUS is received, the terminal device 110 may perform operations in a connected state. In some embodiments, the terminal device 110 may perform operations in a connected state by at least one of: stopping WUS monitoring; performing a cell selection process; if the terminal device 110 is camped in a cell, monitoring system information from the cell; or initiating a RA process.

[0387] Using method 600, the terminal device can request the network to apply the LP mode.

[0388] Figure 7 An example method 700 of communication implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 700 may be implemented in a Figure 1A For the purpose of discussion, reference will be made to Figure 1AMethod 700 is described. It should be understood that method 700 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0389] At block 710 , the network device 120 sends information to apply an LP mode during which WUS monitoring is performed.

[0390] In some embodiments, the network device 120 may send the information for applying the LP mode by sending an RRC release message including the first information of the LP mode.

[0391] In some embodiments, the first information of the LP mode includes at least one of: an indication of the LP mode, a configuration for the LP mode, or a timer for the LP mode.

[0392] In some embodiments, the network device 120 may send information for applying the LP mode by sending a paging message including second information of the low power mode, the second information indicating the identification set of the terminal device. In some embodiments, the network device 120 may also send a DCI that schedules the reception of the paging message and only includes an indication of the LP mode.

[0393] In some embodiments, the network device 120 may send information of applying the LP mode by sending a paging message, the paging message including: an identification set of the terminal device, and a paging reason set corresponding to the identification set, at least one paging reason in the paging reason set indicating the LP mode.

[0394] In some embodiments, the network device 120 may send information for applying the LP mode by sending information of a channel dedicated to notification of the LP mode in the SI; determining a timing set associated with the channel, the timing set being associated with the SSB set; and sending a message based on the timing set and the SSB set.

[0395] In some embodiments, the information of the channel may include at least one of: the length and offset of a channel repetition period; the starting time slot of a transmission window of the channel; or the duration of the transmission window.

[0396] In some embodiments, the network device 120 can determine the timing set in the following manner: based on the search space of the channel and the information of the channel, determine a candidate timing set that does not overlap with the uplink symbol as the timing set; and determine the mapping between the timing set and the SSB set based on the index of the timing, the index of the SSB, the number of timings in the transmission window, and the number of SSBs actually sent.

[0397] In some embodiments, the message may include at least one of the following: an identification list of terminal devices or a configuration for LP mode.

[0398] In some embodiments, the network device 120 may send the information of applying the LP mode in the following manner: send a configuration for the LP mode, where the configuration includes a set of measurement criteria.

[0399] In some embodiments, the network device 120 may send the configuration for the LP mode in the following manners: sending an RRC release message including the configuration for the LP mode; or sending an SI including the configuration for the LP mode.

[0400] In some embodiments, the set of measurement criteria may include at least one of: a measurement criterion for a terminal device with low mobility, a measurement criterion for a terminal device with stationary state, or a measurement criterion for a terminal device that is not at a cell edge.

[0401] Using method 700, the network can notify the terminal device to apply the LP mode.

[0402] Figure 8 Another example method 800 of communication implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 800 may be implemented in a Figure 1A For the purpose of discussion, reference will be made to Figure 1A Method 800 is described. It should be understood that method 800 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0403] At block 810 , the network device 120 receives a request to apply an LP mode during which a primary radio of the terminal device is turned off and a wake-up signal receiver of the terminal device is turned on.

[0404] In some embodiments, the network device 120 may receive the request by: receiving a request for assistance information; or receiving a request for a low power mode through a RA procedure.

[0405] In some embodiments, the network device 120 may send a configuration for transmission of auxiliary information; and receive auxiliary information, which includes at least one of the following: a preference for applying LP mode, or a preference for a timer for LP mode. In some embodiments, the configuration for transmission of auxiliary information may include an additional timer.

[0406] In some embodiments, the network device 120 may send a configuration of CFRA resources dedicated to the request in the SI, the configuration including at least one of a preamble index for the RA process or timing information of the RA process.

[0407] In some embodiments, the network device 120 may also receive a message 3 including a message dedicated to the LP mode in the SDU of the UL-CCCH.

[0408] Using method 800, the terminal device can request the network to apply the LP mode.

[0409] Example implementations of devices and apparatus

[0410] Fig. 9 is a simplified block diagram of a device 900 suitable for implementing an embodiment of the present disclosure. The device 900 can be considered as Figure 1A The device 900 is a further example implementation of the terminal device 110 or the network device 120. Therefore, the device 900 may be implemented at the terminal device 110 or the network device 120 or as at least a part of the terminal device 110 or the network device 120.

[0411] As shown, the device 900 includes a processor 910, a memory 920 coupled to the processor 910, a suitable transmitter (TX) and receiver (RX) 940 coupled to the processor 910, and a communication interface coupled to the TX / RX940. The memory 910 stores at least a portion of the program 930. The TX / RX940 is used for bidirectional communication. Although the TX / RX940 has at least one antenna to facilitate communication, in fact, the access node mentioned in this application may have several antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNB / gNB, an S1 / NG interface for communication between a mobility management entity (MME) / access and mobility management function (AMF) / SGW / UPF and an eNB / gNB, a Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0412] Assume that the program 930 includes program instructions that, when executed by the associated processor 910, enable the device 900 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1A to 8 The embodiments herein may be implemented by computer software executable by a processor 910 of the device 900, or by hardware, or by a combination of software and hardware. The processor 910 may be configured to implement various embodiments of the present disclosure. In addition, the combination of the processor 910 and the memory 920 may form a processing component 950 suitable for implementing various embodiments of the present disclosure.

[0413] The memory 920 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory 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 920 is shown in the device 900, there may be several physically different memory modules in the device 900. As non-limiting examples, the processor 910 may be of any type suitable for the local technology network and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 900 may have multiple processors, such as a dedicated integrated circuit chip that is time-slave to a clock that synchronizes a main processor.

[0414] In some embodiments, the terminal device includes a circuit configured to: determine a configuration for wake-up signal monitoring at the terminal device; determine a time-frequency resource set that is independent of the paging occasion based at least on the configuration; and perform wake-up signal monitoring based at least on the time-frequency resource set.

[0415] In some embodiments, a network device includes a circuit configured to: send a configuration set for wake-up signal monitoring for at least one set of terminal devices at the network device, the configuration in the configuration set indicating a time-frequency resource set that is independent of paging occasions; and perform wake-up signal transmission based at least on the time-frequency resource set.

[0416] The term "circuit" used in this article may refer to a combination of hardware circuits and / or hardware circuits and software. For example, a circuit may be a combination of analog and / or digital hardware circuits and software / firmware. As another example, a circuit may be any part of a hardware processor with software, including a digital signal processor, software, and memory that work together to cause a device such as a terminal device or a network device to perform various functions. In another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware to operate, but when software is not required to operate, the software may not exist. As used herein, the term "circuit" also encompasses the implementation of only a hardware circuit or processor or a part of a hardware circuit or processor and its (or their) accompanying software and / or firmware.

[0417] In summary, the embodiments of the present disclosure may provide the following solutions.

[0418] In one solution, a communication method includes: determining at a terminal device whether a low power mode is applied, performing wake-up signal monitoring during the low power mode; and performing operations associated with the low power mode based on the determination to apply the low power mode.

[0419] In some embodiments, determining whether to apply the low power mode comprises: determining to apply the low power mode based on a determination that a radio resource control release message including first information of the low power mode is received.

[0420] In some embodiments, the first information of the low power mode includes at least one of: an indication of the low power mode, a configuration for the low power mode, or a timer for the low power mode.

[0421] In some embodiments, determining whether to apply the low power mode comprises: starting a timer based on a determination that a radio resource control release message is received; and determining to apply the low power mode based on a determination that the timer expires.

[0422] In some embodiments, the above method also includes: restarting the timer based on the determination that the cell reselection condition is met when the timer is running and the terminal device supports mobility in low power mode; stopping the timer based on the determination that the cell reselection condition is met when the timer is running and the terminal device does not support mobility in low power mode; stopping the timer based on the determination that the terminal device enters a connected state and the timer is running; restarting the timer based on the determination that the terminal device performs a small data transmission process and the timer is running; or restarting the timer based on the determination that the terminal device receives multicast and broadcast services and the timer is running.

[0423] In some embodiments, determining whether to apply the low power mode includes: receiving a paging message including second information of the low power mode, the second information indicating a set of terminal device identifiers; and determining to apply the low power mode based on a determination that an identifier in the set matches an identifier of the terminal device.

[0424] In some embodiments, the method further comprises: receiving downlink control information scheduling reception of a paging message and including only an indication of a low power mode.

[0425] In some embodiments, determining whether to apply a low power mode includes: receiving a paging message, the paging message including: an identifier set of a terminal device, and a paging reason set corresponding to the identifier set; determining, based on a determination that an identifier in the identifier set matches an identifier of the terminal device, whether the paging reason corresponding to the identifier of the terminal device indicates a low power mode; and determining to apply the low power mode based on a determination that the paging reason indicates a low power mode.

[0426] In some embodiments, determining whether to apply the low power mode includes: obtaining information of a channel dedicated to notification of the low power mode from system information; determining a set of timings for monitoring the channel, the timing set being associated with a synchronization signal block set; and determining to apply the low power mode based on a determination that a message from the channel is received based on the timing set and the synchronization signal block set and an identifier included in the message matches an identifier of the terminal device.

[0427] In some embodiments, the information of the channel includes at least one of: the length and offset of a channel repetition period; the starting time slot of a transmission window of the channel; or the duration of the transmission window.

[0428] In some embodiments, determining the opportunity set includes: determining a candidate opportunity set that does not overlap with uplink symbols as the opportunity set based on the search space of the channel and the information of the channel; and determining the mapping between the opportunity set and the synchronization signal block set based on the opportunity index, the index of the synchronization signal block, the number of opportunities in the transmission window, and the number of synchronization signal blocks actually sent.

[0429] In some embodiments, the message comprises at least one of: an identification list of terminal devices or a configuration for a low power mode.

[0430] In some embodiments, determining whether to apply low power mode comprises: receiving a configuration for low power mode, the configuration comprising a set of measurement criteria; performing signal measurements based on the set of measurement criteria; and determining to apply low power mode based on a determination that the set of measurement criteria is met.

[0431] In some embodiments, receiving the configuration for the low power mode comprises: receiving a radio resource control release message comprising the configuration for the low power mode; or receiving system information comprising the configuration for the low power mode.

[0432] In some embodiments, the set of measurement criteria includes at least one of: a measurement criterion for a terminal device with low mobility, a measurement criterion for a terminal device with fixation, or a measurement criterion for a terminal device that is not at a cell edge.

[0433] In some embodiments, performing operations associated with the low power mode includes at least one of: turning off a main radio of the terminal device; turning on a wake-up signal receiver of the terminal device; indicating a reason for applying the low power mode from a lower layer of the terminal device to an upper layer; ceasing to perform operations in an idle or inactive state; applying a configuration for the low power mode; or performing wake-up signal monitoring.

[0434] In another solution, a method of communication includes: determining at a terminal device whether to apply a low power mode, performing wake-up signal monitoring during the low power mode; and sending a request to apply the low power mode based on the determination to apply the low power mode.

[0435] In some embodiments, sending the request comprises: sending the request via assistance information; or sending the request via a random access procedure for low power mode.

[0436] In some embodiments, sending the request via assistance information comprises: receiving a configuration for transmission of assistance information; and sending assistance information comprising at least one of: a preference for applying a low power mode, or a preference for a timer for a low power mode.

[0437] In some embodiments where the configuration for transmission of auxiliary information includes an additional timer, the above method also includes at least one of: starting the additional timer and initiating transmission of the auxiliary information based on a determination that no auxiliary information has been sent since receiving the configuration, or based on a determination that the auxiliary information is different from previous auxiliary information indicated in a previous transmission of the auxiliary information and the additional timer is not running; or not sending the additional auxiliary information based on a determination that the additional timer is running.

[0438] In some embodiments, sending a request through a random access process includes: obtaining a configuration of a contention-free random access resource for the request from system information, the configuration including: at least one of a preamble index for the random access process or timing information for the random access process; selecting a random access preamble corresponding to a selected synchronization signal block from a set of random access preambles determined based on the preamble index; and performing preamble transmission based on the random access preamble and the timing information.

[0439] In some embodiments, the method further includes: determining that reception of the random access response is successful based on a determination that a random access response is received and the random access response includes a medium access control sub-protocol data unit having a random access preamble identifier corresponding to the random access preamble; and performing operations associated with the low power mode based on a determination that the random access response includes a medium access control sub-protocol data unit having only the random access preamble identifier.

[0440] In some embodiments, sending the request by a random access procedure comprises sending Message 3 by having a message dedicated to the low power mode included in a service data unit for an uplink common control channel in accordance with a determination to select a contention based preamble to perform the random access procedure.

[0441] In some embodiments, the method further comprises: determining that contention resolution is successful based on a determination that a contention resolution identifier in a media access control element of a media access control protocol data unit matches a service data unit; and performing operations associated with a low power mode.

[0442] In some embodiments, the medium access control protocol data unit includes a configuration for a low power mode.

[0443] In some embodiments, performing operations associated with the low power mode includes at least one of: turning off a main radio of the terminal device; turning on a wake-up signal receiver of the terminal device; indicating receipt of an acknowledgment of a request from a lower layer of the terminal device to an upper layer; ceasing to perform operations in an idle or inactive state; or performing wake-up signal monitoring.

[0444] In some embodiments, the above method further includes: performing an operation in an idle or inactive state based on a determination that a wake-up signal is received; or performing an operation in a connected state based on a determination that a wake-up signal is received.

[0445] In some embodiments, performing operations in an idle or inactive state includes at least one of: stopping wake-up signal monitoring; performing a cell selection process; or, based on a determination that the terminal device is resident on a cell, monitoring at least one of a paging channel, a short message, or system information from the cell.

[0446] In some embodiments, the method further comprises: performing an operation associated with the short message based on a determination that a short message has been received; stopping operation in an idle or inactive state; and performing wake-up signal monitoring. In some embodiments, the method further comprises: stopping operation in an idle or inactive state based on a determination that the paging message does not contain an identifier that matches an identifier of the terminal device; and performing wake-up signal monitoring.

[0447] In some embodiments, performing operations in a connected state includes at least one of: stopping wake-up signal monitoring; performing a cell selection process; monitoring system information from a cell based on a determination that the terminal device is camped on a cell; or initiating a random access process.

[0448] In another solution, a communication method includes sending information to apply a low power mode at a network device, and performing wake-up signal monitoring during the low power mode.

[0449] In some embodiments, sending information to apply the low power mode includes: sending a radio resource control release message including first information of the low power mode.

[0450] In some embodiments, the first information of the low power mode includes at least one of: an indication of the low power mode, a configuration for the low power mode, or a timer for the low power mode.

[0451] In some embodiments, sending information for applying the low power mode includes sending a paging message including second information of the low power mode, the second information indicating a set of terminal device identifiers.

[0452] In some embodiments, the method further comprises: sending downlink control information scheduling reception of the paging message and including only an indication of the low power mode.

[0453] In some embodiments, sending information for applying a low power mode includes sending a paging message, the paging message including an identifier set of the terminal device and a paging cause set corresponding to the identifier set, at least one paging cause in the paging cause set indicating a low power mode.

[0454] In some embodiments, sending information for applying a low power mode includes: sending information of a channel dedicated to notification of the low power mode in system information; determining a timing set associated with the channel, the timing set being associated with a synchronization signal block set; and sending a message based on the timing set and the synchronization signal block set.

[0455] In some embodiments, the information of the channel includes at least one of: the length and offset of a channel repetition period; the starting time slot of a transmission window of the channel; or the duration of the transmission window.

[0456] In some embodiments, determining the opportunity set includes: determining a candidate opportunity set that does not overlap with uplink symbols as the opportunity set based on the search space of the channel and the information of the channel; and determining the mapping between the opportunity set and the synchronization signal block set based on the opportunity index, the index of the synchronization signal block, the number of opportunities in the transmission window, and the number of synchronization signal blocks actually sent.

[0457] In some embodiments, the message comprises at least one of: an identification list of terminal devices or a configuration for a low power mode.

[0458] In some embodiments, sending information to apply the low power mode includes sending a configuration for the low power mode, the configuration including a set of measurement criteria.

[0459] In some embodiments, sending the configuration for the low power mode comprises: sending a radio resource control release message including the configuration for the low power mode; or sending system information including the configuration for the low power mode.

[0460] In some embodiments, the set of measurement criteria includes at least one of: a measurement criterion for a terminal device with low mobility, a measurement criterion for a terminal device with fixation, or a measurement criterion for a terminal device that is not at a cell edge.

[0461] In another solution, a communication method includes receiving, at a network device, a request to apply a low power mode during which a primary radio of a terminal device is turned off and a wake-up signal receiver of the terminal device is turned on.

[0462] In some embodiments, receiving the request comprises: receiving the request via assistance information; or receiving the request via a random access procedure for low power mode.

[0463] In some embodiments, receiving a request via assistance information comprises sending a configuration for transmission of assistance information and receiving assistance information comprising at least one of a preference for applying a low power mode or a preference for a timer for a low power mode.

[0464] In some embodiments, the configuration for the transmission of assistance information includes an additional timer.

[0465] In some embodiments, the above method further comprises: sending a configuration of a contention-free random access resource dedicated to the request in system information, the configuration comprising: at least one of a preamble code index for a random access process or timing information of a random access process.

[0466] In some embodiments, the above method further comprises: receiving a message 3 including a message dedicated to the low power mode in a service data unit of an uplink common control channel.

[0467] In another solution, a communication device includes: a processor configured to cause the device to perform any of the above methods.

[0468] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. When various aspects of the embodiments of the present disclosure are illustrated or described as block diagrams, flow charts, or using some other graphical representation, it will be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof as non-limiting examples.

[0469] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target real or virtual processor to perform the above-referenced Figures 1A to 8 In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0470] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code causes the functions / operations specified in the flow chart and / or block diagram to be implemented when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine, partially on a remote machine, or completely on a remote machine or server.

[0471] The above program code may be contained on a machine-readable medium, which may be any tangible medium that may contain or store a program used by or in conjunction with an instruction execution system, device, 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, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0472] In addition, although operations are described in a specific order, this should not be understood as requiring the specific order shown or to perform these operations in a sequential order, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0473] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

Claims

1. A communication method, comprising: determining at a terminal device whether a low power mode is applied, during which wake-up signal monitoring is performed; as well as Based on a determination that the low power mode applies, operations associated with the low power mode are performed.

2. The method of claim 1 , wherein determining whether to apply the low power mode comprises: According to a determination that a radio resource control release message including first information of the low power mode is received, it is determined that the low power mode is applied.

3. The method according to claim 2, wherein the first information of the low power mode comprises at least one of the following: The low power mode indication, configuration for the low power mode, or A timer for the low power mode.

4. The method of claim 2, wherein determining whether to apply the low power mode comprises: starting a timer based on a determination of receiving the radio resource control release message; as well as Based on the determination of expiration of the timer, it is determined to apply the low power mode.

5. The method according to claim 4, further comprising: Restarting the timer based on a determination that a cell reselection condition is satisfied while the timer is running and the terminal device supports mobility in the low power mode; stopping the timer based on a determination that a cell reselection condition is satisfied while the timer is running and the terminal device does not support mobility in the low power mode; According to the determination that the terminal device enters a connected state and the timer is running, stopping the timer; Restarting the timer according to a determination that the terminal device is performing a small data transmission process and the timer is running; or Based on a determination that the terminal device is receiving multicast and broadcast services and the timer is running, the timer is restarted.

6. The method of claim 1 , wherein determining whether to apply the low power mode comprises: receiving a paging message including second information of the low power mode, wherein the second information indicates a set of terminal device identifiers; as well as Based on a determination that an identifier in the set matches an identifier of the terminal device, it is determined to apply the low power mode.

7. The method according to claim 6, further comprising: Downlink control information scheduling reception of the paging message and including only an indication of the low power mode is received.

8. The method of claim 1 , wherein determining whether to apply the low power mode comprises: receiving a paging message, the paging message including: an identifier set of a terminal device and a paging reason set corresponding to the identifier set; Determining, based on a determination that an identifier in the identifier set matches an identifier of the terminal device, whether a paging cause corresponding to the identifier of the terminal device indicates the low power mode; and Determining the low power mode according to the paging cause indication, determining to apply the low power mode.

9. The method of claim 1 , wherein determining whether to apply the low power mode comprises: Obtain information of a channel dedicated to notification of the low power mode from system information; determining a set of opportunities for monitoring the channel, the set of opportunities being associated with a set of synchronization signal blocks; as well as The low power mode is determined to be applied based on a determination that a message is received from the channel based on the opportunity set and the synchronization signal block set, and an identifier included in the message matches an identifier of the terminal device.

10. The method of claim 1, wherein determining whether to apply the low power mode comprises: receiving a configuration for the low power mode, the configuration comprising a set of measurement criteria; performing signal measurements based on the set of measurement criteria; as well as Based on a determination that the set of measurement criteria is satisfied, a determination is made to apply the low power mode.

11. The method of claim 1 , wherein performing the operations associated with the low power mode comprises at least one of: turning off the primary radio of the terminal device; Turning on a wake-up signal receiver of the terminal device; Indicating, from a lower layer of the terminal device to an upper layer, a reason for applying the low power mode; Stop executing operations in idle or inactive states; applying a configuration for said low power mode; or Perform wake-up signal monitoring.

12. A communication method, comprising: determining at a terminal device whether a low power mode is applied, during which wake-up signal monitoring is performed; as well as Based on a determination to apply the low power mode, a request to apply the low power mode is sent.

13. The method of claim 12, wherein sending the request comprises: sending the request via auxiliary information; or The request is sent through a random access procedure for the low power mode.

14. The method of claim 13, wherein sending the request via auxiliary information comprises: receiving a configuration for transmission of the auxiliary information; as well as Sending the auxiliary information, wherein the auxiliary information includes at least one of the following: a preference for applying said low power mode, or Preferences regarding a timer for the low power mode.

15. The method of claim 13, wherein sending the request via the random access procedure comprises: Obtaining a configuration of a contention-free random access resource for the request from system information, the configuration comprising: at least one of a preamble index for the random access procedure or timing information for the random access procedure; selecting a random access preamble corresponding to the selected synchronization signal block from a set of random access preambles determined based on the preamble index; and Preamble transmission is performed based on the random access preamble and the timing information.

16. The method of claim 13, wherein sending the request via the random access procedure comprises: According to the determination of selecting the contention based preamble to perform the random access procedure, message 3 is transmitted by causing a message dedicated to the low power mode to be included in a service data unit for an uplink common control channel.

17. The method according to claim 1 or 12, further comprising: Performing an operation in an idle or inactive state based on a determination of receipt of a wake-up signal; or Based on a determination that a wake-up signal is received, an operation is performed in the connected state.

18. The method of claim 17, wherein performing the operation in the idle or inactive state comprises at least one of: Stopping the wake-up signal monitoring; performing a cell selection process; or Based on the determination that the terminal device is camped on a cell, at least one of a paging channel, a short message or system information from the cell is monitored.

19. The method of claim 17, wherein performing the operation in the connected state comprises at least one of: Stopping the wake-up signal monitoring; Performing a cell selection process; Based on the determination that the terminal device is camped on a cell, monitoring system information from the cell; or Initiate a random access procedure.

20. A communication device comprising: A processor configured to cause the device to perform a method according to any one of claims 1 to 11 or any one of claims 12 to 19.

Images