Communication methods, terminals, network devices, communication system and storage medium

Abstract

The embodiments of the present disclosure provide communication methods, terminals, network devices, a communication system and a storage medium. A method comprises: a terminal sending first information to a network device, wherein the first information is used for indicating frequency domain information of the terminal supporting monitoring of a low-power signal. In the method of the present disclosure, the terminal sends the first information to the network device to report the frequency domain information that the terminal supports when monitoring a low-power signal, such that the network device can know the capability of the terminal conveniently, and can conveniently perform reasonable control or configuration operations on the basis of the related capability of the terminal.

Description

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

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

[0002] The base station can send a low-power signal to the terminal to wake it up. The terminal can keep the main transceiver in sleep mode and use a separate low-power wake-up signal receiver (LP WUR) to listen for and receive the low-power signal. After receiving the low-power signal, the main transceiver can be woken up to perform operations such as data transmission and reception.

[0003] Summary of the Invention

[0004] In order to reduce the cost of LP WUR, the functions supported by LP WUR are relatively simple.

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

[0006] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0007] The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low-power consumption signal.

[0008] In a second aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0009] The network device receives first information sent by the terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low-power consumption signal.

[0010] In a third aspect, an embodiment of the present disclosure provides a communication method, including:

[0011] The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of the low-power signal;

[0012] The network device receives the first information.

[0013] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0014] The transceiver module is used to send first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power consumption signals.

[0015] In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

[0016] The transceiver module is used to receive first information sent by a terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power consumption signals.

[0017] In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

[0018] one or more processors;

[0019] The terminal is used to execute the communication method described in the first aspect.

[0020] In a seventh aspect, an embodiment of the present disclosure provides a network device, including:

[0021] one or more processors;

[0022] Wherein, the network device is used to execute the communication method described in the second aspect.

[0023] In an eighth aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0024] The terminal is configured to implement the communication method according to the first aspect;

[0025] The network device is configured to implement the communication method described in the second aspect.

[0026] In a ninth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0027] When the instruction is executed on a communication device, the communication device is caused to execute the method as described in any one of the first aspect or the second aspect.

[0028] In the method disclosed herein, the terminal sends first information to the network device to report the frequency domain information that the terminal can support when monitoring low-power signals, thereby facilitating the network device to learn the capabilities of the terminal and perform reasonable control or configuration operations based on the relevant capabilities of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0030] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0031] 2a to 2c are exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure;

[0032] 3a to 3c are schematic flow diagrams of a method performed by a terminal according to an embodiment of the present disclosure;

[0033] 4a to 4c are flowcharts of methods performed by a network device according to an embodiment of the present disclosure;

[0034] FIG5 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure;

[0035] FIG6a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

[0036] FIG6b is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

[0037] FIG7a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0038] FIG7 b is a schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0040] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0041] The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low-power consumption signal.

[0042] In the above embodiment, the terminal sends the first information to the network device to report the frequency domain information that the terminal can support when monitoring the low-power signal, so that the network device can know the capabilities of the terminal and perform reasonable control or configuration operations based on the relevant capabilities of the terminal.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the frequency domain information includes: one or more frequency domain units.

[0044] In the above embodiment, the terminal can report the frequency domain units that it can support when monitoring low-power signals, so that the network device can reasonably configure the resources of the low-power signal according to the frequency domain units supported by the terminal.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the one or more frequency domain units include at least one group of frequency domain unit combinations.

[0046] In the above embodiment, the terminal may report the frequency domain unit combination that can be supported when monitoring the low power consumption signal, so that the network device can reasonably send the low power consumption signal on the frequency domain unit of the frequency domain unit combination.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0048] The terminal sends second information to the network device, where the second information is used to indicate whether the terminal supports simultaneously monitoring the low-power consumption signal on different frequency domain units.

[0049] In the above embodiment, the terminal can send second information to the network device to report whether it supports simultaneous monitoring of low-power signals on different frequency domain units, so that the network device can send low-power signals in different frequency domain units in an appropriate manner according to the terminal's capabilities.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0051] The terminal supports simultaneously monitoring the low-power signal on different frequency domain units, and the terminal monitors the first low-power signal on the first frequency domain unit and monitors the second low-power signal on the second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

[0052] In the above embodiment, when the terminal supports monitoring low-power signals on different frequency domain units simultaneously, the terminal can monitor different low-power signals on different frequency domain units simultaneously to improve communication and wake-up efficiency.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

[0054] With reference to some embodiments of the first aspect, in some embodiments, the frequency domain information includes: a switching delay of the terminal when switching between different frequency domain units.

[0055] In the above embodiment, the terminal may also report the switching delay between different frequency domain units, so that the network device may send the low power consumption signal on different frequency domain units according to the switching delay.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the frequency domain information includes: the bandwidth size of the frequency domain unit that the terminal supports monitoring the low-power signal, and / or the number of frequency domain units that support simultaneous monitoring of the low-power signal.

[0057] In the above embodiment, the terminal may also report the supported bandwidth size and / or the number of frequency domain units, so that the network device may reasonably configure the frequency domain resources of the low power signal according to the partial frequency domain information.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency domain unit is at least one of the following:

[0059] frequency band;

[0060] carrier wave;

[0061] The portion of bandwidth within a carrier.

[0062] In the above embodiment, the frequency domain units reported by the terminal may include different situations, so that the terminal reports different frequency domain units that support monitoring low-power signals, facilitating reasonable configuration of network equipment according to different frequency domain units.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0064] The terminal receives third information sent by the network device, where the third information is used to indicate the frequency domain resources configured for the low-power consumption signal.

[0065] In the above embodiment, the terminal can receive the third information sent by the network device to obtain the frequency domain resources of the low power consumption signal configured by the network device, so that the terminal can monitor the low power consumption signal on the appropriate frequency domain resources.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: the frequency domain information supported by the terminal does not include the frequency domain resources, and the terminal does not monitor the low power consumption signal.

[0067] In the above embodiment, when the configuration resources of the network device are not compatible with the information supported by the terminal, the terminal may choose not to monitor the corresponding low-power consumption signal to further save energy consumption.

[0068] In a second aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0069] The network device receives first information sent by the terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low-power consumption signal.

[0070] In the above embodiment, the network device receives the first information sent by the terminal and obtains the frequency domain information that the terminal can support when monitoring the low-power signal, so that the network device can perform reasonable control or configuration operations according to the relevant capabilities of the terminal.

