Communication method, terminal, network device, communication system and storage medium

Abstract

Provided in the embodiments of the present disclosure are a communication method, a terminal, a network device, a communication system and a storage medium. The method comprises: when a terminal enters a first state, executing a first behavior, wherein the terminal comprises a first transceiver and a second transceiver, the second transceiver is used for receiving a wake-up signal, and the wake-up signal is used for waking up the first transceiver. By means of the embodiments of the present disclosure, the power consumption of a terminal can be reduced.

Description

Communication method, terminal, network device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a communication method, a terminal, a network device, a communication system, and a storage medium. Background Art

[0002] In the field of communications technology, terminal power consumption is a significant constraint on terminal application scenarios and user experience. High power consumption not only shortens the terminal's standby time but also places higher demands on terminal heat dissipation.

[0003] Summary of the Invention

[0004] In the communication between the terminal and the network side, it is necessary to reduce the power consumption of the terminal.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method includes: when a terminal enters a first state, executing a first action. The terminal includes a first transceiver and a second transceiver. The second transceiver is configured to receive a wake-up signal. The wake-up signal is configured to wake up the first transceiver.

[0006] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method includes: sending first information, wherein the first information is used to instruct a terminal to stop a running bandwidth part (BWP) inactivity timer. The terminal includes a first transceiver and a second transceiver. The second transceiver is used to receive a wake-up signal. The wake-up signal is used to wake up the first transceiver.

[0007] According to a third aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes a processing module. The processing module is configured to execute a first action when the terminal enters a first state. The terminal includes a first transceiver and a second transceiver. The second transceiver is configured to receive a wake-up signal. The wake-up signal is used to wake up the first transceiver.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided. The network device includes a transceiver module. The transceiver module is configured to send first information, wherein the first information is used to instruct a terminal to stop a running BWP inactivity timer. The terminal includes a first transceiver and a second transceiver. The second transceiver is used to receive a wake-up signal. The wake-up signal is used to wake up the first transceiver.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes at least one processor and is configured to execute the method described in the first aspect.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a network device is provided. The network device includes at least one processor and is configured to execute the method described in the second aspect.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a terminal and a network device. The terminal is configured to implement the method described in the first aspect. The network device is configured to implement the method described in the second aspect.

[0012] According to an eighth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed by a processor, the method according to the first aspect or the second aspect is performed.

[0013] According to a ninth aspect of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When executed by a processor, the code performs the method described in the first or second aspect.

[0014] According to the embodiment of the present disclosure, the terminal can execute the first behavior after entering the first state, thereby operating with lower power consumption. In this way, the power consumption of the terminal is reduced.

[0015] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0017] FIG1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0018] FIG2 is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0019] FIG3 is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0020] FIG4 is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0021] FIG5 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0022] FIG6 is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0023] FIG7 is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0024] FIG8 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] Embodiments of the present disclosure provide a communication method, a terminal, a network device, a communication system, and a storage medium.

[0026] In a first aspect, embodiments of the present disclosure provide a communication method. The method includes: upon a terminal entering a first state, executing a first action. The terminal includes a first transceiver and a second transceiver. The second transceiver is configured to receive a wake-up signal. The wake-up signal is configured to wake up the first transceiver.

[0027] In this embodiment, the terminal can execute the first behavior after entering the first state, thereby operating with lower power consumption. In this way, the power consumption of the terminal is reduced.

[0028] In combination with some embodiments of the first aspect, in some embodiments, the first behavior may include at least one of the following: stopping or suspending a running BWP inactivity timer; not monitoring the physical downlink control channel (PDCCH); not receiving the physical downlink shared channel (PDSCH); not sending the physical uplink shared channel (PUSCH); not sending the sounding reference signal (SRS); clearing the configured downlink allocation and configured uplink authorization of configuration authorization type 2; suspending the configured uplink authorization of configuration authorization type 1.

[0029] In this embodiment, for activating the BWP, when entering the first state, the terminal may stop or suspend the BWP inactivity timer. Thus, in the first state, the terminal will not switch the BWP of the master transceiver due to the expiration of the BWP inactivity timer.

[0030] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving first information, where the first information is used to instruct the terminal to stop a running BWP inactivity timer.

[0031] In this embodiment, if the network side predicts that the sleep time of the terminal's primary transceiver will be relatively long, the network device may send a first message to instruct the terminal to stop the BWP inactivity timer. In this way, the terminal can avoid BWP switching of the primary transceiver due to the expiration of the BWP inactivity timer.

[0032] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: executing a second behavior when the terminal leaves the first state.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the second behavior may include at least one of the following: restarting or resuming the BWP inactivity timer; monitoring PDCCH; receiving PDSCH; sending PUSCH; sending SRS; initializing the suspended configuration uplink authorization of configuration authorization type 1 related to the service cell.

[0034] In combination with some embodiments of the first aspect, in some embodiments, when the BWP in which the terminal is located before entering the first state is the same as the BWP after leaving the first state, the second behavior may include: resuming the BWP inactivity timer.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the method may further include: receiving second information, wherein the second information is used to instruct the terminal to restart the BWP inactivity timer. The second behavior includes: restarting the BWP inactivity timer according to the second information.

[0036] In combination with some embodiments of the first aspect, in some embodiments, when the BWP where the first transceiver is located is a dormant BWP or a deactivated BWP, the first behavior is the same as the behavior of the terminal before entering the first state.

[0037] In a second aspect, embodiments of the present disclosure provide a communication method. The method includes: sending first information, wherein the first information is used to instruct a terminal to stop a running BWP inactivity timer. The terminal includes a first transceiver and a second transceiver. The second transceiver is used to receive a wake-up signal. The wake-up signal is used to wake up the first transceiver.

