Sequence type determination method, terminal and network side device

Abstract

The application discloses a sequence type determination method and device, a terminal and a network side equipment, and belongs to the technical field of communication. The sequence type determination method of the application comprises the following steps: a terminal sends first capability information to a network side equipment, wherein the first capability information is used for indicating one or more first target sequence types supported by the terminal; the terminal receives parameter configuration information sent by the network side equipment; and the terminal determines one second target sequence type used by the terminal for transmitting a DMRS of a target PUCCH based on the parameter configuration information, wherein the one second target sequence type is one of the one or more first target sequence types; and the number of PRBs of the target PUCCH is greater than or equal to 1.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a sequence type determination method, a terminal, and a network-side device. Background Technology

[0002] The demodulation reference signal (DMRS) sequence can be generated using low peak-to-average power ratio (low-PAPR) to generate type 1 sequences and low PAPR to generate type 2 sequences.

[0003] However, it is unclear how to configure and use the enhanced Physical Uplink Control Channel (PUCCH) format 4-DMRS sequence introduced in the Frequency range 2-2 (FR2-2) band, i.e., the PUCCH format 4-DMRS sequence extended from one Physical Resource Block (PRB) to multiple PRBs. This makes it impossible to realize the transmission of Physical Uplink Control Channel (PUCCH) DMRS. Summary of the Invention

[0004] This application provides a sequence type determination method, a terminal, and a network-side device, which can solve the problem that DMRS transmission of PUCCH cannot be realized.

[0005] Firstly, a method for determining sequence type is provided, the method comprising:

[0006] The terminal sends first capability information to the network-side device, the first capability information being used to indicate one or more first target sequence types supported by the terminal;

[0007] The terminal receives parameter configuration information sent by the network-side device;

[0008] Based on the parameter configuration information, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS, wherein the second target sequence type is one of the one or more first target sequence types;

[0009] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0010] Secondly, a method for determining sequence type is provided, the method comprising:

[0011] The network-side device receives the first capability information sent by the terminal;

[0012] Based on the first capability information, the network-side device determines one or more first target sequence types supported by the terminal;

[0013] The network-side device sends parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0014] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0015] Thirdly, a sequence type determining apparatus is provided, the apparatus comprising:

[0016] The first sending module is used to send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0017] The first receiving module is used to receive parameter configuration information sent by the network-side device;

[0018] The first determining module is configured to determine, based on the parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH via DMRS, wherein the second target sequence type is one of the one or more first target sequence types;

[0019] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0020] Fourthly, a sequence type determination apparatus is provided, the apparatus comprising:

[0021] The second receiving module is used to receive the first capability information sent by the terminal.

[0022] The second determining module is used to determine one or more first target sequence types supported by the terminal based on the first capability information;

[0023] The second sending module is used to send parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0024] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0025] Fifthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0026] Sixthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0027] Send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0028] Receive parameter configuration information sent by network-side devices;

[0029] The processor is used for:

[0030] Based on the parameter configuration information, a second target sequence type is determined for the DMRS used by the terminal to transmit the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0031] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0032] In a seventh aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0033] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0034] The first capability information sent by the receiving terminal;

[0035] The processor is used for:

[0036] Based on the first capability information, determine one or more first target sequence types supported by the terminal;

[0037] The communication interface is also used for:

[0038] Send parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0039] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0040] A ninth aspect provides a sequence type determination system, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the sequence type determination method as described in the first aspect, and the network-side device can be used to perform the steps of the sequence type determination method as described in the second aspect.

[0041] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0042] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0043] In a twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the sequence type determination method as described in the first aspect, or to implement the steps of the sequence type determination method as described in the second aspect.

[0044] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS. Attached Figure Description

[0045] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied;

[0046] Figure 2 This is one of the flowcharts illustrating the sequence type determination method provided in the embodiments of this application;

[0047] Figure 3 This is a second flowchart illustrating the sequence type determination method provided in the embodiments of this application;

[0048] Figure 4 This is one of the structural schematic diagrams of the sequence type determination device provided in the embodiments of this application;

[0049] Figure 5 This is a second schematic diagram of the sequence type determination device provided in the embodiments of this application;

[0050] Figure 6 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0051] Figure 7 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application;

[0052] Figure 8 A schematic diagram of the hardware structure of a network-side device to implement an embodiment of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0054] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0055] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0056] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0057] The sequence type determination method, apparatus, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0058] First, let's introduce the following content:

[0059] In existing communication systems, PUCCH format 4-DMRS sequences support low peak-to-average power ratio (low-PAPR) sequence generation type 1.

[0060] For PUCCH format 4, which uses Discrete Fourier Transform (DFT) precoding, when PUCCH is configured with π / 2-BPSK modulation, the peak-to-average power ratio (PAPR) of the Orthogonal Frequency Division Multiplexing (OFDM) symbols is lower than that of the OFDM symbols in DMRS. Therefore, different OFDM symbols will have different PAPRs, affecting the PUCCH's reception and demodulation performance. Thus, a low-PAPR sequence can be introduced to generate type 2. When PUCCH is configured with π / 2-BPSK modulation, the PAPR of the type 2 sequence is lower than that of the type 1 sequence. However, the type 2 sequence does not support multiplexing transmission of the same time-frequency resources by different users. When the parameter dmrs-UplinkTransformPrecodingPUCCH is configured and the parameter pi2BPSK is used to indicate that π / 2-BPSK modulation is used for PUCCH format 4, then the sequence for PUCCH format 4 uses a type 2 sequence; otherwise, a type 1 sequence is used. The parameter dmrs-UplinkTransformPrecodingPUCCH is configured per PUCCH format, and the parameter pi2BPSK is configured per UE. When the UE's reporting capability is configured with the higher-layer parameter lowPAPR-DMRS-PUCCH, it means that the UE has the ability to use a type 2 sequence if it meets the conditions of PUCCH format 4-DMRS configuration for DFT precoding and π / 2-BPSK modulation.

[0061] For sequences of PUCCH format 4-DMRS (PF4 extended from one PRB to multiple PRBs) enhanced in Frequency range 2-2 (FR2-2), type 2 sequences can be used when the parameters dmrs-UplinkTransformPrecodingPUCCH and pi2BPSK are configured. When pi / 2-BPSK is not configured, type 1 sequences can be used. UE capabilities include configuring the multi-PRB parameter for different SCSs, including 120kHz / 480kHz / 960kHz, indicating that the UE supports the PUCCH format of the multi-PRB corresponding to that SCS.

[0062] However, it is currently unclear how to configure and use sequences of PUCCH format 4-DMRS that are expanded from a single Physical Resource Block (PRB) to multiple PRBs. To overcome this deficiency, embodiments of this application propose a sequence type determination method, apparatus, terminal, and network-side device.

[0063] Figure 2 This is one of the flowcharts illustrating the sequence type determination method provided in the embodiments of this application, such as... Figure 2 As shown, the method includes the following steps 201 to 203:

[0064] Step 201: The terminal sends first capability information to the network-side device, the first capability information being used to indicate one or more first target sequence types supported by the terminal;

[0065] Step 202: The terminal receives parameter configuration information sent by the network-side device;

[0066] Step 203: Based on the parameter configuration information, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS, wherein the second target sequence type is one of the one or more first target sequence types;

[0067] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0068] Optionally, the terminal may send first capability information to the network-side device;

[0069] Optionally, the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0070] Optionally, after receiving the first capability information, the network-side device can learn about one or more first target sequence types supported by the terminal;