[0071] In combination with some embodiments of the second aspect, in some embodiments, the frequency domain information includes: one or more frequency domain units.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the one or more frequency domain units include at least one group of frequency domain unit combinations.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0074] The network device receives second information sent by the terminal, where the second information is used to indicate whether the terminal supports simultaneously monitoring the low-power consumption signal on different frequency domain units.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0076] The terminal supports simultaneously monitoring the low-power signal on different frequency domain units, and the network device sends a first low-power signal on a first frequency domain unit and simultaneously sends a second low-power signal on a second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

[0077] In combination with some embodiments of the second aspect, in some embodiments, the first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the frequency domain information includes: a switching delay of the terminal switching between different frequency domain units.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the frequency domain information includes: the bandwidth size of the frequency domain unit that the terminal supports monitoring the low-power signal, and / or the number of frequency domain units that support simultaneous monitoring of the low-power signal.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the frequency domain unit is at least one of the following:

[0081] frequency band;

[0082] carrier wave;

[0083] The portion of bandwidth within a carrier.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0085] The network device sends third information to the terminal, where the third information is used to indicate the frequency domain resources configured for the low-power consumption signal.

[0086] In a third aspect, an embodiment of the present disclosure provides a communication method, including:

[0087] The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of the low-power signal;

[0088] The network device receives the first information.

[0089] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0090] The transceiver module is used to send first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power consumption signals.

[0091] In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

[0092] The transceiver module is used to receive first information sent by a terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power consumption signals.

[0093] In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

[0094] one or more processors;

[0095] The terminal is used to execute the communication method described in the first aspect.

[0096] In a seventh aspect, an embodiment of the present disclosure provides a network device, including:

[0097] one or more processors;

[0098] Wherein, the network device is used to execute the communication method described in the second aspect.

[0099] In an eighth aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0100] The terminal is configured to implement the communication method according to the first aspect;

[0101] The network device is configured to implement the communication method described in the second aspect.

[0102] In a ninth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0103] When the instruction is executed on a communication device, the communication device is caused to execute the method as described in any one of the first aspect or the second aspect.

[0104] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0105] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0106] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0107] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in 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.

[0108] The present disclosure provides a communication method, a terminal, a network device, a system, and a medium.

[0109] In some embodiments, terms such as communication method, information processing method, communication processing method, etc. can be replaced with each other, terms such as communication device, information processing device, communication processing device, etc. can be replaced with each other, and terms such as information processing system, communication system, etc. can be replaced with each other.

[0110] 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.

[0111] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, 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.

[0112] 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.

[0113] 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 using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

[0115] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0116] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to 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 above is also applicable when there are more branches such as A, B, and C.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

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

[0122] 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.

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

[0124] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

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

[0126] 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.

[0127] 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.

[0128] 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.

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

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

[0131] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

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

[0133] As shown in FIG. 1 , a communication system 100 includes a terminal 101 and a network device 102 .

[0134] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, 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.

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

[0136] In some embodiments, the access network device is, 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 base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0137] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access 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.

[0138] 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 access 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.

[0139] In some embodiments, a core network device may be a single device comprising one or more network elements, or may be a plurality of devices or a group of devices, each comprising all or part of one or more network elements. A network element 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), and a Next Generation Core (NGC).

[0140] 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.

[0141] 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.

[0142] 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).

[0143] Figure 2a is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2a, the embodiment of the present disclosure relates to a communication method, the method comprising:

[0144] Step S2101 , the terminal 101 sends first information to the network device 102 .

[0145] In some embodiments, the first information is used to indicate that the terminal 101 supports monitoring frequency domain information of the low power consumption signal.

[0146] Optionally, the low power consumption signal includes a low power consumption wake-up signal (Lower Power Wake Up Signal, LP WUS) for a low power consumption receiver, a synchronization signal, etc.

[0147] Optionally, the LP WUS may be further divided into a public LP WUS and a terminal-specific LP WUS.

[0148] It should be understood that some terminals support monitoring low-power signals, while some terminals do not support monitoring low-power signals, and for terminals that support monitoring low-power signals, the terminal may only be able to monitor low-power signals within a specific frequency domain. Thus, the terminal can inform the network device of the frequency domain information (such as the frequency band) that supports monitoring low-power signals, so that the network device can determine the capabilities of the terminal and perform targeted configuration. For example, after obtaining the frequency band information of the low-power signals that the terminal supports monitoring, the network device can schedule and configure the terminal on the frequency band that the terminal supports monitoring.

[0149] In some embodiments, the first information may be indication information or capability information, such as the first information is first capability information.

[0150] Optionally, the terminal 101 uses hardware responsible for monitoring low power signals, such as LP WUR, to monitor low power signals, so that the first information may indicate frequency domain information that the LP WUR supports monitoring low power signals. The low power signal is, for example, LP WUS.

[0151] Optionally, the terminal 101 may include hardware responsible for communication system channels such as NR channels and hardware responsible for monitoring low-power signals, wherein the hardware responsible for NR channels includes, for example, a main transceiver, and the hardware responsible for monitoring low-power signals includes, for example, LP WUR.

[0152] Optionally, the hardware responsible for the NR channel and the hardware responsible for monitoring the low-power signal can be set separately, or they can share components. For example, the main transceiver and the LP WUR are set separately, or the LP WUR reuses some components or functions of the main transceiver.

[0153] Optionally, to ensure the low cost of LP WUR, the LP WUR supports relatively simple functions, such as supporting a simple reception detection algorithm and a very small amount of storage capacity. In addition, due to the frequency characteristics of the hardware itself, the LP WUR may only have the function of monitoring the LP WUS on a few frequency bands and the ability to monitor other signals used by the LP WUR.

[0154] Optionally, the hardware responsible for the NR channel and the hardware responsible for monitoring the LP WUR may have different functions. For example, the main transceiver and the LP WUR may support different frequency bands for signal transmission and reception. Another example is that the main transceiver supports more frequency bands for signal transmission and reception, while the LP WUR only supports signal transmission and reception on some of these bands.

[0155] In some embodiments, the network device 102 may support sending low power consumption signals on multiple frequency bands. The LP WUR of a terminal 101 may not support monitoring low power consumption signals on all frequency bands supported by the network device 102, but may support monitoring low power consumption signals on a few frequency bands.

[0156] In some embodiments, the terminal 101 may be in a radio resource control (RRC) connected state.

