Processing method, communication device and storage medium

CN119174224APending Publication Date: 2024-12-20SHENZHEN TRANSSION HLDG CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380039140.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-02-17
Publication Date
2024-12-20

AI Technical Summary

Technical Problem

The existing downlink control information size determination method is based on RRC configuration, which results in inconsistent downlink control information sizes under different waveforms and increases the blind solution complexity of the terminal equipment.

Method used

The size of the downlink control information is determined through the preset policy to make it consistent in size under CP-OFDM and DFT-S-OFDM waveforms, including the maximum value or the sum of bit widths when transform precoding is disabled and enabled, and the terminal device is based on Different waveform information decodes each domain.

Benefits of technology

It reduces the blind decoding complexity of terminal equipment and ensures the decoding accuracy of downlink control information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119174224A_ABST
    Figure CN119174224A_ABST
Patent Text Reader

Abstract

Disclosed are a processing method, a communication device and a storage medium, the method comprising: a terminal device determining the size of downlink control information based on a preset policy, the downlink control information being used for indicating that uplink transmission uses different waveforms, and indicating that the sizes of the downlink control information of different waveforms are consistent. Therefore, the downlink control information for indicating the CP-OFDM and the downlink control information for indicating the DFT-S-OFDM can be ensured to be consistent in size, so that the terminal equipment does not need to blindly decode two DCI formats 01 / 02, and the blind decoding complexity of the terminal equipment is reduced. Furthermore, when the downlink control information indicating the CP-OFDM and the downlink control information indicating the DFT-S-OFDM are consistent in size, the effective bit number in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform, and the terminal equipment decodes each domain of the downlink control information according to different waveform information, so that the decoding accuracy can be ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Processing method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a processing method, communication equipment and storage medium. Background Art

[0002] In the existing protocol, the network device configures the terminal device to use the CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or the DFT-S-OFDM (Discrete Fourier Transform-Single Carrier-Orthogonal Frequency Division Multiplexing) waveform through the transform precoding parameter. For example, if transform precoding is enabled, the terminal device uses the DFT-S-OFDM waveform, otherwise the terminal device uses the CP-OFDM waveform. For different waveforms, the size of the downlink control information (DCI) field or whether the downlink control information field appears is different. In addition, the presence or absence of the "PTRS-DMRS association" and "DMRS sequence initialization" fields is based on the waveform. For example, when the terminal device uses the DFT-S-OFDM waveform, the above fields do not appear; when the terminal device uses the CP-OFDM waveform, the above fields contain 1 bit or 2 bits. In addition, the presence of the "Precoding information and number of layers" and "Antenna ports" fields is not waveform-dependent, but the size of these fields is waveform-dependent. Furthermore, different resource allocation types in the "FDRA" field can restrict waveform usage.

[0003] During the process of conceiving and implementing this application, the inventors discovered that the related art has at least the following problems: The existing method for determining the size of downlink control information is based on the RRC configuration. Using different waveforms can lead to inconsistent downlink control information sizes. As a result, terminal devices need to blindly decode two DCI formats, 0_1 and 0_2, which increases the complexity of the terminal device's blind decoding.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical Solutions

[0005] The present application provides a processing method, a communication device, and a storage medium that can reduce the complexity of blind decoding of a terminal device. Furthermore, when the size of the DCI indicating CP-OFDM and the downlink control information indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the downlink control information according to the different waveform information, and can also ensure decoding accuracy.

[0006] This application proposes a processing method that can be applied to a terminal device (such as a mobile phone), comprising the steps of:

[0007] S20: Determine the size of the downlink control information based on a preset strategy.

[0008] Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms.

[0009] Optionally, the downlink control information indicating different waveforms has the same size.

[0010] Optionally, the preset strategy includes at least one of the following:

[0011] The size of the downlink control information is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled;

[0012] The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each field when transform precoding is enabled;

[0013] The size of the downlink control information is set to the sum of the bit widths of each field contained in the downlink control information. Optionally, the bit width of each field is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0014] Optionally, the preset strategy includes at least one of the following:

[0015] If transform precoding is disabled, the downlink control information size is determined to be X1 according to the RRC configuration. If transform precoding is enabled, the downlink control information size is determined to be X2 according to the RRC configuration. The larger value of X1 or X2 is selected as the size of the downlink control information.

[0016] If transform precoding is disabled, the bit width of each field of the downlink control information is determined to be M1(i) according to the RRC configuration; if transform precoding is enabled, the bit width of each field is determined to be M2(i) according to the RRC configuration; the larger value of M1(i) and M2(i) is selected as the bit width of each field of the downlink control information, and the size of the downlink control information is determined according to the sum of the bit widths of the fields;

[0017] If transform precoding is disabled, the size of the downlink control information is determined to be X3 according to the RRC configuration;

[0018] If transform precoding is disabled, the bit width M1(i) of each field included in the downlink control information is determined according to the RRC configuration, and the sum of the bit widths M1(i) of each field included in the downlink control information is used as the size of the downlink control information.

[0019] Optionally, the downlink control information includes a dynamic waveform switching indication.

[0020] Optionally, the different waveforms include CP-OFDM and / or DFT-S-OFDM.

[0021] Optionally, the method further comprises the steps of:

[0022] S30: Decode the fields included in the downlink control information.

[0023] Optionally, step S30 includes at least one of the following:

[0024] If the field bit width N(i) corresponding to the indicated waveform is less than or equal to the field bit width M(i) set according to the preset policy, then use the N(i) least significant bits to decode the field, and / or, if greater, use the field bit width M(i) as the low M(i) bits of the field for decoding;

[0025] If the field bit width N(i) corresponding to the indicated waveform is less than or equal to the field bit width M(i) set according to the preset policy, then use the N(i) most significant bits to decode the field, and / or, if greater, use the field bit width M(i) as the high M(i) bits of the field for decoding;

[0026] If the domain bit width N(i) corresponding to the indicated waveform is smaller than the domain bit width M(i) set according to the preset policy, the M(i)-N(i) most significant bits are ignored;

[0027] If the domain bit width N(i) corresponding to the indicated waveform is smaller than the domain bit width M(i) set according to the preset policy, then M(i)-N(i) least significant bits are ignored;

[0028] If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset policy, the downlink control information is decoded using N least significant bits, and the remaining downlink control information bits are zero.

[0029] This application also proposes a processing method, which can be applied to a network device (such as a base station), comprising the steps of:

[0030] S10: Send downlink control information, and set or determine the size of the downlink control information based on a preset policy.

[0031] Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms.

[0032] Optionally, the downlink control information indicating different waveforms has the same size.

[0033] Optionally, the preset strategy includes at least one of the following:

[0034] The size of the downlink control information is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled;

[0035] The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each field when transform precoding is enabled;

[0036] The size of the downlink control information is set to the sum of the bit widths of each field contained in the downlink control information. Optionally, the bit width of each field is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0037] Optionally, the preset strategy includes at least one of the following:

[0038] When setting or determining the size of downlink control information, if transform precoding is disabled, the downlink control information size is determined as X1 according to the RRC configuration; if transform precoding is enabled, the downlink control information size is determined as X2 according to the RRC configuration, and the larger value of X1 and X2 is selected as the size of the downlink control information;

[0039] When determining the size of each field included in the downlink control information, if transform precoding is disabled, determining the bit width of each field included in the downlink control information as M1(i) according to the RRC configuration, and if transform precoding is enabled, determining the bit width of each field as M2(i) according to the RRC configuration, selecting the larger value of M1(i) and M2(i) as the bit width of each field of the downlink control information, and setting or determining the size of the downlink control information according to the sum of the bit widths of the fields;

[0040] If transform precoding is disabled, the terminal device determines the size of the downlink control information as X3 based on the RRC configuration;

[0041] If transform precoding is disabled, the terminal device determines the bit width M1(i) of each field included in the downlink control information according to the RRC configuration, and takes the sum of the bit width M1(i) of each field included in the downlink control information as the size of the downlink control information.

[0042] Optionally, the downlink control information includes a dynamic waveform switching indication.

[0043] Optionally, the different waveforms include CP-OFDM and / or DFT-S-OFDM.

[0044] Optionally, the method further comprises at least one of the following:

[0045] If the field bit width N(i) corresponding to the indicated waveform is less than or equal to the field bit width M(i) set according to the preset policy, the terminal device uses the N(i) least significant bits to decode the field, and / or, if greater, uses the field bit width M(i) as the low M(i) bits of the field for decoding;

[0046] If the field bit width N(i) corresponding to the indicated waveform is less than or equal to the field bit width M(i) set according to the preset policy, the terminal device uses the N(i) most significant bits to decode the field, and / or, if greater, uses the field bit width M(i) as the high M(i) bits of the field for decoding;

[0047] If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset strategy, the terminal device uses the N least significant bits to decode the downlink control information, and the remaining downlink control information bits are filled with zeros.

[0048] The present application also provides a processing device, comprising:

[0049] The determination module is used to determine the size of the downlink control information based on a preset strategy.

[0050] Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms.

