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

Abstract

The present disclosure relates to communication methods, terminals, network devices, a system and a storage medium. A method comprises: receiving a low-power-consumption signal in a first signal format, which signal is sent by a network device. In the method of the present disclosure, a terminal can receive a low-power-consumption signal transmitted on the basis of a certain signal format, so that the terminal can effectively receive the low-power-consumption signal in a timely manner on the basis of energy saving, so as to be suitable for transmission requirements of different scenarios, thereby improving the efficiency of necessary communication.

Description

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

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

[0002] The terminal can put the main radio (MR) into sleep or ultra-deep sleep state and use the low-power wake-up receiver (LP WUR) to listen to low-power signals, thereby reducing the power consumption of the MR and saving power for the terminal.

[0003] Summary of the Invention

[0004] The transmission form or method of the low-power signal needs to be determined.

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

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

[0007] A low power consumption signal in a first signal format sent by a network device is received.

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

[0009] A low power consumption signal in a first signal format is sent to the terminal.

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

[0011] The transceiver module is used to receive a low-power consumption signal in a first signal format sent by a network device.

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

[0013] The transceiver module is used to send a low-power consumption signal in a first signal format to the terminal.

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

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

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

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

[0018] one or more processors;

[0019] The terminal is configured to implement the 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 configured to implement the method described in the second aspect.

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

[0024] When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0025] In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

[0026] When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0027] In the embodiment of the present disclosure, the terminal can receive low-power signals transmitted based on a certain signal format, so that on the basis of energy saving, the terminal can receive low-power signals in a timely and effective manner to adapt to the transmission requirements of different scenarios and improve the efficiency of necessary communications. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0030] FIG2a and FIG2b are exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure;

[0031] 2c to 2e are time domain schematic diagrams of low power consumption signals provided according to an embodiment of the present disclosure;

[0032] 3a to 3b are exemplary flowcharts of a method according to an embodiment of the present disclosure;

[0033] 4a and 4b are exemplary flowcharts of a method according to an embodiment of the present disclosure;

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

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

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

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

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

[0039] In a first aspect, an embodiment of the present disclosure provides a communication method, performed by a terminal, the method comprising:

[0040] A low power consumption signal in a first signal format sent by a network device is received.

[0041] In the above embodiment, the terminal can receive low-power signals transmitted based on a certain signal format, so that on the basis of energy saving, the terminal can receive low-power signals in a timely and effective manner to adapt to the transmission requirements of different scenarios and improve the efficiency of necessary communications.

[0042] In combination with the embodiments of the first aspect, in some embodiments, the first signal format is determined according to a signal format defined by a protocol or a signal format configured by the network device.

[0043] In conjunction with the embodiments of the first aspect, in some embodiments, the signal format includes at least one of the following:

[0044] Modulation method;

[0045] Preamble information;

[0046] Frequency domain information;

[0047] Cyclic Redundancy Check (CRC) information.

[0048] In the above embodiment, one or more signal formats of the low-power signal can be defined by the protocol or configured by the network, so that the terminal can obtain the content of the low-power signal based on the signal format of the low-power signal transmitted by the network device to ensure communication accuracy.

[0049] In combination with the embodiments of the first aspect, in some embodiments, the modulation method used by the low-power signal is a binary on-off keying (OOK) modulation method, wherein at least one OOK symbol corresponding to the modulation of the low-power signal is carried on an orthogonal frequency division multiplexing (OFDM) time domain symbol.

[0050] In the above embodiment, the low-power consumption signal may be modulated using the OOK modulation method, so that the terminal may determine the content of the modulated signal in a corresponding manner.

[0051] In combination with the embodiments of the first aspect, in some embodiments, the number of OOK symbols carried by an OFDM time domain symbol is defined by a protocol; or, the number of OOK symbols carried by an OFDM time domain symbol is determined based on configuration information.

[0052] In the above embodiment, the correspondence between OFDM time domain symbols and OOK symbols may include multiple possibilities. Through protocol definition or network configuration, the terminal can obtain the specific modulation information used by the network device, which facilitates accurate reception and processing of low-power signals.

[0053] In combination with the embodiments of the first aspect, in some embodiments, the configuration information is sent through system information (SI), and the terminal is in a radio resource control (RRC) idle state or an RRC inactive state; or, the configuration information is sent through RRC signaling, and the terminal is in an RRC connected state.

[0054] In the above embodiment, based on different states of the terminal, the network device may send configuration information through different signaling, so that the terminal can accurately obtain modulation-related information.

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

[0056] The capability information is sent to the network device, where the capability information is used to indicate the number of OOK symbols supported by the terminal in one OFDM time domain symbol, wherein the terminal is in an RRC connected state.

[0057] In the above embodiment, a terminal in a connected state can report the number of OOK symbols it supports by sending capability information, so that the network device can be reasonably configured based on the terminal capabilities.

[0058] In combination with the embodiments of the first aspect, in some embodiments, the terminal supports carrying a default number of OOK symbols in one OFDM time-domain symbol.

[0059] In the above embodiment, when the terminal does not report capability information, the network device can be reasonably configured using the default number.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the preamble information includes at least one of the following:

[0061] Whether the low-power signal contains a preamble;

[0062] The symbol length occupied by the preamble;

[0063] Modulation method of the preamble;

[0064] OFDM time domain sequence or frequency domain sequence of the preamble;

[0065] Whether the preamble corresponds to a fixed time-domain pattern.

[0066] In the above embodiment, based on the preamble information corresponding to one or more low-power consumption signals, the terminal can accurately receive and process the low-power consumption signals.

[0067] In combination with the embodiments of the first aspect, in some embodiments, the modulation mode of the preamble code is an OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in an OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in an OFDM time domain symbol.

[0068] In the above embodiment, the modulation mode of the preamble code and the modulation mode of the low-power signal may be the same, but the number of OOK symbols carried in one OFDM symbol is different.

[0069] In conjunction with the embodiments of the first aspect, in some embodiments, the frequency domain information includes at least one of the following:

[0070] Subcarrier spacing (SCS) corresponding to low-power signals;

[0071] The frequency domain unit where the low-power signal is located.

[0072] In the above embodiment, the terminal can receive the low power consumption signal based on a suitable frequency domain position through the frequency domain information of the low power consumption signal.

[0073] In the above embodiment, the frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or

[0074] The frequency domain unit is a frequency band, a carrier or an active bandwidth part (active BandWidth Part, active BWP), and the terminal is in an RRC connected state.

[0075] In the above embodiment, the terminal can determine the frequency domain unit where the low power consumption signal is located based on its own state, and receive the low power consumption signal at the corresponding frequency domain position.

[0076] In conjunction with the embodiments of the first aspect, in some embodiments, the SCS corresponding to the low-power signal is the same as the SCS of at least one of the following:

[0077] Synchronization Signal Block (SSB);

[0078] Type 0 Common Search Space (CSS);

[0079] Activation BWP of the serving cell.

[0080] In the above embodiment, the terminal can determine the SCS of the low-power signal based on the relevant NR channel or signal, so as to accurately receive and process the low-power signal.