[0157] In some embodiments, network device 102 receives first information.

[0158] Optionally, the terminal 101 in the connected state reports the first information to the network device 102 so that the network device 102 knows whether the terminal supports monitoring low-power signals on the frequency band to be configured for monitoring low-power signals, or the network device 102 can adaptively adjust the frequency band for sending low-power signals for different terminals 101.

[0159] In some embodiments, the frequency domain information includes: one or more frequency domain units, where one or more may be two or more.

[0160] Optionally, the frequency domain unit is at least one of the following:

[0161] frequency band;

[0162] carrier wave;

[0163] The portion of bandwidth within a carrier.

[0164] In one example, the terminal 101 may report one or more frequency bands that it supports for monitoring low-power signals. For example, the terminal 101 may report the supported frequency band index through the first information or other information to report the supported frequency bands for monitoring low-power signals.

[0165] In one example, the terminal 101 may report one or more carriers that it supports for monitoring low-power signals. Alternatively, the terminal 101 may report supported frequency bands and / or supported carriers on the frequency bands.

[0166] In one example, the terminal 101 may report a carrier on which it supports monitoring low-power signals and / or a portion of the bandwidth within the carrier.

[0167] In some embodiments, the frequency domain information further includes: the bandwidth of the frequency domain unit that the terminal supports monitoring low power consumption signals, and / or the number of frequency domain units that support simultaneous monitoring of low power consumption signals.

[0168] Optionally, the frequency domain unit may be at least one of a frequency band, a carrier, or a partial bandwidth within a carrier. For example, terminal 101 may report the index of the supported frequency band, such as band40, band41, etc., or the number of supported frequency bands. For another example, terminal 101 may report the bandwidth size of the supported carrier, such as 20 MHz, 50 MHz, or the number of supported carriers.

[0169] Optionally, when the terminal 101 supports multiple frequency bands, the bandwidths supported for monitoring low-power consumption signals on different frequency bands may be different.

[0170] Optionally, for the frequency band and / or carrier reported by the terminal 101, the terminal 101 may only support monitoring of low-power signals on part of the bandwidth of the frequency band and / or the carrier. Therefore, the frequency domain position and / or bandwidth size of the part of the bandwidth reported by the terminal 101 through the first information or other information can indicate the frequency domain position at which the terminal 101 can monitor the low-power signal.

[0171] In some embodiments, the one or more frequency domain units include at least one set of frequency domain unit combinations.

[0172] Optionally, the terminal 101 may report multiple frequency domain units in a manner of reporting a combination of frequency domain units.

[0173] Optionally, the frequency domain unit may be at least one of a frequency band, a carrier, and a partial bandwidth within a carrier.

[0174] Taking the frequency domain unit as a frequency band as an example, the frequency domain unit combination may be a band combination, that is, the terminal 101 reports the band combination that supports monitoring low-power signals. This reporting may be applicable to carrier aggregation or dual connectivity scenarios.

[0175] Optionally, when the terminal 101 needs to support reception of different low-power signals, it reports the supported frequency band combination.

[0176] In some examples, when terminal 101 reports a supported frequency domain unit combination, it implicitly indicates that terminal 101 supports simultaneous monitoring of low power consumption signals on different frequency domain units included in the frequency domain unit combination.

[0177] In other examples, when reporting the supported frequency domain unit combination, the terminal 101 indicates that the terminal 101 can monitor the low-power signal on the frequency domain unit corresponding to the frequency domain unit combination (simultaneous monitoring is not necessarily supported). The terminal 101 can report the same information or additional information of the reported frequency domain unit combination to indicate whether the terminal 101 supports simultaneous monitoring of low-power signals on different frequency domain units. For example, the terminal 101 can send the second information of the following embodiment.

[0178] Step S2102 , the terminal 101 sends second information to the network device 102 .

[0179] In some embodiments, the second information is used to indicate whether the terminal 101 supports simultaneously monitoring low-power signals on different frequency domain units.

[0180] For example, the terminal 101 reports through the second information whether it supports monitoring low-power signals on different frequency bands at the same time, or whether it supports monitoring low-power signals on different carriers in a certain frequency band at the same time.

[0181] Optionally, different frequency domain units may be frequency domain units in the same frequency domain unit combination. In this case, terminal 101 may report the frequency domain unit combination supported by itself in the first information. For example, the second information may be used to indicate whether terminal 101 supports simultaneous monitoring of low-power signals on two different frequency domain units in the frequency domain unit combination. A frequency domain unit is, for example, a frequency band, and a frequency domain unit combination is a frequency band combination.

[0182] Optionally, different frequency domain units may not belong to the same frequency domain unit combination. For example, the second information is used to indicate whether the terminal 101 supports simultaneous monitoring of low-power signals on different frequency bands or different carriers.

[0183] In some embodiments, when the terminal 101 reports the frequency domain unit combination, and the report implicitly indicates that the terminal 101 supports simultaneous monitoring of low power consumption signals on different frequency domain units included in the frequency domain unit combination, step S2102 can be omitted.

[0184] In some embodiments, the second information may be indication information or capability information, for example, the second information is second capability information.

[0185] In some embodiments, the second information and the first information may be sent using the same capability information, or may be sent using different capability information. For example, the first information and the second information may be sent simultaneously using the same capability information, or may be sent first and then the second information using different capability information, or may be sent first and then the first information using different capability information.

[0186] In some embodiments, the network device 102 receives the second information to learn whether the terminal 101 supports the capability of simultaneously monitoring low-power signals in different frequency domain units, such as in different frequency bands.

[0187] In some embodiments, the frequency domain information reported by the terminal 101 through the first information may further include: a switching delay of the terminal 101 switching between different frequency domain units.

[0188] Optionally, the different frequency domain units may belong to or not belong to the same frequency domain unit combination.

[0189] Optionally, in a scenario where the terminal 101 sends a switching delay, the terminal 101 may be implicitly instructed to support monitoring of low power consumption signals on multiple frequency domain units, that is, the frequency domain information may include multiple frequency domain units.

[0190] Optionally, when the terminal 101 does not support monitoring low-power signals on different frequency domain units at the same time, the terminal 101 may report the switching delay through the first information or other information.

[0191] Optionally, the terminal 101 may report at least one of the following: a switching delay between different frequency bands, a switching delay between different carriers, and a switching delay between different partial bandwidths.