[0071] Optionally, the network-side device can send parameter configuration information to the terminal;

[0072] Optionally, after receiving the parameter configuration information, the terminal can determine the specific second target sequence type to be used when transmitting the DMRS of the target PUCCH based on the parameter configuration information; thereby ensuring that the terminal and the network-side device have a consistent understanding of the enhanced PUCCH-DMRS sequence; clarifying that the Type 1 sequence can be used, and clarifying whether the Type 2 sequence is supported and used.

[0073] Optionally, the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS is one of one or more first target sequence types supported by the terminal.

[0074] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0075] Optionally, the first target sequence type includes at least one of the following:

[0076] Low PAPR sequence generation type Type 1;

[0077] Low PAPR sequence generation type Type 2;

[0078] Determining the second target sequence type used by the terminal for transmitting the target PUCCH via DMRS includes:

[0079] The terminal determines that the type of the second target sequence includes Type 1; or

[0080] The terminal determines that the type of the second target sequence includes Type 2.

[0081] Optionally, if the first target sequence type supported by the terminal may include Type1, then the second target sequence type used by the DMRS for transmitting the target PUCCH may include Type1.

[0082] Optionally, if the first target sequence type supported by the terminal may include Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type2.

[0083] Optionally, if the first target sequence type supported by the terminal may include Type1 and Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type1;

[0084] Optionally, if the first target sequence type supported by the terminal may include Type1 and Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type2.

[0085] Optionally, the parameter configuration information includes at least one of the following:

[0086] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0087] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0088] Optionally, the parameter configuration information can be high-level configuration parameters.

[0089] Optionally, the parameter configuration information may include first indication information for indicating that the target PUCCH adopts pi2 BPSK modulation, such as pi2BPSK;

[0090] Optionally, the parameter configuration information may include a second indication information for indicating that the DMRS of the target PUCCH adopts DFT precoding, such as dmrs-UplinkTransformPrecodingPUCCH;

[0091] Optionally, the parameter configuration information may include first indication information for indicating that the PUCCH DMRS adopts pi2 BPSK modulation and second indication information for indicating that the DMRS of the target PUCCH adopts DFT precoding.

[0092] Optionally, pi2 BPSK modulation, also known as π / 2BPSK modulation, where BPSK stands for Binary Phase Shift Keying.

[0093] Optionally, the terminal determines that the second target sequence type includes Type 2, including:

[0094] When the parameter configuration information includes first indication information and second indication information, the terminal determines that the second target sequence type includes Type 2.

[0095] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured simultaneously, or one parameter can be configured only if the other is a prerequisite.

[0096] Optionally, if the terminal determines that the parameter configuration information includes first indication information and second indication information, it may determine that the second target sequence type includes Type 2.

[0097] For example, if the terminal determines that both pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured, it can determine that the second target sequence type includes Type 2.

[0098] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0099] In this case, the terminal can determine that the second target sequence type includes Type 2 if the parameter configuration information includes both the first indication information and the second indication information.

[0100] For example, if the terminal determines that the second target sequence type includes Type 2, given that pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured.

[0101] Optionally, the terminal determines that the second target sequence type includes Type 2, including:

[0102] If the parameter configuration information does not include the first indication information but includes the second indication information, the terminal determines that the second target sequence type includes Type 2.

[0103] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0104] Optionally, the terminal may determine that the second target sequence type includes Type 2 if the parameter configuration information does not include the first indication information but includes the second indication information, or consider this an error situation (the terminal does not expect this configuration).

[0105] For example, if the terminal determines that the second target sequence type includes Type 2 when it finds that pi2BPSK is not configured but dmrs-UplinkTransformPrecodingPUCCH is configured, or considers this an error (the terminal does not expect this configuration).

[0106] Optionally, the terminal may determine that the second target sequence type includes Type 2 if it determines that the parameter configuration information does not include the first indication information but includes the second indication information.

[0107] For example, if the terminal determines that the second target sequence type includes Type 2, but pi2BPSK is not configured, but dmrs-UplinkTransformPrecodingPUCCH is configured.

[0108] Optionally, the terminal determines that the second target sequence type includes Type 1, including:

[0109] If the parameter configuration information includes first indication information but does not include second indication information, the terminal determines that the second target sequence type includes Type 1.

[0110] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0111] Optionally, if the terminal determines that the second target sequence type includes Type 1, or considers it an error (the terminal does not expect this configuration) if the parameter configuration information includes the first indication information but does not include the second indication information.

[0112] For example, if the terminal determines that the second target sequence type includes Type 1, or considers this an error (the terminal does not expect this configuration) when it determines that pi2BPSK is configured but dmrs-UplinkTransformPrecodingPUCCH is not configured.

[0113] Optionally, the terminal determines that the second target sequence type includes Type 1, including:

[0114] If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the terminal determines that the second target sequence type includes Type 1.

[0115] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured simultaneously, or one parameter can be configured only if the other is a prerequisite.

[0116] Optionally, if the terminal determines that the second target sequence type includes Type 1 if it determines that the parameter configuration information does not include either the first indication information or the second indication information.

[0117] For example, the terminal can determine that the second target sequence type includes Type 1 if neither pi2BPSK nor dmrs-UplinkTransformPrecodingPUCCH is configured.

[0118] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0119] Optionally, the terminal may determine that the second target sequence type includes Type 1 if it is determined that the parameter configuration information does not include the first indication information and does not include the second indication information.

[0120] For example, if the terminal determines that the second target sequence type includes Type 1, it can do so if it determines that pi2BPSK is not configured and dmrs-UplinkTransformPrecodingPUCCH is not configured.

[0121] In one embodiment, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured simultaneously, or one parameter can be configured on the condition that the other parameter is configured.

[0122] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 2 if it determines that the parameter configuration information includes first indication information and second indication information.

[0123] For example, if the terminal determines that both pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured, it can determine that the second target sequence type includes Type 2.

[0124] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 1 if it determines that the parameter configuration information does not include either the first indication information or the second indication information.

[0125] For example, the terminal can determine that the second target sequence type includes Type 1 if neither pi2BPSK nor dmrs-UplinkTransformPrecodingPUCCH is configured.

[0126] In this embodiment of the application, the terminal may consider it an error situation, i.e., the terminal does not expect this configuration, if it determines that the parameter configuration information only includes the first indication information and does not include the second indication information, or only includes the second indication information and does not include the first indication information.

[0127] For example, if one of the parameters pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH is configured while the other is not, the terminal considers this an error, meaning that the terminal does not expect this configuration.

[0128] In one embodiment, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0129] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 2 if the parameter configuration information does not include the first indication information but includes the second indication information, or consider this to be an error situation (the terminal does not expect this configuration).

[0130] For example, if the terminal determines that the second target sequence type includes Type 2 when it finds that pi2BPSK is not configured but dmrs-UplinkTransformPrecodingPUCCH is configured, or considers this an error (the terminal does not expect this configuration).

[0131] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 1 if the parameter configuration information includes the first indication information but does not include the second indication information, or consider this to be an error situation (the terminal does not expect this configuration).

[0132] For example, if the terminal determines that the second target sequence type includes Type 1, or considers this an error (the terminal does not expect this configuration) when it determines that pi2BPSK is configured but dmrs-UplinkTransformPrecodingPUCCH is not configured.

[0133] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 2 if it determines that the parameter configuration information does not include the first indication information but includes the second indication information.

[0134] For example, if the terminal determines that the second target sequence type includes Type 2, but pi2BPSK is not configured, but dmrs-UplinkTransformPrecodingPUCCH is configured.