[0038] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: sending second information, where the second information is used to instruct the terminal to restart the BWP inactivity timer.

[0039] In a third aspect, embodiments of the present disclosure provide a communications device. The device includes a processing module. The processing module is configured to execute a first action when a terminal enters a first state. The terminal includes a first transceiver and a second transceiver. The second transceiver is configured to receive a wake-up signal. The wake-up signal is configured to wake up the first transceiver.

[0040] In combination with some embodiments of the third aspect, in some embodiments, the first behavior may include at least one of the following: stopping or suspending the running BWP inactivity timer; not monitoring PDCCH; not receiving PDSCH; not sending PUSCH; not sending SRS; clearing the configured downlink allocation and configured uplink authorization of configuration authorization type 2; suspending the configured uplink authorization of configuration authorization type 1.

[0041] In conjunction with some embodiments of the third aspect, in some embodiments, the apparatus may further include a transceiver module configured to receive first information for instructing the terminal to stop a running BWP inactivity timer.

[0042] In combination with some embodiments of the third aspect, in some embodiments, the processing module may be configured to execute the second behavior when the terminal leaves the first state.

[0043] In combination with some embodiments of the third aspect, in some embodiments, the second behavior may include at least one of the following: restarting or resuming the BWP inactivity timer; monitoring PDCCH; receiving PDSCH; sending PUSCH; sending SRS; initializing the suspended configuration uplink authorization of configuration authorization type 1 related to the service cell.

[0044] In combination with some embodiments of the third aspect, in some embodiments, when the BWP in which the terminal is located before entering the first state is the same as the BWP after leaving the first state, the second behavior may include: resuming the BWP inactivity timer.

[0045] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module may be configured to receive second information. The second information is used to instruct the terminal to restart the BWP inactivity timer. The second action may include: restarting the BWP inactivity timer based on the second information.

[0046] In combination with some embodiments of the third aspect, in some embodiments, when the BWP where the first transceiver is located is a dormant BWP or a deactivated BWP, the first behavior may be the same as the behavior before the terminal enters the first state.

[0047] In a fourth aspect, embodiments of the present disclosure provide a communications device. The device includes a transceiver module. The transceiver module is configured to transmit first information. The first information is used to instruct a terminal to stop a running BWP inactivity timer. The terminal includes a first transceiver and a second transceiver. The second transceiver is used to receive a wake-up signal. The wake-up signal is used to wake up the first transceiver.

[0048] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may be further configured to send second information. The second information is used to instruct the terminal to restart the BWP inactivity timer.

[0049] In a fifth aspect, an embodiment of the present disclosure provides a terminal. The terminal includes at least one processor. The terminal is configured to execute the method described in any one of the first aspect and its embodiments.

[0050] In a sixth aspect, embodiments of the present disclosure provide a network device. The network device includes at least one processor. The network device is configured to execute the method described in any one of the second aspect and its embodiments.

[0051] In a seventh aspect, embodiments of the present disclosure provide a communication system. The communication system includes a terminal and a network device. The terminal is configured to implement the method described in any one of the first aspect and its embodiments. The network device is configured to implement the method described in any one of the second aspect and its embodiments.

[0052] In an eighth aspect, a storage medium is provided. The storage medium stores instructions. When the instructions are executed by a processor, the method according to any one of the first aspect, the second aspect, and the embodiments thereof is implemented.

[0053] In a ninth aspect, a computer program or computer program product is provided. The computer program or computer program product comprises code. When executed by a processor, the code performs the method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0054] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, computer programs, and computer program products are all used to execute the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0055] The present disclosure provides a communication method, terminal, network device, communication system, and storage medium. In some embodiments, the terms management method, communication method, information processing method, and information transmission method are interchangeable; the terms communication device, information processing device, and information transmission device are interchangeable; and the terms communication system, information processing system, and information processing system are interchangeable.

[0056] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0057] In the embodiments of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0058] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0059] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0060] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0061] In some embodiments, the terms "at least one", "one or more", etc. can be used interchangeably.

[0062] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0063] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0064] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0065] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0066] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0067] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0068] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0069] In some embodiments, "network" can be interpreted as devices included in the network (for example, access network equipment, core network equipment, data network equipment, etc.).

[0070] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0071] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0072] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0073] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0074] In some embodiments, a network device may also be referred to as a network function, a network function entity, or a network element.

[0075] In some embodiments, the access network device may also be referred to as an access network function, an access network element, etc.

[0076] In some embodiments, core network devices may also be referred to as core network functions, core networks, core network elements, etc. Furthermore, in some embodiments, each network device in the core network may also be referred to as a network device, a network element, etc.

[0077] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0078] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0079] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

[0080] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things (IoT) device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0081] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0082] In some embodiments, the network device 102 in the communication system 100 may be replaced with another terminal.

[0083] In some embodiments, the communication system 100 may include at least two terminals, and these terminals may communicate using the communication method of the embodiments of the present disclosure.

[0084] In some embodiments, the terminal 101 in the communication system 100 may be replaced by another network device.

[0085] In some embodiments, the communication system 100 may include at least two network devices, and these network devices may communicate using the communication method of the embodiments of the present disclosure.

[0086] In some embodiments, the access network device may be, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a satellite base station, a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0087] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces within the network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0088] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0089] In some embodiments, the core network device may be a single device, multiple devices, or a group of devices. The access network device may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), or a next-generation core (NGC).