[0192] Step S2103 , the network device 102 sends third information to the terminal 101 .

[0193] In some embodiments, the third information is used to indicate the frequency domain resources configured for the low power consumption signal.

[0194] Optionally, the third information may be configuration information or instruction information.

[0195] Optionally, the frequency domain resources include frequency information for sending low-power consumption signals, such as a frequency band or a carrier.

[0196] In some embodiments, the third information may also configure time domain resources of the LP WUS, etc.

[0197] In some embodiments, the network device 102 may determine the third information based on the information reported by the terminal 101 , that is, configure a low power consumption signal based on the report of the terminal 101 .

[0198] In some embodiments, the terminal 101 receives the third information and obtains the time-frequency resources or time-frequency position for sending the low-power signal.

[0199] In some embodiments, the third information may be sent after receiving the first information and / or second information sent by the terminal 101. In this case, the third information may be determined by the network device 102 based on the first information and / or the second information.

[0200] In some embodiments, the third information may be sent directly by the network device 102 according to the configuration. In this case, step S2103 may be executed before step S2101 and / or S2102, or the third information may be sent simultaneously with the first information and / or the second information. In this embodiment, the third information may be irrelevant to the capabilities of the terminal 101, or the third information may not be determined based on the first information and / or the second information. In this embodiment, after receiving the third information, the terminal 101 may compare the frequency domain resources configured in combination with the third information with the frequency domain information supported by its own capabilities. When the supported frequency domain information does not include the configured frequency domain resources, the low-power signal corresponding to the third information is not monitored. This embodiment can refer to the relevant implementation method of Figure 2c and will not be repeated here.

[0201] In step S2104 , the network device 102 sends a first low power consumption signal on the first frequency domain unit, and simultaneously sends a second low power consumption signal on the second frequency domain unit.

[0202] Optionally, the frequency domain units for sending the two low power consumption signals by the network device 102 may be consistent with the configuration in the third information, that is, the network device 102 informs the terminal 101 of the relevant frequency domain resources or frequency domain positions for sending LP WUS through the third information.

[0203] In some embodiments, the first frequency domain unit and the second frequency domain unit are different, that is, they are different frequency domain units.

[0204] Optionally, the first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination. For example, the first frequency domain unit is a first frequency band, the second frequency domain unit is a second frequency band, and the first frequency band and the second frequency band constitute a frequency band combination.

[0205] In some embodiments, when the terminal 101 supports monitoring low-power signals on different frequency domain units simultaneously, the network device 102 sends a first low-power signal on a first frequency domain unit and simultaneously sends a second low-power signal on a second frequency domain unit.

[0206] Optionally, in combination with the description of the foregoing embodiments, the terminal 101 may implicitly indicate support for simultaneous monitoring of low-power signals on different frequency domain units by reporting a supported frequency domain unit combination, or directly indicate support for simultaneous monitoring of low-power signals on different frequency domain units by sending a second message.

[0207] In some embodiments, taking the low power consumption signal as LP WUS as an example, the first low power consumption signal is the first LP WUS, and the second low power consumption signal is the second LP WUS.

[0208] In some embodiments, the first LP WUS may be a public LP WUS. The public LP WUS may be an LP WUS sent by the network device 102 to all terminals within its coverage area. The second LP WUS may be a dedicated LP WUS. The dedicated LP WUS may be an LP WUS sent by the network device 102 to a specific terminal. Both LP WUSs can be used to wake up the corresponding terminal.

[0209] Optionally, the frequency domain units used by the network device 102 to send the first LP WUS and the second LP WUS may be different.

[0210] In step S2105 , the terminal 101 monitors a first low power consumption signal on a first frequency domain unit, and monitors a second low power consumption signal on a second frequency domain unit.

[0211] In some embodiments, when supporting simultaneous monitoring of low power consumption signals such as LP WUS on different frequency domain units, the terminal 101 monitors a first low power consumption signal such as a first LP WUS on a first frequency domain unit, and monitors a second low power consumption signal such as a second LP WUS on a second frequency domain unit.

[0212] In some embodiments, when the LP WUR of the terminal 101 monitors or receives any of the two LP WUSs and the LP WUS indicates wake-up, the terminal 101 may wake up the main transceiver to perform data transmission or processing operations. Otherwise, the terminal 101 may keep the main transceiver in a sleep state to achieve energy saving.

[0213] 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", and "field" can be used interchangeably.

[0214] 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.

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

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

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

[0218] 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.

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

[0220] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain 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, a certain A, any A, or first A, etc., but not limited to this.

[0221] 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.

[0222] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0223] The method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2105. For example, step S2101 may be implemented as an independent embodiment, steps S2101 and S2102 may be implemented as independent embodiments, steps S2101 and S2103 may be implemented as independent embodiments, and steps S2101 and S2104 may be implemented as independent embodiments, but are not limited thereto.

[0224] In some embodiments, steps S2101 and S2102 can be executed simultaneously or exchanged in order, for example, the terminal 101 sends the first information and the second information at the same time through the same capability information, or the terminal 101 sends information containing the first information and the second information at the same time, or the terminal 101 sends the first information first and then sends the second information.

[0225] In some embodiments, at least one of steps S2102 , S2103 , S2104 and S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0227] Figure 2b is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2b, the embodiment of the present disclosure relates to a communication method, the method comprising:

[0228] Step S2201: Terminal 101 sends first information to network device 102.

[0229] Optionally, optional implementations of step S2201 may refer to step S2101 in FIG2 a and other related parts in the embodiment involved in FIG2 a , which will not be described in detail here.

[0230] Step S2202 , the terminal 101 sends second information to the network device 102 .

[0231] Optionally, optional implementations of step S2202 can refer to step S2102 in FIG. 2 a and other related parts in the embodiment involved in FIG. 2 a , which will not be described in detail here.

[0232] Step S2203 , the network device 102 sends third information to the terminal 101 .

[0233] Optionally, optional implementations of step S2203 may refer to step S2103 in FIG2a and other related parts in the embodiment involved in FIG2a , which will not be described in detail here.

[0234] In step S2204 , the network device 102 sends a first low power consumption signal on the first frequency domain unit, and sends a second low power consumption signal on the second frequency domain unit after a switching delay.

[0235] Optionally, the first frequency domain unit, the second frequency domain unit, the first low power consumption signal and the optional implementation of the first low power consumption signal can be referred to step S2104 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0236] In some embodiments, the switching delay may be reported by the terminal 101 in the first information.