[0135] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 1 if it determines that the parameter configuration information includes first indication information but does not include second indication information.

[0136] For example, if the terminal determines that the second target sequence type includes Type 1, even if it has determined that pi2BPSK is configured but dmrs-UplinkTransformPrecodingPUCCH is not configured.

[0137] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 2 if it determines that the parameter configuration information includes both first indication information and second indication information.

[0138] For example, if the terminal determines that the second target sequence type includes Type 2, given that pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured.

[0139] In this embodiment of the application, the terminal may determine that the second target sequence type includes Type 1 if it is determined that the parameter configuration information does not include the first indication information and does not include the second indication information.

[0140] For example, if the terminal determines that the second target sequence type includes Type 1, it can do so if it determines that pi2BPSK is not configured and dmrs-UplinkTransformPrecodingPUCCH is not configured.

[0141] Optionally, the method further includes:

[0142] The terminal does not expect the parameter configuration information to include only the first indication information or only the second indication information.

[0143] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured simultaneously, or one parameter can be configured only if the other is a prerequisite.

[0144] Optionally, the terminal may consider this an error situation, i.e., the terminal does not expect this configuration, if it determines that the parameter configuration information only includes the first indication information and does not include the second indication information, or only includes the second indication information and does not include the first indication information.

[0145] For example, if one of the parameters pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH is configured while the other is not, the terminal considers this an error, meaning that the terminal does not expect this configuration.

[0146] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0147] Optionally, the terminal may consider it an error (the terminal does not expect this configuration) if it determines that the parameter configuration information does not include the first indication information but includes the second indication information.

[0148] For example, if a terminal determines that pi2BPSK is not configured but dmrs-UplinkTransformPrecodingPUCCH is configured, it may consider this an error situation (which the terminal does not expect).

[0149] Optionally, the terminal may consider this an error situation (the terminal does not expect this configuration) if it determines that the parameter configuration information includes the first indication information but does not include the second indication information.

[0150] For example, if a terminal determines that pi2BPSK is configured but dmrs-UplinkTransformPrecodingPUCCH is not configured, it may consider this an error (the terminal does not expect this configuration).

[0151] Optionally, the terminal does not expect the parameter configuration information to include only the first indication information or only the second indication information. This may mean that the terminal considers it an error or erroneous scenario that the parameter configuration information includes only the first indication information or only the second indication information. In such an erroneous scenario, the terminal may determine the second target sequence type on its own, or resend the first capability information to obtain new parameter configuration information, or send one bit of indication information to inform the network-side device that an erroneous scenario has been encountered in order to obtain new parameter configuration information.

[0152] Optionally, the first capability information includes sequence type indication information;

[0153] The first target sequence type includes Type 1 and Type 2. Type 1 is the first target sequence type supported by default by the terminal, and the sequence type indication information is used to indicate that the terminal supports Type 2.

[0154] Optionally, the terminal may support Type 1 by default;

[0155] Optionally, the terminal may support Type 1 by default but not Type 2, in which case it may not report the sequence type indication information, and the network-side device may determine that the terminal supports Type 1 but not Type 2.

[0156] Optionally, the terminal may support Type 1 by default, and if it supports Type 2, it may report sequence type indication information, and the network-side device may then determine that the terminal supports both Type 1 and Type 2.

[0157] In this case, the network side can send parameter configuration information to enable the terminal to further determine the type of the second target sequence used;

[0158] For example, if Type 1 is supported by default and Type 2 is also supported, the parameter configuration information can include the first indication information, such as configuring pi2BPSK, but not the second indication information, such as not configuring dmrs-UplinkTransformPrecodingPUCCH, to determine the sequence type to be used by the terminal, including Type 1.

[0159] For example, if Type 1 is supported by default and Type 2 is also supported, the parameter configuration information can include the first indication information, such as configuring pi2BPSK, and the second indication information, such as configuring dmrs-UplinkTransformPrecodingPUCCH, to determine that the sequence type to be used by the terminal includes Type 2.

[0160] For example, if Type 1 is supported by default and Type 2 is also supported, the parameter configuration information may not include the first indication information, such as not configuring pi2BPSK, but may include the second indication information, such as configuring dmrs-UplinkTransformPrecodingPUCCH, to determine that the sequence type to be used by the terminal includes Type 2.

[0161] For example, if Type 1 is supported by default and Type 2 is also supported, the parameter configuration information may not include the first indication information, such as pi2BPSK not being configured, and it may not include the second indication information, such as dmrs-UplinkTransformPrecodingPUCCH not being configured, thus determining that the sequence type to be used by the terminal includes Type 1.

[0162] Optionally, the sequence type indication information can be "lowPAPR–DMRS–PUCCH", which can be an extension of the UE capability information "lowPAPR–DMRS–PUCCH" in the existing protocol scheme. In the existing scheme, PUCCH format 4 can only indicate the PUCCH of one PRB, but in this application embodiment, it can indicate the PUCCH of one or more PRBs. The sequence type indication information can also be new UE capability information or new signaling in this application embodiment, which only indicates the PUCCH of multiple PRBs.

[0163] Optionally, the first capability information includes first type indication information, which indicates that the first target sequence type includes Type 1.

[0164] Optionally, the terminal may indicate, through the first capability information, that the first target sequence type supported by the terminal includes Type 1;

[0165] Optionally, the terminal may indicate that the first target sequence type supported by the terminal includes Type 1 by indicating the first type indication information.

[0166] Optionally, the first type of indication information can be "lowPAPR-DMRS-PUCCH-type1", which can be an extension of the UE's capability information "lowPAPR-DMRS-PUCCH" in the existing protocol scheme. In the existing scheme, PUCCH format 4 can only indicate the PUCCH of one PRB, but in this application embodiment, it can indicate the PUCCH of one or more PRBs. The first type of indication information can also be new capability information of the UE in this application embodiment, or new signaling, which only indicates the PUCCH of multiple PRBs.

[0167] Optionally, the first capability information further includes second type indication information, which indicates that the first target sequence type also includes Type 2.

[0168] Optionally, if the terminal indicates through the first capability information that the first target sequence type supported by the terminal includes Type 1, and if the terminal also supports Type 2, the first capability information may also include second type indication information.

[0169] Optionally, the first capability information may include first type indication information and second type indication information to indicate that the first target sequence types supported by the terminal include Type 1 and Type 2;

[0170] In this case, the network side can send parameter configuration information to enable the terminal to further determine the type of the second target sequence used;

[0171] For example, if the first capability information includes the first type indication information and the second type indication information, and the parameter configuration information includes the first indication information (e.g., pi2BPSK is configured), but does not include the second indication information (e.g., dmrs-UplinkTransformPrecodingPUCCH is not configured), then the sequence type to be used by the terminal can be determined to include Type 1.

[0172] For example, if the first capability information includes first type indication information and second type indication information, and the parameter configuration information includes the first indication information (e.g., pi2BPSK is configured) and includes the second indication information (e.g., dmrs-UplinkTransformPrecodingPUCCH is configured), then the sequence type to be used by the terminal can be determined to include Type2.

[0173] For example, if the first capability information includes first type indication information and second type indication information, the parameter configuration information may not include the first indication information, such as not configuring pi2BPSK, but may include the second indication information, such as configuring dmrs-UplinkTransformPrecodingPUCCH, thus determining that the sequence type to be used by the terminal includes Type 2.

