Communication method, terminal, network device, and storage medium

Abstract

The present disclosure relates to a communication method, a terminal, a network device, and a storage medium. The method comprises: receiving downlink information sent by a network device, wherein a first waveform is applied to a downlink channel used for transmitting the downlink information, and the first waveform is one of at least two waveforms supported by the downlink channel. In the method of the present disclosure, a downlink channel can support a plurality of waveforms, and a terminal can receive downlink information transmitted by a network device on the basis of a specific waveform, so that suitable waveforms can be applied to different communication scenarios on the basis of communication requirements, thereby improving the communication efficiency in different scenarios.

Description

Communication methods, terminals, network devices and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, terminal, network device and storage medium. Background Technology

[0002] In 5G New Radio (NR), only one waveform is supported for downlink. With the development of communication technology and the need for integrated design of terrestrial networks (TN) and non-terrestrial networks (NTN), the waveform support for downlink in 5G cannot meet the needs of more scenarios.

[0003] Summary of the Invention

[0004] This disclosure provides a communication method, a terminal, a network device, and a storage medium.

[0005] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0006] The downlink information sent by the network device is received, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0007] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0008] Downlink information is sent to the terminal, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0009] Thirdly, embodiments of this disclosure provide a terminal, including:

[0010] The transceiver module is used to receive downlink information sent by a network device, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0011] Fourthly, embodiments of this disclosure provide a communication device, including:

[0012] The transceiver module is used to send downlink information to the terminal, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0013] Fifthly, embodiments of this disclosure provide a communication device, including:

[0014] One or more processors;

[0015] The communication device is configured to implement the method described in the first aspect or the second aspect.

[0016] Sixthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0017] The terminal is configured to implement the method as described in the first aspect;

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

[0019] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0020] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0021] Eighthly, embodiments of this disclosure provide a program product, wherein,

[0022] When the program product is executed by a communication device, the communication device performs the method as described in the first aspect or the second aspect.

[0023] In the embodiments of this disclosure, the downlink channel can support multiple waveforms, and the terminal can receive downlink information transmitted by the network device based on a specific waveform. Thus, appropriate waveforms can be applied based on communication needs in different scenarios, thereby improving communication efficiency in different scenarios. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

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

[0026] Figure 2a is an exemplary interactive schematic diagram of a method provided according to an embodiment of the present disclosure;

[0027] Figures 2b to 2c are schematic diagrams of different waveform processing procedures provided according to embodiments of the present disclosure;

[0028] Figures 3a to 3d are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0029] Figures 4a to 4d are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0030] Figure 5a is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0031] Figure 5b is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0032] Figure 6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0033] Figure 6b is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0034] This disclosure provides a communication method, a terminal, a network device, and a storage medium.

[0035] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0036] The downlink information sent by the network device is received, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0037] In the above embodiments, the downlink channel can support multiple waveforms, and the terminal can receive downlink information transmitted by the network device based on a specific waveform. Thus, appropriate waveforms can be applied based on communication needs in different scenarios, thereby improving communication efficiency in different scenarios.

[0038] In conjunction with the embodiments of the first aspect, in some embodiments, the first waveform of the downlink channel application is determined by a protocol definition.

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

[0040] Receive first information sent by the network device, the first information being used to indicate that the waveform used in the downlink channel is the first waveform.

[0041] In conjunction with the embodiments of the first aspect, in some embodiments, the first information includes a first information field, which is used to indicate the name or index of the first waveform.

[0042] In conjunction with the embodiments of the first aspect, in some embodiments, the first information includes a second information field, which is used to indicate whether a second waveform among multiple waveforms is enabled; wherein, when the second waveform is enabled, the first waveform is the second waveform; when the second waveform is not enabled, the first waveform is the default waveform.

[0043] In conjunction with the embodiments of the first aspect, in some embodiments, the first information includes a third information field, which is used to indicate whether the transformation function corresponding to the waveform is enabled; wherein, when the transformation function is enabled, the first waveform is the waveform that needs to be transformed in the encoding and decoding process; when the transformation function is not enabled, the first waveform is the default waveform.

[0044] In conjunction with the embodiments of the first aspect, in some embodiments, the downlink channel includes:

[0045] Physical Downlink Control Channel (PDCCH);

[0046] Physical Downlink Shared Channel (PDSCH);

[0047] Physical Broadcast Channel (PBCH).

[0048] In conjunction with the embodiments of the first aspect, in some embodiments, different PDCCHs satisfy at least one of the following:

[0049] Different PDCCH formats support or apply different waveforms;

[0050] PDCCHs with different resource unit occupancy rates support or apply different waveforms.

[0051] The PDCCH used to transmit downlink control information (DCI) in different formats supports or applies different waveforms.

[0052] The PDCCH used to transmit different Radio Network Temporary Identity (RNTI) scrambled DCI waveforms supports or is applied differently.

[0053] In conjunction with the embodiments of the first aspect, in some embodiments, the PDSCH includes: a DCI dynamically scheduled PDSCH.

[0054] In conjunction with the embodiments of the first aspect, in some embodiments, the PDSCH includes at least one of the following:

[0055] The first PDSCH used to transmit message B during the two-step random access process;

[0056] The second PDSCH used to transmit message 2 during the four-step random access process;

[0057] The third PDSCH used to transmit message 4 during the four-step random access process.

[0058] In conjunction with the embodiments of the first aspect, in some embodiments, when the PDSCH includes a second PDSCH, the waveform applied by the first PDSCH is the same as the waveform applied by the second PDSCH.

[0059] In conjunction with the embodiments of the first aspect, in some embodiments, when the PDSCH includes a first PDSCH or a second PDSCH, the waveform applied by the third PDSCH is the same as the waveform applied by the first PDSCH or the second PDSCH.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the PDSCH is a semi-statically scheduled PDSCH.

[0061] In conjunction with the embodiments of the first aspect, in some embodiments, when the downlink information is a downlink reference signal, the sequence generation method and / or resource mapping method of the downlink reference signal are determined according to the protocol definition.

[0062] In conjunction with the embodiments of the first aspect, in some embodiments, when the downlink information is a downlink reference signal, the method further includes:

[0063] The system receives second information sent by a network device, which indicates the sequence generation method and / or resource mapping method of the downlink reference signal.

[0064] In conjunction with the embodiments of the first aspect, in some embodiments, the sequence generation method and / or resource mapping method of the downlink reference signal used for the downlink channel are different when the waveform of the downlink channel application is different.

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

[0066] Demodulation Reference Signal (DMRS) used for PDSCH;

[0067] DMRS for PDCCH;

[0068] Phase Tracking Reference Signal (PTRS);

[0069] Tracking Reference Signal (TRS);

[0070] Channel-State-Information Reference Signal (CSI-RS);

[0071] Primary synchronization signal (PSS);

[0072] Secondary synchronization signal (SSS);

[0073] Positioning reference signal (PRS).

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

[0075] Send third information to the network device, which includes waveforms for the downlink channel that the terminal supports demodulation.