[0081] In conjunction with the embodiments of the first aspect, in some embodiments, the frequency domain unit where the low power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located:

[0082] SSB;

[0083] Type 0CSS;

[0084] Activation BWP of the serving cell.

[0085] In the above embodiment, the terminal can determine the frequency domain unit where the low-power signal is located based on the relevant NR channel or signal, so as to accurately receive and process the low-power signal.

[0086] In conjunction with the embodiments of the first aspect, in some embodiments, the CRC information includes:

[0087] Whether the low-power signal carries CRC;

[0088] The number of bits occupied by CRC.

[0089] In the above embodiment, the terminal can effectively process the received low-power signal based on the CRC information of the low-power signal to accurately obtain the content of the signal.

[0090] In conjunction with the embodiments of the first aspect, in some embodiments, the low power consumption signal is:

[0091] Low Power Wake Up signal (LP WUS), the terminal is in RRC connected state, RRC idle state or RRC inactive state; or,

[0092] Low Power Synchronization Signal (LP SS): The terminal is in the RRC idle state or the RRC inactive state.

[0093] In the above embodiment, the terminal can accurately receive the LP WUS or LP SS based on the signal format of the LP WUS or LP SS, so as to perform reasonable operations, such as waking up the MR in time for communication according to the LP WUS or performing synchronization according to the LP SS.

[0094] In a second aspect, an embodiment of the present disclosure provides a communication method, performed by a network device, the method comprising:

[0095] A low power consumption signal in a first signal format is sent to the terminal.

[0096] In combination with the embodiments of the second aspect, in some embodiments, the first signal format is determined according to a signal format defined by a protocol or a signal format configured by the network device.

[0097] In conjunction with the embodiments of the second aspect, in some embodiments, the signal format includes at least one of the following:

[0098] Modulation method;

[0099] Preamble information;

[0100] Frequency domain information;

[0101] CRC information.

[0102] In combination with the embodiments of the second aspect, in some embodiments, the modulation method used by the low-power signal is an OOK modulation method, wherein at least one OOK symbol corresponding to the modulation of the low-power signal is carried on an OFDM time domain symbol.

[0103] In combination with the embodiments of the second aspect, in some embodiments, the number of OOK symbols carried by an OFDM time domain symbol is defined by a protocol; or, the number of OOK symbols carried by an OFDM time domain symbol is determined based on configuration information.

[0104] In combination with the embodiments of the second aspect, in some embodiments, the configuration information is sent through system information, and the terminal is in a radio resource control RRC idle state or an RRC inactive state; or, the configuration information is sent through RRC signaling, and the terminal is in an RRC connected state.

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

[0106] The capability information sent by the receiving terminal is used to indicate the number of OOK symbols supported by the terminal in one OFDM time domain symbol, wherein the terminal is in an RRC connected state.

[0107] In combination with the embodiments of the second aspect, in some embodiments, the number of OOK symbols carried in an OFDM time domain symbol is a default number.

[0108] In conjunction with the embodiments of the second aspect, in some embodiments, the preamble information includes at least one of the following:

[0109] Whether the low-power signal contains a preamble;

[0110] The symbol length occupied by the preamble;

[0111] Modulation method of the preamble;

[0112] OFDM time domain sequence or frequency domain sequence of the preamble;

[0113] Whether the preamble corresponds to a fixed time domain pattern.

[0114] In combination with the embodiments of the second aspect, in some embodiments, the modulation mode of the preamble code is an OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in an OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in an OFDM time domain symbol.

[0115] In conjunction with the embodiments of the second aspect, in some embodiments, the frequency domain information includes at least one of the following:

[0116] SCS corresponding to low-power signals;

[0117] The frequency domain unit where the low-power signal is located.

[0118] In combination with the embodiment of the second aspect, in some embodiments, the frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or

[0119] The frequency domain unit is a frequency band, a carrier or an activated bandwidth part BWP, and the terminal is in an RRC connected state.

[0120] In conjunction with the embodiments of the second aspect, in some embodiments, the SCS corresponding to the low-power signal is the same as the SCS of at least one of the following:

[0121] SSB;

[0122] Type 0CSS;

[0123] Activation BWP of the serving cell.

[0124] In conjunction with the embodiments of the second aspect, in some embodiments, the frequency domain unit where the low power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located:

[0125] SSB;

[0126] Type 0CSS;

[0127] Activation BWP of the serving cell.

[0128] In conjunction with the embodiment of the second aspect, in some embodiments, the CRC information includes:

[0129] Whether the low-power signal carries CRC;

[0130] The number of bits occupied by CRC.

[0131] In conjunction with the embodiments of the second aspect, in some embodiments, the low power consumption signal is:

[0132] Low power wake-up signal LP WUS, the terminal is in RRC connected state, RRC idle state or RRC inactive state; or,

[0133] Low power synchronization signal LP SS, the terminal is in RRC idle state or RRC inactive state.

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

[0135] The transceiver module is used to receive a low-power consumption signal in a first signal format sent by a network device.

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

[0137] The transceiver module is used to send a low-power consumption signal in a first signal format to the terminal.

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

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

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

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

[0142] one or more processors;

[0143] The terminal is configured to implement the method described in the first aspect.

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

[0145] one or more processors;

[0146] Wherein, the network device is configured to implement the method described in the second aspect.

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

[0148] When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0149] In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

[0150] When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0151] In a tenth 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.

[0152] In an eleventh 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0169] In some embodiments, "terminal" or "terminal device" may be referred to as "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.

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

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

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

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

[0174] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

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

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

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

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

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

[0180] In some embodiments, the core network device can be a device including one or more network elements, or it can be multiple devices or device groups, each including all or part of one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC). Alternatively, the core network device refers to a network element with a specific function, such as the Access Management Function (AMF), the Service Management Function (SMF), etc.

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

[0182] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1 , or a part of the main body thereof, but are not limited thereto.

[0183] The entities shown in Figure 1 are examples. The communication system may include all or part of the entities in Figure 1, and may also include other entities outside of Figure 1. The number and form of the entities are arbitrary. The connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

[0184] 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 processing methods, and next-generation systems based on and extending these. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0185] In the embodiment of the present disclosure, the terminal 101 can monitor the low power consumption signal through the LP WUR. However, in order to adapt to the transmission requirements of different scenarios, it is necessary to provide a method for determining or how to determine the format of the low power consumption signal.

[0186] 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:

[0187] Step S2101 : The network device 102 sends a low power consumption signal to the terminal 101 .

[0188] In some embodiments, the low power consumption signal is LP WUS or LP SS.

[0189] For example, the low power consumption signal is LP WUS, and the terminal is in the RRC connected state, RRC idle state, or RRC inactive state; or, the low power consumption signal is LP SS, and the terminal is in the RRC idle state or RRC inactive state.

[0190] Optionally, the terminal 101 may monitor the low power consumption signal through the LP WUR and may perform corresponding operations after receiving the low power consumption signal.