[0051] Optionally, the downlink control information indicating different waveforms has the same size.

[0052] The present application also provides a processing device, comprising:

[0053] The sending module is used to send downlink control information, and the size of the downlink control information is set or determined based on a preset strategy. Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms, indicating that the size of the downlink control information of different waveforms is consistent.

[0054] The embodiment of the present application also provides a communication device, comprising: a memory, a processor, and a processing program stored on the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the processing method described in any of the above embodiments. The communication device mentioned in this application can be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified in the context.

[0055] An embodiment of the present application further provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processing method described in any of the above embodiments is implemented.

[0056] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on a preset policy, wherein the size of the downlink control information indicating different waveforms is consistent, thereby ensuring that the size of the downlink control information indicating CP-OFDM and the downlink control information indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the terminal device's blind decoding. Furthermore, when the size of the downlink control information indicating CP-OFDM and the downlink control information indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the downlink control information according to different waveform information, and can also ensure decoding accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0058] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0059] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0060] FIG3 is a schematic diagram of the hardware structure of the controller 140 involved in the processing method embodiment of the present application;

[0061] FIG4 is a schematic diagram of the hardware structure of the network node 150 involved in the processing method embodiment of the present application;

[0062] FIG5 is a schematic diagram of the interaction process between a terminal device and a network device according to the first embodiment of the processing method of the present application;

[0063] FIG6 is a schematic diagram of the interaction flow between the terminal device and the network device in the second embodiment of the processing method of the present application.

[0064] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0065] Implementation Methods of the Application

[0066] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0067] It should be noted that, in this document, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0068] It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if" as used herein may be interpreted as "when...", "when...", or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the described features, steps, operations, elements, components, items, types, and / or groups, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., used herein, may be interpreted as inclusive, or mean any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0069] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0070] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0071] It should be noted that in this article, step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the order. When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.

[0072] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0073] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0074] The communication equipment mentioned in this application can be a terminal device (such as a mobile terminal, specifically a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified in the context.

[0075] Optionally, the terminal device may be implemented in various forms. For example, the terminal device described in this application may include smart terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs and desktop computers.

[0076] The subsequent description will be made by taking a mobile terminal as an example. It will be understood by those skilled in the art that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminals.

[0077] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application. The mobile terminal 100 may include components such as an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0078] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0079] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and more. Furthermore, the RF unit 101 can communicate with the network and other devices via wireless communication. The above-mentioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution) and 5G, etc.

[0080] WiFi is a short-range wireless transmission technology. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0081] The audio output unit 103 can convert audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Furthermore, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.

[0082] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos captured by an image capture device (e.g., a camera) in video capture mode or image capture mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the GPU 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the RF unit 101 or the WiFi module 102. The microphone 1042 may receive sound (audio data) in operating modes such as a phone call mode, a recording mode, and a voice recognition mode, and may process such sound into audio data. In the phone call mode, the processed audio (voice) data may be converted into a format that can be transmitted to a mobile communication base station via the RF unit 101. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0083] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described here.

[0084] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0085] The user input unit 107 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any other suitable object or accessory on or near the touch panel 1071) and drive the corresponding connection device according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch direction and detects the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 110. It can also receive commands sent by the processor 110 and execute them. In addition, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0086] Optionally, the touch panel 1071 may overlay the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0087] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

[0088] Memory 109 can be used to store software programs and various data. Memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store an operating system and at least one application required for a function (such as a sound playback function or an image playback function); the data storage area may store data generated based on the use of the mobile phone (such as audio data, a phone book, etc.). Furthermore, memory 109 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0089] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0090] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0091] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0092] To facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0093] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an LTE system of universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203 and an operator's IP service 204, which are connected in sequence.

[0094] Optionally, UE201 may be the above-mentioned terminal 100, which will not be described in detail here.

[0095] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 . Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface). eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide access from UE 201 to EPC 203 .

[0096] EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management. HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, and it selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0097] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem), or other IP services.

[0098] Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but can also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., which are not limited here.

[0099] Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

[0100] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0101] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0102] Figure 4 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0103] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0104] The integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0105] Technical terms involved in this embodiment:

[0106] PUSCH, Physical Uplink Shared Channel, physical uplink shared channel;

[0107] CP-OFDM: Cyclic Prefix-Orthogonal Frequency Division Multiplexing, cyclic prefix orthogonal frequency division multiplexing;

[0108] DFT-S-OFDM: Discrete Fourier Transform-Single Carrier-Orthogonal Frequency Division Multiplexing;

[0109] DCI: Downlink Control Information, downlink control information;

[0110] Transform precoding, or transform precoder, transform precoding.

[0111] First embodiment

[0112] 5 , the first embodiment of the present application proposes a processing method, including the following steps:

[0113] S10, the network device sends downlink control information, and sets or determines the size of the downlink control information based on a preset policy. Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms. Optionally, the downlink control information indicating different waveforms has the same size.

[0114] S20, the terminal device determines the size of the downlink control information based on a preset strategy. Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms. Optionally, the sizes of the downlink control information indicating different waveforms are consistent.

[0115] Optionally, the preset strategy includes at least one of the following:

[0116] The size of the downlink control information is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled;

[0117] The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each field when transform precoding is enabled;

[0118] The size of the downlink control information is set to the sum of the bit widths of each field contained in the downlink control information. Optionally, the bit width of each field is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0119] Optionally, the preset strategy includes at least one of the following:

[0120] If transform precoding is disabled, the DCI size is determined to be X1 according to the RRC configuration. If transform precoding is enabled, the DCI size is determined to be X2 according to the RRC configuration. The larger value of X1 or X2 is selected as the size of the downlink control information.

[0121] If transform precoding is disabled, the bit width of each field included in the downlink control information is determined to be M1(i) according to the RRC configuration. If transform precoding is enabled, the bit width of each field is determined to be M2(i) according to the RRC configuration. The larger value of M1(i) and M2(i) is selected as the bit width of each field of DCI, and the size of the downlink control information is determined according to the sum of the bit widths of each field, where i is the index of each field of DCI, and M1(i) and M2(i) are both natural numbers;

[0122] If transform precoding is disabled, determining the size of the downlink control information as X3 according to the RRC configuration; optionally, using the size of the downlink control information X3 as the size of the downlink control information monitored by the terminal device;

[0123] If transform precoding is disabled, the bit width M1(i) of each domain contained in the downlink control information is determined according to the RRC configuration, and the sum of the bit width M1(i) of each domain contained in the downlink control information is used as the size of the downlink control information; optionally, the sum of the bit width M1(i) of each domain contained in the downlink control information is used as the size of the downlink control information monitored by the terminal device, where i is the index of each domain.

[0124] Optionally, if transform precoding is enabled or enabled, a DFT-S-OFDM waveform is used.

[0125] Optionally, if transform precoding is enabled or disabled, the CP-OFDM waveform is used.

[0126] Optionally, the downlink control information includes a dynamic waveform switching indication field, which is used to indicate a waveform used by a physical uplink data channel related to the downlink control information;

[0127] Optionally, the different waveforms include CP-OFDM and / or DFT-S-OFDM.

[0128] Optionally, the downlink control information indicating CP-OFDM and the downlink control information indicating DFT-S-OFDM have the same size.

[0129] Optionally, the downlink control information is used to schedule a physical uplink data channel.

[0130] Optionally, the required format of the downlink control information is DCI format 0_1 ​​and / or DCI format 0_2.

[0131] Optionally, the physical uplink data channel determines a waveform used for transmission according to a dynamic waveform switching indication of the downlink control information.

[0132] Optionally, if the size X of the DCI corresponding to the indicated waveform is smaller than the size Y of the DCI set according to the preset policy, then the X bits correspond to the X least significant bits (LSBs) of the Y bits, and the YX most significant bits (MSBs) in the DCI are padded with zeros. The size X of the DCI corresponding to the indicated waveform refers to the size of the significant bits in the DCI corresponding to the indicated waveform.

[0133] Optionally, if the size X of the DCI corresponding to the indicated waveform is smaller than the size Y of the DCI set according to the preset policy, then the X bits correspond to the X most significant bits (MSBs) of the Y bits, and the YX least significant bits (LSBs) in the DCI are padded with zeros. The size X of the DCI corresponding to the indicated waveform refers to the size of the significant bits in the DCI corresponding to the indicated waveform.

[0134] Optionally, if the bit width M of the domain of the DCI corresponding to the indicated waveform is less than the bit width N of the domain corresponding to the DCI set according to the above preset policy, the M bits correspond to the M least significant bits (LSBs) of the N bits, and the NM most significant bits (MSBs) in the DCI are filled with zeros. Optionally, the most significant bit of each domain is mapped to the lowest order information bit of the domain, for example, the most significant bit of the first domain is mapped to a0. Optionally, the least significant bit of each domain is mapped to the highest order information bit of the domain, for example, the least significant bit of the first domain is mapped to ak. The bit width M of the domain of the DCI corresponding to the indicated waveform refers to the size of the effective bit width of the domain in the DCI corresponding to the indicated waveform.

