Communication method and related device

Abstract

The application provides a communication method and related equipment for reducing power consumption of a terminal device. The communication method applied to a network device comprises: sending first information to the terminal device, the first information indicating a first LO in which a target LP-WUS is located, so that the terminal device listens to the target LP-WUS at the first LO.

Description

Communication method and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410405222.5 and invention name “Communication Method and Related Equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to communication methods and related equipment. Background Art

[0003] With the continuous development of the information age and the widespread use of network communications, green communications has become a hot topic. Green communications aims to reduce the power consumption of communication systems, reduce the generation of electronic waste, and improve the efficient use of resources. Among these, reducing the power consumption of communication equipment has attracted widespread attention.

[0004] In related communication methods, a terminal device parses downlink channel information during the paging occasion (PO) of its corresponding paging frame (PF). However, the paging message may not be addressed to the terminal device itself. Therefore, it is meaningless for the terminal device to wake up and parse the downlink channel information during the PO, wasting the terminal device's power consumption. Summary of the Invention

[0005] The present application provides a communication method and related devices for reducing the power consumption of terminal devices.

[0006] In a first aspect, the present application provides a communication method, which is applied to a network device, comprising:

[0007] The network device sends first information to the terminal device, where the first information is used to indicate a first low power wake-up occasion (LO) at which a target low power wake-up signal (LP-WUS) is located, so that the terminal device monitors the target LP-WUS at the first LO. The network device can configure one or more LOs for the terminal device, so the network device needs to indicate the effective configuration information to synchronize the terminal device and the network device. Therefore, the network device sends the first information to the terminal device, and the first information may include a configuration identifier of the first LO.

[0008] In the communication method, a network device sends a first message to a terminal device, where the first message indicates a first LO where a target LP-WUS is located, so that the terminal device monitors the target LP-WUS at the first LO. For a terminal device in an idle or inactive state, the monitored target LP-WUS indicates whether the terminal device obtains a paging message at the corresponding PF or PO, thereby avoiding waking up the main receiver (MR) during a period when it is not paged, thereby reducing the power consumption of the terminal device. For a terminal device in a connected state, the monitored target LP-WUS indicates whether the terminal device monitors the information of the physical downlink control channel (PDCCH) at the corresponding time, thereby avoiding the terminal device monitoring when there is no information transmission on the PDCCH, thereby reducing the power consumption of the terminal device.

[0009] In some optional implementations of the first aspect, before sending the first information to the terminal device, the network device may further send configuration information of at least one LO to the terminal device, where the configuration information of each LO is used to define the LO, and the configuration information of at least one LO includes configuration information of the first LO. The configuration information of each LO includes at least one of a relationship between the LO and a low power-wake-up signal monitor occasion (LMO), time domain configuration information of the LO, frequency domain configuration information of the LO, or a configuration identifier of the LO. The LO is defined or described from multiple perspectives, making it easier for the terminal device to determine the LO based on the configuration information.

[0010] In this application, the network device configures one or more LOs for the terminal device, which can flexibly adapt to different scenario requirements. In different communication scenarios, the terminal device can monitor LP-WUS based on different LOs, thereby realizing monitoring of downlink signals, enriching the application scenarios and implementation methods of the technical solution of this application.

[0011] In some optional implementations of the first aspect, the LO defined by the configuration information of each LO includes at least one LMO. For the network device, the LMO is used to send the LP-WUS.

[0012] In this application, LO includes at least one LMO, which is used by the network device to send LP-WUS, further refining the sending timing of LP-WUS.

[0013] In a second aspect, the present application provides a communication method, which is applied to a terminal device and includes:

[0014] The terminal device receives first information from the network device, the first information being used to indicate a first LO where a target LP-WUS is located. Based on the first information, the terminal device monitors the target LP-WUS at the first LO. The target LP-WUS indicates when the terminal device should monitor downlink signals. The terminal device wakes up the main receiver only at this time and does not wake up the main receiver at other times, thereby reducing power consumption of the terminal device.

[0015] In some optional implementations of the second aspect, before receiving the first information from the network device, the terminal device may also receive configuration information of at least one LO from the network device, where the configuration information of each LO is used to define the LO, and the configuration information of at least one LO includes the configuration information of the first LO.

[0016] In this application, the network device configures one or more LOs for the terminal device, which can flexibly adapt to different scenario requirements. In different communication scenarios, the terminal device can monitor LP-WUS based on different LOs, thereby realizing monitoring of downlink signals, enriching the application scenarios and implementation methods of the technical solution of this application.

[0017] In some optional implementations of the second aspect, the LO defined by the configuration information of each LO includes at least one LMO. For the terminal device, the LMO is used to monitor the LP-WUS.

[0018] In this application, LO includes at least one LMO, which is used by the terminal device to send LP-WUS, further refining the monitoring timing of LP-WUS.

[0019] In some optional implementations of the second aspect, after a terminal device in an idle or inactive state monitors a target LP-WUS, the terminal device determines, based on an indication from the target LP-WUS, whether to monitor a paging message from a PF or PO corresponding to the target LP-WUS. If the target LP-WUS indicates that it is not monitoring a paging message at the corresponding PF or PO, the terminal device's main receiver is not awakened, thereby reducing power consumption of the terminal device.

[0020] In some optional implementations of the second aspect, after a terminal device in a connected state monitors a target LP-WUS, it determines whether to monitor the PDCCH based on an indication from the target LP-WUS. If the target LP-WUS indicates not to monitor the PDCCH, a primary receiver of the terminal device is not awakened, thereby reducing power consumption of the terminal device.

[0021] In some optional implementations of the first aspect or the second aspect, if the terminal device is in an idle state or an inactive state, the configuration information of each LO includes a first period and / or a first time domain parameter. The first period corresponds to a first duration (i.e., the first duration is configured), or the duration of the first period is predefined, or the duration of the first period is the same as the duration of the paging period. The first time domain parameter includes a first time domain offset and a second time domain offset, or includes a third time domain offset and a second duration. The first time domain offset indicates the time offset between the start time of each LO and the PF or PO, the second time domain offset indicates the time offset between the end time of each LO and the PF or PO, and the third time domain offset indicates the time offset between the start time or end time of each LO and the PF or PO.

[0022] In this application, for terminal devices in an idle or inactive state, the time domain information in the configuration information of each LO configured by the network device is associated with the paging message and matched with the state of the terminal device. This provides technical support for the implementation of the technical solution of this application and enhances the feasibility of the technical solution. At the same time, there are multiple options when configuring the time domain information, which enriches the implementation methods of the technical solution and improves the flexibility of the technical solution.

[0023] In some optional implementations of the first aspect or the second aspect, if the terminal device is in an idle state or an inactive state, each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a bitmap of the paging packet.

[0024] In some optional implementations of the first aspect or the second aspect, if the terminal device is in an idle state or an inactive state, each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a paging packet.

[0025] In this application, there are multiple possibilities for the information indicated by the LP-WUS corresponding to each LMO, which enriches the implementation methods and application scenarios of the technical solution of this application.

[0026] In some optional implementations of the first aspect or the second aspect, the message carrying the first information includes: a radio resource control release (RRC release) message, or a group common downlink control information (group common DCI) message.

[0027] In some optional implementations of the first aspect or the second aspect, if the terminal device is in a connected state, the configuration information of each LO includes a second period and a second time domain parameter. The second period corresponds to a third duration (i.e., the third duration is configured), or the duration of the second period is predefined, or the duration of the second period is the same as the duration of the period of discontinuous reception (DRX) of the terminal device. The second time domain parameter includes a fourth time domain offset and a fifth time domain offset, or includes a sixth time domain offset and a fourth duration. The fourth time domain offset indicates the time offset between the start time of each LO and the start symbol of the DRX of the terminal device in the connected state, the fifth time domain offset indicates the time offset between the end time of each LO and the start symbol of the DRX of the terminal device in the connected state, and the sixth time domain offset indicates the time offset between the start time or end time of each LO and the start symbol of the DRX of the terminal device in the connected state.

[0028] In this application, for a terminal device in a connected state, the time domain information in the configuration information of each LO configured by the network device can be associated with the DRX of the terminal device and matched with the state of the terminal device, providing technical support for the implementation of the technical solution of this application and enhancing the feasibility of the technical solution. At the same time, there are multiple options when configuring the time domain information, which enriches the implementation methods of the technical solution and improves the flexibility of the technical solution.

[0029] In some optional implementations of the first aspect or the second aspect, if the terminal device is in a connected state, the LP-WUS corresponding to each LMO indicates at least one terminal identifier.

[0030] In some optional implementations of the first aspect or the second aspect, if the terminal device is in a connected state, the first information carried includes: an RRC message, a DCI message, or a media access control element (MAC-CE) message.

[0031] In this application, the message type carrying the first information varies depending on the state of the terminal device, matching the state of the terminal device, thereby enhancing the feasibility of the technical solution of this application. In addition, whether it is for a terminal device in an idle or inactive state, or for a terminal device in a connected state, there are multiple possible message types carrying the first information, which can be flexibly selected based on the needs of the actual application, thereby enhancing the flexibility of the technical solution of this application.

[0032] In some optional implementations of the first aspect or the second aspect, the configuration information of each LO may further include a monitoring mode of each LO, where the monitoring mode includes duty-cycled monitoring or continuous monitoring.

[0033] In some optional implementations of the first or second aspects, the configuration information for each LO further includes: the starting position and duration of each LMO included in each LO. Alternatively, the configuration information further includes: the starting position and duration of the first or last LMO in each LO, and the time interval between LMOs included in each LO. Alternatively, the configuration information further includes: the number of LMOs included in each LO, and the time interval between LMOs included in each LO.

[0034] In this application, the configuration information for each LO indicates the relationship between the LO and the LMO, allowing the terminal device to accurately locate the LMO. The LMO is used to send the LP-WUS. The terminal device's low-power receiver only needs to listen when the LMO is awake. During the LO's non-LMO period, it can be dormant, further reducing the terminal device's power consumption.

[0035] In some optional implementations of the first or second aspects, the configuration information for each LO further includes: a frequency domain starting position and a first bandwidth; or a frequency domain offset and a second bandwidth. The frequency domain offset indicates the frequency offset of each LO from a synchronization signal / physical broadcast channel block (SSB). Alternatively, the frequency domain offset indicates the frequency offset of each LO from a frequency reference point (point A).

[0036] In this application, there are multiple ways to set the frequency domain information of each LO, which enriches the implementation methods and application scenarios of the technical solution of this application and improves the flexibility of the technical solution.

[0037] In some optional implementations of the first aspect or the second aspect, the configuration information of each LO further includes: a configuration identifier of each LO.

[0038] In the present application, when multiple LOs are configured, the effective LO can be uniquely indicated by the configuration identifier, thereby avoiding errors caused by unclear indications and improving the reliability of the technical solution.

[0039] In some optional implementations of the first aspect or the second aspect, the message carrying configuration information of at least one LO includes: a system information block (SIB) message and an RRC message.

[0040] In the present application, there are multiple possibilities for messages carrying configuration information of at least one LO, which can be flexibly selected based on the needs of actual applications, enriching the implementation methods of the technical solutions of the present application.

[0041] In some optional implementations of the first aspect or the second aspect, a band with part (BWP) includes configuration information of one or more LOs.