[0191] In one example, when the LP WUR of terminal 101 detects an LP WUS targeting it, it can activate the MR and conduct normal communication transmission. Otherwise, terminal 101 can maintain the MR in sleep or deep sleep mode, significantly reducing MR power consumption. Furthermore, the LP WUR consumes very little power, resulting in even greater power savings.

[0192] Optionally, if the LP WUS is applied to the terminal 101 in the RRC idle state or the RRC inactive state, the LP WUS may indicate whether to wake up the MR of the terminal 101 to monitor paging. In this scenario, the LP WUS is broadcast within the cell.

[0193] Optionally, if LP WUS is applied to the terminal 101 in the RRC connected state, the LP WUS may indicate whether to wake up the MR of the terminal 101 to monitor the Physical Downlink Control Channel (PDCCH). In this scenario, the LP WUS is unicast or multicast.

[0194] In another example, to ensure proper detection of the LP WUS, terminal 101 needs to obtain the time and frequency location of the LP WUS transmission by network device 102 before monitoring the LP WUS. Terminal 101 can achieve time and frequency synchronization by detecting a synchronization signal. Optionally, the synchronization signal can be, for example, a Synchronization Signal Block (SSB) or an LP SS.

[0195] Optionally, based on the time-frequency synchronization obtained by the SSB and / or LP SS, the LP WUS may directly carry wake-up related information.

[0196] Optionally, LP SS is used to maintain synchronization with LP WUR.

[0197] In some embodiments, the LP WUR of terminal 101 can support at least two types: one type of LP WUR supports envelope detection of modulation symbols such as OOK symbols, which can be called OOK LR, and the link performance of the OOK LR receiver is relatively poor; the other type of LP WUR can detect the time domain sequence or frequency domain sequence carried by modulation symbols such as OOK symbols, which can be called OFDM LR, and the OFDM LR receiver can improve the link performance.

[0198] Optionally, the LP WUS may include two types: an LP WUS for OOK LR reception is denoted as OOK LP WUS, and another LP WUS for OFDM LR reception is denoted as OFDM LP WUS.

[0199] Optionally, the LP SS may include two types: an LP SS for OOK LR reception, denoted as OOK LP SS, and an LP SS for OFDM LR reception, denoted as OFDM LP SS. Alternatively, the LP SS may include only the OOK LP SS.

[0200] In some embodiments, the LP WUS may carry wake-up information. For example, the LP WUS carries information through amplitude modulation, or carries information through a frequency domain sequence or a time domain sequence corresponding to an OOK symbol.

[0201] Optionally, in amplitude modulation, the OOK symbol may include the following two cases: a high level (ON) symbol represents bit 1, and a low level (OFF) symbol represents bit 0. In conjunction with the description of the following embodiments, a waveform diagram of the OOK symbol may be shown in FIG2c.

[0202] Optionally, the OOK LP WUS is an LP WUS that carries information through OOK amplitude modulation.

[0203] Optionally, the frequency domain sequence corresponding to each OOK symbol, i.e., the frequency domain sequence, can also be used to carry information, wherein the frequency domain sequence can obtain the corresponding time domain sequence after time-frequency conversion. The frequency domain sequence corresponds to the time domain sequence and can be converted into each other. Therefore, the frequency domain sequence or time domain sequence carried by each OOK symbol can be used to carry information. Optionally, on each OOK symbol, multi-bit information can be represented by carrying different sequences. For example, if there are N optional sequences for carrying information on each OOK symbol, then theoretically, N types of information can be carried on the symbol. If corresponding to the number of bits, it can carry floor(log2N) bits. It can be understood that when N>2, the information that can be carried by using time domain or frequency domain sequences on OOK symbols is more than the information that can be carried by using OOK amplitude modulation.

[0204] Optionally, the OFDM LP WUS is an LP WUS that carries information through a frequency domain sequence or a time domain sequence corresponding to each OOK symbol.

[0205] Optionally, the information carried by the frequency domain sequence or time domain sequence corresponding to the OOK symbol may be the same as or different from the information carried by the amplitude modulated OOK symbol. In the embodiment of the present disclosure, the sequence corresponding to the OOK symbol is represented by a time domain sequence or a frequency domain sequence.

[0206] Optionally, the information carried by the frequency domain sequence or time domain sequence corresponding to the OOK symbol, or the information carried by the amplitude-modulated OOK symbol, may be wake-up information, such as an identifier of a terminal that needs to be awakened. When the information carried by the frequency domain sequence or time domain sequence corresponding to the OOK symbol is the same as the information carried by the amplitude-modulated OOK symbol, it may be the identifier of the same terminal. When the information carried by the frequency domain sequence or time domain sequence corresponding to the OOK symbol is different from the information carried by the amplitude-modulated OOK symbol, it may be the identifier of a different terminal.

[0207] In some embodiments, unlike LP WUS, LP SS may carry no information or only a small amount of information, such as a cell ID. Alternatively, OOK LP SS carries no information, while OFDM LP SS carries a small amount of information (such as a cell ID).

[0208] In some embodiments, the low power consumption signal may be in a first signal format.

[0209] Optionally, the first signal format is determined according to a signal format defined by a protocol or a signal format configured by the network device 102. It is understandable that there may be multiple signal formats defined by a protocol or configured by the network device 102, and the first signal format is used to represent one of them rather than to limit a specific signal format.

[0210] Optionally, the signal format is used to indicate a transmission mode or a time-frequency position adopted by the low-power consumption signal.

[0211] In some embodiments, the signal format may include at least one of the following:

[0212] Modulation method;

[0213] Preamble information;

[0214] Frequency domain information;

[0215] CRC information.

[0216] Optionally, when the low power consumption signal is LP WUS, the signal format of the OOK LP WUS signal may be the same as or different from the signal format of the OFDM LP WUS.

[0217] In the implementation of the first aspect, the modulation method can be amplitude shift keying (ASK), frequency shift keying (FSK) or phase shift keying (PSK), etc. Among them, the OOK modulation in the above embodiment is a special ASK modulation.

[0218] Optionally, the low power signal adopts OOK modulation, wherein at least one OOK symbol corresponding to the modulation of the low power signal is carried in an OFDM time domain symbol. The embodiment of the present disclosure takes OOK modulation as an example, and in other embodiments, it can be extended to other ASK modulations.

[0219] Optionally, in OOK modulation of LP WUS or LP SS, an OFDM time-domain symbol can carry one or more OOK symbols; or an OFDM time-domain symbol can carry one or more OOK coded bits. For example, an OFDM time-domain symbol can carry M coded bits, and these M bits are carried in an OFDM time-domain symbol using OOK modulation, where M>=1.

[0220] Optionally, the OOK symbol can be an ON symbol or an OFF symbol. For example, Data1 represents an ON symbol and Data0 represents an OFF symbol.

[0221] In one example, as shown in FIG2c , one OFDM time domain symbol carries one OOK symbol, or one OFDM time domain symbol carries one OOK coded bit, that is, M = 1. In this example, the length of one OFDM time domain symbol is equal to the length of one OOK symbol.