[0135] Optionally, if the bit width M of the domain of the DCI corresponding to the indicated waveform is less than the bit width N of the domain corresponding to the DCI set according to the above preset policy, the M bits correspond to the M most significant bits (MSBs) of the N bits, and the NM least significant bits (LSBs) in the DCI are filled with zeros. Optionally, the most significant bit of each domain is mapped to the lowest order information bit of the domain, for example, the most significant bit of the first domain is mapped to a0. Optionally, the least significant bit of each domain is mapped to the highest order information bit of the domain, for example, the least significant bit of the first domain is mapped to ak. The bit width M of the domain of the DCI corresponding to the indicated waveform refers to the size of the effective bit width of the domain in the DCI corresponding to the indicated waveform.

[0136] Optionally, the downlink control information includes a waveform dynamic switching indication field, which contains 1 bit for indicating waveform switching, for example, 0 represents DFT-S-OFDM waveform, 1 represents CP-OFDM waveform; or 0 represents CP-OFDM waveform, 1 represents DFT-S-OFDM waveform.

[0137] Optionally, the downlink control information includes a waveform dynamic switching indication field, which includes one bit and is used to indicate dynamic waveform switching. For example, 0 indicates maintaining the waveform used in the previous transmission, and 1 indicates using a waveform different from the waveform used in the previous transmission. For example, the network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM.

[0138] Optionally, the downlink control information includes a waveform dynamic switching indication field, where the field contains one bit and is used to indicate dynamic waveform switching. For example, 0 indicates using the waveform configured by the RRC message, and 1 indicates using a waveform different from the waveform configured by the RRC message. For example, the network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM.

[0139] Optionally, the RRC message enables or disables transform precoding.

[0140] Optionally, the RRC message is used to indicate the waveform used for message 3 (Msg 3) transmission; optionally, the RRC message may be msg3-transformPrecoder.

[0141] Optionally, the RRC message is used to indicate a waveform used for physical uplink data channel transmission; optionally, the RRC message may be a transformPrecoder.

[0142] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset strategy, and the terminal device determines the size of the downlink control information based on the preset strategy, wherein the size of the downlink control information indicating different waveforms is consistent, thereby ensuring that the size of the downlink control information indicating CP-OFDM and the downlink control information indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the blind decoding of the terminal device.

[0143] Second embodiment

[0144] 6 , based on the embodiment shown in FIG. 5 , a second embodiment of the present application proposes a processing method.

[0145] Optionally, the method further comprises the steps of:

[0146] S30, the terminal device decodes the domain included in the downlink control information.

[0147] Optionally, step S30 includes at least one of the following:

[0148] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, then use the N(i) least significant bits to decode the field, and / or, if greater, use the field width M(i) as the low M(i) bits of the field for decoding, where i is the index of each DCI field;

[0149] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, then use the N(i) most significant bits to decode the field, and / or, if greater, use the field width M(i) as the high M(i) bits of the field for decoding, where i is the index of each DCI field;

[0150] If the field width N(i) corresponding to the indicated waveform is less than the field width M(i) set according to the preset policy, the M(i)-N(i) most significant bits are ignored, where i is the index of each DCI field;

[0151] If the domain width N(i) corresponding to the indicated waveform is less than the domain width M(i) set according to the preset policy, the M(i)-N(i) least significant bits are ignored, where N(i) and M(i) are both natural numbers and i is the index of each DCI domain;

[0152] If the downlink control information size X corresponding to the indicated waveform is smaller than the downlink control information size Y set according to the preset policy, the downlink control information is decoded using X least significant bits, and the remaining downlink control information bits are zero, where X and Y are both natural numbers.

[0153] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on a preset policy, wherein the size of the downlink control information indicating different waveforms is consistent, thereby ensuring that the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the terminal device's blind decoding. Furthermore, when the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the DCI according to different waveform information, and can also ensure decoding accuracy.

[0154] Third embodiment

[0155] Based on the above embodiments, the third embodiment of the present application proposes a processing method.

[0156] In this embodiment, the network device sends downlink control information, sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on the preset policy. Optionally, the downlink control information is used to indicate that different waveforms are used for uplink transmission, indicating that the size of the downlink control information of different waveforms is consistent.

[0157] Optionally, the preset policy includes: the size of the downlink control information is set to a maximum value between a size when transform precoding is disabled and a size when transform precoding is enabled.

[0158] Optionally, this embodiment determines the monitored DCI format 0_1 ​​in the UE-specific search space according to the following method:

[0159] Optionally, for downlink control information including a dynamic waveform switching indication, its size is set to a maximum value between a size when transform precoding is disabled and a size when transform precoding is enabled.

[0160] Optionally, when determining the DCI size, first assume that transform precoding is disabled (CP-OFDM waveform), and then determine the DCI size to be X1 based on the RRC configuration; then assume that transform precoding is enabled (DFT-S-OFDM waveform), and then determine the DCI size to be X2 based on the RRC configuration; compare X1 and X2, and select the larger value of X1 and X2 as the DCI size.

[0161] Optionally, assuming that transform precoding is disabled, the DCI size is determined to be X3 according to the RRC configuration, and the DCI size X3 is used as the size of the DCI monitored by the terminal.

[0162] Optionally, if the domain bit width N corresponding to the indicated waveform is less than or equal to the domain bit width M set according to the above-mentioned preset strategy, the N least significant bits are used to decode the domain; and / or, if it is greater, the domain bit width M is used as the low M bits of the domain for decoding, where N and M are both natural numbers.

[0163] Optionally, if the domain bit width N corresponding to the indicated waveform is less than or equal to the domain bit width M set according to the above-mentioned preset strategy, the N most significant bits are used to decode the domain, and / or, if greater, the domain bit width M is decoded as the high M bits of the domain.

[0164] Optionally, if the field bit width N corresponding to the indicated waveform is smaller than the field bit width M set according to the above preset policy, the terminal ignores MN most significant bits.

[0165] Optionally, if the field bit width N corresponding to the indicated waveform is smaller than the field bit width M set according to the above preset policy, the terminal ignores MN least significant bits.

[0166] Optionally, DCI format 0_1 ​​is used to schedule one or more PUSCHs to the terminal device.

[0167] Optionally, DCI format 0_2 is used to schedule a PUSCH to the terminal device.

[0168] Optionally, the following information is transmitted using DCI format 0_1 ​​and / or DCI format 0_2 scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI:

[0169] The corresponding waveform switching indication field contains 0 or 1 bits:

[0170] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit to indicate waveform switching, for example, 0 for DFT-S-OFDM waveform and 1 for CP-OFDM waveform. If the cell / carrier does not support dynamic waveform switching, this field does not exist, that is, it is 0 bit.

[0171] Optionally, the field includes one bit for indicating dynamic waveform switching, for example, 0 indicates maintaining the waveform used in the previous transmission, and 1 indicates using a waveform different from the previous transmission. For example, the network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0172] Optionally, the field includes 1 bit for indicating dynamic waveform switching, for example, 0 indicates using the waveform configured by the RRC message, and 1 indicates using a waveform different from the waveform configured by the RRC message. For example, a network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0173] Optionally, the RRC message is used to indicate the waveform used for message 3 (Msg 3) transmission; optionally, the RRC message may be msg3-transformPrecoder.

[0174] Optionally, the RRC message is used to indicate a waveform used for physical uplink data channel transmission; optionally, the RRC message may be a transformPrecoder.

[0175] Optionally, the corresponding PTRS-DMRS relationship (PTRS-DMRS Association) field contains 0 bits or 2 bits:

[0176] Optionally, the field is used to indicate a PTRS-DMRS port relationship.

[0177] If the cell / carrier supports dynamic waveform switching, this field contains 2 bits. If the Waveform Switching Indication field indicates CP-OFDM, the 2 bits are valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the terminal ignores this field.

[0178] Optionally, if the cell / carrier supports dynamic waveform switching, this field contains 2 bits. If the waveform switching indication field indicates CP-OFDM, the 2 bits are valid; if the waveform switching indication field indicates DFT-S-OFDM, the information in this field is zero.

[0179] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains 0 bits or 2 bits. When transform precoding is disabled, the 2 bits are valid; when transform precoding is enabled, this field is invalid, that is, it contains only 0 bits.

[0180] Optionally, if PTRS-UplinkConfig is not configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoding is disabled, or maxRank=1, this field includes 0 bits.

[0181] And / or, if PTRS-UplinkConfig is configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoding is enabled, or maxRank is greater than 1, this field includes 2 bits, where TS 38.212 Tables 7.3.1.1.2-25 / 7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between the PTRS port(s) and the DMRS port when maxNrofPorts in PTRS-UplinkConfig is configured with one PT-RS port and two PT-RS ports, respectively, and the DMRS port is indicated by the antenna port field. When the SRS resource set indicator field exists and maxRank>2, this field indicates the association between the PTRS port and the DMRS port corresponding to the SRS resource indicator field and / or the precoding information and layer number field according to TS 38.212 Table 7.3.1.1.2-25 and 7.3.1.1.2-26. When the SRS resource set indicator field exists and is equal to "10" and "11" and maxRank=2, the most significant bit (MSB) of this field indicates the association between the PTRS port and the DMRS port corresponding to the SRS resource indicator and / or precoding information and layer number field, and the least significant bit (LSB) of this field indicates the association between the PTRS port and the DMRS port corresponding to the second SRS resource indicator field and / or the second precoding information field, refer to TS 38.212 Table 7.3.1.2-25A.