[0174] For example, if the first capability information includes first type indication information and second type indication information, but the parameter configuration information does not include the first indication information (e.g., pi2BPSK is not configured) and does not include the second indication information (e.g., dmrs-UplinkTransformPrecodingPUCCH is not configured), then it can be determined that the sequence type to be used by the terminal includes Type 1.

[0175] Optionally, the second type of indication information can be "lowPAPR–DMRS–PUCCH-type2", which can be an extension of the UE's capability information "lowPAPR–DMRS–PUCCH" in the existing protocol scheme. In the existing scheme, PUCCH format 4 can only indicate the PUCCH of one PRB, but in this application embodiment, it can indicate the PUCCH of one or more PRBs. The second type of indication information can also be new capability information of the UE in this application embodiment, or new signaling, which only indicates the PUCCH of multiple PRBs.

[0176] Optionally, the terminal is in a first frequency band;

[0177] The first frequency band includes at least one of the following:

[0178] FR2-2 band;

[0179] The unlicensed frequency band of FR2-2.

[0180] Optionally, when the UE is in a specific frequency band, such as the FR2-2 band or the unlicensed FR2-2 band, the sequence type method of the various embodiments of this application can be applied to determine the first target sequence type and the second target sequence type.

[0181] Optionally, the terminal in this application embodiment can be in a specific frequency band, namely the first frequency band;

[0182] Optionally, the terminal can be in the FR2-2 frequency band;

[0183] Optionally, the terminal can operate in the unlicensed frequency band of FR2-2.

[0184] Optionally, the first capability information is further used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0185] The target PUCCH includes the PUCCH of multiple PRBs corresponding to the target SCS.

[0186] Optionally, the first capability information is also used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0187] Optionally, the sequence type determination method provided in the embodiments of this application can be applied to PUCCH with multiple PRBs;

[0188] Optionally, the first capability information can indicate that the number of PRBs of the PUCCH corresponding to at least one target SCS is greater than 1. If so, the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type.

[0189] Optionally, if the first capability information does not indicate that the number of PRBs supporting a certain SCS corresponding to a PUCCH is greater than 1, then the DMRS of the PUCCH corresponding to that SCS can use an existing scheme to determine the sequence type.

[0190] Optionally, if the first capability information does not indicate that the number of PRBs supporting a certain SCS corresponding to a PUCCH is greater than 1, then the DMRS of the PUCCH corresponding to that SCS can be determined by the sequence type determination method provided in the embodiments of this application to determine the first target sequence type and the second target sequence type.

[0191] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0192] The PUCCH that meets the first condition includes at least one of the following:

[0193] PUCCH in a default format;

[0194] A PUCCH containing a preset number of PRBs.

[0195] Optionally, when PUCCH is in a specific format, such as PUCCH format 4, the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type.

[0196] Optionally, when the PUCCH contains a specific number of PRBs, the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type;

[0197] Optionally, the target PUCCH may be a PUCCH that meets the first condition, and the first target sequence type and the second target sequence type are determined by the sequence type determination method provided in the embodiments of this application;

[0198] Alternatively, for PUCCHs that do not meet the first condition, existing schemes can be used to determine the sequence type.

[0199] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0200] Figure 3 This is a second flowchart illustrating the sequence type determination method provided in this application embodiment, such as... Figure 3 As shown, the method includes the following steps 301 to 303:

[0201] Step 301: The network-side device receives the first capability information sent by the terminal;

[0202] Step 302: The network-side device determines one or more first target sequence types supported by the terminal based on the first capability information;

[0203] Step 303, the network-side device sends parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0204] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0205] Optionally, the network-side device may receive the first capability information sent by the terminal;

[0206] Optionally, the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0207] Optionally, after receiving the first capability information, the network-side device can learn about one or more first target sequence types supported by the terminal;

[0208] Optionally, the network-side device can send parameter configuration information to the terminal;

[0209] Optionally, after receiving the parameter configuration information, the terminal can determine the specific second target sequence type to be used when transmitting the DMRS of the target PUCCH based on the parameter configuration information; thereby ensuring that the terminal and the network-side device have a consistent understanding of the enhanced PUCCH-DMRS sequence; clarifying that the Type 1 sequence can be used, and clarifying whether the Type 2 sequence is supported and used.

[0210] Optionally, the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS is one of one or more first target sequence types supported by the terminal.

[0211] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0212] Optionally, the network-side device determines one or more first target sequence types supported by the terminal based on the first capability information, including at least one of the following:

[0213] The network-side device determines that the type of the first target sequence includes Type 1;

[0214] Based on the first capability information, the network-side device determines that the first target sequence type includes Type2.

[0215] Optionally, the network-side device may determine that the first target sequence type includes Type 1 based on the first capability information or based on a default setting;

[0216] Optionally, the network-side device may determine that the type of the first target sequence includes Type 2 based on the first capability information;

[0217] Optionally, if the network-side device determines that the first target sequence type supported by the terminal may include Type1, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type1.

[0218] Optionally, if the network-side device determines that the first target sequence type supported by the terminal may include Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type2.

[0219] Optionally, if the network-side device determines that the first target sequence type supported by the terminal may include Type1 and Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH in the DMRS may include Type1.

[0220] Optionally, if the network-side device determines that the first target sequence type supported by the terminal may include Type1 and Type2, then the second target sequence type used by the terminal for transmitting the target PUCCH DMRS may include Type2.

[0221] Optionally, determining the type of the first target sequence includes Type 1, which includes:

[0222] The network-side device determines that the first target sequence type includes Type 1 by default.

[0223] Optionally, the terminal may support Type 1 by default.

[0224] Optionally, determining the type of the first target sequence includes Type 2, which includes:

[0225] If the network-side device determines that the first capability information includes sequence type indication information, the target sequence type includes Type 2.

[0226] Optionally, the terminal may support Type 1 by default but not Type 2. In this case, the terminal may not report the sequence type indication information, and the network-side device may determine that the terminal supports Type 1 but not Type 2.

[0227] Optionally, the terminal may support Type 1 by default, and if it supports Type 2, the terminal reports sequence type indication information, and the network-side device can then determine that the terminal supports both Type 1 and Type 2.

[0228] Optionally, determining the type of the first target sequence includes Type 1, which includes:

[0229] If the network-side device determines that the first capability information includes first type indication information, the target sequence type includes Type 1.

[0230] Optionally, the terminal may indicate, through the first capability information, that the first target sequence type supported by the terminal includes Type 1;

[0231] Optionally, the terminal may indicate that the first target sequence type supported by the terminal includes Type 1 by indicating the first type indication information.

[0232] Optionally, the network-side device may determine that the target sequence type includes Type 1 if it determines that the first capability information includes first type indication information.

[0233] Optionally, the first type of indication information can be "lowPAPR-DMRS-PUCCH-type1", which can be an extension of the UE's capability information "lowPAPR-DMRS-PUCCH" in the existing protocol scheme. In the existing scheme, PUCCH format 4 can only indicate the PUCCH of one PRB, but in this application embodiment, it can indicate the PUCCH of one or more PRBs. The first type of indication information can also be new capability information of the UE in this application embodiment, or new signaling, which only indicates the PUCCH of multiple PRBs.

[0234] Optionally, determining the type of the first target sequence includes Type 2, which includes:

[0235] If the network-side device determines that the target sequence type includes Type 2 when it determines that the first capability information includes second type indication information.

[0236] Optionally, if the terminal indicates through the first capability information that the first target sequence type supported by the terminal includes Type 1, and if the terminal also supports Type 2, the first capability information may also include second type indication information.