[0076] In conjunction with the embodiments of the first aspect, in some embodiments, the third information includes: waveforms supported by the terminal in addition to the default waveform.

[0077] In conjunction with the embodiments of the first aspect, in some embodiments, the multiple waveforms include at least two of the following:

[0078] Orthogonal Frequency Division Multiplexing (OFDM) waveform;

[0079] Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform;

[0080] Orthogonal time-frequency space OTFS waveform.

[0081] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0082] Downlink information is sent to the terminal, wherein the downlink channel used to transmit the downlink information applies a first waveform, which is one of at least two waveforms supported by the downlink channel.

[0083] In conjunction with the embodiments of the second aspect, in some embodiments, the first waveform applied to the downlink channel is determined by a protocol definition.

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

[0085] Send first information to the terminal. The first information is used to indicate that the waveform used in the downlink channel is the first waveform.

[0086] In conjunction with embodiments of the second aspect, in some embodiments, the first information includes a first information field, which is used to indicate the name or index of the first waveform.

[0087] In conjunction with the embodiments of the second aspect, in some embodiments, the first information includes a second information field, which is used to indicate whether a second waveform among multiple waveforms is enabled; wherein, when the second waveform is enabled, the first waveform is the second waveform; when the second waveform is not enabled, the first waveform is the default waveform.

[0088] In conjunction with the embodiments of the second aspect, in some embodiments, the first information includes a third information field, which is used to indicate whether the transformation function corresponding to the waveform is enabled; wherein, when the transformation function is enabled, the first waveform is the waveform that needs to be transformed in the encoding and decoding process; when the transformation function is not enabled, the first waveform is the default waveform.

[0089] In conjunction with embodiments of the second aspect, in some embodiments, the downlink channel includes:

[0090] Physical Downlink Control Channel (PDCCH);

[0091] Physical Downlink Shared Channel (PDSCH);

[0092] Physical Broadcast Channel (PBCH).

[0093] In conjunction with the embodiments of the second aspect, in some embodiments,

[0094] Different PDCCH formats support or apply different waveforms;

[0095] PDCCHs with different resource unit occupancy rates support or apply different waveforms.

[0096] The PDCCH used to transmit downlink control information (DCI) in different formats supports or applies different waveforms.

[0097] The PDCCH used to transmit different wireless network temporary flags RNTI scrambled DCI supports or applies different waveforms.

[0098] In conjunction with the embodiments of the second aspect, in some embodiments, the PDSCH includes: a DCI dynamically scheduled PDSCH.

[0099] In conjunction with embodiments of the second aspect, in some embodiments, the PDSCH includes at least one of the following:

[0100] The first PDSCH used to transmit message B during the two-step random access process;

[0101] The second PDSCH used to transmit message 2 during the four-step random access process;

[0102] The third PDSCH used to transmit message 4 during the four-step random access process.

[0103] In conjunction with the embodiments of the second aspect, in some embodiments, when the PDSCH includes the second PDSCH, the waveform applied by the first PDSCH is the same as the waveform applied by the second PDSCH.

[0104] In conjunction with the embodiments of the second aspect, in some embodiments, when the PDSCH includes the first PDSCH or the second PDSCH, the waveform of the third PDSCH application is the same as the waveform of the first PDSCH or the second PDSCH application.

[0105] In conjunction with the embodiments of the second aspect, in some embodiments, the PDSCH is a semi-statically scheduled PDSCH.

[0106] In conjunction with the embodiments of the second aspect, in some embodiments, when the downlink information is a downlink reference signal, the sequence generation method and / or resource mapping method of the downlink reference signal are determined according to the protocol definition.

[0107] In conjunction with the embodiments of the second aspect, in some embodiments, when the downlink information is a downlink reference signal, the method further includes:

[0108] Send a second message to the terminal, the second message being used to indicate the sequence generation method and / or resource mapping method of the downlink reference signal.

[0109] In conjunction with the embodiments of the second aspect, in some embodiments, the sequence generation method and / or resource mapping method of the downlink reference signal used for the downlink channel are different when the waveform of the downlink channel application is different.

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

[0111] The demodulation reference signal DMRS is used for PDSCH;

[0112] DMRS for PDCCH;

[0113] Phase tracking reference signal PTRS;

[0114] Tracking reference signal TRS;

[0115] Channel State Information Reference Signal (CSI-RS);

[0116] Master synchronization signal PSS;

[0117] Auxiliary synchronization signal SSS;

[0118] Positioning reference signal PRS.

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

[0120] The receiving terminal sends third information, which includes waveforms for the downlink channel that the terminal supports demodulation.

[0121] In conjunction with embodiments of the second aspect, in some embodiments, the third information includes: waveforms supported by the terminal in addition to the default waveform.

[0122] In conjunction with the embodiments of the second aspect, in some embodiments, the multiple waveforms include at least two of the following:

[0123] Orthogonal Frequency Division Multiplexing (OFDM) waveform;

[0124] Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform;

[0125] Orthogonal time-frequency space OTFS waveform.

[0126] Thirdly, embodiments of this disclosure provide a terminal, including:

[0127] The transceiver module is used to receive downlink information sent by the network device, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of a variety of waveforms supported by the downlink channel.

[0128] Fourthly, embodiments of this disclosure provide a communication device, including:

[0129] The transceiver module is used to send downlink information to the terminal, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of a variety of waveforms supported by the downlink channel.

[0130] Fifthly, embodiments of this disclosure provide a communication device, including:

[0131] One or more processors;

[0132] The communication device is configured to implement the method described in the first aspect or the second aspect.

[0133] Sixthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0134] The terminal is configured to implement the method as described in the first aspect;

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

[0136] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0137] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0138] Eighthly, embodiments of this disclosure provide a program product, wherein,

[0139] When the program product is executed by a communication device, the communication device performs the method as described in the first aspect or the second aspect.

[0140] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0141] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0142] It is understood that the aforementioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0143] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0144] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0145] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0146] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0147] In the embodiments of this disclosure, "multiple" refers to two or more.

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

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

[0150] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0151] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0152] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0153] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0154] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

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

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

[0157] 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," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

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

[0159] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0161] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0162] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0163] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

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

[0165] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0166] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

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

[0168] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

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

[0170] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0171] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to a part thereof, but are not limited thereto.

[0172] The entities shown in Figure 1 are illustrative. The communication system may include all or some of the entities in Figure 1, or it may include other entities outside of Figure 1. The number and form of each entity are arbitrary. The connection relationship between the entities is illustrative. The entities may not be connected to each other or may be connected in any way. The connection may be direct or indirect, wired or wireless.

[0173] The embodiments disclosed herein 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication processing methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0174] In 5G NR, downlink only supports one waveform: Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM), or OFDM for short. This waveform has a relatively high peak-to-average power ratio (PAPR). When NTN was first developed in Release 18 (Rel-18), the issue of downlink (DL) PAPR was addressed, but there were certain limitations to waveform modifications.