[0090] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0091] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0092] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0093] In the field of communications technology, terminal power consumption is a significant constraint on terminal application scenarios and user experience. High power consumption not only shortens the terminal's standby time but also places higher demands on terminal heat dissipation.

[0094] In some embodiments, power-saving mechanisms such as a low-power-wakeup signal (LP-WUS) can be used for terminals in the connected state. For terminals in the radio resource control (RRC) connected state, the ultra-deep sleep state is no longer applicable. Instead, in terminals using power-saving mechanisms, the primary transceiver is not completely shut down and can perform some measurements without monitoring the PDCCH.

[0095] In some embodiments, the terminal's primary transceiver may be in sleep mode on an active BWP. In this case, PDCCH monitoring is also stopped. In this case, after the BWP inactivity timer (enabled on the active BWP) expires, the primary transceiver will perform BWP fallback. For a terminal that is already in sleep mode, this BWP fallback is unnecessary.

[0096] In some cases, upon receiving a wake-up signal, the terminal's behavior on the active BWP may change, and such a change needs to be defined.

[0097] FIG2 is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in FIG2, the method includes steps S210 to S270.

[0098] In step S210 , the network device 102 sends first indication information to the terminal 101 .

[0099] In some embodiments, the terminal 101 may receive first indication information from the network device 102 .

[0100] In some embodiments, the first indication information may be used to instruct the terminal 101 to enter the first state. In other words, the first indication information may be used to instruct the terminal 101 to activate the first state. In this case, the first indication information may be used to "explicitly" instruct the terminal 101 to enter the first state.

[0101] In some embodiments, the terminal may be in a connected state (RRC_connected). Of course, the terminal may also be in other states, which are not specifically limited in the embodiments of the present disclosure.

[0102] In step S220 , the terminal 101 determines to enter the first state.

[0103] In some embodiments, the terminal 101 may determine to enter the first state on its own.

[0104] In some embodiments, the terminal 101 may include a first timer. The first timer is used to time a state in which the terminal has no data transmission.

[0105] In some embodiments, if terminal 101 has not transmitted data within the duration of a first timer, terminal 101 may determine that it has entered the first state. In one example, the first timer may start timing when terminal 101 has not transmitted data. If terminal 101 starts transmitting data while the first timer is running, the first timer may stop. If the first timer times out, it indicates that terminal 101 has not transmitted data within the duration of the first timer, and terminal 101 may determine that it has entered the first state. In this case, the first timer may be used to "implicitly" indicate that terminal 101 has entered the first state.

[0106] In step S230, the terminal 101 enters the first state.

[0107] In some embodiments, after receiving the first indication information in step S210 or determining to enter the first state in step S220, the terminal 101 may enter the first state. In one example, when entering the first state according to step S210, the terminal 101 may be considered to have activated the first state. In another example, when entering the first state according to step S220, the terminal 101 may be considered to have "actively" entered the first state.

[0108] In some embodiments, terminal 101 may include two or more transceivers. These transceivers include at least a first transceiver and a second transceiver. In one embodiment, the first transceiver may be the terminal's primary transceiver. The primary transceiver may be used for measurement, monitoring, communication, etc. of the terminal. In one embodiment, the second transceiver may be a secondary transceiver of the terminal. For example, the second transceiver may be a low-power wake-up transceiver.

[0109] In some embodiments, the first state may be referred to as a low power consumption state, an ultra power saving state, a low power consumption wake-up signal state (LP-WUS state), etc., and the embodiments of the present disclosure do not specifically limit this.

[0110] In some embodiments, in the first state, the first transceiver may be in a partially shut down state or in a dormant state. In the partially shut down state, some functions of the first transceiver are disabled. Simultaneously, in the first state, the second transceiver may be in an active state. In this case, the second transceiver is configured to receive a wake-up signal. This wake-up signal is used to wake up the first transceiver to monitor data.

[0111] In some embodiments, the BWP where the first transceiver resides can be one of the following: an activated BWP and a deactivated BWP. Specifically, the types of BWPs available to terminal 101 include activated BWPs and deactivated BWPs. It is understood that "the BWP where the first transceiver resides" means that the first transceiver can operate on this BWP or that the first transceiver can transmit and receive data on this BWP.

[0112] The first transceiver may operate in one of an active BWP and a deactivated BWP. In some embodiments, the active BWP may include a dormant BWP and a non-dormant BWP.

[0113] In some embodiments, the BWP where the first transceiver is located may be associated with a BWP inactivity timer.

[0114] In step S240 , the terminal 101 performs a first action.

[0115] In some embodiments, after entering the first state, the terminal 101 may execute a corresponding first behavior.

[0116] In some embodiments, the first behavior may include at least one of the following: stopping or suspending a running BWP inactivity timer; not monitoring the PDCCH; not receiving the PDSCH; not sending the PUSCH; not sending the SRS; clearing the configured downlink allocation and configured uplink grant of configured grant type 2; suspending the configured uplink grant of configured grant type 1; sending a random access channel (RACH); sending a scheduling request (SR); and performing beam failure detection (BFD). It is understandable that the first behavior may also include other operations, which are not specifically limited in the embodiments of the present disclosure.

[0117] In some embodiments, when or after terminal 101 enters the first state, if a BWP inactivity timer of terminal 101 is running, the BWP inactivity timer can be stopped or suspended. Stopping means clearing or resetting the BWP inactivity timer. Suspending means temporarily suspending the BWP inactivity timer without clearing it. In one example, if the BWP inactivity timer associated with the BWP in which the first transceiver is located is running, the BWP inactivity timer can be stopped or suspended.