[0237] Optionally, the first capability information may include first type indication information and second type indication information to indicate that the first target sequence types supported by the terminal include Type 1 and Type 2;

[0238] In this case, the network side can send parameter configuration information to enable the terminal to further determine the type of the second target sequence used;

[0239] Optionally, if the network-side device determines that the first capability information includes first type indication information and second type indication information, the target sequence type includes Type 1 and Type 2.

[0240] Optionally, the second type of indication information can be "lowPAPR–DMRS–PUCCH-type2", which can be an extension of the UE's capability information "lowPAPR–DMRS–PUCCH" in the existing protocol scheme. In the existing scheme, PUCCH format 4 can only indicate the PUCCH of one PRB, but in this application embodiment, it can indicate the PUCCH of one or more PRBs. The second type of indication information can also be new capability information of the UE in this application embodiment, or new signaling, which only indicates the PUCCH of multiple PRBs.

[0241] Optionally, the parameter configuration information is empty, or the parameter configuration information includes at least one of the following:

[0242] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0243] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0244] Optionally, the parameter configuration information may include first indication information for indicating that the target PUCCH adopts pi2 BPSK modulation, such as pi2BPSK;

[0245] Optionally, the parameter configuration information may include a second indication information for indicating that the DMRS of the target PUCCH adopts DFT precoding, such as dmrs-UplinkTransformPrecodingPUCCH;

[0246] Optionally, the parameter configuration information may include first indication information for indicating that the target PUCCH uses pi2 BPSK modulation and second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding.

[0247] Optionally, if the parameter configuration information includes first indication information and second indication information, the second target sequence type includes Type 2.

[0248] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured simultaneously, or one parameter can be configured only if the other is a prerequisite.

[0249] Optionally, the network-side device may determine that the second target sequence type includes Type 2 if the parameter configuration information indicates that the parameter configuration information includes first indication information and second indication information.

[0250] For example, if both pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured, the network-side device can determine that the second target sequence type includes Type 2.

[0251] Optionally, the network-side device may determine that the second target sequence type includes Type 1 if the parameter configuration information indicates that neither the first indication information nor the second indication information is included.

[0252] For example, a network-side device can determine that the second target sequence type includes Type 1 even when neither pi2BPSK nor dmrs-UplinkTransformPrecodingPUCCH is configured.

[0253] Optionally, the network-side device may consider this an error situation if the parameter configuration information includes only the first indication information and not the second indication information, or only the second indication information and not the first indication information, meaning that the terminal does not expect this configuration.

[0254] For example, if one of the parameters pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH is configured while the other is not, the network-side device considers this an error, meaning it assumes the terminal does not expect this configuration.

[0255] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH are configured independently;

[0256] In this case, the network-side device can determine that the second target sequence type includes Type 2 if the instruction parameter configuration information includes both the first instruction information and the second instruction information.

[0257] For example, a network-side device may determine that the second target sequence type includes Type 2 if it is instructed to configure pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH is configured.

[0258] Optionally, if the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type includes Type 1.

[0259] Optionally, pi2BPSK and dmrs-UplinkTransformPrecodingPUCCH can be configured independently.

[0260] Optionally, the network-side device may determine that the second target sequence type includes Type 1, or consider it an error (the terminal does not expect this configuration) if the configuration parameter configuration information includes the first indication information but does not include the second indication information.

[0261] For example, if pi2BPSK is configured but dmrs-UplinkTransformPrecodingPUCCH is not configured, the network-side device may determine that the second target sequence type includes Type 1, or consider this an error (the terminal does not expect this configuration).

[0262] Optionally, if the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type includes Type 2.

[0263] Optionally, the network-side device may determine that the second target sequence type includes Type 2 if the configuration parameter configuration information does not include the first indication information but includes the second indication information, or consider this to be an error situation (the terminal does not expect this configuration).

[0264] For example, a network-side device may determine that the second target sequence type includes Type 2 even if pi2BPSK is not configured but dmrs-UplinkTransformPrecodingPUCCH is configured, or consider this an error (the terminal does not expect this configuration).

[0265] Optionally, if the parameter configuration information does not include either first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type includes Type 1.

[0266] Optionally, if the terminal determines that the second target sequence type includes Type 1 if it determines that the parameter configuration information does not include either the first indication information or the second indication information.

[0267] For example, the terminal can determine that the second target sequence type includes Type 1 if neither pi2BPSK nor dmrs-UplinkTransformPrecodingPUCCH is configured.

[0268] Optionally, the method further includes:

[0269] Based on the first capability information, the network-side device determines that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS, and determines that the target PUCCH includes a PUCCH with multiple PRBs corresponding to the target SCS.

[0270] Optionally, the first capability information is also used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0271] Optionally, the sequence type determination method provided in the embodiments of this application can be applied to a target PUCCH with multiple PRBs;

[0272] Optionally, the first capability information can indicate that the number of PRBs of the target PUCCH corresponding to any one of the target SCSs is greater than 1, and the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type.

[0273] Optionally, if the first capability information does not indicate that the number of PRBs supporting a certain SCS corresponding to a PUCCH is greater than 1, then the DMRS of the PUCCH corresponding to that SCS can use an existing scheme to determine the sequence type.

[0274] Optionally, if the first capability information does not indicate that the number of PRBs supporting a certain SCS corresponding to a PUCCH is greater than 1, then the DMRS of the PUCCH corresponding to that SCS can be determined by the sequence type determination method provided in the embodiments of this application to determine the first target sequence type and the second target sequence type.

[0275] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0276] The PUCCH that meets the first condition includes at least one of the following:

[0277] PUCCH in a default format;

[0278] A PUCCH containing a preset number of PRBs.

[0279] The first capability information is also used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0280] The target PUCCH includes the PUCCH of multiple PRBs corresponding to the target SCS.

[0281] Optionally, when PUCCH is in a specific format, such as PUCCH format 4, the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type.

[0282] Optionally, when the PUCCH contains a specific number of PRBs, the sequence type determination method provided in the embodiments of this application can be used to determine the first target sequence type and the second target sequence type;

[0283] Optionally, the target PUCCH may be a PUCCH that meets the first condition, and the first target sequence type and the second target sequence type are determined by the sequence type determination method provided in the embodiments of this application;

[0284] Alternatively, for PUCCHs that do not meet the first condition, existing schemes can be used to determine the sequence type.

[0285] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0286] The sequence type determination method provided in this application can be executed by a sequence type determination device. This application uses the execution of the sequence type determination method by a sequence type determination device as an example to illustrate the sequence type determination device provided in this application.

[0287] Figure 4 This is one of the structural schematic diagrams of the sequence type determination device provided in the embodiments of this application, such as... Figure 4 As shown, the sequence type determination device 400 includes: a first transmitting module 401, a first receiving module 402, and a first determining module 403; wherein:

[0288] The first sending module 401 is used to send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0289] The first receiving module 402 is used to receive parameter configuration information sent by the network-side device;

[0290] The first determining module 403 is used to determine a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information, wherein the second target sequence type is one of the one or more first target sequence types;

[0291] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0292] Optionally, the sequence type determination device can send first capability information to the network-side device through the first sending module 401, the first capability information being used to indicate one or more first target sequence types supported by the terminal; then, it can receive parameter configuration information sent by the network-side device through the first receiving module 402; subsequently, based on the parameter configuration information, it can determine a second target sequence type used by the terminal for transmitting the target PUCCH DMRS through the first determining module 403, wherein the second target sequence type is one of the one or more first target sequence types; wherein the number of PRBs of the target PUCCH is greater than or equal to 1.