[0175] In 6G downlink waveform design, if the integrated design of TN and NTN networks is considered simultaneously, the communication system may need to support multiple downlink waveforms to meet the needs of more scenarios. It is necessary to address how the terminal obtains the downlink waveform in this coexisting scenario, so that the terminal can handle different waveforms with different generation and decoding methods appropriately.

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

[0177] In step S2101, terminal 101 sends third information to network device 102.

[0178] In some embodiments, the third information includes waveforms for the downlink channel that the terminal 101 supports demodulation.

[0179] Optionally, the third piece of information can be capability information.

[0180] In some embodiments, the communication system in this disclosure can support multiple downlink waveforms, such as supporting more than one waveform simultaneously for downlink channel or signal transmission. In this step, terminal 101 can report the downlink waveforms it supports processing via third information for network reference.

[0181] In some embodiments, the downlink waveforms supported by the communication system, or the various downlink waveforms applicable to the downlink channel, may include at least two of the following:

[0182] Waveform of Orthogonal Frequency Division Multiplexing (OFDM) technology;

[0183] Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform;

[0184] Orthogonal Time Frequency Space (OTFS) waveform.

[0185] In one example, the communication system supports downlink waveforms of OTFS and DFT-s-OFDM, which can be denoted as OTFS&DFT-s-OFDM. In another example, the communication system supports downlink waveforms of OTFS and OFDM, which can be denoted as OTFS&OFDM. In yet another example, the communication system supports downlink waveforms of OFDM and DFT-s-OFDM, which can be denoted as OFDM&DFT-s-OFDM.

[0186] Optionally, the OFDM waveform may refer to the CP-OFDM waveform.

[0187] Alternatively, different waveforms have different characteristics and can be applied to communication scenarios with different requirements.

[0188] For example, different subcarrier signals have relatively high peak values ​​after undergoing Inverse Fast Fourier Transform (IFFT) operations. Compared to single-carrier systems, multi-carrier systems have a very high PAPR, thus the PAPR of DFT-S-OFDM waveforms, i.e., single-carrier OFDM, is lower than that of CP-OFDM waveforms.

[0189] For example, DFT-s-OFDM waveforms outperform OFDM waveforms in terms of Error Vector Magnitude (EVM) and Block Error Rate (BLER). However, in multi-beam designs, due to the superposition effect between beams, the performance of DFT-sOFDM waveforms gradually approaches that of OFDM waveforms. The selected waveform can be chosen by comprehensively considering the advantages and disadvantages of both OFDM and DFT-s-OFDM waveforms based on the payload design scheme.

[0190] For example, wireless channels may have characteristics that are detrimental to communication, such as severe delay, Doppler spread, and limited path lifetime. These characteristics may degrade the performance of OFDM modulation. OTFS waveforms can modulate data in the Delay Doppler domain rather than the traditional Time Frequency (TF) domain, such as encoding information in typical high-mobility environments, to combat Doppler shift in multipath propagation channels. It has the advantages of strong Doppler resistance and delay resistance for highly dynamic and complex environments.

[0191] Optionally, as shown in Figure 2b, the DFT-s-OFDM waveform enables the transform precoding function or operation relative to the OFDM waveform.

[0192] Optionally, as shown in Figure 2c, compared to the OFDM waveform, OTFS can be a traditional OFDM system with the addition of a pre-processing module and a post-processing module. The pre-processing module (Precoder) is an Inverse Symmetric Finite Fourier Transform (ISFFT), and the post-processing module (Decoder) is a Symmetric Finite Fourier Transform (SFFT). It also includes an OFDM modulator, a channel function module, an OFDM demodulator, and, in the figure, an outer dashed box representing the Delay-Doppler Domain, an inner dashed box representing the Time-Frequency Domain, and N OFDM symbols.

[0193] In some embodiments, terminal 101 may report some or all of the supported downlink waveforms in the third information.

[0194] In some embodiments, the third information includes waveforms supported by terminal 101 in addition to the default waveform.

[0195] Optionally, the default waveform is a waveform that is supported by default in the communication system. For example, network device 102 can transmit downlink information based on the default waveform, and terminal 101 can support demodulation of the downlink information of the default waveform.

[0196] Optionally, the default waveform can be defined by the protocol or configured by the network device 102. For example, in OFDM, DFT-s-OFDM, and OTFS, the default waveform is defined or configured as an OFDM waveform.

[0197] Optionally, terminal 101 may report only waveforms other than the default waveform in the third information to save signaling resources.

[0198] In some embodiments, the third information of terminal 101 may also include other capabilities, such as supported uplink waveforms. Alternatively, terminal 101 may support uplink waveforms defined by protocol or network configuration, in which case terminal 101 does not need to report supported uplink waveforms.

[0199] Optionally, the uplink waveform of terminal 101 can support OFDM waveform and DFT-S-OFDM waveform. The DFT encoding module (Transform precoding) in the uplink signal transmitter can be enabled or disabled. When enabled, the uplink waveform is DFT-S-OFDM; when disabled, the uplink waveform is OFDM.

[0200] Optionally, for uplink data channels such as the Physical Uplink Shared channel (PUSCH), terminal 101 can determine whether DFT coding is used, i.e., whether to use DFT-s-OFDM waveforms, based on the configuration. For uplink control channels, such as Physical Uplink Control Channel (PUCCH) format 0, 1, or 2, terminal 101 can use OFDM waveforms; for PUCCH format 3 or 4, terminal 101 can use DFT-s-OFDM waveforms; the Random Access Channel (RACH) is essentially a sequence and does not require DFT.

[0201] Optionally, for uplink reference signals: such as the demodulation reference signal DMRS for PUSCH, a transform precoding step is not required. The sequence generation method of DMRS can be determined based on whether the data portion of PUSCH is a DFT-s-OFDM waveform or an OFDM waveform (DMRS for PUSCH follows PUSCH). Similarly, for DMRS for PUCCH, a transform precoding step is not required. The sequence generation method of DMRS can be determined based on whether the control portion of PUCCH is a DFT-s-OFDM waveform or an OFDM waveform (DMRS for PUCCH follows PUCCH). For example, the phase tracking reference signal PTRS determines its sequence generation method based on a separate RRC configuration, without DFT, but has different sequence generation methods depending on the configuration. The sounding reference signal (SRS) uses an OFDM waveform.

[0202] Optionally, for the uplink waveforms supported by terminal 101, whether to enable them can be determined based on the following configuration of network device 102:

[0203] For example, the following field in the ConfiguredGrantConfig Information Element (IE) is used to enable or disable transform precoding for type 1 and type 2: transformPrecoder ENUMERATED{enabled,disabled}. If this field does not exist, terminal 101 enables or disables transform precoding based on the msg3-transformPrecoder field of RACH-ConfigCommon included in the Bandwidth Part (BWP) configuration (not included in the additional RACH-ConfigList).

[0204] For example, the following field in the MsgA-PUSCH-Config information element is used to enable or disable transform precoding: msgA-TransformPrecoder-r16 ENUMERATED{enabled,disabled}.