[0182] Optionally, corresponding to the scenario where the DMRS sequence initialization field contains 0 bits or 1 bits:

[0183] Optionally, the field is used to indicate an initialization parameter of a demodulation reference signal sequence of a PUSCH.

[0184] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit. If the Waveform Switching Indication field indicates CP-OFDM, the 1 bit is valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the terminal ignores this field.

[0185] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit. If the Waveform Switching Indication field indicates CP-OFDM, 1 bit is valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the information in this field is zero.

[0186] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains 0 bits or 1 bits. When transform precoding is disabled, 1 bit is valid; when transform precoding is enabled, this field is invalid, that is, it contains only 0 bits.

[0187] Optionally, corresponding to the scenario where the precoding information and number of layers field contains 0 bits, 1 bit, 2 bits, 3 bits, 4 bits, 5 bits, or 6 bits:

[0188] Optionally, the field is used to indicate the number of transmission layers and precoding information.

[0189] Optionally, if the cell / carrier supports dynamic waveform switching, this field contains {0, 1, 2, 3, 4, 5, 6} bits. If the waveform switching indication field indicates CP-OFDM, {0, 1, 2, 3, 4, 5, 6} bits are valid; if the waveform switching indication field indicates DFT-S-OFDM, {0, 2, 3, 4, 5} bits are valid.

[0190] Optionally, if the size of the domain is calculated by the terminal assuming that the CP-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal parses all bits of the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal device uses the N least significant bits to decode the domain.

[0191] Optionally, if the size of the domain is calculated by the terminal assuming that the DFT-S-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal device uses the N least significant bits to decode the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal parses all bits of the domain.

[0192] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains {0, 1, 2, 3, 4, 5, 6} bits. When transform precoding is disabled, {0, 1, 2, 3, 4, 5, 6} bits are valid; when transform precoding is enabled, {0, 2, 4, 5} bits are valid.

[0193] Optionally, if the upper layer parameter txConfig=nonCodeBook, field 0 contains bits.

[0194] Optionally, if the upper layer parameter txConfig=codebook, this field contains 0 bits and is applicable to 1 antenna port.

[0195] Optionally, according to TS 38.212 Table 7.3.1.1.2-2, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper layer parameters maxRank and codebookSubset, this field contains 4, 5 or 6 bits.

[0196] Optionally, according to TS 38.212 Table 7.3.1.1.2-2A, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode 1, maxRank=2, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 5 bits.

[0197] Optionally, according to TS 38.212 Table 7.3.1.1.2-2B, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=3 or 4, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 6 bits.

[0198] Optionally, according to TS 38.212 Table 7.3.1.1.2-3, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2, 4 or 5 bits.

[0199] Optionally, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, according to TS 38.212 Table 7.3.1.1.2-3A, for 4 antenna ports, and depending on whether transform precoding is enabled or disabled, and the value of the higher-layer parameter codebookSubset, this field contains 3 or 4 bits.

[0200] Optionally, according to TS 38.212 Table 7.3.1.1.2-4, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2, or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2 or 4 bits.

[0201] Optionally, according to TS 38.212 Table 7.3.1.1.2-4A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, transform precoding is disabled, maxRank=2, and codebookSubset=nonCoherent, this field contains 2 bits.

[0202] Optionally, according to TS 38.212 Table 7.3.1.1.2-5, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 1 or 3 bits.

[0203] Optionally, according to TS 38.212 Table 7.3.1.1.2-5A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, and depending on whether transform precoding is enabled or disabled, and the value of the upper layer parameter codebookSubset, this field contains 2 bits.

[0204] Optionally, the corresponding antenna port (Antenna ports) field contains 2 bits, 3 bits, 4 bits, or 5 bits:

[0205] Optionally, the field is used to indicate information of an antenna port.

[0206] If the cell / carrier supports dynamic waveform switching, this field contains {2, 3, 4, 5} bits. If the Waveform Switching Indication field indicates CP-OFDM, {3, 4, 5} bits are valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, {2, 4} bits are valid.

[0207] Optionally, if the size of the domain is calculated by the terminal assuming that the CP-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal parses all bits of the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal device uses the N least significant bits to decode the domain.

[0208] Optionally, if the size of the domain is calculated by the terminal assuming that the DFT-S-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal device uses the N least significant bits to decode the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal parses all bits of the domain.

[0209] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains bits {2, 3, 4, 5}. When transform precoding is disabled, bits {2, 3, 4, 5} are valid; when transform precoding is enabled, bits {2, 4} are not valid.

[0210] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6, if transform precoding is enabled, dmrs-Type = 1, maxLength = 1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0211] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6A, if transform precoding is enabled and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, π / 2 BPSK modulation is used, dmrs-Type = 1, maxLength = 1, where nsCID is the antenna port scrambling identifier defined in [TS 38.2116.4.1.1.2].

[0212] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7, if transform precoding is enabled, dmrs-Type = 1, maxLength = 2, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0213] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7A, if transform precoding is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, using π / 2 BPSK modulation, dmrs-Type = 1, maxLength = 2, where n SCID It is the antenna port scrambling identifier defined in [TS 38.2116.4.1.1.2].

[0214] Optionally, corresponding to 3 bits, as defined in TS 38.212 Table 7.3.1.1.2-8 / 9 / 10 / 11, if transform precoding is disabled, dmrs-Type = 1, maxLength = 1, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field; if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0215] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-12 / 13 / 14 / 15, if transform precoding is disabled, dmrs-Type = 1, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0216] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-16 / 17 / 18 / 19, if transform precoding is disabled, dmrs-Type = 2, maxLength = 1, and if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, and if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0217] Optionally, corresponding to 5 bits, as defined in TS 38.212 Table 7.3.1.1.2-20 / 21 / 22 / 23, if transform precoding is disabled, dmrs-Type = 2, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0218] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on the preset policy, wherein the size of the downlink control information indicating different waveforms is consistent, and for the downlink control information containing a dynamic waveform switching indication, its size is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled, thereby ensuring that the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the blind decoding of the terminal device. Furthermore, when the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the DCI according to different waveform information. Optionally, if the domain bit width N corresponding to the indicated waveform is less than or equal to the domain bit width M set according to the above-mentioned preset strategy, the N least significant bits are used to decode the domain; and / or, if it is greater, the domain bit width M is decoded as the low M bits of the domain, thereby ensuring the accuracy of the decoding.

[0219] Fourth embodiment

[0220] Based on the above embodiments, the fourth embodiment of the present application proposes a processing method.

[0221] In this embodiment, the network device sends downlink control information, sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on the preset policy. Optionally, the downlink control information is used to indicate that different waveforms are used for uplink transmission, indicating that the size of the downlink control information of different waveforms is consistent.

[0222] Optionally, the preset policy includes: the size of the downlink control information is set to a maximum value between a size when transform precoding is disabled and a size when transform precoding is enabled.

[0223] Optionally, this embodiment determines the monitored DCI format 0_1 ​​and / or DCI format 0_2 in the UE-specific search space according to the following method:

[0224] Optionally, for downlink control information including a dynamic waveform switching indication, its size is set to a maximum value between a size when transform precoding is disabled and a size when transform precoding is enabled.

[0225] Optionally, when determining the DCI size, first assume that transform precoding is disabled, and then determine the DCI size as X1 according to the RRC configuration; then assume that transform precoding is enabled, and then determine the DCI size as X2 according to the RRC configuration; compare X1 and X2, and select the larger value of X1 and X2 as the DCI size.

[0226] Optionally, assuming transform precoding is disabled, the DCI size is determined according to the RRC configuration, and the DCI size is used as the size of the DCI monitored by the terminal.

[0227] Optionally, if the downlink control information size Y corresponding to the indicated waveform is smaller than the downlink control information size X set as above, the downlink control information is decoded using Y most significant bits, where X and Y are both natural numbers.

[0228] Optionally, the remaining downlink control information bits are zero, that is, the remaining XY information bits in the downlink control information are set to zero.

[0229] Optionally, DCI format 0_1 ​​is used to schedule one or more PUSCHs to the terminal.

[0230] Optionally, DCI format 0_2 is used to schedule a PUSCH to the terminal.

[0231] The following information is transmitted using DCI format 0_1 ​​and / or DCI format 0_2 scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI:

[0232] Optionally, the corresponding waveform switching indication field contains 0 or 1 bits:

[0233] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit to indicate waveform switching, for example, 0 for DFT-S-OFDM waveform and 1 for CP-OFDM waveform. If the cell / carrier does not support dynamic waveform switching, this field does not exist, that is, it is 0 bit.

