Communication method, terminal, network device, system, and storage medium
Patent Information
- Application Number
- PCT/CN2025/085140
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-26
- Publication Date
- 2026-10-01
Smart Images

Figure CN2025085140_01102026_PF_FP_ABST
Abstract
Description
Communication methods, terminals, network devices, systems, and storage media Technical Field
[0001] This disclosure relates to the field of communications, and in particular to communication methods, terminals, network devices, systems, and storage media. Background Technology
[0002] Currently, Discontinuous Reception (DRX) in connected mode has been introduced to improve battery consumption by allowing the terminal to periodically enter a "sleep" state. Summary of the Invention
[0003] To further reduce terminal power consumption, embodiments of this disclosure provide a communication method, a terminal, a network device, a system, and a storage medium.
[0004] According to a first aspect of the present disclosure, a communication method is provided, the method being executed by a terminal, the method comprising:
[0005] Based on the configuration information sent by the network device in a predefined manner, determine whether to listen for the low-power wake-up signal LP-WUS during the first time period.
[0006] According to a second aspect of the present disclosure, a communication method is provided, the method being performed by a network device, the method comprising:
[0007] The terminal sends configuration information, wherein the configuration information is used by the terminal to determine whether to listen for the low-power wake-up signal LP-WUS during the first time period.
[0008] According to a third aspect of the present disclosure, a terminal is provided, comprising:
[0009] The processing module is configured to determine whether to listen for the low-power wake-up signal LP-WUS during the first time period based on configuration information sent by a predefined method or network device.
[0010] According to a fourth aspect of the present disclosure, a network device is provided, comprising:
[0011] The transceiver module is configured to send configuration information to the terminal, wherein the configuration information is used by the terminal to determine whether to listen for the low-power wake-up signal LP-WUS during a first time period.
[0012] According to a fifth aspect of the present disclosure, a terminal is provided, comprising:
[0013] One or more processors;
[0014] The processor is used to execute the method described in any one of the first aspects.
[0015] According to a sixth aspect of the present disclosure, a network device is provided, comprising:
[0016] One or more processors;
[0017] The processor is used to execute the communication method described in any one of the second aspects.
[0018] According to a seventh aspect of the present disclosure, a communication system is provided, comprising:
[0019] A terminal, the terminal being configured to implement the communication method described in any one of the first aspects;
[0020] A network device configured to implement the communication method described in any one of the second aspects.
[0021] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a communication method as described in any one of the first or second aspects.
[0022] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, is used to implement the communication method described in any one of the first or second aspects.
[0023] In this embodiment of the disclosure, the terminal can determine whether to listen to LP-WUS in the first time period based on a predefined method or configuration information sent by the network device, thereby achieving the purpose of terminal energy saving and improving the reliability of data scheduling.
[0024] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0025] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0026] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0027] Figure 2 is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.
[0028] Figure 3A is one of the exemplary flowcharts of a communication method provided according to an embodiment of the present disclosure.
[0029] Figure 3B is a second exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.
[0030] Figure 4A is an exemplary block diagram of a terminal provided according to an embodiment of the present disclosure.
[0031] Figure 4B is an exemplary block diagram of a network device provided according to an embodiment of the present disclosure.
[0032] Figure 5A is an exemplary schematic diagram of a communication device provided according to an embodiment of the present disclosure.
[0033] Figure 5B is an exemplary schematic diagram of a chip provided according to an embodiment of the present disclosure. Detailed Implementation
[0034] This disclosure provides a communication method, terminal, network device, system, and storage medium.
[0035] In a first aspect, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising: determining whether to listen for a low-power wake-up signal LP-WUS during a first time period based on configuration information sent by a predefined method or a network device.
[0036] In the above embodiments, the terminal can determine whether to listen to LP-WUS in the first time period based on the configuration information sent by the predefined method or the network device, thereby achieving the purpose of terminal energy saving and improving the reliability of data scheduling.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is used to indicate whether the terminal listens to the LP-WUS during the first time period.
[0038] In the above embodiments, the configuration information can directly instruct the terminal whether to listen to the LP-WUS during the first time period. With less signaling resources, it can be ensured that the network device and the terminal have a consistent understanding of whether the terminal is listening to the LP-WUS during the first time period, which is beneficial to improving the reliability of data scheduling.
[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the first time period includes at least one of the following: a measurement gap; a runtime segment of a random access response window; a runtime segment of a round-trip delay timer; and a switching period of the bandwidth portion (BWP).
[0040] In the above embodiments, the first time period may include at least one of the above time periods, which improves the reliability of the terminal monitoring LP-WUS.
[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes at least one of the following: if it is determined, based on the predefined method or the configuration information, that the LP-WUS is being monitored during the first time period, determine whether to start a first timer based on whether the LP-WUS sent by the network device is received; if it is determined, based on the predefined method or the configuration information, that the LP-WUS is not being monitored during the first time period, determine to start the first timer; if it is determined, based on the predefined method or the configuration information, that the LP-WUS is not being monitored during the first time period, determine not to start the first timer; wherein, the first timer is a timer used to monitor the Physical Downlink Control Channel (PDCCH).
[0042] In the above embodiments, the terminal can determine whether to start the first timer to listen to the PDCCH, thereby improving the flexibility and reliability of data transmission.
[0043] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to start the first timer based on whether the LP-WUS sent by the network device is received includes any one of the following: determining to start the first timer if the LP-WUS sent by the network device is received; determining not to start the first timer if the LP-WUS sent by the network device is not received.
[0044] In the above embodiments, the terminal can determine whether to start the first timer based on whether it receives LP-WUS sent by the network device, thereby improving the reliability of PDCCH monitoring.
[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first timer includes at least one of the following: an activation period timer, the timing duration of which is the duration of listening to the physical downlink control channel (PDCCH) during a discontinuous reception DRX period; and a PDCCH listening timer corresponding to LP-WUS.
[0046] In the above embodiments, the first timer may include at least one of the above-mentioned features, which clarifies the terminal behavior, ensures that the network device and the terminal are immediately consistent with the terminal behavior, and improves communication reliability.
[0047] In conjunction with some embodiments of the first aspect, in some embodiments, each listening opportunity of the LP-WUS is located within the first time period; or some listening opportunities of the LP-WUS are located within the first time period.
[0048] In the above embodiments, each listening opportunity of LP-WUS may be located within the first time period, or some listening opportunities may be located within the first time period. The terminal listens to LP-WUS during the listening opportunities located within the first time period, which helps to save terminal power consumption.
[0049] Secondly, embodiments of this disclosure propose a communication method executed by a network device, the method comprising: sending configuration information to a terminal, wherein the configuration information is used by the terminal to determine whether to listen for a low-power wake-up signal LP-WUS during a first time period.
[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is used to indicate whether the terminal listens to the LP-WUS during the first time period.
[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the first time period includes at least one of the following: a measurement gap; a runtime segment of a random access response window; a runtime segment of a round-trip delay timer; and a switching period of the bandwidth portion (BWP).
[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes at least one of the following: if it is determined that the terminal is listening to the LP-WUS during the first time period, determining whether the terminal starts a first timer based on whether the LP-WUS has been sent to the terminal; if it is determined that the terminal is not listening to the LP-WUS during the first time period, determining that the terminal starts a first timer; if it is determined that the terminal is not listening to the LP-WUS during the first time period, determining that the terminal does not start a first timer; wherein, the first timer is a timer used to listen to the Physical Downlink Control Channel (PDCCH).
[0053] In conjunction with some embodiments of the second aspect, in some embodiments, determining whether the terminal starts the first timer based on whether the LP-WUS has been sent to the terminal includes any one of the following: if the LP-WUS has been sent to the terminal, determining that the terminal starts the first timer; if the LP-WUS has not been sent to the terminal, determining that the terminal does not start the first timer.
[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the first timer includes at least one of the following: an activation period timer, the timing duration of which is the duration of listening to the physical downlink control channel (PDCCH) during a discontinuous reception DRX period; and a PDCCH listening timer corresponding to LP-WUS.
[0055] In conjunction with some embodiments of the second aspect, in some embodiments, each listening opportunity of the LP-WUS is located within the first time period; or some listening opportunities of the LP-WUS are located within the first time period.
[0056] Thirdly, embodiments of this disclosure provide a terminal, including: a processing module configured to determine whether to listen to a low-power wake-up signal LP-WUS during a first time period based on configuration information sent by a predefined method or a network device.
[0057] Fourthly, embodiments of this disclosure provide a network device, including: a transceiver module configured to send configuration information to a terminal, wherein the configuration information is used by the terminal to determine whether to listen to a low-power wake-up signal LP-WUS during a first time period.
[0058] Fifthly, embodiments of this disclosure provide a terminal comprising: one or more processors; wherein the processors are configured to execute the communication method described in any one of the first aspects.
[0059] In a sixth aspect, embodiments of this disclosure provide a network device comprising: one or more processors; wherein the processors are configured to perform the communication method described in any one of the second aspects.
[0060] In a seventh aspect, embodiments of this disclosure provide a communication system comprising: a terminal configured to perform the communication method described in any one aspect; and a network device configured to perform the communication method described in any one aspect.
[0061] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in either the first or second aspect.
[0062] In a ninth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, is used to implement the communication method described in any one of the first or second aspects.
[0063] It is understood that the aforementioned terminals, network devices, communication systems, and storage media are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0064] This disclosure provides communication methods, terminals, network devices, systems, and storage media. In some embodiments, the terms "communication method" and "information transmission method," "information processing method," etc., can be used interchangeably; the terms "communication device" and "information transmission device," "information processing device," etc., can be used interchangeably; and the terms "information transmission system," "information processing system," "communication system," etc., can be used interchangeably.
[0065] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0066] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0067] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0068] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0069] In the embodiments disclosed herein, "multiple" refers to two or more.
[0070] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0071] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.
[0072] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.
[0073] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0074] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0075] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "body", etc.
[0076] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0077] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0078] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0079] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0080] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.
[0081] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.
[0082] In some embodiments, network device 102 may include at least one of access network device 102-1 and core network device 102-2.
[0083] In some embodiments, the access network device 102-1 is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.
[0084] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0085] In some embodiments, the access network device 102-2 may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. By adopting the CU-DU structure, the protocol layer of the access network device can be separated. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. However, this is not the only possibility.
[0086] In some embodiments, the core network device 102-2 may be a single device, including a first network element, a second network element, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0087] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0088] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0089] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0090] In some embodiments, DRX is described below.
[0091] The terminal periodically enters a "sleep" state (or shutdown period) to improve battery consumption, during which time there is no need to monitor the Physical Downlink Control Channel (PDCCH). To monitor the PDCCH for potential downlink and / or uplink data, the terminal can periodically wake up and remain "awake" (or on) for a period before entering the "sleep" state again. Additionally, the terminal may occasionally need to wake up to monitor the PDCCH, for example, to receive possible retransmissions.
[0092] In some embodiments, the Low Power-Wake Up Signal (LP-WUS) is described below.
[0093] For connected terminals, power-saving signals can be introduced, namely wake-up signals (WUS) or power-saving downlink control information (DCI). If the terminal detects a DCP signal, it means that PDCCH monitoring is required (e.g., starting the DRX activation period timer onDurationTimer). If no DCP signal is detected, onDurationTimer is not started, meaning the terminal skips PDCCH monitoring.
[0094] The aforementioned power-saving signals all require detection by the terminal's main radio (MR). However, simply enabling the main radio to detect the power-saving signals is still insufficient for energy efficiency. Currently, a separate receiver, namely a low-power receiver (LR), can be introduced to receive the power-saving signal LP-WUS. When the terminal uses the LR to receive LP-WUS, the MR can be put to sleep or turned off. The terminal only activates the MR to monitor the PDCCH after receiving the LP-WUS signal.
[0095] There are two schemes for connected LP-WUS: one is to start an ondurationTimer after receiving LP-WUS, and the other is to start a PDCCH monitoring timer after receiving LP-WUS, for example...
[0096] lpwus_PDCCHMonitoringTimer.
[0097] In some embodiments, if all DCP occasions associated with the current DRX cycle occur within a measurement gap, or, for example, in a scenario where a terminal associated with Beam Failure Recovery (BRF) needs to listen to the Cell-Radio Network Temporary Identifier (C-RNTI), and this occurs during the Random Access Response (RAR) window, the terminal does not listen to the DCP signal and instead starts the onduratonTimer for the current DRX cycle. The above scheme is designed for MR (Mean Memory Access). However, LP-WUS signals use a separate low-power receiver and cannot be directly implemented using this scheme.
[0098] To further reduce terminal power consumption, embodiments of this disclosure provide the following communication methods, terminals, network devices, systems, and storage media.
[0099] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to a communication method, which includes:
[0100] In step S2101, network device 102 sends configuration information to terminal 101.
[0101] In some embodiments, terminal 101 receives configuration information.
[0102] In some embodiments, configuration information may be used to indicate whether the terminal 101 listens to LP-WUS during the first time period.
[0103] In some embodiments, configuration information may occupy 1 bit, where a bit value of "1" can be used to instruct terminal 101 to listen to LP-WUS during the first time period. A bit value of "0" can be used to instruct terminal 101 not to listen to LP-WUS during the first time period.
[0104] Alternatively, a bit value of "0" can be used to instruct terminal 101 to listen to LP-WUS during the first time period. A bit value of "1" can be used to instruct terminal 101 not to listen to LP-WUS during the first time period.
[0105] The above is merely an illustrative example, and this disclosure does not limit the method by which the configuration information indicates whether the terminal 101 listens to LP-WUS during the first time period.
[0106] In some embodiments, the first time period may include, but is not limited to, at least one of the following time periods: measurement gap; runtime of random access response window; runtime of round-trip time (RTT) timer; and switching period of bandwidth part (BWP).
[0107] In one example, in a scenario where terminal 1001 associated with Beam Failure Recovery (BRF) needs to listen to C-RNTI, the first time period could be the runtime period of the RAR window.
[0108] In one example, when the RAR window is running, the Medium Access Control (MAC) entity can listen to the recovery search space, which keeps the RAR window running. The MAC entity can listen to PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the special cell (or cell group) identified by C-RNTI.
[0109] In one example, the RTT timer can be started during random access.
[0110] In one example, the switching period of a BWP includes, but is not limited to, any of the following: the period during which the BWP switches from the initial BWP to the active BWP; or the period during which the BWP switches from the deactivated BWP to the active BWP.
[0111] The above is merely an illustrative example. The first time period may also be any other time period indicated by network device 102 or agreed upon by the protocol. This disclosure does not limit this.
[0112] In some embodiments, when the network device 102 determines that the terminal 101 has energy-saving needs, it sends configuration information to the terminal 101.
[0113] In some embodiments, network device 102 may send configuration information to terminal 101 based on a terminal request.
[0114] In some embodiments, when the terminal 101 is unable to determine whether to listen to LP-WUS in the first time period based on a predefined method, the network device 102 sends configuration information to the terminal 101.
[0115] In some embodiments, network device 102 sends configuration information to terminal 101 based on scheduling requirements.
[0116] The above is merely an illustrative example, and this disclosure does not limit the conditions or timing for triggering network device 102 to send configuration information to terminal 101.
[0117] In some embodiments, step S2101 is an optional execution step. For example, if terminal 101 determines whether to listen to LP-WUS in the first time period based on other methods, step S2101 may not be executed.
[0118] In step S2102, terminal 101 determines whether to listen to LP-WUS during the first time period.
[0119] In some embodiments, terminal 101 may determine whether to listen to LP-WUS during a first time period based on a predefined method, such as a protocol agreement.
[0120] In some embodiments, terminal 101 may determine whether to listen to LP-WUS during a first time period based on configuration information sent by network device 102.
[0121] The above is merely an illustrative example, and this disclosure does not limit the method by which terminal 101 determines whether to listen to LP-WUS during the first time period.
[0122] Step S2103: Terminal 101 listens to LP-WUS during the first time period.
[0123] In some embodiments, if terminal 101 determines that it needs to listen to LP-WUS during the first time period, it listens to LP-WUS during the first time period.
[0124] In some embodiments, each listening opportunity of LP-WUS can be located within the first time period. For example, all listening opportunities of LP-WUS are located within the first time period, such as when there are three listening opportunities in LP-WUS, and all three listening opportunities are located within the first time period.
[0125] In some embodiments, some LP-WUS listening opportunities are located within the first time period. For example, some LP-WUS listening opportunities are located within the first time period, and some are located outside the first time period. For example, there are a total of 3 LP-WUS listening opportunities, of which 2 are located within the first time period and the other is located outside the first time period. At this time, terminal 101 listens to LP-WUS at the LP-WUS listening opportunities located within the first time period.
[0126] In some embodiments, terminal 101 initiates LR to listen to LP-WUS during a first time period. Correspondingly, MR may not be initiated at this time.
[0127] In some embodiments, step S2103 is an optional execution step. For example, if terminal 101 determines that it will not listen to LP-WUS during the first time period, step S2103 may not be executed.
[0128] In step S2104, terminal 101 determines whether to start the first timer.
[0129] In some embodiments, the first timer may include, but is not limited to, at least one of the following timers: an activation period timer; and a PDCCH listening timer corresponding to LP-WUS.
[0130] In one example, the duration of the active time period timer is the duration of listening to the PDCCH within the DRX cycle.
[0131] For example, the active time period timer can be onDurationTimer.
[0132] In one example, the PDCCH monitoring timer corresponding to LP-WUS can be lpwus_PDCCHMonitoringTimer.
[0133] The above is merely an illustrative example, and this disclosure does not limit the type of the first timer.
[0134] In some embodiments, if terminal 101 determines, based on the predefined method or the configuration information, that it is listening to the LP-WUS during the first time period, it can determine whether to start the first timer based on whether it receives the LP-WUS sent by the network device.
[0135] In one example, upon receiving the LP-WUS sent by the network device, terminal 101 determines to start a first timer.
[0136] In one example, terminal 101 determines not to start the first timer if it does not receive the LP-WUS sent by the network device.
[0137] In some embodiments, if terminal 101 determines that it will not listen to LP-WUS during the first time period based on the predefined method or the configuration information, terminal 101 will receive LP-WUS by default, and at this time terminal 101 will start the first timer.
[0138] In some embodiments, if terminal 101 determines that it does not listen to LP-WUS during the first time period based on the predefined method or the configuration information, terminal 101 defaults to not receiving LP-WUS, and at this time terminal 101 determines not to start the first timer.
[0139] The above is merely an illustrative example, and this disclosure does not limit the method by which terminal 101 determines whether to start the first timer.
[0140] Step S2105: Terminal 101 starts the first timer.
[0141] In some embodiments, terminal 101 starts an activation period timer.
[0142] In one example, terminal 101 can start the activation period timer at the beginning of the activation period according to the DRX cycle.
[0143] In some embodiments, terminal 101 starts the PDCCH listening timer corresponding to LP-WUS.
[0144] In one example, terminal 101 can start the PDCCH listener timer immediately if it determines that the timer corresponding to LP-WUS should be started.
[0145] In some embodiments, terminal 101 starts an activation period timer and starts a PDCCH listening timer corresponding to LP-WUS.
[0146] In one example, terminal 101 can immediately start the PDCCH listening timer corresponding to LP-WUS, and start the activation period timer at the beginning of the activation period according to the DRX cycle.
[0147] The above is merely an illustrative example, and this disclosure does not limit the timing of starting the first timer.
[0148] In some embodiments, for scenarios where the decision to start the first timer, such as lpwus_PDCCHMonitoringTimer, is based on whether LP-WUS is received, the network device 102 may not need to configure the Channel State Information-mask (CSI-mask), or the network device 102 may not be able to configure the CSI-mask, or the network device 102 may not be able to set the CSI-mask to true. In other words, the CSI-mask is not applicable to this scenario.
[0149] CSI-mask refers to the method of masking or ignoring certain subcarriers during CSI measurements. CSI-mask can reduce interference and noise during the measurement process, improving the accuracy and reliability of the measurement.
[0150] In some embodiments, step S2105 is an optional execution step. For example, if terminal 101 determines that the first timer will not be started, step S2105 may not be executed.
[0151] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0152] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0153] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.
[0154] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0155] In some embodiments, the communication method involved in this disclosure may include at least one of steps S2101 to S2105. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2101+S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, steps S2101 to S2103 may be implemented as independent embodiments, step S2104 may be implemented as an independent embodiment, step S2105 may be implemented as an independent embodiment, steps S2104+S2105 may be implemented as an independent embodiment, and steps S2101 to S2105 may be implemented as independent embodiments, but are not limited thereto.
[0156] In some embodiments, steps S2101 to S2105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0157] In some embodiments, the execution order of steps S2101 to S2105 is not limited.
[0158] The above embodiments achieve the goal of terminal energy saving, which is conducive to improving the reliability of data scheduling.
[0159] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication method that can be executed by a terminal 101, and the method includes:
[0160] Step S3101: Determine whether to monitor LP-WUS during the first time period.
[0161] In some embodiments, optional implementations of step S3101 can be found in optional implementations of step S2102 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0162] The above embodiments achieve the goal of terminal energy saving, which is conducive to improving the reliability of data scheduling.
[0163] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method that can be executed by a network device 102, and the method includes:
[0164] Step S3201: Send configuration information.
[0165] In some embodiments, configuration information is used to indicate whether the terminal 101 listens to LP-WUS during the first time period.
[0166] In some embodiments, network device 102 sends configuration information to terminal 101.
[0167] In some embodiments, terminal 101 receives configuration information.
[0168] In some embodiments, optional implementations of step S3201 can be found in optional implementations of step S2101 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.
[0169] In the above embodiments, the network device can configure the terminal to determine whether to listen to LP-WUS in the first time period through configuration information, thereby achieving the purpose of terminal energy saving and improving the reliability of data scheduling.
[0170] The above process is further illustrated with examples below.
[0171] This disclosure provides a network-controlled LP-WUS monitoring method that enables terminals and network devices to have a unified understanding of the startup of ondurationTimer or lpwus_PDCCHMonitoringTimer, facilitating terminal energy saving and network scheduling data.
[0172] The method includes the following:
[0173] 1. The terminal determines whether to listen to LP-WUS during the first time period based on the protocol agreement or network configuration information.
[0174] 2. Based on 1, the configuration information indicates whether the terminal is listening to LP-WUS during the first time period;
[0175] 3. Based on 1, the first time period includes the measurement gap.
[0176] 4. Based on 1, the first time period includes the runtime of the RAR window.
[0177] As an example:
[0178] At this time, the MAC entity is listening to the recovery search space, causing the RAR window to run; the MAC entity can listen to PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the SpCell identified by C-RNTI.
[0179] 5. Based on 1, the first time period includes the runtime segment of RTT;
[0180] 6. Based on 1, the first time period includes the time period of BWP switching;
[0181] 7. Based on 1, if the terminal is listening to LP-WUS based on the protocol agreement or network indication, the terminal will determine whether to start ondurationTimer or lpwus_PDCCHMonitoringTimer based on whether LP-WUS is received.
[0182] 8. Based on 1, if LP-WUS is not monitored based on protocol agreement or network indication, the terminal starts ondurationTimer or lpwus_PDCCHMonitoringTimer.
[0183] 9. Based on 1, if the instruction is not to listen to LP-WUS, the terminal will not start ondurationTimer or lpwus_PDCCHMonitoringTimer.
[0184] 10. Based on 1, for the first time period, all or part of the monitoring occasions of LP-WUS are in the first time period.
[0185] In some embodiments, for scenarios where the start of lpwus_PDCCHMonitoringTimer is determined by whether LP-WUS is received, since ondurationTimer is not started, the network may not need to configure CSI-mask, or the network may not configure CSI-mask, or the network may not set CSI-mask=true. In other words, CSI-mask is not applicable to this scenario.
[0186] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0187] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0188] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0189] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. The terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, the terminal 4100 may include a processing module 4101.
[0190] In some embodiments, the processing module 4101 is used to determine whether to listen to the low-power wake-up signal LP-WUS during a first time period based on configuration information sent by a predefined method or network device.
[0191] Optionally, the processing module 4101 is used to execute at least one of the other steps executed by the terminal 4100 in any of the above methods (e.g., steps S2102, S2103, S2104, S2105, but not limited thereto), which will not be elaborated here.
[0192] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include a transceiver module 4201.
[0193] In some embodiments, the transceiver module 4201 is used to send configuration information to the terminal, wherein the configuration information is used by the terminal to determine whether to listen to the low-power wake-up signal LP-WUS during a first time period.
[0194] Optionally, the transceiver module 4201 is used to perform at least one of the communication steps (such as step S2101, but not limited thereto) performed by the network device 4200 in any of the above methods, which will not be described in detail here.
[0195] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0196] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor, and the transceiver module may be interchangeable with a transceiver.
[0197] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0198] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.
[0199] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps (e.g., step S2101, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 5101 performs at least one of other steps (e.g., steps S2102, S2103, S2104, S2105, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0200] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.
[0201] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0202] Figure 5B is a schematic diagram of the structure of the chip 5200 proposed in an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, the schematic diagram of the chip 5200 shown in Figure 5B can be referred to, but is not limited thereto.
[0203] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.
[0204] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.
[0205] In some embodiments, the interface circuit 5202 performs at least one of the communication steps (e.g., step S2101, but not limited thereto) in the above-described method, such as sending and / or receiving. For example, the interface circuit 5202 performing the communication steps (e.g., sending and / or receiving) in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103, S2104, S2105, but not limited thereto).
[0206] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0207] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0208] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0209] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0210] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A communication method characterized by comprising: The method is executed by a terminal, and the method includes: Based on the configuration information sent by the network device in a predefined manner, determine whether to listen for the low-power wake-up signal LP-WUS during the first time period.
2. The method according to claim 1, characterized in that, The configuration information is used to indicate whether the terminal listens to the LP-WUS during the first time period.
3. The method according to claim 1 or 2, characterized in that, The first time period includes at least one of the following: Measuring gap; The runtime segment for the random access response window; The runtime segment of the round-trip delay timer; The switching period for the bandwidth portion of BWP.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes at least one of the following: If it is determined, based on the predefined method or the configuration information, that the LP-WUS is being monitored during the first time period, then it is determined whether to start the first timer based on whether the LP-WUS sent by the network device is received. Based on the predefined method or the configuration information, if it is determined that the LP-WUS is not being monitored during the first time period, the first timer is started. Based on the predefined method or the configuration information, if it is determined that the LP-WUS is not being monitored during the first time period, it is determined that the first timer will not be started; The first timer is used to monitor the Physical Downlink Control Channel (PDCCH).
5. The method of claim 4, wherein, The step of determining whether to start the first timer based on whether the LP-WUS sent by the network device is received includes any one of the following: Upon receiving the LP-WUS sent by the network device, determine to start the first timer; If the LP-WUS is not received from the network device, it is determined that the first timer will not be started.
6. The method according to claim 4 or 5, characterized in that, The first timer includes at least one of the following: An activation period timer is set up, the duration of which is the duration of listening to the physical downlink control channel (PDCCH) during a discontinuous reception DRX period. The PDCCH monitoring timer corresponding to LP-WUS.
7. The method according to any one of claims 1-6, characterized in that, Each listening opportunity of the LP-WUS is located within the first time period; or The LP-WUS monitoring occurs during the first time period.
8. A communication method characterized by comprising: The method is performed by a network device, and the method includes: Send configuration information to the terminal, wherein the configuration information is used by the terminal to determine whether to listen for the low-power wake-up signal LP-WUS during the first time period.
9. The method according to claim 8, characterized in that, The configuration information is used to indicate whether the terminal listens to the LP-WUS during the first time period.
10. The method according to claim 8 or 9, characterized in that, The first time period includes at least one of the following: Measuring gap; The runtime segment for the random access response window; The runtime segment of the round-trip delay timer; The switching period for the bandwidth portion of BWP.
11. The method according to any one of claims 8-10, characterized in that, The method further includes at least one of the following: If it is determined that the terminal is listening to the LP-WUS during the first time period, it is determined whether the terminal starts the first timer based on whether the LP-WUS is sent to the terminal. If it is determined that the terminal does not listen to the LP-WUS during the first time period, it is determined that the terminal starts the first timer; If it is determined that the terminal does not listen to the LP-WUS during the first time period, it is determined that the terminal does not start the first timer; The first timer is used to monitor the Physical Downlink Control Channel (PDCCH).
12. The method of claim 11, wherein, The step of determining whether the terminal starts the first timer based on whether the LP-WUS has been sent to the terminal includes any one of the following: If the LP-WUS is sent to the terminal, it is determined that the terminal starts the first timer; If the LP-WUS is not sent to the terminal, it is determined that the terminal will not start the first timer.
13. The method according to claim 11 or 12, characterized in that, The first timer includes any one of the following: An activation period timer is set up, the duration of which is the duration of listening to the physical downlink control channel (PDCCH) during a discontinuous reception DRX period. The PDCCH monitoring timer corresponding to LP-WUS.
14. The method according to any one of claims 8-13, characterized in that, Each listening opportunity of the LP-WUS is located within the first time period; or The LP-WUS monitoring occurs during the first time period.
15. A terminal, characterized by include: The processing module is configured to determine whether to listen for the low-power wake-up signal LP-WUS during the first time period based on configuration information sent by a predefined method or network device.
16. A network device, comprising: include: The transceiver module is configured to send configuration information to the terminal, wherein the configuration information is used by the terminal to determine whether to listen for the low-power wake-up signal LP-WUS during a first time period.
17. A terminal, characterized by include: One or more processors; The processor is used to execute the method according to any one of claims 1-7.
18. A network device, comprising: include: One or more processors; The processor is used to execute the communication method according to any one of claims 8-14.
19. A communication system, characterized by include: A terminal configured to implement the communication method according to any one of claims 1-7; A network device configured to implement the communication method according to any one of claims 8-14.
20. A storage medium, the storage medium storing instructions, wherein, When the instruction is executed on the communication device, it causes the communication device to perform the communication method as described in any one of claims 1-7 or 8-14.
21. A computer program product comprising a computer program, characterized in that, When executed by a processor, the computer program is used to implement the communication method according to any one of claims 1-7 or 8-14.