[0222] In another example, as shown in Figures 2d to 2e, one OFDM time-domain symbol carries multiple OOK symbols. In Figure 2d, one OFDM time-domain symbol carries two OOK symbols, or one OFDM time-domain symbol carries two OOK coded bits, i.e., M = 2. In Figure 2e, one OFDM time-domain symbol carries four OOK symbols, or one OFDM time-domain symbol carries four OOK coded bits, i.e., M = 4.

[0223] In this example, the coded bits of the LP WUS information are mapped to OOK symbols after encoding. When M = 2, this corresponds to 1 / 2 Manchester coding, i.e., the encoding rate is 1 / 2. For example, information bit 1 can be mapped to 2 coded bits (1, 0), and information bit 0 can be mapped to 2 coded bits (0, 1). When M = 4, this corresponds to 1 / 4 Manchester coding, i.e., the encoding rate is 1 / 4. Information bit 1 can be mapped to 4 coded bits (1, 0, 1, 0), and information bit 0 can be mapped to 4 coded bits (0, 1, 0, 1).

[0224] Alternatively, in this example, the LP WUS information is mapped to the OOK symbol after encoding. When M=2, it corresponds to 1 / 2 Manchester encoding, that is, the encoding code rate is 1 / 2, such as information bit 1 can be mapped to 2 encoding bits (1, 0), and information bit 0 can be mapped to 2 encoding bits (0, 1); wherein, one OFDM time domain symbol carries 2 OOK symbols, and each of the 2 encoding bits is mapped to a corresponding 1 OOK symbol, that is, 2 encoding bits are mapped one to one with 2 OOK symbols. When M=4, it corresponds to 1 / 2 Manchester encoding, that is, the encoding code rate is 1 / 2, information bit 1 can be mapped to 2 encoding bits (1, 0), information bit 0 can be mapped to 2 encoding bits (0, 1), and 1 OFDM time domain symbol can carry 2 information bits.

[0225] It can be understood that in other examples, if M=4 without Manchester encoding, each of the 4 information bits can be mapped to an OOK symbol, wherein one OFDM time domain symbol still carries 4 OOK symbols.

[0226] Optionally, the number of OOK symbols carried by an OFDM time-domain symbol, that is, the M value, is defined by a protocol; or, the M value is configured through configuration information sent by the network device 102 .

[0227] Optionally, for the terminal 101 in the RRC idle state or the RRC inactive state, the network device 102 may configure the value of M through system information. For the terminal 101 in the RRC connected state, the network device 102 may configure the value of M through RRC signaling.

[0228] Optionally, for the terminal 101 in the RRC connected state, the terminal 101 can report the M value supported by itself to the network device 102 through capability information. Thus, the network device 102 can configure the M value of the LP WUS corresponding to the UE using UE-specific RRC signaling.

[0229] Optionally, the terminal 101 supports carrying a default number of OOK symbols in one OFDM time-domain symbol.

[0230] The default number may be a default value defined by the protocol. For example, when the network device 102 is not configured with M, the terminal 101 considers M to be a default value defined by the protocol.

[0231] Alternatively, a default number M=K is defined, where K is a capability that the terminal 101 must support. There can be one or more values ​​of K, such as 1, 2, or 4. When the terminal 101 does not report its capabilities, the network device 102 assumes that the terminal 101 supports M=K.

[0232] Optionally, when the terminal 101 supports the default number, the network device 102 may not perform M configuration, and the terminal 101 may not report M-related capabilities, so that defining the default number is beneficial to the signaling resources between the network device 102 or the terminal 101.

[0233] In an implementation of the second aspect, the preamble information may include at least one of the following:

[0234] Whether the low-power signal contains a preamble;

[0235] The symbol length occupied by the preamble;

[0236] Modulation method of the preamble;

[0237] OFDM time domain sequence or frequency domain sequence of the preamble;

[0238] Whether the preamble corresponds to a fixed time-domain pattern.

[0239] Optionally, the preamble information may be used to indicate the preamble format of the low power consumption signal. For example, in the embodiment of the present disclosure, the low power consumption signal is LP WUS as an example, and the preamble information is used to indicate the preamble format thereof.

[0240] Optionally, whether to include one or more of the preamble, symbol length, modulation mode, OFDM time domain sequence or frequency domain sequence, and whether to correspond to a fixed time domain pattern may be defined by a protocol, or configured by the network device 102 through system information. If the network device 102 is not configured, the default parameters defined by the protocol may be used.

[0241] Optionally, when a low-power signal requires a preamble, for example, a preamble needs to be included before the low-power signal or the low-power signal needs a prefix preamble, it is necessary to determine at least one other item of preamble information, such as determining one of the following: the symbol length occupied by the preamble; the modulation method of the preamble; the OFDM time domain sequence or frequency domain sequence of the preamble; whether the preamble corresponds to a fixed time domain pattern.

[0242] Optionally, the modulation mode of the preamble code can be OOK modulation. The number of OOK symbols corresponding to the preamble code carried by an OFDM time domain symbol, or the number of OOK coding bits corresponding to the preamble code carried in an OFDM time domain symbol can be defined by the protocol or configured by the network device 102. The number of OOK symbols or coding bits corresponding to the preamble code carried by an OFDM time domain symbol is recorded as M'. Among them, the relevant implementation methods of the preamble code OOK modulation can still refer to the implementation methods of the low-power signal OOK modulation in the aforementioned embodiment, such as the implementation methods related to Figures 2c to 2e.

[0243] Optionally, the number of OOK symbols corresponding to the preamble carried in one OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in one OFDM time domain symbol, that is, M' is greater than M.

[0244] Optionally, the OFDM time domain sequence or frequency domain sequence may be represented by a sequence index.

[0245] Optionally, for a terminal 101 in an RRC connected state, it is necessary to determine whether the preamble code corresponds to a fixed time domain pattern; for a terminal 101 in an RRC idle state or an inactive state, this does not need to be determined.

[0246] When the preamble corresponds to a fixed time-domain pattern, the waveform of the OOK symbol corresponding to the preamble is fixed. In this fixed time-domain pattern, the OOK LP WUS carries no information; only the OFDM LP WUS carries information. In this scenario, the LP WUS sent by network device 102 can be considered to be sent for terminal 101 equipped with OFDM LR.

[0247] In an implementation of the third aspect, the frequency domain information includes at least one of the following:

[0248] SCS corresponding to low-power signals;

[0249] The frequency domain unit where the low-power signal is located.

[0250] Optionally, the frequency domain information may be used to indicate frequency domain information of the LP WUS or the LP SS.

[0251] Optionally, for a terminal 101 in an RRC connected state, only the frequency domain information of the LP WUS may be defined or configured. The terminal 101 in the RRC connected state does not need to monitor the LP SS. Even if it monitors the LP SS, the LP SS is still the LP SS for synchronization of the terminal 101 in the RRC idle or inactive state.

[0252] Optionally, for a terminal 101 in an RRC idle state or an inactive state, the network device 102 may configure the SCS of the LP WUS or LP SS through system information. Optionally, for a terminal 101 in an RRC connected state, the network device 102 may configure the SCS of the LP WUS through UE-specific RRC signaling.