[0234] Optionally, the field includes 1 bit for indicating dynamic waveform switching, for example, 0 indicates keeping the waveform used in the previous transmission, and 1 indicates using a waveform different from that used in the previous transmission.

[0235] For example, the network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0236] Optionally, the field includes 1 bit for indicating dynamic waveform switching, for example, 0 indicates using the waveform configured by the RRC message, and 1 indicates using a waveform different from the waveform configured by the RRC message. For example, a network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0237] Optionally, the RRC message is used to indicate the waveform used for message 3 (Msg 3) transmission; it may be msg3-transformPrecoder.

[0238] Optionally, the RRC message is used to indicate a waveform used for physical uplink data channel transmission; it may be transformPrecoder.

[0239] Optionally, if the waveform switching indication field indicates that the waveform used by the physical uplink channel is CP-OFDM, that is, DCI format 0_1 ​​and / or DCI format 0_2 are used to indicate that the PUSCH transmission uses the CP-OFDM waveform, the remaining fields are set as follows:

[0240] Optionally, corresponding to the PTRS-DMRS Association field - 0 bits or 2 bits:

[0241] If PTRS-UplinkConfig is not configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB, and transform precoding is disabled, or transform precoding is enabled, or maxRank = 1, this field includes 0 bits.

[0242] And / or, if PTRS-UplinkConfig is configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoding is enabled, or maxRank is greater than 1, this field includes 2 bits. Optionally, when maxNrofPorts in PTRS-UplinkConfig is configured with one PT-RS port and two PT-RS ports respectively, and the DMRS port is indicated by the antenna port field, TS 38.212 Tables 7.3.1.1.2-25 / 7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between the PTRS port and the DMRS port. When the SRS resource set indicator field exists and maxRank>2, the field is used to indicate the association between the PTRS port and the DMRS port, corresponding to the SRS resource indication field and / or the precoding information and layer number field according to TS 38.212 Table 7.3.1.1.2-25 and 7.3.1.1.2-26. When the SRS resource indication field exists and is equal to "10" and "11" and maxRank=2, the most significant bit (MSB) of the field is used to indicate the association between the PTRS port and the DMRS port corresponding to the SRS resource indication field and / or the precoding information and layer number field, and the least significant bit (LSB) of the field represents the association between the PTRS port and the DMRS port corresponding to the second SRS resource indication field and / or the second precoding information field, according to TS 38.211 Table 7.3.1.2-25A.

[0243] Optionally, the field is used to indicate a PTRS-DMRS port relationship.

[0244] Optionally, corresponding to the scenario of DMRS sequence initialization field -1 bit:

[0245] Optionally, the field is used to indicate an initialization parameter of a demodulation reference signal sequence of a PUSCH.

[0246] Optionally, the corresponding precoding information and number of layers field contains 0 bits, 1 bits, 2 bits, 3 bits, 4 bits, 5 bits, or 6 bits, where:

[0247] Optionally, the field is used to indicate the number of transmission layers and precoding information.

[0248] Optionally, if the upper layer parameter txConfig=nonCodeBook, this field is 0 bits.

[0249] Optionally, if the upper layer parameter txConfig=codebook, this field is 0 bits and is applicable to 1 antenna port.

[0250] Optionally, according to TS 38.212 Table 7.3.1.1.2-2, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper layer parameters maxRank and codebookSubset, this field contains 4, 5 or 6 bits.

[0251] Optionally, according to TS 38.212 Table 7.3.1.1.2-2A, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=2, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 5 bits.

[0252] Optionally, according to TS 38.212 Table 7.3.1.1.2-2B, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=3 or 4, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 6 bits.

[0253] Optionally, according to TS 38.212 Table 7.3.1.1.2-3, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2, 4 or 5 bits.

[0254] Optionally, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, according to TS 38.212 Table 7.3.1.1.2-3A, for 4 antenna ports, and depending on whether transform precoding is enabled or disabled, and the value of the higher-layer parameter codebookSubset, this field contains 3 or 4 bits.

[0255] Optionally, according to TS 38.212 Table 7.3.1.1.2-4, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2, or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2 or 4 bits.

[0256] Optionally, according to TS 38.212 Table 7.3.1.1.2-4A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, transform precoding is disabled, maxRank=2, and codebookSubset=nonCoherent, this field contains 2 bits.

[0257] Optionally, according to TS 38.212 Table 7.3.1.1.2-5, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 1 or 3 bits.

[0258] Optionally, according to TS 38.212 Table 7.3.1.1.2-5A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, and depending on whether transform precoding is enabled or disabled, and the value of the upper layer parameter codebookSubset, this field contains 2 bits.

[0259] Optionally, the corresponding antenna port (Antenna ports) field contains 3 bits, 4 bits, or 5 bits, where:

[0260] Optionally, the field is used to indicate information of an antenna port.

[0261] Optionally, corresponding to 3 bits, as defined in TS 38.212 Table 7.3.1.1.2-8 / 9 / 10 / 11, if transform precoding is disabled, dmrs-Type = 1, maxLength = 1, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0262] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-12 / 13 / 14 / 15, if transform precoding is disabled, dmrs-Type = 1, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0263] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-16 / 17 / 18 / 19, if transform precoding is disabled, dmrs-Type = 2, maxLength = 1, and if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, and if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0264] Optionally, corresponding to 5 bits, as defined in TS 38.212 Table 7.3.1.1.2-20 / 21 / 22 / 23, if transform precoding is disabled, dmrs-Type = 2, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0265] Optionally, if the DCI size calculated based on the waveform assumption of CP-OFDM is smaller than the DCI size calculated based on the waveform assumption of DFT-S-OFDM, the remaining bits in DCI 0_1 are set to 0; otherwise, the terminal parses all bits.

[0266] Optionally, if the waveform switching indication field indicates DFT-S-OFDM, that is, DCI format 0_1 ​​and / or DCI format

[0267] 0_2 is used to indicate that PUSCH transmission uses DFT-S-OFDM waveform, and the remaining fields are set as follows:

[0268] Optionally, the corresponding PTRS-DMRS Association field contains 0 bits, where:

[0269] Optionally, the field is used to indicate a PTRS-DMRS port relationship.

[0270] Optionally, if PTRS-UplinkConfig is not configured in dmrs-UplinkForPUSCH-MappingTypeA, or transform precoding is enabled, or maxRank=1, the bit is 0.

[0271] Optionally, corresponding to the scenario where the DMRS sequence initialization field contains 0 bits:

[0272] Optionally, the field is used to indicate an initialization parameter of a demodulation reference signal sequence of a PUSCH.

[0273] The corresponding precoding information and number of layers field contains 0 bits, 1 bit, 2 bits, 3 bits, 4 bits, or 5 bits, where:

[0274] Optionally, if the upper layer parameter txConfig=nonCodeBook, this field contains 0 bits.

[0275] Optionally, if the upper layer parameter txConfig=codebook, this field contains 0 bits and is applicable to 1 antenna port.

[0276] Optionally, according to TS 38.212 Table 7.3.1.1.2-3, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2, 4 or 5 bits.

[0277] Optionally, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, according to TS 38.212 Table 7.3.1.1.2-3A, for 4 antenna ports, and depending on whether transform precoding is enabled or disabled, and the value of the higher-layer parameter codebookSubset, this field contains 3 or 4 bits.

[0278] Optionally, according to TS 38.212 Table 7.3.1.1.2-4A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, transform precoding is disabled, maxRank=2, and codebookSubset=nonCoherent, this field contains 2 bits.

[0279] Optionally, according to TS 38.212 Table 7.3.1.1.2-5, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 1 or 3 bits.

[0280] Optionally, according to TS 38.212 Table 7.3.1.1.2-5A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, and depending on whether transform precoding is enabled or disabled, and the value of the upper layer parameter codebookSubset, this field contains 2 bits.

[0281] Optionally, the corresponding antenna port (Antenna ports) field contains 2 bits or 4 bits, where:

[0282] Optionally, the field is used to indicate information of an antenna port.

[0283] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6, if transform precoding is enabled, dmrs-Type = 1, maxLength = 1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0284] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6A, if transform precoding is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, using π / 2 BPSK modulation, dmrs-Type = 1, maxLength = 1, where n SCID It is the antenna port scrambling identifier defined in [TS 38.2116.4.1.1.2].

[0285] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7, if transform precoding is enabled, dmrs-Type = 1, maxLength = 2, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0286] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7A, if transform precoding is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, using π / 2 BPSK modulation, dmrs-Type = 1, maxLength = 2, where n SCID It is the antenna port scrambling identifier defined in [TS 38.2116.4.1.1.2].

[0287] Optionally, if the DCI size calculated based on the DFT-S-OFDM waveform assumption is smaller than the DCI size calculated based on the CP-OFDM waveform assumption, the remaining bits in DCI 0_1 are set to 0; otherwise, the terminal parses all bits.

[0288] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on the preset policy, wherein the size of the downlink control information indicating different waveforms is consistent. For the downlink control information containing the dynamic waveform switching indication, its size is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled, thereby ensuring that the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the terminal device's blind decoding. Furthermore, when the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the DCI according to the different waveform information. Optionally, if the downlink control information size Y corresponding to the indicated waveform is smaller than the downlink control information size X set as described above, the downlink control information is decoded using the Y most significant bits, thereby ensuring the accuracy of the decoding.