[0042] In the present application, there are multiple possible amounts of LO configuration information included in a BWP, which enriches the implementation methods and application scenarios of the technical solution of the present application.

[0043] In a third aspect, the present application provides a communication method, which is applied to a network device, and the method includes:

[0044] Second information is sent to the terminal device, where the second information indicates first configuration information of the first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB.

[0045] In this application, the second information sent by the network device to the terminal device indicates the configuration information of LP-WUS or LP-SS, so that the terminal device determines whether to wake up the main receiver to monitor the downlink channel during a specified period based on LP-WUS, thereby reducing the power consumption of the terminal device. Alternatively, the terminal device synchronizes and measures the low-power wake-up receiver based on LP-SS to ensure the normal operation of the low-power wake-up receiver, thereby improving the accuracy of the solution.

[0046] In some optional implementations of the third aspect, before sending the second information to the terminal device, the network device further sends at least one set of configuration information of the first signal to the terminal device, where the at least one set of configuration information includes the first configuration information.

[0047] In this application, the network device can configure multiple sets of first signal configuration information for the terminal device. When using a certain set of configurations, it only needs to send information indicating a certain set of configurations to the terminal device, thereby flexibly adapting to different scenario requirements and improving the flexibility of the technical solution of this application.

[0048] In a fourth aspect, the present application provides a communication method, which is applied to a terminal device, and the method includes:

[0049] The terminal device receives second information from a network device, the second information indicating first configuration information of a first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB. Based on the first configuration information, the terminal device monitors the first signal. If the first signal is LP-SS, the terminal device synchronizes and measures a low-power wake-up receiver based on the LP-SS. If the first signal is LP-WUS, the terminal device determines, based on the LP-WUS, whether to wake up the main receiver during a specified LP-WUS period to monitor the downlink channel, thereby reducing power consumption of the terminal device.

[0050] In some optional implementations of the fourth aspect, before receiving the second information from the network device, the terminal device also receives at least one set of configuration information of a first signal from the network device, and the at least one set of configuration information includes the first configuration information.

[0051] In this application, the network device can configure multiple sets of first signal configuration information for the terminal device. When using a certain set of configurations, it only needs to send information indicating a certain set of configurations to the terminal device, thereby flexibly adapting to different scenario requirements and improving the flexibility of the technical solution of this application.

[0052] In some optional implementations of the fourth aspect, after the terminal device in an idle state or an inactive state monitors the first signal. If the first signal includes LP-WUS, the terminal device determines whether to monitor the paging message of the PF or PO corresponding to the LP-WUS based on the indication of the LP-WUS. If the LP-WUS indication does not monitor the paging message at the corresponding PF or PO, the main receiver of the terminal device will not be awakened, thereby reducing the power consumption of the terminal device. If the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on the LP-SS, thereby ensuring the normal operation of the low-power wake-up receiver.

[0053] In some optional implementations of the fourth aspect, after the terminal device in the connected state monitors the first signal. If the first signal includes LP-WUS, the terminal device determines whether to monitor PDCCH based on the indication of LP-WUS. If the LP-WUS indicates not to monitor PDCCH, the main receiver of the terminal device will not be awakened, reducing the power consumption of the terminal device. If the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on LP-SS, thereby ensuring the normal operation of the low-power wake-up receiver. In some optional implementations of the third aspect or the fourth aspect, each set of configuration information in at least one set of configuration information includes time domain configuration information of the first signal. Specifically including: the time domain offset between the time domain starting position of the first signal and the starting position of the SSB, and / or the duration of the first signal.

[0054] In some optional implementations of the third or fourth aspects, each set of configuration information in the at least one set of configuration information includes frequency domain configuration information of the first signal. Specifically, it includes: a frequency domain offset of the first signal and / or a bandwidth of the first signal. The frequency domain offset of the first signal indicates a frequency domain offset between a frequency domain starting position of the first signal and an SSB, or indicates a frequency offset between the frequency domain starting position of the first signal and point A.

[0055] In some optional implementations of the third aspect or the fourth aspect, each set of configuration information in the at least one set of configuration information includes a configuration identifier and a period of the first signal, wherein the period of the first signal can be understood as a time domain configuration of the first signal.

[0056] In the present application, the time domain configuration and frequency domain configuration included in each set of configuration information of the first signal have multiple possible situations, which can flexibly adapt to different scenarios and enrich the implementation method of the technical solution of the present application.

[0057] In some optional implementations of the third aspect or the fourth aspect, if the terminal device is in an idle state or an inactive state, the message carrying the second information includes: an RRC release message or a group-common DCI message. If the terminal device is in a connected state, the message carrying the second information includes: an RRC message, a DCI message, or a MAC-CE message.

[0058] In the embodiments of the present application, the message type carrying the first information varies depending on the state of the terminal device, matching the state of the terminal device, thereby enhancing the feasibility of the technical solution of the present application. In addition, whether it is for a terminal device in an idle or inactive state, or for a terminal device in a connected state, there are multiple possible message types carrying the second information, which can be flexibly selected based on the needs of the actual application, thereby enhancing the flexibility of the technical solution of the present application.

[0059] In some optional implementations of the third aspect or the fourth aspect, the message carrying at least one set of configuration information of the first signal includes a SIB message or an RRC message.

[0060] In the embodiment of the present application, there are multiple possibilities for the message carrying at least one set of configuration information of the first signal, which can be flexibly selected based on the needs of actual application, enriching the implementation method of the technical solution of the present application.

[0061] In a fifth aspect, an embodiment of the present application provides a communication method, which is applied to a network device, and the method includes:

[0062] The network device sends a master information block (MIB) message to the terminal device. The MIB message includes a first field and a second field. The first field is used to determine the subcarrier offset, and the second field is used to indicate the position of SIB1. When the subcarrier offset determined based on the first field is a preset value, a first signal is sent to the terminal device based on the communication resources of SIB1. The first signal includes a low-power wake-up signal LP-WUS or a low-power synchronization signal LP-SS.

[0063] In a sixth aspect, an embodiment of the present application provides a communication method, which is applied to a terminal device, and the method includes:

[0064] A terminal device receives a MIB message from a network device, the MIB message including a first field and a second field, the first field being used to determine a subcarrier offset, and the second field being used to indicate a position of SIB1. When the subcarrier offset determined based on the first field is a preset value, the terminal device receives a first signal sent by the network device based on a communication resource of SIB1, the first signal including LP-WUS or LP-SS.

[0065] In some optional implementations of the sixth aspect, if the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on the LP-SS. If the first signal includes LP-WUS, then for a terminal device in an idle or inactive state, it is determined whether to wake up the main receiver at the time indicated by the LP-WUS and obtain a paging message; for a terminal device in a connected state, it is determined whether to wake up the main receiver at the time indicated by the LP-WUS and monitor the PDCCH, thereby reducing power consumption of the terminal device.

[0066] In some optional implementations of the fifth or sixth aspects, the preset value includes: a subcarrier offset value of 30 in a frequency band below 6 GHz, or a subcarrier offset value of 14 in a 5G millimeter wave frequency band. That is, the preset value includes FR1 Kssb=30, or FR2 Kssb=14.

[0067] In this application, a network device may define a new meaning for a subcarrier offset determined based on a first field in a MIB message to enable transmission of a first signal. A new method for indicating the communication resources used when transmitting the first signal is provided, so that a terminal device can monitor the first signal based on the MIB message.

[0068] In a seventh aspect, the present application provides a communication method, which is applied to a network device, and the method includes:

[0069] When the network device schedules the SSB according to the resource group block (RGB), and the RGB of the scheduled SSB also includes an idle RB, the network device sends a first signal to the terminal device based on the communication resources of the idle RB. The first signal includes LP-WUS or LP-SS.

[0070] In an eighth aspect, an embodiment of the present application provides a communication method, which is applied to a terminal device, and the method includes:

[0071] The terminal device receives a first signal from the network device. The first signal is sent to the terminal device based on communication resources of an idle RB when the network device schedules the SSB according to the RGB, and the RGB of the scheduled SSB also includes an idle RB. The first signal includes LP-WUS or LP-SS.

[0072] In some optional implementations of the eighth aspect, if the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on the LP-SS. If the first signal includes LP-WUS, then, for a terminal device in an idle or inactive state, it is determined whether to wake up the main receiver at the time indicated by the LP-WUS and obtain a paging message; for a terminal device in a connected state, it is determined whether to wake up the main receiver at the time indicated by the LP-WUS and monitor the PDCCH, thereby reducing power consumption of the terminal device.

[0073] In a ninth aspect, the present application provides a communication device, comprising a module capable of implementing the operation of the network device in the first aspect, any possible implementation of the first aspect, the third aspect, any possible implementation of the third aspect, the fifth aspect, any possible implementation of the fifth aspect, the seventh aspect, or any possible implementation of the seventh aspect. The beneficial effects thereof are as described in the corresponding implementations and are not further described herein.

[0074] In a tenth aspect, the present application provides a communication device, comprising a module capable of implementing the operation of a network device in the second aspect, any possible implementation of the second aspect, the fourth aspect, any possible implementation of the fourth aspect, the sixth aspect, any possible implementation of the sixth aspect, the eighth aspect, or any possible implementation of the eighth aspect. The beneficial effects thereof are as described in the corresponding implementations and are not further described herein.

[0075] In the eleventh aspect, the present application provides a communication device comprising a processor and a memory, wherein the processor stores instructions. When the instructions stored in the memory are executed on the processor, the method shown in any one of the aforementioned aspects from the first to the eighth aspect, or any possible implementation of the first aspect to any possible implementation of the eighth aspect is implemented.

[0076] In the twelfth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a processor, the method shown in any one of the aforementioned aspects from the first to the eighth aspects, or any possible implementation of the first aspect to any possible implementation of the eighth aspect is implemented.

[0077] In the thirteenth aspect, the present application provides a computer program product, which, when executed on a processor, implements the method shown in any one of the aforementioned aspects from the first to the eighth aspect, or any possible implementation of the first aspect to any possible implementation of the eighth aspect.

[0078] The beneficial effects shown in any one of aspects 11 to 13 are similar to the methods shown in any one of aspects 1 to 8, or any possible implementation of aspect 1 to any possible implementation of aspect 8, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] FIG1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0080] FIG2 is a schematic diagram showing the working principle of a low-power wake-up signal provided in an embodiment of the present application;

[0081] FIG3 is a schematic diagram of a discontinuous reception mechanism of a terminal device provided in an embodiment of the present application;

[0082] FIG4 is a schematic diagram of a paging frame provided in an embodiment of the present application;

[0083] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;

[0084] FIG6 is a schematic diagram of a LO provided in an embodiment of the present application;

[0085] FIG7 is another schematic diagram of a LO provided in an embodiment of the present application;

[0086] FIG8 is another schematic diagram of a LO provided in an embodiment of the present application;

[0087] FIG9 is another schematic diagram of a LO provided in an embodiment of the present application;

[0088] FIG10 is another schematic diagram of a LO provided in an embodiment of the present application;

[0089] FIG11 is another schematic diagram of a communication method provided in an embodiment of the present application;

[0090] FIG12 is another schematic diagram of a communication method provided in an embodiment of the present application;

[0091] FIG13 is a schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0092] FIG14 is a schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0093] FIG15 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] The embodiments of the present application provide a communication method and related devices for reducing the power consumption of terminal devices.