[0253] Optionally, the frequency domain information of the LP WUS or LP SS may also be determined based on related NR channels.

[0254] In one example, the SCS corresponding to the low power consumption signal is the same as the SCS of at least one of the following:

[0255] SSB;

[0256] Type 0CSS;

[0257] Activation BWP of the serving cell.

[0258] In this example, for the terminal 101 in the RRC idle state or inactive state, the SCS of the low power signal (such as LP WUS or LP SS) can be the same as the SCS of the SSB or Type 0CSS.

[0259] In this example, for the terminal 101 in the RRC connected state, the SCS of the low power consumption signal, such as the LP WUS, may be the same as the SCS of the activated BWP of the serving cell, which may be an active downlink (DL) BWP.

[0260] Optionally, the serving cell may be a primary cell of the terminal 101, for example, a primary cell of a Master Cell Group (MCG).

[0261] In another example, the frequency domain unit where the low power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located:

[0262] SSB;

[0263] Type 0CSS;

[0264] Activation BWP of the serving cell.

[0265] Optionally, the frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or, the frequency domain unit is a frequency band, a carrier or an active BWP, and the terminal is in an RRC connected state.

[0266] In this example, for the terminal 101 in the RRC idle state or inactive state, the frequency domain unit where the low power signal (such as LP WUS or LP SS) is located can be the same as or different from the frequency domain unit where the SSB or Type 0CSS is located.

[0267] In this example, for the terminal 101 in the RRC connected state, the frequency domain unit where the low power consumption signal such as LP WUS is located may be the same as or different from the frequency domain unit where the activated BWP of the serving cell is located.

[0268] In an implementation of the fourth aspect, the CRC information includes:

[0269] Whether the low-power signal carries CRC;

[0270] The number of bits occupied by CRC.

[0271] Optionally, the low power consumption signal may be LP WUS or LP SS.

[0272] Optionally, for different types of LP WUS, CRC information may be defined or configured respectively.

[0273] For example, whether the OOK LP WUS carries a CRC is defined by the protocol or configured by the network. If this option is "yes", the number of bits of the CRC carried by the OOK LP WUS is defined by the protocol or configured by the network.

[0274] For another example, whether the OFDM LP WUS carries CRC is defined or configured. When the option is "yes", the number of bits of CRC carried by the OFDM LP WUS is defined by the protocol or configured by the network.

[0275] In one example, it may be defined by a protocol or configured by a network that the OOK LP WUS does not carry a CRC, and the OFDM LP WUS carries a CRC.

[0276] In another example, the OOK LP WUS may carry a CRC 5-bit and the OFDM LP WUS may carry a CRC 8-bit through protocol definition or network configuration.

[0277] Optionally, in a network configuration manner, the network device 102 may configure the terminal 101 in an RRC idle state or an inactive state through system information, or configure the terminal 101 in an RRC connected state through UE specific RRC signaling.

[0278] Step S2102: The terminal 101 performs corresponding operations after receiving the low power consumption signal.

[0279] In some embodiments, when the low power consumption signal is an LP WUS, after the terminal 101 receives the LP WUS via the LP WUR, performing corresponding operations includes:

[0280] If the LP WUS instructs the terminal 101 to wake up, the terminal 101 wakes up the MR, that is, the MR switches from the sleep or deep sleep state to the normal data receiving and transmitting state to perform normal communication transmission.

[0281] Alternatively, if the LP WUS does not indicate wake-up, or is not the LP WUS corresponding to the terminal 101, the terminal 101 may maintain the MR sleep or deep sleep state and still use the LP WUR to monitor the signal to achieve energy saving.

[0282] In some embodiments, when the low power consumption signal is an LP SS, upon receiving the LP SS via the LP WUR, terminal 101 may perform corresponding operations including: obtaining time and frequency synchronization of the LP WUR of terminal 101 based on the LP SS. Optionally, after obtaining time and frequency synchronization, the LP WUR of terminal 101 may more accurately receive the LP WUR.

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

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

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

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

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

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

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

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

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

[0292] The method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2102, such as the method including step S2101.

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

[0294] 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:

[0295] Step S2201 : Terminal 101 sends capability information to network device 102 .

[0296] In some embodiments, the terminal 101 may be a terminal in an RRC connected state.

[0297] In some embodiments, the capability information may be used to indicate a signal format of a low power consumption signal supported by the terminal 101 .

[0298] Optionally, the signal format includes at least one of the following:

[0299] Modulation method;

[0300] Preamble information;

[0301] Frequency domain information;

[0302] CRC information.

[0303] Optionally, the capability information is used to indicate the number of OOK symbols supported by the terminal 101 and carried in one OFDM time domain symbol, that is, the M value supported by the terminal 101.

[0304] In some embodiments, the network device 102 receives capability information to learn about the terminal capabilities to facilitate configuration of M.

[0305] Step S2202 , the network device 102 sends configuration information to the terminal 101 .

[0306] In some embodiments, the configuration information is used to configure a signal format of terminal 101 .

[0307] Optionally, the configuration information is used to indicate the number of OOK symbols carried by an OFDM time domain symbol, that is, to indicate the M value.

[0308] In some embodiments, when the terminal 101 is in the RRC idle state or the RRC inactive state, the configuration information is sent via system information. When the terminal 101 is in the RRC connected state, the configuration information is sent via RRC signaling, such as UE-specific RRC signaling.

[0309] In some embodiments, the terminal 101 receives the configuration information to learn the signal format configured by the network device 102 .

[0310] Step S2203 : The network device 102 sends a low power consumption signal to the terminal 101 .

[0311] In some embodiments, the implementation method of step S2203 can refer to the optional implementation method of step S2101 in Figure 2a, which will not be repeated here.

[0312] Step S2204: The terminal 101 performs corresponding operations after receiving the low power consumption signal.

[0313] In some embodiments, the implementation method of step S2204 can refer to the optional implementation method of step S2102 in Figure 2a, which will not be repeated here.

[0314] The method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2204, such as the method including step S2203.

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

[0316] In some embodiments, the execution order of step S2201 or S2202 can be exchanged or executed synchronously.

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

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

[0319] Step S3101: Send capability information.

[0320] In some embodiments, the implementation method of step S3101 can refer to the optional implementation method of step S2201 in Figure 2b, which will not be repeated here.

[0321] Step S3102, receiving configuration information.

[0322] In some embodiments, the implementation method of step S3102 can refer to the optional implementation method of step S2202 in Figure 2b, which will not be repeated here.

[0323] Step S3103: receiving a low power consumption signal.

[0324] In some embodiments, the implementation method of step S3101 can refer to the optional implementation method of step S2101 in Figure 2a or S2203 in Figure 2b, which will not be repeated here.

[0325] Step S3104: Execute corresponding operations after receiving the low power consumption signal.

[0326] In some embodiments, the implementation method of step S3104 can refer to the optional implementation method of step S2102 in Figure 2a, which will not be repeated here.