[0237] Optionally, the terminal 101 may report at least one of the following frequency domain information through the first information: supported frequency domain units or frequency domain unit combinations, bandwidth of the frequency domain units, number of frequency domain units, and switching delay of the terminal 101 switching between different frequency domain units. The frequency domain unit may be a frequency band, a carrier, or a portion of the bandwidth within a carrier.

[0238] Optionally, when the terminal 101 does not support monitoring low-power signals on different frequency domain units at the same time, it can support monitoring low-power signals of different frequency domain units in a time division multiplexing (TDM) manner through the reported switching delay indication, and can also use separate information to report whether it supports monitoring low-power signals of different frequency domain units in a TDM manner.

[0239] In some embodiments, when the terminal 101 does not support monitoring low-power signals on different frequency domain units at the same time, the network device 102 sends a first low-power signal such as a first LP WUS on a first frequency domain unit, and sends a second low-power signal such as a second LP WUS on a second frequency domain unit after a switching delay.

[0240] Optionally, the network device 102 can obtain the switching delay based on the received first information, so that when sending the above two LP WUS on different frequency domain units, it can control the time interval between sending the two LP WUS, ensuring that the LP WUR of the terminal 101 can be switched between the two frequency domain units in a timely manner.

[0241] In some embodiments, when the terminal 101 does not support simultaneous monitoring of low-power signals on different frequency domain units and does not support TDM, the network device 102 may configure the terminal 101 (e.g., a connected terminal) to monitor only dedicated low-power signals, such as dedicated LP WUS, in conflicting frequency domain units when configuring the low-power signal resources monitored by the terminal 101. For public low-power signals, such as public LP WUS, the network device 102 may notify through dedicated signaling or dedicated LP WUS.

[0242] Optionally, for connected terminals, it is necessary to monitor the public LP-WUS when the system broadcast changes and the public warning system (PWS) notifications occur. If a system broadcast change or PWS notification occurs, the network device 102 can send the changed system broadcast information or PWS information through RRC dedicated signaling. Or send the changed system broadcast information or PWS information through a dedicated LP-WUS.

[0243] Step S2205: The terminal 101 monitors the first low power consumption signal on the first frequency domain unit, and monitors the second low power consumption signal on the second frequency domain unit after the switching delay.

[0244] In some embodiments, the switching delay may be a switching delay between different frequency bands, or a switching delay between different carriers.

[0245] Optionally, within the switching delay range, terminal 101 may perform operations such as adjusting software and hardware parameters to switch the monitoring frequency. For example, after monitoring the first LP WUS on the first frequency domain unit, terminal 101 may adjust the monitoring frequency to the second frequency domain unit within the switching delay range to monitor the second LP WUS.

[0246] In one example, using a carrier as the frequency domain unit, terminal 101 may support operation on a single carrier at a given time. If the frequencies of the public LP WUS and dedicated LP WUS that terminal 101 needs to monitor cannot be covered by a single carrier bandwidth, terminal 101's LP WUS needs to perform frequency switching between the carrier where the public LP WUS is located and the carrier where the dedicated LP WUS is located. Terminal 101 may report the switching delay between different carriers via first information or other information. In this example, network device 102 may ensure that the time interval between sending the public LP WUS and the dedicated LP WUS is greater than or equal to the switching delay based on the switching delay.

[0247] The method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2205. For example, step S2201 may be implemented as an independent embodiment, steps S2201 and S2202 may be implemented as independent embodiments, steps S2201 and S2203 may be implemented as independent embodiments, and steps S2201 and S2204 may be implemented as independent embodiments, but are not limited thereto.

[0248] In some embodiments, steps S2201 and S2202 may be performed simultaneously.

[0249] In some embodiments, at least one of steps S2202, S2203, S2204 and S2205 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0251] Figure 2c is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2c, an embodiment of the present disclosure relates to a communication method, the method comprising:

[0252] Step S2301: Terminal 101 sends first information to network device 102.

[0253] Optionally, optional implementations of step S2301 may refer to step S2101 in FIG2 a and other related parts in the embodiment involved in FIG2 a , which will not be described in detail here.

[0254] Step S2302 , the terminal 101 sends second information to the network device 102 .

[0255] Optionally, optional implementations of step S2302 can refer to step S2102 in FIG. 2 a and other related parts in the embodiment involved in FIG. 2 a , which will not be described in detail here.

[0256] Step S2303 , the network device 102 sends third information to the terminal 101 .

[0257] Optionally, optional implementations of step S2303 may refer to step S2103 in FIG2a and other related parts in the embodiment involved in FIG2a , which will not be described in detail here.

[0258] Step S2304: Terminal 101 does not monitor the low power consumption signal.

[0259] In some embodiments, when the frequency domain information supported by the terminal 101 does not include frequency domain resources, the terminal 101 does not monitor the low power consumption signal such as LP WUS.

[0260] Optionally, the frequency domain resources configured by network device 102 via the third information may be a transmission frequency band or carrier for the LP WUS. In conjunction with the description of the preceding embodiment, the frequency domain information supported by terminal 101 may include a frequency band, carrier, or partial bandwidth within a carrier that supports monitoring of the LP WUS. After receiving the third information, terminal 101 may compare the information configured by network device 102 with its own support information. If the frequency band or carrier of the LP WUS in the third information is outside the frequency band or carrier supported by terminal 101, for example, if the configured frequency of the LP WUS is not within a frequency band supported by the UE, terminal 101 may not monitor the LP WUS.

[0261] The method involved in the embodiments of the present disclosure may include at least one of steps S2301 to S2304. For example, step S2301 may be implemented as an independent embodiment, steps S2301 and S2302 may be implemented as independent embodiments, steps S2301 and S2303 may be implemented as independent embodiments, and steps S2301, S2303, and S2304 may be implemented as independent embodiments, but are not limited thereto.

[0262] In some embodiments, steps S2301 and S2302 may be performed simultaneously.

[0263] In some embodiments, at least one of steps S2302, S2303, S2304 and S2305 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0265] FIG3a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3a , the present disclosure embodiment relates to a communication method, which is executed by terminal 101 and includes:

[0266] Step S3101, sending the first information.

[0267] Optionally, optional implementations of step S3101 may refer to step S2101 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0268] In some embodiments, the terminal 101 sends the first information to the network device 102, but is not limited thereto and the first information may also be sent to other entities.

