State switching method, communication equipment and storage medium

Abstract

The invention provides a state switching method, communication equipment and a storage medium. The state switching method applied to a first communication node comprises the following steps: determining dormant state indication information based on a media access control (MAC) layer; and switching to a dormant state based on the dormant state indication information.

Description

State switching methods, communication devices and storage media Technical Field

[0001] This application relates to the field of communication technology, specifically to a state switching method, a communication device, and a storage medium. Background Technology

[0002] With the rapid development of mobile communication technology, the power consumption problem of User Equipment (UE) has become increasingly prominent. Existing energy-saving mechanisms mainly focus on idle and connected states, such as the Discontinuous Reception (DRX) mechanism. However, these mechanisms cannot fully balance power consumption and performance in certain scenarios. For example, when data load is low or services are inactive, a large amount of protocol stack configuration still needs to be maintained, leading to unnecessary energy consumption. Summary of the Invention

[0003] In view of this, embodiments of this application provide a state switching method, a communication device, and a storage medium, which effectively reduce the energy consumption of the physical layer.

[0004] This application provides a state switching method applied to a first communication node, including:

[0005] Determine the sleep state indication information based on the Media Access Control (MAC) layer;

[0006] Switch to sleep mode based on the sleep state indication information.

[0007] This application provides a state switching method applied to a second communication node, including:

[0008] Determine the sleep state indication information based on the Media Access Control (MAC) layer;

[0009] The hibernation state indication information is sent to the first communication node so that the first communication node switches to hibernation state based on the hibernation state indication information.

[0010] This application provides a state switching device applied to a first communication node, comprising:

[0011] The module is configured to determine sleep state indication information based on the Media Access Control (MAC) layer.

[0012] The switching module is configured to switch to a sleep state based on the sleep state indication information.

[0013] This application provides a state switching device applied to a second communication node, comprising:

[0014] The module is configured to determine sleep state indication information based on the Media Access Control (MAC) layer.

[0015] The switching module is configured to send the hibernation state indication information to the first communication node, so that the first communication node switches to hibernation state based on the hibernation state indication information.

[0016] This application provides a communication device, including: a memory, and one or more processors;

[0017] The memory is configured to store one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0019] This application provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in any of the above embodiments. Attached Figure Description

[0020] Figure 1 is a flowchart of a state switching method provided in an embodiment of this application;

[0021] Figure 2 is a flowchart of another state switching method provided in an embodiment of this application;

[0022] Figure 3 is a schematic diagram of switching between an active state and a dormant state provided in an embodiment of this application;

[0023] Figure 4 is a schematic diagram of another switching between an active state and a dormant state provided in an embodiment of this application;

[0024] Figure 5 is a structural block diagram of a state switching device provided in an embodiment of this application;

[0025] Figure 6 is a structural block diagram of another state switching device provided in an embodiment of this application;

[0026] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application will be described below with reference to the accompanying drawings. The examples given are for illustrative purposes only and are not intended to limit the scope of this application.

[0028] In existing 5G systems, the UE can control power consumption through Radio Resource Control (RRC) state transitions and Media Access Control (MAC) layer DRX mechanisms.

[0029] For RRC state transitions: a lot of signaling interaction is required, the transition process has high overhead and long latency; frequent switching may lead to resource waste, especially for small data transmission scenarios.

[0030] Regarding the DRX mechanism: although it reduces the receiver's operating time, it still needs to maintain a complete physical layer configuration; in low-load or intermittent service scenarios, the power consumption optimization effect is limited.

[0031] Therefore, this application proposes a new state switching method that, by implementing finer-grained power management at the MAC layer, further reduces physical layer power consumption while maintaining the protocol stack context, thus meeting the requirements for low power consumption and fast response.

[0032] In one embodiment, Figure 1 is a flowchart of a state switching method provided by an embodiment of this application. This embodiment is applied to the case of terminal sleep control based on the MAC layer in a 5G communication system. This embodiment can be applied to IoT scenarios, low-frequency service scenarios, and dynamic network environments, etc. This embodiment can be executed by a first communication node. As shown in Figure 1, this embodiment includes: S110-S120.

[0033] S110. Determine the sleep state indication information based on the MAC layer.

[0034] S120: Switch to sleep mode based on sleep mode indication information.

[0035] In one example, the sleep state refers to the low-power operation state of the first communication node in the wireless communication system. This can be achieved by selectively disabling certain physical layer (PHY) configurations and hardware modules, reducing power consumption while retaining basic network connectivity. Sleep state indication information is a specific type of information used to control and manage the first communication node's entry into sleep state; it can inform the first communication node of the time it enters sleep state and the wake-up time. In one example, the sleep state indication information may include: light sleep state indication information and deep sleep state indication information; whereby the light sleep state indication information instructs the first communication node to enter a light sleep state, and the deep sleep state indication information instructs the first communication node to enter a deep sleep state. After the first communication node obtains the MAC layer-based sleep state indication information, it can control itself to switch between sleep states based on the sleep state indication information to reduce power consumption. This allows the first communication node to achieve efficient and flexible power management while ensuring service continuity and communication quality.

[0036] The hibernation state indication information in the embodiments of this application may also be referred to as hibernation state indication configuration or hibernation state configuration, and there is no limitation thereto.

[0037] In one embodiment, determining sleep state indication information based on the MAC layer includes one of the following:

[0038] Receive sleep state indication information based on the MAC layer configured by the second communication node;

[0039] The first communication node negotiates and configures MAC-layer-based sleep state indication information with the second communication node. In one example, the second communication node can directly configure the MAC-layer-based sleep state indication information and then send it to the first communication node. In another example, the first and second communication nodes can negotiate and configure the MAC-layer-based sleep state indication information.

[0040] In one embodiment, the sleep state indication information includes at least one of the following: sleep state type; sleep state duration; physical layer configuration retention indication information; and wake-up trigger condition. In one example, the sleep state type is used to characterize which sleep state the first communication node is about to enter; the sleep state duration is used to define the duration of the sleep state; the physical layer configuration retention indication information is used to indicate the physical layer configuration that needs to be retained; and the wake-up trigger condition is used to define the trigger condition for waking up the first communication node.

[0041] In one embodiment, the wake-up trigger condition includes at least one of the following: a sleep timer expires; uplink or downlink data arrives; a system information update indication; or an uplink data request triggered by a user operation. In one example, sleep timer expiration means the sleep timer finishes counting down, triggering the wake-up of the first communication node. In one example, uplink or downlink data arrival means the second communication node indicates the presence of downlink data or the first communication node triggers an uplink data request. In one example, a system information update indication means the first communication node acquires new system information or parameter configurations based on its own needs or based on instructions sent by the second communication node. In one example, the wake-up trigger condition further includes: a high-priority service transmission requirement; if the second communication node detects a high-priority urgent service requirement, it can send a rapid wake-up indication message.

[0042] In one embodiment, before determining the sleep state indication information based on the MAC layer, the method further includes: determining sleep state bearer signaling based on the Radio Resource Control (RRC) layer. In one example, the sleep state bearer signaling is used to ensure the context synchronization required for the first communication node to switch to a sleep state, ensuring that the remaining MAC and PHY configuration retention lists between the first and second communication nodes are consistent. The first communication node can send its own sleep state support capabilities to the second communication node, and the second communication node can configure the sleep state bearer signaling based on the first communication node's sleep state support capabilities.

[0043] In one embodiment, determining the sleep state bearer signaling based on the RRC layer includes one of the following:

[0044] Receive the sleep state bearer signaling configured by the second communication node at the RRC layer;

[0045] Negotiate and configure the sleep state bearer signaling of RRC with the second communication node.

[0046] In one embodiment, the sleep state bearer signaling includes at least one of the following: sleep state type; sleep state duration; physical layer configured retention indication information; and wake-up trigger condition. In one example, multiple selectable values ​​for at least one of the following indicators—sleep state type, sleep state duration, physical layer configured retention indication information, and wake-up trigger condition—can be configured through the sleep state bearer signaling. For example, the sleep state duration can be configured to include 5 milliseconds (ms), 10 ms, and 20 ms; correspondingly, the sleep state duration included in the sleep state indication information can be 5 ms. Alternatively, the sleep state type can be configured as a first type of sleep state or a second type of sleep state through the sleep state bearer signaling, and the sleep state duration included in the sleep state indication information can be the first type of sleep state; or the sleep state type can be configured as a second type of sleep state through the sleep state bearer signaling, and the sleep state duration included in the sleep state indication information can be the duration of the second type of sleep state.

[0047] In one embodiment, switching to a sleep state based on sleep state indication information includes at least one of the following:

[0048] Store the active physical layer configuration as a physical layer context;

[0049] Based on the reservation indication information configured in the physical layer, the radio frequency link, Channel State Information (CSI) measurement operation, and Sounding Reference Sign (SRS) transmission operation are selectively disabled.

[0050] A sleep timer is started based on the duration of the sleep state. In one example, after the first communication node enters a sleep state, it can store the active PHY configuration as a physical layer context. In another example, after the first communication node enters a sleep state, it can shut down unnecessary modules, such as selectively shutting down high-power modules like the RF link, CSI measurement function, and SRS transmission function based on the reserved information of the physical layer configuration. In yet another example, after the first communication node enters a sleep state, it can start a sleep timer and set the sleep timer's duration to the same value as the sleep state duration. In one example, after the first communication node enters a sleep state, it can combine the above operations without limitation.

[0051] In one embodiment, the state switching method applied to the first communication node further includes:

[0052] A hibernation state confirmation message is sent to the second communication node; the hibernation state confirmation message includes: a hibernation state switch success indication and the actual retained physical layer configuration. After the first communication node enters hibernation, the first communication node can send a hibernation state confirmation message to the second communication node to notify the second communication node that the first communication node has successfully entered hibernation.

[0053] In one embodiment, the sleep state type includes at least one of the following: a first type of sleep state; a second type of sleep state; wherein the second type of sleep state is more energy-efficient than the first type of sleep state. In one example, from an energy consumption perspective, when the first communication node is in the second type of sleep state, its energy consumption is lower than when it is in the first type of sleep state. In one example, from a sleep duration perspective, when the first communication node is in the second type of sleep state, its sleep duration is longer than when it is in the first type of sleep state. Exemplarily, the first type of sleep state can be a light sleep state, and correspondingly, the second type of sleep state is a deep sleep state. Exemplarily, the first type of sleep state can be a short-term sleep state (referred to as short-time sleep), and correspondingly, the second type of sleep state is a long-term sleep state (referred to as long-time sleep). In one example, short-term sleep is suitable for short periods of business idleness or intermittent data transmission scenarios, preserving more PHY configuration to support fast wake-up; long-term sleep is suitable for scenarios with long periods of no data interaction, shutting down more modules to achieve deep energy saving.

[0054] In one embodiment, when in a first type of sleep state, the MAC context is preserved, and the physical layer retains the configuration for processing the common physical layer.

[0055] In the second type of sleep state, the MAC context is retained, and the physical layer retains the relevant configurations for handling system information and paging messages. In one example, the MAC context may include, but is not limited to, one of the following: Hybrid Automatic Repeat Request (HARQ); Power Headroom Report (PHR); Buffer Status Report (BSR); and DRX. In one example, when the first communication node is in the first type of sleep state, the retained common physical layer configurations include: common physical layer configurations for the idle state and common physical layer configurations for the connected state. In one example, when the first communication node is in the second type of sleep state, the physical layer retains the common physical layer configurations for the idle state and the relevant MAC layer configurations, i.e., retains the configurations relevant to handling system information and paging messages.

[0056] In one embodiment, switching to a sleep state based on sleep state indication information includes one of the following:

[0057] The hibernation state is switched from the first type of hibernation state to the second type of hibernation state based on the hibernation state indication information;

[0058] Switching from the second type of hibernation state to the first type of hibernation state based on hibernation state indication information;

[0059] Based on the hibernation state indication information, the system switches from the active state to the first type of hibernation state;

[0060] Based on the hibernation state indication information, the system switches from the active state to the second type of hibernation state.

[0061] In one embodiment, when switching from a first type of hibernation state to a second type of hibernation state, a first type of operation is performed; the first type of operation includes at least one of the following:

[0062] The process involves: saving the first type of sleep configuration; disabling the RF link; stopping time-frequency synchronization maintenance; stopping listening to the downlink control channel; disabling SRS transmission and CSI measurement functions; starting a second type of sleep timer; stopping listening to the common search space; stopping listening to the dedicated search space; and disabling the data processing unit. In one example, saving the first type of sleep configuration means storing the PHY configuration and PHY context information in the first type of sleep state to low-power memory; starting the second type of sleep timer means starting a deep sleep timer, setting the second type of sleep timer's duration to the same value as the sleep state duration, and automatically triggering wake-up after timeout. In one example, after the first communication node enters the second type of sleep state, it can disable more unnecessary modules, such as disabling the RF link, stopping time-frequency synchronization maintenance, stopping listening to the downlink control channel, disabling SRS transmission, and disabling CSI measurement functions—all high-power modules. In another example, after the first communication node enters the second type of sleep state, it can stop listening to the common search space, stop listening to the dedicated search space, and disable the data processing unit—all high-power operations.

[0063] In one embodiment, when switching from a second type of hibernation state to a first type of hibernation state, a second type of operation is performed; the second type of operation includes at least one of the following:

[0064] The process involves: restoring the RF link; rebuilding time-frequency synchronization maintenance; enabling the listening downlink control channel; restoring the SRS configuration; and retaining some antenna configurations. In one example, restoring the RF link means restarting the RF module and establishing a basic physical connection; rebuilding time-frequency synchronization maintenance means regaining time and frequency synchronization through the primary synchronization signal (PSS) and secondary synchronization signal (SS); in another example, after the first communication node switches from a second-type sleep state to a first-type sleep state, the first communication node can restore the first-type sleep configuration, i.e., load the previously stored PHY configuration and PHY context information from the first-type sleep state, and activate some functions: enabling the listening downlink control channel; restoring the SRS configuration; and retaining some antenna configurations. In one example, the downlink control channel can be the Physical Downlink Control Channel (PDCCH), enabling PDCCH listening to receive network commands; restoring the SRS configuration to support uplink measurements; and retaining some antenna configurations, which means retaining some power-optimized antenna configurations.

[0065] In one embodiment, the first communication node is in a first type of sleep state, and the sleep state indication information further includes: a first type of data transmission support capability; the state switching method applied to the first communication node further includes:

[0066] A reserved public channel is used to transmit first-type data to a second communication node; wherein the amount of first-type data is less than a data volume threshold. Exemplarily, first-type data can also be referred to as small data. In one example, first-type data refers to relevant data with a data volume less than the data volume threshold, or it can be relevant data that occurs and is transmitted occasionally. In one example, if the first communication node supports the capability to transmit first-type data, the first communication node can use a reserved public channel to transmit the first-type data to the second communication node.

[0067] In one embodiment, for a first type of sleep state, the reserved list configured by the physical layer includes one of the following: system information; synchronization signal processing; random access parameters; and common search space.

[0068] In one embodiment, switching to a sleep state based on sleep state indication information includes:

[0069] If the first hibernation state switching trigger condition is met, the system switches to hibernation state based on the hibernation state indication information.

[0070] In one embodiment, for the first communication node, the first sleep state switching trigger condition includes one of the following: the actual remaining power is less than the power threshold; the service prediction model determines it to be a first type of load scenario; the actual hardware temperature is greater than the temperature threshold; the load in the first type of load scenario is less than the load threshold. In one example, the first type of load scenario can also be referred to as a low load scenario.

[0071] In one embodiment, the state switching method applied to the first communication node further includes: determining a wake-up trigger event based on the MAC layer; and switching from a dormant state to an active state based on the wake-up trigger event.

[0072] In one embodiment, determining a wake-up trigger event based on the MAC layer includes:

[0073] Receive wake-up indication information based on the MAC layer configured by the second communication node;

[0074] Negotiate and configure wake-up indication information based on the MAC layer with the second communication node.

[0075] In one embodiment, the wake-up indication information includes at least one of the following: wake-up type; wake-up reason; duration of active state; and physical layer configuration update indication information.

[0076] In one embodiment, the state switching method applied to the first communication node further includes: sending a hibernation exit message to the second communication node, so that the second communication node confirms, based on the hibernation exit message, that the first communication node has exited the hibernation state and returned to the active state. In one example, after the first communication node exits the hibernation state, the first communication node may send a hibernation exit message to the second communication node so that the second communication node knows that the first communication node has exited the hibernation state and returned to the active state.

[0077] In one embodiment, Figure 2 is a flowchart of another state switching method provided by an embodiment of this application. This embodiment is applied to the case of terminal sleep control based on the MAC layer in a 5G communication system. This embodiment can be executed by a second communication node. As shown in Figure 2, this embodiment includes: S210-S220.

[0078] S210. Determine the sleep state indication information based on the MAC layer.

[0079] S220. Send the hibernation state indication information to the first communication node so that the first communication node switches to hibernation state based on the hibernation state indication information.

[0080] In one embodiment, determining sleep state indication information based on the MAC layer includes one of the following:

[0081] Pre-configure sleep state indication information based on the MAC layer;

[0082] Negotiate and configure sleep state indication information based on the MAC layer with the first communication node.

[0083] In one embodiment, the hibernation state indication information includes at least one of the following: hibernation state type; hibernation state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0084] In one embodiment, the wake-up trigger condition includes at least one of the following: the sleep timer expires; uplink or downlink data arrives; system information update indication; uplink data request triggered by user operation.

[0085] In one embodiment, the state switching method applied to the second communication node further includes:

[0086] Determine the signaling bearer for the sleep state based on the Radio Resource Control (RRC) layer;

[0087] The hibernation state bearer signaling is sent to the first communication node so that the first communication node can perform negotiation and configuration of hibernation state indication information based on the MAC layer based on the hibernation state bearer signaling.

[0088] In one embodiment, determining the sleep state bearer signaling based on the RRC layer includes one of the following:

[0089] Pre-configured RRC layer sleep state bearer signaling;

[0090] Negotiate and configure the sleep state bearer signaling of the RRC layer with the first communication node.

[0091] In one embodiment, the sleep state carrying signaling includes at least one of the following: sleep state type; sleep state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0092] In one embodiment, switching to a sleep state based on sleep state indication information includes at least one of the following:

[0093] Store the active physical layer configuration as a physical layer context;

[0094] Based on the reservation indication information configured in the physical layer, the radio frequency link, the channel state information (CSI) measurement function, and the sounding reference signal (SRS) transmission function are selectively disabled.

[0095] The hibernation timer is started based on the duration of the hibernation state.

[0096] In one embodiment, the state switching method applied to the second communication node further includes:

[0097] Receive a hibernation state confirmation message sent by the first communication node; wherein the hibernation state confirmation message includes: hibernation state switching success indication information and the actual retained physical layer configuration.