[0327] The method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3104, such as the method including step S3103.

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

[0329] 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:

[0330] Step S3201 , receiving a low power consumption signal sent by the network device 102 .

[0331] In some embodiments, the implementation method of step S201 can refer to the optional implementation method of step S2101 in Figure 2a or S2203 in Figure 2b, which will not be repeated here.

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

[0333] 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:

[0334] Step S4101: receiving capability information.

[0335] In some embodiments, the implementation method of step S4101 can refer to the optional implementation method of step S2201 in Figure 2b, which will not be repeated here.

[0336] Step S4102, sending configuration information.

[0337] In some embodiments, the implementation method of step S4102 can refer to the optional implementation method of step S2202 in Figure 2b, which will not be repeated here.

[0338] Step S4103: Send a low power consumption signal.

[0339] In some embodiments, the implementation method of step S4103 can refer to the optional implementation method of step S2101 in Figure 2a or S2203 in Figure 2b, which will not be repeated here.

[0340] The method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4103, such as the method including step S4103.

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

[0342] 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:

[0343] Step S4201: Send a low power consumption signal to the terminal 101.

[0344] In some embodiments, the implementation method of step S4201 can refer to the optional implementation method of step S2101 in Figure 2a or S2203 in Figure 2b, which will not be repeated here.

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

[0346] The method of the embodiment of the present disclosure can determine the LP WUS or LP-SS signal format to meet the transmission requirements of different scenarios. The signal format mentioned here includes the modulation method used by the LP WUS signal, SCS, preamble length, preamble modulation method, CRC length, etc. To facilitate understanding of the method of determining the signal format of the LP WUS in the embodiment of the present disclosure, some examples are listed below:

[0347] Example 1:

[0348] Determines the modulation method used by OOK LP WUS or OOK LP SS.

[0349] An OFDM time domain symbol can carry M (M>=1) bits, which are carried in an OFDM time domain symbol using OOK modulation. Figures 2c to 2d illustrate scenarios where M=1, M=2, or M=4, respectively.

[0350] Optionally, M may be defined by the protocol.

[0351] Optionally, M can be configured by the base station. For RRC idle or inactive terminals, M can be configured in system information. For RRC connected terminals, M can be configured using UE-specific RRC signaling.

[0352] Optionally, when the base station does not configure M, the UE considers M to be a default value defined by the protocol.

[0353] Optionally, the UE may also report the M value supported by itself to the base station, so that the base station can configure the M value of the LP WUS corresponding to the UE using UE-specific RRC signaling (applicable to RRC connected UE).

[0354] Optionally, M=K (there may be one or more K values) is defined as a capability that the UE must support. K may be 1, 2, or 4. When the UE does not report its own capabilities, the base station assumes that the UE supports M=K.

[0355] Example 2:

[0356] Determine the preamble format of LP WUS.

[0357] In some embodiments, for an RRC idle or inactive UE, determining the preamble format of the LP WUS includes:

[0358] 1) Determine whether the LP WUS is prefixed with a preamble;

[0359] 2) Determine the symbol duration occupied by the preamble;

[0360] 3) Determine the OOK modulation mode used by the preamble, that is, the value of M in embodiment 1. In one case, the M of the preamble is greater than the M value of the LP WUS data information portion;

[0361] 4) Determine the OFDM time domain / frequency domain sequence used on the preamble (eg, the index of the sequence).

[0362] Optionally, the above 1) to 4) can all be defined by the protocol or configured by the base station through system information. If the base station is not configured, the default value defined in the protocol is used.

[0363] In some embodiments, for an RRC connected UE, determining the preamble format of the LP WUS includes:

[0364] 5) Determine whether the LP WUS is prefixed with a preamble;

[0365] 6) Determine the symbol duration occupied by the preamble;

[0366] 7) Determine the OOK modulation mode used by the preamble, that is, the value of M in content 1. In one embodiment, the M value of the preamble is greater than the M value of the LP WUS data information portion;

[0367] 8) Determine whether the OOK time-domain signal used in the preamble is a fixed time-domain pattern. (In the case of a fixed time-domain pattern, the OOK-LP WUS carries no information, and only the OFDM-LP WUS carries information, meaning that this LP WUS is sent specifically for OFDM LR UEs.)

[0368] 9) Determine the OFDM time domain / frequency domain sequence used on the preamble (e.g., sequence index)

[0369] Optionally, the above 5) to 9) can be defined by the protocol or configured by the base station through UE-specific signaling information. If the base station is not configured, the default value defined in the protocol is used.

[0370] Example 3:

[0371] Determine the SCS of LP WUS or LP-SS.

[0372] In some embodiments, for an RRC idle or inactive UE, determining the SCS of an LP WUS or LP-SS includes:

[0373] 1) The SCS of LP WUS or LP-SS is the same as that of NR channels.

[0374] Optionally, the above NR channels can be SSB or Type 0CSS;

[0375] Optionally, LP WUS or LP-SS and NR channels are in the same frequency domain unit (carrier or band);

[0376] Optionally, LP WUS or LP-SS and NR channels are in different frequency domain units (carrier or band).

[0377] 2) The SCS of LP WUS or LP-SS is configured by system information.

[0378] In some embodiments, for an RRC connected UE, determining the SCS of an LP WUS or LP-SS includes:

[0379] 3) The SCS of the LP WUS is the same as the NR channels. A connected UE does not monitor the LP SS, and even if a connected UE monitors the LP-SS, the LP-SS is the same as the LP-SS used in RRC idle or inactive conditions.

[0380] Optionally, the NR channels may be an SCS of an active DL bwp of a serving cell of the UE, and the serving cell may be a primary cell of the UE, and further, may be a primary cell of the MCG;

[0381] Optionally, the LP WUS and NR channels are on the same frequency domain unit (band, carrier or active BWP);

[0382] Optionally, LP WUS or LP-SS and NR channels are in different frequency domain units (band, carrier or active BWP).

[0383] 4) The SCS of LP WUS is configured by UE-specific RRC signaling.

[0384] Example 4:

[0385] Determine the CRC length of the LP WUS.

[0386] In some embodiments, determining whether the OOK LP WUS carries a CRC;

[0387] In some embodiments, determining the number of bits of the OOK LP WUS carrying the CRC;

[0388] In some embodiments, determining whether the OFDM LP WUS carries a CRC;

[0389] In some embodiments, the number of bits of the OFDM LP WUS carrying the CRC is determined.

[0390] In some embodiments, any of the above embodiments may be configured through protocol definition, base station system message configuration, and UE specific signaling configuration;

[0391] In an optional embodiment, the OOK LP WUS does not carry a CRC, and the OFDM LP WUS carries a CRC;

[0392] In an optional embodiment, the OOK LP WUS carries a CRC of 5 bits, and the OFDM LP WUS carries a CRC of 8 bits.

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

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

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

[0396] Figure 5a is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in Figure 5a, terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. In some embodiments, transceiver module 5101 is configured to receive a low-power signal in a first signal format sent by a network device.