[0293] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0294] Optionally, the first target sequence type includes at least one of the following:

[0295] Low PAPR sequence generation type Type 1;

[0296] Low PAPR sequence generation type Type 2;

[0297] The first determining module is used for:

[0298] The type of the second target sequence is determined to include Type 1; or

[0299] The type of the second target sequence is determined to include Type 2.

[0300] Optionally, the parameter configuration information includes at least one of the following:

[0301] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0302] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0303] Optionally, the first determining module is configured to:

[0304] When the parameter configuration information includes first indication information and second indication information, the second target sequence type is determined to include Type 2.

[0305] Optionally, the first determining module is configured to:

[0306] If the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type is determined to include Type 2.

[0307] Optionally, the first determining module is configured to:

[0308] If the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type is determined to include Type 1.

[0309] Optionally, the first determining module is configured to:

[0310] If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type is determined to include Type 1.

[0311] Optionally, the device further includes:

[0312] The expectation module is configured to not expect the parameter configuration information to include only the first indication information or only the second indication information.

[0313] Optionally, the first capability information includes sequence type indication information;

[0314] The first target sequence type includes Type 1 and Type 2. Type 1 is the first target sequence type supported by default by the terminal, and the sequence type indication information is used to indicate that the terminal supports Type 2.

[0315] Optionally, the first capability information includes first type indication information, which indicates that the first target sequence type includes Type 1.

[0316] Optionally, the first capability information further includes second type indication information, which indicates that the first target sequence type also includes Type 2.

[0317] Optionally, the terminal is in a first frequency band;

[0318] The first frequency band includes at least one of the following:

[0319] FR2-2 band;

[0320] The unlicensed frequency band of FR2-2.

[0321] Optionally, the first capability information is further used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0322] The target PUCCH includes the PUCCH of multiple PRBs corresponding to the target SCS.

[0323] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0324] The PUCCH that meets the first condition includes at least one of the following:

[0325] PUCCH in a default format;

[0326] A PUCCH containing a preset number of PRBs.

[0327] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0328] The sequence type determination device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0329] Figure 5This is a second schematic diagram of the sequence type determination device provided in the embodiments of this application, as shown below. Figure 5 As shown, the sequence type determination device 500 includes: a second receiving module 501, a second determining module 502, and a second sending module 503; wherein:

[0330] The second receiving module 501 is used to receive the first capability information sent by the terminal;

[0331] The second determining module 502 is used to determine one or more first target sequence types supported by the terminal based on the first capability information;

[0332] The second sending module 503 is used to send parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0333] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0334] Optionally, the sequence type determination device may receive first capability information sent by the terminal through the second receiving module 501; then, based on the first capability information, determine one or more first target sequence types supported by the terminal through the second determining module 502; subsequently, send parameter configuration information to the terminal through the second sending module 503; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types; wherein the number of PRBs of the target PUCCH is greater than or equal to 1.

[0335] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0336] Optionally, the second determining module is used for at least one of the following:

[0337] The type of the first target sequence is determined to include Type 1;

[0338] Based on the first capability information, the type of the first target sequence is determined to include Type 2.

[0339] Optionally, the second determining module is configured to:

[0340] The type of the first target sequence is determined to include Type 1 by default.

[0341] Optionally, the second determining module is configured to:

[0342] If the first capability information is determined to include sequence type indication information, then the target sequence type is determined to include Type 2.

[0343] Optionally, the second determining module is configured to:

[0344] If the first capability information is determined to include first type indication information, the target sequence type is determined to include Type 1.

[0345] Optionally, the second determining module is configured to:

[0346] If the first capability information is determined to include second type indication information, the target sequence type is determined to include Type 2.

[0347] Optionally, the parameter configuration information is empty, or the parameter configuration information includes at least one of the following:

[0348] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0349] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0350] Optionally, if the parameter configuration information includes first indication information and second indication information, the second target sequence type includes Type 2.

[0351] Optionally, if the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type includes Type 1.

[0352] Optionally, if the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type includes Type 2.

[0353] Optionally, if the parameter configuration information does not include either first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type includes Type 1.

[0354] Optionally, the device further includes:

[0355] The third determining module is used to determine, based on the first capability information, that the number of PRBs supporting the PUCCH corresponding to the target SCS is greater than 1, and to determine that the target PUCCH includes a PUCCH with multiple PRBs corresponding to the target SCS.

[0356] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0357] The PUCCH that meets the first condition includes at least one of the following:

[0358] PUCCH in a default format;

[0359] A PUCCH containing a preset number of PRBs.

[0360] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0361] The sequence type determination device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0362] The sequence type determination device provided in this application embodiment can achieve... Figures 2 to 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0363] Optional, Figure 6 This is a schematic diagram of the communication device provided in the embodiments of this application, such as... Figure 6As shown in the illustration, this application also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores programs or instructions that can run on the processor 601. For example, when the communication device 600 is a terminal, the program or instructions executed by the processor 601 implement the various steps of the above-described sequence type determination method embodiment and achieve the same technical effect. When the communication device 600 is a network-side device, the program or instructions executed by the processor 601 implement the various steps of the above-described sequence type determination method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0364] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is used for:

[0365] Send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0366] Receive parameter configuration information sent by network-side devices;

[0367] The processor is used for:

[0368] Based on the parameter configuration information, a second target sequence type is determined for the DMRS used by the terminal to transmit the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0369] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0370] This terminal embodiment corresponds to the aforementioned terminal-side method embodiment. All implementation processes and methods of the aforementioned method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 7 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0371] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0372] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 7The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0373] It should be understood that, in this embodiment, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0374] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low-noise amplifier, duplexer, etc.

[0375] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0376] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0377] The radio frequency unit 701 is used for:

[0378] Send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal;

[0379] Receive parameter configuration information sent by network-side devices;

[0380] Processor 710 is used for:

[0381] Based on the parameter configuration information, a second target sequence type is determined for the DMRS used by the terminal to transmit the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0382] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0383] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0384] Optionally, the first target sequence type includes at least one of the following:

[0385] Low PAPR sequence generation type Type 1;

[0386] Low PAPR sequence generation type Type 2;

[0387] The first determining module is used for:

[0388] The type of the second target sequence is determined to include Type 1; or

[0389] The type of the second target sequence is determined to include Type 2.

[0390] Optionally, the parameter configuration information includes at least one of the following:

[0391] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0392] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0393] Optionally, the processor 710 is used for:

[0394] When the parameter configuration information includes first indication information and second indication information, the second target sequence type is determined to include Type 2.

[0395] Optionally, the processor 710 is used for:

[0396] If the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type is determined to include Type 2.

[0397] Optionally, the processor 710 is used for:

[0398] If the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type is determined to include Type 1.

[0399] Optionally, the processor 710 is used for:

[0400] If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type is determined to include Type 1.

[0401] Optionally, the processor 710 is used for:

[0402] It is not expected that the parameter configuration information includes only the first indication information or only the second indication information.

[0403] Optionally, the first capability information includes sequence type indication information;

[0404] The first target sequence type includes Type 1 and Type 2. Type 1 is the first target sequence type supported by default by the terminal, and the sequence type indication information is used to indicate that the terminal supports Type 2.

[0405] Optionally, the first capability information includes first type indication information, which indicates that the first target sequence type includes Type 1.

[0406] Optionally, the first capability information further includes second type indication information, which indicates that the first target sequence type also includes Type 2.