[0098] In one embodiment, the hibernation state type includes at least one of the following: a first type of hibernation state; a second type of hibernation state; wherein the second type of hibernation state is more energy-efficient than the first type of hibernation state.

[0099] In one embodiment, when in a first type of sleep state, the MAC context is preserved, and the physical layer retains the configuration for processing the common physical layer.

[0100] In the second type of hibernation state, the MAC context is preserved, and the physical layer retains the relevant configurations for handling system information and paging messages.

[0101] In one embodiment, switching to a sleep state based on sleep state indication information includes one of the following:

[0102] The hibernation state is switched from the first type of hibernation state to the second type of hibernation state based on the hibernation state indication information;

[0103] Switching from the second type of hibernation state to the first type of hibernation state based on hibernation state indication information;

[0104] Based on the hibernation state indication information, the system switches from the active state to the first type of hibernation state;

[0105] Based on the hibernation state indication information, the system switches from the active state to the second type of hibernation state.

[0106] In one embodiment, when switching from a first type of hibernation state to a second type of hibernation state, a first type of operation is performed; the first type of operation includes at least one of the following:

[0107] Save the first type of sleep configuration; shut down the RF link; stop time-frequency synchronization maintenance; stop monitoring the downlink control channel; disable SRS transmission and CSI measurement functions; start the second type of sleep timer; stop monitoring the common search space; stop monitoring the dedicated search space; disable the data processing unit function.

[0108] In one embodiment, when switching from a second type of hibernation state to a first type of hibernation state, a second type of operation is performed; the second type of operation includes at least one of the following:

[0109] Restore the radio frequency link; rebuild time and frequency synchronization maintenance; enable the monitoring downlink control channel; restore SRS configuration; retain some antenna configurations.

[0110] In one embodiment, the first communication node is in a first type of sleep state, and the sleep state indication information further includes: first type of data transmission support capability; the state switching method applied to the second communication node further includes:

[0111] The first type of data transmitted by the first communication node is received using a reserved public channel; wherein the amount of the first type of data is less than the data amount threshold.

[0112] In one embodiment, for a first type of sleep state, the reserved list configured by the physical layer includes one of the following: system information; synchronization signal processing; random access parameters; and common search space.

[0113] In one embodiment, the state switching method applied to the second communication node further includes: triggering the first communication node to switch to a sleep state based on a second sleep state switching trigger condition.

[0114] In one embodiment, for the second communication node, the second sleep state switching trigger condition includes one of the following: the downlink buffer data volume is less than the data volume threshold; the duration of inactive service reaches a preset duration threshold; or the load balancing demand changes.

[0115] In one embodiment, the state switching method applied to the second communication node further includes:

[0116] Determine the wake-up trigger event based on the MAC layer;

[0117] Switching from a dormant state to an active state based on a wake-up trigger event.

[0118] In one embodiment, determining a wake-up trigger event based on the MAC layer includes:

[0119] Pre-configure wake-up indication information based on the MAC layer;

[0120] Negotiate and configure wake-up indication information based on the MAC layer with the first communication node.

[0121] In one embodiment, the wake-up indication information includes at least one of the following: wake-up type; wake-up reason; duration of active state; and physical layer configuration update indication information.

[0122] In one embodiment, the state switching method applied to the second communication node further includes:

[0123] Receive the hibernation exit message sent by the first communication node;

[0124] The first communication node exits the dormant state and returns to the active state based on the dormant state exit message.

[0125] It should be noted that the explanations of parameters such as sleep state indication information, sleep state type, sleep state duration, physical layer configuration retention indication information, and wake-up trigger conditions in the state switching method applied to the second communication node can be found in the explanations of the corresponding parameters in the state switching method applied to the first communication node, and will not be repeated here.

[0126] In the following embodiments, the first communication node is the terminal, the second communication node is the network side, the first type of sleep state is the Light_Sleep state, and the second type of sleep state is the Deep_Sleep state. The process of state switching is described.

[0127] Figure 3 is a schematic diagram illustrating the switching between an active state and a sleep state according to an embodiment of this application. As shown in Figure 3, after receiving a sleep state indication message, the system enters a sleep state; after receiving a wake-up indication message, it enters an active state.

[0128] Figure 4 is a schematic diagram illustrating the switching between an active state and a sleep state provided in another embodiment of this application. As shown in Figure 4, the sleep state includes a Light_Sleep state and a Deep_Sleep state. When in the active state, if a light sleep state indication is received, it enters the Light_Sleep state; if a deep sleep state indication is received, it enters the Deep_Sleep state. When in the Light_Sleep state, if a wake-up indication is received, it enters the active state; if a deep sleep state indication is received, it enters the Deep_Sleep state. When in the Deep_Sleep state, if a light sleep state indication is received, it enters the Light_Sleep state; if a wake-up indication is received, it enters the active state.

[0129] Example 1

[0130] This embodiment provides a specific implementation of the Light_Sleep state based on the MAC layer. This embodiment describes in detail the control flow, signaling interaction, PHY configuration filtering and status confirmation process between the network side and the terminal side.

[0131] The Light_S leep state transition process includes the following parts:

[0132] Part 1. Preparatory Work:

[0133] Regarding configuration parameter preparation: Both the network side and the terminal have their respective Light_Sleep parameters pre-configured, including:

[0134] The threshold for entering the Light_Sleep state is (e.g., the downlink cache data volume is less than the data volume threshold, the duration of inactive service reaches a preset duration threshold, the actual remaining battery power of the terminal is less than the battery power threshold, etc.).

[0135] Media Access Control - Control Element (MAC CE) field definitions: Sleep status indicator, sleep duration, retained PHY configuration flags, allowed wake-up reasons, etc.

[0136] The PHY configuration retain list: determines the system information, synchronization signal processing, and common search space that need to be retained in the Light_Sleep state.

[0137] Regarding context synchronization: Before entering the Light_Sleep state, the network side and the terminal complete the necessary context synchronization through RRC or other control signaling (such as semantic or intent-based interaction based on the agent) to ensure that both parties agree on the remaining MAC configuration and PHY configuration retention lists.

[0138] RRC signaling interaction: The network side sends an RRC connection reconfiguration message to the terminal side;

[0139] Context synchronization items include: (1) Security context: integrity protection key synchronization; encryption key update identifier; counter initial value; (2) Status parameters: Packet Data Convergence Protocol (PDCP) sequence number range; Radio Link Control (RLC) window size; HARQ process configuration; timer parameter group;

[0140] Measurement configuration synchronization includes: dormant measurement cycle; set of measurement objects; report configuration thresholds; and event triggering conditions.

[0141] Resource reservation includes: periodic configuration of scheduling request (SR) resources; pre-allocation of physical uplink control channel (PUCCH) resources; allocation of channel state information reference signal (CSI-RS) resources; and sleep paging parameters.

[0142] The detailed scheme for negotiation-based context synchronization includes: the capability exchange phase and the parameter negotiation process;

[0143] The parameter negotiation process includes the following steps: Step 1: UE sends capability information; Step 2: Network proposes initial configuration; Step 3: UE responds with acceptance / adjustment suggestions; Step 4: Network confirms final configuration.

[0144] Part 2. Network-side processes include:

[0145] The network-side process includes the following parts:

[0146] Part 21, State Detection and Trigger Judgment: The network side continuously monitors the UE's service activity and downlink cached data status. When the cached data volume is detected to be lower than a preset threshold and the service inactivity time exceeds t1, the Light_Sleep state transition is triggered.

[0147] Part 22, Generating a Sleep Indicator: The network side constructs and sends a sleep indicator MAC CE, the format of which includes the following information:

[0148] Sleep State Type (CE Type): Indicates the current state is Light_Sleep;

[0149] Duration of hibernation: Recommended duration of hibernation;

[0150] Physical layer configuration retention indication information (Config_Retain): identifies the list of PHY configurations that need to be retained (e.g., information that needs to be retained and synchronization processing configuration);

[0151] Wake-up trigger condition (Wake_Cause): Allowed wake-up reasons (such as emergency call, timed wake-up, etc.);

[0152] Reserved: Reserved field.

[0153] Part 23, Status Update and Recording: After sending MAC CE, the network side updates the UE's context record, marks the expected entry into the Light_Sleep state, and starts the corresponding monitoring timer to trigger the wake-up or error recovery process when necessary.

[0154] Part 3. Terminal-side process:

[0155] The terminal-side process includes the following parts:

[0156] Part 31, Receiving and parsing MAC CE: After receiving the sleep instruction MAC CE, the terminal side parses the instruction, confirms that the Light_Sleep state transition needs to be performed, and extracts the corresponding sleep duration and retention configuration requirements.

[0157] Section 32, PHY Configuration Filtering: Based on the list of retained configurations and its own hardware resources, the terminal side selectively retains necessary PHY configuration items: system information decoding related configurations; synchronization signal processing; common physical layer configurations.

[0158] The unreserved portion enters a low-power sleep state and shuts down the corresponding data processing unit.

[0159] Part 33: Notify the PHY layer to perform configuration adjustments: The terminal sends instructions to the PHY layer through the interface between the MAC and PHY to perform necessary module deactivation operations, retaining only the selected core configurations, while other modules enter a sleep state to reduce power consumption.

[0160] Part 34, Status Confirmation Feedback: After the terminal completes the configuration adjustment, it generates a status confirmation message (e.g., MAC LevelStatus Confirmation) and sends it back to the network side. This message may contain information about the actual retained configuration items, the current status flag, and possible exception information (such as configuration failure or insufficient resources).

[0161] Part 35, Entering Light Sleep State: After the state is confirmed, the terminal enters a lightweight sleep state. At this time:

[0162] The MAC layer maintains complete context information to quickly respond to subsequent operations;

[0163] The PHY layer is used only for critical signal processing and a small amount of synchronization processing; other modules are in a low-power sleep state.

[0164] Part 4. Wake-up Process and Exception Handling:

[0165] The wake-up process and exception handling include the following parts:

[0166] Part 41, Wake-up Trigger: When an external trigger condition is detected (such as receiving a wake-up command from the upper layer, detecting a service activation requirement, or a timer timeout), the terminal or network side initiates a wake-up operation.

[0167] Part 42, Fast Recovery: The terminal begins to gradually restore the full configuration of the PHY layer according to its internal state management mechanism.

[0168] First, reactivate the non-reserved modules;

[0169] Then, a rapid synchronization is performed with the network side to ensure that the MAC layer and PHY layer states are consistent.

[0170] Finally, the MAC layer state is updated to active, and normal data transmission is restored.

[0171] Section 43, Anomaly Handling: If an error occurs during state transition or recovery, such as delayed state confirmation, configuration synchronization failure, or signaling loss, the terminal can automatically exit Light_Sleep through the anomaly detection module, trigger a full recovery process, or request the network side to reissue the relevant configuration instructions.

[0172] This embodiment achieves rapid entry into a low-power state in inactive scenarios through refined MAC layer control and PHY configuration filtering. In the Light_Sleep state, the terminal retains its core communication context, ensuring rapid wake-up, while significantly reducing the PHY processing burden, thus achieving energy savings. The entire process encompasses network-side triggering, command issuance, terminal-side parsing and configuration adjustment, as well as subsequent wake-up and anomaly recovery measures, ensuring high robustness in practical applications.

[0173] Example 2

[0174] This embodiment provides a specific implementation of the Deep_Sleep state based on the MAC layer. This embodiment details the control flow, signaling interaction, PHY configuration filtering, and status confirmation process between the network side and the terminal side. It includes the following parts:

[0175] Part 1. Definition and applicable scenarios of Deep_S sleep state:

[0176] Deep_S leep is a more advanced energy-saving state than Light_S leep, and is suitable for the following scenarios:

[0177] Prolonged periods of inactivity: such as long periods without data transmission or intermittent low-frequency services;

[0178] Terminal battery is too low: If the actual remaining battery is lower than a certain threshold, i.e., the battery threshold (e.g., the battery threshold can be 10%).

[0179] Heavy network load: Allows terminals to reduce signaling interaction and physical layer processing for extended periods;

[0180] Low-frequency information reporting scenarios for IoT devices: such as the periodic data collection and transmission of environmental monitoring equipment.

[0181] In the Deep_Sleep state, the terminal will further disable more physical layer modules, retaining only basic time synchronization and a very small amount of necessary physical layer context information to minimize power consumption, while allowing the network side to trigger the terminal to wake up through specific events.

[0182] Part 2. Deep_S leep state transition process

[0183] Part 2.1 Network-side procedures; the network-side procedures include the following parts:

[0184] Part 211, Status Detection and Trigger Judgment: The network side monitors the UE's active status and determines whether the following conditions are met:

[0185] The downlink buffer has very low or zero data volume, and the duration exceeds T2 (e.g., 10 seconds);

[0186] Historical business data analysis shows a high probability (e.g., over 90%) of no active business in the short term, which can also be understood as the duration of business inactivity reaching a preset time threshold.

[0187] The network load is low, allowing the terminal to sleep for extended periods.

[0188] Part 212, generating sleep state indication information based on MAC CE: The network side constructs and sends Deep_Sleep state indication information based on MAC CE, the format of which is as follows:

[0189] CE Type: Indicates the current state is Deep_Sleep;

[0190] Duration: Recommended hibernation time (e.g., 5-10 seconds);

[0191] Config_Retain: Marks the configurations that need to be retained (only the most basic system information and time synchronization parameters are retained);

[0192] Wake_Cause: Allowed wake-up conditions (such as timer timeout, emergency call, special service trigger, etc.);

[0193] Reserved: Reserved field.

[0194] Section 213, Context Logging and Monitoring:

[0195] The network side records the timestamp and related context of the UE entering the Deep_Sleep state, marks the UE as being in deep sleep, starts a timer to monitor the duration of the Deep_Sleep state, and sends a wake-up command to the UE when necessary.

[0196] Section 2.2 Terminal-side process; the terminal-side process includes the following parts:

[0197] Part 221, receiving and parsing MAC CE: After receiving the Deep_Sleep indication MAC CE, the terminal parses and confirms that it has entered the Deep_Sleep state; it extracts information such as sleep duration, retained configuration and allowed wake-up conditions.

[0198] Part 222, PHY configuration filtering and disabling:

[0199] According to the network side instructions, only the minimal PHY configuration should be retained: retain the following functions: system information decoding and time synchronization processing; disable the following functions: CSI measurement, SRS transmission, public / private search space monitoring, data processing unit, etc.

[0200] The PHY layer enters a deep sleep state, and hardware modules are significantly reduced in frequency or shut down to minimize power consumption.

[0201] Part 223, Hardware Resource Management:

[0202] Shut down unnecessary radio frequency channels and antennas;

[0203] Reduce the processor's clock frequency to maintain only basic time synchronization and wake-up monitoring functions;

[0204] Monitor the battery in real time to avoid excessive power consumption.

[0205] Part 224, Status Confirmation and Entering Hibernation:

[0206] After the terminal completes the configuration adjustment, it sends a sleep state confirmation message to the network side, indicating that the terminal has successfully entered the Deep_Sleep state;

[0207] Record the current state configuration information, timestamp, and timer parameters.

[0208] Part 3. Deep_S leep state maintenance mechanism; The Deep_S leep state maintenance mechanism includes the following parts:

[0209] Part 31, Periodic Synchronous Check:

[0210] In the Deep_Sleep state, the terminal briefly activates the physical layer every T3 (e.g., 1 second) to perform the following operations: synchronization signal detection and update; basic system information update check; wake-up condition detection (e.g., network command or timer timeout).

[0211] Activation time should be as short as possible (e.g., 10ms) to reduce power consumption.

[0212] Part 32, Low Power Monitoring Mechanism:

[0213] Retain a very low-frequency monitoring module for detecting emergency calls or high-priority service requests.

[0214] During monitoring, the terminal remains in a state where it can be quickly woken up, while minimizing power consumption.

[0215] Part 4. Deep_S leep state exit procedure; The Deep_S leep state exit procedure includes the following parts:

[0216] Section 41, the wake-up trigger conditions include the following events, and the Deep_S leep state can be triggered to exit through the following events:

[0217] The network side detects the arrival of downlink data and sends a wake-up command.

[0218] The terminal detected an uplink data request (such as a user action or application trigger).

[0219] The timer expired after the preset sleep duration.

[0220] Network configuration update requirements (such as changes in system information).

[0221] Part 42, the quick recovery process includes:

[0222] The terminal immediately activates the physical layer module and quickly recovers based on the recorded context information:

[0223] Restore the complete PHY configuration, including synchronization signals, measurement modules, etc.

[0224] Confirm with the network side that the status recovery is complete.

[0225] The network side updates the UE's context state and marks it as Active.

[0226] Section 43, exception handling includes: if an error occurs during the wake-up process (such as configuration synchronization failure or signal loss), the terminal can request the network to re-establish the configuration through the re-initialization process to ensure the reliability of state recovery.

[0227] Part 5. The comparison between the Deep_S leep and Light_S leep states is shown in Table 1:

[0228] Table 1

[0229]

[0230] Deep_Sleep is a deep power-saving mechanism designed for long-term low-activity scenarios. By shutting down most physical layer modules and hardware resources, it achieves a more significant power reduction than Light_Sleep. This mechanism features a refined state transition process and exit mechanism to ensure that the terminal can maintain necessary network synchronization during deep sleep and quickly respond to external wake-up events. It is suitable for IoT devices and ultra-low-power terminals in 5G and future communication systems.

[0231] Example 3

[0232] This embodiment provides a specific implementation scheme for a general sleep state based on the MAC layer. The embodiment describes in detail the control flow, signaling interaction, PHY configuration filtering and status confirmation process between the network side and the terminal side.

[0233] Part 1. Definition and applicable scenarios for the Sleep state:

[0234] Sleep state definition: The Sleep state is a state in which a terminal device (UE) operates with low power in a wireless communication system. It reduces power consumption by selectively shutting down some physical layer (PHY) configurations and hardware modules, while retaining basic network connectivity capabilities.

[0235] Sleep states can be divided into the following two types: Short-term Sleep: suitable for short periods of business idleness or intermittent data transmission scenarios, retaining more PHY configuration to support fast wake-up; Long-term Sleep: suitable for scenarios with no data interaction for a long time, shutting down more modules to achieve deep energy saving.

[0236] Applicable scenarios: IoT scenarios: terminal devices need to report data periodically but are idle most of the time; low-frequency business scenarios: such as terminals that only need to occasionally receive network broadcasts or are in standby mode when the user does not operate; dynamic network environment: supports the network side to dynamically adjust the sleep state of the terminal according to business needs, optimizing power consumption and service quality.

[0237] Part 2. Regarding the Sleep state transition process:

[0238] The state entry process includes:

[0239] Part 21, Network Side Sends Sleep Instruction: A Sleep instruction is sent via the MAC layer control element (MAC CE), containing the following fields:

[0240] CE_Type: Indicates that the device has entered the Sleep state;