[0269] Step S3102, sending the second information.

[0270] Optionally, optional implementations of step S3102 may refer to step S2102 in FIG. 2a and other related parts in the embodiments involved in FIG. 2a to FIG. 2c , which will not be described in detail here.

[0271] In some embodiments, the terminal 101 sends the second information to the network device 102, but is not limited thereto and the second information may also be sent to other entities.

[0272] Step S3103, obtain third information.

[0273] Optionally, optional implementations of step S3103 may refer to step S2103 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0274] In some embodiments, the terminal 101 obtains the third information from the network device 102, but is not limited thereto and the third information may also be obtained from other entities.

[0275] Step S3104: Determine whether to monitor the low power consumption signal according to the third information.

[0276] Optionally, optional implementations of step S3104 may refer to steps S2104 to S2105 in FIG2a and other related parts in the embodiment involved in FIG2a , which will not be described in detail here.

[0277] Optionally, optional implementations of step S3104 may refer to steps S2204 to S2205 in FIG2b and other related parts of the embodiment involved in FIG2b , which will not be described in detail here.

[0278] Optionally, optional implementations of step S3104 may refer to step S2304 in FIG2c and other related parts of the embodiment involved in FIG2c, which will not be described in detail here.

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

[0280] FIG3b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3b , the present disclosure embodiment relates to a communication method, which is executed by terminal 101 and includes:

[0281] Step S3201, sending the first information.

[0282] Optionally, optional implementations of step S3201 may refer to step S2101 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0283] Step S3202, obtain third information.

[0284] Optionally, optional implementations of step S3202 may refer to step S2103 in FIG. 2a and other related parts in the embodiments involved in FIG. 2a to FIG. 2c , which will not be described in detail here.

[0285] Step S3203: Determine whether to monitor the low power consumption signal according to the third information.

[0286] Optionally, optional implementations of step S3203 may refer to steps S2104 to S2105 in FIG2a and other related parts in the embodiment involved in FIG2a , which will not be described in detail here.

[0287] Optionally, optional implementations of step S3203 may refer to steps S2204 to S2205 in FIG2b and other related parts of the embodiment involved in FIG2b , which will not be described in detail here.

[0288] Optionally, optional implementations of step S3203 may refer to step S2304 in FIG2c and other related parts in the embodiment involved in FIG2c, which will not be described in detail here.

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

[0290] FIG3c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3c, the present disclosure embodiment relates to a communication method, which is executed by terminal 101 and includes:

[0291] Step S3301, sending the first information.

[0292] Optionally, optional implementations of step S3301 may refer to step S2101 in FIG. 2a and other related parts in the embodiments involved in FIG. 2a to FIG. 2c , which will not be described in detail here.

[0293] In some embodiments, the first information is used to indicate that the terminal supports monitoring frequency domain information of the low power consumption signal.

[0294] In some embodiments, the frequency domain information includes: one or more frequency domain units.

[0295] Optionally, the one or more frequency domain units include at least one group of frequency domain unit combinations.

[0296] In some embodiments, the method may further include: the terminal sending second information to the network device, wherein the second information is used to indicate whether the terminal supports simultaneous monitoring of low-power signals on different frequency domain units.

[0297] Optionally, when the terminal supports simultaneous monitoring of low-power signals on different frequency domain units, the method may further include: the terminal monitors a first low-power signal on a first frequency domain unit, and simultaneously monitors a second low-power signal on a second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

[0298] Optionally, the first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

[0299] In some embodiments, the frequency domain information includes: a switching delay of the terminal switching between different frequency domain units.

[0300] In some embodiments, the frequency domain information includes: the bandwidth of the frequency domain unit that the terminal supports monitoring low power consumption signals, and / or the number of frequency domain units that support simultaneous monitoring of low power consumption signals.

[0301] In some embodiments, the frequency domain unit is at least one of the following:

[0302] frequency band;

[0303] carrier wave;

[0304] The portion of bandwidth within a carrier.

[0305] In some embodiments, the method may further include: the terminal receiving third information sent by the network device, wherein the third information is used to indicate the frequency domain resources configured for the low-power signal.

[0306] In some embodiments, when the frequency domain information supported by the terminal does not include frequency domain resources, the terminal does not monitor the low power consumption signal.

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

[0308] FIG4a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4a , the present disclosure embodiment relates to a communication method, which is executed by a network device 102 and includes:

[0309] Step S4101, obtain first information.

[0310] Optionally, optional implementations of step S4101 may refer to step S2101 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0311] In some embodiments, the network device 102 may obtain the first information from the terminal 101, but is not limited thereto and may also obtain the first information from other entities.

[0312] Step S4102, obtaining second information.

[0313] Optionally, optional implementations of step S4102 may refer to step S2102 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0314] In some embodiments, the network device 102 may obtain the second information from the terminal 101, but is not limited thereto and may also obtain the second information from other entities.

[0315] Step S4103, sending the third information.

[0316] Optionally, optional implementations of step S4103 may refer to step S2103 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0317] In some embodiments, the network device 102 may send the third information to the terminal 101, but is not limited thereto and may also send the third information to other entities.

[0318] Step S4104: Send a low power consumption signal according to the third information.

[0319] Optionally, optional implementations of step S4104 may refer to steps S2104 to S2105 in FIG2a and other related parts of the embodiment involved in FIG2a , which will not be described in detail here.

[0320] Optionally, optional implementations of step S4104 may refer to steps S2204 to S2205 in FIG. 2 b and other related parts of the embodiment involved in FIG. 2 b , which will not be described in detail here.

[0321] Optionally, optional implementations of step S4104 may refer to step S2304 in FIG2c and other related parts of the embodiment involved in FIG2c, which will not be described in detail here.

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

[0323] FIG4 b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4 b , the present disclosure embodiment relates to a communication method, which is executed by the network device 102 and includes:

[0324] Step S4201, obtain first information.

[0325] Optionally, optional implementations of step S4201 may refer to step S2101 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0326] Step S4202, sending the third information.

[0327] Optionally, optional implementations of step S4202 may refer to step S2103 in FIG. 2a and other related parts in the embodiments involved in FIG. 2a to FIG. 2c , which will not be described in detail here.

[0328] Step S4203: Send a low power consumption signal according to the third information.

[0329] Optionally, optional implementations of step S4203 may refer to steps S2104 to S2105 in FIG2 a and other related parts in the embodiment involved in FIG2 a , which will not be described in detail here.