[0407] Optionally, the terminal is in a first frequency band;

[0408] The first frequency band includes at least one of the following:

[0409] FR2-2 band;

[0410] The unlicensed frequency band of FR2-2.

[0411] Optionally, the first capability information is further used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS;

[0412] The target PUCCH includes the PUCCH of multiple PRBs corresponding to the target SCS.

[0413] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0414] The PUCCH that meets the first condition includes at least one of the following:

[0415] PUCCH in a default format;

[0416] A PUCCH containing a preset number of PRBs.

[0417] In this embodiment of the application, by first instructing the network side on one or more first target sequence types supported by the terminal and obtaining parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH DMRS is determined based on the parameter configuration information, so that both the terminal and the network-side device can determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device have a consistent understanding of the sequence of the enhanced PUCCH-DMRS, thereby ensuring the successful transmission of the PUCCH DMRS.

[0418] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is used for:

[0419] The first capability information sent by the receiving terminal;

[0420] The processor is used for:

[0421] Based on the first capability information, determine one or more first target sequence types supported by the terminal;

[0422] The communication interface is also used for:

[0423] Send parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0424] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0425] This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0426] Specifically, embodiments of this application also provide a network-side device. Figure 8 A schematic diagram of the hardware structure of a network-side device according to an embodiment of this application; such as Figure 8 As shown, the network-side device 800 includes: an antenna 801, a radio frequency (RF) device 802, a baseband device 803, a processor 804, and a memory 805. The antenna 801 is connected to the RF device 802. In the uplink direction, the RF device 802 receives information through the antenna 801 and transmits the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be transmitted and sends it to the RF device 802. The RF device 802 processes the received information and transmits it through the antenna 801.

[0427] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 803, which includes a baseband processor.

[0428] The baseband device 803 may, for example, include at least one baseband board on which multiple chips are disposed, such as... Figure 8 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 805 via a bus interface to call the program in the memory 805 and execute the network device operation shown in the above method embodiment.

[0429] The network-side device may also include a network interface 806, such as a common public radio interface (CPRI).

[0430] Specifically, the network-side device 800 of this embodiment further includes: instructions or programs stored in a memory 805 and executable on a processor 804, wherein the processor 804 calls the instructions or programs in the memory 805 to execute... Figure 5 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0431] The radio frequency device 802 is used for:

[0432] The first capability information sent by the receiving terminal;

[0433] Processor 804 is used for:

[0434] Based on the first capability information, determine one or more first target sequence types supported by the terminal;

[0435] Radio frequency device 802 is used for:

[0436] Send parameter configuration information to the terminal; the higher-layer configuration parameters are used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types;

[0437] Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1.

[0438] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0439] Alternatively, the processor 804 is used for at least one of the following:

[0440] The type of the first target sequence is determined to include Type 1;

[0441] Based on the first capability information, the type of the first target sequence is determined to include Type 2.

[0442] Optionally, processor 804 is used for:

[0443] The type of the first target sequence is determined to include Type 1 by default.

[0444] Optionally, processor 804 is used for:

[0445] If the first capability information is determined to include sequence type indication information, then the target sequence type is determined to include Type 2.

[0446] Optionally, processor 804 is used for:

[0447] If the first capability information is determined to include first type indication information, the target sequence type is determined to include Type 1.

[0448] Optionally, processor 804 is used for:

[0449] If the first capability information is determined to include second type indication information, the target sequence type is determined to include Type 2.

[0450] Optionally, the parameter configuration information is empty, or the parameter configuration information includes at least one of the following:

[0451] First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK;

[0452] The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

[0453] Optionally, if the parameter configuration information includes first indication information and second indication information, the second target sequence type includes Type 2.

[0454] Optionally, if the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type includes Type 1.

[0455] Optionally, if the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type includes Type 2.

[0456] Optionally, if the parameter configuration information does not include either first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type includes Type 1.

[0457] Optionally, processor 804 is used for:

[0458] Based on the first capability information, it is determined that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS, and it is determined that the target PUCCH includes a PUCCH with multiple PRBs corresponding to the target SCS.

[0459] Optionally, the target PUCCH includes a PUCCH that meets the first condition;

[0460] The PUCCH that meets the first condition includes at least one of the following:

[0461] PUCCH in a default format;

[0462] A PUCCH containing a preset number of PRBs.

[0463] In this embodiment of the application, by determining one or more first target sequence types supported by the terminal and indicating parameter configuration information to the terminal, the terminal determines a second target sequence type used by the terminal for transmitting the target PUCCH DMRS based on the parameter configuration information. This allows both the terminal and the network-side device to determine the sequence of the enhanced PUCCH-DMRS, and the terminal and the network-side device maintain a consistent understanding of the enhanced PUCCH-DMRS sequence, thereby ensuring the successful transmission of the PUCCH DMRS.

[0464] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described sequence type determination method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0465] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0466] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described sequence type determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0467] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0468] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described sequence type determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0469] This application embodiment also provides a sequence type determination system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the sequence type determination method as described above, and the network-side device can be used to execute the steps of the sequence type determination method as described above.

[0470] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0471] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they 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 this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0472] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining sequence type, characterized in that, include: The terminal sends first capability information to the network-side device, the first capability information being used to indicate one or more first target sequence types supported by the terminal; The terminal receives parameter configuration information sent by the network-side device; Based on the parameter configuration information, the terminal determines a second target sequence type used by the terminal to transmit the demodulation reference signal DMRS of the target physical uplink control channel PUCCH, wherein the second target sequence type is one of the one or more first target sequence types; Wherein, the number of physical resource blocks (PRBs) of the target PUCCH is greater than or equal to 1; The first target sequence type includes at least one of the following: Low peak-to-average power ratio (Low PAPR) sequence generation type 1; Low PAPR sequence generation type Type 2.

2. The sequence type determination method according to claim 1, characterized in that, Determining the second target sequence type used by the terminal for transmitting the target PUCCH via DMRS includes: The terminal determines that the type of the second target sequence includes Type 1; or The terminal determines that the type of the second target sequence includes Type 2.

3. The sequence type determination method according to claim 2, characterized in that, The parameter configuration information includes at least one of the following: First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK; The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

4. The sequence type determination method according to claim 3, characterized in that, The terminal determines that the second target sequence type includes Type 2, including: When the parameter configuration information includes first indication information and second indication information, the terminal determines that the second target sequence type includes Type 2.

5. The sequence type determination method according to claim 3, characterized in that, The terminal determines that the second target sequence type includes Type 2, including: If the parameter configuration information does not include the first indication information but includes the second indication information, the terminal determines that the second target sequence type includes Type 2.

6. The sequence type determination method according to claim 3, characterized in that, The terminal determines that the second target sequence type includes Type 1, including: If the parameter configuration information includes first indication information but does not include second indication information, the terminal determines that the second target sequence type includes Type 1.

7. The sequence type determination method according to claim 2, characterized in that, The terminal determines that the second target sequence type includes Type 1, including: If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the terminal determines that the second target sequence type includes Type 1.

8. The sequence type determination method according to claim 3, characterized in that, The method further includes: The terminal does not expect the parameter configuration information to include only the first indication information or only the second indication information.

9. The sequence type determination method according to any one of claims 1-8, characterized in that, The first capability information includes sequence type indication information; The first target sequence type includes Type 1 and Type 2. Type 1 is the first target sequence type supported by default by the terminal, and the sequence type indication information is used to indicate that the terminal supports Type 2.