[0205] For example, the following fields in the PTRS-UplinkConfig information element are used to enable or disable transform precoder: transformPrecoderDisabled, transformPrecoderEnabled.

[0206] For example, the following field in the PUSCH-Config information element is used to enable or disable transform precoder: transformPrecoder

[0207] ENUMERATED{enabled,disabled}.

[0208] For example, the following field in the RACH-ConfigCommon information element is used to enable or disable transform precoder: msg3-transformPrecoder.

[0209] Enabling transform precoding indicates that terminal 101 can use DFT-s-OFDM waveforms, while disabling transform precoding indicates that terminal 101 can use OFDM waveforms.

[0210] Optionally, when applying transform precoding on the PUSCH, the behavior of terminal 101 can be based on the UE procedure defined in the protocol.

[0211] For example, for a PUSCH scheduled by random access response (RAR) uplink (UL) authorization, or a PUSCH scheduled by fallback RAR UL authorization, or a PUSCH scheduled by DC1 format 0_0 with scrambled cyclic redundancy check (CRC) using Temporary Cell Radio Network Temporary Identity (TC-RNTI), terminal 101 can enable or disable transform precoding according to the parameter msg 3-transformprecoder configured by the higher layer.

[0212] For example, for MsgA PUSCH, terminal 101 can enable or disable transform precoding based on the higher-layer configuration parameter msgA-TransformPrecocer. If the higher-layer parameter msgA-TransformPrecoder is not configured, terminal 101 can enable or disable transform precoding based on the higher-layer configuration parameter msg3-TransformPrecoder.

[0213] For example, a PUSCH that meets the following conditions: PDCCH scheduling with CRC scrambled by Configured Scheduling RNTI (CS-RNTI) and New Data Indicator (NDI) = 1; or, scrambling with Cell RNTI (C-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), or Semi-Persistent Channel-State-Information RNTI (SP-CSI-RNTI).

[0214] If the DCI with scheduling grant is received in DC1 format 0_0, then for this PUSCH transmission, terminal 101 can enable or disable transform precoding according to the parameter msg3-transformPrecocder configured by the higher layer.

[0215] If no DCI with scheduling authority is received using DCl format 0_0:

[0216] If terminal 101 has configured the transformPrecocer parameter in the higher-level parameter pusch-Config, terminal 101 can enable or disable transform precoding according to the parameter for this PUSCH transmission.

[0217] If terminal 101 does not configure the transformPrecoder parameter in the higher-layer parameter pusch-Config, then for this PUSCH transmission, terminal 101 can enable or disable transform precoding according to the higher-layer configuration parameter msg3-transformPrecocder.

[0218] For example, for a PUSCH transport with a configured grant:

[0219] If terminal 101 has configured the transformPrecocer parameter in the higher-level parameter configuredGrantConfig, terminal 101 can enable or disable transform precoding for this PUSCH transmission according to the parameter.

[0220] If the UE does not configure the transformPrecocer parameter in the higher-layer parameter configuredGrantConfig, for this PUSCH transmission, the terminal 101 can enable or disable transform precoding according to the parameter msg3-transformPrecocder configured in the higher-layer configuration.

[0221] In some embodiments, network device 102 may receive the third information and may consider the third information to select the applied downlink waveform.

[0222] In some embodiments, step S2101 can be omitted. For example, by default, terminal 101 can support the above-mentioned multiple downlink waveforms, so terminal 101 does not need to report the supported downlink waveforms.

[0223] Even if step S2101 is omitted, the description of the relevant implementation in step S2101 can still be used as a reference or application for the following embodiments.

[0224] In step S2102, network device 102 sends first information to terminal 101.

[0225] In some embodiments, the first information is used to indicate that the waveform applied or used by the downlink channel is a first waveform. The first waveform is one of at least two waveforms supported by the downlink channel. The descriptions of the at least two waveforms and the different waveforms can be found in the implementation of step S2101. For example, the at least two waveforms may include two or three of the following: OFDM waveform, DFT-s-OFDM waveform, and OTFS waveform, as described using OFDM & DFT-s-OFDM as an example.

[0226] Optionally, the first information can be instruction information, such as denoted as the first instruction information.

[0227] In some embodiments, the downlink channel includes at least one of the following:

[0228] Physical Downlink Control Channel (PDCCH);

[0229] Physical Downlink Shared Channel (PDSCH);

[0230] Physical Broadcast Channel (PBCH).

[0231] In some embodiments, network device 102 may transmit the first information via Radio Resource Control (RRC) signaling. For example, network device 102 may use RRC signaling to indicate the waveform used by the downlink channel.

[0232] Optionally, network device 102 uses the first waveform of the first information PDCCH or PDSCH.

[0233] In the first example, the PDSCH includes the DCI dynamically scheduled PDSCH. In this example, network device 102 configures the waveform used by the DCI scheduled or dynamically scheduled PDSCH via RRC signaling.

[0234] In the second example, PDSCH includes at least one of the following:

[0235] The first PDSCH used to transmit message B during the two-step random access process;

[0236] The second PDSCH used to transmit message 2 during the four-step random access process;

[0237] The third PDSCH used to transmit message 4 during the four-step random access process.

[0238] Among them, message B can be denoted as MSGB, message 2 as MSG2, and message 4 as MSG4. The first PDSCH can be denoted as MSGB PDSCH, the second PDSCH as MSG2 PDSCH, and the third PDSCH as MSG4 PDSCH.

[0239] In this example, network device 102 can configure the waveform used by the PDSCH scheduled by DCI during random access via RRC signaling. For example, network device 102 can configure the waveform used by the PDSCH (i.e., MSG2 PDSCH) of transmission MSG2 scheduled by DCI and / or the PDSCH (i.e., MSG4 PDSCH) of transmission MSG2 scheduled by DCI via RRC signaling.

[0240] In this example, when the PDSCH includes the second PDSCH but not the first PDSCH, for example, when network device 102 is not configured or indicates the waveform used by MSGB PDSCH, the waveform applied by the first PDSCH is the same as the waveform applied by the second PDSCH, that is, the waveform indication or waveform configuration refers to (follow) MSG2 PDSCH.

[0241] In this example, when the PDSCH includes the first PDSCH or the second PDSCH, but does not include the third PDSCH, for example, when network device 102 does not configure or indicate the waveform used by MSG4 PDSCH, the waveform used by the third PDSCH is the same as the waveform used by the first PDSCH or the second PDSCH, such as referring to the waveform indication or waveform configuration of MSG2 PDSCH.

[0242] In the third example, the PDSCH is a semi-persistent scheduled PDSCH, such as a semi-persistent scheduled PDSCH configured for RRC. In this example, network device 102 indicates or configures the waveform used by the semi-persistently scheduled PDSCH via RRC.

[0243] The RRC configuration uses a semi-persistent scheduled PDSCH to describe

[0244] In the fourth example, network device 102 can indicate or configure the waveform used by the PDCCH via RRC signaling. Different PDCCHs satisfy at least one of the following:

[0245] Different PDCCH formats support or apply different waveforms;

[0246] PDCCHs that occupy different numbers of resource units support or apply different waveforms. For example, PDCCHs using different aggregation levels (AL) occupy different numbers of resource units, and different waveforms can be configured for these PDCCHs.

[0247] The PDCCH used to transmit downlink control information (DCI) in different formats supports or applies different waveforms.

[0248] The PDCCH used to transmit different RNTI scrambled DCIs supports or applies different waveforms. For example, for a specific RNTI scrambled DCI format, network device 102 can indicate the corresponding waveform.

[0249] Optionally, different PDCCH formats can use the same waveform; or, some PDCCH formats can use the same waveform, while the remaining PDCCH formats can use different waveforms. Alternatively, different PDSCH formats can use the same waveform.

[0250] In some embodiments, the first information sent by the network device 102 via RRC signaling can indicate the waveform in different ways.

[0251] In one example, the first information includes a first information field, which is used to indicate the name or index of the first waveform. In this example, the name or index of the waveform can be directly indicated through the first information field. For example, using the option{OFDM, DFT-s-OFDM} method, the network device 102 can indicate one of them as the waveform to be used or applied.

[0252] In another example, the first information includes a second information field, which indicates whether a second waveform among multiple waveforms is enabled; wherein, when the second waveform is enabled, the first waveform is the second waveform; when the second waveform is not enabled, the first waveform is the default waveform.

[0253] In this example, the second information field can indicate whether a particular waveform (such as the second waveform in this embodiment) is enabled or activated among the various waveforms supported by the communication system. The default waveform can be based on protocol definitions or network device 102 configuration, such as an OFDM waveform. For example, if the communication system supports OFDM, DFT-s-OFDM, and OTFS waveforms, the second information field can indicate whether DFT-s-OFDM is enabled. If enabled, the downlink channel uses the DFT-s-OFDM waveform; if not enabled, the downlink channel uses the OFDM waveform.

[0254] In another example, the first information includes a third information field, which is used to indicate whether the transformation function corresponding to the waveform is enabled; wherein, when the transformation function is enabled, the first waveform is the waveform that needs to be transformed in the encoding and decoding process; when the transformation function is not enabled, the first waveform is the default waveform.

[0255] In this example, the function indicating whether the waveform to be applied is enabled is shown.

[0256] For example, the difference between OFDM and DFT-s-OFDM is that DFT-s-OFDM requires inverse-transformer precoding during reception. If the second information field indicates that inverse-transformer precoding is enabled, it means that the waveform used by the downlink channel is DFT-s-OFDM; if this function is not enabled or the corresponding field does not appear, it means that the downlink uses the default waveform such as OFDM.

[0257] For example, the difference between OFDM and OTFS is that OTFS requires a Symmetric Finite Fourier Transform during reception. If the second information field indicates that the Symmetric Finite Fourier Transform is enabled, it means that the waveform used in the downlink channel is OTFS; if this function is not enabled or the corresponding field does not appear, it means that the downlink uses the default waveform such as OFDM.

[0258] In some examples, the first information may include multiple items such as: a first information field, a second information field, and a third information field.

[0259] In some examples, if the first information field, the second information field, and the third information field do not appear in the first information, the downlink channel can use the default waveform or the waveform defined by the protocol by default.

[0260] In some embodiments, step S2102 can be omitted. For example, the first waveform of the downlink channel application is determined by a protocol definition. The first waveforms of different downlink channel applications can be the same or different.

[0261] Optionally, the first waveform used by PDCCH or PBCH is defined by a protocol.

[0262] In one example, the waveforms that can be used for different PDCCHs can be defined based on the protocol. For instance, for a PDCCH corresponding to a specific DCI format, a waveform defined by the protocol can be used. Or, for a PDCCH corresponding to a specific RNTI-scrambled DCI, a waveform defined by the protocol can be used.

[0263] In another example, the PBCH can use protocol-defined waveforms. For instance, downlink channels during the initial access process, such as msg2 PDSCH, msg4 PDSCH, or the PDCCH containing the DCI scrambled with RA-RNTI, all use the same predefined waveforms.

[0264] In some embodiments, terminal 101 may receive the first information described above to know the waveform used by the downlink channel.

[0265] In step S2103, network device 102 sends second information to terminal 101.

[0266] In some embodiments, the second information is used to indicate the sequence generation method and / or resource mapping method of the downlink reference signal.

[0267] Optionally, network device 102 can send a second message via RRC signaling.

[0268] Optionally, the second information can be instruction information, such as denoted as the second instruction information.

[0269] Optionally, the first information and the second information can be sent via the same RRC signaling or via different RRC signaling.

[0270] In some embodiments, this step can be performed when the downlink information is a downlink reference signal.

[0271] Optionally, the downlink reference signal includes at least one of the following:

[0272] DMRS (DMRS for PDSCH) is a demodulation reference signal used for PDSCH.

[0273] DMRS for PDCCH;

[0274] Phase tracking reference signal PTRS;

[0275] Tracking reference signal TRS;

[0276] Channel State Information Reference Signal (CSI-RS);

[0277] Master synchronization signal PSS;

[0278] Auxiliary synchronization signal SSS;

[0279] Positioning reference signal PRS.

[0280] Optionally, network device 102 configures or indicates the sequence generation method and / or resource mapping method of any downlink reference signal via RRC signaling. For example, PTRS or TRS determines its corresponding sequence generation method and / or resource mapping method through RRC configuration.

[0281] In some embodiments, step S2102 can be omitted, for example, the method for generating the downlink reference signal sequence and / or the resource mapping method are determined according to the protocol definition.

[0282] For example, CSI-RS determines the sequence generation method and / or resource mapping method through predefined protocol methods. Alternatively, SSS and / or PSS determine the sequence generation method and / or resource mapping method through predefined protocol methods. Or, PRS determines the sequence generation method and / or resource mapping method through predefined protocol methods.

[0283] In some embodiments, the sequence generation method and / or resource mapping method of the downlink reference signal are related to the waveform of the downlink channel application.

[0284] In some embodiments, at least one of the following steps for generating downlink reference signals, sequence generation methods, and resource mapping methods may be defined by the protocol.

[0285] In some embodiments, the sequence generation method and / or resource mapping method of the downlink reference signal used for the downlink channel are different when the waveform of the downlink channel application is different.

[0286] For example, for DMRS used in PDSCH, different sequence generation methods and / or resource mapping methods are used when different waveforms are used in PDSCH. Similarly, for DMRS used in PDCCH, different corresponding sequence generation methods and / or resource mapping methods are used when different waveforms are used in PDCCH.

[0287] In some embodiments, terminal 101 receives second information, or determines the sequence generation method and / or resource mapping method of downlink reference signals based on protocol definitions.

[0288] In step S2104, network device 102 sends downlink information to terminal 101.

[0289] In some embodiments, network device 102 transmits downlink information in a downlink channel. The waveform used in the downlink channel can be defined by a protocol or indicated by first information. For example, the waveform used in the downlink channel is a first waveform among a variety of supported waveforms.