[0241] Duration: Defines the duration of the Sleep state;

[0242] Config_Retain: Indicates which PHY configurations should be retained;

[0243] Wake_Cause: Defines the wake-up trigger condition.

[0244] Part 22, Terminal execution state switching, includes the following operations:

[0245] Determine command validity: Verify whether the MAC CE content matches the current terminal state;

[0246] Save current configuration: Store the active PHY configuration as context;

[0247] Disable unnecessary modules: Selectively disable high-power modules such as RF links, CSI measurements, and SRS transmissions based on the Config_Retain field;

[0248] Start the hibernation timer: Set the duration to the value specified in the Duration field.

[0249] Part 23, Status Confirmation: The terminal sends a status confirmation message to the network side, including the actual retained configuration items and the current status flag, confirming that it has successfully entered the Sleep state.

[0250] Part 3. Regarding the Sleep state maintenance mechanism: During the Sleep state, the terminal device maintains low-power operation through the following mechanisms:

[0251] Part 31, Dynamic Configuration Adjustment: The network side can dynamically update the Config_Retain field by resending the MAC CE, adjusting the PHY configuration retained by the terminal to adapt to real-time service requirements.

[0252] For example, when the workload increases, the signal monitoring range is expanded; when the workload decreases, more modules are shut down.

[0253] Part 32, Wake-up Event Listening: Based on the triggering conditions defined in the Wake_Cause field, the terminal listens for the following events in real time: timer expiration; arrival of uplink or downlink data; system information update indication; uplink data request triggered by user operation.

[0254] Part 33, Synchronization Maintenance: By retaining the time-frequency synchronization configuration, the terminal periodically checks and corrects time and frequency deviations to avoid communication interruptions due to synchronization loss; the interval for periodically checking synchronization is defined by the network side or the terminal's internal policy (e.g., checking once every 100ms).

[0255] Section 34, Anomaly Handling Protection: During the Sleep state, if an anomaly (such as synchronization loss or hardware failure) is detected, the terminal can forcibly exit the Sleep state and send an anomaly report to the network side.

[0256] Part 4. Exit procedure for Sleep state:

[0257] Part 41, Wake-up Condition Trigger: The terminal device exits the Sleep state when any of the following wake-up conditions are met:

[0258] Timer Expiration: The sleep timer expires, triggering a wake-up call;

[0259] Data arrival indication: The network side indicates that there is downlink data or the user has triggered an uplink data request;

[0260] System configuration update: The network side sends a command to request the terminal to obtain new system information or parameter configuration;

[0261] High-priority services: The network side detects an urgent service requirement and sends a quick wake-up instruction.

[0262] Part 42, Configuration Recovery Process: PHY Configuration Recovery: The terminal gradually restores the disabled PHY modules according to the stored active state context, such as: restoring the RF link and reopening the necessary hardware resources; restoring search space listening, CSI measurement and SRS transmission functions.

[0263] Time / Frequency Synchronization: Initiate the synchronization and reconstruction process to ensure that the time and frequency of the terminal are consistent with those of the network.

[0264] Part 43, State Transition Confirmation: The terminal sends a state transition completion indication to the network side, confirming that it has exited the Sleep state and returned to the active state.

[0265] Section 44, Anomaly Handling: If an error occurs during the configuration recovery process (such as configuration item recovery failure or synchronization reconstruction failure), the terminal can request the network side to resend the necessary configuration instructions and activate random backoff protection to avoid conflicts.

[0266] Through the above steps, the terminal device achieves efficient and flexible power management during the entry, maintenance, and exit of the Sleep state, while ensuring service continuity and communication quality. This design is applicable to various wireless communication scenarios, providing a universal low-power solution for terminal devices.

[0267] Example 4 This scheme describes in detail the data transmission process in a light sleep state, including the uplink and downlink data transmission flow, channel and flow configuration. It also clearly states that the PDCP and RLC layers will not be aware of the sleep state switching of the MAC layer, and their data processing flow remains relatively independent. The MAC layer is responsible for resource control and configuration adjustment when switching between sleep and active states.

[0268] Part 1. Regarding the overall framework for data transmission:

[0269] Part 11, characteristics of light sleep state: (1) The terminal retains some PHY configuration (such as master synchronization, some control channel listening capabilities) in light sleep state in order to quickly respond to wake-up events; (2) The MAC layer is responsible for dynamic resource application, sleep wake-up and status confirmation, while the PDCP and RLC layers always process data according to the preset configuration and do not directly perceive the MAC layer switching status.

[0270] Part 12, Inter-layer collaboration: (1) The PDCP / RLC layer continuously performs functions such as data header processing, encryption and decryption, segmentation and reassembly, and reordering. (2) The MAC layer enables SR (Scheduling Request) and configures downlink air interface transmission according to the specific transmission scenario in a light sleep state, but at the same time shields the impact of sleep state changes on PDCP / RLC so that it does not need to be aware of state transitions.

[0271] Part 2. Regarding the uplink data transmission process:

[0272] Part 21, Data Triggering and Wake-up includes:

[0273] Data triggering: When uplink data (such as interactive services or periodic reports) is generated in the UE's cache, the UE prepares for data transmission.

[0274] Wake-up mechanism: Although the PDCP / RLC layer continues to process data according to the normal process, after the MAC layer detects the uplink transmission requirement, it will compare the light sleep configuration with the preset sleep policy to decide whether to exit the sleep state and start the PUSCH channel transmission.

[0275] Part 22, Resource Request and Channel Access includes:

[0276] SR Channel: The UE sends a scheduling request through a pre-configured SR (Schedule Request) channel.

[0277] PUCCH resources: Some PUCCH resources reserved in a light sleep state can also be used to transmit control information.

[0278] Scheduled configuration: For example, the SR configuration period is 20ms to ensure timely data transmission.

[0279] Part 23, data transmission includes:

[0280] MAC layer scheduling: After receiving the resource allocation, the MAC layer selects the PUSCH channel to transmit data in the uplink transmission.

[0281] Uplink modulation: A fixed MCS configuration is used (e.g., QPSK with a bit rate of 1 / 2), and the minimum PRB (physical resource block) configuration is selected to save power.

[0282] PDCP / RLC processing:

[0283] The PDCP layer performs header processing, segmentation, AES-128 encryption, and count updates on data packets in the uplink.

[0284] The RLC layer uses AM (acknowledgment mode) or UM (unacknowledgment mode) to segment data, assemble PDUs, and set timed retransmissions (e.g., extending the status report cycle to 500ms to accommodate low-frequency operations).

[0285] Part 24, HARQ and End of Transmission includes:

[0286] HARQ Feedback: The MAC layer waits for HARQ feedback from the network side regarding uplink data transmission.

[0287] Return to sleep: If there is no new data, the MAC layer quickly switches back to a light sleep state after completing data transmission to maintain synchronization and monitor the downlink control channel.

[0288] Part 3. Regarding the downlink data transmission process:

[0289] Part 31, Wake-up and Signaling Reception includes:

[0290] Network-side triggering: When the network side has downlink data transmission requirements, the eNB / gNB sends a wake-up indication through control channels such as PDCCH.

[0291] Specific search space monitoring: Even when the UE is in a light sleep state, it still retains some PDCCH monitoring capabilities, thus enabling it to respond to downlink wake-up instructions in a timely manner.

[0292] Section 32, Resource Allocation and Control Information includes:

[0293] DCI and CCE configuration: The network uses a compressed DCI format and distributes resource allocation information at a fixed CCE aggregation level (e.g., AL=4).

[0294] Channel mapping: Common logical channel mapping schemes include DCCH mapping to PUCCH / PDCCH, DTCH mapping to PDSCH / PUSCH, and BCCH receiving only system broadcast information (such as SIB).

[0295] Part 33, data transmission, includes:

[0296] PDSCH Data Reception: The UE receives data via PDSCH, using a pre-configured antenna scheme and a conservative modulation and coding scheme.

[0297] PDCP / RLC processing: The PDCP layer performs frame reassembly and decryption processing (AES-128 or other predefined algorithms) in the downlink and maintains state information; the RLC layer performs reordering (the reordering window is small, and t-Reordering is extended to 300ms to adapt to low-frequency scenarios), thereby reducing the feedback frequency and reducing power consumption.

[0298] Part 34, HARQ feedback includes:

[0299] The UE uses the PUCCH channel to send HARQ feedback information to ensure the reliability of uplink and downlink data transmission.

[0300] After data transmission is completed, the MAC layer continues to maintain a light sleep monitoring state to ensure that it can respond to subsequent wake-up commands at any time.

[0301] Part 4. Design for mutual insensitivity between PDCP / RLC and MAC sleep states:

[0302] Part 41, the PDCP layer design includes:

[0303] Data transparency: The PDCP layer is unaware of whether the MAC layer is in a light sleep state, and always processes and encrypts / decrypts data packets based on their arrival.

[0304] State maintenance: The state of PDCP entities (including sequence number, retransmission counter, encryption / decryption parameters) remains unchanged during scheduling requests and transmission. The MAC layer's sleep switching is completely transparent to PDCP operations.

[0305] Part 42, the RLC layer design includes:

[0306] Data link transmission: In AM or UM mode, the RLC layer does not care about the MAC sleep state, but continues to perform data segmentation, PDU assembly and reordering.

[0307] Buffer management: Data buffering and PDU size settings (e.g., fixed 256 bytes) and transmission timing configuration are determined by upper-layer services and network configurations, and are not affected by MAC layer sleep mode.

[0308] Section 43, the responsibilities of the MAC layer include:

[0309] The MAC layer is responsible for detecting sleep conditions, resource requests, and control channel configuration, and provides transparent transmission bearer and necessary state switching for upper layer data (PDCP / RLC).

[0310] Once the data transmission requirement is initiated, the MAC layer will temporarily "wake up" channels such as PUSCH / PDSCH to activate RF resources related to data transmission, while the PDCP / RLC layer will maintain the continuity of the data stream.

[0311] Part 5. Regarding high-level configuration and security:

[0312] Part 51, Logical Channel Mapping and Configuration includes:

[0313] SRB configuration: SRB1 is usually kept active, while SRB2 can be selectively activated according to business needs;

[0314] DRB configuration: Data carrying is provided through dynamically established DRBs, and retransmission and segmentation parameters are adjusted in a timely manner to adapt to the channel characteristics in sleep mode.

[0315] Part 52, PDCP security procedures include:

[0316] Encryption algorithms such as AES-128 are used to ensure data security, and counters and security contexts are continuously managed in the PDCP layer;

[0317] Even if the MAC layer enters a dormant state, the upper-layer security processing flow remains unaffected, maintaining a consistent encryption / decryption process.

[0318] Part 53, RLC transmission characteristics include:

[0319] With the support of higher-level services, the RLC layer selects AM or UM mode for reliable transmission, and has optimized parameters for the lower feedback frequency and transmission interval in the light sleep state.

[0320] The t-Reordering and reordering window parameters have been adjusted (extended to 300ms and appropriately reduced, respectively) to ensure data transmission continuity and retransmission efficiency.

[0321] Part 6. Regarding the achieved effects and advantages:

[0322] Power consumption optimization: In light sleep mode, the MAC layer achieves effective control of the RF module through intelligent resource scheduling and dynamic wake-up, which greatly reduces unnecessary power consumption.

[0323] Data continuity: The PDCP and RLC layers operate independently of the MAC sleep state changes, ensuring that data encryption / decryption, segmentation / assembly, reordering, and state management are always uninterrupted, providing a stable bearer for upper-layer service transmission.

[0324] Fast response: After detecting the wake-up condition, the MAC layer can quickly activate the necessary channels (PUSCH / PDSCH, etc.), enabling the terminal to "wake up" from a light sleep state with a small delay and complete data transmission and reception.

[0325] Safe and reliable: Through the design of PDCP security processing and RLC control, data transmission still meets the requirements of high reliability and security in low power mode.

[0326] Example 4 above describes a full-link implementation scheme for data transmission in a light sleep state. It fully considers the decoupling design between MAC layer sleep control and upper layer PDCP / RLC data processing, thereby ensuring power consumption optimization without interfering with the continuity and security of upper layer data logic.

[0327] Example 5

[0328] This embodiment describes the implementation scheme for switching between light sleep state and deep sleep state.

[0329] Part 1. For application scenarios:

[0330] In wireless communication systems, terminal equipment (UE) can dynamically switch between light sleep and deep sleep to adapt to different service needs and power consumption requirements.

[0331] Light sleep mode: Suitable for short-term idle business scenarios, retaining some PHY configuration to support fast wake-up and response.

[0332] Deep sleep mode: Suitable for scenarios with no data interaction for a long time. It achieves maximum energy saving by further shutting down modules, but the wake-up time is relatively long.

[0333] Part 2. State transition conditions include:

[0334] Section 21, the transition from light hibernation to deep hibernation includes two triggering methods:

[0335] Firstly, the network side sends a deep sleep indication signaling: based on the prediction of a long service idle period (e.g., more than 1 second); the terminal's battery is low and needs to enter a deep power saving mode; the dynamic network load is high, reducing the resource occupation of low-priority terminals.

[0336] Secondly, timer trigger: If the light sleep state is maintained for more than a preset time (such as 500ms) and no wake-up event occurs, it will automatically enter deep sleep.

[0337] Section 22, the transition from deep hibernation to light hibernation includes two triggering methods:

[0338] Firstly, the network side sends a light sleep indication signaling: potential data transmission needs are detected (such as uplink data queuing or downlink data about to be sent); the network load is reduced, allowing more terminals to enter light sleep to maintain higher service availability.

[0339] Secondly, wake-up event triggering: The terminal detects supported wake-up conditions (such as timer expiration or emergency service).

[0340] Part 3. The implementation of the state transition process includes:

[0341] Partial 3.1 transition from light hibernation to deep hibernation:

[0342] For network-side triggering:

[0343] eNB / gNB sends a deep sleep instruction via MAC CE, including the following commands:

[0344] CE_Type: Status type flag (1 indicates deep sleep);

[0345] Duration: The expected duration of deep hibernation;

[0346] Wake_Cause: Allowed wake-up conditions (such as timer expiration or system information update).

[0347] Execute on terminal:

[0348] Save light hibernation configuration: Store the PHY configuration and context information during light hibernation to low-power memory.

[0349] Disable more modules: disable the RF link; stop time-frequency synchronization maintenance; stop monitoring the downlink control channel (PDCCH); disable high-power functions such as SRS and CSI measurements.

[0350] Start a deep sleep timer: Set the duration to the value of the Duration field, and trigger a wake-up after the timeout.

[0351] For state confirmation: The UE sends a state transition confirmation message through a predefined low-power channel (such as RACH resource or simplified PUCCH channel) to notify the network side that it has successfully entered deep sleep state.

[0352] Partial 3.2 Deep hibernation state is switched to light hibernation state:

[0353] For wake-up condition triggering:

[0354] Timer Expiration: When the deep sleep timer expires, a state switch is triggered;

[0355] Network-side command wake-up: The eNB / gNB sends an emergency service instruction via PDCCH, requesting the terminal to return to light sleep mode;

[0356] System information update: New system information is broadcast over the network, and the terminal needs to be restored to receive the update.

[0357] Execute on terminal:

[0358] Restore RF link: Reboot the RF module and establish the basic physical connection;

[0359] Re-establish time and frequency synchronization: Time and frequency synchronization is re-acquired through the primary synchronization signal (PSS) and secondary synchronization signal (SSS);

[0360] Restore light sleep configuration: Load the previously stored light sleep PHY configuration and activate some functions: enable PDCCH listening to receive network commands; restore SRS configuration to support uplink quality reports; retain some power-optimized antenna configurations.

[0361] The status confirmation includes: the UE sending a status switch completion indication to the network side, notifying that it has successfully switched to a light sleep state and is ready to receive or send data.

[0362] Part 4. Key mechanisms for state transitions include:

[0363] The timer design includes:

[0364] Light sleep timer: Monitors the duration of light sleep state and triggers the transition to deep sleep state after timeout;

[0365] Deep sleep timer: Controls the maximum duration of deep sleep state, automatically waking up to light sleep state after timeout;

[0366] Protection timer: Used for timeout protection in abnormal situations to ensure that the conversion process does not freeze.

[0367] Resource management includes:

[0368] In a light sleep state, some PHY resources are retained (such as synchronization signal monitoring and simplified control channel decoding);

[0369] In deep sleep mode, PHY resources are completely released, maintaining only the lowest power hardware state.

[0370] Exception handling includes:

[0371] If a configuration recovery failure is detected during the state transition, the terminal can request the network to resend the configuration command;

[0372] If synchronization loss is detected during deep sleep, the terminal can force exit and re-establish the connection.

[0373] Part 5. Regarding the achieved effect:

[0374] Power consumption optimization: Flexible power management is achieved by dynamically switching between light sleep and deep sleep states, maximizing energy saving during long periods of inactivity.

[0375] Service Assurance: By quickly responding to wake-up events through a light sleep state, basic service quality for latency-sensitive services is ensured.

[0376] Adaptable to multiple scenarios: Supports various scenarios from high-frequency services to long periods without services, improving the energy-saving performance and applicability of terminals.

[0377] The above solutions demonstrate a flexible switching mechanism between light sleep and deep sleep states, achieving a balance between energy saving and quality of service, and providing an efficient low-power management method for wireless communication systems.

[0378] In one embodiment, FIG5 is a structural block diagram of a state switching device provided in this application. This embodiment is applied to a first communication node. As shown in FIG5, the state switching device in this embodiment includes: a determining module 510 and a switching module 520.

[0379] The module 510 is configured to determine sleep state indication information based on the Media Access Control (MAC) layer.

[0380] The switching module 520 is configured to switch to sleep mode based on sleep state indication information.

[0381] In one embodiment, determining sleep state indication information based on the MAC layer includes one of the following:

[0382] Receive sleep state indication information based on the MAC layer configured by the second communication node;

[0383] Negotiate and configure sleep state indication information based on the MAC layer with the second communication node.

[0384] In one embodiment, the hibernation state indication information includes at least one of the following: hibernation state type; hibernation state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0385] In one embodiment, the wake-up trigger condition includes at least one of the following: the sleep timer expires; uplink or downlink data arrives; system information update indication; uplink data request triggered by user operation.

[0386] In one embodiment, before determining the sleep state indication information based on the MAC layer, the method further includes:

[0387] Determine the sleep state bearer signaling based on the Radio Resource Control (RRC) layer.

[0388] In one embodiment, determining the sleep state bearer signaling based on the RRC layer includes one of the following:

[0389] Receive the sleep state bearer signaling configured by the second communication node at the RRC layer;

[0390] Negotiate and configure the sleep state bearer signaling of RRC with the second communication node.

[0391] In one embodiment, the sleep state carrying signaling includes at least one of the following: sleep state type; sleep state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0392] In one embodiment, switching to a sleep state based on sleep state indication information includes at least one of the following:

