Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. The method comprises the following steps: receiving first configuration information sent by a network device, wherein the first configuration information indicates measurement parameters and multiple sets of low-power wake-up signal (LP-WUS) parameter sets; measuring a reference signal based on the measurement parameters to obtain a first signal measurement result, wherein the first signal measurement result is used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; sending the first signal measurement result, wherein the first signal measurement result is used to determine the first LP-WUS parameter set used for sending an LP-WUS; and receiving the LP-WUS based on the first LP-WUS parameter set. The method can adapt to a dynamically changing wireless environment, so that the terminal device and the network device can interact with each other in time, and the network performance is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods and communication devices. Background Technology

[0002] The terminal equipment includes the main radio (MR) and the low-power wake-up signal receiver (LR). When the terminal equipment is in connected mode (RRC_CONNECTED) and there is no data interaction between the terminal equipment and the network equipment, the LR of the terminal equipment is usually active, while the MR is in sleep mode. When there is data interaction between the terminal equipment and the network equipment, the LR of the terminal equipment receives a low-power wake-up signal (LP-WUS) from the network equipment, which wakes up the MR of the terminal equipment, thus enabling data interaction with the network equipment. That is, the LR is used to receive LP-WUS, and the MR is used to receive other data (such as radio resource control (RRC) signaling).

[0003] In the MR wake-up mode of the terminal device, the network device configures relevant LP-WUS parameters (such as the number of detection opportunities) for the terminal device via RRC signaling (e.g., when the terminal device powers on). After the terminal device enters sleep mode, the LR of the terminal device starts working, that is, the LR of the terminal device monitors LP-WUS according to the relevant parameters configured by the network device. If the LR of the terminal device receives LP-WUS, it wakes up the MR to conduct subsequent data interaction.

[0004] However, when channel state information (such as channel state deterioration) or traffic volume changes, the previously configured LP-WUS parameters may no longer be applicable, resulting in the terminal device being unable to detect LP-WUS, the MR being unable to be woken up in time, and consequently the terminal device being unable to receive data sent by subsequent network devices in a timely manner. Summary of the Invention

[0005] This application provides a communication method and communication device that can adapt to dynamically changing wireless environments, enabling timely data exchange between terminal devices and network devices, thereby improving network performance.

[0006] Firstly, some embodiments of this application provide a retransmission method. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the terminal device's functions. This application does not limit this. The following description uses a terminal device as an example. The communication method may include: receiving first configuration information sent from a network device, the first configuration information indicating measurement parameters and multiple sets of Low Power Wake-up Signal (LP-WUS) parameter sets; measuring a reference signal based on the measurement parameters to obtain a first signal measurement result, the first signal measurement result being used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; sending the first signal measurement result, the first signal measurement result being used to determine the first LP-WUS parameter set used when sending LP-WUS; and receiving LP-WUS based on the first LP-WUS parameter set.

[0007] In this way, network devices configure multiple LP-WUS parameter sets for terminal devices. The terminal device selects one LP-WUS parameter set from these sets based on signal measurement results. Since signal measurement results are related to channel conditions, the LP-WUS parameter set determined based on these results is suitable for the current channel conditions. This adapts to dynamically changing wireless environments, enabling timely data exchange between terminal devices and network devices, thus improving network performance.

[0008] In one possible embodiment, the first configuration information indicates a parameter switching event, and sending a first signal measurement result includes: sending the first signal measurement result if the first signal measurement result satisfies the parameter switching event.

[0009] In this way, the first signal measurement result is reported to the network device, so that the network device can determine the same LP-WUS parameter set as the terminal device.

[0010] In one possible embodiment, the first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predefined by the protocol.

[0011] In this way, network devices and terminal devices simultaneously activate the same LP-WUS parameter set based on a pre-defined first time. This ensures that the LP-WUS parameter sets activated by network devices and terminal devices are synchronized.

[0012] In one possible embodiment, after receiving LP-WUS based on the first LP-WUS parameter set, the method further includes: sending a first notification to the network device, the first notification indicating that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is the first LP-WUS parameter set.

[0013] In one possible embodiment, the first configuration information indicates multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

[0014] In one possible embodiment, the LP-WUS parameter set includes the number of LP-WUS monitoring opportunities, the strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition, the number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition; the second coverage level decision condition and the third coverage level decision condition are any two of a plurality of coverage level decision conditions.

[0015] In one possible embodiment, update information is received from a network device, the update information being used to update the coverage level decision conditions in the first configuration information.

[0016] Secondly, some embodiments of this application provide a communication method. This method can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit this. The following description uses a network device as an example. The method includes: sending first configuration information, the first configuration information including multiple sets of LP-WUS parameter sets and measurement parameters; receiving a first signal measurement result, the first signal measurement result being used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; and sending LP-WUS based on the first LP-WUS parameter set.

[0017] In one possible embodiment, the first configuration information indicates a parameter switching event, and receiving a first signal measurement result includes: receiving the first signal measurement result if the first signal measurement result satisfies the parameter switching event.

[0018] In one possible embodiment, the first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predefined by the protocol.

[0019] In one possible embodiment, after sending LP-WUS based on the first LP-WUS parameter set, the method further includes: receiving a first notification, the first notification indicating that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is the first LP-WUS parameter set.

[0020] In one possible embodiment, the first configuration information includes multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

[0021] In one possible embodiment, the LP-WUS parameter set includes the number of LP-WUS monitoring opportunities, the strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition, the number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition; the second coverage level decision condition and the third coverage level decision condition are any two of a plurality of coverage level decision conditions.

[0022] In one possible embodiment, update information is sent to update the coverage level decision conditions in the first configuration information.

[0023] Thirdly, this application provides a communication device including a transceiver module and a processing module. The transceiver module is used to receive first configuration information sent from a network device, the first configuration information indicating measurement parameters and multiple sets of Low Power Wake-up Signal (LP-WUS) parameter sets; the processing module is used to measure a reference signal based on the measurement parameters to obtain a first signal measurement result, the first signal measurement result being used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; the transceiver module is also used to transmit the first signal measurement result, the first signal measurement result being used to determine the first LP-WUS parameter set used when transmitting LP-WUS; and to receive LP-WUS based on the first LP-WUS parameter set.

[0024] Fourthly, this application provides a communication device including a transceiver module. The transceiver module is used to transmit first configuration information, which includes multiple sets of LP-WUS parameter sets and measurement parameters; receive a first signal measurement result, which is used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; and transmit LP-WUS based on the first LP-WUS parameter set.

[0025] The third and fourth aspects are the implementation on the device side, which correspond to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0026] Fifthly, this application provides a communication device including a processor coupled to a memory, which can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0027] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0028] In another implementation, the communication device is a chip configured in the first device. When the communication device is a chip configured in the first device, the communication interface can be an input / output interface.

[0029] Sixthly, this application provides a communication device including a processor coupled to a memory, which can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0030] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0031] In another implementation, the communication device is a chip configured in the reader / writer. When the communication device is a chip configured in the reader / writer, the communication interface can be an input / output interface.

[0032] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0033] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0034] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0035] Optionally, the processor may be one or more, and the memory may be one or more.

[0036] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0037] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.