[0118] In some embodiments, the terminal 101 may not monitor the PDCCH. For example, the first transceiver of the terminal 101 may not be used to receive scheduling information or other control information carried in the PDCCH.

[0119] In some embodiments, the terminal 101 may not receive the PDSCH. For example, the first transceiver of the terminal 101 may not be used to receive data carried in the PDSCH.

[0120] In some embodiments, the terminal 101 may not transmit the PUSCH. For example, the first transceiver of the terminal 101 may not be used to transmit the PUSCH.

[0121] In some embodiments, the terminal 101 may not transmit an SRS. For example, the first transceiver of the terminal 101 may not be used to transmit an SRS.

[0122] In some embodiments, the non-dynamic transmission mode of the PUSCH by the terminal 101 may include the following two types: configured grant Type 1 and configured grant Type 2. The BWP where the first transceiver is located may be configured with these two types of configuration grants.

[0123] In some embodiments, the terminal 101 may clear the configured downlink assignment and the configured uplink grant of configuration grant type 2. Here, the configured downlink assignment and the configured uplink grant of configuration grant type 2 correspond to the BWP where the first transceiver is located.

[0124] In some embodiments, the terminal 101 may suspend a configuration uplink grant of configuration grant type 1. Here, the configuration uplink grant of configuration grant type 1 corresponds to the BWP where the first transceiver is located.

[0125] In some embodiments, the terminal 101 may transmit a RACH. For example, the first transceiver of the terminal 101 may be configured to transmit the RACH.

[0126] In some embodiments, the terminal 101 may send an SR. For example, the first transceiver of the terminal 101 may be configured to send an SR.

[0127] In some embodiments, the terminal 101 may perform BFD. For example, the terminal 101 may perform BFD via the first transceiver.

[0128] In some embodiments, in the scenario of carrier aggregation (CA), the network device 102 may include a primary cell (PCell) and at least one secondary cell (SCell). Furthermore, in combination with dual connectivity (DC), the network device 102 may include not only a master cell group (MCG) but also a secondary cell group (SCG). The MCG may include a PCell and at least one SCell. The SCG may include a primary secondary cell (PSCell) and at least one SCell. The PCell and / or PSCell may be used for signaling transmission. The BWP where the first transceiver of the terminal 101 is located may correspond to one of the PCell, PSCell, and SCell.

[0129] In some embodiments, the BWP where the first transceiver is located may be a first BWP. The first BWP is an activated BWP and not a dormant BWP, and the serving cell corresponding to the first BWP is not a PSCell with a deactivated SCG. For the first BWP, the terminal 101 may perform a first behavior.

[0130] In some embodiments, the BWP in which the first transceiver resides may be a dormant BWP. In this case, the first behavior performed by terminal 101 in the first state may be the same as the behavior before entering the first state. It is understood that before entering the first state, since the first transceiver of terminal 101 is in the dormant BWP, the behavior of terminal 101 may conform to the aforementioned first behavior. Therefore, after entering the first state, terminal 101 may maintain this behavior.

[0131] In some embodiments, the BWP in which the first transceiver resides may be a deactivated BWP. In this case, the first behavior performed by terminal 101 in the first state may be the same as the behavior before entering the first state. It is understood that before entering the first state, since the first transceiver of terminal 101 is in a deactivated BWP, the behavior of terminal 101 may conform to the aforementioned first behavior. Therefore, after entering the first state, terminal 101 may maintain this behavior.

[0132] In some embodiments, terminal 101 may stop the BWP inactivity timer in response to the first information. The first information may be used to instruct terminal 101 to stop the currently running BWP inactivity timer. Specifically, after receiving the first information, terminal 101 may stop the currently running BWP inactivity timer based on the first information. In one embodiment, the first information may be from network device 102 or another entity. In one embodiment, the first information may be carried in the first indication information in step S210. In this case, terminal 101 may obtain the first information upon receiving the first indication information. In one embodiment, the first information may be sent to terminal 101 by network device 102 via another message. This message may be sent to terminal 101 before, simultaneously with, or after the first indication information.

[0133] In step S250 , the network device 102 sends a wake-up signal to the terminal 101 .

[0134] In some embodiments, terminal 101 may receive a wake-up signal.

[0135] In some embodiments, the terminal 101 in the first state may receive a wake-up signal through the second transceiver.

[0136] In some embodiments, after receiving the wake-up signal, the terminal 101 may determine to leave the first state according to the wake-up signal. In one example, according to the wake-up signal, the second transceiver of the terminal 101 may wake up the first transceiver.

[0137] In step S260 , the terminal 101 leaves the first state.

[0138] In some embodiments, when the terminal 101 wakes up the first transceiver, it means that the terminal 101 leaves the first state.

[0139] In some embodiments, after leaving the first state, the second transceiver of the terminal 101 may continue to work, or stop working.

[0140] In step S270 , terminal 101 performs a second action.

[0141] In some embodiments, after leaving the first state, the terminal 101 may perform a corresponding second behavior.

[0142] In some embodiments, the second behavior may include at least one of the following: restarting or resuming the BWP inactivity timer; monitoring PDCCH; receiving PDSCH; sending PUSCH; sending SRS; initializing the suspended configuration uplink grant of configuration grant type 1 related to the serving cell.

[0143] In some embodiments, if the terminal 101 suspends the BWP inactivity timer in step S240, the second action performed by the terminal 101 may include resuming the previously suspended BWP inactivity timer. The suspended BWP inactivity timer may then continue to run after being resumed. In this case, the BWP in which the first transceiver is located before the terminal 101 enters the first state and the BWP in which the first transceiver is located after leaving the first state may be the same.