[0095] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0096] First, please refer to Figure 1, which is a schematic diagram of the system architecture provided in an embodiment of the present application. It should be understood that Figure 1 shows a possible, non-limiting system schematic diagram.

[0097] As shown in FIG1 , the communication system includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes a RAN node 110, a terminal device 121, and a terminal device 122.

[0098] Exemplarily, terminal device 121 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wiredly connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 may be different physical devices, or may be the same physical device that integrates core network logical functions and radio access network logical functions, which is not specifically limited herein.

[0099] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0100] The RAN node 110 , also known as a network device, sometimes also referred to as an access network device, a RAN entity or an access node, is a part of a communication system and is used to help terminal devices achieve wireless access.

[0101] In some possible implementations, the RAN node 110 may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node 110 may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. It should be noted that the RAN node 110 in this application may also be a logical node, a logical module, or software that can implement all or part of the functions of the RAN node 110, and the specific details are not limited here.

[0102] The terminal device 121 may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal in the embodiment of the present application can be widely used in various scenarios, for example, device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The embodiment of the present application does not limit the device form of the terminal. For example, Figure 1 shows two different types of terminal devices, namely terminal device 121 and terminal device 122. In addition, all or part of the functions of the terminal device in this application can also be implemented through software functions running on hardware. The terminal device in this application can also be a logical node, logical module or software that can implement all or part of the terminal device functions. The specific details are not limited here.

[0103] It should be noted that Figure 1 is only an example of a communication system. In actual applications, the RAN 100 may include a larger number of RAN nodes and a larger or smaller number of terminal devices. The types of the multiple RAN nodes may be the same, partially the same, or completely different, and the specifics are not limited here. The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul equipment (not shown in Figure 1).

[0104] In this application, "sending information to... (e.g., a terminal device)" can be understood as the destination of the information being the terminal device. This can include sending information to the terminal device directly or indirectly. "Receiving information from... (e.g., a terminal device)" can be understood as the source of the information being the terminal device, which can include receiving information from the terminal device directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0105] The following is an explanation of the relevant technical background involved in the embodiment of the present application. Please refer to Figure 2, which is a schematic diagram of the working principle of the low-power wake-up signal provided in the embodiment of the present application.

[0106] As shown in Figure 2, the terminal device includes a main receiver (MR) and a low power wake-up receiver. The low power wake-up signal LP-WUS is used by the network device to instruct the terminal device whether to monitor the downlink control channel PDCCH. Before the terminal device monitors LP-WUS, the main receiver can be set to a dormant state and the low power wake-up receiver to an active state to monitor LP-WUS. If the low power wake-up receiver monitors LP-WUS, it can wake up the main receiver according to the LP-WUS instruction. In this way, the main receiver can be in a dormant state as much as possible, thereby reducing the power consumption of the terminal device.

[0107] In addition, in the related mechanism of the low power wake-up signal, a low power synchronization signal (LP-SS) may be set to wake up the receiver with low power consumption for synchronization and measurement.

[0108] Next, please refer to FIG3 , which is a schematic diagram of a discontinuous reception mechanism of a terminal device provided in an embodiment of the present application.

[0109] A discontinuous reception mechanism is configured for a terminal device in the connected state. A discontinuous reception cycle consists of an on-duration period. During the on-duration period, the terminal device monitors and receives information carried on the physical downlink control channel (PDCCH). Outside of the on-duration period, the terminal device is in a dormant state. As shown in Figure 3, the terminal device is in the active state during on-duration period T1.1 of the discontinuous reception cycle T2.1, monitoring the PDCCH.

[0110] When a terminal device receives scheduling information on the PDCCH during a continuous period, it starts a timer and monitors the PDCCH during the timer. As shown in Figure 3, assuming the terminal device receives the scheduling information at time t4 and the timer ends at time t5, the terminal device monitors the PDCCH from time t4 to t5. The terminal device is also in the active state during this period.

[0111] Next, please refer to FIG4 , which is a schematic diagram of a paging frame provided in an embodiment of the present application.

[0112] It is understood that a paging frame (PF) may be a radio frame, a paging cycle includes one or more PFs, and a PF may include one or more paging occasions (POs). The embodiment shown in FIG4 is an example of a PF including multiple POs.

[0113] For terminal devices, each terminal device is associated with one PO in a PF during a paging cycle. However, for a PO, the number of terminal devices associated with each PO may be more than one. The paging message on a PO may be targeted at some or all UEs associated with the PO.

[0114] The terminal device monitors the PDCCH on its corresponding PO and reads the terminal identification list corresponding to the paging message. If the terminal device is not in the terminal identification list, it indicates that the terminal device is not the target of the paging. In this case, it is meaningless for the terminal device to monitor the PDCCH or physical downlink shared channel (PDSCH), and the terminal device will discard the received paging message. This causes power consumption of the terminal device, which is also the problem to be solved by this application.

[0115] Below, the communication method provided in the embodiment of the present application is described in conjunction with a schematic diagram. Please refer to Figure 5, which is a flow chart of the communication method provided in the embodiment of the present application.

[0116] 501. The network device sends first information to the terminal device, where the first information is used to indicate a first LO where a target LP-WUS is located.

[0117] The network device can configure an LO for the terminal device, so that the terminal device determines when to monitor the LP-WUS based on the LO configuration information. In actual applications, the network device can configure one or more LOs for the terminal device. In this case, the network device needs to indicate the effective configuration information to synchronize the terminal device and the network device. Therefore, the network device sends first information to the terminal device. The first information indicates a first LO among the one or more LOs, that is, indicates that the configuration information of the effective LO is the configuration information of the first LO, so that the terminal device monitors the target LP-WUS on the first LO.

[0118] The amount of LO configuration information received by the terminal device is different, and the first information is slightly different, which are described below:

[0119] If the terminal device receives configuration information for only one LO, then that LO is the first LO, and the configuration information is also the configuration information of the first LO. In this solution, the first information can be multiple: Optionally, if the network device sends other signaling to enable or activate the UE monitoring LP-WUS function after sending the configuration information, then the signaling can be considered the first information. Optionally, if the network device does not send other enablement or activation signaling, then the configuration information can be considered the first information.

[0120] If the terminal device includes configuration information of multiple LOs, that is, the terminal device receives configuration information of multiple LOs before being enabled, then after enabling the terminal device, the network device sends first information to the terminal device, where the first information includes a configuration identifier of the first LO, so that the terminal device determines the configuration information of the first LO from the configuration information of the multiple LOs.

[0121] In the present application, a network device sends a first message to a terminal device, where the first message indicates a first LO where a target LP-WUS is located, so that the terminal device monitors the target LP-WUS at the first LO. For a terminal device in an idle or inactive state, the monitored target LP-WUS indicates whether the terminal device obtains a paging message at the corresponding PF or PO, thereby avoiding waking up the host during a period when it is not paged, thereby reducing the power consumption of the terminal device. For a terminal device in a connected state, the monitored target LP-WUS indicates whether the terminal device monitors the PDCCH at the corresponding time, thereby avoiding the terminal device monitoring the downlink channel when there is no information transmission on the downlink channel, thereby reducing the power consumption of the terminal device.

[0122] In some optional implementations, before step 501, the network device may further perform step 502. Send configuration information of at least one LO to the terminal device, where the configuration information of each LO is used to define the LO, and the configuration information of at least one LO includes configuration information of the first LO.

[0123] The configuration information for each LO includes at least one of the following: the relationship between the LO and LMO, the LO's time-domain configuration information, the LO's frequency-domain configuration information, or the LO's configuration identifier. This defines or describes the LO from multiple perspectives, making it easier for terminal devices to determine the LO based on the configuration information.

[0124] In addition, the network device configures one or more LOs for the terminal device, which can flexibly adapt to different scenario requirements. In different communication scenarios, the terminal device can monitor LP-WUS based on different LOs, thereby realizing monitoring of downlink signals, enriching the application scenarios and implementation methods of the technical solution of this application.

[0125] The following describes the contents of the configuration information of each LO.

[0126] In some optional implementations, the LO defined by the configuration information of each LO includes at least one LMO. For network devices, the LMO is used to send LP-WUS messages. For terminal devices, the LMO is used to monitor LP-WUS messages. In other words, when a terminal device monitors LP-WUS messages on the LO, it actually monitors LP-WUS messages on the LMO included in the LO.

[0127] Here, LO includes at least one LMO, which can be understood as LO being a time window within which there is at least one LMO, or as LO including at least one discrete LMO.

[0128] In this application, LO includes at least one LMO, which is used by the network device to send LP-WUS and by the terminal device to monitor LP-WUS, further refining the sending timing or monitoring timing of LP-WUS.

[0129] In some optional implementations, the configuration information for each LO further includes: the starting position and duration of each LMO included in each LO. The starting position of each LMO can be at the slot level or the symbol level; the duration of each LMO can also be at the slot level or the symbol level, which are not limited herein.

[0130] For example, the configuration information of a certain LO may include: the starting position of the first LMO is symbol 1, the duration of the first LMO is 2 symbols, the starting position of the second LMO is symbol 4, the duration of the second LMO is 2 symbols, the starting position of the third LMO is symbol 7, and the duration of the third LMO is 2 symbols.

[0131] In some optional implementations, the configuration information for each LO further includes: the starting position and duration of the first LMO in each LO, and the interval between LMOs included in each LO. The starting position, duration, and interval between LMOs of each LMO may be expressed in slots or symbols, which are not specifically limited herein.

[0132] Optionally, the duration of each LMO included in the LO may be the same. For example, the configuration information of a certain LO may include: the starting position of the first LMO is symbol 1, the duration of each LMO is 3 symbols, and the time interval between each LMO is 2 symbols.

[0133] Optionally, the duration of each LMO included in the LO may be different. In this case, the configuration information of each LO also needs to include the duration of each LMO.

[0134] Optionally, based on the above two examples, the configuration information of each LO may further include the number of LMOs included in each LO.

[0135] In some optional implementations, the configuration information of each LO further includes: the number of LMOs included in each LO, and the time interval between the LMOs included in each LO. In this solution, the time intervals between adjacent LMOs are set to be the same by default, and the time interval between the start moment of the LO and the first LMO is the same as the time interval between adjacent LMOs. Alternatively, the time intervals between adjacent LMOs are set to be the same by default, and the time interval between the start moment of the LO and the last LMO is the same as the time interval between adjacent LMOs. Alternatively, the time intervals between adjacent LMOs are set to be the same, and the start moment of the LO is the start moment of the first LMO. Alternatively, the time intervals between adjacent LMOs are set to be the same, and the end moment of the LO is the start moment of the last LMO.

[0136] In this application, the configuration information for each LO indicates the relationship between the LO and the LMO, allowing the terminal device to accurately locate the LMO. The LMO is used to send the LP-WUS. The terminal device's low-power receiver only needs to listen when the LMO is awake. During the LO's non-LMO period, it can be dormant, further reducing the terminal device's power consumption.

[0137] The previous section explains the relationship between LO and LMO. Next, we will explain the time domain configuration included in the LO configuration information. For terminal devices in different states, the time domain information of the LO configured by the network device is different, which is explained below.

[0138] 1. Time domain configuration when the terminal device is in idle or inactive state.