[0038] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0039] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0040] In a twelfth aspect, a communication system is provided, including the aforementioned terminal equipment / access network equipment. Optionally, the communication system may further include other devices that communicate with the terminal equipment and / or network equipment. Attached Figure Description

[0041] Figure 1This application provides a schematic diagram of the architecture of a communication system.

[0042] Figure 2a A schematic diagram of a C-DRX cycle provided for an embodiment of this application;

[0043] Figure 2b A schematic diagram of LR and MR provided for an embodiment of this application;

[0044] Figure 2c A schematic diagram of a communication scenario provided in an embodiment of this application;

[0045] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0046] Figure 4 A schematic diagram of a first time point provided in an embodiment of this application;

[0047] Figure 5 A flowchart illustrating another communication method provided in an embodiment of this application;

[0048] Figure 6a This is another schematic diagram of a communication scenario provided in an embodiment of this application;

[0049] Figure 6b A schematic diagram illustrating yet another communication method provided in an embodiment of this application;

[0050] Figure 6c A schematic diagram illustrating yet another communication method provided in an embodiment of this application;

[0051] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0052] Figure 8 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0054] It should be understood that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0055] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0056] To facilitate a detailed understanding of the embodiments of this application, the system architecture involved in the embodiments of this application will be described below.

[0057] Figure 1 This is a schematic diagram of the architecture of the communication system 1000 used in an embodiment of this application. Figure 1 As shown, the communication system includes a radio access network (RAN) 100 and a core network 200. Optionally, the communication system 1000 may also include an Internet or a data network 300. The RAN 100 includes at least one RAN node (e.g., ...). Figure 1 (110a and 110b in the original text), may also include at least one terminal (such as...) Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (120a-120j). Figure 1 (Not shown in the diagram). Terminals connect wirelessly to the RAN nodes, and the RAN nodes connect wirelessly or via wired connection to the core network 200. The core network equipment in the core network 200 and the RAN nodes in the RAN 100 can be independent physical devices, or they can be the same physical device integrating the logical functions of both the core network equipment and the RAN nodes. Terminals can connect to each other, and RAN nodes can connect to each other, via wired or wireless connections. It should be noted that, in the following text, the RAN node may also be referred to as a network device.

[0058] RAN 100 can be an evolved universal terrestrial radioaccess (E-UTRA) system, a new radio (NR) system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN 100 can also include two or more of the above-mentioned different radio access systems. RAN 100 can also be an open RAN (O-RAN).

[0059] RAN nodes, also known as radio access network equipment, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in 5G mobile communication systems, a next-generation base station in 6G mobile communication systems, or a base station in future mobile communication systems. RAN nodes can also be macro base stations (such as...) Figure 1 (e.g., 110a), or it can be a micro base station or an indoor station (such as...) Figure 1 (110b in the original text) can also be a relay node or a donor node.

[0060] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The CU performs the functions of the base station's Radio Resource Set Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes or integrated into the same RAN node, such as within a baseband unit (BBU). The RU can be included in radio frequency equipment, such as in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0061] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0062] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as 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 grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0063] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0064] The roles of base stations and terminals can be relative, for example, Figure 1 The helicopter or drone 120i can be configured as a mobile base station. For terminals 120j accessing the wireless access network 100 via 120i, 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0065] Before describing the technical solutions of the embodiments of this application, the relevant technical terms in the embodiments of this application will be explained first. It should be noted that these descriptions are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0066] I. Connected-mode discontinuous reception (C-DRX) cycle

[0067] C-DRX allows terminal devices maintaining an RRC connection with network equipment to periodically shut down their main receiver (MR), thereby reducing the terminal device's power consumption. Conversely, the terminal device will also periodically wake up its MR based on this C-DRX cycle.

[0068] Optionally, the C-DRX cycle can be configured via RRC signaling.

[0069] For example, such as Figure 2a As shown, the C-DRX cycle consists of the following parts: monitoring time (also known as OnDuration time) and inactivity timer (also known as inactivity timer).

