Communication method, apparatus and system
Patent Information
- Application Number
- CN202510562331.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-03-28
- Filing Date
- 2025-04-29
- Publication Date
- 2026-09-29
AI Technical Summary
[0005]然而,终端周期性地进入唤醒状态,来监测和网络设备间的PDCCH,仍会使得终端的功耗较大,能耗较高
Smart Images

Figure CN122846352A_ABST
Abstract
Description
[0001] This application claims priority to Chinese Patent Application No. 202510400123.2, filed with the State Intellectual Property Office of China on March 28, 2025, entitled "A Method, Terminal and System for Setting a Low-Power Wake-up Signal", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communications, and more particularly to a communication method, apparatus and system. Background Technology
[0003] In mobile communication systems, terminals need to monitor the physical downlink control channel (PDCCH) between themselves and network devices in order to receive data sent by the network devices and complete communication service interactions. However, during monitoring, the terminal consumes a significant amount of power, increasing its overall power consumption.
[0004] To save energy, the terminal can periodically monitor the PDCCH with network devices using the connected discontinuous reception (CDRX) mode. During non-monitoring periods, the terminal enters sleep mode, thereby saving power consumption.
[0005] However, the periodic wake-up state of the terminal to monitor the PDCCH between the terminal and the network device still results in higher power consumption and energy consumption for the terminal. Summary of the Invention
[0006] This application provides a communication method, apparatus, and system that, in a connected discontinuous reception CDRX mode, monitors a first low-power wake-up signal (LP-WUS) at a first moment and a second LP-WUS at a second moment. The first moment is determined based on a first offset value associated with a long period, and the second moment is determined based on a second offset value associated with a short period. This facilitates the terminal's decision on whether to wake up to receive data. When the terminal does not detect LP-WUS, it remains in sleep mode and no longer periodically wakes up to monitor the PDCCH, reducing terminal power consumption, saving battery power, and improving the user experience.
[0007] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:
[0008] Firstly, a communication method is provided. This method can be executed by a terminal, or by a component configured in the terminal (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the terminal's functions. This application does not limit this. The following description uses a terminal as an example. The method includes:
[0009] In the connected discontinuous reception CDRX mode, a first LP-WUS is monitored at a first time point, which is determined based on a first offset value, and the first offset value is associated with the long period of CDRX. The first LP-WUS is used to trigger the terminal to wake up and monitor the physical downlink control channel (PDCCH) during the long period. A second LP-WUS is monitored at a second time point, which is determined based on a second offset value, and the second offset value is associated with the short period of CDRX. The second LP-WUS is used to trigger the terminal to wake up and monitor the PDCCH during the short period.
[0010] Based on the method described in the first aspect, the terminal determines a first time period based on a first offset value related to a long period, and monitors a first LP-WUS at the first time period. A second time period is determined based on a second offset value related to a short period, and a second LP-WUS is monitored at the second time period. If the first LP-WUS is detected, the terminal wakes up and monitors the PDCCH for the long period; if the first LP-WUS is not detected, the terminal enters a sleep state. If the second LP-WUS is detected, the terminal wakes up and monitors the PDCCH for the short period; if the second LP-WUS is not detected, the terminal enters a sleep state.
[0011] Compared with related technologies, when the first LP-WUS or the second LP-WUS is not detected, the terminal no longer needs to periodically wake up to monitor the PDCCH, which reduces the terminal's power consumption, saves the terminal's battery, and improves the user experience.
[0012] Furthermore, both long and short cycles are configured with associated offset values to determine their respective LP-WUS monitoring times. The terminal can determine the appropriate monitoring time not only within the long cycle using the offset value associated with the long cycle, but also within the short cycle using the offset value associated with the short cycle, thereby enabling effective monitoring of low-power wake-up signals within the short cycle.
[0013] In one possible implementation of the first aspect, the first moment is located before the long-cycle start moment, and the difference between the long-cycle start moment and the first moment is a first offset value; the second moment is located before the short-cycle start moment, and the difference between the short-cycle start moment and the second moment is a second offset value.
[0014] Therefore, the terminal can monitor LP-WUS at a first moment accurately determined using a first offset value associated with the long cycle within the long cycle. The terminal can also monitor LP-WUS at a second moment accurately determined using a second offset value associated with the short cycle within the short cycle. Thus, the terminal can effectively monitor LP-WUS before the start times of both the long and short cycles.
[0015] In one possible implementation of the first aspect, the method further includes: receiving first information from a network device; the first information includes a first offset value and a second offset value.
[0016] Therefore, the network device can send first information containing a first offset value and a second offset value to the terminal, which makes it easier for the terminal to monitor the low-power wake-up signal at the first and second moments according to the configured offset value, wake up the terminal in time, improve the accuracy of data reception, and reduce the power consumption of the terminal.
[0017] In one possible implementation of the first aspect, the second offset value is less than or equal to the first offset value.
[0018] Because the duration of a short cycle is shorter than that of a long cycle, the duration of the non-monitoring period in a short cycle is also shorter than that in a long cycle. Therefore, the offset value associated with a short cycle is relatively smaller compared to that associated with a long cycle. This allows the terminal to effectively monitor LP-WUS during the non-monitoring period of the short cycle.
[0019] In one possible implementation of the first aspect, the short period includes a monitoring period and a non-monitoring period, and the second offset value is less than the duration of the non-monitoring period of the short period.
[0020] Therefore, since the second offset value is less than the short-period non-monitoring period of CDRX, the time when the terminal monitors LP-WUS, determined based on the second offset value, falls within the non-monitoring period. This ensures that the terminal can be woken up promptly upon detecting LP-WUS, guaranteeing timely data reception and preventing data loss. Otherwise, it might be impossible to set the LP-WUS monitoring time during the non-monitoring period, or LP-WUS monitoring might be missed, resulting in the terminal failing to wake up and receiving data in a timely manner, leading to data loss.
[0021] In one possible implementation of the first aspect, if the terminal detects the second LP-WUS at the second moment, the terminal starts monitoring the PDCCH from the short cycle startup moment.
[0022] Therefore, when the terminal detects the second LP-WUS, it is woken up and begins monitoring the PDCCH; when it does not detect the second LP-WUS, it remains in sleep mode. Compared to related technologies, this allows the terminal to remain in sleep mode even when the second LP-WUS is not detected, eliminating the need for periodic wake-ups to monitor the PDCCH, thus reducing power consumption, saving battery power, and improving the user experience.
[0023] In one possible implementation of the first aspect, when the terminal detects the second LP-WUS at the second moment, the terminal enters the wake-up state at the short cycle startup moment and remains in the wake-up state for several consecutive short cycles thereafter.
[0024] Therefore, the terminal enters the wake-up state during the short-cycle startup, enabling it to receive data sent by network devices in a timely manner. This avoids delays caused by the time consumed during wake-up, which would prevent the terminal from being woken up in time and thus from receiving data from network devices, resulting in data loss and improving the accuracy of data reception by the terminal.
[0025] In one possible implementation of the first aspect, the terminal enters the wake-up state when it detects the second LP-WUS at the second moment, and remains in the wake-up state for several consecutive short cycles thereafter.
[0026] Therefore, when the terminal detects the second LP-WUS at the second moment, it enters the wake-up state, which can provide sufficient wake-up time. This avoids the situation where the terminal fails to wake up in time, and the network device starts sending data. If the terminal fails to wake up, it will be unable to receive data, resulting in data loss. This improves the accuracy of the terminal's data reception and reduces latency.
[0027] In one possible implementation of the first aspect, the terminal initiates an activation period at a short-cycle startup time; wherein, the period during which the terminal initiates monitoring of the PDCCH can be referred to as the activation period.
[0028] Therefore, upon detecting the second LP-WUS, the terminal initiates the activation period at the short-cycle startup time. The activation period coincides with the short-cycle monitoring period, the startup point of the activation period coincides with the short-cycle startup time, and the duration of the activation period coincides with the duration of the short-cycle monitoring period. The terminal does not actually start monitoring the PDCCH at the activation period startup point, but only starts monitoring the PDCCH at the third moment. This allows sufficient time for the terminal to wake up, preventing data loss if the network device starts sending data before the terminal wakes up in time, thus improving the accuracy of data reception.
[0029] In one possible implementation of the first aspect, if the terminal detects the second LP-WUS at the second time, it enters the wake-up state and monitors the PDCCH at the third time; wherein the offset value between the third time and the short cycle start time is a first difference value, and the first difference value is the difference between the first offset value and the second offset value.
[0030] Therefore, the terminal enters the wake-up state at the third moment and monitors the PDCCH, reserving enough time for the terminal to wake up and ensuring the accuracy of the data received by the terminal.
[0031] In one possible implementation of the first aspect, if the terminal detects the second LP-WUS at the second moment, it initiates the activation period at the third moment within a short period.
[0032] Therefore, the activation start point and the start of PDCCH monitoring occur at the same time, without needing to modify the relevant technical standards regarding the activation period and activation start point. This ensures compatibility with existing protocols and reduces implementation complexity.
[0033] In one possible implementation of the first aspect, the short-cycle activation period duration is a second difference, which is the difference between the short-cycle activation period duration configured by the network device and the first difference.
[0034] Therefore, when the second LP-WUS is detected, the activation point of the short cycle is the third moment, after the short cycle activation moment. The duration of the short cycle activation period is shorter than the duration of the short cycle monitoring period. The terminal actually starts monitoring the PDCCH during the short cycle activation period and goes into sleep mode during the short cycle inactive period.
[0035] In one possible implementation of the first aspect, the terminal includes a low-power wake-up receiver (LR) and a main radio receiver (MR); the terminal monitors a first LP-WUS and a second LP-WUS via the LR; if the LR monitors the first LP-WUS or the second LP-WUS, the MR is woken up and monitors the PDCCH.
[0036] Therefore, the terminal monitors the first LP-WUS and the second LP-WUS through the low-power LR, thereby reducing the power consumption of MR and the power consumption of the terminal.
[0037] Secondly, a communication method is provided, applied to a network device. The method includes: sending first information to a terminal; the first information includes a first offset value and a second offset value; wherein the first offset value is associated with a long period of a connected discontinuous reception (CDRX) mode, the first offset value is used to determine a first moment, the first moment is used to monitor a first LP-WUS, the first LP-WUS is used to trigger the terminal to be woken up and monitor the physical downlink control channel (PDCCH) within the long period; the second offset value is associated with a short period of CDRX, the second offset value is used to determine a second moment, the second moment is used to monitor a second LP-WUS, the second LP-WUS is used to trigger the terminal to be woken up and monitor the PDCCH within the short period.
[0038] In one possible implementation of the second aspect, the second offset value is less than or equal to the first offset value.
[0039] In one possible implementation of the second aspect, the short period includes a monitoring period and a non-monitoring period, and the second offset value is less than the duration of the non-monitoring period of the short period.
[0040] In one possible implementation of the second aspect, the method further includes: sending a first LP-WUS to the terminal; and sending a second LP-WUS to the terminal.
[0041] The second aspect is the implementation on the network device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.
[0042] Thirdly, a communication device is provided for use in a terminal, the device comprising: a module for performing the method of any of the above aspects and any possible implementation thereof.
[0043] Fourthly, a communication system is provided, comprising: a network device and a terminal, wherein the terminal is configured to execute the methods of the first aspect and any possible implementation thereof, and the network device is configured to execute the methods of the second aspect and any possible implementation thereof.
[0044] Fifthly, a communication device is provided, comprising: at least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement any of the above aspects and any possible implementation of the above aspects through logic circuits or execution code instructions.
[0045] Optionally, the communication device further includes a memory for storing program instructions. The processor is coupled to the memory via an interface.
[0046] In a sixth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions configured to perform a method of any of the foregoing aspects and any possible implementation thereof.
[0047] In a seventh aspect, a chip is provided, comprising: an interface circuit and a logic circuit, wherein the interface circuit is used to receive signals from other chips outside the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other chips outside the chip, and the logic circuit is used to implement any of the above aspects and any possible implementation of the above aspects.
[0048] Eighthly, a computer program product is provided, comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform any of the above aspects and any possible implementation thereof. Attached Figure Description
[0049] Figure 1 A schematic diagram of the CDRX cycle provided for related technologies;
[0050] Figure 2 A schematic diagram of a CDRX monitoring mechanism provided for related technologies;
[0051] Figure 3 This is a schematic diagram of a CDRX monitoring mechanism;
[0052] Figure 4 This application provides a schematic diagram of the architecture of a communication system.
[0053] Figure 5 A signaling interaction diagram of a communication method provided in an embodiment of this application;
[0054] Figure 6 This is a schematic diagram of a CDRX monitoring mechanism provided in an embodiment of this application;
[0055] Figure 7 This is a schematic diagram of another CDRX monitoring mechanism provided in an embodiment of this application;
[0056] Figure 8 This is a schematic diagram of another CDRX monitoring mechanism provided in an embodiment of this application;
[0057] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0058] Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation
[0059] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. "Multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items."
[0060] In embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0061] In the embodiments of this application, "and / or" 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, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0062] In the embodiments of this application, it should be noted that, unless otherwise explicitly specified and limited, the terms "set", "connected", and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection. Those skilled in the art can understand the specific meaning of the above terms in the embodiments of this application based on the specific circumstances.
[0063] The terminal can periodically monitor the PDCCH with network devices through the connected, discontinuous CDRX reception mode. See also... Figure 1 , Figure 1 This is a schematic diagram of a CDRX cycle provided for related technologies. For example... Figure 1 As shown, a CDRX cycle can be divided into a monitoring period and a non-monitoring period. During the monitoring period, the terminal is in a wake-up state and monitors the PDCCH between the terminal and the network device. During the non-monitoring period, the terminal is in a sleep state and does not monitor the PDCCH between the terminal and the network device, thus saving the terminal's power consumption.
[0064] The monitoring period can also be referred to as the monitoring time period. In this application, the name of the monitoring period is not limited.
[0065] The non-monitoring period can also be referred to as the non-monitoring period, dormancy period, or sleep period. In this application embodiment, the name of the non-monitoring period is not limited.
[0066] Furthermore, the CDRX cycle can be divided into long cycle and short cycle. Among them, the cycle length of the long cycle is longer than that of the short cycle.
[0067] Please see Figure 2 , Figure 2 A schematic diagram of a CDRX monitoring mechanism provided for related technologies. For example... Figure 2 As shown, the terminal monitors the PDCCH during the long monitoring period. When the terminal detects downlink control information (DCI) during the long period, it begins receiving data sent by the network device and converts the next period into a short period to continue monitoring the DCI and receiving data sent by the network device, as shown. Figure 2 The black area in the diagram illustrates this. If the terminal fails to detect the PDCCH within N consecutive short monitoring periods, the next period becomes a long period, and monitoring continues within that long period. Here, N can be configured by the network device, and N is a positive integer.
[0068] However, this method requires the terminal to remain awake to monitor DCI even during long or short monitoring periods, even if there is no data transmission. This increases the terminal's power consumption, drains its battery, and affects the user experience.
[0069] To further reduce terminal power consumption, one technical solution involves the terminal monitoring a low-power wake-up signal (LP-WUS) during long-term non-monitoring periods. The time at which the LP-WUS signal is monitored is the offset point preceding the long-term monitoring period.
[0070] Please see Figure 3 A schematic diagram of a CDRX monitoring mechanism is provided. (For example...) Figure 3 As shown, the terminal monitors LP-WUS at the offset value before the long-cycle startup time. If the terminal does not detect LP-WUS, it remains in sleep mode during the monitoring period and does not switch to wake-up mode. If the terminal detects LP-WUS, it enters wake-up mode during the monitoring period and monitors PDCCH.
[0071] However, Figure 3The proposed solution only monitors LP-WUS during long periods, while high power consumption still exists during short periods. Furthermore, the offset value corresponding to the long period is not applicable to the short period. One implementation could apply this offset to the short period. However, because the non-monitoring period is short, it's easy to miss LP-WUS detection during this short period, leading to missed LP-WUS detection and inability to wake up the terminal in time, resulting in missed data reception and other problems.
[0072] This application provides a communication method that enables a terminal to monitor LP-WUS during long-term and short-term non-monitoring periods. When the terminal detects LP-WUS during a long-term or short-term period, it switches to a wake-up state to monitor and receive data. When the terminal does not detect LP-WUS during a long-term or short-term period, it enters a sleep state and no longer monitors or receives data. This saves the terminal's power consumption, reduces power consumption, and improves the user experience.
[0073] and Figure 3 Compared to the methods shown, the communication method provided in this application's embodiments configures associated offset values for both the long and short periods to determine their respective LP-WUS monitoring times. This allows the terminal to determine a suitable monitoring time not only within the long period using the offset value associated with the long period, but also within the short period using the offset value associated with the short period. This effectively monitors low-power wake-up signals, further reducing terminal power consumption while avoiding issues such as missed LP-WUS detection leading to delayed terminal wake-up and missed data reception.
[0074] The following detailed explanation of the solution provided in this application, in conjunction with the corresponding flowcharts, illustrates the method. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminals, network devices) as examples of the execution entities for this interactive illustration, but this application does not limit the execution entities of the interactive illustrations. For example, the devices (e.g., terminals, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software capable of implementing all or part of the device's functions.
[0075] As a general statement, the message or signaling interactions involved in the interaction process of the embodiments of this application can be standard messages or signaling, or they can be newly introduced messages or signaling. The embodiments of this application do not make specific limitations on this.
[0076] The technical solutions provided in this application can be applied to various communication systems. These communication systems may include, but are not limited to, the following systems: Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), non-terrestrial network (NTN), 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems may include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not impose any limitations on this.
[0077] Please see Figure 4 , Figure 4 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 4 As shown, the communication system provided in this application embodiment may include: a network device 10 and a terminal 20. The network device 10 can send DCI and data information to the terminal 20 via PDCCH, and the terminal 20 is within the low-power wake-up signal coverage range of the network device 10.
[0078] The network device 10 described above can be a device capable of providing mobile communication access to the terminal. When the terminal 20 is in a connected state and the terminal 20 is within the coverage range of the low-power wake-up signal of the network device 10, the network device 10 can instruct the terminal 20 to monitor LP-WUS through radio resource control (RRC) signaling.
[0079] Network device 10 can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be macro base stations, micro base stations, or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.
[0080] In this application embodiment, the device for implementing the function of the network device can be the network device itself, or it can be any device capable of supporting the network device in implementing that function, such as a processor, circuit, chip, or chip system. This device can be installed in the network device or connected to and used with the network device. In the technical solution provided in this application, the example of a network device being used to implement the function of the network device is used to describe the technical solution provided in this application.
[0081] The terminal 20 in this application can be a wireless terminal capable of receiving scheduling and instruction information from network device 10. The wireless terminal 20 can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal 20 can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal 20 can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal 20 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), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal 20.
[0082] In this embodiment of the application, terminal 20 may include a main receiver (MR) and a low power wake-up receiver (LP-WUR).
[0083] Among them, MR is used to receive configuration information of CDRX configured by network device 10, monitor DCI, and receive data information sent by network device 10.
[0084] Among them, LP-WUR is a low-power receiver used to monitor LP-WUS.
[0085] In this embodiment, the device for implementing the function of terminal 20 can be a terminal or a device capable of supporting the terminal in implementing the function, such as a processor, circuit, chip, chip system, etc. This device can be installed in the terminal or connected to the terminal for use. In the technical solution provided in this application, a terminal is used as an example to describe the technical solution provided in this application.
[0086] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. They can be deployed in the same or different scenarios; for example, both can be deployed on land, or the access network device can be deployed on land while the terminal is deployed on water, etc., and so on.
[0087] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0088] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.
[0089] Below, embodiments of this application will be used to illustrate the concept of having Figure 4 Taking the terminal 20 and network device 10 shown in the diagram as examples, and in conjunction with the accompanying drawings and application scenarios, the communication method provided in this application embodiment will be described in detail. This method is executed by the network device and the terminal. The network device can be... Figure 4The network device 10 or a device within the network device 10. The terminal may be... Figure 4 The method is described using terminal 20 or the device within terminal 20. For simplicity, the method will be explained using the example of it being executed by a network device and a terminal.
[0090] Please see Figure 5 , Figure 5 This is a signaling interaction diagram of a communication method provided in an embodiment of this application. For example... Figure 5 As shown, the communication method provided in this application embodiment may include:
[0091] S101. In the connected state discontinuous CDRX reception mode, the terminal monitors the first LP-WUS at the first moment.
[0092] The first moment is determined based on the first offset value, which is associated with the long period of CDRX.
[0093] In some embodiments, the first moment is located before the long cycle start moment, and the difference between the long cycle start moment and the first moment is a first offset value. That is, the first moment is located before the long cycle start moment and is offset by the first offset value.
[0094] Since the start time of the long cycle is the beginning time of the long cycle monitoring period, it can also be understood that the first moment is before the start time of the long cycle monitoring period, and the difference between the start time of the long cycle monitoring period and the first moment is the first offset value. That is, the first moment is before the start time of the long cycle monitoring period and is offset by the first offset value.
[0095] Among them, the first offset value is related to the long period of CDRX, and the first offset value is less than the duration of the long period of CDRX monitoring.
[0096] In some embodiments, the first offset value is configured by the network device and sent to the terminal. In other embodiments, the first offset value is determined by the terminal based on a long-term non-monitoring period of CDRX. The embodiments of this application do not limit the configuration method of the first offset value.
[0097] In some embodiments, the first LP-WUS is used to trigger the terminal to wake up and monitor the PDCCH for a long period. If the first LP-WUS is detected, the terminal is woken up and monitors the PDCCH for a long period. If the first LP-WUS is not detected, the terminal remains in sleep mode and is not periodically woken up.
[0098] In the embodiments of this application, "terminal in sleep state" means that the high-power MR of the terminal is in sleep state, and "terminal in wake-up state" means that the high-power MR of the terminal is in wake-up state. When the MR is in sleep state, the terminal monitors the first LP-WUS through the low-power LR. After the terminal detects the first LP-WUS for itself, the MR is woken up and the terminal uses the MR to monitor the PDCCH.
[0099] S102, The terminal monitors the second LP-WUS at the second moment.
[0100] The second time step is determined based on the second offset value, which is related to the short period of CDRX.
[0101] The second time point is located before the short cycle start time point, and the difference between the short cycle start time point and the second time point is the second offset value. That is, the second time point is located before the short cycle start time point and is offset by the second offset value.
[0102] Since the short-cycle start time is the beginning time of the short-cycle monitoring period, it can also be understood that the second time is before the beginning time of the short-cycle monitoring period, and the difference between the beginning time of the short-cycle monitoring period and the second time is the second offset value. That is, the second time is before the beginning time of the short-cycle monitoring period and is offset by the second offset value.
[0103] In some embodiments, the second offset value is configured by the network device and sent to the terminal. In other embodiments, the second offset value is determined by the terminal based on a short-period non-monitoring period of CDRX. In still other embodiments, the second offset value is determined by the terminal based on the first offset value. This application does not limit the method of determining the value of the second offset value.
[0104] In some embodiments, the second LP-WUS is used to trigger the terminal to wake up and monitor the PDCCH for a short period. If the terminal detects the second LP-WUS, the terminal is woken up and monitors the PDCCH for a short period. If the terminal does not detect the second LP-WUS, the terminal remains in sleep mode.
[0105] In the embodiments of this application, when the MR is in sleep mode, the terminal monitors the second LP-WUS via low-power LR. After detecting the second LP-WUS for itself, the terminal wakes up the MR and uses the MR to monitor the PDCCH.
[0106] In some embodiments, the magnitudes of the first offset value and the second offset value are related to the subcarrier spacing.
[0107] In summary, the terminal can determine the first time point based on a first offset value related to the long period and monitor the first LP-WUS at that first time point. It can also determine the second time point based on a second offset value related to the short period and monitor the second LP-WUS at that second time point. When the first LP-WUS is detected, the terminal wakes up and monitors the PDCCH during the long period; when the first LP-WUS is not detected, the terminal enters a sleep state, effectively reducing the terminal's power consumption and improving the user experience.
[0108] And with Figure 3 Compared to the previous scheme, the terminal monitors the low-power wake-up signal not only during long-term non-monitoring periods but also during short-term non-monitoring periods. The communication method provided in steps S101-S102 enables the terminal to monitor the first LP-WUS at a first offset value before the start time of the long-term monitoring period and the second LP-WUS at a second offset value before the start time of the short-term monitoring period, ensuring that the terminal monitors the second LP-WUS during the short-term non-monitoring period. This avoids the terminal failing to detect the low-power wake-up signal when monitoring data during the short-term monitoring period, thus preventing it from being woken up in the next short period and thus failing to receive data information sent by the network device. Monitoring the second LP-WUS during the short-term non-monitoring period allows the terminal to be woken up promptly and receive data in a timely manner, improving the accuracy of data information reception.
[0109] In some embodiments of this application, the second offset value is less than the duration of the short-period non-monitoring period of CDRX.
[0110] exist Figure 3 In the illustrated scheme, since the offset value is configured for long periods, if this offset is applied to short periods, the non-monitoring time of the short period may be shorter than the offset. During this time, the terminal may be receiving data and therefore unable to monitor LP-WUS within the short period. This can easily lead to the terminal missing LP-WUS monitoring, failing to be woken up in time, and consequently, missing data reception. In this embodiment, the second offset value is less than the duration of the non-monitoring time of the short period of CDRX. This allows the terminal to set the LP-WUS monitoring time during the non-monitoring time, ensuring timely wake-up upon LP-WUS detection and preventing missed data reception. Otherwise, it may result in the inability to set the LP-WUS monitoring time during the non-monitoring time, or the failure to monitor LP-WUS, leading to the terminal failing to be woken up, failing to receive data in time, and missing data reception.
[0111] In other embodiments of this application, the second offset value is less than or equal to the first offset value.
[0112] In CDRX mode, the non-monitoring period of a longer period is longer than that of a shorter period. If the second offset value is greater than the first offset value, the terminal may start monitoring LP-WUS during the monitoring period of a shorter period. At this time, the terminal may be receiving data and therefore unable to monitor LP-WUS within the shorter period. This can easily lead to the terminal missing LP-WUS monitoring, failing to be woken up in time, and consequently, missing data reception. Therefore, in this embodiment, the second offset value is less than or equal to the first offset value, ensuring that the terminal can monitor LP-WUS during the non-monitoring period of a shorter period, thus better waking up the terminal to receive data. If the second offset value is greater than the first offset value, the time when the terminal monitors LP-WUS within the shorter period may fall within the monitoring period, causing the terminal to fail to be woken up and unable to receive data in time, resulting in missed data reception.
[0113] It should be understood that after the terminal is woken up, the actual time when the terminal starts monitoring the PDCCH can be the same as the short cycle startup time, as in the first implementation method below. The actual time when the terminal starts monitoring the PDCCH can also be different from the short cycle startup time, as in the second and third implementation methods below.
[0114] The following describes in detail the communication method provided in the embodiments of this application, using three specific implementation methods as examples.
[0115] Implementation method 1:
[0116] Please see Figure 6 , Figure 6 This is a schematic diagram of a CDRX monitoring mechanism provided in an embodiment of this application. Figure 6 As shown, the communication method provided in this application embodiment may include:
[0117] S201, The terminal monitors the first LP-WUS at the first moment.
[0118] This step S201 can be referred to the specific description in the aforementioned S101.
[0119] S202. If the terminal does not detect the first LP-WUS at the first moment, it shall remain in sleep state and continue to monitor the first LP-WUS at the first moment in the next long cycle.
[0120] Understandably, if the terminal does not detect the first LP-WUS targeting itself, it remains in sleep mode during both long monitoring periods and non-monitoring periods. The terminal does not periodically wake up during long monitoring periods, and it does not initiate PDCCH monitoring during long monitoring periods.
[0121] S203. If the terminal detects the first LP-WUS at the first moment, it switches to the wake-up state during the long-cycle startup time and begins monitoring the PDCCH. That is, if the first LP-WUS is detected, the terminal starts monitoring the DCI during the long-cycle startup time and receives data information sent by the network device.
[0122] The period during which the terminal initiates PDCCH monitoring can be referred to as the activation period. When the first LP-WUS is detected, the long-term activation period coincides with the long-term monitoring period, and the start point of the long-term activation period coincides with the start time of the long-term period. The terminal actually initiates PDCCH monitoring during the activation period.
[0123] During the activation period, the terminal can configure an onduration timer to time the duration of the activation period. The terminal starts the timer at the start point of either a long or short activation period to determine the duration of the activation period.
[0124] Specifically, upon detecting the first LP-WUS, the terminal wakes up and monitors the PDCCH during a long monitoring period, and then goes into sleep mode during a long non-monitoring period.
[0125] Upon detecting the first LP-WUS, the terminal will start a timer at the start point of the long-term activation period to time the duration of the long-term activation period.
[0126] S204. After the terminal finishes receiving data within the long period, it switches to sleep mode, changes the long period to a short period, and monitors the second LP-WUS at the second moment.
[0127] S205. If the terminal detects the second LP-WUS at the second moment, it enters the wake-up state at the short cycle startup moment and starts monitoring PDCCH.
[0128] In other words, when a second LP-WUS is detected targeting itself, the terminal starts monitoring DCI during the short-cycle startup and receives data information sent by the network device.
[0129] Thus, if the terminal does not detect the first LP-WUS, it remains in sleep mode and continues to monitor the first LP-WUS in the next long cycle. If the terminal detects the first LP-WUS, it is awakened and begins monitoring the PDCCH, then switches to a short cycle in the next cycle to monitor the second LP-WUS. If the terminal detects the second LP-WUS, it is awakened and begins monitoring the PDCCH; if it does not detect the second LP-WUS, it remains in sleep mode.
[0130] Compared with related technologies, the terminal can remain in sleep mode when the second LP-WUS is not detected, eliminating the need to wake the terminal to monitor the PDCCH, thus reducing the terminal's power consumption, saving battery power, and improving the user experience.
[0131] and Figure 3 Compared to the previous solution, this approach avoids the situation where the terminal cannot detect the low-power wake-up signal during short-cycle monitoring periods, thus failing to be woken up in the next short cycle and unable to receive data from the network device. By monitoring the second LP-WUS during short-cycle non-monitoring periods, the terminal can be woken up in time and receive data promptly, improving the accuracy of data reception.
[0132] In this embodiment, when a second LP-WUS is detected, the activation period of the short cycle coincides with the monitoring period of the short cycle, the start point of the activation period of the short cycle coincides with the start time of the short cycle, and the duration of the activation period of the short cycle coincides with the duration of the monitoring period of the short cycle. The terminal actually starts monitoring the PDCCH during the activation period.
[0133] In some embodiments, when a second LP-WUS is detected, the terminal wakes up and monitors the PDCCH during a short monitoring period, and sleeps during a short non-monitoring period.
[0134] In other embodiments, after detecting the second LP-WUS and entering a wake-up state during a short-cycle startup, the terminal may remain awake instead of entering a sleep state for several consecutive short cycles until its monitoring cycle switches from short to long, at which point it enters a sleep state. Compared to related technologies where the terminal enters a sleep state after receiving all the data within a short cycle, the communication method provided in this application can reduce the latency of the terminal monitoring the PDCCH and improve the accuracy of the data received by the terminal.
[0135] In some other embodiments, the terminal may also switch to a wake-up state when it detects the second LP-WUS at a second time. It may then remain in a wake-up state without entering a sleep state, continuing for several consecutive short cycles until its monitoring cycle changes from short to long, at which point it enters a sleep state. This ensures the terminal has sufficient wake-up time to receive data accurately and promptly, reducing latency.
[0136] S206. If the terminal does not detect the second LP-WUS at the second moment, it will detect the second LP-WUS at the second moment of the next short cycle.
[0137] Understandably, if the terminal does not detect a second LP-WUS targeting itself, it remains in sleep mode during both short monitoring and non-monitoring periods. The terminal does not periodically wake up during short monitoring periods, nor does it initiate PDCCH monitoring during these periods.
[0138] S207. If the terminal does not detect the second LP-WUS for N consecutive short cycles, the terminal's monitoring cycle is switched from short cycle to long cycle, and the wake-up state is switched to sleep state.
[0139] Wherein, N is a positive integer. N can be configured by network devices or by terminals. In this application embodiment, there are no limitations on the configuration size and configuration source of N.
[0140] In summary, the terminal monitors the first LP-WUS at the first moment of the long cycle and the second LP-WUS at the second moment of the short cycle. When the terminal detects the second LP-WUS, it is woken up and begins monitoring the PDCCH; when it does not detect the second LP-WUS, it enters a sleep state. Compared to related technologies, this method allows the terminal to remain in sleep mode even when the second LP-WUS is not detected, eliminating the need to wake the terminal to monitor the PDCCH. This reduces power consumption, saves battery power, and improves the user experience.
[0141] Furthermore, upon detecting the second LP-WUS at the second moment, the terminal enters a wake-up state and remains awake for several consecutive short cycles. Compared to related technologies where the terminal enters a sleep state after receiving data within a short cycle, the communication method provided in this application can reduce the latency of the terminal monitoring the PDCCH and improve the accuracy of the data received by the terminal.
[0142] Implementation Method Two:
[0143] Please see Figure 7 , Figure 7 This is a schematic diagram of another CDRX monitoring mechanism provided in an embodiment of this application. Step S205 described above can be replaced by, in the case where the terminal detects a second LP-WUS at a second time, as follows: Figure 7 As shown, at the third moment, the terminal enters the wake-up state and begins monitoring the PDCCH.
[0144] The offset between the third moment and the short cycle start moment is the first difference, which is the difference between the first offset and the second offset. That is, the third moment is the moment of the first difference before the short cycle start moment.
[0145] In addition, the duration of the terminal monitoring PDCCH in the short cycle is shortened to the second difference value, while the duration of the terminal in the short cycle activation period remains unchanged.
[0146] The second difference is the difference between the short-cycle activation period configured for the network device and the first difference.
[0147] In this scheme, if the terminal detects the second LP-WUS at the second moment, it can initiate the activation period and enter the wake-up state at the short-cycle startup moment, and start monitoring the PDCCH at the third moment. Compared with the first embodiment where the terminal enters the wake-up state and starts monitoring the PDCCH at the short-cycle startup moment, this scheme delays the start time of the terminal monitoring the PDCCH, reserving sufficient time for waking up the terminal, thereby improving the accuracy of the data information received by the terminal.
[0148] In this embodiment, when a second LP-WUS is detected, the short-cycle activation period coincides with the short-cycle monitoring period, the short-cycle activation start point coincides with the short-cycle start time, and the short-cycle activation period duration coincides with the short-cycle monitoring period duration. The terminal does not actually start monitoring the PDCCH at the activation start point, but only starts monitoring the PDCCH at the third moment. The terminal actually starts monitoring the PDCCH during the short-cycle activation period and sleeps during the short-cycle inactive period.
[0149] Furthermore, compared to Embodiment 1, the terminal does not need to remain in a wake-up state for several consecutive short cycles. The terminal can enter a sleep state after the short cycle activation period ends, thereby saving the terminal's power consumption.
[0150] Implementation method three:
[0151] Please see Figure 8 , Figure 8 This is a schematic diagram of another CDRX monitoring mechanism provided in an embodiment of this application. Step S205 described above can be replaced by, in the case where the terminal detects a second LP-WUS at a second time, as follows: Figure 8 As shown, at the third moment, the terminal enters the wake-up state and begins monitoring the PDCCH.
[0152] Furthermore, compared to Embodiment 1, the terminal's short cycle is shortened to the second difference value, and the duration of the terminal's short cycle PDCCH monitoring is also shortened to the second difference value. Compared to Embodiment 1, where the terminal initiates the activation period, enters the wake-up state, and begins monitoring the PDCCH at the start of the short cycle, this method delays the start time of the terminal being woken up and monitoring the PDCCH, reserving sufficient time for the terminal to wake up, thereby improving the accuracy of the data information received by the terminal.
[0153] In this embodiment, when the second LP-WUS is detected, the activation point of the short cycle is the third moment, after the short cycle activation moment. The duration of the short cycle activation period is shorter than the duration of the short cycle monitoring period. The terminal actually starts monitoring the PDCCH during the short cycle activation period and goes into sleep mode during the short cycle inactive period.
[0154] Compared with implementation method two, implementation method three involves the terminal waking up and the start of PDCCH monitoring occurring at the same time, without requiring modification of relevant technical standards, thus ensuring compatibility with existing protocols and reducing implementation complexity.
[0155] Based on the above description, the first offset value and the second offset value can be configured by the network device and sent to the terminal. Therefore, this application embodiment also provides a communication method applied to a network device, the method comprising:
[0156] The network device sends first information to the terminal. This first information includes a first offset value and a second offset value. The first offset value is associated with the long period of the connected discontinuous reception (CDRX) mode. The first offset value is used to determine a first time point. The first time point is used to monitor a first LP-WUS. The first LP-WUS is used to trigger the terminal to be woken up and monitor the Physical Downlink Control Channel (PDCCH) within the long period. The second offset value is associated with the short period of CDRX. The second offset value is used to determine a second time point. The second time point is used to monitor a second LP-WUS, which is used to trigger the terminal to be woken up and monitor the PDCCH within the short period.
[0157] Correspondingly, the terminal receives first information from the network device. This first information includes a first offset value and a second offset value. The first offset value is associated with the long period of the connected discontinuous reception (CDRX) mode. The first offset value is used by the terminal to determine a first moment. The first moment is used to monitor a first LP-WUS. The first LP-WUS is used to trigger the terminal to be woken up and monitor the Physical Downlink Control Channel (PDCCH) within the long period. The second offset value is associated with the short period of CDRX. The second offset value is used to determine a second moment. The second moment is used to monitor a second LP-WUS, which is used to trigger the terminal to be woken up and monitor the PDCCH within the short period.
[0158] In summary, network devices can send first information containing a first offset value and a second offset value to the terminal, thereby enabling the terminal to monitor the low-power wake-up signal at the first and second moments according to the configured offset value. This allows the terminal to wake up in a timely manner in both long and short periods, improving the accuracy of data reception and reducing terminal power consumption.
[0159] It should be understood that Figures 1 to 8The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 8 The examples in the document can be transformed into equivalent ways to obtain more implementations.
[0160] The above text combined Figures 1 to 8 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figure 9 and Figure 10 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.
[0161] In the embodiments described above, the terminal may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.
[0162] By way of example, embodiments of this application also provide a communication device.
[0163] Please see Figure 9 , Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
[0164] The communication device 500 may include a communication module 520. The communication module 520 can implement corresponding communication functions, which can be internal communication functions of the communication device 500 or communication functions between the communication device 500 and other devices. Optionally, the communication module 520 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 500 also includes a processing module 510. The processing module 510 can implement corresponding processing functions.
[0165] Optionally, the communication device 500 further includes a storage module, which can be used to store instructions and / or data; the processing module 510 can read the instructions and / or data in the storage module so that the communication device 500 can implement the aforementioned method embodiments.
[0166] In one possible design, the communication device 500 may correspond to the terminal in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the terminal. The communication device 500 can be used to execute the steps or processes performed by the terminal in any of the above method embodiments.
[0167] For example, in the connected discontinuous reception CDRX mode, the processing module 510 monitors the first LP-WUS at the first moment, which is determined based on the first offset value. The first offset value is associated with the long period of CDRX. The first LP-WUS is used to trigger the wake-up of the terminal and monitor the physical downlink control channel PDCCH during the long period.
[0168] The processing module 510 monitors the second LP-WUS at a second time, which is determined based on the second offset value. The second offset value is associated with the short cycle of CDRX. The second LP-WUS is used to trigger the wake-up terminal and monitor PDCCH within the short cycle.
[0169] For example, the first moment is before the start of the long cycle, and the difference between the start of the long cycle and the first moment is the first offset value; the second moment is before the start of the short cycle, and the difference between the start of the short cycle and the second moment is the second offset value.
[0170] For example, communication module 520 receives first information from a network device; the first information includes a first offset value and a second offset value.
[0171] For example, the second offset value is less than or equal to the first offset value.
[0172] For example, the short period includes both the monitoring period and the non-monitoring period, and the second offset value is less than the duration of the non-monitoring period in the short period.
[0173] For example, if a second LP-WUS is detected at the second time, the processing module 510 starts monitoring the PDCCH from the short cycle start time.
[0174] For example, if a second LP-WUS is detected at the second moment, the processing module 510 wakes up the terminal at the short cycle start moment and keeps the terminal in the wake-up state for several consecutive short cycles thereafter.
[0175] For example, when the processing module 510 detects the second LP-WUS at the second moment, it enters the wake-up state and remains in the wake-up state for several consecutive short cycles.
[0176] For example, the processing module 510 starts the activation period at the short cycle startup time and enters the wake-up state and monitors the PDCCH at the third time; wherein, the offset value between the third time and the corresponding short cycle startup time is the first difference value, which is the difference between the first offset value and the second offset value.
[0177] For example, when the processing module 510 detects the second LP-WUS at the second moment, the terminal starts the activation period at the third moment within the short cycle, and enters the wake-up state and monitors the PDCCH at the third moment; wherein, the offset value between the third moment and the short cycle start moment is the first difference value, and the first difference value is the difference between the first offset value and the second offset value.
[0178] For example, the short-cycle activation period duration is the second difference, which is the difference between the short-cycle activation period duration configured on the network device and the first difference.
[0179] For example, the terminal includes a low-power wake-up receiver (LR) and a main wireless receiver (MR);
[0180] The terminal monitors the first LP-WUS and the second LP-WUS via LR; the terminal is woken up and monitors the PDCCH, including the MR being woken up and monitoring the PDCCH.
[0181] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.
[0182] In one possible design, the communication device 500 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 500 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.
[0183] For example, the communication module 520 sends first information to the terminal; the first information includes a first offset value and a second offset value; wherein, the first offset value is associated with the long period of the connected discontinuous reception CDRX mode, the first offset value is used to determine a first moment, the first moment is used to monitor the first LP-WUS, the first LP-WUS is used to trigger the terminal to be woken up and monitor the physical downlink control channel PDCCH within the long period; the second offset value is associated with the short period of CDRX, the second offset value is used to determine a second moment, the second moment is used to monitor the second LP-WUS, the second LP-WUS is used to trigger the terminal to be woken up and monitor the PDCCH within the short period.
[0184] For example, the second offset value is less than or equal to the first offset value.
[0185] For example, the short period includes both monitoring and non-monitoring periods, and the second offset value is less than the duration of the non-monitoring period of the short period.
[0186] For example, communication module 520 sends a first LP-WUS to the terminal; communication module 520 sends a second LP-WUS to the terminal.
[0187] By way of example, embodiments of this application also provide a communication device.
[0188] Please see Figure 10 , Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application.
[0189] like Figure 10 As shown, the communication device 600 can be a chip, chip system, or processor, etc., used in a terminal or network device to implement the above methods. This communication device 600 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0190] The communication device 600 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 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 600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.
[0191] In an alternative design, the processor 610 may also store instructions and / or data, which can be executed by the processor 610 to cause the communication device 600 to perform the methods described in the above method embodiments.
[0192] In another alternative design, the communication device 600 may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 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.
[0193] Optionally, the communication device 600 may include one or more memories 630, which may store instructions that can be executed on the processor 610, causing the communication device 600 to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.
[0194] 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.
[0195] In one implementation, the communication device 600 may correspond to the terminal in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal.
[0196] In another implementation, the communication device 600 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.
[0197] 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.
[0198] 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.
[0199] 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.
[0200] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.
[0201] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal.
[0202] 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 network device or terminal in any of the foregoing method embodiments.
[0203] 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 network device or terminal in any of the foregoing method embodiments.
[0204] 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.
[0205] 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.
[0206] 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. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.
[0207] 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.
[0208] 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.
[0209] In summary, the above are merely preferred embodiments of the technical solutions of this application and are 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, Applied to a terminal, the method includes: In the connected discontinuous reception CDRX mode, a first low-power wake-up signal LP-WUS is monitored at a first moment. The first moment is determined based on a first offset value, which is associated with the long period of the CDRX. The first LP-WUS is used to trigger the wake-up of the terminal and monitor the physical downlink control channel PDCCH during the long period. The second LP-WUS is monitored at a second time point, which is determined based on a second offset value, which is associated with a short period of the CDRX; the second LP-WUS is used to trigger the wake-up of the terminal and monitor the PDCCH within the short period.
2. The method according to claim 1, characterized in that, The first moment is located before the long-cycle start moment, and the difference between the long-cycle start moment and the first moment is the first offset value; The second time point is located before the short cycle start time point, and the difference between the short cycle start time point and the second time point is the second offset value.
3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive first information from the network device; the first information includes the first offset value and the second offset value.
4. The method according to any one of claims 1-3, characterized in that, The second offset value is less than or equal to the first offset value.
5. The method according to any one of claims 1-4, characterized in that, The short period includes a monitoring period and a non-monitoring period, and the second offset value is less than the duration of the non-monitoring period of the short period.
6. The method according to claim 5, characterized in that, If the second LP-WUS is detected at the second time, the terminal starts monitoring the PDCCH from the short cycle start time.
7. The method according to claim 6, characterized in that, When the second LP-WUS is detected at the second moment, the terminal enters the wake-up state at the short cycle startup moment and remains in the wake-up state for a number of subsequent short cycles.
8. The method according to claim 6, characterized in that, The terminal enters a wake-up state when it detects the second LP-WUS at the second moment, and remains in the wake-up state for several consecutive short periods thereafter.
9. The method according to claim 5, characterized in that, The terminal initiates an activation period at the short-cycle startup time, and enters a wake-up state at the third time to monitor the PDCCH; The offset between the third time point and the corresponding short-cycle start time point is a first difference, which is the difference between the first offset and the second offset.
10. The method according to claim 5, characterized in that, If the second LP-WUS is detected at the second time, the terminal starts the activation period at the third time within the short period, and enters the wake-up state at the third time and monitors the PDCCH; The offset between the third time point and the short-cycle start time point is a first difference, which is the difference between the first offset and the second offset.
11. The method according to claim 10, characterized in that, The activation period duration of the short cycle is the second difference, which is the difference between the short cycle activation period duration configured by the network device and the first difference.
12. The method according to any one of claims 1-11, characterized in that, The terminal includes a low-power wake-up receiver (LR) and a main wireless receiver (MR). The terminal monitors the first LP-WUS and the second LP-WUS through the LR; The terminal being woken up and monitoring the PDCCH includes: the MR being woken up and monitoring the PDCCH.
13. A communication method, characterized in that, Applied to network devices, the method includes: Send first information to the terminal; the first information includes a first offset value and a second offset value; Wherein, the first offset value is associated with the long period of the connected discontinuous reception CDRX mode, the first offset value is used to determine the first moment, the first moment is used to monitor the first low power wake-up signal LP-WUS, and the first LP-WUS is used to trigger the terminal to be woken up and monitor the physical downlink control channel PDCCH within the long period. The second offset value is associated with a short period of the CDRX. The second offset value is used to determine a second moment. The second moment is used to monitor a second LP-WUS. The second LP-WUS is used to trigger the terminal to be woken up and monitor the PDCCH within the short period.
14. The method according to claim 13, characterized in that, The second offset value is less than or equal to the first offset value.
15. The method according to claim 12 or 13, characterized in that, The short period includes a monitoring period and a non-monitoring period, and the second offset value is less than the duration of the non-monitoring period of the short period.
16. The method according to any one of claims 13-15, characterized in that, The method further includes: Send the first LP-WUS to the terminal; The second LP-WUS is sent to the terminal.
17. A communication device, characterized in that, include: At least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 1-16 via logic circuits or execution code instructions.
18. A computer-readable storage medium, characterized in that, It includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-16.