[0330] Optionally, optional implementations of step S4203 may refer to steps S2204 to S2205 in FIG2b and other related parts of the embodiment involved in FIG2b , which will not be described in detail here.

[0331] Optionally, optional implementations of step S4203 may refer to step S2304 in FIG2c and other related parts of the embodiment involved in FIG2c, which will not be described in detail here.

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

[0333] FIG4c is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4c, the present disclosure embodiment relates to a communication method, which is executed by the network device 102 and includes:

[0334] Step S4301, obtain first information.

[0335] Optionally, optional implementations of step S3301 may refer to step S2101 in FIG. 2a and other related parts in the embodiments involved in FIG. 2a to FIG. 2c , which will not be described in detail here.

[0336] In some embodiments, the first information is used to indicate that the terminal supports monitoring frequency domain information of the low power consumption signal.

[0337] In some embodiments, the frequency domain information includes: one or more frequency domain units.

[0338] Optionally, the one or more frequency domain units include at least one group of frequency domain unit combinations.

[0339] In some embodiments, the method may further include: the network device receiving second information sent by the terminal, wherein the second information is used to indicate whether the terminal supports simultaneous monitoring of low-power signals on different frequency domain units.

[0340] Optionally, when the terminal supports simultaneous monitoring of low-power signals on different frequency domain units, the method may further include: the network device sends a first low-power signal on a first frequency domain unit, and simultaneously sends a second low-power signal on a second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

[0341] Optionally, the first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

[0342] In some embodiments, the frequency domain information includes: a switching delay of the terminal switching between different frequency domain units.

[0343] In some embodiments, the frequency domain information includes: the bandwidth of the frequency domain unit that the terminal supports monitoring low power consumption signals, and / or the number of frequency domain units that support simultaneous monitoring of low power consumption signals.

[0344] In some embodiments, the frequency domain unit is at least one of the following:

[0345] frequency band;

[0346] carrier wave;

[0347] The portion of bandwidth within a carrier.

[0348] In some embodiments, the method may further include: the network device sending third information to the terminal, wherein the third information is used to indicate the frequency domain resources configured for the low-power signal.

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

[0350] Figure 5 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 5, the embodiment of the present disclosure relates to a communication method, which includes:

[0351] Step S5101: Terminal 101 sends first information to network device 102.

[0352] Optionally, optional implementations of step S5101 may refer to step S2101 in FIG. 2 a and other related parts in the embodiments involved in FIG. 2 a to FIG. 2 c , which will not be described in detail here.

[0353] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0354] The present disclosure provides a communication method in which a UE may report to a base station the bands supported for monitoring low power consumption signals such as LP WUS. In some embodiments, the method may include the following examples:

[0355] Example 1:

[0356] The UE reports to the base station the bands supported for monitoring low power signals such as LP WUS.

[0357] Optionally, there can be one or more supported bands.

[0358] Optionally, the example still holds true when band is replaced by carrier.

[0359] Example 2:

[0360] The UE may also report the supported LPWUS band combination.

[0361] For example, if the UE needs to support receiving common LPWUS+dedicated LPWUS, the UE reports the supported LPWUS frequency band combination.

[0362] Optionally, when reporting the frequency band combination, it may be indicated that the terminal supports simultaneous monitoring of LP WUS on this frequency band combination.

[0363] Optionally, if the reported frequency band combination cannot indicate that the terminal monitors the LP WUS simultaneously on this frequency band combination, the UE needs to report whether it can work simultaneously on the frequency band combination.

[0364] Optionally, the example still holds true when band is replaced by carrier.

[0365] Example 3:

[0366] The UE can report the delay required to switch between multiple bands.

[0367] For example, if a UE needs to monitor a public LPWUS and a dedicated LPWUS on two bands, and the UE does not support simultaneous operation on multiple bands, it needs to switch between the two bands to monitor the two LPWUS signals. The UE reports the delay of switching the bands, allowing the base station to control the time interval between the two LPWUS signals when sending the LPWUS on the two bands, ensuring that the UE's LPWUS can be switched between the two bands in a timely manner.

[0368] Optionally, Example 3 may be performed based on Example 1 or Example 2.

[0369] Optionally, the example still holds true when band is replaced by carrier.

[0370] Example 4:

[0371] The UE reports the supported LP WUS bandwidth size. If the UE supports multiple bands, the LP WUS bandwidth sizes supported on different bands may be different.

[0372] Optionally, the example still holds true when band is replaced by carrier.

[0373] Optionally, if the LP WUR supports a certain band, the bandwidth of the carrier supported on the band (eg, 20 MHz, 50 MHz) and the number of carriers that support simultaneous monitoring of the LP WUS may also be reported.

[0374] Optionally, the UE can also report the delay of switching between carriers. For example, it is possible that the UE only supports operation on one carrier at a time. If the frequencies of the public LP WUS and dedicated LP WUS to be received by the UE cannot be covered by one carrier bandwidth, in this case, the LP WUR needs to be switched between the carrier where the public LP WUS is located and the carrier where the dedicated LP WUS is located. The base station needs to know the delay of the UE's LP WUR switching to ensure that there is a time interval between the public LP WUS and the dedicated LP WUS that is greater than or equal to the switching delay.

[0375] Example 5:

[0376] The UE receives the LP WUS configuration information from the base station. If the frequency resource configured for the LP WUS is not on a band supported by the UE, the terminal will not monitor the LP WUS.

[0377] Optionally, the example still holds true when band is replaced by carrier.

[0378] Example 6:

[0379] If the UE does not support simultaneous reception on two carriers or bands, the UE can also report whether it supports TDM reception of LP-WUS signals on two bands. If not, the network side will only require monitoring of the dedicated LP-WUS when configuring, for example, for RRC_CONNECTED. For the public LP-WUS, the network side will use dedicated signaling or dedicated LP-WUS notification.

[0380] Optionally, for RRC_CONNECTED UEs, the only requirement for monitoring the public LP-WUS is system broadcast changes and PWS notifications. If a system broadcast change or PWS notification occurs, the network ensures that the changed system broadcast information or PWS information is sent via RRC dedicated signaling, or a dedicated LP-WUS notification change indication or notification indication is sent.

[0381] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0382] It should be understood that the division of the various units or modules in the above device 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 device, 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.

[0383] 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 (CPU), 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 an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), 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.