[0070] OnDuration Time: During the OnDuration time, the terminal device is in the DRX active period (the terminal device's master receiver (MR) is in a wake-up state), and the terminal device monitors the downlink control channel. The length of this OnDuration time is indicated by the parameter drxOnDurationTimer in the RRC signaling. For example, if the value of the parameter drxOnDurationTimer is 10ms, then the length of the OnDuration time is 10 milliseconds.

[0071] inactivity timer: When the main receiver (MR) of the terminal device successfully receives data (e.g., DCI) within the OnDuration time, the terminal device enables the inactivity timer, and the terminal device continuously monitors during the execution of the inactivity timer.

[0072] During the DRX cycle outside of the OnDuration and inactivity timers, the terminal device's main receiver (MR) enters sleep mode, and the terminal device does not monitor the PDCCH.

[0073] While C-DRX can achieve energy savings, it still generates unnecessary power consumption because terminal devices periodically enter OnDuration periods. During the development of communication, LP-WUS was introduced on top of C-DRX. This means that, unlike C-DRX, the terminal device's MR does not wake up during the OnDuration period each cycle. The OnDuration period is only triggered and the terminal device's MR is woken up when the MO (Mobile Object) receives an LP-WUS signal corresponding to the OnDuration period. In other words, under LP-WUS, the terminal device's MR will not wake up during every C-DRX OnDuration period.

[0074] II. Low-power receiver

[0075] A low-power receiver (LR), also known as a wake-up receiver, is used to monitor low-power signals such as LP-WUS. Figure 2b As described above, when the terminal device is in connected mode (RRC_CONNECTED), and there is no data interaction between the terminal device and the network device, the terminal device's receiver (LR) is typically active, while the main receiver (MR) is in sleep mode. When there is data interaction between the terminal device and the network device, the terminal device's primary receiver (LP) receives a low-power wake-up signal (LP-WUS) from the network device to wake up the terminal device's MR, thereby enabling data interaction with the network device. That is, the LR is used to receive LP-WUS, and the MR is used to receive other data (such as RRC signaling).

[0076] For example, the workflow of MR and LR is as follows:

[0077] Phase 1: System Initialization and LP-WUS Configuration. Phase 1 can occur after the terminal device powers on or after the master system (master receiver, MR) is actively woken up and performs its first communication. Phase 1 mainly includes the following steps: parameter negotiation (the terminal device and network device communicate to negotiate the relevant LP-WUS parameters); hardware configuration (the terminal device's MR writes the negotiated LP-WUS parameters into the LR's configuration register); power and clock configuration (configure the power management unit to allocate a normally open low-power power domain for the LR).

[0078] Phase 2: The main receiver (MR) enters sleep mode. After the configuration in Phase 1 is completed, the system prepares to enter an ultra-low power state (i.e., the main receiver (MR) enters sleep mode). This Phase 2 mainly includes the following steps: context saving (the system stores the current network connection status, session key, and other necessary context information into memory); orderly shutdown (the RF front-end and baseband processor of the main receiver are turned off, and the main receiver (MR) enters the hardware-defined power-off state); switching control and final sleep mode (the main receiver (MR) is completely powered off, the receiver (LR) is powered on independently and runs, continuously or periodically monitoring the wireless channel).

[0079] Phase 3: Listening and Wake-up Process. After Phase 2, the Low-Power Receiver (LR) operates independently. The LR continuously monitors the channel based on the LP-WUS parameters configured in Phase 1. For example... Figure 2b As shown, if the low-power receiver LR receives the relevant LP-WUS, the low-power receiver LR triggers the wake-up of the master receiver MR.

[0080] Phase 4: Master Receiver (MR) Recovery and Response. Phase 4 mainly includes the following steps: rapid initialization (the terminal device rapidly initializes the RF and baseband of the master receiver (MR) and restores the network connection state from the previously saved context); establishing master link communication (the master receiver (MR) monitors downlink data on the standard data channel); task execution and re-entering sleep mode (after the terminal device completes tasks such as data exchange, it repeats the processes of Phase 1 and Phase 2 above, and the master receiver (MR) enters sleep mode again).

[0081] As discussed above, there are two ways a terminal device's main receiver (MR) can be woken up: either automatically during the OnDuration period of the C-DRX cycle, or the terminal device's low-power receiver (LR) wakes up the MR after receiving the relevant LP-WUS. The LR receives LP-WUS according to its configured parameters. Therefore, when channel state information (such as deteriorating channel conditions) or traffic volume changes, the previously configured LP-WUS parameters may no longer be applicable, causing the terminal device to fail to receive LP-WUS in a timely manner. In this case, the terminal device must wait for it to automatically fall back to C-DRX due to prolonged inactivity, and only during the OnDuration period of the C-DRX cycle can the MR be woken up. In other words, if the MR cannot be woken up in time, the terminal device cannot receive data sent by subsequent network devices. For example... Figure 2cAs shown, after the terminal device moves from position 1 to position 2, the distance between position 2 and the network device is greater than the distance between position 1 and the network device. Therefore, it can be understood that the channel state at position 2 is worse than that at position 1. For the terminal device, the deterioration of the channel state causes a mismatch in the previously configured LP-WUS parameters. If the terminal device uses the previously configured LP-WUS parameters, it may be unable to detect LP-WUS, or may miss LP-WUS detection.

[0082] To address this issue, this application proposes a communication method. In this method, the network device configures multiple LP-WUS parameter sets for the terminal device. After measuring the reference signal, the terminal device independently determines the LP-WUS parameter set to use based on the signal measurement results, thereby adapting to the dynamically changing wireless environment and enabling timely data exchange between the terminal device and the network device, thus improving network performance.

[0083] The following is combined with Figure 3 The communication method provided in the embodiments of this application will be further described. It is understood that this application uses terminal devices and network devices as examples to illustrate the execution of the interaction, but it does not limit the execution subject of the interaction. For example, the method executed by the network device in this application can also be executed by a module applied to the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the network device's functions; similarly, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. Wherein:

[0084] 301. The network device sends first configuration information, which indicates measurement parameters and multiple sets of Low Power Wake-up Signal (LP-WUS) parameter sets. Correspondingly, the terminal device receives the first configuration information sent by the network device.

[0085] Optionally, the first configuration information is sent to the terminal device via RRC signaling (e.g., RRCReconfiguration), and the first configuration information is carried in the RRC signaling.

[0086] Optionally, measurement parameters include those related to Radio Resource Management (RRM). Examples include the measurement object, report configuration (ReportConfig), and measurement identifier (MeasID).

[0087] In one possible embodiment, the parameters in the LP-WUS parameter set may differ between the network device and the terminal device. Some LP-WUS parameters do not need to be configured for the terminal device and are directly executed by the network device. The following sections describe the LP-WUS parameters executed on the network device side and the LP-WUS parameters executed on the terminal device side, respectively:

[0088] Optionally, the LP-WUS parameters executed on the terminal device side include, but are not limited to, one or more of the following LP-WUS parameters:

[0089] Actual LP-WUS Monitoring Hour (MO) Duration: Indicates the length of OFDM symbols for which the terminal device's LP-WUS reception window is actually open within each monitoring hour. The terminal device only performs signal detection within this actual LP-WUS monitoring hour (MO) duration.

[0090] Monitoring cycle and frequency / time offset: Indicates the repetition period and start time of when the terminal device wakes up the LR for monitoring. This cycle is independent of the C-DRX cycle, allowing the terminal device to flexibly adjust the monitoring frequency according to coverage requirements.

[0091] LP-WUS Monitoring Time Count (MO Count): This parameter indicates the number of MOs that the terminal device needs to continuously check within a monitoring cycle.

[0092] Wake-up Time Offset: Indicates the length of time the terminal device delays initiating downlink control channel monitoring after successfully detecting LP-WUS. This wake-up time offset is analogous to the offset in C-DRX (e.g., ...). Figure 2a The offset shown in the figure.

[0093] Downlink Control Channel Monitoring Timer: Indicates the duration for which the terminal device, after being woken up by LP-WUS, maintains the master receiver MR enabled while waiting for downlink control channel scheduling. This PDCCH downlink control channel monitoring timer can be compared to the Inactivity timer in C-DRX (e.g., ...). Figure 2a (The Inactivity timer shown).

[0094] Display Feedback Resource Configuration / Scheduling Request (SR) Resource Configuration: Indicates the dedicated uplink resources used by the terminal device's master receiver (MR) to send an acknowledgment message after successful wake-up.

[0095] Optionally, when receiving LP-WUS subsequently, in addition to needing to receive LP-WUS based on one or more parameters from the aforementioned LP-WUS parameter set, the terminal device also needs to receive LP-WUS based on its own capability parameters. These capability parameters include, but are not limited to, one or more of the following parameters:

[0096] Minimum time interval: Indicates the time required for the terminal device's master receiver (MR) to wake up after receiving data from LP-WUS. For example, the shortest physical time required for the terminal device's MR to complete hardware warm-up, time-frequency synchronization, and be ready to receive PDCCH. This minimum time interval is greater than the network device's scheduling interval (e.g., the interval for sending DCI).

[0097] Maximum number of checkpoints: Indicates the maximum number of wake-up codepoints (codepoints) that the terminal device's hardware can search and match in parallel during a single monitoring session (e.g., 2 or 8). This maximum number of checkpoints indicates the terminal device system's ability to monitor wake-up signals from different groups of active services.

[0098] QCL Source Configuration / CORESET Association: Indicates the spatial reception parameters required to receive LP-WUS. Network devices configure a Control Resource Set Identifier (CORESET ID) to instruct terminal devices to deduce the QCL source (such as a reference signal for measurement) for LP-WUS based on the Active Transmission Configuration Indication (TCI) state of that CORESET. Accordingly, the terminal device can determine the beam direction information required to receive LP-WUS.

[0099] For example, after receiving the QCL source configuration / CORESET association, the terminal device attempts to receive LP-WUS based on the optimal receiving beam direction (the beam direction corresponding to the reference signal) corresponding to the first signal measurement result, thereby avoiding blind beam scanning and enabling the terminal device to detect LP-WUS faster and more accurately.

[0100] In one possible embodiment, the first configuration information indicates multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

[0101] For example, coverage level decision condition 1 corresponds to LP-WUS parameter set 1, coverage level decision condition 2 corresponds to LP-WUS parameter set 2, and coverage level decision condition 3 corresponds to LP-WUS parameter set 3.

[0102] In a possible embodiment, the LP-WUS parameter set includes the number of LP-WUS monitoring opportunities. The intensity range of the LP-WUS signal indicated by the second coverage level determination condition is greater than the intensity range of the LP-WUS signal indicated by the third coverage level determination condition, and the number of LP-WUS monitoring opportunities corresponding to the second coverage level determination condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level determination condition; the second coverage level determination condition and the third coverage level determination condition are any two of multiple coverage level determination conditions.

[0103] Among them, the coverage level determination condition is used to determine the coverage level of the channel where the current terminal device is located.

[0104] Optionally, since the LP-WUS signal and the reference signal are quasi-co-located, the intensity of the LP-WUS signal is related to the RSRP measurement value of the reference signal. The greater the intensity of the LP-WUS signal, the greater the RSRP measurement value of the reference signal. Conversely, the smaller the intensity of the LP-WUS signal, the smaller the RSRP measurement value of the reference signal.

[0105] Optionally, the coverage level determination condition is used to determine the magnitude of the RSRP measurement value of the measurement object (reference signal). The greater the RSRP measurement value, the better the channel state at this time; conversely, the smaller the RSRP measurement value, the worse the channel state at this time.

[0106] Optionally, the coverage level determination condition is used to determine the signal-to-interference-plus-noise ratio or the reference signal reception quality of the measurement object (such as the reference signal).

[0107] Alternatively, the coverage level determination condition is used to comprehensively determine the RSRP measurement value, the signal-to-interference-plus-noise ratio, and the reference signal reception quality.

[0108] Exemplarily, coverage level determination condition 1: RSRP measurement value > the first threshold; coverage level determination condition 2: the second threshold < RSRP measurement value <= the first threshold; coverage level determination condition 3: RSRP measurement value <= the second threshold. Optionally, the first threshold can also be represented by represented, and the second threshold can also be represented by [[ID=2i]]<o000251> represented. The first threshold is greater than the second threshold.

[0109] Optionally, the LP-WUS parameter set includes the mapping relationship between the coverage level and the coverage level determination condition.

[0110] It should be noted that there seems to be a typo in the original text where "[[ID=2i]]<o000251> " should probably be " ". This has been corrected in the translation as much as possible while maintaining the integrity of the original text.Exemplarily, Level 1 (coverage level): Coverage level decision condition 1 (RSRP measurement > first threshold), this Level 1 represents that the channel state is good and the probability of detecting LP-WUS is relatively high; Level 2: Coverage level decision condition 2 (second threshold < RSRP measurement <= first threshold), this Level 2 represents that the channel state is average; Level 3: Coverage level decision condition 3 (RSRP measurement value <= second threshold), this Level 3 represents that the channel state is poor and the probability of detecting LP-WUS is relatively low.

[0111] Optionally, the better the channel state corresponding to the coverage level, the greater the probability of detecting LP-WUS, and the fewer the number of LP-WUS monitoring opportunities corresponding to the coverage level, thereby achieving energy saving.

[0112] Exemplarily, the mapping relationship between the coverage level, the coverage level decision condition, and the number of LP-WUS monitoring opportunities is illustrated below.

[0113] Level 1 (RSRP measurement > first threshold): LP-WUS parameter set 1. LP-WUS parameter set 1: The number of LP-WUS monitoring opportunities is 2, M = 4. The M value is related to the number of orthogonal frequency division multiplexing superposition sequences. M = 4 corresponds to a relatively small number of superposition sequences (such as 4), and the transmission efficiency is high. This LP-WUS is a parameter on the terminal device side. In the case of a good channel state, configuring a smaller number of LP-WUS monitoring opportunities reduces unnecessary wake-up of the terminal device and achieves energy saving. This M is a parameter on the network device side, and this M may not be configured for the terminal device and may be executed by the network device side itself.

[0114] Level 2 (second threshold < RSRP measurement <= first threshold): LP-WUS parameter set 2. LP-WUS parameter set 2: The number of LP-WUS monitoring opportunities is 4, M = 2.

[0115] Level 3 (RSRP measurement value <= second threshold): LP-WUS parameter set 3. LP-WUS parameter set 3: The number of LP-WUS monitoring opportunities is 8, M = 1. M = 1 corresponds to a relatively large number of superposition sequences (such as 16), providing the strongest coverage enhancement performance to ensure detection even in a poor channel.

[0116] Optionally, for Level 3, dedicated SR resources are configured so that the terminal device can autonomously feedback or request through the dedicated SR resources in extreme cases.

[0117] 302. The terminal device measures the reference signal based on the measurement parameters to obtain a first signal measurement result, and the first signal measurement result is used to determine a first LP-WUS parameter set from multiple groups of LP-WUS parameter sets.

[0118] Optionally, the reference signal is a signal corresponding to the measurement object indicated by the measurement parameter.

[0119] Optionally, the first signal measurement result includes the RSRP measurement value of the reference signal, and / or the signal-to-interference-plus-noise ratio, etc.

[0120] Optionally, the terminal device determines the first LP-WUS parameter set based on the RSRP measurement value and the coverage level decision condition in the LP-WUS parameter set.

[0121] Exemplarily, assume that Level1 (RSRP measurement > -105 dBm) corresponds to LP-WUS parameter set 1; Level2 (-115 dBm < RSRP measurement <= -105 dBm) corresponds to LP-WUS parameter set 2; Level3 (RSRP measurement value <= -115 dBm) corresponds to LP-WUS parameter set 3. After the terminal device measures the reference signal, the obtained RSRP measurement value is -110 dBm, and this -110 dBm is within the range of -115 dBm < RSRP measurement <= -80 dBm. The first LP-WUS parameter set is LP-WUS parameter set 2.

[0122] In step 302, the terminal device determines the first LP-WUS parameter set through the first signal measurement result, that is, the terminal device has determined that the LP-WUS parameter set used for receiving LP-WUS is the first LP-WUS parameter set. The LP-WUS parameter set used by the network device side to send LP-WUS must also be the LP-WUS parameter set, so that the terminal device can successfully receive LP-WUS using the first LP-WUS parameter set. That is, the LP-WUS parameter sets effective on the terminal device side and the network device side need to be synchronized. The following introduces how to synchronize in combination with step 303.

[0123] 303. The terminal device sends the first signal measurement result, and the first signal measurement result is used to determine the first LP-WUS parameter set used when sending LP-WUS. Correspondingly, the network device receives the first signal measurement result.

[0124] Optionally, the first configuration information includes the transmission resource for reporting the first signal measurement result. The terminal device sends the first signal measurement result through the transmission resource configured in the first configuration information.

[0125] Optionally, the network device stores the mapping relationship between multiple coverage level decision conditions and multiple groups of LP-WUS parameter sets.

[0126] Optionally, the LP-WUS parameters executed on the network device side include, but are not limited to, one or more of the following LP-WUS parameters:

[0127] M value: Indicates the orthogonal frequency division multiplexing (OFDM) overlay sequence configuration used when generating the LP-WUS signal. Network devices select the M value (e.g., M=1, 2, or 4) based on current coverage requirements, thereby determining the maximum number of candidate overlay sequences supported per OOK ON chip. By adjusting the M value, network devices can control the coverage performance and robustness of the LP-WUS signal (e.g., M=1 corresponds to the maximum number of sequences, providing the strongest coverage).

[0128] QCL Source Configuration / CORESET Association: Indicates the spatial reception parameters required to receive LP-WUS. Network devices configure a Control Resource Set Identifier (CORESET ID) to instruct terminal devices to deduce the LP-WUS QCL source (such as a specific CSI-RS) based on the Active Transmission Configuration Indicator (TCI) state of that CORESET. Accordingly, the terminal device can determine the beam direction information required to receive LP-WUS.

[0129] Maximum number of information bits: Defines the upper limit of the capacity of the LP-WUS physical layer payload (e.g., up to 16 bits in RRC_CONNECTED mode). The terminal device constructs an LP-WUS containing a specific terminal device identifier (such as RNTI) according to this limit to achieve precise wake-up of a specific terminal device.

[0130] In one possible embodiment, the LP-WUS parameters on the network device side can be sent to the terminal device, or they can be left unsent and executed by the network device itself.

[0131] Optionally, since some parameters of the LP-WUS parameters on the network device side (such as the maximum number of information bits) do not need to be executed by the terminal device, the first LP-WUS parameter set may not include these parameters. That is, the first LP-WUS parameter set only includes the LP-WUS parameters that need to be executed by the terminal device side.

[0132] Optionally, the network device determines the first LP-WUS parameter set based on the RSRP value corresponding to the first signal measurement result in the same way as the terminal device does, and will not be described in detail here.

[0133] In one possible embodiment, the first configuration information indicates a parameter switching event, and sending a first signal measurement result includes: sending the first signal measurement result if the first signal measurement result satisfies the parameter switching event.

[0134] Optionally, this parameter switching event indicates to the terminal device that the coverage level has changed. For example, from Level 1 to Level 2. Or, the terminal device determines that the measured RSRP value is different from the coverage level judgment condition of the previously measured RSRP value.

[0135] Optionally, the reporting triggered by the parameter switching event can be an additional signal measurement report. For example, the first configuration information includes a reporting configuration, which includes the reporting period. If a parameter switching event occurs, the terminal device is triggered to immediately report the first signal measurement result (regardless of whether it is currently within the reporting period). If no parameter switching event occurs, the terminal device reports the first signal measurement result according to the configured reporting period.

[0136] Through the above steps, both the terminal device and network device can determine the first LP-WUS parameter set based on the first signal measurement results. Currently, the LP-WUS parameters on the terminal device and network device sides are symmetrical. Furthermore, the terminal device and network device need to synchronously switch to this first LP-WUS parameter set; that is, the terminal device and network device need to ensure that the first LP-WUS parameter set is effective simultaneously.

[0137] In one possible embodiment, the first configuration information indicates a discontinuous reception C-DRX period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predefined by the protocol.

[0138] Optionally, this first time point is the starting point of the C-DRX cycle.

[0139] Optionally, the first time point is the start point of the next C-DRX cycle after the terminal device sends the first signal measurement result.

[0140] Optionally, the first time point can be pre-defined by the protocol, negotiated between the terminal device and the network device, or configured by the network device for the terminal device.

[0141] For example, such as Figure 4 As shown, a parameter switching event occurs during the second C-DRX cycle. The terminal device reports the first signal measurement result during this cycle, and the terminal device and network device determine the first LP-WUS parameter set. At the beginning of the third C-DRX cycle (the first time point), both the terminal device and network device simultaneously activate this first LP-WUS parameter set. That is, after the first time point, the network device transmits LP-WUS using the first LP-WUS parameter set, and the terminal device receives LP-WUS using the first LP-WUS parameter set.

[0142] As described above, by reporting the first signal measurement result, the terminal device and network device are made to use the same LP-WUS parameter set. At the first point in time, both the terminal device and network device simultaneously activate the same LP-WUS parameter set, thus achieving LP-WUS parameter set synchronization.

[0143] 304. The network device sends LP-WUS based on the first LP-WUS parameter set. Correspondingly, the terminal device receives LP-WUS based on the first LP-WUS parameter set.

[0144] In one possible embodiment, after the low-power receiver LR of the terminal device receives LP-WUS, it wakes up the main receiver MR of the terminal device.

[0145] In one possible embodiment, after the terminal device receives LP-WUS based on the first LP-WUS parameter set, the method further includes: the terminal device sending a first notification to the network device, the first notification indicating that the LP-WUS parameter set effective in the next discontinuous reception period is the first LP-WUS parameter set. Accordingly, the network device receives the first notification.

[0146] Optionally, the terminal device's master receiver (MR) sends a first notification to the network device.

[0147] Optionally, the first configuration information indicates a dedicated scheduling request (SR) resource, the first notification being an SR transmitted on the dedicated SR resource.

[0148] Optionally, after sending LP-WUS, the network device starts a first timer. If the network device receives an SR during the first timer's execution, it then sends data. That is, if the network device receives an SR during the first timer's execution, the network device considers that the terminal device's master receiver (MR) has been awakened, and the network device and the terminal device will then engage in subsequent interactions.

[0149] In one possible embodiment, the network device sends update information to update the coverage level decision conditions in the first configuration information. Correspondingly, the terminal device receives the update information.

[0150] Optionally, after sending LP-WUS, the network device enables a first timer. If the network device does not receive an SR during the operation of the first timer, it updates multiple sets of LP-WUS parameter sets and sends update information to enable the terminal device to synchronously update the LP-WUS parameter sets. That is, if the network device does not receive an SR during the operation of the first timer, the network device considers that the main receiver (MR) of the terminal device fails to wake up (due to the terminal device missing the detection of LP-WUS). The network device considers that the current LP-WUS parameter set is not applicable to the current channel state. The network device updates the coverage level determination condition and sends update information to the terminal device to synchronize the terminal device for updating.

[0151] Optionally, after the first sending of LP-WUS, the network device enables a first timer and a first counter, and the first counter is used to determine the number of wake-up failures.

[0152] Optionally, the network device sends the update information during the OnDuration time in the C-DRX cycle.

[0153] Exemplarily, after the first sending of LP-WUS, the network device enables a first timer and a first counter. Before the first timeout of the first timer, the network device does not receive an SR sent by the terminal device. The network device increments the first counter by 1. After the second sending of LP-WUS, the network device restarts the first timer. Before the first timer times out again, the network device does not receive an SR sent by the terminal device. The network device increments the first counter by 1 again. This process is repeated until the first counter reaches a preset threshold. The network device updates the coverage level determination condition and sends update information to the terminal device to synchronize the terminal device for updating.

[0154] Optionally, the second threshold in the updated coverage level determination condition is greater than the second threshold in the coverage level determination condition before the update. And / or, the first threshold in the updated coverage level determination condition is greater than the first threshold in the coverage level determination condition before the update.

[0155] Exemplarily, assume that the coverage level determination condition before the update is: RSRP measurement value > -110 dBm (good channel state, and the number of LP-WUS monitoring opportunities in the corresponding LP-WUS parameter set is small), -115 dBm < RSRP measurement value <= -110 dBm (general channel state), RSRP measurement value <= -115 dBm (poor channel state, and the number of LP-WUS monitoring opportunities in the corresponding LP-WUS parameter set is large).

[0156] The updated coverage level decision condition is as follows: RSRP measurement value > -105 dBm (good channel state, corresponding to a smaller number of LP-WUS monitoring opportunities in the LP-WUS parameter set), -110 dBm < RSRP measurement value <= -105 dBm (average channel state), RSRP measurement value <= -110 dBm (poor channel state, corresponding to a larger number of LP-WUS monitoring opportunities in the LP-WUS parameter set).

[0157] From the above content, it can be seen that the updated coverage level decision condition will achieve the following effects: When the terminal device determines the current coverage level based on the RSRP and the coverage level decision condition, it is easier to determine the coverage level with a poor channel state, so that the number of LP-WUS monitoring opportunities in the effective LP-WUS parameter set is larger, in order to increase the probability that the terminal device successfully monitors LP-WUS. For example, when the value of RSRP is -113 dBm, the current coverage level would originally be determined as Level2 (-115 dBm < RSRP measurement value <= -110 dBm). The LP-WUS parameter set 2 corresponding to this Level2 is used as the first LP-WUS parameter set (the number of LP-WUS monitoring opportunities is 4). Now, after updating the coverage level decision condition, when the value of RSRP is -113 dBm, the current coverage level will be determined as Level3 (RSRP measurement value <= -110 dBm). The LP-WUS parameter set 3 corresponding to this Level3 is used as the first LP-WUS parameter set (the number of LP-WUS monitoring opportunities is 8).

[0158] Optionally, each update is performed according to a preset step size. Or it is adaptively updated by the network device based on the current scenario.

[0159] Exemplarily, the difference between the first threshold after each update and the first threshold before the update is the first step size, and / or the difference between the second threshold after each update and the second threshold before the update is the second step size. The first step size and the second step size can be the same.

[0160] In a possible embodiment, the network device sends update information to the terminal device, and the update information is used to update the parameters in the LP-WUS parameter set of the first configuration information. Or the update information is used to update the number of LP-WUS monitoring opportunities in the LP-WUS parameter set of the first configuration information.

[0161] Optionally, the number of LP-WUS monitoring opportunities corresponding to the updated coverage level decision condition is greater than the number of LP-WUS monitoring opportunities corresponding to the coverage level decision condition before the update.

[0162] For example, assume that the number of LP-WUS monitoring opportunities in LP-WUS parameter set 1 corresponding to coverage level decision condition 1 before the update is 2, the number of LP-WUS monitoring opportunities in LP-WUS parameter set 2 corresponding to coverage level decision condition 2 before the update is 4, and the number of LP-WUS monitoring opportunities in LP-WUS parameter set 3 corresponding to coverage level decision condition 3 before the update is 6.

[0163] The number of LP-WUS monitoring opportunities in LP-WUS parameter set 1 corresponding to the updated coverage level decision condition 1 is 4; the number of LP-WUS monitoring opportunities in LP-WUS parameter set 2 corresponding to the updated coverage level decision condition 2 is 6; and the number of LP-WUS monitoring opportunities in LP-WUS parameter set 3 corresponding to the updated coverage level decision condition 3 is 8.

[0164] As shown above, the updated LP-WUS parameter set will have the following effect: when the terminal device determines the LP-WUS parameter set based on RSRP and coverage level decision conditions, the number of LP-WUS monitoring opportunities in the determined LP-WUS parameter set will be greater. This increases the probability that the terminal device will successfully detect LP-WUS. For example, both LP-WUS parameter set 2 correspond to coverage level decision condition 2, but the updated LP-WUS parameter set 2 has two more LP-WUS monitoring opportunities than the original LP-WUS parameter set 2.

[0165] The following is combined Figure 5 The communication method provided in this application will be further described. Figure 5 The illustrated embodiment is performed by a terminal device and a network device, the terminal device including a main receiver (MR) and a low-power receiver (LR). Wherein:

[0166] 501. Network devices are configured with multiple LP-WUS parameter sets.

[0167] The LP-WUS parameter set can be found in the above description. The LP-WUS parameter set configured by the network device can be divided into LP-WUS parameter sets executed on the network device side (e.g., M value, maximum number of information bits, etc.), LP-WUS parameter sets executed on the terminal device side (e.g., PDCCH detection timer), and LP-WUS parameter sets jointly executed on the network device side and the terminal device side (e.g., number of LP-WUS monitoring opportunities, QCL source configuration / CORESET association, etc.).

[0168] 502. The network device sends first configuration information to the MR of the terminal device. The first configuration information includes the LP-WUS parameter set and measurement parameters.

[0169] Step 502 can be described in the above-mentioned step 301, and will not be repeated here.

[0170] 503. The network device sends a reference signal to the MR of the terminal device.

[0171] Optionally, the reference signal can be a channel state information reference signal (CSI-RS), a cell-specific reference signal (CRS), or other similar signals. This application does not impose any restrictions on the type of reference signal.

[0172] 504. The terminal device measures the reference signal based on the measurement parameters to obtain the first measurement result.

[0173] Optionally, the terminal device performs radio resource management (RRM) measurements on the reference signal based on the measurement parameters to obtain a first measurement result. This step 504 can be referred to the description in step 302 above, and will not be repeated here.

[0174] 505. The network device determines the first LP-WUS parameter set based on the first measurement result.

[0175] Optionally, the network device determines the first LP-WUS parameter set from multiple sets of LP-WUS parameter sets based on the RSRP value corresponding to the first measurement result.

[0176] Optionally, the network device determines the first LP-WUS parameter set in the same way as the terminal device, that is, by using the coverage level judgment conditions and RSRP value of the LP-WUS parameter set.

[0177] During steps 501-505 above, the terminal device MR is in a wake-up state.

[0178] 506. The terminal device determines a first LP-WUS parameter set based on the first measurement result; the terminal device monitors LP-WUS based on the first LP-WUS parameter set.

[0179] Optionally, the LR of the terminal device monitors LP-WUS based on the first LP-WUS parameter set.

[0180] Optionally, step 506 can be referred to the description in step 304 above, and will not be repeated here.

[0181] 507. Network devices send LP-WUS on demand based on the first LP-WUS parameter set.

[0182] In steps 506-507, the MR of the terminal device is in a sleep state. The MR of the terminal device performs periodic sleep according to C-DRX.

[0183] 508. The terminal device responds to LP-WUS and sends a scheduling request.

[0184] Optionally, after receiving LP-WUS, the LR of the terminal device wakes up the MR of the terminal device. The MR of the terminal device sends an SR (Schedule Request) to the network device. This SR can be the first notification mentioned above.

[0185] Optionally, step 508 is optional; the terminal device may not be able to detect LP-WUS, and the terminal device will not send SR.

[0186] 509. If the network device receives a scheduling request feedback within the first timer, it maintains multiple LP-WUS groups and sends data.

[0187] Optionally, the first timer is enabled in step 507. A description of the first timer can be found above. Figure 3 The details of the first timer will not be elaborated here.

[0188] Optionally, if the network device receives SR feedback within the first timer, it indicates that the current multiple sets of LP-WUS parameters are appropriate and do not need to be updated. The network device continues to maintain the multiple sets of LP-WUS parameters.

[0189] 510. The terminal device monitors the PDCCH to receive data.

[0190] In steps 508-510, the MR of the terminal device is in a wake-up state, and the MR of the terminal device is woken up through LP-WUS.

[0191] 511. If the network device does not receive SR feedback within the first timer, the first counter is incremented by 1. The value of the first counter is then used to determine whether to update multiple sets of LP-WUS parameter sets.

[0192] Optionally, when the first counter reaches the threshold, multiple sets of LP-WUS parameter sets are updated. This updating of the multiple sets of LP-WUS parameter sets includes: updating the coverage level determination conditions of the multiple sets of LP-WUS parameter sets, or updating the LP-WUS monitoring timing of the multiple sets of LP-WUS parameter sets. Optionally, please refer to the description in step 304 above; this application will not repeat it here.

[0193] 512. The network device sends update information to the terminal device to update multiple sets of LP-WUS parameter sets.

[0194] Optionally, the network device sends the update information during the OnDuration period of the C-DRX cycle.

[0195] In steps 511-512, the MR of the terminal device is in a wake-up state, and the MR of the terminal device is woken up through the C-DRX cycle.

[0196] It should be noted that the measurement parameters in the first measurement information include the measurement period. The terminal device will perform RRM measurements according to the measurement period to obtain the signal measurement results. After periodically performing measurements, the terminal device will also periodically re-determine the currently effective LP-WUS parameter set. When the channel state changes, the signal measurement results will also change. Therefore, this method of determining the effective LP-WUS parameter set based on the signal measurement results can adapt to dynamic channel states, thereby increasing the probability of the terminal device receiving LP-WUS signals.

[0197] The following is combined Figures 6a-6c The communication method is further described below. To better understand this communication method, an embodiment of this application provides a scenario in which this communication method is applied. (See also:) Figure 6a The diagram illustrates a scenario where a terminal device moves from coverage level 1 to coverage level 2. The terminal device is in RRC_CONNECTED mode during the move. Based on 3GPP meeting guidelines, LP-WUS monitoring occurs before the C-DRX OnDuration time. Figure 6b and Figure 6c The OnDuration time in this context differs from the OnDuration time of the C-DRX cycle described earlier. Figure 6b and Figure 6c The OnDuration time in the table represents the time it takes for the MR to be awakened by LP-WUS after the MO detects LP-WUS. In other words, this OnDuration time is the OnDuration time within the C-DRX cycle after the introduction of LP-WUS.

[0198] Phase 1 (e.g.) Figure 6b As shown): The terminal device is at Level 1.