[0393] Store the active physical layer configuration as a physical layer context;

[0394] Based on the reservation indication information configured in the physical layer, the radio frequency link, the channel state information (CSI) measurement function, and the sounding reference signal (SRS) transmission function are selectively disabled.

[0395] The hibernation timer is started based on the duration of the hibernation state.

[0396] In one embodiment, the state switching device applied to the first communication node further includes:

[0397] The sending module is configured to send a sleep state confirmation message to the second communication node; wherein, the sleep state confirmation message includes: a sleep state switching success indication information and the actual retained physical layer configuration.

[0398] In one embodiment, the hibernation state type includes at least one of the following: a first type of hibernation state; a second type of hibernation state; wherein the second type of hibernation state is more energy-efficient than the first type of hibernation state.

[0399] In one embodiment, when in a first type of sleep state, the MAC context is preserved, and the physical layer retains the configuration for processing the common physical layer.

[0400] In the second type of hibernation state, the MAC context is preserved, and the physical layer retains the relevant configurations for handling system information and paging messages.

[0401] In one embodiment, switching to a sleep state based on sleep state indication information includes one of the following:

[0402] The hibernation state is switched from the first type of hibernation state to the second type of hibernation state based on the hibernation state indication information;

[0403] Switching from the second type of hibernation state to the first type of hibernation state based on hibernation state indication information;

[0404] Based on the hibernation state indication information, the system switches from the active state to the first type of hibernation state;

[0405] Based on the hibernation state indication information, the system switches from the active state to the second type of hibernation state.

[0406] In one embodiment, when switching from a first type of hibernation state to a second type of hibernation state, a first type of operation is performed; the first type of operation includes at least one of the following:

[0407] Save the first type of sleep configuration; shut down the RF link; stop time-frequency synchronization maintenance; stop monitoring the downlink control channel; disable SRS transmission and CSI measurement functions; start the second type of sleep timer; stop monitoring the common search space; stop monitoring the dedicated search space; disable the data processing unit function.

[0408] In one embodiment, when switching from a second type of hibernation state to a first type of hibernation state, a second type of operation is performed; the second type of operation includes at least one of the following:

[0409] Restore the radio frequency link; rebuild time and frequency synchronization maintenance; enable the monitoring downlink control channel; restore SRS configuration; retain some antenna configurations.

[0410] In one embodiment, the first communication node is in a first type of sleep state, and the sleep state indication information further includes: a first type of data transmission support capability; the state switching device applied to the first communication node further includes:

[0411] The transmission module is configured to transmit a first type of data to a second communication node using a reserved public channel; wherein the amount of the first type of data is less than a data amount threshold.

[0412] In one embodiment, for a first type of sleep state, the reserved list configured by the physical layer includes one of the following: system information; synchronization signal processing; random access parameters; and common search space.

[0413] In one embodiment, switching to a sleep state based on sleep state indication information includes:

[0414] If the first hibernation state switching trigger condition is met, the system switches to hibernation state based on the hibernation state indication information.

[0415] In one embodiment, for the first communication node, the first sleep state switching trigger condition includes one of the following: the actual remaining power is less than the power threshold; the service prediction model determines it to be a first type of load scenario; the actual hardware temperature is greater than the temperature threshold; wherein, the load in the first type of load scenario is less than the load threshold.

[0416] In one embodiment, the state switching device applied to the first communication node further includes:

[0417] The module is also configured to determine wake-up trigger events based on the MAC layer;

[0418] The switching module is also configured to switch from a sleep state to an active state based on a wake-up trigger event.

[0419] In one embodiment, determining a wake-up trigger event based on the MAC layer includes:

[0420] Receive wake-up indication information based on the MAC layer configured by the second communication node;

[0421] Negotiate and configure wake-up indication information based on the MAC layer with the second communication node.

[0422] In one embodiment, the wake-up indication information includes at least one of the following: wake-up type; wake-up reason; duration of active state; and physical layer configuration update indication information.

[0423] In one embodiment, the state switching device applied to the first communication node further includes:

[0424] The sending module is configured to send a hibernation exit message to the second communication node, so that the second communication node can confirm that the first communication node has exited the hibernation state and returned to the active state based on the hibernation exit message.

[0425] The state switching device provided in this embodiment is configured to implement the state switching method applied to the second communication node in the embodiment shown in Figure 2. The implementation principle and technical effect of the state switching device provided in this embodiment are similar, and will not be described again here.

[0426] In one embodiment, FIG6 is a structural block diagram of another state switching device provided in this application. This embodiment is applied to a second communication node. As shown in FIG6, the state switching device in this embodiment includes: a determining module 610 and a switching module 620.

[0427] The module 610 is configured to determine sleep state indication information based on the Media Access Control (MAC) layer.

[0428] The switching module 620 is configured to send sleep state indication information to the first communication node so that the first communication node switches to sleep state based on the sleep state indication information.

[0429] In one embodiment, determining sleep state indication information based on the MAC layer includes one of the following:

[0430] Pre-configure sleep state indication information based on the MAC layer;

[0431] Negotiate and configure sleep state indication information based on the MAC layer with the first communication node.

[0432] In one embodiment, the hibernation state indication information includes at least one of the following: hibernation state type; hibernation state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0433] In one embodiment, the wake-up trigger condition includes at least one of the following: the sleep timer expires; uplink or downlink data arrives; system information update indication; uplink data request triggered by user operation.

[0434] In one embodiment, the state switching device applied to the second communication node further includes:

[0435] The determination module is also configured to determine the sleep state bearer signaling based on the Radio Resource Control (RRC) layer;

[0436] The sending module is configured to send the hibernation state bearer signaling to the first communication node, so that the first communication node can perform negotiation and configuration of hibernation state indication information based on the hibernation state bearer signaling.

[0437] In one embodiment, determining the sleep state bearer signaling based on the RRC layer includes one of the following:

[0438] Pre-configured RRC layer sleep state bearer signaling;

[0439] Negotiate and configure the sleep state bearer signaling of the RRC layer with the first communication node.

[0440] In one embodiment, the sleep state carrying signaling includes at least one of the following: sleep state type; sleep state duration; physical layer configuration retention indication information; and wake-up trigger condition.

[0441] In one embodiment, switching to a sleep state based on sleep state indication information includes at least one of the following:

[0442] Store the active physical layer configuration as a physical layer context;

[0443] Based on the reservation indication information configured in the physical layer, the radio frequency link, the channel state information (CSI) measurement function, and the sounding reference signal (SRS) transmission function are selectively disabled.

[0444] The hibernation timer is started based on the duration of the hibernation state.

[0445] In one embodiment, the state switching device applied to the second communication node further includes:

[0446] The receiving module is configured to receive a sleep state confirmation message sent by the first communication node; wherein the sleep state confirmation message includes: a sleep state switching success indication information and the actual retained physical layer configuration.

[0447] In one embodiment, the hibernation state type includes at least one of the following: a first type of hibernation state; a second type of hibernation state; wherein the second type of hibernation state is more energy-efficient than the first type of hibernation state.

[0448] In one embodiment, when in a first type of sleep state, the MAC context is preserved, and the physical layer retains the configuration for processing the common physical layer.

[0449] In the second type of hibernation state, the MAC context is preserved, and the physical layer retains the relevant configurations for handling system information and paging messages.

[0450] In one embodiment, switching to a sleep state based on sleep state indication information includes one of the following:

[0451] The hibernation state is switched from the first type of hibernation state to the second type of hibernation state based on the hibernation state indication information;

[0452] Switching from the second type of hibernation state to the first type of hibernation state based on hibernation state indication information;

[0453] Based on the hibernation state indication information, the system switches from the active state to the first type of hibernation state;

[0454] Based on the hibernation state indication information, the system switches from the active state to the second type of hibernation state.

[0455] In one embodiment, when switching from a first type of hibernation state to a second type of hibernation state, a first type of operation is performed; the first type of operation includes at least one of the following:

[0456] Save the first type of sleep configuration; shut down the RF link; stop time-frequency synchronization maintenance; stop monitoring the downlink control channel; disable SRS transmission and CSI measurement functions; start the second type of sleep timer; stop monitoring the common search space; stop monitoring the dedicated search space; disable the data processing unit function.

[0457] In one embodiment, when switching from a second type of hibernation state to a first type of hibernation state, a second type of operation is performed; the second type of operation includes at least one of the following:

[0458] Restore the radio frequency link; rebuild time and frequency synchronization maintenance; enable the monitoring downlink control channel; restore SRS configuration; retain some antenna configurations.

[0459] In one embodiment, the first communication node is in a first type of sleep state, and the sleep state indication information further includes: first type of data transmission support capability; the state switching device applied to the second communication node further includes:

[0460] The receiving module is also configured to receive first type data transmitted by the first communication node using a reserved public channel; wherein the amount of the first type data is less than a data amount threshold.

[0461] In one embodiment, for a first type of sleep state, the reserved list configured by the physical layer includes one of the following: system information; synchronization signal processing; random access parameters; and common search space.

[0462] In one embodiment, the state switching device applied to the second communication node further includes:

[0463] The triggering module is also configured to trigger the first communication node to switch to a sleep state based on the second sleep state switching trigger condition.

[0464] In one embodiment, for the second communication node, the second sleep state switching trigger condition includes one of the following: the downlink buffer data volume is less than the data volume threshold; the duration of inactive service reaches a preset duration threshold; or the load balancing demand changes.

[0465] In one embodiment, the state switching device applied to the second communication node further includes:

[0466] The module is also configured to determine wake-up trigger events based on the MAC layer;