[0139] When the terminal device is in an idle state or an inactive state, the time domain information in the configuration information of each LO is associated with the paging message. In summary, the configuration information of each LO includes a first period and / or a first time domain parameter.

[0140] The first cycle can be configured as a first duration, or the first cycle is predefined, or the duration of the first cycle is the same as the duration of the PF paging cycle. Optionally, the first cycle can be predefined as a duration in milliseconds.

[0141] Optionally, the LO configuration information may include a first period. In this solution, the duration of the first period is the first duration. The value of the first duration can be set based on actual application requirements; it can also be set to a default value, which indicates that the first duration is the same as the duration of the paging cycle. The specific details are not limited here. The first duration can be configured as a duration at the millisecond (ms), slot level, or symbol level.

[0142] Optionally, the configuration information of the LO may not include the first cycle. In this solution, the duration of the first cycle is predefined or defaulted to be the same as the duration of the paging cycle.

[0143] The first time domain parameter includes a first time domain offset and a second time domain offset, or includes a third time domain offset and a second duration. The first time domain offset indicates the time offset between the start time of each LO and the PF or PO, the second time domain offset indicates the time offset between the end time of each LO and the PF or PO, and the third time domain offset indicates the time offset between the start time or end time of each LO and the PF or PO.

[0144] When the first time domain parameter includes a first time domain offset and a second time domain offset, the start time, end time, and duration of the LO can be determined based on the two time domain offsets, that is, the time domain resources used by the LO can be determined.

[0145] When the first time domain parameter includes the third time domain offset and the second duration, the start time or end time of the LO can be determined based on the third time domain offset. Combined with the second duration, the time domain resource used by the LO can be determined.

[0146] It should also be noted that the second duration, or LO duration, can be in milliseconds, slots, or symbols, and is not specifically limited here. The aforementioned time domain offsets can also be in milliseconds, slots, or symbols, and can be positive or negative, and are not specifically limited here.

[0147] In the embodiments of the present application, for terminal devices in an idle or inactive state, the time domain information in the configuration information of each LO configured by the network device is associated with the paging message and matched with the state of the terminal device, providing technical support for the implementation of the technical solution of the present application and enhancing the feasibility of the technical solution. Furthermore, multiple options are available when configuring the time domain information, enriching the implementation methods of the technical solution and improving its flexibility.

[0148] There are various possible associations between LO and PF or PO, which are illustrated below with reference to schematic diagrams. For example, Figures 6 and 7 are schematic diagrams of LO provided in embodiments of the present application. Figures 6 and 7 illustrate examples in which LO configuration information includes a third offset and a second duration.

[0149] In some optional implementations, one LO is associated with one PF. In this solution, one LO may include at least one set of LMOs, and one PF may include at least one PO. The at least one set of LMOs corresponds one-to-one with the at least one PO, or each set of LMOs is associated with each PO in sequence.

[0150] For example, as shown in Figure 6 (a), the LO includes two groups of LMOs, each group of LMOs includes four LMOs. The LO configuration information includes the time domain offset offset1 between the LO start time and the PF. The terminal device then determines the LO start time based on the PF start time and offset1. Combined with the second duration, the LO end time can be determined. The first group of LMOs is associated with PO1 in the PF, and these four LMOs correspond to the four beams of PO1. The second group of LMOs is associated with PO2 in the PF, and these four LMOs correspond to the four beams of PO2.

[0151] In some optional implementations, one LO is associated with one PO. In this solution, at least one LMO included in one LO is associated with the same PO.

[0152] For example, as shown in Figure 6(b), the configuration information for LO1 includes a time domain offset, offset1, between the start time of LO1 and the start time of PO1. The terminal device then determines the start time of LO based on the start time of PO1 and offset1. Combined with the second duration, the end time of LO1 can be determined. The configuration information for LO2 includes a time domain offset, offset2, between the start time of LO2 and the start time of PO2. The terminal device then determines the start time of LO2 based on the start time of PO2 and offset1. Combined with the second duration, the end time of LO2 can be determined. The four LMOs included in LO1 are all associated with PO1, and the four LMOs included in LO2 are all associated with PO2.

[0153] In some optional implementations, one LO is associated with multiple PFs. In this solution, one LO may include at least one set of LMOs, which correspond one-to-one with the POs in at least one PF, or each set of LMOs is sequentially associated with the POs of each PF.

[0154] For example, as shown in Figure 7(a), the LO includes four groups of LMOs, each group of LMOs including four LMOs. The LO configuration information includes the LO start time and the time domain offset of PF1, offset1. The terminal device then determines the LO start time based on the PF1 start time and offset1. Combined with the second duration, the end time of LO1 can be determined. Furthermore, PF1 and PF2 each include two POs. In the embodiment shown in Figure 7(a), the first and second groups of LMOs are associated with PF1. Specifically, the first group of LMOs is associated with PO1 in PF1, and the second group of LMOs is associated with PO2 in PF1. The third and fourth groups of LMOs are associated with PF2. Specifically, the third group of LMOs is associated with PO3 in PF2, and the fourth group of LMOs is associated with PO4 in PF2.

[0155] In some optional implementations, one LO is associated with multiple POs. In this solution, one LO may include at least one set of LMOs, which correspond one-to-one with at least one PO, or in other words, each set of LMOs is sequentially associated with POs in consecutive PFs.

[0156] For example, as shown in Figure 7(b), the LO includes four groups of LMOs, each group of LMOs including four LMOs. The LO configuration information includes the LO start time and the time domain offset (offset1) of PO1. The terminal device then determines the LO start time based on the PO1 start time and offset1. Combined with the second duration, the LO end time can be determined. In the embodiment shown in Figure 7(b), the LO is associated with PO1 to PO4. Specifically, the first group of LMOs is associated with PO1, the second group of LMOs is associated with PO2, the third group of LMOs is associated with PO3 in PF2, and the fourth group of LMOs is associated with PO4 in PF2.

[0157] In some optional implementations, multiple LOs may be associated with one PF, or multiple LOs may be associated with one PO. The specific configuration may be based on communication requirements and is not limited here.

[0158] It should be noted that the aforementioned association between LMO and PO refers to the timing of the LP-WUS detected by the LMO as indicated by the associated PO. For example, assuming LMO1 is associated with PO1, the LP-WUS sent by the network device at LMO1, or the LP-WUS received by the terminal device at LMO1, indicates the timing of LO1.

[0159] It should be noted that the embodiments shown in Figures 6 and 7 are based on an example in which a group of LMOs includes 4 LMOs and a PF includes 2 POs. In actual applications, a group of LMOs may also include a larger or smaller number of LMOs, and a PF may also include a larger or smaller number of POs. The specifics are not limited here.

[0160] For terminal devices in an idle or inactive state, the LP-WUS signal sent on the LMO has multiple ways to indicate the paged terminal device, which are explained below in conjunction with Figures 8 and 9, respectively. Figures 8 and 9 are both schematic diagrams of the LO provided in embodiments of the present application.

[0161] In some optional embodiments, each LMO included in the LO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a bitmap of paging packets. Therefore, when monitoring the LMO, the terminal device determines whether the terminal device is being paged based on the paging packet of the terminal device, the beam corresponding to the LMO, and the paging packet indicated by the LP-WUS on the LMO.

[0162] Furthermore, for idle or inactive devices, the network device does not know which beam they are in when paging them, so it pages them in every beam. When a device is monitoring LMO, it selects the beam with the strongest signal.

[0163] For example, assume that the terminal device corresponds to PO1 and the paging group the terminal device is in is paging group 1. In the embodiment shown in Figure 8, LMO1 and LMO2 correspond to PO1. This means that the terminal device detects the LP-WUS on LMO1 and LMO2. The bitmap of the paging group indicated by the LP-WUS corresponding to LMO1 and LMO2 is 11000000, representing paging group 1 and paging group 2. The terminal device then monitors the LP-WUS on LMO1 and LMO2, determines based on the bitmap that the group the terminal device is in is being paged, and wakes up the main receiver at PO1 based on the LP-WUS indication, monitors the PDCCH, and parses the corresponding paging message. It should also be noted that Figure 8 uses two beams as an example. In actual applications, a greater or fewer number of beams may be included, and this is not limited here. Figure 8 uses an 8-bit bitmap length, meaning a maximum of eight paging groups. In actual applications, the bitmap may be longer or shorter, and the number of paging groups may be greater or fewer, and this is not limited here.

[0164] Optionally, in the implementation shown in Figure 8, LMO3 and LMO4 can be associated with PO1. LMO3 and LMO4 indicate the same information as LMO1 and LMO2, respectively, and can be understood as duplications of LMO1 and LMO2, respectively. This configuration takes into account the large amount of information carried by each LMO, which can lead to errors during parsing. The duplication allows for verification and enhances the reliability of the technical solution.

[0165] In some optional implementations, each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a paging packet. Then, when the terminal device monitors the LMO, it determines whether the terminal device is paged based on the paging packet of the terminal device and the above information.

[0166] For example, assume that the terminal device corresponds to PO1, and the paging group in which the terminal device is located is paging group 1. In the embodiment shown in Figure 9, the paging group indicated by the LP-WUS corresponding to LMO1 is group 1, and the paging group indicated by the LP-WUS corresponding to LMO2 is group 2, and both LMO1 and LMO2 correspond to beam 1. Then, the terminal device monitors the LP-WUS on LMO1, determines that the terminal device is paged based on the group value, and can wake up the main receiver at PO1 based on the indication of the LP-WUS, monitor the PDCCH and parse the corresponding paging message.

[0167] In some optional implementations, the terminal device determines the LP-WUS monitored in a certain LMO, that is, determines that the LP-WUS corresponding to a certain LMO indicates the group to which the terminal device belongs. Then, the terminal device may no longer monitor the LP-WUS in subsequent LMOs, further reducing the power consumption of the terminal device.

[0168] In some optional implementations, if the paging packets corresponding to the LP-WUS monitored by the terminal device at each LMO do not include the packet in which the terminal device is located, then it means that the terminal device has not been paged. The PO corresponding to the terminal device does not wake up the main receiver.

[0169] Based on the foregoing description, it can be seen that in the embodiment of the present application, there are multiple possibilities for the information indicated by the LP-WUS corresponding to each LMO, which enriches the implementation methods and application scenarios of the technical solution of the present application.

[0170] 2. Time domain configuration when the terminal device is in a connected state.

[0171] When the terminal device is in a connected state, the configuration information of each LO includes a second period and / or a second time domain parameter. The configuration information of each LO may be associated with the discontinuous reception (DRX) of the terminal device in the connected state, or may not be associated with CDRX. The following are respectively described:

[0172] 1) LO configuration information is associated with CDRX.

[0173] In this solution, the configuration information of each LO includes a second period and / or a second time domain parameter.

[0174] The second period may be positioned as the third duration, or the duration of the second period may be predefined, or the duration of the second period may be the same as the duration of the CDRX period. Optionally, the second period may be predefined as a duration in milliseconds.

[0175] Optionally, the LO configuration information may include a second period. In this solution, the duration of the second period is the third period. The value of the third period can be set based on actual application requirements or set to a default value, indicating that the third period is the same as the duration of the CDRX period, which is not specifically defined herein. The third period can be expressed in units of milliseconds, slots, or symbols, which are not specifically defined herein.