[0199] The terminal device is located at the center of the base station (Level 1) with good channel conditions (good signal). The RSRP value measured by the terminal device meets the coverage level decision criteria corresponding to Level 1. For example, the RSRP value measured by the terminal device is greater than -105dBm.

[0200] The LP-WUS parameter set that is effective on the terminal device under Level 1 is as follows:

[0201] LP-WUS monitoring periodicity: long period, consistent with the C-DRX period.

[0202] Number of LP-WUS monitoring opportunities: 2. Due to the strong LP-WUS signal, the probability of detection by the terminal device is relatively high. Therefore, configuring fewer LP-WUS monitoring opportunities saves energy consumption of the terminal device.

[0203] Time-Offset2: Adjusted to the minimum value corresponding to the terminal device capability report.

[0204] Optional, such as Figure 6b As shown, under black MO conditions, the terminal device receives LP-WUS, thus triggering the monitoring time (OnDuration time) and waking up the terminal device's MR. Under other white monitoring times, the terminal device does not receive LP-WUS, thus not triggering the OnDuration event (i.e., Figure 6b The dashed OnDuration time indicates that it was not triggered.

[0205] Optionally, this capability report is a report sent by the terminal device to the network device when accessing the network, containing its own capability information. This capability report includes: minimum wake-up latency (the wake-up time for the terminal device to switch from LR to MR operation).