[0144] In some embodiments, when terminal 101 stops the BWP inactivity timer in step S240, the second action performed by terminal 101 may include restarting the previously stopped BWP inactivity timer. In this case, restarting the BWP inactivity timer may also be referred to as resetting the BWP inactivity timer. In this case, the BWP in which the first transceiver is located before terminal 101 enters the first state and the BWP in which the first transceiver is located after leaving the first state may be the same or different.

[0145] In some embodiments, when the BWP where the first transceiver is located is a non-dormant BWP of the activated BWP type and is not a default BWP or an initial BWP, the terminal 101 may restart the BWP inactivity timer corresponding to the BWP in response to the second information.

[0146] In some embodiments, the second information may be carried in the wake-up signal. In this case, the terminal 101 may restart the BWP inactivity timer simultaneously with or after waking up the first transceiver.

[0147] In some embodiments, the second information may be received by terminal 101 after terminal 101 enters the first state. In this case, terminal 101 may restart the BWP inactivity timer after terminal 101 enters the first state. In some embodiments, the second information may include downlink control information (DCI) or other information.

[0148] In some embodiments, the terminal 101 may monitor the PDCCH. For example, the first transceiver of the terminal 101 may be configured to receive scheduling information or other control information carried in the PDCCH.

[0149] In some embodiments, the terminal 101 may receive a PDSCH. For example, the first transceiver of the terminal 101 may be configured to receive data carried in the PDSCH.

[0150] In some embodiments, the terminal 101 may transmit a PUSCH. For example, the first transceiver of the terminal 101 may be configured to transmit the PUSCH.

[0151] In some embodiments, the terminal 101 may transmit an SRS. For example, the first transceiver of the terminal 101 may not transmit an SRS.

[0152] In some embodiments, the terminal 101 may initialize (or reinitialize) a configuration uplink grant of configuration grant type 1. Here, the configuration uplink grant of configuration grant type 1 corresponds to the BWP where the first transceiver is located.

[0153] The communication method involved in the embodiments of the present disclosure may include at least one of steps S210 to S270. For example, step S210 can be implemented as an independent embodiment, step S240 can be implemented as an independent embodiment, step S250 can be implemented as an independent embodiment, step S270 can be implemented as an independent embodiment, the combination of steps S240 and S270 can be implemented as an independent embodiment, the combination of steps S260 and S270 can be implemented as an independent embodiment, and the combination of steps S210, S230, and S240 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0154] In some embodiments, steps S210 and S220 may be alternative embodiments, and steps S210 or S220 may be selectively performed in different embodiments.

[0155] In some embodiments, steps S230 and S240 may be performed sequentially or simultaneously.

[0156] In some embodiments, steps S260 and S270 may be performed sequentially or simultaneously.

[0157] In some embodiments, steps S220, S230, S240, S250, S260, and S270 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0158] In some embodiments, steps S210, S220, S230, S250, S260, and S270 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0159] In some embodiments, steps S210, S220, S230, S240, S260, and S270 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0160] In some embodiments, steps S210, S220, S230, S240, S250, and S260 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0161] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0162] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0163] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0164] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0165] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0166] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0167] In some embodiments, terms such as "synchronization signal (SS)", "synchronization signal block (SSB)", "reference signal (RS)", "pilot", and "pilot signal" can be used interchangeably.

[0168] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0169] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0170] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0171] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0172] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0173] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0174] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0175] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0176] FIG3 is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. The communication method in this embodiment can be applied to terminal 101. As shown in FIG3, the method includes steps S310 to S370.

[0177] In step S310, first indication information is obtained.

[0178] The optional implementation of step S310 can refer to the optional implementation of step S210 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0179] In some embodiments, the terminal 101 may receive the first indication information sent by the network device 102, but is not limited thereto and may also receive the first indication information sent by other entities.

[0180] In some embodiments, the first indication information may also be referred to as state transition indication information, sleep indication information, etc., but is not limited thereto, and the embodiments of the present disclosure do not make specific limitations on this.

[0181] In some embodiments, the first indication information may include first information. The first information is used to instruct the terminal 101 to stop the running BWP inactivity timer. Of course, the first information may also be received by the terminal 101 independently of the first indication information, which is not specifically limited in the embodiments of the present disclosure.

[0182] In step S320 , it is determined to enter the first state.

[0183] The optional implementation of step S320 can refer to the optional implementation of step S220 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0184] In step S330, the first state is entered.

[0185] The optional implementation of step S330 can refer to the optional implementation of step S230 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0186] In step S340 , the first behavior is executed.

[0187] The optional implementation of step S340 can refer to the optional implementation of step S240 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0188] In step S350 , a wake-up signal is acquired.

[0189] The optional implementation of step S350 can refer to the optional implementation of step S250 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0190] In some embodiments, the terminal 101 may receive a wake-up signal sent by the network device 102 , but is not limited thereto and may also receive a wake-up signal sent by other entities.

[0191] In some embodiments, the wake-up signal may include second information. The second information is used to instruct the terminal 101 to restart the BWP inactivity timer. Of course, the second information may also be received by the terminal 101 independently of the wake-up signal, which is not specifically limited in the present embodiment.

[0192] In step S360, the first state is left.

[0193] The optional implementation of step S360 can refer to the optional implementation of step S260 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0194] In step S370, the second behavior is performed.