[0289] Fifth embodiment

[0290] The fifth embodiment of the present application proposes a processing method.

[0291] In this embodiment, the network device sends downlink control information, sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on the preset policy. Optionally, the downlink control information is used to indicate that different waveforms are used for uplink transmission, indicating that the size of the downlink control information of different waveforms is consistent.

[0292] Optionally, the preset strategy includes: the size of the downlink control information is set to the maximum value between the sum of the bit widths of each domain included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each domain when transform precoding is enabled; and / or, the size of the downlink control information is set to the sum of the bit widths of each domain included in the downlink control information, optionally, the bit width of each domain is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0293] Optionally, this embodiment determines the monitored DCI format 0_1 ​​and / or DCI format 0_2 in the UE-specific search space according to the following method:

[0294] Optionally, for downlink control information including a dynamic waveform switching indication, the size thereof is set to the sum of the bit widths of various fields included in the downlink control information.

[0295] Optionally, for each domain, its bit width M(i) is set to the maximum value between the bit width M1(i) when transform precoding is disabled and the bit width M2(i) when transform precoding is enabled, where i is the index of each DCI domain.

[0296] Optionally, when determining the size of each DCI domain, first assume that transform precoding is disabled, and then determine the bit width of each DCI domain as M1(i) according to the RRC configuration; then assume that transform precoding is enabled, and then determine the bit width of each DCI domain as M2(i) according to the RRC configuration; compare M1(i) and M2(i), and select the larger value as the bit width of each DCI domain, where i is the index of each DCI domain.

[0297] Optionally, assuming that transform precoding is disabled, the bit width M1(i) of each DCI field is determined according to the RRC configuration, and the sum ΣM1(i) of the bit width M1(i) of each DCI field is used as the size of the DCI monitored by the terminal.

[0298] Optionally, if the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the above preset strategy, the N(i) least significant bits are used to decode the domain, where i is the index of each DCI domain.

[0299] Optionally, if the field bit width N(i) corresponding to the indicated waveform is less than or equal to the field bit width M(i) set according to the above preset strategy, the N(i) most significant bits are used to decode the field.

[0300] Optionally, if the domain width N(i) corresponding to the indicated waveform is smaller than the domain width M(i) set according to the above preset strategy, the terminal ignores the M(i)-N(i) most significant bits, where i is the index of each DCI domain.

[0301] Optionally, if the field width N(i) corresponding to the indicated waveform is less than the field width M(i) set according to the above preset policy, the terminal ignores the M(i)-N(i) least significant bits, where N(i) and M(i) are both natural numbers, and i is the index of each DCI field.

[0302] Optionally, DCI format 0_1 ​​is used to schedule one or more PUSCHs to the terminal device.

[0303] Optionally, DCI format 0_2 is used to schedule a PUSCH to the terminal device.

[0304] Optionally, the following information is transmitted using DCI format 0_1 ​​and / or DCI format 0_2 scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI:

[0305] The corresponding waveform switching indication field contains 0 or 1 bits:

[0306] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit to indicate waveform switching, for example, 0 for DFT-S-OFDM waveform and 1 for CP-OFDM waveform. If the cell / carrier does not support dynamic waveform switching, this field does not exist, that is, it is 0 bit.

[0307] Optionally, the field includes one bit for indicating dynamic waveform switching, for example, 0 indicates maintaining the waveform used in the previous transmission, and 1 indicates using a waveform different from the previous transmission. For example, the network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0308] Optionally, the field includes 1 bit for indicating dynamic waveform switching, for example, 0 indicates using the waveform configured by the RRC message, and 1 indicates using a waveform different from the waveform configured by the RRC message. For example, a network device sends an RRC message to set the waveform used by the physical uplink data channel. The waveform includes CP-OFDM and / or DFT-S-OFDM. The RRC message enables or disables transform precoding.

[0309] Optionally, the RRC message is used to indicate the waveform used for message 3 (Msg 3) transmission; it may be msg3-transformPrecoder.

[0310] Optionally, the RRC message is used to indicate a waveform used for physical uplink data channel transmission; it may be transformPrecoder.

[0311] Optionally, the corresponding PTRS-DMRS relationship (PTRS-DMRS Association) field contains 0 bits or 2 bits:

[0312] Optionally, the field is used to indicate a PTRS-DMRS port relationship.

[0313] If the cell / carrier supports dynamic waveform switching, this field contains 2 bits. If the Waveform Switching Indication field indicates CP-OFDM, the 2 bits are valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the terminal ignores this field.

[0314] Optionally, if the cell / carrier supports dynamic waveform switching, this field contains 2 bits. If the waveform switching indication field indicates CP-OFDM, the 2 bits are valid; if the waveform switching indication field indicates DFT-S-OFDM, the information in this field is zero.

[0315] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains 0 bits or 2 bits. When transform precoding is disabled, the 2 bits are valid; when transform precoding is enabled, this field is invalid, that is, it contains only 0 bits.

[0316] Optionally, if PTRS-UplinkConfig is not configured in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB and transform precoding is disabled, or maxRank=1, it is 0 bits.

[0317] Otherwise, it is 2 bits, where TS 38.212 Tables 7.3.1.1.2-25 / 7.3.1.1.2-25A and 7.3.1.1.2-26 are used to indicate the association between the PTRS port(s) and the DMRS port when maxNrofPorts in PTRS-UplinkConfig is configured with one PT-RS port and two PT-RS ports, respectively, and the DMRS port is indicated by the antenna port field. When the SRS Resource Set Index field is present and maxRank>2, this field indicates the association between the PTRS port and the DMRS port corresponding to the SRS Resource Index field and / or the Precoding Information and Layer Number field according to TS 38.212 Tables 7.3.1.1.2-25 and 7.3.1.1.2-26. When the SRS resource set indicator field exists and is equal to "10" and "11" and maxRank = 2, the most significant bit (MSB) of this field represents the association between the PTRS port and the DMRS port corresponding to the SRS resource indicator and / or precoding information and layer number field, and the least significant bit (LSB) of this field represents the association between the PTRS port and the DMRS port corresponding to the second SRS resource indicator field and / or the second precoding information field, refer to TS 38.212 Table 7.3.1.2-25A.

[0318] Optionally, corresponding to the scenario where the DMRS sequence initialization field contains 0 bits or 1 bits:

[0319] Optionally, the field is used to indicate an initialization parameter of a demodulation reference signal sequence of a PUSCH.

[0320] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit. If the Waveform Switching Indication field indicates CP-OFDM, the 1 bit is valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the terminal ignores this field.

[0321] If the cell / carrier supports dynamic waveform switching, this field contains 1 bit. If the Waveform Switching Indication field indicates CP-OFDM, the 1 bit is valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, the information in this field is zero.

[0322] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains 0 bits or 1 bits. When transform precoding is disabled, 1 bit is valid; when transform precoding is enabled, this field is invalid, that is, it contains only 0 bits.

[0323] Optionally, corresponding to the scenario where the precoding information and number of layers field contains 0 bits, 1 bits, 2 bits, 3 bits, 4 bits, 5 bits, or 6 bits:

[0324] Optionally, the field is used to indicate the number of transmission layers and precoding information.

[0325] Optionally, if the cell / carrier supports dynamic waveform switching, this field contains {0, 1, 2, 3, 4, 5, 6} bits. If the waveform switching indication field indicates CP-OFDM, {0, 1, 2, 3, 4, 5, 6} bits are valid; if the waveform switching indication field indicates DFT-S-OFDM, {0, 2, 3, 4, 5} bits are valid.

[0326] Optionally, if the size of the domain is calculated by the terminal assuming that the CP-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal parses all bits of the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal device uses the N least significant bits to decode the domain.

[0327] Optionally, if the size of the domain is calculated by the terminal assuming that the DFT-S-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal device uses the N least significant bits to decode the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal parses all bits of the domain.

[0328] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains {0, 1, 2, 3, 4, 5, 6} bits. When transform precoding is disabled, {0, 1, 2, 3, 4, 5, 6} bits are valid; when transform precoding is enabled, {0, 2, 4, 5} bits are valid.

[0329] Optionally, if the upper layer parameter txConfig=nonCodeBook, this field contains 0 bits.

[0330] Optionally, if the upper layer parameter txConfig=codebook, this field contains 0 bits and is applicable to 1 antenna port.

[0331] Optionally, according to TS 38.212 Table 7.3.1.1.2-2, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper layer parameters maxRank and codebookSubset, this field contains 4, 5 or 6 bits.

[0332] Optionally, according to TS 38.212 Table 7.3.1.1.2-2A, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=2, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 5 bits.

[0333] Optionally, according to TS 38.212 Table 7.3.1.1.2-2B, for 4 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=3 or 4, transform precoding is disabled, and depending on the value of the higher-layer parameter codebookSubset, this field contains 4 or 6 bits.