[0290] In some embodiments, terminal 101 may learn the waveform of the downlink channel application based on protocol definitions or first information. For example, terminal 101 may determine the demodulation method of the downlink channel based on the indication of the downlink channel by network device 102.

[0291] Optionally, terminal 101 receives downlink information and determines demodulation steps. During the downlink information reception process, demodulation processing can be performed based on the waveform used by the downlink channel. For example, if the downlink channel uses a DFT-s-OFDM waveform, terminal 101 needs to perform an inverse DFT transform during downlink information reception. If the downlink channel uses an OFDM waveform, terminal 101 does not need to perform an inverse DFT transform when receiving downlink information.

[0292] In some embodiments, when the downlink information is a downlink reference signal, the terminal 101 may determine the demodulation method of the downlink reference signal based on the second information or protocol definition, such as determining the sequence generation method and / or resource mapping method of the downlink reference signal, and then perform demodulation processing on the downlink reference signal based on the corresponding sequence generation method and / or resource mapping method.

[0293] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", and "field" can be used interchangeably.

[0294] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0295] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0296] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0297] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

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

[0299] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0300] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0301] 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 receiver to respond to the sent content.

[0302] The method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104.

[0303] In some embodiments, step S2101 is optional and can be replaced by one or more steps in different embodiments.

[0304] In some embodiments, step S2102 is optional and can be replaced by one or more steps in different embodiments.

[0305] In some embodiments, step S2103 is optional and can be replaced by one or more steps in different embodiments.

[0306] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2a.

[0307] Figure 3a is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3a, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method comprising:

[0308] Step S3101: Send the third message.

[0309] In some embodiments, the implementation of step S3101 can be found in the implementation of step S2101 in FIG2a, and will not be repeated here.

[0310] Step S3102: Receive the first information.

[0311] In some embodiments, the implementation of step S3102 can be found in the implementation of step S2102 in FIG2a, and will not be repeated here.

[0312] Step S3103: Receive the second information.

[0313] In some embodiments, the implementation of step S3103 can be found in the implementation of step S2103 in FIG2a, and will not be repeated here.

[0314] Step S3104: Receive downlink information.

[0315] In some embodiments, the implementation of step S3104 can be found in the implementation of step S2104 in FIG2a, and will not be repeated here.

[0316] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3a.

[0317] Figure 3b is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3b, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0318] Step S3201: Receive the first information.

[0319] In some embodiments, the implementation of step S3201 can be referred to the implementation of step S2102 in FIG2a, and will not be repeated here.

[0320] Step S3202: Receive downlink information.

[0321] In some embodiments, the implementation of step S3202 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0322] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3b.

[0323] Figure 3c is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3c, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0324] Step S3301: Receive the second information.

[0325] In some embodiments, the implementation of step S3301 can be referred to the implementation of step S2103 in FIG2a, and will not be repeated here.

[0326] Step S3302: Receive downlink information.

[0327] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0328] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG3c.

[0329] Figure 3d is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3d, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method comprising:

[0330] Step S3401: Receive downlink information.

[0331] In some embodiments, the implementation of step S3401 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0332] In some embodiments, other alternative implementations may be described before or after the specification corresponding to Figure 3d.

[0333] Figure 4a is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4a, this embodiment of the disclosure relates to a communication method executed by a network device 102, the method comprising:

[0334] Step S4101: Receive third information.

[0335] In some embodiments, the implementation of step S4101 can be found in the implementation of step S2101 in FIG2a, and will not be repeated here.

[0336] Step S4102: Send the first message.

[0337] In some embodiments, the implementation of step S4102 can be found in the implementation of step S2102 in FIG2a, and will not be repeated here.

[0338] Step S4103: Send the second message.

[0339] In some embodiments, the implementation of step S4103 can be found in the implementation of step S2103 in FIG2a, and will not be repeated here.

[0340] Step S4104: Send downlink information.

[0341] In some embodiments, the implementation of step S4104 can be found in the implementation of step S2104 in FIG2a, and will not be repeated here.

[0342] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4a.

[0343] Figure 4b is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4b, this embodiment of the disclosure relates to a communication method executed by a network device 102, the method comprising:

[0344] Step S4201: Send the first message.

[0345] In some embodiments, the implementation of step S4201 can be found in the implementation of step S2102 in FIG2a, and will not be repeated here.

[0346] Step S4202: Send downlink information.

[0347] In some embodiments, the implementation of step S4202 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0348] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4b.

[0349] Figure 4c is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4c, this embodiment of the disclosure relates to a communication method executed by a network device 102, the method comprising:

[0350] Step S4301: Send the second message.

[0351] In some embodiments, the implementation of step S4301 can be referred to the implementation of step S2103 in FIG2a, and will not be repeated here.

[0352] Step S4302: Send downlink information.

[0353] In some embodiments, the implementation of step S4302 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0354] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG4c.

[0355] Figure 4d is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4d, this embodiment of the disclosure relates to a communication method executed by a network device 102, the method comprising:

[0356] Step S4401: Send downlink information.

[0357] In some embodiments, the implementation of step S3401 can be referred to the implementation of step S2104 in FIG2a, and will not be repeated here.

[0358] In some embodiments, other alternative implementations may be described before or after the specification corresponding to Figure 4d.

[0359] This disclosure applies to 6G downlink waveform application scenarios. For example, considering the integrated design of TN and NTN networks, the system needs to support multiple downlink waveforms simultaneously, such as OTFS & DFT-s-OFDM, or OFDM & DFT-s-OFDM. Different waveforms have different generation and decoding methods. This disclosure can indicate the waveform used for downlink to the UE in a 6G network so that the UE can perform corresponding demodulation. This disclosure provides a waveform indication method for downlink signals or / and channels, so that the UE can accurately demodulate downlink signals / channels when multiple downlink waveforms coexist in a 6G network. To facilitate understanding of this disclosure, some examples are listed below:

[0360] Example 1:

[0361] The communication system can simultaneously support more than one waveform for downlink channel / signal transmission.

[0362] In one embodiment, the system supports OTFS & DFT-s-OFDM.

[0363] In one embodiment, the system supports OFDM & DFT-s-OFDM, and OFDM & DFT-s-OFDM will be used as an example below.

[0364] In one embodiment, the system supports OTFS & OFDM.

[0365] Example 2:

[0366] Based on any of the above examples, the base station indicates the waveform used by the UE's downlink channel through downlink signaling.

[0367] In one embodiment, the base station configures the waveform used by the downlink channel (PDCCH, PDSCH) via RRC signaling.

[0368] Optionally, the base station configures the waveform used by the PDSCH for DCI scheduling / dynamic scheduling via RRC.

[0369] Optionally, the waveforms of msg2 PDSCH and / or msg4 PDSCH scheduled by DCI during random access are also configured by RRC. In one embodiment, if msgB PDSCH does not indicate a waveform, then the waveform configuration of msg2 PDSCH is followed. In another embodiment, if msg4 PDSCH does not indicate a waveform, then the waveform of msg2 PDSCH is followed.