[0176] Optionally, the configuration information of the LO may not include the second period. In this solution, the duration of the second period is predefined or defaulted to be the same as the duration of the CDRX period.

[0177] The second time domain parameters include a fourth time domain offset and a fifth time domain offset, or a sixth time domain offset and a fourth duration, wherein the fourth time domain offset indicates the time offset between the start time of each LO and the start symbol of CDRX, the fifth time domain offset indicates the time offset between the end time of each LO and the start symbol of CDRX, and the sixth time domain offset indicates the time offset between the start time or end time of each LO and the start symbol of CDRX.

[0178] When the second time domain parameters include the fourth time domain offset and the fifth time domain offset, the start time, end time, and duration of the LO can be determined based on these two time domain offsets, that is, the time domain resources used by the LO can be determined.

[0179] When the second time domain parameters include the sixth time domain offset and the fourth duration, the start time or end time of the LO can be determined based on the sixth time domain offset. Combined with the fourth duration, the time domain resources used by the LO can be determined.

[0180] It should also be noted that the fourth duration, or the duration of the LO, can be expressed in units of milliseconds, slots, or symbols, without specific limitations. The aforementioned time domain offsets can also be expressed in units of milliseconds, slots, or symbols, and can be positive or negative, without specific limitations.

[0181] In an embodiment of the present application, for a terminal device in a connected state, the time domain information in the configuration information of each LO configured by the network device can be associated with CDRX and matched with the state of the terminal device, providing technical support for the implementation of the technical solution of the present application and enhancing the feasibility of the technical solution.

[0182] 2) LO configuration information is not associated with CDRX.

[0183] In some optional implementations, the configuration information of the LO may include the start time of the LO, which means that the LO is a continuous period, and the terminal device continuously monitors the LO from the start time of the LO.

[0184] In some optional implementations, the LO configuration information may include the LO start time and period. This means that the terminal device periodically monitors the LO. The LO period may be predefined or set based on actual application needs, and is not specifically limited here.

[0185] At the same time, there are multiple options when configuring time domain information, which enriches the implementation methods of the technical solution and improves the flexibility of the technical solution.

[0186] In some optional implementations, for a terminal device in a connected state, if the LO configuration information is associated with CDRX, or if the LO configuration information is not associated with CDRX but the LO configuration information includes the LO period, then each LO may include one or more LMOs, and in the LO configuration information, the LP-WUS corresponding to each LMO indicates at least one terminal identifier. Then, when monitoring the LMO, the terminal device determines whether to monitor the PDCCH at the timing corresponding to the LP-WUS based on the terminal device identifier and the at least one terminal identifier indicated by the LP-WUS on the LMO.

[0187] Among them, monitoring PDCCH at the time corresponding to LP-WUS can be monitoring PDCCH immediately at the end time of LO or LMO where LP-WUS is located; or monitoring PDCCH after a certain time period after the end time of LO or LMO where LP-WUS is located.

[0188] For example, please refer to Figure 10, which is a schematic diagram of the LO provided in an embodiment of the present application. Figure 10 takes the association between the configuration information of the LO and the CDRX as an example.

[0189] In the embodiment shown in Figure 10, CDRX represents discontinuous reception of a terminal device in a connected state, and on duration represents a duration. The terminal identifier indicated by the LP-WUS corresponding to LMO1 is UE ID1, and the terminal identifier indicated by the LP-WUS corresponding to LMO2 is UE ID2. Assuming that the terminal device identifier is UE ID1 and the terminal device monitors the LP-WUS on LMO1, and the terminal identifier indicated by the LP-WUS is also UE ID1, then the terminal device wakes up the main receiver and monitors the PDCCH for a duration based on the LP-WUS instruction.

[0190] In some optional implementations, for the LO configured for the terminal device in the connected state, each LMO may also correspond to a beam.

[0191] In the above description, the time domain configuration in the configuration information of each LO is introduced. In actual application, other information of each LO can also be configured, which is explained below.

[0192] In some optional embodiments, the LO configuration information may further include a LO monitoring mode, which may include continuous monitoring or duty-cycled monitoring. Continuous monitoring means that the low-power wake-up receiver of the terminal device continuously monitors the LO from the start of the LO. Duty-cycled monitoring means that the low-power wake-up receiver of the terminal device discretely monitors the LP-WUS within the LO.

[0193] For example, in a duty cycle monitoring solution, each LMO is monitored within the LO, which is one implementation of the duty cycle monitoring.

[0194] In some optional implementations, the configuration information of each LO further includes frequency domain configuration information of the LO, which is used to indicate the frequency domain resources used by each LO.

[0195] Optionally, the frequency domain configuration information of each LO includes the frequency domain starting position and the first bandwidth of each LO, or includes the frequency domain starting position of each LO. In the latter solution, the first bandwidth can be considered as a preset value. The frequency domain starting position can be represented by an index value of a resource block (RB) or a resource element (RE), that is, the frequency domain starting position includes RB_index or RE_index.

[0196] Optionally, the frequency domain configuration information for each LO includes a frequency domain offset and a second bandwidth for each LO, or alternatively, includes a frequency domain offset for each LO. In the latter scenario, the second bandwidth can be considered a preset value. The frequency domain offset indicates the frequency offset between each LO and the SSB, or the frequency offset between each LO and point A. The frequency domain offset can be expressed in RBs or REs, and can be positive or negative, with no specific limitation here.

[0197] In addition, the first bandwidth and the second bandwidth can also be set according to the needs of actual applications. For example, they can be set to a specific bandwidth amount, such as 5M or 20M; or, they can be set to the number of RBs included, or the number of REs, which is not specifically limited here.

[0198] In the embodiments of the present application, there are multiple ways to set the frequency domain information of each LO, which enriches the implementation methods and application scenarios of the technical solution of the present application and improves the flexibility of the technical solution.

[0199] In some optional implementations, the configuration information for each LO also includes a configuration identifier for each LO. A configuration identifier uniquely identifies a LO configuration. For example, if a network device configures three LOs for a terminal device, the configuration identifiers of these three LOs are LO config1, LO config2, and LO config3, respectively, to distinguish between the different LOs. If multiple LOs are configured, the LO configuration identifiers can be used to identify the corresponding LO. Regarding step 501 above, if the terminal device receives the configuration information for multiple LOs and then receives the first information, the first information also includes the configuration identifier of the first LO to identify the first LO.

[0200] In the embodiment of the present application, when multiple LOs are configured, the effective LO can be uniquely indicated by the configuration identifier, thereby avoiding errors caused by unclear indications and improving the reliability of the technical solution.

[0201] In some optional implementations, the message carrying configuration information of at least one LO includes: a SIB message or an RRC message. Exemplarily, a SIB message can carry configuration information of one LO, and an RRC message can carry configuration information of one or more LOs.

[0202] In the embodiment of the present application, there are multiple possibilities for messages carrying configuration information of at least one LO, which can be flexibly selected based on the needs of actual applications, enriching the implementation methods of the technical solutions of the present application.

[0203] In some optional implementations, for a terminal device in an idle or inactive state, the message carrying the first information includes an RRC release message or a group common DCI message. For a terminal device in a connected state, the message carrying the first information includes: an RRC message, a DCI message, or a MAC-CE message.

[0204] In the embodiment of the present application, the message type carrying the first information varies with the status of the terminal device, matching the status of the terminal device, thereby enhancing the feasibility of the technical solution of the present application.

[0205] In some optional implementations, the network device may also send LO configuration information based on the BWP. A BWP includes configuration information for one or more LOs. For different scenarios, the network device may indicate the first LO in different ways.

[0206] In a solution where a BWP includes configuration information of a LO, switching the BWP by the network device also means switching the configuration information of the LO, instructing the terminal device to use the configuration of the LO included in the switched BWP. Then, for step 501, the first information can be carried in the message of switching the BWP.

[0207] In scenarios where a BWP includes configuration information for multiple LOs, switching the BWP by the network device means that the LO configuration indicated to the terminal device is the configuration of a specific LO included in the switched BWP. Since the switched BWP includes configurations for multiple LOs, the network device can also indicate the LO configuration to the terminal device.

[0208] Optionally, the network device may send information indicating the configuration of the LO to the terminal device when switching the BWP or after switching the BWP. Exemplarily, after switching the BWP, the network device may send first information to the terminal device, where the first information includes a configuration identifier of the first LO and instructs the terminal device to use the configuration information of the first LO.

[0209] Alternatively, the network device may not indicate the configuration of a specific LO. In this case, switching the BWP means using the default LO configuration included in the switched BWP. For example, assume that BWP1 includes LO1 configuration information, and BWP2 includes LO2 and LO3 configuration information, with the default configuration being LO2. If the network device switches from BWP1 to BWP2 and does not indicate any LO configuration information, the terminal device defaults to LO2 configuration information and monitors the LP-WUS based on LO2 configuration.

[0210] In the embodiment of the present application, there are multiple possible ways to switch the BWP. The switching instruction can include RRC signaling, timer, or DCI implementation. The specific implementation method is similar to the related technical solution and will not be repeated here. The difference is that in the embodiment of the present application, when switching the BWP, the configuration information of the target LO included in the switched BWP may also be synchronously instructed to use. Specifically, the configuration identifier of the target LO can be carried in the switching instruction.

[0211] In the embodiment of the present application, there are multiple possible amounts of configuration information of LOs included in a BWP, which enriches the implementation methods and application scenarios of the technical solution of the present application.

[0212] In some optional implementations, the terminal device may further perform step 503 , monitoring the target LP-WUS at the first LO according to the first information.

[0213] The first information indicates a first LO, so that the terminal device monitors the target LP-WUS on the first LO.

[0214] If the terminal device is in an idle state or an inactive state, the target LP-WUS is associated with the PF or PO. After the terminal device monitors the target LP-WUS, it determines to monitor the paging message on the PF or PO corresponding to the target LP-WUS based on the indication of the target LP-WUS. If the target LP-WUS indicates that the terminal device is paged, the terminal device wakes up the main receiver on the corresponding PF or PO and monitors the paging message. If the target LP-WUS indicates that the terminal device is not paged, the terminal device does not wake up the main receiver on the corresponding PF or PO, thereby reducing the power consumption of the terminal device. The specific implementation process is similar to the embodiment shown in Figure 8 above. Please see the previous text for details and will not be repeated here.

[0215] If the terminal device is in a connected state, the target LP-WUS can correspond to the target duration in CDRX. After monitoring the target LP-WUS, the terminal device determines whether to wake up the primary receiver and monitor the PDCCH during the target duration corresponding to the target LP-WUS based on the target LP-WUS indication. If the target LP-WUS indicates not to monitor the PDCCH, the terminal device's primary receiver will not be woken up, reducing the terminal device's power consumption. The specific implementation process is similar to the embodiment shown in Figure 9 above, as detailed above, and will not be repeated here.

[0216] If the terminal device is in a connected state, the target LP-WUS may not be associated with the CDRX. In this solution, the terminal device determines whether to monitor the PDCCH based on the indication of the target LP-WUS. If the terminal identifier indicated by the target LP-WUS includes the identifier of the terminal device, the terminal device monitors the PDCCH at the time indicated by the target LP-WUS. If the terminal identifier indicated by the target LP-WUS does not include the identifier of the terminal device, the terminal device does not wake up the terminal device's main receiver and does not monitor the PDCCH at the time indicated by the target LP-WUS.