[0195] The optional implementation of step S370 can refer to the optional implementation of step S270 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0196] The communication method involved in the embodiments of the present disclosure may include at least one of steps S310 to S370. For example, step S310 can be implemented as an independent embodiment, step S340 can be implemented as an independent embodiment, step S350 can be implemented as an independent embodiment, step S370 can be implemented as an independent embodiment, the combination of steps S340 and S370 can be implemented as an independent embodiment, the combination of steps S360 and S370 can be implemented as an independent embodiment, and the combination of steps S310, S330, and S340 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0197] In some embodiments, steps S310 and S320 may be alternative embodiments, and step S310 or S320 may be selectively performed in different embodiments.

[0198] In some embodiments, steps S330 and S340 may be performed sequentially or simultaneously.

[0199] In some embodiments, steps S360 and S370 may be performed sequentially or simultaneously.

[0200] In some embodiments, steps S320, S330, S340, S350, S360, and S370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0201] In some embodiments, steps S310, S320, S330, S350, S360, and S370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0202] In some embodiments, steps S310, S320, S330, S340, S360, and S370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0203] In some embodiments, steps S310, S320, S330, S340, S350, and S360 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0204] Figure 4 is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. The communication method in this embodiment can be applied to the network device 102. As shown in Figure 4, the method includes steps S410 to S420.

[0205] In step S410, first indication information is sent.

[0206] The optional implementation of step S410 can refer to the optional implementation of step S210 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0207] In some embodiments, the first indication information may be used to instruct the terminal 101 to enter the first state.

[0208] In some embodiments, the first indication information may include first information. The first information is used to instruct the terminal 101 to stop the running BWP inactivity timer. Of course, the first information may also be sent by the network device 102 independently of the first indication information, which is not specifically limited in the embodiments of the present disclosure.

[0209] In step S420, a wake-up signal is sent.

[0210] The optional implementation of step S420 can refer to the optional implementation of step S250 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0211] In some embodiments, the wake-up signal may be used to instruct the terminal 101 to leave the first state.

[0212] In some embodiments, the wake-up signal may include second information. The second information is used to instruct the terminal 101 to restart the BWP inactivity timer. Of course, the second information may also be sent by the network device 102 independently of the wake-up signal, which is not specifically limited in the present embodiment.

[0213] The communication method involved in the embodiment of the present disclosure may include at least one of steps S410 to S420. For example, step S410 may be implemented as an independent embodiment, step S420 may be implemented as an independent embodiment, and the combination of steps S410 and S420 may be implemented as an independent embodiment.

[0214] In some embodiments, step S420 is optional and may be omitted or replaced in different embodiments.

[0215] In some embodiments, step S410 is optional and may be omitted or replaced in different embodiments.

[0216] FIG5 is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , an embodiment of the present disclosure relates to a communication method. The method includes steps S510 to S520.

[0217] In step S510 , the network device 102 sends first information to the terminal 101 .

[0218] Optional implementations of step S510 can refer to the optional implementations of step S210 in Figure 2, step S310 in Figure 3, step S410 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0219] In step S520 , when the terminal 101 enters the first state, a first action is executed.

[0220] Optional implementations of step S520 can refer to the optional implementations of step S240 in FIG. 2 , step S340 in FIG. 3 , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 , which will not be described in detail here.

[0221] The communication method according to the embodiments of the present disclosure may include at least one of steps S510 to S520. For example, step S510 may be implemented as an independent embodiment, step S520 may be implemented as an independent embodiment, and a combination of steps S510 and S520 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0222] In some embodiments, steps S510 and S520 may be performed in an interchangeable order or simultaneously.

[0223] In some embodiments, step S510 is optional and may be omitted or replaced in different embodiments.

[0224] In some embodiments, step S520 is optional and may be omitted or replaced in different embodiments.

[0225] Hereinafter, the solutions of the embodiments of the present disclosure are exemplified by using specific examples.

[0226] In some embodiments, for a terminal in a connected state, the main transceiver (i.e., the first transceiver) of the terminal 101 is not completely turned off or is in a dormant state when a low power wake-up signal (LP-WUS) mechanism is adopted. At this time, the terminal 101 can perform operations such as RRM, but does not perform PDCCH monitoring. For the terminal, if the main transceiver on the activated BWP is already dormant at the time, the monitoring of the PDCCH has stopped. According to the current mechanism, after the BWP inactivity timer expires, the main transceiver of the terminal 101 will still perform BWP fallback. However, when the main transceiver is dormant, such BWP fallback is unnecessary. At the same time, after receiving the wake-up signal, the behavior of the main transceiver of the terminal 101 on the BWP also needs to be determined.

[0227] In some embodiments, the behavior of the terminal 101 in the protection connected state when entering the low power consumption state or when the low power consumption state is activated (ie, the first state) is as follows:

[0228] (1) Low power consumption state: the terminal is activated or the terminal 101 starts a low power consumption wake-up transceiver (ie, the second transceiver) to receive a low power consumption wake-up signal, which is used to wake up the main transceiver for data monitoring.

[0229] (2) Low power consumption state: that is, some functions of the main transceiver of the terminal 101 are turned off (for example, monitoring of the PDCCH is stopped) or in a dormant state.

[0230] (3) The low power consumption state of the terminal 101 may be activated based on the following two situations: the network sends an explicit indication (i.e., the first indication information) to activate the low power consumption monitoring, and there is no data transmission within the timer (i.e., the first timer).

[0231] In some embodiments, the behavior (i.e., the first behavior) of the connected terminal 101 after entering the low power consumption state (or activating the low power consumption state) may include at least one of the following:

[0232] (1) If the BWP inactivity timer is running or started, stop or suspend the BWP inactivity timer;

[0233] (2) Terminal 101 cannot monitor PDCCH;

[0234] (3) Terminal 101 does not receive PDSCH;

[0235] (4) Terminal 101 does not send PUSCH;