[0206] Optional LP-WUS parameter set: including but not limited to time offset 2. This time offset 2 represents the time reserved for the terminal device to wake up MR. This time offset 2 is greater than or equal to the minimum wake-up latency.

[0207] Optionally, after the terminal device sends a capability report to the network device, the network device determines the time offset 2 based on the minimum wake-up delay in the capability report. The network device then sends the time offset 2 to the terminal device.

[0208] Alternatively, the network device determines the time offset of 2 based on the minimum wake-up latency and UE assistance information (UAI) in the capability report. For example, the UAI reported by the terminal device includes the following three enumerated values: 2, 30, and 42. After receiving the UAI, the network device reasonably arranges the LP-WUS parameter set based on the reported UAI.

[0209] Optionally, at Level 1, the time offset 2 is the time offset corresponding to the enumerated value '2' mentioned above.

[0210] Phase 2 (e.g.) Figure 6c As shown): The LP-WUS parameter set of the terminal device is switched from Level 1 to Level 2.

[0211] When the terminal device moves, it periodically measures the RSRP of the reference signal co-located with LP-WUS to be -112 dBm (which meets the coverage level decision criteria for Level 2). The coverage level of the terminal device then drops from Level 1 to Level 2.

[0212] The terminal device immediately reports the first signal measurement result. The terminal device and network device then synchronously switch to the LP-WUS parameter set corresponding to Level 2 in the next C-DRX cycle.