[0217] In the embodiment of the present application, the signals related to the low-power wake-up mechanism can also be associated with the BBS, which is explained below.

[0218] Please refer to Figure 11, which is a flow chart of the communication method provided in an embodiment of the present application.

[0219] 1101. The network device sends second information to the terminal device, where the second information indicates first configuration information of a first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB.

[0220] The first signal includes LP-WUS or LP-SS. LP-WUS is used to indicate the timing for the terminal device to wake up the main receiver to monitor the signal carried on the downlink channel. LP-SS is used for synchronization and measurement of the low-power wake-up receiver of the terminal device.

[0221] Optionally, the second information includes an identifier of the first configuration information, so that the terminal device can determine the first configuration information from at least one set of configuration information of the first signal according to the identifier.

[0222] The first signal is associated with the SSB, which means that the configuration information of the first signal is associated with the configuration information of the SSB. Optionally, in the case of high load of the network device, energy saving of the network device may not be considered. Then, in the time domain resources, the first signal may use the symbols not used by SSB in the synchronization signal / physical broadcast channel block measurement timing configuration (SS / PBCH block measurement timing configuration, SMTC). In the case of low load of the network device, considering the energy saving of the network device, in the time domain resources, the same symbols as SSB are used, and frequency-division multiplexing (FDM) is used with SSB in the frequency domain resources. The specific configuration method is described below and will not be expanded here.

[0223] In this application, the second information sent by the network device to the terminal device indicates the configuration information of LP-WUS or LP-SS, so that the terminal device determines whether to wake up the main receiver to monitor the downlink signal during a specified period based on LP-WUS. Alternatively, the terminal device synchronizes and measures the low-power wake-up receiver based on LP-SS to ensure the normal operation of the low-power wake-up receiver, thereby improving the accuracy of the solution.

[0224] In some optional implementations, the type of message carrying the second information varies depending on the state of the terminal device. Optionally, in a scenario where the terminal device is in an idle or inactive state, the message carrying the second information includes: an RRC release message, or a group common DCI message. In a scenario where the terminal device is in a connected state, the message carrying the second information includes: an RRC message, a DCI message, or a MAC-CE message.

[0225] In the embodiment of the present application, the message type carrying the first information varies with the status of the terminal device, matching the status of the terminal device, thereby enhancing the feasibility of the technical solution of the present application.

[0226] In some optional implementations, before step 1101, the network device may further perform step 1102. Send at least one set of configuration information of a first signal to the terminal device, where the at least one set of configuration information includes the first configuration information.

[0227] In an embodiment of the present application, the network device can configure multiple sets of first signal configuration information for the terminal device. When using a certain set of configurations, it only needs to send information indicating a certain set of configurations to the terminal device, thereby flexibly adapting to different scenario requirements and improving the flexibility of the technical solution of the present application.

[0228] As used herein, "at least one set of configuration information for a first signal" and "at least one set of configuration information for the first signal" have the same meaning, indicating one or more sets of configuration information for the first signal. Each set of configuration information includes at least one of the time domain configuration, frequency domain configuration, or configuration identifier of the first signal, each of which is described below.

[0229] In some optional embodiments, each set of configuration information in at least one set of configuration information includes time domain configuration information of the first signal, and the time domain configuration information includes: the time domain offset between the time domain starting position of the first signal and the starting position of the SSB, and / or the duration of the first signal.

[0230] The time domain offset can be positive or negative, or 0, and its unit can be symbol. A time domain offset of 0 indicates that the time domain starting position of the first signal is the same as the starting position of the SSB. The duration of the first signal can be determined based on the needs of the actual service scenario, or it can be predefined as a fixed duration, for example, predefined as 2 symbols.

[0231] Optionally, in a solution in which the duration of the first signal is predefined, the duration of the first signal may no longer be configured in the configuration information of the first signal, thereby reducing the amount of data transmitted between the network device and the terminal device.

[0232] In some optional implementations, each set of configuration information in the at least one set of configuration information includes frequency domain configuration information of the first signal, and the frequency domain configuration information includes: a frequency domain offset of the first signal and / or a bandwidth of the first signal.

[0233] Among them, the frequency domain offset of the first signal indicates the frequency offset between the frequency domain starting position of the first signal and the SSB, or indicates the frequency offset between the frequency domain starting position of the first signal and pointA. The value of the frequency domain offset can be positive or negative, or 0, and its unit can be RB or RE. A frequency domain offset of 0 indicates that the frequency domain starting position of the first signal is the same as the SSB or pointA. The bandwidth of the first signal can be set based on the needs of the actual business scenario, or it can be predefined as a fixed bandwidth, and its unit can be RB or RE, which is not limited here.

[0234] Optionally, in a solution where the bandwidth of the first signal is predefined, the bandwidth of the first signal may no longer be configured in the configuration information of the first signal, thereby reducing the amount of data transmitted between the network device and the terminal device.

[0235] In some optional implementations, each set of configuration information in the at least one set of configuration information includes a configuration identifier and a period of the first signal, wherein the period of the first signal can be understood as including time domain configuration information of the first signal.

[0236] The configuration identifier of the first signal uniquely indicates a set of configuration information. The period of the first signal can be defined as a duration, such as 320ms or 640ms, based on the needs of the actual business scenario. It can also be predefined as a fixed duration. In addition, it can also be defined in other ways, such as defining the relationship between the period of the first signal and the SSB period.

[0237] For example, considering that the SSB signal period is short and the first signal does not need to be sent frequently, the period of the first signal can be defined as N times the SSB period, where N is greater than 1. Alternatively, the SSB period can be defined as M times the period of the first signal, where M is less than 1.

[0238] Optionally, in a solution in which the period of the first signal is predefined, the period of the first signal may no longer be configured in the configuration information of the first signal, thereby reducing the amount of data transmitted between the network device and the terminal device.

[0239] In some optional embodiments, the time domain starting position of the first signal may not be configured in the configuration information of the first signal, or the time domain starting position of the first signal may be empty, which means that the time domain starting position of the first signal is the same as the starting position of the SSB.

[0240] In some optional embodiments, the frequency domain starting position of the first signal may not be configured in the configuration information of the first signal, or the frequency domain starting position of the first signal may be empty, which means that the frequency domain starting position of the first signal is the same as the position of the SSB.

[0241] For example, in a scenario where the network device is under low load, the time domain resources of the first signal may be the same as those of SSB. Then the configuration information of the first signal may not include the time domain resources of the first signal, but may only include the frequency domain configuration information and configuration identifier of the first signal.

[0242] In the embodiment of the present application, the time domain configuration and frequency domain configuration included in each set of configuration information of the first signal have multiple possible situations, can flexibly adapt to different scenarios, and enrich the implementation method of the technical solution of the present application.

[0243] In some optional implementations, the message carrying at least one set of configuration information for the first signal may include a SIB message or an RRC message. Optionally, a SIB message may include a set of configuration information for the first signal, and a RRC message may include one or more sets of configuration information for the first signal.

[0244] In the embodiment of the present application, there are multiple possibilities for the message carrying at least one set of configuration information of the first signal, which can be flexibly selected based on the needs of actual application, enriching the implementation method of the technical solution of the present application.

[0245] In some optional implementations, after step 1101, the terminal device may further perform step 1103. Based on the second information, monitor the first signal.

[0246] The terminal device obtains the second information, and thus obtains the first configuration information of the first signal. Based on the first configuration information, the terminal device can determine the time domain resources, frequency domain resources, etc. used by the first signal, thereby determining the timing of monitoring the first signal.

[0247] In some optional implementations, if the first signal includes an LP-WUS, the terminal device determines, based on an indication of the LP-WUS, whether to monitor the PDCCH at a time corresponding to the LP-WUS.

[0248] Optionally, for a terminal device in an idle or inactive state, if the terminal identifier indicated by the LP-WUS includes the identifier of the terminal device, the terminal device monitors the PDCCH and parses the paging message at the timing corresponding to the LP-WUS. If the terminal identifier indicated by the LP-WUS does not include the identifier of the terminal device, the main receiver of the terminal device will not be awakened at the timing corresponding to the LP-WUS, thereby reducing the power consumption of the terminal device.

[0249] Optionally, for a terminal device in a connected state, if the terminal identifier indicated by the LP-WUS includes the identifier of the terminal device, then the terminal device monitors the PDCCH at the timing corresponding to the LP-WUS. If the terminal identifier indicated by the LP-WUS does not include the identifier of the terminal device, then the main receiver of the terminal device will not be awakened at the timing corresponding to the LP-WUS, thereby reducing the power consumption of the terminal device.

[0250] In some optional embodiments, if the first signal includes LP-WUS, the terminal device synchronizes and measures the low power wake-up receiver based on LP-SS based on the indication of LP-WUS, thereby ensuring the normal operation of the low power wake-up receiver.

[0251] In the embodiment shown in FIG11 , the first signal is associated with SSB. In practical applications, the first signal may also be associated with SIB1. This solution is described below.

[0252] Please refer to Figure 12, which is a flow chart of the communication method provided in an embodiment of the present application.

[0253] 1201. The network device sends a MIB message to the terminal device, where the MIB message includes a first field for determining a subcarrier offset and a second field for indicating a position of SIB1.

[0254] The MIB message includes a first field (ssb-subcarrier Offset) and a second field (pdcch-config SIB). The first field is used to determine the subcarrier offset, and the second field is used to indicate the position of SIB1.

[0255] Different subcarrier offsets are defined differently in different communication scenarios. For frequency bands below 6 GHz, the subcarrier offset is expressed as FR1Kssb; for 5G millimeter wave bands, the subcarrier offset is expressed as FR2Kssb.

[0256] 1202. The subcarrier offset is a preset value, and a first signal is sent to the terminal device based on the communication resources of SIB1. The first signal includes LP-WUS or LP-SS.

[0257] In existing technical solutions, FR1Kssb=30 or FR2Kssb=14, determined based on the first domain, indicates a reserved field with no clear meaning. In the embodiments of the present application, these two values ​​are given new meanings. Specifically, when the subcarrier offset determined based on the first domain is a preset value, it indicates that the network device sends a first signal to the terminal device based on the communication resources of SIB1.

[0258] That is to say, when FR1Kssb=30 or FR2Kssb=14 is determined based on the first field in the MIB message, it means that the network device has sent a first signal to the terminal device, and the resources used by the first signal are the communication resources of SIB1, including the time domain resources and frequency domain resources of SIB1.

[0259] Based on the second field in the MIB message, the terminal device determines the communication resource of SIB1 and monitors the first signal on the resource. If the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on LP-SS. If the first signal includes LP-WUS, the terminal device determines whether to monitor the downlink channel during the time period specified by LP-WUS based on LP-WUS, thereby reducing the power consumption of the terminal device. The specific implementation method is similar to the embodiment shown in Figure 11. Please refer to the relevant description above and will not be repeated here.

[0260] In the implementation of this application, a network device may define a new meaning for the subcarrier offset determined based on the first field in the MIB message to enable transmission of the first signal. A new method for indicating the communication resources used when transmitting the first signal is provided, so that a terminal device can monitor the first signal based on the MIB message.

[0261] In some optional implementations, in addition to the embodiment shown in FIG. 11 , the first signal may be associated with an SSB and a resource block group (RBG) related to the SSB, which will be described in detail below.