[0467] The switching module is also configured to switch from a sleep state to an active state based on a wake-up trigger event.

[0468] In one embodiment, determining a wake-up trigger event based on the MAC layer includes:

[0469] Pre-configure wake-up indication information based on the MAC layer;

[0470] Negotiate and configure wake-up indication information based on the MAC layer with the first communication node.

[0471] In one embodiment, the wake-up indication information includes at least one of the following: wake-up type; wake-up reason; duration of active state; and physical layer configuration update indication information.

[0472] In one embodiment, the state switching device applied to the second communication node further includes:

[0473] The receiving module is also configured to receive a sleep state exit message sent by the first communication node;

[0474] The exit module is configured to confirm the exit of the first communication node from the dormant state and restore it to the active state based on the exit message from the dormant state.

[0475] The state switching device provided in this embodiment is configured to implement the state switching method applied to the second communication node in the embodiment shown in Figure 2. The implementation principle and technical effect of the state switching device provided in this embodiment are similar, and will not be described again here.

[0476] In one embodiment, FIG7 is a schematic diagram of the structure of a communication device provided in this application. As shown in FIG7, the device provided in this application includes: a processor 710, a memory 720, and a communication module 730. The number of processors 710 in the device can be one or more; FIG7 shows an example of one processor 710. The number of memories 720 in the device can be one or more; FIG7 shows an example of one memory 720. The processor 710, memory 720, and communication module 730 of the device can be connected via a bus or other means; FIG7 shows an example of connection via a bus. In this embodiment, the device can be a first communication node or a second communication node.

[0477] The memory 720, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device in any embodiment of this application (e.g., the determining module 510 and switching module 520 applied in the state switching device of the first communication node). The memory 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created according to the use of the device, etc. Furthermore, the memory 720 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 720 may further include memory remotely located relative to the processor 710, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0478] When the communication device is the first communication node, the device provided above can be configured to execute the state switching method for the first communication node provided in any of the above embodiments, and has the corresponding functions and effects.

[0479] When the communication device is a second communication node, the device provided above can be configured to execute the state switching method for the second communication node provided in any of the above embodiments, and has the corresponding functions and effects.

[0480] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a state switching method applied to a first communication node. The method includes: determining sleep state indication information based on the Media Access Control (MAC) layer; and switching to sleep state based on the sleep state indication information.

[0481] This application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute a state switching method applied to a second communication node. The method includes: determining sleep state indication information based on the Media Access Control (MAC) layer; and sending the sleep state indication information to a first communication node so that the first communication node switches to a sleep state based on the sleep state indication information.

[0482] Those skilled in the art will understand that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0483] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0484] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0485] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0486] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A state switching method, characterized in that, Applied to the first communication node, it includes: determining sleep state indication information based on the Media Access Control (MAC) layer; and switching to sleep state based on the sleep state indication information.

2. The method according to claim 1, characterized in that, The determination of the MAC layer-based sleep state indication information includes one of the following: receiving the MAC layer-based sleep state indication information configured by the second communication node; negotiating with the second communication node to configure the MAC layer-based sleep state indication information.

3. The method according to claim 2, characterized in that, The hibernation state indication information includes at least one of the following: hibernation state type; hibernation state duration; physical layer configuration retention indication information; wake-up trigger condition.

4. The method according to claim 3, characterized in that, The wake-up trigger conditions include at least one of the following: the sleep timer expires; uplink or downlink data arrives; system information update indication; uplink data request triggered by user operation.

5. The method according to claim 1, characterized in that, Before determining the sleep state indication information based on the MAC layer, the method further includes: determining the sleep state bearer signaling based on the Radio Resource Control (RRC) layer.

6. The method according to claim 5, characterized in that, The determination of the sleep state bearer signaling based on the RRC layer includes one of the following: receiving the sleep state bearer signaling configured by the second communication node; negotiating with the second communication node to configure the sleep state bearer signaling of the RRC layer.

7. The method according to claim 5, characterized in that, The sleep state carrying signaling includes at least one of the following: sleep state type; sleep state duration; physical layer configuration retention indication information; wake-up trigger condition.

8. The method according to claim 3, characterized in that, The process of switching to a sleep state based on the sleep state indication information includes at least one of the following: storing the physical layer configuration in the active state as a physical layer context; selectively disabling the radio frequency link, disabling the channel state information (CSI) measurement function, and disabling the sounding reference signal (SRS) transmission function according to the retention indication information of the physical layer configuration; and starting a sleep timer based on the duration of the sleep state.

9. The method according to claim 1, characterized in that, The method further includes: sending a hibernation state confirmation message to a second communication node; wherein the hibernation state confirmation message includes: hibernation state switching success indication information and the actual retained physical layer configuration.

10. The method according to claim 3, characterized in that, The sleep state type includes at least one of the following: a first type of sleep state; a second type of sleep state; wherein the second type of sleep state is more energy-efficient than the first type of sleep state.

11. The method according to claim 10, characterized in that, When in the first type of sleep state, the MAC context is retained, and the physical layer retains the configuration for processing the common physical layer; when in the second type of sleep state, the MAC context is retained, and the physical layer retains the relevant configuration for processing system information and paging messages.

12. The method according to claim 10, characterized in that, The switching to a hibernation state based on the hibernation state indication information includes one of the following: switching from a first type of hibernation state to a second type of hibernation state based on the hibernation state indication information; switching from a second type of hibernation state to a first type of hibernation state based on the hibernation state indication information; switching from an active state to a first type of hibernation state based on the hibernation state indication information; or switching from an active state to a second type of hibernation state based on the hibernation state indication information.

13. The method according to claim 12, characterized in that, When switching from the first type of sleep state to the second type of sleep state, a first type of operation is performed; the first type of operation includes at least one of the following: saving the first type of sleep configuration; shutting down the radio frequency link; stopping time-frequency synchronization maintenance; stopping monitoring the downlink control channel; disabling SRS transmission and CSI measurement functions; starting the second type of sleep timer; stopping monitoring the common search space; stopping monitoring the dedicated search space; and disabling the functions of the data processing unit.

14. The method according to claim 12, characterized in that, When switching from the second type of sleep state to the first type of sleep state, the second type of operation is performed; the second type of operation includes at least one of the following: restoring the radio frequency link; re-establishing time-frequency synchronization maintenance; enabling the listening downlink control channel; restoring the SRS configuration; and retaining part of the antenna configuration.

15. The method according to claim 10, characterized in that, The first communication node is in a first type of sleep state, and the sleep state indication information further includes: first type of data transmission support capability; the method further includes: transmitting the first type of data with the second communication node using a reserved public channel; wherein the data volume of the first type of data is less than the data volume threshold.

16. The method according to claim 10, characterized in that, For the first type of sleep state, the reserved list configured by the physical layer includes one of the following: system information; synchronization signal processing; random access parameters; common search space.

17. The method according to claim 1, characterized in that, The step of switching to a sleep state based on the sleep state indication information includes: switching to a sleep state based on the sleep state indication information when the first sleep state switching trigger condition is met.

18. The method according to claim 17, characterized in that, For the first communication node, the first sleep state switching trigger condition includes one of the following: the actual remaining power is less than the power threshold; the service prediction model determines it to be a first type of load scenario; the actual hardware temperature is greater than the temperature threshold; the load in the first type of load scenario is less than the load threshold.

19. The method according to any one of claims 1-18, characterized in that, The method further includes: determining a wake-up trigger event based on the MAC layer; and switching from the sleep state to the active state based on the wake-up trigger event.

20. The method according to claim 19, characterized in that, The determination of the MAC layer-based wake-up trigger event includes: receiving MAC layer-based wake-up indication information configured by the second communication node; and negotiating with the second communication node to configure the MAC layer-based wake-up indication information.

21. The method according to claim 20, characterized in that, The wake-up indication information includes at least one of the following: wake-up type; wake-up reason; duration of active state; and physical layer configuration update indication information.

22. The method according to claim 19, characterized in that, The method further includes: sending a hibernation exit message to a second communication node, so that the second communication node confirms, based on the hibernation exit message, that the first communication node has exited the hibernation state and returned to the active state.

23. A state switching method, characterized in that, Applied to a second communication node, the method includes: determining sleep state indication information based on the Media Access Control (MAC) layer; and sending the sleep state indication information to a first communication node so that the first communication node switches to a sleep state based on the sleep state indication information.

24. The method according to claim 23, characterized in that, The method further includes: determining sleep state bearer signaling based on the Radio Resource Control (RRC) layer; and sending the sleep state bearer signaling to a first communication node so that the first communication node can perform negotiation and configuration of sleep state indication information based on the sleep state bearer signaling.

25. The method according to claim 23, characterized in that, The method further includes: triggering the first communication node to switch to a sleep state based on a second sleep state switching trigger condition.

26. The method according to claim 25, characterized in that, For the second communication node, the triggering conditions for the second sleep state switching include one of the following: the downlink buffer data volume is less than the data volume threshold; the duration of inactive service reaches a preset duration threshold; or the load balancing demand changes.

27. The method according to claim 23, characterized in that, The method further includes: receiving a hibernation state confirmation message sent by a first communication node; wherein the hibernation state confirmation message includes: hibernation state switching success indication information and the actual retained physical layer configuration.

28. The method according to claim 23, characterized in that, The method further includes: receiving a hibernation exit message sent by a first communication node; and confirming, based on the hibernation exit message, that the first communication node exits the hibernation state and returns to the active state.

29. A communication device, characterized in that, include: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any one of claims 1-22 or 23-28.

30. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-22 or 23-28.

Images