[0213] The LP-WUS parameter set corresponding to this Level 2 is as follows:

[0214] Number of LP-WUS monitoring opportunities: 4.

[0215] Time-Offset2: Adjusted to the intermediate value supported in the terminal device capability report.

[0216] Optionally, at Level 2, the time offset 2 corresponds to the time offset of the enumerated value '30' mentioned above. Configuring different time offsets of 2 in the LP-WUS parameters can be applied to different business scenarios.

[0217] Figure 7 This is a schematic block diagram illustrating communication provided in an embodiment of this application. For example... Figure 7 As shown, the communication device 700 may include a transceiver module 710 and a processing module 720. The transceiver module 710 can implement corresponding communication functions, which can be internal communication functions of the communication device 700 or communication functions between the communication device 700 and other devices.

[0218] In one possible design, the communication device 700 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 700 can be used to perform the steps or processes performed by the terminal device in any of the above method embodiments.

[0219] For example, the transceiver module 710 is used to receive first configuration information sent from a network device, the first configuration information indicating measurement parameters and multiple sets of low-power wake-up signal LP-WUS parameter sets;

[0220] The processing module 720 is used to measure the reference signal based on the measurement parameters to obtain a first signal measurement result. The first signal measurement result is used to determine a first LP-WUS parameter set from multiple sets of LP-WUS parameter sets.