[0370] Optionally, the base station configures the waveform used by the semi-static scheduling PDSCH via RRC.

[0371] In one embodiment, the base station configures the waveform used by the PDCCH via RRC:

[0372] Different DCI formats can have different waveforms;

[0373] PDCCHs that consume different numbers of resources (e.g., using different aggregation levels) can have different waveforms;

[0374] Different PDCCH formats can have different waveforms;

[0375] A DCI format with specific RNTI scrambling.

[0376] Example 3:

[0377] Based on any of the above examples, the base station instructs the UE on the sequence generation method and / or resource mapping method of the downlink reference signal through downlink signaling.

[0378] In one embodiment, the downlink reference signal determines the sequence generation method and / or resource mapping method based on the base station's configuration information:

[0379] DMRS for PDSCH: Different waveforms used in PDSCH have different corresponding sequence generation methods and / or resource mapping methods.

[0380] DMRS for PDCCH: Different waveforms used in PDCCH have different corresponding sequence generation methods and / or resource mapping methods.

[0381] PTRS and TRS determine their corresponding sequence generation methods and / or resource mapping methods through RRC configuration.

[0382] Example 4:

[0383] Based on any of the above examples, the waveform used in the downlink channel, the sequence generation method of the downlink reference signal, and / or the resource mapping method are determined through standard predefined methods. For example:

[0384] CSI-RS determines the sequence generation method and / or resource mapping method through a standard predefined approach;

[0385] SSS and PSS determine the sequence generation method and / or resource mapping method through standard predefined methods;

[0386] PRS determines the sequence generation method and / or resource mapping method through standard predefined methods;

[0387] PDCCH uses a standard predefined waveform for a specific DCI format, or a standard predefined waveform for a specific RNTI scrambled DCI.

[0388] PBCH uses a standard predefined waveform.

[0389] In one embodiment, the downlink channels during the initial access process use predefined waveforms, such as msg2 PDSCH, msg4 PDSCH, and the PDCCH containing the DCI scrambled with RA-RNTI.

[0390] Example 5:

[0391] Based on any of the above examples, the specific ways in which a base station indicates the waveform of a downlink signal / signal can include:

[0392] Method 1: Indicate the waveform name, for example, using option {OFDM, DFT-s-OFDM}, the base station selects one to indicate;

[0393] Method 2: Indicate whether one of the waveforms is enabled; if disabled, the default waveform is used. For example, if the default waveform is OFDM, the base station indicates whether DFT-s-OFDM is enabled; if the corresponding field does not appear, the default is DFT-s-OFDM disabled.

[0394] Method 3: Indicate whether the function of the waveform to be given is enabled. For example, the difference between OFDM and DFT-s-OFDM is that DFT-s-OFDM requires DFT inverse transformation during reception. If the base station indicates that inverse-transformer precoding is enabled, it means that the downlink waveform is DFT-S-OFDM. Otherwise (disable, or the corresponding field does not appear), it means that it is OFDM.

[0395] Optionally, for method 3, it can be distinguished according to different waveforms, such as OFDM and OTFS, and Symmetric Finite Fourier Transform can be enabled.

[0396] Example 6:

[0397] Based on any of the above examples, for the downlink channel, unless otherwise specified or the field in Example 5 does not appear, the default waveform / standard predefined waveform will be used. That is, through standard predefined signal generation steps, standard predefined sequence generation methods, and resource mapping methods.

[0398] Example 7:

[0399] Based on any of the above examples, the UE determines the demodulation method for the downlink channel / signal according to the base station's indication of the downlink channel / signal. For the downlink channel, the UE determines the demodulation steps; for example, DFT-s-OFDM requires inverse DFT transformation during reception, while OFDM does not require inverse DFT transformation. For the downlink reference signal, the UE determines its sequence and mapping method.

[0400] Example 8:

[0401] Based on any of the above examples, the UE reports the supported downlink waveforms to the base station.

[0402] Optionally, the UE may not be required to report the supported downlink waveforms; in this case, the UE supports multiple waveforms by default.

[0403] In one embodiment, the UE reports waveforms other than those that are required to be supported by default.

[0404] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0405] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0406] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 configuring the hardware circuit 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. Furthermore, 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), or a Deep Learning Processing Unit (DPU).

[0407] Figure 5a is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 5a, the terminal 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to receive downlink information sent by a network device, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

[0408] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be described in detail here. Optionally, the processing module 5102 is used to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be described in detail here.

[0409] Figure 5b is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 5b, the network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to send downlink information to the terminal, wherein the downlink channel used to transmit the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel.

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

[0411] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0412] Figure 6a is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0413] 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, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0414] 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 method, and the processor 6101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0415] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional 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 can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

[0416] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this 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 a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0417] Figure 6b is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6b, but it is not limited thereto.

[0418] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

[0420] 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 interaction 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.

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

[0422] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0423] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0424] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0425] The downlink channel can support multiple waveforms, and the terminal can receive downlink information transmitted by the network device based on a specific waveform. This allows the appropriate waveform to be applied based on communication needs in different scenarios, thereby improving communication efficiency in different scenarios.

Claims