[0334] Optionally, according to TS 38.212 Table 7.3.1.1.2-3, for 4 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2, 4 or 5 bits.

[0335] Optionally, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, according to TS 38.212 Table 7.3.1.1.2-3A, for 4 antenna ports, and depending on whether transform precoding is enabled or disabled, and the value of the higher-layer parameter codebookSubset, this field contains 3 or 4 bits.

[0336] Optionally, according to TS 38.212 Table 7.3.1.1.2-4, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2, or configured as fullpower, transform precoding is disabled, and depending on the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 2 or 4 bits.

[0337] Optionally, according to TS 38.212 Table 7.3.1.1.2-4A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, transform precoding is disabled, maxRank=2, and codebookSubset=nonCoherent, this field contains 2 bits.

[0338] Optionally, according to TS 38.212 Table 7.3.1.1.2-5, for 2 antenna ports, if txConfig = codebook, ul-FullPowerTransmission is not configured or configured as fullpowerMode2 or configured as fullpower, and depending on whether transform precoding is enabled or disabled, and the values ​​of the upper-layer parameters maxRank and codebookSubset, this field contains 1 or 3 bits.

[0339] Optionally, according to TS 38.212 Table 7.3.1.1.2-5A, for 2 antenna ports, if txConfig=codebook, ul-FullPowerTransmission=fullpowerMode1, maxRank=1, and depending on whether transform precoding is enabled or disabled, and the value of the upper layer parameter codebookSubset, this field contains 2 bits.

[0340] Optionally, the corresponding antenna port (Antenna ports) field contains 2 bits, 3 bits, 4 bits, or 5 bits:

[0341] Optionally, the field is used to indicate information of an antenna port.

[0342] If the cell / carrier supports dynamic waveform switching, this field contains {2, 3, 4, 5} bits. If the Waveform Switching Indication field indicates CP-OFDM, {3, 4, 5} bits are valid; if the Waveform Switching Indication field indicates DFT-S-OFDM, {2, 4} bits are valid.

[0343] Optionally, if the size of the domain is calculated by the terminal assuming that the CP-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal parses all bits of the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal device uses the N least significant bits to decode the domain.

[0344] Optionally, if the size of the domain is calculated by the terminal assuming that the DFT-S-OFDM waveform is used, when the waveform switching indication domain indicates CP-OFDM, the terminal device uses the N least significant bits to decode the domain; when the waveform switching indication domain indicates DFT-S-OFDM, the terminal parses all bits of the domain.

[0345] Optionally, if the cell / carrier does not support dynamic waveform switching, this field contains bits {2, 3, 4, 5}. When transform precoding is disabled, bits {2, 3, 4, 5} are valid; when transform precoding is enabled, bits {2, 4} are valid.

[0346] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6, if transform precoding is enabled, dmrs-Type = 1, maxLength = 1, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0347] Optionally, corresponding to 2 bits, as defined in TS 38.212 Table 7.3.1.1.2-6A, if transform precoding is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, using π / 2 BPSK modulation, dmrs-Type = 1, maxLength = 1, where n SCID It is the antenna port scrambling identifier defined in [TS 38.2116.4.1.1.2].

[0348] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7, if transform precoding is enabled, dmrs-Type = 1, maxLength = 2, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and π / 2 BPSK modulation is used.

[0349] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-7A, if transform precoding is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, using π / 2 BPSK modulation, dmrs-Type = 1, maxLength = 2, where n SCID It is the antenna port scrambling identifier defined in [TS 38.211 section 6.4.1.1.2].

[0350] Optionally, corresponding to 3 bits, as defined in TS 38.212 Table 7.3.1.1.2-8 / 9 / 10 / 11, if transform precoding is disabled, dmrs-Type = 1, maxLength = 1, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0351] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-12 / 13 / 14 / 15, if transform precoding is disabled, dmrs-Type = 1, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0352] Optionally, corresponding to 4 bits, as defined in TS 38.212 Table 7.3.1.1.2-16 / 17 / 18 / 19, if transform precoding is disabled, dmrs-Type = 2, maxLength = 1, and if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, and if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and number of layers field.

[0353] Optionally, corresponding to 5 bits, as defined in TS 38.212 Table 7.3.1.1.2-20 / 21 / 22 / 23, if transform precoding is disabled, dmrs-Type = 2, maxLength = 2, if the upper layer parameter txConfig = nonCodebook, the level value is determined according to the SRS resource indication field, if the upper layer parameter txConfig = codebook, it is determined according to the precoding information and layer number field.

[0354] In the technical solution of the present application, the network device sets or determines the size of the downlink control information based on a preset policy, and the terminal device determines the size of the downlink control information based on a preset policy, wherein the size of the downlink control information indicating different waveforms is consistent, and for the downlink control information containing a dynamic waveform switching indication, its size is set to the sum of the bit widths of the various domains contained in the downlink control information, and for each domain, its bit width M(i) is set to the maximum value between the bit width M1(i) when transform precoding is disabled and the bit width M2(i) when transform precoding is enabled. This ensures that the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are consistent, so that the terminal device does not need to blindly decode the two DCI formats 0_1 / 0_2, thereby reducing the complexity of the terminal device's blind decoding. Furthermore, when the size of the DCI indicating CP-OFDM and the DCI indicating DFT-S-OFDM are the same, the number of valid bits in the corresponding domain is different for the CP-OFDM waveform and the DFT-S-OFDM waveform. The terminal device decodes each domain of the DCI according to different waveform information. Optionally, if the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the above-mentioned preset strategy, the N(i) least significant bits are used to decode the domain, thereby ensuring the accuracy of the decoding.

[0355] The present application also provides a processing device, which is applied to a terminal device or is the terminal device, and includes:

[0356] The determination module is used to determine the size of the downlink control information based on a preset strategy. Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms. Optionally, the sizes of the downlink control information indicating different waveforms are consistent.

[0357] Optionally, the preset strategy includes at least one of the following:

[0358] The size of the downlink control information is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled;

[0359] The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each field when transform precoding is enabled;

[0360] The size of the downlink control information is set to the sum of the bit widths of each field contained in the downlink control information. Optionally, the bit width of each field is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0361] Optionally, the preset strategy includes at least one of the following:

[0362] If transform precoding is disabled, the DCI size is determined to be X1 according to the RRC configuration. If transform precoding is enabled, the DCI size is determined to be X2 according to the RRC configuration. The larger value of X1 or X2 is selected as the size of the downlink control information.

[0363] If transform precoding is disabled, the bit width of each field of the downlink control information is determined to be M1(i) according to the RRC configuration; if transform precoding is enabled, the bit width of each field is determined to be M2(i) according to the RRC configuration; the larger value of M1(i) and M2(i) is selected as the bit width of each field of the DCI, and the size of the downlink control information is determined according to the sum of the bit widths of the fields;

[0364] If transform precoding is disabled, the size of the downlink control information is determined to be X3 according to the RRC configuration;

[0365] If transform precoding is disabled, the bit width M1(i) of each field included in the downlink control information is determined according to the RRC configuration, and the sum of the bit widths M1(i) of each field included in the downlink control information is used as the size of the downlink control information.

[0366] Optionally, the device further comprises at least one of the following:

[0367] The downlink control information includes a dynamic waveform switching indication;

[0368] The different waveforms include CP-OFDM and / or DFT-S-OFDM.

[0369] Optionally, the device further comprises:

[0370] A decoding module is used to decode the domain included in the downlink control information.

[0371] Optionally, the device includes at least one of the following:

[0372] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, then use the N(i) least significant bits to decode the field, and / or, if greater, use the field width M(i) as the low M(i) bits of the field for decoding, where i is the index of each DCI field;

[0373] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, then use the N(i) most significant bits to decode the field, and / or, if greater, use the field width M(i) as the high M(i) bits of the field for decoding, where i is the index of each DCI field;

[0374] If the field width N(i) corresponding to the indicated waveform is less than the field width M(i) set according to the preset policy, the M(i)-N(i) most significant bits are ignored, where i is the index of each DCI field;

[0375] If the field width N(i) corresponding to the indicated waveform is less than the field width M(i) set according to the preset policy, then M(i)-N(i) least significant bits are ignored, where i is the index of each DCI field;

[0376] If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset policy, the downlink control information is decoded using N least significant bits, and the remaining downlink control information bits are zero.

[0377] The present application also provides a processing device, which is applied to a network device or is a network device, and includes:

[0378] The sending module is used to send downlink control information, and the size of the downlink control information is set or determined based on a preset strategy. Optionally, the downlink control information is used to indicate that uplink transmission uses different waveforms. Optionally, the size of the downlink control information indicating different waveforms is consistent.

[0379] Optionally, the preset strategy includes at least one of the following:

[0380] The size of the downlink control information is set to the maximum value between the size when transform precoding is disabled and the size when transform precoding is enabled;

[0381] The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when transform precoding is disabled and the sum of the bit widths of each field when transform precoding is enabled;