[0236] (5) Terminal 101 does not send SRS;

[0237] (6) Clear the configuration downlink allocation and configuration uplink authorization of configuration authorization type 2 for BWP;

[0238] (7) Suspend the configuration uplink authorization of configuration authorization type 1 for BWP.

[0239] (8) The terminal can send RACH;

[0240] (9) The terminal can send SR;

[0241] (10) The terminal can perform BFD.

[0242] In one example, for an activated BWP (the activated BWP is not a dormant BWP and the SCell to which the BWP belongs is not the primary cell of a deactivated SCG), when LP-WUS monitoring is activated, the media access control (MAC) entity (i.e., the terminal 101) may perform at least one of the following:

[0243] (1) Do not monitor PDCCH on this BWP;

[0244] (2) The downlink shared channel (DL-SCH) is not received on the BWP;

[0245] (3) No SRS is sent on this BWP;

[0246] (4) The uplink shared channel (UL-SCH) is not sent on the BWP;

[0247] (5) Clear the configuration downlink allocation and configuration uplink authorization of configuration authorization type 2 for the BWP;

[0248] (6) Suspend the configuration uplink authorization of configuration authorization type 1 for the BWP;

[0249] (7) Stop or suspend the BWP inactivity timer running in the serving cell;

[0250] (8) The terminal can send RACH;

[0251] (9) The terminal can send SR;

[0252] (10) The terminal can perform BFD.

[0253] In some embodiments, after the connected terminal 101 leaves the low power state (or the low power state is deactivated), if the activated BWP is a non-dormant BWP, at this time, the BWP activated after the terminal leaves the low power state may be the same as or different from the BWP activated when the terminal enters the low power state, then the behavior of the terminal 101 (ie, the second behavior) may include at least one of the following:

[0254] (1) If a BWP inactivity timer was running on the active BWP before entering the low power state, and the BWP inactivity timer was suspended, the BWP inactivity timer is resumed (at this time, the BWP is not replaced, that is, the BWP activated after the terminal leaves the low power state may be the same as the BWP activated when the terminal enters the low power state);

[0255] (2) If the activated BWP is a non-dormant BWP, a non-default BWP, or an initial BWP, the BWP inactivity timer may be started when the DCI (i.e., the second information) is detected;

[0256] (3) Terminal 101 can monitor PDCCH;

[0257] (4) Terminal 101 can receive PDSCH;

[0258] (5) Terminal 101 may send PUSCH;

[0259] (6) Terminal 101 may send SRS;

[0260] (7) Initialize or reinitialize the pending configuration uplink grant of configuration grant type 1 related to the serving cell.

[0261] In one example, for an activated BWP (the activated BWP is not a dormant BWP and the SCell to which the BWP belongs is not the primary cell of a deactivated SCG), when LP-WUS monitoring is deactivated, the MAC entity may perform at least one of the following:

[0262] (1) Send UL-SCH on BWP;

[0263] (2) If a physical random access channel (PRACH) opportunity is configured, RACH is sent on the BWP;

[0264] (3) Monitor PDCCH on BWP;

[0265] (4) Sending the possible configured PUCCH on the BWP;

[0266] (5) Reporting channel state information (CSI) for BWP;

[0267] (6) Sending the possible configured SRS on the BWP;

[0268] (7) receiving DL-SCH on BWP;

[0269] (8) Initialize or re-initialize the pending configuration uplink grant of configuration grant type 1 for activating the BWP, based on any existing stored configuration;

[0270] (9) Start, restart or resume the BWP inactivity timer associated with the activated DL BWP of the serving cell.

[0271] In some embodiments, when the activated BWP is a non-dormant BWP and the SCell where the activated BWP is located is not the PSCell in the deactivated SCG, the connected terminal can perform the first behavior and the second behavior after entering the low power consumption state (or the low power consumption state is activated).

[0272] In some embodiments, when the activated BWP is a dormant BWP, the terminal in the connected state may maintain the behavior unchanged on the BWP after entering the low power consumption state (or the low power consumption state is activated).

[0273] In some embodiments, when the BWP is a deactivated BWP, or when the service cell corresponding to the BWP is a PSCell of a deactivated SCG, the connected terminal can maintain unchanged behavior on the activated BWP after entering a low power consumption state (or being activated to a low power consumption state).

[0274] In some embodiments, the network device 102 may instruct the terminal in the connected state whether to stop the BWP inactivity timer after entering the low power consumption state (or activating the low power consumption state). It is understood that when it is determined that the sleep time of the primary transceiver of the terminal 101 is long, in order to avoid BWP switching of the primary transceiver during the sleep process, the network device 102 may instruct the terminal 101 to stop the BWP inactivity timer.

[0275] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0276] The embodiments of the present disclosure also provide a communication device for implementing any of the above methods. For example, the embodiments of the present disclosure provide a communication device. The communication device includes units or modules for implementing each step performed by a terminal in any of the above methods. In this case, the communication device can be provided in the terminal. For another example, the embodiments of the present disclosure also provide another communication device, including units or modules for implementing each step performed by a network device in any of the above methods. In this case, the communication device can be provided in the network device.

[0277] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0278] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by a dedicated integrated circuit or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0279] FIG6 is an exemplary structural diagram of a communication device according to an embodiment of the present disclosure. The communication device 600 may include a transceiver module 601 and a processing module 602 .

[0280] In some embodiments, the transceiver module 601 can be used to execute at least one of the reception-related steps (for example, steps S210, S250, S310, S350, S410, S420, S510, S530, but not limited thereto) performed by the terminal 101 in any of the above methods.