[0221] The transceiver module 710 is also used to send a first signal measurement result, which is used to determine a first LP-WUS parameter set used when sending LP-WUS; and to receive LP-WUS based on the first LP-WUS parameter set.

[0222] In one possible embodiment, the transceiver module 710 is further configured to send a first signal measurement result when the first configuration information indicates a parameter switching event, including: sending the first signal measurement result when the first signal measurement result satisfies the parameter switching event.

[0223] In one possible embodiment, the first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predefined by the protocol.

[0224] In one possible embodiment, the transceiver module 710 is further configured to send a first notification to the network device, the first notification being configured to indicate that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is the first LP-WUS parameter set.

[0225] In one possible embodiment, the first configuration information indicates multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

[0226] In one possible embodiment, the LP-WUS parameter set includes the number of LP-WUS monitoring opportunities, the strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition, the number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition; the second coverage level decision condition and the third coverage level decision condition are any two of a plurality of coverage level decision conditions.

[0227] In one possible embodiment, the transceiver module 710 is further configured to receive update information sent from the network device, the update information being used to update the coverage level decision conditions in the first configuration information.

[0228] In one possible design, the communication device 700 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 700 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0229] For example, the transceiver module 710 is used to send first configuration information, which includes multiple sets of LP-WUS parameter sets and measurement parameters; receive first signal measurement results, which are used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; and send LP-WUS based on the first LP-WUS parameter set.