[0397] Optionally, the transceiver module 5101 is configured to execute at least one of the communication steps of sending and / or receiving performed by the terminal 101 in any of the above methods, which are not described in detail here. Optionally, the processing module 5102 is configured to execute at least one of the other steps performed by the terminal 101 in any of the above methods, which are not described in detail here.

[0398] In some embodiments, the first signal format is determined according to a signal format defined by a protocol or a signal format configured by a network device.

[0399] In some embodiments, the signal format includes at least one of the following:

[0400] Modulation method;

[0401] Preamble information;

[0402] Frequency domain information;

[0403] Cyclic redundancy check code CRC information.

[0404] In some embodiments, the modulation method used by the low power consumption signal is a binary on-off keying (OOK) modulation method, wherein at least one OOK symbol corresponding to the modulation of the low power consumption signal is carried on an orthogonal frequency division multiplexing (OFDM) time domain symbol.

[0405] In some embodiments, the number of OOK symbols carried by one OFDM time-domain symbol is defined by a protocol; or,

[0406] The number of OOK symbols carried by an OFDM time-domain symbol is determined according to configuration information.

[0407] In some embodiments, the configuration information is sent via system information, and the terminal is in a radio resource control RRC idle state or an RRC inactive state; or, the configuration information is sent via RRC signaling, and the terminal is in an RRC connected state.

[0408] In some embodiments, the transceiver module 5101 is further used to send capability information to the network device, where the capability information is used to indicate the number of OOK symbols supported by the terminal in one OFDM time domain symbol.

[0409] In some embodiments, the terminal supports carrying a default number of OOK symbols in one OFDM time-domain symbol.

[0410] In some embodiments, the preamble information includes at least one of the following:

[0411] Whether the low-power signal contains a preamble;

[0412] The symbol length occupied by the preamble;

[0413] Modulation method of the preamble;

[0414] OFDM time domain sequence or frequency domain sequence of the preamble;

[0415] Whether the preamble corresponds to a fixed time domain pattern.

[0416] In some embodiments, the modulation mode of the preamble code is OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in an OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in the OFDM time domain symbol.

[0417] In some embodiments, the frequency domain information includes at least one of the following:

[0418] Subcarrier spacing SCS corresponding to the low power consumption signal;

[0419] The frequency domain unit where the low-power signal is located.

[0420] In some embodiments, the frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or

[0421] The frequency domain unit is a frequency band, a carrier or an activated bandwidth part BWP, and the terminal is in an RRC connected state.

[0422] In some embodiments, the SCS corresponding to the low power consumption signal is the same as the SCS of at least one of the following:

[0423] Synchronization signal block SSB;

[0424] Type 0 public search space CSS;

[0425] Activation BWP of the serving cell.

[0426] In some embodiments, the frequency domain unit where the low power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located:

[0427] SSB;

[0428] Type 0CSS;

[0429] Activation BWP of the serving cell.

[0430] In some embodiments, the CRC information includes:

[0431] Whether the low-power signal carries CRC;

[0432] The number of bits occupied by CRC.

[0433] In some embodiments, the low power signal is:

[0434] Low power wake-up signal LP WUS, the terminal is in RRC connected state, RRC idle state or RRC inactive state; or,

[0435] Low power synchronization signal LP SS, the terminal is in RRC idle state or RRC inactive state.

[0436] FIG5 b is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. As shown in FIG5 b , the network device 5200 may include at least one of a transceiver module 5201 and a processing module 5202 .

[0437] In some embodiments, when the network device 5200 is a network device, the transceiver module 5201 is used to send a low-power consumption signal in a first signal format to the terminal.

[0438] Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps of sending and / or receiving performed by the network device in any of the above methods, which are not described in detail here. Optionally, the processing module 5202 is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

[0439] In some embodiments, the first signal format is determined according to a signal format defined by a protocol or a signal format configured by a network device.

[0440] In some embodiments, the signal format includes at least one of the following:

[0441] Modulation method;

[0442] Preamble information;

[0443] Frequency domain information;

[0444] CRC information.

[0445] In some embodiments, the modulation method used by the low power consumption signal is an OOK modulation method, wherein at least one OOK symbol corresponding to the modulation of the low power consumption signal is carried on an OFDM time domain symbol.

[0446] In some embodiments, the number of OOK symbols carried by one OFDM time-domain symbol is defined by a protocol; or,

[0447] The number of OOK symbols carried by an OFDM time-domain symbol is determined according to configuration information.

[0448] In some embodiments, the configuration information is sent via system information, and the terminal is in a radio resource control RRC idle state or an RRC inactive state; or, the configuration information is sent via RRC signaling, and the terminal is in an RRC connected state.

[0449] In some embodiments, the transceiver module 5201 is further used to receive capability information sent by the terminal, where the capability information is used to indicate the number of OOK symbols supported by the terminal in one OFDM time domain symbol.

[0450] In some embodiments, the number of OOK symbols carried in one OFDM time-domain symbol is a default number.

[0451] In some embodiments, the preamble information includes at least one of the following:

[0452] Whether the low-power signal contains a preamble;

[0453] The symbol length occupied by the preamble;

[0454] Modulation method of the preamble;

[0455] OFDM time domain sequence or frequency domain sequence of the preamble;

[0456] Whether the preamble corresponds to a fixed time domain pattern.

[0457] In some embodiments, the modulation mode of the preamble code is OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in one OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in one OFDM time domain symbol.

[0458] In some embodiments, the frequency domain information includes at least one of the following:

[0459] SCS corresponding to low-power signals;

[0460] The frequency domain unit where the low-power signal is located.

[0461] In some embodiments, the frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or

[0462] The frequency domain unit is a frequency band, a carrier or an activated bandwidth part BWP, and the terminal is in an RRC connected state.

[0463] In some embodiments, the SCS corresponding to the low power consumption signal is the same as the SCS of at least one of the following:

[0464] SSB;

[0465] Type 0CSS;

[0466] Activation BWP of the serving cell.

[0467] In some embodiments, the frequency domain unit where the low power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located:

[0468] SSB;

[0469] Type 0CSS;

[0470] Activation BWP of the serving cell.

[0471] In some embodiments, the CRC information includes:

[0472] Whether the low-power signal carries CRC;

[0473] The number of bits occupied by CRC.

[0474] In some embodiments, the low power signal is:

[0475] Low power wake-up signal LP WUS, the terminal is in RRC connected state, RRC idle state or RRC inactive state; or,

[0476] Low power synchronization signal LP SS, the terminal is in RRC idle state or RRC inactive state.

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

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

[0479] Figure 6a is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 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 implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above methods. Communication device 6100 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.

[0480] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 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 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0481] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 6101 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.

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

[0483] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. 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.

[0484] FIG6b is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6b , but the present disclosure is not limited thereto.

[0485] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

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

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

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

[0489] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 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 transient storage medium.

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

[0491] 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

[0492] The terminal can receive low-power signals transmitted based on a certain signal format. On the basis of energy saving, the terminal can receive low-power signals in a timely and effective manner to adapt to the transmission requirements of different scenarios and improve the efficiency of necessary communications.