[0262] As shown in Table 1 below, the corresponding relationship between the number of RBs included in a BWP and the resource block granularity is defined:

[0263] Table 1

[0264] As shown in Table 1, for BWPs containing 1-36 RBs, the RGB granularity used is 2 RBs or 4 RBs. For BWPs containing 37-72 RBs, the RGB granularity used is 4 RBs or 8 RBs. For BWPs containing 73-144 RBs, the RGB granularity used is 8 RBs or 16 RBs. For BWPs containing 145-275 RBs, the RGB granularity used is 16 RBs.

[0265] If SSB is scheduled according to RGB, the number of RBs occupied by SSB may be less than the number of RBs included in the scheduled RGB due to the size of the RBG, resulting in idle RBs. In this embodiment of the present application, a first signal is sent based on the resources of the idle RBs, and the first signal includes LP-WUS or LP-SS.

[0266] For example, assume a 100 Mbps bandwidth, including 273 RBs, which falls within the range of interval 4 in Table 1. Within this range, each RGB consists of 16 RBs. If an SSB occupies 20 RBs, then sending this SSB requires scheduling two RGBs, occupying a total of 32 RBs. Of these 32 RBs, 20 are used to send the SSB, leaving 12 idle. The network device can use these 12 RBs to send the first signal.

[0267] In an embodiment of the present application, in a scheme based on RGB scheduling SSB, the network device can use the idle RB in RGB to send the first signal, saving resources used for signal transmission between the network device and the terminal device. In addition, the terminal device receives the first signal. If the first signal includes LP-SS, the terminal device synchronizes and measures the low-power wake-up receiver based on LP-SS. If the first signal includes LP-WUS, the terminal device determines whether to monitor the downlink channel during the time period specified by LP-WUS based on LP-WUS, thereby reducing the power consumption of the terminal device. The specific implementation method is similar to the embodiment shown in Figure 11. Please refer to the relevant description above and will not be repeated here.

[0268] Below, the relevant equipment provided in the embodiments of the present application is described.

[0269] The present application provides a communication device that can implement the functions of a network device or a terminal device in any of the aforementioned embodiments. The device includes corresponding units or modules for executing the above-mentioned method. The units or modules included in the device can be implemented by software and / or hardware. The device can be, for example, a terminal device, or a module (such as a chip) of a terminal device, or a logical node, logical module, or software that can implement all or part of the functions of the terminal device, and the specific details are not limited here.

[0270] Please refer to Figures 13 and 14. Figure 13 is a schematic diagram of the structure of a network device provided in an embodiment of the present application, and Figure 14 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in Figure 13, network device 1300 includes a transceiver unit 1301. As shown in Figure 14, terminal device 1400 includes a transceiver unit 1401 and a processing unit 1402.

[0271] In some optional implementations, the network device 1300 is configured to implement the operations performed by the network device in the embodiments shown in FIG. 5 to FIG. 10 , and the terminal device is configured to implement the operations performed by the terminal device in the embodiments shown in FIG. 5 to FIG. 10 . In summary, the operations include the following:

[0272] In some optional implementations, the transceiver unit 1301 is configured to send first information to the terminal device 1400 , where the first information is used to indicate a first LO where the target LP-WUS is located, so that the terminal device monitors the target LP-WUS at the first LO.

[0273] In some optional implementations, the transceiver unit 1301 is further configured to send configuration information of at least one LO to the terminal device 1400 , where the configuration information of each LO is used to define the LO, and the configuration information of at least one LO includes configuration information of the first LO.

[0274] In some optional implementations, the transceiver unit 1401 is configured to receive first information from the network device 1300, where the first information indicates a first LO where the target LP-WUS is located. The processing unit 1402 is configured to monitor the target LP-WUS at the first LO based on the first information.

[0275] In some optional implementations, the transceiver unit 1401 is further configured to receive configuration information of at least one LO from the network device 1300 , where the configuration information of each LO is used to define the LO, and the configuration information of at least one LO includes configuration information of the first LO.

[0276] In some optional implementations, the LO defined by the configuration information of each LO includes at least one LMO. For the network device 1300, the LMO is used to send the LP-WUS. For the terminal device 1400, the LMO is used to monitor the LP-WUS.

[0277] In some optional implementations, the processing unit 1402 is further configured to determine, based on the target LP-WUS, whether the terminal device 1400 monitors a paging message of a PF or PO corresponding to the target LP-WUS when the terminal device 1400 is in an idle state or an inactive state.

[0278] In some optional implementations, the processing unit 1402 is further configured to determine, based on the target LP-WUS, whether the terminal device 1400 monitors the PDCCH when in the connected state.

[0279] In some optional implementations, if the terminal device 1400 is in an idle state or an inactive state, the configuration information of each LO includes a first period and / or a first time domain parameter.

[0280] The first cycle corresponds to a first duration, or the duration of the first cycle is predefined, or the duration of the first cycle is the same as the duration of the paging cycle.

[0281] The first time domain parameter includes a first time domain offset and a second time domain offset, or includes a third time domain offset and a first duration. The first time domain offset indicates the time offset between the start time of each LO and the PF or PO, the second time domain offset indicates the time offset between the end time of each LO and the PF or the PO, and the third time domain offset indicates the time offset between the start time or end time of each LO and the PF or the PO.

[0282] In some optional implementations, each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a bitmap of a paging packet.

[0283] In some optional implementations, each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a paging packet.

[0284] In some optional implementations, if the terminal device 1400 is in an idle state or an inactive state, the message carrying the first information includes: an RRC release message, or a group common DCI message.

[0285] In some optional implementations, if the terminal device 1400 is in a connected state, the configuration information of each LO includes a second period and / or a second time domain parameter.

[0286] The second period corresponds to the third duration, or the duration of the second period is predefined, or the duration of the second period is the same as the duration of the CDRX period.

[0287] The second time domain parameter includes a fourth time domain offset and a fifth time domain offset, or includes a sixth time domain offset and a fourth duration. The fourth time domain offset indicates a time offset between the start time of each LO and the start symbol of the DRX of the terminal device, the fifth time domain offset indicates a time offset between the end time of each LO and the start symbol of the DRX of the terminal device, and the sixth time domain offset indicates a time offset between the start time or end time of each LO and the start symbol of the DRX of the terminal device.

[0288] In some optional implementations, the LP-WUS corresponding to each LMO indicates at least one terminal identifier.

[0289] In some optional implementations, if the terminal device 1400 is in a connected state, the first information carried includes: an RRC message, a DCI message, or a MAC-CE message.

[0290] In some optional implementations, the configuration information of each LO further includes a monitoring mode of each LO, where the monitoring mode includes duty cycle monitoring or continuous monitoring.

[0291] In some optional implementations, the configuration information for each LO further includes: the starting position and duration of each LMO included in each LO. Alternatively, the configuration information further includes: the starting position and duration of the first LMO in each LO, and the time interval between LMOs included in each LO. Alternatively, the configuration information further includes: the number of LMOs included in each LO, and the time interval between LMOs included in each LO.

[0292] In some optional implementations, the configuration information for each LO further includes: a frequency domain starting position and a first bandwidth; or a frequency domain offset and a second bandwidth. The frequency domain offset indicates the frequency offset of each LO from the SSB, or indicates the frequency offset of each LO from point A.

[0293] In some optional implementations, the configuration information of each LO further includes: a configuration identifier of each LO.

[0294] In some optional implementations, the message carrying the configuration information of at least one LO includes: a system information block SIB message and an RRC message.

[0295] In some optional implementations, a BWP includes configuration information of one or more LOs.

[0296] For the specific operations of the network device 1300 and the terminal device 1400, refer to the operations performed by the network device and the terminal device in the embodiments shown in Figures 5 to 10 above, which will not be repeated here.

[0297] In some optional implementations, the network device 1300 is used to implement the operations performed by the network device in the embodiment shown in FIG. 11 , and the terminal device is used to implement the operations performed by the terminal device in the embodiment shown in FIG. 11 , which generally include the following:

[0298] In some optional implementations, the transceiver unit 1301 is configured to send second information to the terminal device 1400 , where the second information indicates first configuration information of the first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB.

[0299] In some optional implementations, the transceiver unit 1301 is further configured to send at least one set of configuration information of the first signal to the terminal device 1400 , where the at least one set of configuration information includes the first configuration information.

[0300] In some optional implementations, transceiver unit 1401 is configured to receive second information from network device 1300, where the second information indicates first configuration information of a first signal, where the first signal includes LP-WUS or LP-SS, and is associated with SSB. Processing unit 1402 is configured to monitor the first signal based on the first configuration information.

[0301] In some optional implementations, the transceiver unit 1401 is further configured to receive at least one set of configuration information of a first signal from a network device, where the at least one set of configuration information includes the first configuration information.

[0302] In some optional embodiments, the processing unit 1402 is further configured to, when the first signal includes LP-SS, synchronize and measure the low power wake-up receiver based on LP-SS, and, when the first signal includes LP-WUS, determine whether to monitor the downlink channel at a timing indicated by the LP-WUS.

[0303] In some optional embodiments, each set of configuration information in at least one set of configuration information includes a time domain offset between a time domain starting position of the first signal and a starting position of the SSB, and / or a duration of the first signal.

[0304] In some optional implementations, each set of configuration information in the at least one set of configuration information includes a frequency domain offset of the first signal and / or a bandwidth of the first signal. The frequency domain offset of the first signal indicates a frequency domain offset between a frequency domain start position of the first signal and an SSB, or indicates a frequency offset between the frequency domain start position of the first signal and point A.

[0305] In some optional implementations, each set of configuration information in the at least one set of configuration information includes a configuration identifier and / or a period of the first signal.

[0306] In some optional implementations, if the terminal device 1400 is in an idle state or an inactive state, the message carrying the second information includes: an RRC release message or a group-common DCI message. If the terminal device 1400 is in a connected state, the message carrying the second information includes: an RRC message, a DCI message, or a MAC-CE message.

[0307] In some optional implementations, the message carrying at least one set of configuration information of the first signal includes a SIB message or an RRC message.

[0308] For the specific operations of the network device 1300 and the terminal device 1400, refer to the operations performed by the network device and the terminal device in the embodiment shown in FIG11 , which will not be described again here.

[0309] In some optional implementations, the network device 1300 is configured to implement the operations performed by the network device in the embodiment shown in FIG. 12 , and the terminal device is configured to implement the operations performed by the terminal device in the embodiment shown in FIG. 12 . In summary, the operations include the following:

[0310] In some optional implementations, the transceiver unit 1301 is configured to send a MIB message to the terminal device 1400, where the MIB message includes a first field and a second field, where the first field is used to determine a subcarrier offset, and the second field is used to indicate a position of SIB1. When the subcarrier offset determined based on the first field is a preset value, a first signal is sent to the terminal device 1400 based on the communication resources of SIB1, where the first signal includes LP-WUS or LP-SS.

[0311] In some optional implementations, transceiver unit 1401 is configured to receive a MIB message from a network device, the MIB message including a first field and a second field, the first field being used to determine a subcarrier offset, and the second field being used to indicate a position of SIB1. When the subcarrier offset determined based on the first field is a preset value, transceiver unit 1401 is configured to receive a first signal sent by network device 1300 based on a communication resource of SIB1, the first signal including LP-WUS or LP-SS.