10. The sequence type determination method according to any one of claims 1-8, characterized in that, The first capability information includes first type indication information, which indicates that the first target sequence type includes Type 1.

11. The sequence type determination method according to claim 10, characterized in that, The first capability information also includes second type indication information, which is used to indicate that the first target sequence type also includes Type 2.

12. The sequence type determination method according to claim 1, characterized in that, The terminal is in the first frequency band; The first frequency band includes at least one of the following: FR2-2 band; The unlicensed frequency band of FR2-2.

13. The sequence type determination method according to claim 1, characterized in that, The first capability information is also used to indicate that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS; The target PUCCH includes the PUCCH of multiple PRBs corresponding to the target SCS.

14. The sequence type determination method according to claim 1, characterized in that, The target PUCCH includes PUCCHs that meet the first condition; The PUCCH that meets the first condition includes at least one of the following: PUCCH in a default format; A PUCCH containing a preset number of PRBs.

15. A method for determining sequence type, characterized in that, include: The network-side device receives the first capability information sent by the terminal; Based on the first capability information, the network-side device determines one or more first target sequence types supported by the terminal; The network-side device sends parameter configuration information to the terminal; the parameter configuration information is used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types; Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1; The first target sequence type includes at least one of the following: Low peak-to-average power ratio (Low PAPR) sequence generation type 1; Low PAPR sequence generation type Type 2.

16. The sequence type determination method according to claim 15, characterized in that, Based on the first capability information, the network-side device determines one or more first target sequence types supported by the terminal, including at least one of the following: The network-side device determines that the type of the first target sequence includes Type 1; Based on the first capability information, the network-side device determines that the first target sequence type includes Type 2.

17. The sequence type determination method according to claim 15 or 16, characterized in that, Determining the type of the first target sequence includes Type 1, which includes: The network-side device determines that the first target sequence type includes Type 1 by default.

18. The sequence type determination method according to claim 17, characterized in that, Determining that the type of the first target sequence includes Type 2 includes: If the network-side device determines that the first capability information includes sequence type indication information, the target sequence type includes Type 2.

19. The sequence type determination method according to claim 15 or 16, characterized in that, Determining the type of the first target sequence includes Type 1, which includes: If the network-side device determines that the first capability information includes first type indication information, the target sequence type includes Type 1.

20. The sequence type determination method according to claim 19, characterized in that, Determining that the type of the first target sequence includes Type 2 includes: If the network-side device determines that the target sequence type includes Type 2 when it determines that the first capability information includes second type indication information.

21. The sequence type determination method according to claim 15, characterized in that, The parameter configuration information is empty, or the parameter configuration information includes at least one of the following: First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK; The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

22. The sequence type determination method according to claim 21, characterized in that, When the parameter configuration information includes first indication information and second indication information, the second target sequence type includes Type 2.

23. The sequence type determination method according to claim 21, characterized in that, If the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type includes Type 1.

24. The sequence type determination method according to claim 21, characterized in that, If the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type includes Type 2.

25. The sequence type determination method according to claim 15, characterized in that, If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type includes Type1.

26. The sequence type determination method according to claim 15, characterized in that, The method further includes: Based on the first capability information, the network-side device determines that the terminal supports a PRB number greater than 1 for the PUCCH corresponding to the target SCS, and determines that the target PUCCH includes a PUCCH with multiple PRBs corresponding to the target SCS.

27. The sequence type determination method according to claim 15, characterized in that, The target PUCCH includes PUCCHs that meet the first condition; The PUCCH that meets the first condition includes at least one of the following: PUCCH in a default format; A PUCCH containing a preset number of PRBs.

28. A sequence type determination device, characterized in that, include: The first sending module is used to send first capability information to the network-side device, wherein the first capability information is used to indicate one or more first target sequence types supported by the terminal; The first receiving module is used to receive parameter configuration information sent by the network-side device; The first determining module is configured to determine, based on the parameter configuration information, a second target sequence type used by the terminal for transmitting the target PUCCH via DMRS, wherein the second target sequence type is one of the one or more first target sequence types; Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1; The first target sequence type includes at least one of the following: Low peak-to-average power ratio (Low PAPR) sequence generation type 1; Low PAPR sequence generation type Type 2.

29. The sequence type determination apparatus according to claim 28, characterized in that, The first determining module is used for: The type of the second target sequence is determined to include Type 1; or The type of the second target sequence is determined to include Type 2.

30. The sequence type determination apparatus according to claim 29, characterized in that, The parameter configuration information includes at least one of the following: First indication information used to indicate that the target PUCCH is modulated using pi2 BPSK; The DMRS used to indicate the target PUCCH employs a second indication information pre-coded by DFT.

31. The sequence type determination apparatus according to claim 30, characterized in that, The first determining module is used for: When the parameter configuration information includes first indication information and second indication information, the second target sequence type is determined to include Type 2.

32. The sequence type determination device according to claim 31, characterized in that, The first determining module is used for: If the parameter configuration information does not include the first indication information but includes the second indication information, the second target sequence type is determined to include Type 2.

33. The sequence type determination device according to claim 31, characterized in that, The first determining module is used for: If the parameter configuration information includes first indication information but does not include second indication information, the second target sequence type is determined to include Type 1.

34. The sequence type determination apparatus according to claim 30, characterized in that, The first determining module is used for: If the parameter configuration information does not include either the first indication information for indicating that the target PUCCH uses pi2 BPSK modulation or the second indication information for indicating that the DMRS of the target PUCCH uses DFT precoding, the second target sequence type is determined to include Type 1.

35. The sequence type determination apparatus according to claim 31, characterized in that, The device further includes: The expectation module is configured to not expect the parameter configuration information to include only the first indication information or only the second indication information.

36. A sequence type determination device, characterized in that, include: The second receiving module is used to receive the first capability information sent by the terminal. The second determining module is used to determine one or more first target sequence types supported by the terminal based on the first capability information; The second sending module is used to send parameter configuration information to the terminal; the parameter configuration information is used to determine a second target sequence type used by the DMRS of the target PUCCH, wherein the second target sequence type is one of the one or more first target sequence types; Wherein, the number of PRBs in the target PUCCH is greater than or equal to 1; The first target sequence type includes at least one of the following: Low peak-to-average power ratio (Low PAPR) sequence generation type 1; Low PAPR sequence generation type Type 2.

37. The sequence type determination apparatus according to claim 36, characterized in that, The second determining module is used for at least one of the following: The type of the first target sequence is determined to include Type 1; Based on the first capability information, the type of the first target sequence is determined to include Type 2.

38. The sequence type determination apparatus according to claim 36 or 37, characterized in that, The second determining module is used for: The type of the first target sequence is determined to include Type 1 by default.

39. The sequence type determination apparatus according to claim 38, characterized in that, The second determining module is used for: If the first capability information is determined to include sequence type indication information, then the target sequence type is determined to include Type 2.

40. The sequence type determination apparatus according to claim 36 or 37, characterized in that, The second determining module is used for: If the first capability information is determined to include first type indication information, the target sequence type is determined to include Type 1.

41. The sequence type determination apparatus according to claim 40, characterized in that, The second determining module is used for: If the first capability information is determined to include second type indication information, the target sequence type is determined to include Type 2.

42. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the sequence type determination method as described in any one of claims 1 to 14.

43. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the sequence type determination method as described in any one of claims 15 to 27.

44. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the sequence type determination method as described in any one of claims 1 to 14, or implement the steps of the sequence type determination method as described in any one of claims 15 to 27.

Images