Claims

1. A communication method, performed by a terminal, comprising: A low power consumption signal in a first signal format sent by a network device is received.

2. The method according to claim 1, wherein The first signal format is determined according to a signal format defined by a protocol or a signal format configured by the network device.

3. The method according to claim 2, wherein: The signal format includes at least one of the following: Modulation method; Preamble information; Frequency domain information; Cyclic redundancy check code CRC information.

4. The method according to claim 3, wherein: The modulation mode adopted by the low-power signal is a binary on-off keying (OOK) modulation mode, wherein at least one OOK symbol corresponding to the modulation of the low-power signal is carried on an orthogonal frequency division multiplexing (OFDM) time domain symbol.

5. The method according to claim 4, wherein: The number of OOK symbols carried by one OFDM time domain symbol is defined by a protocol; or, The number of OOK symbols carried by one OFDM time domain symbol is determined according to configuration information.

6. The method according to claim 5, wherein: The configuration information is sent via system information, and the terminal is in a radio resource control RRC idle state or an RRC inactive state; or, the configuration information is sent via RRC signaling, and the terminal is in an RRC connected state.

7. The method according to claim 5, wherein: The method further comprises: Capability information is sent to the network device, where the capability information is used to indicate the number of OOK symbols supported by the terminal and carried in one OFDM time domain symbol.

8. The method of claim 5, wherein: The terminal supports carrying a default number of OOK symbols in one OFDM time-domain symbol.

9. The method according to any one of claims 3 to 8, wherein: The preamble information includes at least one of the following: Whether the low-power signal includes a preamble; The symbol length occupied by the preamble; Modulation method of the preamble; OFDM time domain sequence or frequency domain sequence of the preamble; Whether the preamble corresponds to a fixed time domain pattern.

10. The method of claim 9, wherein: The modulation mode of the preamble code is an OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in an OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in the OFDM time domain symbol.

11. The method according to any one of claims 3 to 10, wherein: The frequency domain information includes at least one of the following: The subcarrier spacing SCS corresponding to the low power consumption signal; The frequency domain unit where the low-power consumption signal is located.

12. The method of claim 11, wherein: The frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or The frequency domain unit is a frequency band, a carrier or an activated bandwidth part BWP, and the terminal is in an RRC connected state.

13. The method of claim 11, wherein: The SCS corresponding to the low-power signal is the same as the SCS of at least one of the following: Synchronization signal block SSB; Type 0 public search space CSS; Activation BWP of the serving cell.

14. The method of claim 11, wherein: The frequency domain unit where the low-power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located: SSB; Type 0 CSS; Activation BWP of the serving cell.

15. The method according to any one of claims 3 to 14, wherein: The CRC information includes: Whether the low-power signal carries a CRC; The number of bits occupied by the CRC.

16. The method according to any one of claims 1 to 15, wherein: The low power consumption signal is: Low power consumption wake-up signal LP WUS, the terminal is in RRC connected state, RRC idle state or RRC inactive state; or, Low power synchronization signal LP SS, the terminal is in RRC idle state or RRC inactive state.

17. A communication method, performed by a network device, the method comprising: A low power consumption signal in a first signal format is sent to the terminal.

18. The method of claim 17, wherein: The first signal format is determined according to a signal format defined by a protocol or a signal format configured by the network device.

19. The method of claim 18, wherein: The signal format includes at least one of the following: Modulation method; Preamble information; Frequency domain information; CRC information.

20. The method of claim 19, wherein: The modulation mode adopted by the low-power signal is the OOK modulation mode, wherein at least one OOK symbol corresponding to the modulation of the low-power signal is carried on an OFDM time domain symbol.

21. The method of claim 20, wherein: The number of OOK symbols carried by one OFDM time domain symbol is defined by a protocol; or, The number of OOK symbols carried by one OFDM time domain symbol is determined according to configuration information.

22. The method of claim 21, wherein: The configuration information is sent via system information, and the terminal is in a radio resource control RRC idle state or an RRC inactive state; or, the configuration information is sent via RRC signaling, and the terminal is in an RRC connected state.

23. The method of claim 21, wherein: The method further comprises: Receive capability information sent by the terminal, where the capability information is used to indicate the number of OOK symbols supported by the terminal and carried in one OFDM time domain symbol.

24. The method of claim 21, wherein: The number of OOK symbols carried in one OFDM time domain symbol is a default number.

25. The method according to any one of claims 19 to 24, wherein: The preamble information includes at least one of the following: Whether the low-power signal includes a preamble; The symbol length occupied by the preamble; Modulation method of the preamble; OFDM time domain sequence or frequency domain sequence of the preamble; Whether the preamble corresponds to a fixed time domain pattern.

26. The method of claim 25, wherein: The modulation mode of the preamble code is an OOK modulation mode, wherein the number of OOK symbols corresponding to the preamble code carried in one OFDM time domain symbol is greater than the number of OOK symbols corresponding to the low power consumption signal carried in one OFDM time domain symbol.

27. The method according to any one of claims 19 to 26, wherein: The frequency domain information includes at least one of the following: The SCS corresponding to the low-power signal; The frequency domain unit where the low-power consumption signal is located.

28. The method of claim 27, wherein: The frequency domain unit is a frequency band or a carrier, and the terminal is in an RRC idle state or an RRC inactive state; or The frequency domain unit is a frequency band, a carrier or an activated bandwidth part BWP, and the terminal is in an RRC connected state.

29. The method of claim 27, wherein: The SCS corresponding to the low-power signal is the same as the SCS of at least one of the following: SSB; Type 0 CSS; Activation BWP of the serving cell.

30. The method of claim 27, wherein: The frequency domain unit where the low-power consumption signal is located is the same as the frequency domain unit where at least one of the following items is located: SSB; Type 0 CSS; Activation BWP of the serving cell.

31. The method according to any one of claims 19 to 30, wherein: The CRC information includes: Whether the low-power signal carries a CRC; The number of bits occupied by the CRC.

32. The method according to any one of claims 17 to 31, wherein The low power consumption signal is: Low power consumption wake-up signal LP WUS, the terminal is in RRC connected state, RRC idle state or RRC inactive state; or, Low power synchronization signal LP SS, the terminal is in RRC idle state or RRC inactive state.

33. A terminal comprising: The transceiver module is used to receive a low-power consumption signal in a first signal format sent by a network device.

34. A network device comprising: The transceiver module is used to send a low-power consumption signal in a first signal format to the terminal.

35. A communication system comprising a terminal and a network device, wherein: The terminal is configured to implement the method according to any one of claims 1 to 16; The network device is configured to implement the method according to any one of claims 17 to 32.

36. A terminal comprising: one or more processors; The terminal is configured to implement the method according to any one of claims 1 to 16.

37. A network device comprising: one or more processors; The network device is configured to implement the method according to any one of claims 17 to 32.

38. 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 16 or any one of claims 17 to 32.

39. A program product, wherein When the program product is executed by a communication device, the communication device is caused to execute the method according to any one of claims 1 to 16 or any one of claims 17 to 32.

Images