[0312] In some optional embodiments, the processing unit 1402 is configured to, when the first signal includes an LP-SS signal, synchronize and measure the low power wake-up receiver based on the LP-SS signal, and, when the first signal includes an LP-WUS signal, determine whether to monitor a downlink channel at a timing indicated by the LP-WUS signal.

[0313] In some optional embodiments, the preset values ​​include: a subcarrier offset value of 30 in the frequency band below 6 GHz, or a subcarrier offset value of 14 in the 5G millimeter wave frequency band.

[0314] For the specific operations of the network device 1300 and the terminal device 1400, refer to the operations performed by the network device and the terminal device in the embodiment shown in FIG12 above, which will not be repeated here.

[0315] In some optional implementations, the transceiver unit 1301 is configured to send a first signal to the terminal device 1400 based on the communication resources of the idle RB when the SSB is scheduled according to the RGB and the RGB of the scheduled SSB also includes an idle RB. The first signal includes LP-WUS or LP-SS.

[0316] In some optional embodiments, the transceiver unit 1401 is used to receive a first signal from the network device 1300, where the first signal is sent by the network device 1300 to the terminal device 1400 based on the communication resources of the idle RB when the SSB is scheduled according to RGB and the RGB of the scheduled SSB also includes an idle RB.

[0317] In some optional embodiments, the processing unit 1402 is configured to, when the first signal includes LP-SS, synchronize and measure the low power wake-up receiver based on LP-SS, and, when the first signal includes LP-WUS, monitor the downlink channel at a timing indicated by the LP-WUS.

[0318] Please refer to Figure 15, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1500 can be used to implement the functions of the terminal device or network device in the above embodiments.

[0319] The communication device 1500 shown in FIG15 may include a processor 1501 , a memory 1502 , a communication interface 1503 , and a bus 1504 . The processor 1501 , the memory 1502 , and the communication interface 1503 may be connected via the bus 1504 .

[0320] The processor 1501 is the control center of the communication device 1500 and can be a general-purpose central processing unit (CPU) or other general-purpose processors, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0321] As an example, processor 1501 may include one or more CPUs.

[0322] The memory 1502 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0323] In one possible implementation, memory 1502 may exist independently of processor 1501. Memory 1502 may be connected to processor 1501 via bus 1504 and used to store data, instructions, or program code. When processor 1501 calls and executes the instructions or program code stored in memory 1502, the method provided in the embodiments of the present application can be implemented.

[0324] In another possible implementation, the memory 1502 may also be integrated with the processor 1501 .

[0325] The communication interface 1503 is used to connect the communication device 1500 to other devices via a communication network, which may be Ethernet, a radio access network (RAN), a wireless local area network (WLAN), or the like.

[0326] Bus 1504 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus can be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, FIG15 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0327] It should be noted that the structure shown in FIG15 does not constitute a limitation on the communication device 1500. In addition to the components shown in FIG15, the communication device 1500 may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0328] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned plug-in processing method.

[0329] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored on any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the aforementioned plug-in processing method.

[0330] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0331] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0332] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. The term "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules clearly listed, but may include other steps or modules that are not clearly listed or inherent to these processes, methods, products or devices. The naming or numbering of the steps in this application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The named or numbered process steps can be changed in the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved. The division of modules in this application is a logical division. There may be other division methods when implementing in actual applications. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some ports, and the indirect coupling or communication connection between modules can be electrical or other similar forms, which are not limited in this application. In addition, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this application.

[0333] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method is applied to a network device, and the method includes: First information is sent to a terminal device, where the first information is used to indicate a first low power wake-up opportunity LO where a target low power wake-up signal LP-WUS is located, so that the terminal device monitors the target LP-WUS at the first LO.

2. The method according to claim 1, characterized in that Before sending the first information to the terminal device, the method further includes: Configuration information of at least one LO is sent to the terminal device, where the configuration information of each LO is used to define the LO, and the configuration information of the at least one LO includes the configuration information of the first LO.

3. The method according to claim 2, characterized in that The LO defined by the configuration information of each LO includes at least one low power wake-up signal monitoring opportunity LMO, and the LMO is used to send LP-WUS.

4. The method according to claim 2 or 3, characterized in that If the terminal device is in an idle state or an inactive state, the configuration information of each LO includes a first period and / or a first time domain parameter; The first cycle corresponds to a first duration, or the duration of the first cycle is predefined, or the duration of the first cycle is the same as the duration of the paging cycle; The first time domain parameter includes a first time domain offset and a second time domain offset, or includes a third time domain offset and a second duration; The first time domain offset indicates the time offset between the start moment of each LO and the paging frame PF or the paging period PO, the second time domain offset indicates the time offset between the end moment of each LO and the PF or the PO, and the third time domain offset indicates the time offset between the start moment or end moment of each LO and the PF or the PO.

5. The method according to claim 4, characterized in that Each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a bitmap of a paging packet.

6. The method according to claim 4, characterized in that Each LMO corresponds to a beam, and the LP-WUS corresponding to each LMO indicates a paging packet.

7. The method according to any one of claims 4 to 6, characterized in that The message carrying the first information includes: a radio resource control release RRC release message, or a group common downlink control information DCI message.

8. The method according to claim 2 or 3, characterized in that If the terminal device is in a connected state, the configuration information of each LO includes a second period and / or a second time domain parameter; The second cycle corresponds to a third duration, or the duration of the second cycle is predefined, or the duration of the second cycle is the same as the duration of the discontinuous reception (DRX) cycle of the terminal device; The second time domain parameters include a fourth time domain offset and a fifth time domain offset, or include a sixth time domain offset and a fourth duration; The fourth time domain offset indicates the time offset between the starting moment of each LO and the starting symbol of the discontinuous reception of the terminal device, the fifth time domain offset indicates the time offset between the ending moment of each LO and the starting symbol of the DRX of the terminal device, and the sixth time domain offset indicates the time offset between the starting moment or ending moment of each LO and the starting symbol of the DRX of the terminal device.

9. The method according to claim 8, characterized in that The LP-WUS corresponding to each LMO indicates at least one terminal identifier.

10. The method according to claim 8 or 9, characterized in that The message carrying the first information includes: an RRC message, a DCI message, or a media access control element MAC-CE message.

11. The method according to any one of claims 2 to 10, characterized in that The configuration information of each LO also includes a monitoring mode of each LO, and the monitoring mode includes duty cycle monitoring or continuous monitoring.

12. The method according to any one of claims 2 to 10, characterized in that The configuration information of each LO also includes: The starting position and duration of each LMO included in each LO; Alternatively, it further includes: the starting position and duration of the first LMO or the last LMO in each LO, and the time interval between the LMOs included in each LO; Alternatively, it also includes the number of LMOs included in each LO and the time interval between the LMOs included in each LO.

13. The method according to any one of claims 2 to 12, characterized in that The configuration information of each LO further includes: a frequency domain starting position and a first bandwidth; or a frequency domain offset and a second bandwidth; The frequency domain offset indicates a frequency offset between each LO and a synchronization signal / physical broadcast channel block SSB, or indicates a frequency offset between each LO and a frequency reference point A.

14. The method according to any one of claims 2 to 13, characterized in that The configuration information of each LO further includes: a configuration identifier of each LO.

15. The method according to any one of claims 2 to 14, characterized in that The message carrying the configuration information of the at least one LO includes: a system information block SIB message and an RRC message.

16. The method according to any one of claims 1 to 15, characterized in that A BWP includes configuration information of one or more LOs.

17. A communication method, characterized in that: The method is applied to a terminal device, and the method includes: receiving first information from a network device, where the first information is used to indicate a first LO where a target LP-WUS is located; Based on the first information, the target LP-WUS is monitored at the first LO.

18. The method according to claim 17, characterized in that Before receiving the first information from the network device, the method further includes: Configuration information of at least one LO is received from the network device, where the configuration information of each LO is used to define the LO, and the configuration information of the at least one LO includes the configuration information of the first LO.

19. The method according to claim 18, characterized in that The LO defined by the configuration information of each LO includes at least one LMO, and the LMO is used to monitor the LP-WUS.

20. The method according to any one of claims 17 to 19, characterized in that The method further comprises: Based on the target LP-WUS, it is determined whether the terminal device monitors the paging message of the PF or PO corresponding to the target LP-WUS when the terminal device is in an idle state or an inactive state.

21. The method according to any one of claims 17 to 19, characterized in that The method further comprises: Based on the target LP-WUS, it is determined whether the terminal device monitors a downlink control channel PDCCH when in a connected state.

22. A communication method, characterized in that: The method is applied to a network device, and the method includes: Second information is sent to the terminal device, where the second information indicates first configuration information of a first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB.

23. The method according to claim 22, characterized in that Before sending the second information to the terminal device, the method further includes: At least one set of configuration information of the first signal is sent to a terminal device, where the at least one set of configuration information includes the first configuration information.

24. The method according to claim 23, wherein Each set of configuration information in the at least one set of configuration information includes the time domain offset between the time domain starting position of the first signal and the starting position of the SSB, and / or the duration of the first signal.

25. The method according to claim 23 or 24, characterized in that Each set of configuration information in the at least one set of configuration information includes a frequency domain offset of the first signal and / or a bandwidth of the first signal; The frequency domain offset of the first signal indicates the frequency domain offset between the frequency domain starting position of the first signal and the SSB, or indicates the frequency offset between the frequency domain starting position of the first signal and pointA.

26. The method according to any one of claims 23 to 25, characterized in that Each set of configuration information in the at least one set of configuration information includes a configuration identifier and / or a period of the first signal.

27. The method according to any one of claims 22 to 26, characterized in that If the terminal device is in an idle state or an inactive state, the message carrying the second information includes: an RRC release message or a group-common DCI message; If the terminal device is in a connected state, the message carrying the second information includes: an RRC message, a DCI message, or a MAC-CE message.

28. The method according to any one of claims 22 to 27, characterized in that The message carrying at least one set of configuration information of the first signal includes an SIB message or an RRC message.

29. A communication method, characterized in that: The method is applied to a terminal device, and the method includes: receiving second information from a network device, where the second information indicates first configuration information of a first signal, where the first signal includes LP-WUS or LP-SS, and the first signal is associated with SSB; Based on the first configuration information, monitor the first signal.

30. The method according to claim 29, wherein Before receiving the second information from the network device, the method further includes: At least one set of configuration information of the first signal is received from a network device, where the at least one set of configuration information includes the first configuration information.

31. A network device, characterized in that: The method comprises modules for implementing the method of any one of claims 1 to 16 or 22 to 28.

32. A terminal device, characterized in that: The method comprises means for implementing the method of any one of claims 17 to 21 or 29 to 30.

33. A communication device, characterized in that: comprising a processor coupled to a memory; Instructions are stored in the memory, and when the instructions are executed on the processor, the communication device implements the method of any one of claims 1 to 16, 17 to 21, 22 to 28, or 29 to 30.

34. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a processor, enable the method of any one of claims 1 to 16, 17 to 21, 22 to 28, or 29 to 30 to be implemented.

35. A computer program product, characterized in that When the computer program product is executed on a computer, the method of any one of claims 1 to 16, 17 to 21, 22 to 28, or 29 to 30 is implemented.

Images