[0384] Figure 6a is a structural diagram of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 6a, the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the above-mentioned transceiver module 6101 is used to send a first information to a network device, and the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power signals. Optionally, the above-mentioned transceiver module 6101 is used to execute at least one of the communication steps such as sending and / or receiving executed by the terminal 101 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps executed by the terminal 101 in any of the above methods, which will not be repeated here.

[0385] Figure 6b is a schematic diagram of the structure of the network device proposed in an embodiment of the present disclosure. As shown in Figure 6b, the network device 6200 may include: at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the above-mentioned transceiver module 6201 is used to receive first information sent by the terminal, and the first information is used to indicate that the terminal supports monitoring frequency domain information of low-power signals. Optionally, the above-mentioned transceiver module 6201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the network device 102 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps performed by the network device 102 in any of the above methods, which will not be repeated here.

[0386] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0387] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

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

[0389] As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 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 the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0390] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 7101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0391] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Alternatively, all or part of the memories 7103 may be located outside the communication device 7100. In alternative embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memory 7102 and may be configured to receive data from the memory 7102 or other devices, or to send data to the memory 7102 or other devices. For example, the interface circuits 7104 may read data stored in the memory 7102 and send the data to the processor 7101.

[0392] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. 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 or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, 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) others, etc.

[0393] FIG7 b is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 7200 shown in FIG7 b , but the present disclosure is not limited thereto.

[0394] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0395] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Alternatively, all or part of memory 7203 may be located external to chip 7200. Optionally, interface circuit 7202 is connected to memory 7203 and may be used to receive data from memory 7203 or other devices, or may be used to send data to memory 7203 or other devices. For example, interface circuit 7202 may read data stored in memory 7203 and send the data to processor 7201.

[0396] In some embodiments, the interface circuit 7202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 7202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 7202 performs data exchange between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps.

[0397] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0398] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

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

[0400] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods. Industrial Applicability

[0401] In the method disclosed herein, the terminal sends first information to the network device to report the frequency domain information that the terminal can support when monitoring low-power signals, thereby facilitating the network device to learn the capabilities of the terminal and perform reasonable control or configuration operations based on the relevant capabilities of the terminal.

Claims

1. A communication method, the method comprising: The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low power consumption signal.

2. The method of claim 1, wherein: The frequency domain information includes: one or more frequency domain units.

3. The method of claim 2, wherein: The one or more frequency domain units include at least one group of frequency domain unit combinations.

4. The method according to claim 2 or 3, wherein: The method further comprises: The terminal sends second information to the network device, where the second information is used to indicate whether the terminal supports simultaneously monitoring the low power consumption signal on different frequency domain units.

5. The method of claim 4, wherein: The method further comprises: The terminal supports simultaneously monitoring the low power consumption signal on different frequency domain units, the terminal monitors a first low power consumption signal on a first frequency domain unit, and simultaneously monitors a second low power consumption signal on a second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

6. The method of claim 5, wherein: The first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

7. The method according to any one of claims 2 to 4, wherein: The frequency domain information includes: a switching delay of the terminal when switching between different frequency domain units.

8. The method according to any one of claims 2 to 7, wherein: The frequency domain information includes: the bandwidth size of the frequency domain unit that the terminal supports monitoring the low power consumption signal, and / or the number of frequency domain units that support simultaneous monitoring of the low power consumption signal.

9. The method according to any one of claims 2 to 8, wherein: The frequency domain unit is at least one of the following: frequency band; Carrier; The portion of bandwidth within a carrier.

10. The method according to any one of claims 1 to 9, wherein: The method further comprises: The terminal receives third information sent by the network device, where the third information is used to indicate the frequency domain resources configured for the low power consumption signal.

11. The method of claim 10, wherein: The method further comprises: The frequency domain information supported by the terminal does not include the frequency domain resources, and the terminal does not monitor the low power consumption signal.

12. A communication method, the method comprising: The network device receives first information sent by a terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of a low power consumption signal.

13. The method of claim 12, wherein: The frequency domain information includes: one or more frequency domain units.

14. The method of claim 13, wherein: The one or more frequency domain units include at least one group of frequency domain unit combinations.

15. The method according to claim 13 or 14, wherein: The method further comprises: The network device receives second information sent by the terminal, where the second information is used to indicate whether the terminal supports simultaneously monitoring the low power consumption signal on different frequency domain units.

16. The method of claim 15, wherein: The method further comprises: The terminal supports simultaneously monitoring the low-power consumption signal on different frequency domain units, and the network device sends a first low-power consumption signal on a first frequency domain unit and simultaneously sends a second low-power consumption signal on a second frequency domain unit; wherein the first frequency domain unit is different from the second frequency domain unit.

17. The method of claim 16, wherein: The first frequency domain unit and the second frequency domain unit belong to the same frequency domain unit combination.

18. The method according to any one of claims 13 to 15, wherein: The frequency domain information includes: a switching delay of the terminal when switching between different frequency domain units.

19. The method according to any one of claims 13 to 18, wherein: The frequency domain information includes: the bandwidth size of the frequency domain unit that the terminal supports monitoring the low power consumption signal, and / or the number of frequency domain units that support simultaneous monitoring of the low power consumption signal.

20. The method according to any one of claims 13 to 19, wherein: The frequency domain unit is at least one of the following: frequency band; Carrier; The portion of bandwidth within a carrier.

21. The method according to any one of claims 12 to 20, wherein: The method further comprises: The network device sends third information to the terminal, where the third information is used to indicate the frequency domain resources configured for the low power consumption signal.

22. A communication method, comprising: The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of the low power consumption signal; The network device receives the first information.

23. A terminal, comprising: The transceiver module is used to send first information to the network device, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low power consumption signals.

24. A network device comprising: The transceiver module is used to receive first information sent by a terminal, where the first information is used to indicate that the terminal supports monitoring frequency domain information of low power consumption signals.

25. A terminal, comprising: one or more processors; The terminal is used to execute the communication method according to any one of claims 1 to 11.

26. A network device comprising: one or more processors; Wherein, the network device is used to execute the communication method described in any one of claims 12-21.

27. A communication system, comprising a terminal and a network device, wherein: The terminal is configured to implement the communication method according to any one of claims 1 to 11; The network device is configured to implement the communication method according to any one of claims 12 to 21.

28. A storage medium storing instructions, wherein: When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 11 or any one of claims 12 to 21.

Images