[0281] In some embodiments, the processing module 602 can be used to execute at least one of the steps (for example, steps S220 to S240, S260, S270, S320 to S340, S360, S370, S520, but not limited to) related to the processing (including entry, determination, exit, execution) performed by the terminal 101 in any of the above methods.

[0282] FIG7 is an exemplary structural diagram of a communication device according to an embodiment of the present disclosure. The communication device 700 may include a transceiver module 701 .

[0283] In some embodiments, the transceiver module 701 can be used to execute at least one of the sending-related steps (for example, steps S210, S250, S310, S350, S410, S420, S510, S530, but not limited to these) performed by the network device 102 in any of the above methods.

[0284] Figure 8 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 800 can be a network device (e.g., an access network device or a core network device), a terminal (e.g., a user device), a chip, a chip system, or a processor that supports a network device implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above communication methods. Communication device 800 can be used to implement the communication methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0285] As shown in Figure 8, the communication device 800 includes one or more processors 801. The processor 801 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a network device, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute programs, and process program data. The processor 801 is used to call instructions to enable the communication device 800 to execute any of the above communication methods.

[0286] In some embodiments, the communication device 800 further includes one or more memories 802 for storing instructions. Optionally, all or part of the memories 802 may be located outside the communication device 800.

[0287] In some embodiments, the communication device 800 further includes one or more transceivers 803. When the communication device 800 includes one or more transceivers 803, the communication steps such as sending and receiving in the above method are performed by the transceiver 803, and the other steps are performed by the processor 801.

[0288] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, transceiver, and receiving circuit may be used interchangeably.

[0289] Optionally, the communication device 800 further includes one or more interface circuits 804, which are connected to the memory 802. The interface circuit 804 can be used to receive signals from the memory 802 or other devices, and can be used to send signals to the memory 802 or other devices. For example, the interface circuit 804 can read instructions stored in the memory 802 and send the instructions to the processor 801.

[0290] The communication device 800 described in the above embodiment may be an access network device, a core network device, an external network device or a terminal, but the scope of the communication device 800 described in the present disclosure is not limited thereto, and the structure of the communication device 800 may not be limited by FIG8 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a transceiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) other devices.

[0291] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 800, the communication device 800 executes any of the above communication methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0292] The present disclosure further provides a program product, which, when executed by the communication device 800, enables the communication device 800 to perform any of the above communication methods. Optionally, the program product is a computer program product.

[0293] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0294] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0295] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method, comprising: When the terminal enters the first state, executing a first behavior; The terminal includes a first transceiver and a second transceiver, the second transceiver is used to receive a wake-up signal, and the wake-up signal is used to wake up the first transceiver.

2. The method according to claim 1, wherein: The first behavior includes at least one of the following: Stop or suspend the running bandwidth part BWP inactivity timer; Do not monitor the physical downlink control channel PDCCH; The physical downlink shared channel PDSCH is not received; The physical uplink shared channel PUSCH is not sent; Do not send a sounding reference signal SRS; Clear the configuration downlink allocation and configuration uplink authorization of configuration authorization type 2; Suspend configuration uplink authorization of configuration authorization type 1.

3. The method according to claim 2, wherein: The method further comprises: First information is received, wherein the first information is used to instruct the terminal to stop a running BWP inactivity timer.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: When the terminal leaves the first state, a second action is performed.

5. The method according to claim 4, wherein: The second behavior includes at least one of the following: Restart or resume the BWP inactivity timer; Monitor PDCCH; Receive PDSCH; Send PUSCH; Send SRS; Initialize the suspended configuration uplink authorization of configuration authorization type 1 related to the serving cell.

6. The method according to claim 5, wherein: In a case where the BWP of the terminal before entering the first state is the same as the BWP of the terminal after leaving the first state, the second behavior includes: Resume the BWP inactivity timer.

7. The method according to claim 5, wherein: The method further comprises: receiving second information, wherein the second information is used to instruct the terminal to restart the BWP inactivity timer; The second behavior includes: restarting the BWP inactivity timer according to the second information.

8. The method according to any one of claims 1 to 7, wherein: In a case where the BWP where the first transceiver is located is a dormant BWP or a deactivated BWP, the first behavior is the same as a behavior of the terminal before entering the first state.

9. A communication method, comprising: Sending first information, wherein the first information is used to instruct the terminal to stop a running bandwidth part BWP inactivity timer; The terminal includes a first transceiver and a second transceiver, wherein the second transceiver is used to receive a wake-up signal, and the wake-up signal is used to wake up the first transceiver.

10. The method according to claim 9, wherein: The method further comprises: Sending second information, wherein the second information is used to instruct the terminal to restart the BWP inactivity timer.

11. A terminal, comprising: A processing module, configured to execute a first behavior when the terminal enters a first state; The terminal includes a first transceiver and a second transceiver, wherein the second transceiver is used to receive a wake-up signal, and the wake-up signal is used to wake up the first transceiver.

12. A network device comprising: A transceiver module, configured to send first information, wherein the first information is used to instruct the terminal to stop the running BWP inactivity timer; The terminal includes a first transceiver and a second transceiver, wherein the second transceiver is used to receive a wake-up signal, and the wake-up signal is used to wake up the first transceiver.

13. A terminal, comprising: at least one processor; The terminal is used to execute the method as claimed in any one of claims 1 to 8.

14. A network device comprising: at least one processor; The network device is used to execute the method according to claim 9 or 10.

15. A communication system, comprising a terminal and a network device, wherein: The terminal is configured to implement the method according to any one of claims 1 to 8, and the network device is configured to implement the method according to claim 9 or 10.

16. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 10 is performed.

Images