[0230] In one possible embodiment, the first configuration information indicates a parameter switching event, and the transceiver module 710 is used to receive a first signal measurement result, including: receiving the first signal measurement result when the first signal measurement result satisfies the parameter switching event.

[0231] In one possible embodiment, the first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predefined by the protocol.

[0232] In one possible embodiment, the transceiver module 710 is configured to receive a first notification, which indicates that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is a first LP-WUS parameter set.

[0233] In one possible embodiment, the first configuration information includes multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

[0234] In one possible embodiment, the LP-WUS parameter set includes the number of LP-WUS monitoring opportunities, the strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition, the number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition; the second coverage level decision condition and the third coverage level decision condition are any two of a plurality of coverage level decision conditions.

[0235] In one possible embodiment, the transceiver module 710 is configured to send update information, which is used to update the coverage level decision conditions in the first configuration information.

[0236] Figure 8This is another schematic block diagram of the communication device 800 provided in the embodiments of this application. The communication device 800 may be a terminal device or a network device (network device / core network) implementing the above-described methods, such as a chip, chip system, or processor. The communication device 800 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0237] like Figure 8 As shown, the communication device 800 may include one or more processors 810, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 810 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 800 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0238] In an alternative design, the processor 810 may also store instructions and / or data that can be executed by the processor 810 to cause the communication device 800 to perform the methods described in the above method embodiments.

[0239] In another alternative design, the communication device 800 may include a communication interface 820 for implementing receiving and transmitting functions. For example, the communication interface 820 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0240] Optionally, the communication device 800 may include one or more memories 830, which may store instructions that can be executed on the processor 810, causing the communication device 800 to perform the methods described in the above method embodiments. Optionally, the memories 830 may also store data. Optionally, the processor 810 may also store instructions and / or data. The processor 810 and the memories 830 may be provided separately or integrated together.

[0241] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0242] In one implementation, the communication device 800 may correspond to the first Bluetooth device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the first Bluetooth device in the above method embodiments. The processor 810 may be used to execute instructions stored in the memory 830, and when the processor 810 executes the instructions stored in the memory, the processor 810 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first Bluetooth device.

[0243] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0244] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0245] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0246] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0247] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned terminal device and network device.

[0248] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the terminal device or network device in any of the foregoing method embodiments.

[0249] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the terminal device or network device in any of the foregoing method embodiments.

[0250] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0251] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0252] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0253] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0254] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0255] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method includes: Receive first configuration information sent from a network device, the first configuration information indicating measurement parameters and multiple sets of low-power wake-up signal LP-WUS parameter sets; Based on the measurement parameters, the reference signal is measured to obtain a first signal measurement result. The first signal measurement result is used to determine a first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets. The first signal measurement result is sent to the network device, and the first signal measurement result is used by the network device to determine the first LP-WUS parameter set to be used when sending LP-WUS; Receive LP-WUS based on the first LP-WUS parameter set; The first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predetermined by the protocol.

2. The method according to claim 1, characterized in that, The first configuration information indicates a parameter switching event, and the sending of the first signal measurement result includes: If the first signal measurement result satisfies the parameter switching event, the first signal measurement result is sent.

3. The method according to claim 1, characterized in that, After receiving LP-WUS based on the first LP-WUS parameter set, the method further includes: Send a first notification to the network device, the first notification being used to indicate that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is the first LP-WUS parameter set.

4. The method according to any one of claims 1-3, characterized in that, The first configuration information indicates multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with the multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

5. The method according to claim 4, characterized in that, The LP-WUS parameter set includes the number of LP-WUS monitoring opportunities. The strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition. The number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition. The second coverage level decision condition and the third coverage level decision condition are any two of the plurality of coverage level decision conditions.

6. The method according to claim 4, characterized in that, The method further includes: The system receives update information from the network device, which is used to update the coverage level decision conditions in the first configuration information.

7. A communication method, characterized in that, The method includes: Send first configuration information to the terminal device. The first configuration information includes multiple sets of LP-WUS parameter sets and measurement parameters. The first configuration information is used by the terminal device to determine the first signal measurement result. Receive the first signal measurement result, which is used to determine the first LP-WUS parameter set from the multiple sets of LP-WUS parameter sets; Based on the first LP-WUS parameter set, send LP-WUS; The first configuration information indicates a discontinuous reception period, and the first LP-WUS parameter set takes effect from a first time point within the discontinuous reception period, the first time point being predetermined by the protocol.

8. The method according to claim 7, characterized in that, The first configuration information indicates a parameter switching event, and the receiving of the first signal measurement result includes: If the first signal measurement result satisfies the parameter switching event, the first signal measurement result is received.

9. The method according to claim 8, characterized in that, After sending LP-WUS based on the first LP-WUS parameter set, the method further includes: Receive a first notification, which indicates that the LP-WUS parameter set effective in the next discontinuous reception period of the network device is the first LP-WUS parameter set.

10. The method according to any one of claims 7-9, characterized in that, The first configuration information includes multiple coverage level decision conditions, and the multiple coverage level decision conditions correspond one-to-one with the multiple sets of LP-WUS parameter sets; the first LP-WUS parameter set is the LP-WUS parameter set corresponding to the first coverage level decision condition, and the first signal measurement result satisfies the first coverage level decision condition.

11. The method according to claim 10, characterized in that, The LP-WUS parameter set includes the number of LP-WUS monitoring opportunities. The strength range of the LP-WUS signal indicated by the second coverage level decision condition is greater than the strength range of the LP-WUS signal indicated by the third coverage level decision condition. The number of LP-WUS monitoring opportunities corresponding to the second coverage level decision condition is less than the number of LP-WUS monitoring opportunities corresponding to the third coverage level decision condition. The second coverage level decision condition and the third coverage level decision condition are any two of the plurality of coverage level decision conditions.

12. The method according to claim 10, characterized in that, The method further includes: Send update information, which is used to update the coverage level decision conditions in the first configuration information.

13. A communication device, characterized in that, Includes units for performing the method as described in any one of claims 1 to 12.

14. A communication device, characterized in that, It includes a processor coupled to a memory, which can be used to execute instructions or data in the memory to implement the method as described in any one of claims 1 to 12.

15. A chip, characterized in that, The device includes a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions to cause the method of any one of claims 1 to 12 to be performed.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked, cause the computer to perform the method described in any one of claims 1 to 12.

Images