A communication method performed by a terminal, the method comprising: receiving downlink information transmitted by a network device, wherein a first waveform is applied to a downlink channel used for transmitting the downlink information, the first waveform being one of at least two waveforms supported by the downlink channel. The method of claim 1, wherein The first waveform applied to the downlink channel is determined in a manner defined by a protocol. The method of claim 1, wherein, The method further comprises: receiving first information transmitted by the network device, the first information being used to indicate that a waveform applied to the downlink channel is the first waveform. The method of claim 3, wherein The first information comprises a first information field used to indicate a name or an index of the first waveform. The method of claim 3 or 4, wherein The first information comprises a second information field used to indicate whether a second waveform of the at least two waveforms is enabled; wherein the first waveform is the second waveform when the second waveform is enabled; and the first waveform is a default waveform when the second waveform is not enabled. The method of any one of claims 3 to 5, wherein The first information comprises a third information field used to indicate whether a transform function corresponding to a waveform is enabled; wherein the first waveform is a waveform for which the transform function needs to be performed in a codec process when the transform function is enabled; and the first waveform is a default waveform when the transform function is not enabled. The method of any one of claims 2 to 6, wherein, The downlink channel comprises: a physical downlink control channel (PDCCH); a physical downlink shared channel (PDSCH); a physical broadcast channel (PBCH). The method of claim 7, wherein waveforms supported or applied by PDCCHs of different formats are different; waveforms supported or applied by PDCCHs occupying different numbers of resource units are different; waveforms supported or applied by PDCCHs used for transmitting different formats of downlink control information (DCI) are different; waveforms supported or applied by PDCCHs used for transmitting DCI scrambled by different radio network temporary identifiers (RNTIs) are different. The method of claim 7, wherein, The PDSCH comprises: The method of claim 7, wherein, a first PDSCH used for transmitting a message B in a two-step random access procedure. The PDSCH comprises at least one of: a first PDSCH used for transmitting a message B in a two-step random access procedure; a second PDSCH used for transmitting a message 2 in a four-step random access procedure; a third PDSCH used for transmitting a message 4 in a four-step random access procedure. The method of claim 10, wherein when the PDSCH comprises the second PDSCH, a waveform applied to the first PDSCH is the same as a waveform applied to the second PDSCH. The method of claim 10, wherein The method of claim 7, wherein, when the PDSCH comprises the first PDSCH or the second PDSCH, a waveform applied to the third PDSCH is the same as a waveform applied to the first PDSCH or the second PDSCH. The PDSCH is a semi-statically scheduled PDSCH. The method of any one of claims 1 to 13, wherein When the downlink information is a downlink reference signal, a sequence generation method and / or a resource mapping manner of the downlink reference signal is determined according to a protocol defined manner. The method of any one of claims 1 to 13, wherein, When the downlink information is a downlink reference signal, the method further comprises: receiving second information sent by the network device, the second information being used for indicating a sequence generation manner and / or a resource mapping manner of the downlink reference signal. The method of claim 14 or 15, wherein, When waveforms applied to the downlink channels are different, the sequence generation manner and / or the resource mapping manner of the downlink reference signal for the downlink channels are different. The method of any one of claims 14 to 16, wherein, The downlink reference signal comprises at least one of: a demodulation reference signal (DMRS) for a PDSCH; a DMRS for a PDCCH; a phase tracking reference signal (PTRS); a tracking reference signal (TRS); a channel state information reference signal (CSI-RS); a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a positioning reference signal (PRS). The method of any one of claims 1 to 17, wherein, The method further comprises: sending, to the network device, third information, the third information comprising a waveform supported by the terminal for demodulation of a downlink channel. The method of claim 18, wherein, The third information comprises a waveform supported by the terminal in addition to a default waveform. The method of any one of claims 1 to 19, wherein, The at least two waveforms are at least two of: an orthogonal frequency division multiplexing (OFDM) waveform; a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) waveform; an orthogonal time frequency space (OTFS) waveform. A communication method performed by a network device, the method comprising: sending, to a terminal, downlink information, wherein a downlink channel used for transmission of the downlink information applies a first waveform, the first waveform being one of at least two waveforms supported by the downlink channel. The method of claim 21, wherein The first waveform applied to the downlink channel is determined by a protocol defined manner. The method further comprises: The method of claim 21, wherein, sending, to the terminal, first information, the first information being used for indicating that a waveform applied to the downlink channel is the first waveform. The method of claim 23, wherein The first information comprises a first information field, the first information field being used for indicating a name or an index of the first waveform. The method of claim 23 or 24, wherein The first information comprises a second information field, the second information field being used for indicating whether a second waveform of the at least two waveforms is enabled; wherein, when the second waveform is enabled, the first waveform is the second waveform; and when the second waveform is not enabled, the first waveform is a default waveform. The method of any one of claims 23 to 25, wherein The first information comprises a third information field, the third information field being used for indicating whether a transform function corresponding to a waveform is enabled; wherein, when the transform function is enabled, the first waveform is a waveform for which the transform function needs to be performed in codec processing; and when the transform function is not enabled, the first waveform is a default waveform. The downlink channel comprises: The method of any one of claims 22 to 26, wherein, a physical downlink control channel (PDCCH); a physical downlink shared channel (PDSCH); a physical broadcast channel (PBCH). The method of claim 27, wherein ​ Different waveforms are supported or applied for PDCCHs of different formats; Different waveforms are supported or applied for PDCCHs occupying different numbers of resource units; Different waveforms are supported or applied for PDCCHs used for transmitting downlink control information (DCI) of different formats; Different waveforms are supported or applied for PDCCHs used for transmitting DCI scrambled by different radio network temporary identifiers (RNTIs). The method of claim 27, wherein, The PDSCH includes a PDSCH dynamically scheduled by DCI. The method of claim 27, wherein, The PDSCH includes at least one of the following: a first PDSCH used for transmitting a message B in a two-step random access procedure; a second PDSCH used for transmitting a message 2 in a four-step random access procedure; a third PDSCH used for transmitting a message 4 in the four-step random access procedure. The method of claim 30, wherein when the PDSCH includes the second PDSCH, a waveform applied to the first PDSCH is the same as a waveform applied to the second PDSCH. The method of claim 30, wherein when the PDSCH includes the first PDSCH or the second PDSCH, a waveform applied to the third PDSCH is the same as a waveform applied to the first PDSCH or the second PDSCH. The PDSCH is a semi-statically scheduled PDSCH. The method of claim 27, wherein, The method of any one of claims 21 to 33, wherein when the downlink information is a downlink reference signal, a sequence generation method and / or a resource mapping manner of the downlink reference signal are determined according to a protocol-defined manner. The method of any one of claims 21 to 33, wherein The method of any one of claims 21 to 33, wherein, when the downlink information is a downlink reference signal, the method further includes: sending, to the terminal, second information used for indicating a sequence generation method and / or a resource mapping manner of the downlink reference signal. The method of claim 34 or 35, wherein when waveforms applied to the downlink channels are different, the sequence generation method and / or the resource mapping manner of the downlink reference signal for the downlink channels are different. The method of any one of claims 34 to 36, wherein, The downlink reference signal includes at least one of the following: a demodulation reference signal (DMRS) for a PDSCH; a DMRS for a PDCCH; a phase tracking reference signal (PTRS); a tracking reference signal (TRS); a channel state information reference signal (CSI-RS); a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a positioning reference signal (PRS). The method of any one of claims 21 to 37, wherein, The method further includes: receiving third information sent by the terminal, the third information including waveforms supported by the terminal for demodulation of a downlink channel. The method of claim 38, wherein, The third information includes waveforms supported by the terminal in addition to a default waveform. The method of any one of claims 21 to 39, wherein, The at least two waveforms are at least two of the following: an orthogonal frequency division multiplexing (OFDM) waveform; a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) waveform; an orthogonal time frequency space (OTFS) waveform. A terminal includes: a transceiver configured to receive downlink information sent by a network device, wherein a downlink channel used for transmitting the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel. A communication device includes: The transceiver is configured to transmit downlink information to the terminal, wherein a downlink channel used for transmitting the downlink information applies a first waveform, and the first waveform is one of at least two waveforms supported by the downlink channel. A communication device comprising: one or more processors; wherein the communication device is configured to implement the method of any one of claims 1 to 20, or claims 21 to 40. A communication system comprising a terminal and a network device, wherein the terminal is configured to implement the method of any one of claims 1 to 20; the network device is configured to implement the method of any one of claims 21 to 40. A storage medium having stored instructions, wherein the instructions, when executed on a communication device, cause the communication device to perform the method of any one of claims 1 to 20, or claims 21 to 40. A program product, wherein the program product, when executed by a communication device, causes the communication device to perform the method of any one of claims 1 to 20, or claims 21 to 40.

Images