[0382] The size of the downlink control information is set to the sum of the bit widths of each field contained in the downlink control information. Optionally, the bit width of each field is set to the maximum value between the bit width when transform precoding is disabled and the bit width when transform precoding is enabled.

[0383] Optionally, the preset strategy includes at least one of the following:

[0384] When setting or determining the size of downlink control information, if transform precoding is disabled, the DCI size is determined to be X1 according to the RRC configuration; if transform precoding is enabled, the DCI size is determined to be X2 according to the RRC configuration; the larger of X1 and X2 is selected as the size of the downlink control information;

[0385] When determining the size of each field included in the downlink control information, if transform precoding is disabled, determining the bit width of each field included in the downlink control information as M1(i) according to the RRC configuration, and if transform precoding is enabled, determining the bit width of each field as M2(i) according to the RRC configuration, selecting the larger value of M1(i) and M2(i) as the bit width of each field of the DCI, and setting or determining the size of the downlink control information according to the sum of the bit widths of the fields;

[0386] If transform precoding is disabled, the terminal device determines the size of the downlink control information as X3 based on the RRC configuration;

[0387] If transform precoding is disabled, the terminal device determines the bit width M1(i) of each field included in the downlink control information according to the RRC configuration, and takes the sum of the bit width M1(i) of each field included in the downlink control information as the size of the downlink control information.

[0388] Optionally, the device further comprises at least one of the following:

[0389] The downlink control information includes a dynamic waveform switching indication;

[0390] The different waveforms include CP-OFDM and / or DFT-S-OFDM.

[0391] Optionally, the device further comprises at least one of the following:

[0392] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, the terminal device uses the N(i) least significant bits to decode the field, and / or, if greater, uses the field width M(i) as the low M(i) bits of the field for decoding, where i is the index of each DCI field;

[0393] If the field width N(i) corresponding to the indicated waveform is less than or equal to the field width M(i) set according to the preset policy, the terminal device uses the N(i) most significant bits to decode the field, and / or, if greater, uses the field width M(i) as the high M(i) bits of the field for decoding, where i is the index of each DCI field;

[0394] If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset strategy, the terminal device uses the N least significant bits to decode the downlink control information, and the remaining downlink control information bits are filled with zeros.

[0395] An embodiment of the present application also provides a communication system, comprising: a terminal device described in any of the above embodiments, and a network device described in any of the above embodiments.

[0396] An embodiment of the present application also provides a communication device, comprising: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the processing method described in any of the above embodiments.

[0397] The communication equipment mentioned in this application can be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified in the context.

[0398] An embodiment of the present application further provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processing method described in any of the above embodiments is implemented.

[0399] In the embodiments of the communication device and storage medium provided in the embodiments of the present application, all technical features of any of the above-mentioned processing method embodiments may be included. The expanded and explained contents of the specification are basically the same as those of the embodiments of the above-mentioned methods and will not be repeated here.

[0400] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the methods in the various possible implementation modes described above.

[0401] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

[0402] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0403] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0404] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0405] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0406] In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous relevant detailed descriptions.

[0407] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0408] The various technical features of the technical solution of this application can be combined arbitrarily. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0409] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as mentioned above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the method of each embodiment of the present application.

[0410] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0411] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A processing method, wherein: Includes steps: S20: Determine the size of the downlink control information based on a preset strategy, wherein the downlink control information is used to indicate that uplink transmission uses different waveforms, and the sizes of the downlink control information indicating different waveforms are consistent.

2. The method according to claim 1, wherein: The preset strategy includes at least one of the following: The size of the downlink control information is set to the maximum value between the size when the conversion precoding is disabled and the size when the conversion precoding is enabled; The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when the conversion precoding is disabled and the sum of the bit widths of each field when the conversion precoding is enabled; The size of the downlink control information is set to the sum of the bit widths of the fields contained in the downlink control information, wherein the bit width of each field is set to the maximum value between the bit width when conversion precoding is disabled and the bit width when conversion precoding is enabled.

3. The method according to claim 2, wherein: The preset strategy includes at least one of the following: If the conversion precoding is disabled, the size of the downlink control information is determined to be X1 according to the RRC configuration. If the conversion precoding is enabled, the size of the downlink control information is determined to be X2 according to the RRC configuration. The larger value of X1 and X2 is selected as the size of the downlink control information. If conversion precoding is disabled, the bit width of each domain included in the downlink control information is determined to be M1(i) according to the RRC configuration; if conversion precoding is enabled, the bit width of each domain is determined to be M2(i) according to the RRC configuration, and the larger value of M1(i) and M2(i) is selected as the bit width of each domain of the downlink control information, and the size of the downlink control information is determined according to the sum of the bit widths of each domain; if conversion precoding is disabled, the size of the downlink control information is determined to be X3 according to the RRC configuration; If conversion precoding is disabled, the bit width M1(i) of each field included in the downlink control information is determined according to the RRC configuration, and the sum of the bit width M1(i) of each field included in the downlink control information is used as the size of the downlink control information.

4. The method according to claim 1, wherein: Also includes at least one of the following: The downlink control information includes a dynamic waveform switching indication; The different waveforms include CP-OFDM and / or DFT-S-OFDM.

5. The method according to claim 1, wherein: The method further comprises the steps of: S30: Decode the field included in the downlink control information.

6. The method according to claim 5, characterized in that The step S30 includes at least one of the following: If the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the preset strategy, the domain is decoded using the N(i) least significant bits, and / or, if greater, the domain bit width M(i) is decoded as the lower M(i) bits of the domain; If the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the preset strategy, the domain is decoded using the N(i) most significant bits, and / or, if greater, the domain bit width M(i) is decoded as the high M(i) bits of the domain; If the domain bit width N(i) corresponding to the indicated waveform is smaller than the domain bit width M(i) set according to the preset strategy, the M(i)-N(i) most significant bits are ignored; If the domain bit width N(i) corresponding to the indicated waveform is smaller than the domain bit width M(i) set according to the preset strategy, M(i)-N(i) least significant bits are ignored; If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset strategy, the downlink control information is decoded using the N least significant bits, and the remaining downlink control information bits are zero.

7. A processing method, wherein: Includes steps: S10, sending downlink control information, setting or determining the size of the downlink control information based on a preset strategy, wherein the downlink control information is used to indicate that uplink transmission uses different waveforms, indicating that the sizes of the downlink control information of different waveforms are consistent.

8. The method according to claim 7, characterized in that The preset strategy includes at least one of the following: The size of the downlink control information is set to the maximum value between the size when the conversion precoding is disabled and the size when the conversion precoding is enabled; The size of the downlink control information is set to the maximum value between the sum of the bit widths of each field included in the downlink control information when the conversion precoding is disabled and the sum of the bit widths of each field when the conversion precoding is enabled; The size of the downlink control information is set to the sum of the bit widths of the fields contained in the downlink control information, wherein the bit width of each field is set to the maximum value between the bit width when conversion precoding is disabled and the bit width when conversion precoding is enabled.

9. The method according to claim 8, wherein: The preset strategy includes at least one of the following: If the conversion precoding is disabled, the size of the downlink control information is determined to be X1 according to the RRC configuration. If the conversion precoding is enabled, the size of the downlink control information is determined to be X2 according to the RRC configuration. The larger value of X1 and X2 is selected as the size of the downlink control information. If conversion precoding is disabled, determining according to the RRC configuration that the bit width of each field included in the downlink control information is M1(i); if conversion precoding is enabled, determining according to the RRC configuration that the bit width of each field is M2(i), selecting a larger value between M1(i) and M2(i) as the bit width of each field of the downlink control information, and setting or determining the size of the downlink control information according to the sum of the bit widths of each field; If the conversion precoding is disabled, the terminal device determines the size of the downlink control information as X3 according to the RRC configuration; If conversion precoding is disabled, the terminal device determines the bit width M1(i) of each field included in the downlink control information according to the RRC configuration, and takes the sum of the bit width M1(i) of each field included in the downlink control information as the size of the downlink control information.

10. The method according to claim 7, wherein: The method further comprises at least one of the following: The downlink control information includes a dynamic waveform switching indication; The different waveforms include CP-OFDM and / or DFT-S-OFDM.

11. The method according to claim 7, wherein: The method further comprises at least one of the following: If the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the preset policy, the terminal device uses the N(i) least significant bits to decode the domain, and / or, if greater, uses the domain bit width M(i) as the lower M(i) bits of the domain for decoding; If the domain bit width N(i) corresponding to the indicated waveform is less than or equal to the domain bit width M(i) set according to the preset policy, the terminal device uses the N(i) most significant bits to decode the domain, and / or, if greater, uses the domain bit width M(i) as the high M(i) bits of the domain for decoding; If the downlink control information size N corresponding to the indicated waveform is smaller than the downlink control information size M set according to the preset strategy, the terminal device uses the N least significant bits to decode the downlink control information and adds zeros to the remaining downlink control information bits.

12. A communication device, wherein: include: A memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the processing method according to claim 1 or 7 is implemented.

13. A storage medium, wherein: The storage medium stores a computer program, and when the computer program is executed by the processor, the processing method according to claim 1 or 7 is implemented.