Communication method, apparatus, and system

Abstract

The present application provides a communication method, apparatus, and system, which are applied to the technical field of communications. The communication method provided in the present application can protect orthogonality of uplink information transmitted by a terminal from being damaged, thereby preventing a network side from failing to correctly receive the uplink information. The communication method comprises: a terminal device determines that a first time-frequency resource and a second time-frequency resource overlap, the first time-frequency resource being used for carrying a PUCCH comprising scheduling request information, and the second time-frequency resource being used for carrying a PUSCH; and the terminal device sends a PUSCH on the second time-frequency resource, all or part of uplink information in the PUSCH being multiplied by elements in an orthogonal sequence.

Description

Communication methods, devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202411403070.1, filed with the State Intellectual Property Office of China on September 30, 2024, entitled "Communication Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods, apparatus and systems. Background Technology

[0003] Orthogonal cover code (OCC) is an information processing technology that can be applied to communication systems. Based on OCC, the network side can configure different orthogonal sequences in the same orthogonal matrix for multiple terminal devices using the same time-frequency resources. The elements in the orthogonal sequence are called OCC elements. Each terminal device can multiply the information to be transmitted with the different OCC elements in its configured orthogonal sequence (this can also be called that the terminal device sends information based on OCC), thereby realizing code division multiplexing or code division extension.

[0004] Currently, terminal devices are considering transmitting the Physical Uplink Shared Channel (PUSCH) based on the OCC to improve the transmission rate of both the system and the terminal devices. However, in some scenarios, terminal devices transmitting PUSCH based on the OCC may affect PUSCH transmission. Summary of the Invention

[0005] This application provides communication methods, apparatus, and systems that can protect the orthogonality of uplink information transmitted by terminals from being compromised. To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a communication method is provided, which can be executed by a terminal device, or by a component within the terminal device (e.g., a processor, chip, or chip system). The following description uses terminal device execution as an example. The method includes: the terminal device determining that a first time-frequency resource and a second time-frequency resource overlap; wherein the first time-frequency resource is used to carry a PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry a PUSCH. The terminal device transmits a PUSCH on the second time-frequency resource, and all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0007] Based on the communication method provided in the embodiments of this application, the terminal device can send PUSCH through OCC when PUSCH and PUCCH overlap, so as to protect the orthogonality of uplink information sent between different terminals in the scenario where other terminals also send uplink information based on OCC, and avoid the network side being unable to correctly decode the received uplink information due to the destruction of orthogonality.

[0008] In conjunction with the first aspect mentioned above, in one possible design, PUSCH includes first information, which includes scheduling request information.

[0009] Based on this scheme, the scheduling request information in PUCCH can be reused in PUSCH, so that uplink resources can still be requested from the network side.

[0010] In conjunction with the first aspect mentioned above, in one possible design, the first orthogonal frequency division multiplexing (OFDM) symbol of the third time-frequency resource is the first OFDM symbol after the first set of consecutive OFDM symbols carrying the demodulation reference signal (DMRS) in the PUSCH, and the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0011] This application provides a design for mapping uplink information in the PUSCH in the time domain.

[0012] In conjunction with the first aspect above, in one possible design, if the number of bits of the first information does not exceed a first value, the first information is mapped in the PUSCH using a puncturing method; and / or, if the number of bits of the first information exceeds a first value, the first information is mapped in the PUSCH using a non-puncturing method.

[0013] This application provides a design for mapping uplink information in the PUSCH in the frequency domain.

[0014] In conjunction with the first aspect mentioned above, in one possible design, the first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0015] This application provides a design for mapping uplink information in the PUSCH in the time domain.

[0016] In conjunction with the first aspect mentioned above, in one possible design, when the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

[0017] Based on this scheme, when the PUCCH includes active scheduling request information, i.e., when the terminal device has uplink resource requirements, the scheduling request information can be reused in the PUSCH. This avoids reusing the scheduling request information in the PUSCH when the terminal device does not actually have uplink resource requirements, thus avoiding resource waste.

[0018] In conjunction with the first aspect mentioned above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The method further includes: the terminal device sending second information on the fourth time-frequency resource, the second information being used to request uplink authorization.

[0019] Based on this solution, even if the terminal device does not transmit scheduling request information, it can request uplink authorization to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0020] In conjunction with the first aspect above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The method further includes: sending a cache status report on the fifth time-frequency resource, the cache status report being used to indicate the amount of data cached by the terminal device.

[0021] Based on this solution, if the terminal device does not transmit scheduling request information, it can send a cache status report to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0022] In conjunction with the first aspect mentioned above, in one possible design, the first information also includes uplink information in the PUCCH that differs from the scheduling request information.

[0023] Based on this scheme, other uplink information that differs from scheduling request information in PUCCH can also be reused in PUSCH.

[0024] Secondly, a communication method is provided, which can be executed by a network device, or by a component of the network device (e.g., a processor, chip, or chip system). The following description uses network device execution as an example. The method includes: the network device sending configuration information to a terminal device. The configuration information is used to configure a first time-frequency resource and a second time-frequency resource, wherein the first and second time-frequency resources overlap. The first time-frequency resource is used to carry a PUCCH, which includes scheduling request information. The second time-frequency resource is used to carry a PUSCH. The PUSCH is received on the second time-frequency resource, and all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0025] Based on the communication method provided in the embodiments of this application, when PUSCH and PUCCH overlap, the network device can receive the PUSCH transmitted through OCC. Therefore, in scenarios where other terminals also send uplink information based on OCC, the orthogonality of uplink information sent between different terminals can be protected, avoiding the network device's inability to correctly decode the received uplink information due to the destruction of orthogonality.

[0026] In conjunction with the second aspect mentioned above, in one possible design, PUSCH includes first information, which includes scheduling request information.

[0027] Based on this scheme, the scheduling request information in PUCCH can be reused in PUSCH, so that the network can still allocate uplink resources to terminal devices according to the scheduling request information in PUSCH.

[0028] In conjunction with the second aspect above, in one possible design, the first OFDM symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying DMRS in the PUSCH, and the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0029] This application provides a design for mapping uplink information in the PUSCH in the time domain.

[0030] In conjunction with the second aspect above, in one possible design, the first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0031] This application provides a design for mapping uplink information in the PUSCH in the frequency domain.

[0032] In conjunction with the second aspect above, in one possible design, when the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

[0033] This application provides a design for mapping uplink information in the PUSCH in the time domain.

[0034] In conjunction with the second aspect above, in one possible design, the PUSCH includes first information, which does not include scheduling request information, and the method further includes: the network device receiving second information on a fourth time-frequency resource, the second information being used to request uplink authorization.

[0035] Based on this solution, even if the terminal device does not transmit scheduling request information, it can request uplink authorization to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0036] In conjunction with the second aspect above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The method further includes: receiving a cache status report on a fifth time-frequency resource, the cache status report being used to indicate the amount of data cached by the terminal device.

[0037] Based on this solution, if the terminal device does not transmit scheduling request information, it can send a cache status report to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0038] In conjunction with the second aspect mentioned above, in one possible design, the first information also includes uplink information in the PUCCH that differs from the scheduling request information.

[0039] Based on this solution, the terminal device can also reuse other uplink information in the PUCCH that is different from the scheduling request information in the PUSCH.

[0040] Thirdly, a communication device is provided for implementing the method implemented by the terminal device in the first aspect above.

[0041] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0042] In conjunction with the third aspect mentioned above, in one possible design, the communication device includes a transceiver module and a processing module: the processing module is used to determine that a first time-frequency resource and a second time-frequency resource overlap; wherein the first time-frequency resource is used to carry a PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry a PUSCH. The transceiver module is used to transmit a PUSCH on the second time-frequency resource, wherein all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0043] In conjunction with the third aspect mentioned above, in one possible design, PUSCH includes first information, which includes scheduling request information.

[0044] In conjunction with the third aspect mentioned above, in one possible design, the first OFDM symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying DMRS in the PUSCH, and the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0045] In conjunction with the third aspect mentioned above, in one possible design, if the number of bits of the first information does not exceed the first value, the first information is mapped in the PUSCH using a puncturing method; and / or, if the number of bits of the first information exceeds the first value, the first information is mapped in the PUSCH using a non-puncturing method.

[0046] In conjunction with the third aspect mentioned above, in one possible design, the first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0047] In conjunction with the third aspect mentioned above, in one possible design, when the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

[0048] In conjunction with the third aspect mentioned above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The transceiver module is also used to send second information on the fourth time-frequency resource, and the second information is used to request uplink authorization.

[0049] In conjunction with the third aspect mentioned above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The transceiver module is also used to send a cache status report on the fifth time-frequency resource. The cache status report is used to indicate the amount of data cached by the terminal device.

[0050] In conjunction with the third aspect mentioned above, in one possible design, the first information also includes uplink information in the PUCCH that differs from the scheduling request information.

[0051] Fourthly, a communication device is provided for implementing the method implemented by the network device in the second aspect above.

[0052] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0053] In conjunction with the fourth aspect mentioned above, in one possible design, the communication device includes a processing module and a transceiver module; wherein the processing module is used to determine configuration information. The transceiver module is used to send configuration information to the terminal device, the configuration information being used to configure a first time-frequency resource and a second time-frequency resource, wherein the first time-frequency resource and the second time-frequency resource overlap, the first time-frequency resource being used to carry PUCCH, which includes scheduling request information, and the second time-frequency resource being used to carry PUSCH. The transceiver module is also used to receive PUSCH on the second time-frequency resource, wherein all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0054] In conjunction with the fourth aspect mentioned above, in one possible design, the PUSCH includes first information, which includes scheduling request information.

[0055] In conjunction with the fourth aspect above, in one possible design, the first OFDM symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying DMRS in the PUSCH, and the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0056] In conjunction with the fourth aspect above, in one possible design, the first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

[0057] In conjunction with the fourth aspect above, in one possible design, when the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

[0058] In conjunction with the fourth aspect mentioned above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The transceiver module is also used to receive second information on the fourth time-frequency resource, and the second information is used to request uplink authorization.

[0059] In conjunction with the fourth aspect mentioned above, in one possible design, the PUSCH includes first information, which does not include scheduling request information. The transceiver module is also used to receive a cache status report on the fifth time-frequency resource. The cache status report is used to indicate the amount of data cached by the terminal device.

[0060] In conjunction with the fourth aspect mentioned above, in one possible design, the first information also includes uplink information in the PUCCH that differs from the scheduling request information.

[0061] Fifthly, a communication device is provided, comprising: a processor configured to execute instructions stored in a memory, wherein when the processor executes the instructions, the communication device performs the method described in any of the preceding aspects. The communication device may be a terminal device (or a component, such as a chip, in the first aspect or any possible design of the first aspect). Alternatively, the communication device may be a network device (or a component, such as a chip, in the second aspect or any possible design of the second aspect).

[0062] In one possible design, the communication device also includes a memory for storing computer instructions. Optionally, the processor and memory are integrated together, or they are separate.

[0063] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0064] A sixth aspect provides a communication device, comprising: a processor and an interface circuit for communicating with a module outside the communication device; the processor for executing the method described in any of the preceding aspects via logic circuitry or by running a computer program or instructions. The communication device may be a terminal device (or a component, such as a chip, in the first aspect or any possible design of the first aspect). Alternatively, the communication device may be a network device (or a component, such as a chip, in the second aspect or any possible design of the second aspect).

[0065] Alternatively, the interface circuit can be a code / data read / write interface circuit, which receives computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmits them to the processor so that the processor runs the computer execution instructions to perform the methods described in any of the above aspects.

[0066] In one possible design, the communication device also includes a memory for storing computer programs or instructions. Optionally, the processor and memory are integrated together, or the processor and memory are separate.

[0067] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0068] In some possible designs, the communication device can be a chip or a chip system.

[0069] In a seventh aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the methods described in the first to second aspects, or any possible design of the first to second aspects.

[0070] Eighthly, this application provides a computer program product containing instructions that, when executed on a computer, enable the computer to perform the methods described in the first to second aspects, or any possible design of the first to second aspects.

[0071] A ninth aspect provides a communication device (e.g., the communication device may be a chip or a chip system), the communication device including a processor for implementing the functions involved in the first to second aspects, or any possible design of the first to second aspects. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0072] In a tenth aspect, a communication system is provided. In one possible design, the communication system includes a network device and a terminal device, wherein the network device is used to perform the methods described in the second aspect above, or any possible design of the second aspect. The terminal device is used to perform the methods described in the first aspect above, or any possible design of the first aspect.

[0073] The technical effects of any of the design methods in aspects three through ten can be found in the technical effects of the different design methods in aspects one through two above, and will not be repeated here. Attached Figure Description

[0074] Figure 1 is a schematic flowchart of a signal processing method provided in an embodiment of this application;

[0075] Figure 2 is a schematic diagram illustrating the principle of inter-slot OCC extension provided in an embodiment of this application;

[0076] Figure 3 is a flowchart illustrating another signal processing method provided in an embodiment of this application;

[0077] Figure 4 is a schematic diagram illustrating the principle of in-symbol OCC extension provided in the embodiments of this application;

[0078] Figure 5 is a schematic diagram of multiple terminal devices transmitting uplink information according to an embodiment of this application;

[0079] Figure 6 is another schematic diagram of multiple terminal devices transmitting uplink information according to an embodiment of this application;

[0080] Figure 7 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0081] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0082] Figure 9 is a schematic diagram of information transmission in PUSCH based on OCC according to an embodiment of this application;

[0083] Figure 10 is a schematic diagram of the mapping method of scheduling request information provided in the embodiments of this application;

[0084] Figure 11 is a schematic diagram of another mapping method for scheduling request information provided in an embodiment of this application;

[0085] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0086] Figure 13 is a schematic diagram of another communication device provided in an embodiment of this application;

[0087] Figure 14 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0088] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0089] 1. Time and frequency resources:

[0090] Time-frequency resources include time-domain resources and frequency-domain resources.

[0091] Temporal resources refer to one or more consecutive temporal resource units distributed in the temporal domain. Temporal resource units can be simply referred to as temporal units and may include superframes, radio frames (simply referred to as frames), subframes, slots, sub-slots, symbols, etc., without limitation here.

[0092] In the embodiments of this application, the symbol can be an orthogonal frequency division multiplexing (OFDM) symbol.

[0093] Frequency domain resources refer to one or more consecutive resource elements (REs) distributed in the frequency domain. Consecutive REs in the frequency domain can be called a resource block (RB). An RE is defined as the resource bounded by one symbol in the time domain and one subcarrier in the frequency domain. A subcarrier can be understood as the smallest granularity of a frequency domain resource; one RE can be called one subcarrier. For example, an RB in an LTE communication system includes 12 subcarriers, and an RB in an NR communication system also includes 12 subcarriers. As communication systems evolve, the number of subcarriers included in an RB can be other values. At the physical layer, an RB is called a physical resource block (PRB).

[0094] 2. OCC:

[0095] The basic principle of OCC is to assign different orthogonal sequences to different terminal devices using the same time-frequency resources. Different terminal devices can use the assigned orthogonal sequences to encode the information to be transmitted on the time-frequency resources, so that the data transmitted by different terminal devices on the time-frequency resources are orthogonal in the code domain, thereby achieving non-interference between multiple users.

[0096] Specifically, multiple terminal devices using the same time-frequency resources can be configured with different orthogonal sequences within the same orthogonal matrix. For example, a network device can configure orthogonal sequences within an orthogonal matrix for each terminal device. An orthogonal matrix comprises multiple mutually orthogonal sequences. The terminal device can multiply the information to be transmitted by different elements of the configured orthogonal sequences before sending it to the receiving end. Upon receiving the information, the receiving end can decode the information by multiplying the received information by the transpose of the orthogonal sequences, thus eliminating interference signals from other users.

[0097] For example, the orthogonal matrix of OCC includes matrix A as shown below, where the orthogonal sequences in matrix A include W1 assigned to terminal A and W2 assigned to terminal B, where W1 = [1 1] and W2 = [1 -1].

[0098] In the embodiments of this application, the orthogonal sequence can also be referred to as the coded sequence or OCC sequence. Optionally, the orthogonal matrix may include DFT code, Hadamard code, etc., wherein Hadamard code may also be referred to as Walsh code.

[0099] In this embodiment of the application, the elements (or values) in the orthogonal sequence can also be called OCC elements.

[0100] In this embodiment, the length of an orthogonal sequence refers to the number of elements in the orthogonal sequence. The length of an orthogonal sequence can also be called the spreading factor L or the spreading factor. This application does not limit the size of the orthogonal sequence length; for example, it can be 2, 4, etc. For example, the orthogonal sequence length of matrix A is 2.

[0101] In this embodiment of the application, the information may include data and / or signaling.

[0102] In this embodiment, multiplying information by different OCC elements in its configured orthogonal sequence can also be referred to as using OCC, or using the orthogonal sequence to perform OCC extension, or based on the OCC-extended information, performing code division extension or code division multiplexing, etc. It can also be described as performing OCC extension and repetition. In other words, multiplying information by different OCC elements in the orthogonal sequence can achieve code division multiplexing or OCC extension.

[0103] Taking matrix A as an example, if terminal A transmits information X and terminal B transmits information Y, then multiplying X by the OCC elements in W1 yields X and X, and multiplying Y by the OCC elements in W2 yields Y and -Y. Therefore, terminals A and B transmit the information obtained by multiplying by the OCC elements on the same time-frequency resources, so that the information received by the receiving side can be X+Y and XY, respectively. The receiving side can multiply the received information by the OCC elements in W1 and then add them together to obtain X, which is transmitted twice by terminal A. The receiving side can also multiply the received information by the OCC elements in W2 and then add them together to obtain Y, which is transmitted twice by terminal B.

[0104] In this embodiment of the application, code division multiplexing or OCC extension is performed on the information transmitted on the resource based on orthogonal sequences (which can also be replaced by descriptions based on / using orthogonal sequences, etc.). It can also be described as code division multiplexing or OCC extension of the resource based on orthogonal sequences.

[0105] In this embodiment, multiplying information with different OCC elements in the orthogonal sequence specifically includes: determining the OCC element corresponding to the time unit in the orthogonal sequence, and multiplying the information at each time unit with the OCC element corresponding to that time unit. These time units can be time units obtained by extending the time units occupied by the information according to the code length of the OCC, wherein the extended time units are integer multiples of the code length of the OCC, or multiple time units occupied by the information can be used as the time units required for extension.

[0106] In this embodiment, the OCC element corresponding to a time unit refers to the OCC element multiplied when the information in that time unit is expanded using OCC. For example, the OCC element corresponding to a time slot is the OCC element multiplied when the information in that time slot is expanded using inter-time slot OCC, and the OCC element corresponding to a symbol can be the OCC element multiplied when the information in that symbol is expanded using OCC (e.g., inter-time slot OCC expansion, inter-symbol OCC expansion, intra-symbol OCC expansion, etc.). Inter-time slot OCC expansion, inter-symbol OCC expansion, and intra-symbol OCC expansion will be described in detail below.

[0107] Currently, OCCs can be divided into inter-slot OCCs (OCC across slots; Inter-repetition OCC), inter-symbol OCCs (OCC across OFDM symbols), and intra-symbol OCCs (OCC within an OFDM symbol) according to time units.

[0108] OCCs can be categorized by repetition type into inter-repetition OCCs for PUSCH repetition type A and inter-repetition OCCs for PUSCH repetition type B. Both types can be collectively referred to as inter-repetition OCCs. Specifically, the inter-repetition OCC for PUSCH repetition type A extends the OCC for slot-level PUSCH, while the inter-repetition OCC for PUSCH repetition type B extends the OCC for min-slot-level or symbol-level PUSCH.

[0109] Information based on inter-slot OCC extension can be slot-level information, min-slot-level information, or symbol-level information. Inter-slot OCC extension can be divided into inter-slot OCC for PUSCH repetition type A and inter-slot OCC for PUSCH repetition type B.

[0110] The following explains in detail how OCC extension is performed between time slots, between symbols, and within symbols.

[0111] I. OCC between time slots:

[0112] 1. Inter-slot OCC for PUSCH repetition type A:

[0113] The inter-slot OCC of PUSCH repetition type A can extend and repeat information through multiple time slots (i.e., extend information by using time slots as extension units).

[0114] Specifically, each time slot configured in the network device is extended according to the orthogonal sequence length to obtain the time slot and the corresponding time slot group after the extension. The number of time slots in each time slot group is the length of the orthogonal sequence, such that the number of extended time slots is an integer multiple of the orthogonal sequence length. The information on each time slot in each time slot group is multiplied by an OCC element in the orthogonal sequence (i.e., multiplied by the OCC element corresponding to that time slot). Within a time slot group, the information on the OFDM symbols at the same position in each time slot is the same, but the OCC elements multiplied by the information on each time slot in a time slot group are different.

[0115] Optionally, the OCC element corresponding to a time slot can be related to the position of the time slot, and the OCC element corresponding to each time slot can be determined sequentially and cyclically according to the order of the OCC elements in the orthogonal sequence.

[0116] For example, if the number of time slots is 2, and the code length of the orthogonal sequence is 2, the first time slot corresponds to the first OCC element of the orthogonal sequence, and the second time slot corresponds to the second OCC element of the orthogonal sequence.

[0117] 2. Inter-slot OCC for PUSCH repetition type B:

[0118] The inter-slot OCC of PUSCH repetition type B extends information using OFDM symbol groups within the time slot as the extension unit. Optionally, the inter-slot OCC of PUSCH repetition type B can also be called the inter-symbol OCC with PUSCH repetition type B.

[0119] Specifically, each OFDM symbol within the time slot configured in the network device is extended according to the orthogonal sequence length, such that the number of extended symbols is an integer multiple of the orthogonal sequence length. The extended OFDM symbols are then grouped according to the orthogonal sequence length, resulting in at least two symbol groups. The number of symbol groups is equal to the orthogonal sequence length; that is, the number of OFDM symbols in each symbol group is the quotient between the total number of extended OFDM symbols and the orthogonal sequence length. The information on each OFDM symbol in each symbol group is multiplied by an OCC element in the orthogonal sequence (i.e., multiplied by the OCC element corresponding to that OFDM symbol group). The information on each OFDM symbol within a symbol group is different, while the OCC element multiplied by the information on each OFDM symbol within an OFDM symbol group is the same.

[0120] Unless otherwise specified, the time slot OCC mentioned below refers to the time slot OCC of PUSCH repetition type A.

[0121] II. Inter-symbol OCC:

[0122] Information is expanded and repeated using OCC (Optical Code Correction) with different OFDM symbols within at least one time slot; that is, information is expanded using OFDM symbols as expansion units. Specifically, each OFDM symbol can be expanded according to its code length within the time slots configured in the network device to obtain the symbol group to which the OFDM symbol belongs. The number of OFDM symbols in each symbol group is equal to the code length, ensuring that the number of expanded symbols is an integer multiple of the code length. The information on each OFDM symbol in a symbol group is identical, and each symbol is multiplied by an OCC element in an orthogonal sequence to achieve OCC expansion and repetition between symbols.

[0123] III. Intra-symbol OCC:

[0124] Intra-symbol OCC extension uses symbols within an OFDM symbol as extension units to extend data. In this embodiment, the symbols within an OFDM symbol are referred to as data symbols, which can specifically be complex symbols. A data symbol can be understood as the frequency domain symbol of an OFDM symbol. Hereinafter, REs are used to describe data symbols or frequency domain units, which can be subcarriers. Specifically, intra-symbol OCC extension extends each frequency domain unit of the OFDM symbol configured by the network device according to the orthogonal sequence length, obtaining each frequency domain unit and a corresponding RE group for the extended frequency domain unit. The number of frequency domain units in each RE group is equal to the orthogonal sequence length, ensuring that the number of extended symbols is an integer multiple of the orthogonal sequence length. The data on each RE in each RE group is multiplied by an OCC element in the orthogonal sequence, and the OCC element multiplied by the data on each RE in each RE group is the same. The data on each RE in each RE group is different, but the data on REs in corresponding orders within each RE group are the same.

[0125] For example, the specific processes of inter-slot OCC and inter-symbol OCC will be described below with reference to Figures 1 and 2. Figure 1 is a schematic flowchart of a signal processing method provided in an embodiment of this application. As shown in Figure 1, the method includes the following steps, wherein:

[0126] S101: Perform block segmentation and encoding on the transport block to obtain the block code.

[0127] Step S101 is applicable to cases where the transmission block is large. Specifically, it may include: dividing the transmission block into code blocks to obtain multiple code blocks; adding a cyclic redundancy check (CRC) code to the end of each code block; and performing channel coding (such as Hamming code, convolutional code, Turbo code, Polar code, etc.) on the code blocks with added CRC so that the receiver can detect or correct errors that occur during transmission to achieve reliable transmission, thereby obtaining the block code.

[0128] Optionally, after channel coding, the method may further include: rate matching of the block codes obtained from channel coding to achieve matching of information and resources; or concatenating the block codes obtained from channel coding or rate matching to link individual block codes together.

[0129] S102: Scramble the block code to obtain the first complex value symbol block.

[0130] Scrambling involves multiplying the original signal by a scrambling code to obtain a new signal. If the block code is represented by b(i) and the scrambling sequence by c(i), the data in the first complex-valued symbol block can be represented by d(i), where d(i) = c(i) * b(i). In a general sense, scrambling is a modulation technique. The inverse operation of scrambling is descrambling. By scrambling the code block, the resulting first complex-valued symbol block is broken down in both the time and frequency domains compared to the block code.

[0131] S103: Modulate the first complex value symbol block to obtain the second complex value symbol block.

[0132] The data in the second complex-valued symbol block can be represented by x(i). After modulation, the symbol in the time slot can be called either the modulation symbol or the first symbol.

[0133] S104: Pre-encode the second complex number symbol block to obtain the third complex number symbol block.

[0134] The precoding can be a DFT, as described above, and will not be repeated here. The data in the third complex numerical symbol block can be represented by y(i).

[0135] S105: The third complex value symbol block is extended based on the orthogonal sequence to obtain the fourth complex value symbol block.

[0136] Among them, the spread is also called block spread or (or block spreading), and when spread in the frequency domain, it can also be called spread spectrum. The spread of complex value symbol blocks can also be called block spread of complex value symbol blocks. The data in the fourth complex value symbol block can be represented by z(i). In one implementation, step S105 can be implemented by inter-slot OCC spread, which satisfies the following equation (1).

[0137] Among them, w i Let y(m) be an orthogonal sequence and y(n) be the third complex number symbol block. n represents the order of the data in the third complex number symbol block, and m represents the order of the values ​​in the orthogonal sequence. The number of PRBs allocated to terminal devices. The number of subcarriers in each RB, It is based on the PUSCH resource allocation in the time domain, and the number of DFT-s-OFDM symbols repeated each time. is the length of the orthogonal sequence.

[0138] For example, Then m = 0, 1, 2, 3, meaning the number of values ​​in the forward sequence of the terminal device is 4. If =1, It is 12. If n is 1, then n = 0, ..., 11, meaning the number of data in the third complex number symbol block is 12. Each data in the third complex number symbol block is expanded 4 times, so the number of data in the fourth complex number symbol block is 12 * 4, or 48.

[0139] For example, please refer to Figure 2, which is a schematic diagram of the principle of inter-slot OCC extension provided by an embodiment of this application. As shown in Figure 2, the orthogonal sequence includes two values, w(1) and w(2). If the orthogonal sequence is W1 in the example above, then both w(1) and w(2) can be 1. If the orthogonal sequence is W2 in the example above, then w(1) can be 1 and w(2) can be -1. In Figure 2, the horizontal axis represents the time domain, and there are two time slots, slot#1 and slot#2. Slot#1 can be used as the time slot before extension, and slot#2 can be used as the time slot obtained by slot#1 to realize inter-slot OCC extension. Each time slot in slot#1 and slot#2 includes two OFDM symbols occupied by demodulation reference signals (DMRS). OFDM symbols with the same sequence number indicate that the data to be extended on these OFDM symbols is the same. The data on the OFDM symbols in slot #1 before expansion (excluding the OFDM symbols occupied by DMRS) can be multiplied by w(1), and the data on the OFDM symbols in slot #2 after expansion (excluding the OFDM symbols occupied by DMRS) can be multiplied by w(2). In this way, OCC expansion between time slots can be achieved by multiplying the data on the OFDM symbols in slot #2 before expansion (excluding the OFDM symbols occupied by DMRS) by different OCC elements in the orthogonal sequence.

[0140] In another implementation, step S105 may be implemented by (multiple) inter-symbol OCC extensions, which satisfy the following equation (2).

[0141] Among them, w i (m) is an orthogonal sequence, and y(n) is the complex value symbol block to be expanded (the third complex value symbol block). n) is the expanded complex value symbol block (the fourth complex value symbol block). n is the order of the data in the complex value symbol block, and m represents the order of the values ​​in the orthogonal sequence. The number of PRBs allocated to terminal devices. This represents the number of subcarriers in each RB. The length of the orthogonal sequence. Inter-symbol OCC can be applied to PUSCH across DFT-s-OFDM symbols, specifically, for blocks of complex-valued symbols. Mapped onto the subcarrier corresponding to the DFT-s-OFDM symbol, and using the orthogonal sequence w according to formula (1). i (m) Perform block-by-block expansion. A is the number of DFT-s-OFDM symbols in the symbol group. When using inter-symbol OCC expansion, A is 1. When using inter-symbol OCC, A is greater than 1.

[0142] For example, Then m = 0, 1, 2, 3, meaning the number of values ​​in the orthogonal sequence of the terminal devices is 4. If =1, If n = 12, then n = 0, ..., 11, meaning the number of data in the third complex number symbol block is 12, and each data is expanded 4 times. The number of data in the fourth complex number symbol block is 12 * 4, which is 48.

[0143] During inter-symbol OCC extension, OFDM symbols in each symbol group are implemented sequentially through the corresponding OCC elements according to the order of the OCC elements in the orthogonal sequence.

[0144] S106: Perform an inverse fast fourier transform (IFFT) on the fourth complex-valued symbol block to obtain the fifth complex-valued symbol block.

[0145] In the method shown in Figure 1, after precoding, the complex-valued symbol block can be expanded through inter-slot OCC extension, inter-symbol OCC extension, or inter-symbol group OCC extension. Inter-slot OCC extension using orthogonal sequences allows for the expansion of time slots and the transmission of data through the expanded time slots. Similarly, inter-symbol OCC extension or inter-symbol group OCC extension using orthogonal sequences allows for the expansion of OFDM symbols and the transmission of data through the expanded OFDM symbols.

[0146] For example, the specific process of OCC within a symbol will be described below with reference to Figures 3 and 4. Figure 3 is a schematic flowchart of another signal processing method provided in an embodiment of this application. As shown in Figure 3, the method includes the following steps, wherein:

[0147] S301: Perform block segmentation and encoding on the transport block to obtain the block code.

[0148] S302: Scramble the block code to obtain the first complex value symbol block.

[0149] S303: Modulate the first complex value symbol block to obtain the second complex value symbol block.

[0150] Steps S301 to S303 can be referred to the description of steps S101 to S103, and will not be repeated here.

[0151] S304: The second complex value symbol block is extended based on the orthogonal sequence to obtain the third complex value symbol block.

[0152] The data in the third complex-valued symbol block can be represented by x(i). Step S304 specifically involves performing OCC intra-symbol spread on the second complex-valued symbol block based on an orthogonal sequence to obtain the third complex-valued symbol block. The formula for intra-symbol OCC spread satisfies the following equation (3).

[0153] in, The description can be found in equation (1), and will not be repeated here. M symb This represents the number of symbols transmitted. k and l are used to distinguish parameters. This represents the expanded complex number symbol block (the third complex number symbol block). This represents an orthogonal sequence. This represents the complex number symbol block to be expanded (the second complex number symbol block), such as d(0), ..., d(M). symb -1).

[0154] For example, if =1, If it is 12, then k = 0, 1, ..., 11. That is, the number of values ​​in the orthogonal sequence of the terminal device is 4. M symb =3, then l=0, that is, the data of the second complex value symbol block is d(0),…,d(M) symb -1), that is, 3 data to be expanded, each data is expanded 4 times, resulting in 12 data after expansion, that is, the third complex number symbol block includes 12 data.

[0155] For example, please refer to Figure 4, which is a schematic diagram of an intra-symbol OCC extension provided by an embodiment of this application. In Figure 4, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Figure 4 uses an OFDM symbol, M symb =6, with an OCC length of 2 for example. As shown in Figure 4, the frequency domain resources configured on this OFDM symbol are 6 REs, and after expansion, the OFDM symbol includes 12 REs. These 12 REs include 2 RE groups, and the data on each RE in the RE group is multiplied by the same OCC element. The number of REs with the same index is 2, and REs with the same index indicate that the data to be expanded on these REs is the same. The orthogonal sequence includes 2 values, w(1) and w(2). w(1) can be multiplied by the data on each RE in the RE group before expansion, and w(2) can be multiplied by the data on each RE in the expanded RE group. Or w(2) can be multiplied by the data on each RE in the RE group before expansion, and w(1) can be multiplied by the data on each RE in the expanded RE group. In this way, by multiplying the data on the RE before expansion or the expanded RE by different OCC elements in the orthogonal sequence, the OCC expansion within the symbol can be achieved.

[0156] S305: Pre-encode the third complex number symbol block to obtain the fourth complex number symbol block.

[0157] S306: Perform IFFT on the fourth complex number symbol block to obtain the fifth complex number symbol block.

[0158] Step S305 can be referred to step S104, and step S306 can be referred to the description of step S106, and will not be repeated here.

[0159] It is understandable that in the method shown in Figure 4, the step of employing intra-symbol OCC extension is performed before precoding, which can realize the data extension to be transmitted on different second complex-valued symbols of the same OFDM symbol.

[0160] 2. Uplink control information (UCI) is mapped onto the PUSCH:

[0161] Multiplexing UCI onto PUSCH, or mapping UCI onto PUSCH, can be mainly divided into the following 6 steps:

[0162] 1. When the number of bits in the hybrid automatic repeat-request (HARQ) acknowledgment character (ACK) (HARQ-ACK) is less than or equal to 2, find the position reserved for HARQ-ACK.

[0163] 2. When the number of bits in HARQ-ACK is greater than 2, map the already encoded HARQ-ACK;

[0164] 3. Part 1 (CSI-part1) and Part 2 (CSI-part2) of the mapped and encoded channel state information (CSI).

[0165] 4. Uplink shared channel (UL-SCH) after mapping and encoding.

[0166] 5. When the number of bits in HARQ-ACK is less than or equal to 2, the HARQ-ACK is mapped and encoded.

[0167] 6. Form codewords.

[0168] For details on the mapping process, please refer to section 6.2.7 of protocol TS38.212.

[0169] In steps 1 and 2, when determining the location of HARQ-ACK resources, it is generally required to start from the first symbol after DMRS. In step 3, when mapping CSI-part1, it is generally required to start from the first OFDM symbol.

[0170] Currently, when multiplexing UCI onto PUSCH, scheduling requests (SRs) are not reused.

[0171] 3. Scheduling request:

[0172] When a terminal device needs to send uplink data but lacks uplink resources, it can request uplink scheduling from the network by sending a scheduling request. Currently, terminal devices can send scheduling requests through the physical uplink control channel (PUCCH).

[0173] Scheduling requests can be categorized into positive scheduling requests (SRs) and negative scheduling requests (SRs). A scheduling request sent by the terminal device at the physical layer can be considered a positive scheduling request. Conversely, if the terminal device fails to send a scheduling request at the physical layer at the time specified for sending the configured resources, it can be considered a negative scheduling request.

[0174] In this embodiment of the application, the scheduling request can also be referred to as scheduling request information.

[0175] Currently, when a terminal device transmits a PUSCH that does not contain a UL-SCH in the serving cell, if the PUSCH overlaps with a PUCCH containing a positive SR in the serving cell, the terminal device will not transmit the PUSCH. That is, if the PUSCH does not contain a UL-SCH and overlaps with a PUCCH containing a positive SR, the terminal device will transmit the PUCCH but not the PUSCH. In this case, if the terminal device and other terminal devices are configured with different orthogonal sequences in the orthogonal matrix, and these multiple terminal devices need to send PUSCH based on the configured orthogonal sequences, the orthogonality between the uplink information transmitted by these multiple terminal devices will be disrupted because the terminal device transmits the PUCCH (and not the PUCCH based on the OCC) instead of the PUSCH, affecting the correct decoding on the network side.

[0176] For example, as shown in Figure 5, assume that terminal devices 1-4 are configured with different orthogonal sequences in an orthogonal matrix. In time slot 2, the PUSCH originally sent by terminal device 1 overlaps with the PUCCH, and the terminal device actually sends the PUCCH in time slot 2. Furthermore, in time slot 2, other terminal devices send PUSCH based on OCC. Therefore, the orthogonality between the uplink information transmitted by terminal devices 1-4 in time slot 2 is disrupted, potentially causing the network side to fail to correctly receive the uplink information transmitted by terminals 1-4.

[0177] For example, as shown in Figure 6, suppose terminal devices 1-4 are configured with different orthogonal sequences in the orthogonal matrix. On symbol 0, the PUSCH and PUCCH originally transmitted by terminal device 1 on single carrier (SC) 0 (which can be denoted as SC#0), SC#4, and SC#8 overlap. Terminal device 1 actually transmits PUCCH on SC#0, SC#4, and SC#8. Furthermore, on symbol 0, other terminal devices transmit PUSCH based on OCC. Therefore, on symbol 0, the orthogonality between the uplink information transmitted by terminal devices 1-4 is disrupted, which may cause the network side to fail to correctly receive the uplink information transmitted by terminals 1-4.

[0178] In this article, a single carrier can also be replaced with a subcarrier.

[0179] To address the issue mentioned above where the orthogonality between uplink information transmitted by terminal devices may be disrupted in certain scenarios, embodiments of this application provide a communication method, apparatus, and system. When the time-frequency resources of PUCCH and PUSCH overlap, the terminal device will transmit PUSCH on the time-frequency resources, and all or part of the information on PUSCH will be transmitted based on OCC, in order to protect the orthogonality of uplink information transmitted based on OCC in PUSCH from being disrupted, and to prevent the network side from being unable to correctly receive uplink information due to the orthogonality between uplink information.

[0180] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0181] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0182] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0183] In the embodiments of this application, "predefined," "pre-defined," "pre-configured," "pre-configured," or "locally configured" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when it leaves the factory, or configured when it first connects to the network. The embodiments of this application do not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and the embodiments of this application do not limit this.

[0184] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0185] In this embodiment of the application, "sending information to... (taking a terminal device as an example)" can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. "Receiving information from... (taking a terminal device as an example)" can be understood as the source of the information being the terminal device, and can include receiving information directly or indirectly from the terminal device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this embodiment of the application can be understood in a similar way, and will not be repeated here.

[0186] The technical solutions provided in this application can be used in various communication systems, such as Long Term Evolution (LTE) systems, 4G mobile communication systems, 5th Generation (5G) mobile communication systems and their evolution systems, 5th Generation Advanced (5GA) systems, non-terrestrial network (NTN) systems, vehicle-to-everything (V2X) systems, LTE and New Radio (NR) hybrid networking systems, device-to-device (D2D) systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, and future communication systems. Furthermore, the term "system" can be used interchangeably with "network."

[0187] It should be noted that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0188] It should be noted that the names of network elements appearing in this document are merely possible and exemplary names. If the actual names used by network elements in subsequent communication networks differ from those appearing in this document, it will not affect the application of the communication method provided in the embodiments of this application.

[0189] Figure 7 is a schematic diagram of the architecture of a possible, non-limiting communication system applicable to the embodiments of this application. As shown in Figure 7, the communication system includes RAN 100 and core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 7, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 7, collectively referred to as 120). RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 7). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0190] Optionally, the communication system 10 may also include an Internet 300. The Internet 300 may be connected to the core network 200 or the RAN 100.

[0191] RAN 100 can be a cellular system related to the 3rd generation partnership project (3GPP). RAN 100 can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems.

[0192] Terminal equipment refers to devices that provide voice and / or data connectivity to users, and can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the device form of the terminal.

[0193] RAN node 110, sometimes referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal equipment 120 are relative. For example, network element 120i in Figure 7 can be a helicopter or drone, which can be configured as a mobile base station. For terminal equipment 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal equipment. RAN node 110 and terminal equipment 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 7 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal equipment functions.

[0194] In one possible scenario, the RAN node can help terminals achieve wireless access, fulfilling the functions of a base station. For example, the RAN node can be a Node B (also called a base station), an evolved Node B (eNodeB) in an LTE system, a next-generation Node B (gNB) in a 5G system, an access point (AP), a transmission and reception point (TRP), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 7, 110a), a micro base station or indoor station (as shown in Figure 7, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software that can implement all or part of the functions of the RAN node.

[0195] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0196] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0197] Core network equipment (or core network elements) refers to the equipment in the core network that provides service support to terminals. Examples of some core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which will not be listed here.

[0198] The RAN node will be referred to as a network device below. The communication method provided in the embodiments of this application will be described in conjunction with the communication system shown in Figure 7.

[0199] It should be noted that the names of each network element, the message names between each network element, or the names of each parameter in the message in the following embodiments of this application are just examples. In specific implementations, other names may also be used, and this application does not specifically limit them.

[0200] Figure 8 is a flowchart of a communication method provided in an embodiment of this application, but this application does not limit the executing entity illustrated in the flowchart. For example, the terminal device in Figure 8 can also be a module applied to the first network element, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software that can implement all or part of the functions of the terminal device. As another example, the network device in Figure 8 can also be a module applied to the network device, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software that can implement all or part of the functions of the network device.

[0201] As shown in Figure 8, the communication method includes the following steps:

[0202] S801. The terminal device determines that the first time-frequency resource and the second time-frequency resource overlap; wherein, the first time-frequency resource is used to carry PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry PUSCH.

[0203] Wherein, the overlap between the first time-frequency resource and the second time-frequency resource means that the time-domain resources of the first time-frequency resource overlap with the time-domain resources of the second time-frequency resource (which may be partially or completely overlapping), and / or, the frequency-domain resources of the first time-frequency resource overlap with the frequency-domain resources of the second time-frequency resource (which may be partially or completely overlapping).

[0204] In this embodiment of the application, "time-frequency resources are used to carry... (taking PUCCH / PUSCH as an example)" can also be referred to as "time-frequency resources are used to transmit PUCCH / PUSCH". It is understood that "time-frequency resources are used to carry... (taking PUCCH / PUSCH as an example)" means that time-frequency resources can be used to transmit PUCCH / PUSCH, and PUCCH / PUSCH can be carried on time-frequency resources, but it does not mean that the terminal device has actually transmitted PUCCH / PUSCH on the time-frequency resources. That is to say, when the terminal device determines that the first time-frequency resource and the second time-frequency resource overlap, the terminal device has not yet transmitted uplink information on either the first or second time-frequency resource.

[0205] In this embodiment, the first time-frequency resource and the second time-frequency resource can be configured by the network device for the terminal device (i.e., the network device sends configuration information for configuring the first time-frequency resource and configuration information for configuring the second time-frequency resource to the terminal device). The first time-frequency resource used to carry PUCCH can be understood as the time-frequency resource configured by the network device for the terminal device that can be used to carry PUCCH, including the first time-frequency resource. Similarly, the second time-frequency resource used to carry PUSCH can be understood as the time-frequency resource configured by the network device for the terminal device that can be used to carry PUSCH, including the second time-frequency resource.

[0206] In this embodiment of the application, the PUCCH carried on the first time-frequency resource may include scheduling request information. This can be understood as the first time-frequency resource including time-frequency resources for sending scheduling request information. The scheduling request information included in the PUCCH can be either active or passive scheduling request information.

[0207] In this embodiment of the application, the terminal device can determine whether the scheduling request information is an active scheduling request information or a passive scheduling request information based on whether it needs to send scheduling request information.

[0208] For example, suppose that in the first time-frequency resource, the time-frequency resource corresponding to time slot 1 is used to send scheduling request information. If the terminal device decides to send the scheduling request information at the physical layer, the terminal device can consider the scheduling request information included in the PUCCH as an active scheduling request information. If the terminal device decides not to send the scheduling request information at the physical layer, the terminal device can consider the scheduling request information included in the PUCCH as a passive scheduling request information.

[0209] Optionally, in addition to scheduling request information, the PUCCH may also include other uplink information. For example, the PUCCH may also include one or more uplink information such as CSI and HARQ-ACK. The inclusion of other uplink information in the PUCCH carried on the first time-frequency resource can also be understood as the first time-frequency resource including resources used for transmitting other uplink information.

[0210] It is understandable that one or more uplink information included in the PUCCH that can be carried on the first time-frequency resource are information that the terminal device expects to transmit on the first time-frequency resource via the PUCCH before S801, and do not represent that the terminal device actually sends the PUCCH on the first time-frequency resource to send this one or more information.

[0211] In this embodiment, the uplink information carried by the PUSCH on the second time-frequency resource may include at least one of the following: service data or control information. It is understood that the uplink information included in the PUSCH is information that the terminal device anticipates transmitting via the PUSCH on the second time-frequency resource before S801.

[0212] Optionally, the PUSCH, which can carry all or part of the uplink information on the second time-frequency resource, can be extended based on OCC. That is, prior to S801, the terminal device anticipates transmitting all or part of the PUSCH information on the second time-frequency resource based on OCC. In this case, the second time-frequency resource can be understood as a time-frequency resource reserved for one extension of the PUSCH information based on OCC. It is understood that transmitting information based on OCC requires multiple extensions, and the terminal device can reserve multiple time-frequency resources to carry these multiple extensions. The second time-frequency resource is the one that overlaps with the first time-frequency resource among these multiple time-frequency resources.

[0213] Optionally, if the terminal device anticipates performing OCC extension on all or part of the information included in the PUSCH based on a configured orthogonal sequence (or OCC sequence), the second time-frequency resource can be a time-frequency resource reserved for one extension of the information based on the orthogonal sequence. For example, assuming the terminal device anticipates extending the information included in the PUSCH based on orthogonal sequence 1, and the terminal device reserves time-frequency resources for the extended information, the second time-frequency resource can be a time-frequency resource reserved for one extension in multiple extensions of the information.

[0214] Optionally, if the terminal device anticipates transmitting all or part of the uplink information in the PUSCH based on inter-slot OCC, the time-domain resources of the second time-frequency resource may include one time slot, and the frequency-domain resources may include at least one subcarrier. If the terminal device anticipates transmitting all or part of the information included in the PUSCH based on intra-symbol OCC, the second time-frequency resource may include at least one RE. For details, please refer to the above introduction to OCC extensions.

[0215] For example, suppose the terminal device plans to use inter-slot OCC to transmit uplink information in PUSCH, and plans to extend the information twice based on an OCC sequence of length 2, with the time slot as the extension unit. In order to carry the extended information, the terminal device reserves two time slots and corresponding frequency domain resources. The second time-frequency resource can be the time slot that overlaps with the first time-frequency resource in these two time slots and the time-frequency resource corresponding to that time slot.

[0216] For example, suppose the terminal device plans to transmit uplink information in the PUSCH based on intra-symbol OCC, and plans to extend the information twice based on OCC sequences of length 2, using complex-valued symbol blocks within the OFDM symbol as extension units. To carry the extended information, the terminal device extends the 6 REs configured within an OFDM symbol into 12 REs. These 12 REs can be divided into two RE groups. The second time-frequency resource can be any RE group that overlaps with the first time-frequency resource from these two RE groups.

[0217] It is understandable that when the terminal device anticipates transmitting all or part of the information included in the PUSCH on the second time-frequency resource based on OCC, the terminal device has not yet actually mapped the extended information onto the second time-frequency resource.

[0218] S802, the terminal device transmits a PUSCH on the second time-frequency resource, and multiplies all or part of the uplink information in the PUSCH with elements in the orthogonal sequence. That is, the terminal device transmits a PUSCH on the second time-frequency resource and transmits all or part of the uplink information in the PUSCH based on OCC.

[0219] Based on the communication method provided in the embodiments of this application, the terminal device can send PUSCH based on OCC when PUSCH and PUCCH overlap, so as to protect the orthogonality of uplink information sent between different terminals in the scenario where other terminals also send uplink information based on OCC, and avoid the network side being unable to correctly decode the received uplink information due to the destruction of orthogonality.

[0220] Optionally, the orthogonal sequence can be configured by the network device for the terminal device. Alternatively, the terminal device can obtain the orthogonal sequence through other means, which is not limited in this embodiment. Other orthogonal sequences in the matrix to which the orthogonal sequence belongs can be configured for other terminal devices.

[0221] Optionally, in addition to the OCC sequence, the network device can also configure other OCC-related parameters for the terminal device. For example, when the terminal device transmits information based on OCC, it can select the OCC type (which can be called the OCC scheme), such as inter-slot OCC, inter-symbol OCC, and intra-symbol OCC, and configure the OCC length (or the length of the orthogonal sequence). Alternatively, the terminal device can also obtain other OCC-related parameters through other means, which is not limited in this embodiment.

[0222] In S802, after the terminal device determines that the second time-frequency resource overlaps with the first time-frequency resource, it transmits all or part of the information in the PUSCH based on OCC on the second time-frequency resource and other time-frequency resources corresponding to the first orthogonal sequence. Here, the first orthogonal sequence is the orthogonal sequence to which the OCC element corresponding to the second time-frequency resource belongs. At this time, the second time-frequency resource can be understood as an extension unit that expands all or part of the information in the PUSCH when transmitting all or part of the information based on OCC, and the other time-frequency resources corresponding to the first orthogonal sequence are other extension units.

[0223] Based on the number of times the information is extended using OCC, the terminal device can determine the second time-frequency resource and other time-frequency resources corresponding to the first orthogonal sequence. The number of time-frequency resources corresponding to the first orthogonal sequence (including the second time-frequency resource and other time-frequency resources corresponding to the first orthogonal sequence) is the same as the length of the orthogonal sequence configured by the terminal device, or the number of time-frequency resources corresponding to the first orthogonal sequence can be an integer multiple of the orthogonal sequence length. The terminal device can send all or part of the uplink information included in the PUSCH on each of the multiple time-frequency resources corresponding to the first orthogonal sequence, thereby achieving the extension of all or part of the uplink information included in the PUCCH.

[0224] In this process, all or part of the information in the PUSCH transmitted by the terminal device on each time-frequency resource corresponding to the first orthogonal sequence can be multiplied by an element of the orthogonal sequence. Uplink information multiplied by different OCC elements on different time-frequency resources corresponding to the first orthogonal sequence can be the same. For example, if the terminal device determines to expand information 1 by multiplying it by different elements in the orthogonal sequence, and determines multiple time-frequency resources to carry the expanded information 1, the second time-frequency resource can be one of these multiple time-frequency resources that overlaps with the first time-frequency resource.

[0225] For example, suppose the terminal device plans to transmit information based on OCC extension in time slots 1-4, and the terminal device determines that time slot 2 overlaps with the first time-frequency resource, thus being the second time-frequency resource. The information transmitted by the terminal device in time slot 1 is multiplied by the first element of the orthogonal sequence, the information transmitted in time slot 3 is multiplied by the third element of the orthogonal sequence, and the information transmitted in time slot 4 is multiplied by the fourth element of the orthogonal sequence. The terminal device can determine that time slots 1-4 correspond to the first orthogonal sequence, and time slot 2 corresponds to the second element of the first orthogonal sequence, based on the elements multiplied with the information in time slots 1, 3, and 4. When the terminal device transmits information based on OCC in time slots 1-4, the information transmitted in time slot 2 is multiplied by the second element of the first orthogonal sequence.

[0226] Optionally, the terminal device may also transmit a portion of the PUSCH information on the second time-frequency resource without basing it on the OCC elements of the first orthogonal sequence. The information in the PUSCH transmitted without basing it on the first orthogonal sequence does not need to be multiplied with elements of the first orthogonal sequence when mapped to the second time-frequency resource. For example, when the terminal device transmits the PUSCH on the second time-frequency resource, if the PUSCH includes DMRS, the terminal device may transmit the DMRS without basing it on the first orthogonal sequence. Similarly, on other time-frequency resources corresponding to the first orthogonal sequence, the terminal device may also transmit a portion of the PUSCH information without basing it on the first orthogonal sequence.

[0227] Optionally, in this embodiment, the terminal device can transmit all or part of the uplink information in the PUSCH based on inter-slot OCC. In this case, the time-domain resource of the second time-frequency resource may include one time slot, and the frequency-domain resource may include at least one subcarrier. The other time-frequency resources corresponding to the first orthogonal sequence also include one time slot and at least one subcarrier. For details, please refer to the above description of inter-slot OCC extension.

[0228] Optionally, the terminal device may use intra-symbol OCC to transmit all or part of the uplink information in the PUSCH. In this case, the terminal device may transmit the PUSCH on an OFDM symbol that includes at least two RE groups, and the second time-frequency resource may be at least one RE group in the OFDM symbol that overlaps with the first time-frequency resource. Other time-frequency resources corresponding to the first orthogonal sequence are other RE groups in the OFDM symbol. For details, please refer to the above introduction to OCC extension.

[0229] In one possible implementation, the terminal device can directly decide to send PUSCH on the second time-frequency resource if it is determined that the first time-frequency resource and the second time-frequency resource overlap.

[0230] In another possible implementation, the terminal device may decide to send the PUSCH on the second time-frequency resource if it determines that the first and second time-frequency resources overlap and it anticipates transmitting all or part of the information in the PUSCH based on OCC. In this implementation, if the terminal device determines that it will not transmit uplink information in the PUSCH based on OCC, the terminal device may choose not to send the PUSCH on the second time-frequency resource.

[0231] The following section elaborates on how terminal devices transmit PUSCH on the second time-frequency resource in different scenarios.

[0232] Scenario 1: The terminal device multiplexes the scheduling request information included in the PUCCH into the PUSCH and transmits the PUSCH on the second time-frequency resource. In other words, the PUSCH transmitted by the terminal device on the second time-frequency resource includes scheduling request information. The terminal device can transmit the scheduling request information in the PUSCH based on the OCC. In other words, the terminal device transmits all or part of the information included in the PUSCH on each time-frequency resource corresponding to the first orthogonal sequence, and the transmitted information includes scheduling information. The information transmitted on each time-frequency resource corresponding to the first orthogonal sequence is multiplied by the OCC element corresponding to each time-frequency resource.

[0233] The following example illustrates how a terminal device transmits all or part of the information in the PUSCH on the second time-frequency resource based on OCC, and how scheduling request information is multiplexed and sent on the PUSCH.

[0234] For example, suppose a terminal device plans to transmit information 1, information 2, and information 3, which originally comprised the PUSCH, based on OCC. The terminal device reserves time slots 1-4 for OCC extension of information 1, time slots 5-8 for OCC extension of information 2, and time slots 9-12 for OCC extension of information 3. The orthogonal sequence configured by the terminal device is orthogonal sequence 1 in the matrix. The network device can also configure other orthogonal sequences in the matrix for other terminal devices. These other terminal devices can then transmit information based on OCC in time slots 1-12 using their own configured orthogonal sequences. Figure 9 illustrates the principle of a terminal device configured with orthogonal sequence 1 transmitting PUSCH based on OCC in time slots 1-12; other terminal devices are not shown.

[0235] For time slots 1-4, the terminal device anticipates that information 1 is multiplied by the first element of orthogonal sequence 1 and then mapped onto time slot 1; it anticipates that information 1 is multiplied by the second element of orthogonal sequence 1 and then mapped onto time slot 2, and so on for time slots 3 and 4. For time slots 5-8, the terminal device anticipates that information 2 is multiplied by the first element of orthogonal sequence 1 and then mapped onto time slot 5; it anticipates that information 2 is multiplied by the second element of orthogonal sequence 1 and then mapped onto time slot 6, and so on for time slots 7 and 8. For time slots 9-12, the terminal device anticipates that information 3 is multiplied by the first element of orthogonal sequence 1 and then mapped onto time slot 9; it anticipates that information 3 is multiplied by the second element of orthogonal sequence 1 and then mapped onto time slot 10, and so on for time slots 11 and 12.

[0236] The terminal device determines that time slot 6 overlaps with the time-frequency resource used to carry PUCCH. The terminal device then determines to transmit PUSCH on time slot 6 and multiplexes the scheduling request information originally included in the PUCCH into the PUSCH transmitted through time slot 6. In other words, the terminal device determines that the second time-frequency resource (time slot 6) overlaps with the time-frequency resource used to carry PUCCH, and determines to transmit the information in the PUSCH based on OCC on the second time-frequency resource, and to multiplex the scheduling request information into the PUSCH transmitted through the second time-frequency resource.

[0237] In addition, time slots 1-4, 9-12 do not overlap with the time-frequency resources used to carry PUCCH. As expected, the terminal equipment transmits the corresponding information based on OCC on time slots 1-4 and 5-8.

[0238] To implement OCC extension for the scheduling request information, the terminal device determines that the scheduling request information will also be multiplexed in the PUSCH transmitted through time slots 5, 7, and 8. Based on the length of orthogonal sequence 1 (4) and the element multiplied by the information transmitted in time slots 5, 7, and 8, the terminal device determines the second element in orthogonal sequence 1 corresponding to time slot 6. When the terminal device multiplexes the scheduling request information in the PUSCH transmitted through time slot 6, it multiplies the scheduling request information with the second element of orthogonal sequence 1. Furthermore, when the terminal device multiplexes the scheduling request information in the PUSCH transmitted through time slot 5, it multiplies the scheduling request information with the first element of orthogonal sequence 1; when it multiplexes the scheduling request information in the PUSCH transmitted through time slot 7, it multiplies the scheduling request information with the third element of orthogonal sequence 1; and when it multiplexes the scheduling request information in the PUSCH transmitted through time slot 8, it multiplies the scheduling request information with the third element of orthogonal sequence 1.

[0239] In this application embodiment, there is no limitation on whether the information transmitted based on OCC on different time-frequency resources is the same. Taking the example shown in Figure 9, in this application embodiment, the information 1 carried in time slots 1-4, the information 2 carried in time slots 5-8, and the information 3 carried in time slots 9-12 can be the same or different.

[0240] This application does not impose restrictions on the rules for reusing scheduling request information on PUSCH. Several possible implementations provided by this application are described below.

[0241] Implementation 1: The rule for multiplexing scheduling request information on PUSCH can be referenced from the rule for multiplexing HARQ-ACK on PUSCH.

[0242] For example, scheduling request information can be mapped onto the PUSCH starting from the nth symbol following the first group of consecutive OFDM symbols of the DMRS carried by the PUSCH. Taking the second time-frequency resource as an example, the first OFDM symbol of the time-frequency resource transmitting scheduling request information in the second time-frequency resource can be the nth symbol following the first group of consecutive OFDM symbols of the DMRS carried by the PUSCH. Here, n can be a positive integer, such as 1, 2, etc. Alternatively, scheduling request information can be mapped onto the PUSCH starting from the nth symbol following other groups (e.g., the second group, the third group, etc., which are not limited in this embodiment) of the DMRS carried by the PUSCH. That is, the first OFDM symbol of the time-frequency resource transmitting scheduling request information in the PUSCH can be the nth symbol following other groups of consecutive OFDM symbols of the DMRS carried by the PUSCH. Here, n can be a positive integer, such as 1, 2, etc.

[0243] Optionally, if the number of bits in the scheduling request information does not exceed a first value, the scheduling request information can be mapped into the PUSCH using a puncturing method. That is, the time-frequency resources in the PUSCH that transmit scheduling request information have discontinuous frequency domain resources.

[0244] Optionally, if the number of bits in the scheduling request information exceeds a first value, the scheduling request information may not be mapped into the PUSCH using a puncturing method. In one possible design, the time-frequency resources in the PUSCH that transmit the scheduling request information have a frequency domain resource that is a continuous segment of the second time-frequency resources. Of course, if the scheduling request information is not mapped into the PUSCH using a puncturing method, the frequency domain resources in the PUSCH that transmit the scheduling request information may also be discontinuous; this embodiment does not limit this.

[0245] The embodiments of this application do not limit the first value; for example, the first value can be 2 bits.

[0246] For example, assuming the terminal device transmits all or part of the uplink information included in the PUSCH based on the OCC between time slots, the time domain resource of the second time-frequency resource is one time slot. The rule for multiplexing the scheduling request information on the PUSCH refers to the rule for multiplexing HARQ-ACK on the PUSCH, with the first value being 2 bits, as shown in (1) of Figure 10. When the number of bits in the scheduling request information does not exceed 2 bits, the scheduling request information can be mapped in the PUSCH using a puncturing method. As shown in (2) of Figure 10, when the number of bits in the scheduling request information exceeds 2 bits, the scheduling request information is not mapped in the PUSCH using a puncturing method, and the frequency domain resource used to transmit the scheduling request information is continuous. Furthermore, as shown in (1) and (2) of Figure 10, the scheduling request information starts from the first symbol after the first group of consecutive OFDM symbols in the DMRS and is mapped in the PUSCH.

[0247] Implementation 2: The rules for reusing scheduling request information on PUSCH can be referenced from the rules for reusing CSI-part on PUSCH.

[0248] For example, scheduling request information can be mapped onto the PUSCH starting from the first OFDM symbol of the second time-frequency resource. That is, in the second time-frequency resource, the first OFDM symbol of the time-frequency resource that transmits scheduling request information is the first OFDM symbol in the PUSCH that does not carry DMRS.

[0249] For example, suppose the terminal device uses the inter-slot OCC to send all or part of the uplink information included in the PUSCH, and the time domain resource of the second time-frequency resource is one time slot. The rule for multiplexing scheduling request information on the PUSCH refers to the rule for multiplexing CSI-part on the PUSCH, as shown in Figure 11. The scheduling request information starts from the first OFDM symbol of the second time-frequency resource and is mapped in the PUSCH.

[0250] Optionally, in Scenario 1, if the terminal device determines that the scheduling request information included in the PUCCH is an active scheduling request, it may reuse the scheduling request information in the PUSCH sent via the second time-frequency resource. If the terminal device determines that the scheduling request information included in the PUCCH is a passive scheduling request, the terminal device may choose not to reuse the scheduling request information in the PUSCH sent via the second time-frequency resource.

[0251] Optionally, in Scenario 1, the PUSCH transmitted by the terminal device on the second time-frequency resource may further include all or part of the uplink information included in the PUSCH that the terminal device expected to transmit on the second time-frequency resource before S801 (which can be understood as all or part of the uplink information included in the PUSCH that the terminal device originally intended to transmit on the second time-frequency resource before S801), such as the information included in UL-SCH. Optionally, the terminal device may transmit this part of the information via OCC when transmitting the PUSCH.

[0252] This application does not specifically limit the method by which all or part of the uplink information included in the PUSCH that the terminal device expects to transmit on the second time-frequency resource is reused on the PUSCH sent on the second time-frequency resource. For example, as shown in (1) or (2) of FIG10 and FIG11, all or part of the uplink information included in the PUSCH that was originally intended to be transmitted on the second time-frequency resource can be reused on the empty time-frequency resource in the second time-frequency resource.

[0253] Scenario 2: Prior to S801, the PUCCH that could be carried on the first time-frequency resource included scheduling request information and other information. In this case, the terminal device could multiplex the scheduling request information and all or part of the other information included in the PUCCH into a PUSCH and send the PUSCH on the second time-frequency resource. Specifically, the terminal device could send the scheduling request information in the PUSCH, as well as all or part of the other information originally contained in the PUCCH, via the OCC. That is, the PUSCH sent by the terminal device on each time-frequency resource corresponding to the first orthogonal sequence includes scheduling request information and all or part of the other information originally contained in the PUCCH. The information sent on each time-frequency resource corresponding to the first orthogonal sequence is multiplied by the OCC element corresponding to each time-frequency resource.

[0254] In this embodiment, the information originally included in the PUCCH and multiplexed into the PUSCH can be referred to as the first information. That is, in scenario one, the first information includes scheduling request information. In scenario two, the first information includes scheduling request information and other information. The resource in the PUSCH that transmits the first information can be referred to as the third time-frequency resource.

[0255] This application does not limit the rules for mapping the first information to PUSCH in the embodiments.

[0256] For example, the mapping rule for the first information in the time domain may include: the first OFDM symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying DMRS in the PUSCH. As another example, the mapping rule for the first information in the time domain may include: the first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS. For details, please refer to the above description of the mapping rule for scheduling request information in Scenario 1.

[0257] For example, the mapping rule for the first information in the frequency domain may include: if the number of bits of the first information does not exceed a first value, the first information is mapped in the PUSCH using a puncturing method, and / or, if the number of bits of the first information exceeds the first value, the first information is not mapped in the PUSCH using a puncturing method. Optionally, if the first information is not mapped in the PUSCH using a puncturing method, the frequency domain resource of the third time-frequency resource may be a continuous segment of the second time-frequency resource, or it may be discontinuous; this embodiment does not limit this. For details, please refer to the above description of the mapping rule for the scheduling request information in Scenario 1.

[0258] Optionally, different pieces of information in the first information can be mapped in the PUSCH in different ways. This application embodiment does not limit the way different pieces of information in the first information are mapped in the PUSCH. For example, the mapping rules for the scheduling request information in the first information can refer to the mapping rules of the CSI-part, and the mapping rules for the HARQ-ACK in the first information can refer to the above description of the mapping rules for HARQ-ACK in the existing UL-SCH.

[0259] Optionally, in scenario two, if the terminal device determines that the scheduling request information included in the PUCCH is positive scheduling request information, it may reuse the scheduling request information in the PUSCH sent through the second time-frequency resource. If the terminal device determines that the scheduling request information included in the PUCCH is negative scheduling request information, the terminal device may not reuse the scheduling request information in the PUSCH sent through the second time-frequency resource, that is, the first information does not include scheduling request information.

[0260] Optionally, in scenario two, the PUSCH transmitted by the terminal device on the second time-frequency resource may also include all or part of the uplink information included in the PUSCH that the terminal device expects to transmit on the second time-frequency resource before S801. For details, please refer to the above introduction of scenario one.

[0261] Scenario 3: The PUSCH sent by the terminal device on the second time-frequency resource includes the first information, but the first information does not include the scheduling request information.

[0262] Specifically, if the uplink information originally included in the PUCCH is scheduling request information (i.e., before S801, the uplink information included in the PUCCH that could be carried on the first time-frequency resource is scheduling request information), the terminal device does not multiplex the scheduling request information onto the PUSCH sent through the second time-frequency resource. In other words, the terminal device does not transmit the information originally included in the PUCCH, or in other words, the terminal device discards the PUCCH.

[0263] If the PUCCH originally includes uplink information such as scheduling request information and other information (e.g., HARQ-ACK), the terminal device may choose not to reuse the scheduling request information, but instead reuse all or part of the other information in the PUSCH transmitted via the second time-frequency resource. Alternatively, the terminal device may choose not to reuse the other information in the PUSCH, meaning the terminal device may not transmit the information originally included in the PUCCH.

[0264] Optionally, if the terminal device reuses other information originally included in the PUCCH onto the PUSCH, this application embodiment does not limit the rules for reusing other information included in the PUCCH onto the PUSCH. For example, the rules for reusing at least one of the HARQ-ACK information, CSI part 1, or CSI part 2 included in the UL-SCH onto the PUSCH can be referred to above.

[0265] Optionally, in scenario three, the PUSCH transmitted by the terminal device on the second time-frequency resource may also include all or part of the uplink information included in the PUSCH that the terminal device expects to transmit on the second time-frequency resource before S801. For details, please refer to the above introduction of scenario one.

[0266] Optionally, in scenario three, the terminal device can also send second information to the network device on the fourth time-frequency resource. This second information is used to request an uplink grant (UL grant). After receiving the second information, the network device can allocate uplink grant resources to the terminal device. The terminal device can request uplink grant by sending the second information to the network device through a random access procedure. This application embodiment does not limit the fourth time-frequency resource.

[0267] Based on this solution, even if the terminal device does not transmit scheduling request information, it can request uplink authorization to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0268] Optionally, in scenario three, the terminal device may send the second information if it determines that the scheduling request information included in the PUCCH is an active scheduling request. If the terminal device determines that the scheduling request information included in the PUCCH is a passive scheduling request, the terminal device may choose not to send the second information.

[0269] For example, the following description can be added to the communication protocol:

[0270] If the PUCCH contains a positive SR and overlaps with a PUSCH using the OCC scheme, the terminal device initiates a random access procedure on the serving cell and cancels the pending SR.

[0271] Optionally, in scenario three, the terminal device can also send a buffer status report (BSR) to the network device on the fifth time-frequency resource. The buffer status report indicates the amount of data cached by the terminal device. After receiving the BSR, the network device can allocate uplink resources to the terminal device based on the amount of data cached by the terminal device.

[0272] Based on this scheme, if the terminal device does not transmit scheduling request information, it can send a BSR to request the network side to allocate uplink resources, thus avoiding the inability to transmit uplink information normally due to the lack of a scheduling request.

[0273] For example, the following event can be added to the event defined in the communication protocol that triggers the terminal device to send a BSR:

[0274] SR overlaps with PUSCH under OCC scheme (inter-slot OCC / intra-symbol OCC).

[0275] In addition, this application embodiment also provides another communication method. This communication method includes the following steps:

[0276] S1101. The terminal device determines that the first time-frequency resource and the second time-frequency resource overlap; wherein, the first time-frequency resource is used to carry PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry PUSCH.

[0277] For details on S1101, please refer to the above introduction to S801.

[0278] S1102. The terminal device sends PUCCH on the first time-frequency resource, and the terminal device transmits all or part of the uplink information included in PUCCH through OCC, that is, all or part of the uplink information included in PUCCH is multiplied with the elements in the orthogonal sequence.

[0279] Specifically, the PUCCH information, including all or part of the uplink information, is transmitted via OCC. For details, please refer to the introduction of OCC above.

[0280] Optionally, the terminal device may transmit all or part of the uplink information included in the PUCCH through the time-slot OCC or the symbol-intra-OCC.

[0281] Based on the communication method provided in the embodiments of this application, the terminal device can send PUCCH through OCC when PUSCH and PUCCH overlap, so as to protect the orthogonality of uplink information sent between different terminals in the scenario where other terminals also send uplink information based on OCC, and avoid the network side being unable to correctly decode the received uplink information due to the destruction of orthogonality.

[0282] Optionally, the terminal device may multiplex all or part of the uplink information in the PUSCH that is expected to be carried on the second time-frequency resource onto the PUCCH carried on the first time-frequency resource. That is, all or part of the uplink information originally included in the PUSCH can be multiplexed into the PUCCH carried on the first time-frequency resource and sent to the network device via the PUCCH. Optionally, all or part of the information originally included in the PUSCH and multiplexed onto the PUCCH can be transmitted based on OCC.

[0283] This application does not limit the rules for reusing information from PUSCH onto PUCCH. For example, refer to the above description of the specific implementation of reusing information from PUCCH onto PUSCH in S802.

[0284] The above mainly describes the solutions provided by the embodiments of this application from the perspective of the interaction between different modules or network elements in the terminal device and the terminal device. Accordingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be the terminal device in the above method embodiments, or a component / module included in the terminal device in the above method embodiments, or a network device in the above method embodiments, or a component / module included in the network device in the above method embodiments.

[0285] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0286] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0287] Figure 12 shows a schematic diagram of a communication device 1200. The communication device 1200 includes a transceiver module 1201 and a processing module 1202. The transceiver module 1201 can also be referred to as a transceiver unit 1201. The processing module 1202 can also be referred to as a processing unit 1202.

[0288] The transceiver module 1201 can realize the functions of receiving and / or sending. The processing module 1202 can realize the processing function.

[0289] Optionally, the communication device 1200 may also include other modules, such as a storage module 1203, which can perform storage functions.

[0290] In one possible design, the communication device 1200 can implement the functions of the terminal device in the above method embodiments. Specifically, the transceiver module 1201 can implement the receiving and / or transmitting functions of the terminal device in the above method embodiments. The processing module 1202 can implement the processing functions of the terminal device in the above method embodiments. For example, the processing module 1202 is used to determine that a first time-frequency resource and a second time-frequency resource overlap; wherein the first time-frequency resource is used to carry a PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry a PUSCH. The transceiver module 1201 is used to transmit a PUSCH on the second time-frequency resource, where all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0291] In another possible design, the communication device 1200 can implement the functions of the network device in the above method embodiments. Specifically, the transceiver module 1201 can implement the receiving and / or sending functions of the network device in the above method embodiments. The processing module 1202 can implement the processing functions of the network device in the above method embodiments. For example, the processing module 1202 is used to determine configuration information. The transceiver module 1201 is used to send configuration information to the terminal device. The configuration information is used to configure a first time-frequency resource and a second time-frequency resource, wherein the first time-frequency resource and the second time-frequency resource overlap. The first time-frequency resource is used to carry a PUCCH, which includes scheduling request information, and the second time-frequency resource is used to carry a PUSCH. The transceiver module 1201 is also used to receive a PUSCH on the second time-frequency resource, where all or part of the uplink information in the PUSCH is multiplied by elements in an orthogonal sequence.

[0292] Alternatively, in the communication device shown in Figure 12, the names of the various modules may not be those shown in the figure.

[0293] If the modules in Figure 12 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0294] In this embodiment, the communication device 1200 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0295] Figure 13 shows a schematic diagram of another communication device 1300. As shown in Figure 13, the communication device 1300 includes one or more processors 1001, a communication line 1002, and at least one communication interface (Figure 13 is only an example illustrating the inclusion of a communication interface 1004 and a processor 1001), and optionally may also include a memory 1003.

[0296] The processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of programs according to the present application.

[0297] The communication line 1002 may include a path for connecting different components.

[0298] The communication interface 1004 can be a transceiver module used to communicate with other modules, devices, or communication networks, such as Ethernet, RAN, terminals, and wireless local area networks (WLAN). For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 1004 can also be a transceiver circuit or input / output interface located within the processor 1001, used to implement signal input and signal output for the processor.

[0299] The memory 1003 can be a device with storage function. For example, it can be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions; random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via communication line 1002. The memory can also be integrated with the processor.

[0300] The memory 1003 stores computer execution instructions for implementing the scheme of this application, and the processor 1001 controls the execution. The processor 1001 executes the computer execution instructions stored in the memory 1003, thereby implementing the communication method provided in the embodiments of this application.

[0301] Alternatively, in this embodiment of the application, the processor 1001 may execute the processing-related functions in the communication method provided in the above embodiments of the application, and the communication interface 1004 may be responsible for communicating with other devices or communication networks. This embodiment of the application does not specifically limit this.

[0302] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0303] In a specific implementation, as one embodiment, the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 in FIG13.

[0304] In a specific implementation, as one embodiment, the communication device 1300 may include multiple processors, such as processor 1001 and processor 1007 in FIG. 13. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: CPU, microprocessor, digital signal processing (DSP) processor, microcontroller unit (MCU), or artificial intelligence processor, etc., various computing devices that run software, and each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0305] In a specific implementation, as one embodiment, the communication device 900 may further include an output device 1005 and an input device 1006. The output device 1005 communicates with the processor 1001 and can display information in various ways. For example, the output device 1005 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1006 communicates with the processor 1001 and can receive user input in various ways. For example, the input device 1006 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0306] The aforementioned communication device 1300 may sometimes be referred to as a communication equipment, which can be a general-purpose device or a special-purpose device. For example, the communication device 1300 may be a terminal device, a network device, or a device with a similar structure to that in Figure 13, as described above. The embodiments of this application do not limit the type of the communication device 1300.

[0307] Furthermore, the composition shown in FIG13 does not constitute a limitation on the communication device. In addition to the components shown in FIG13, the communication device 1300 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0308] Optionally, in the communication device 1200 of FIG12, the functions / implementation processes of the transceiver module 1201 and the processing module 1202 can be implemented by the processor 1001 in the communication device 1300 shown in FIG13 calling computer execution instructions stored in the memory 1003. Alternatively, the functions / implementation processes of the transceiver module 1201 can be implemented by the communication interface 1004 in the communication device 1300 shown in FIG13, and the functions / implementation processes of the processing module 1202 can be implemented by the processor 1001 in the communication device 1300 shown in FIG13 calling computer execution instructions stored in the memory 1003.

[0309] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as FPGAs, programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0310] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, DSP chip, MCU, artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0311] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor for implementing the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0312] For example, Figure 14 shows a schematic diagram of a chip system. This chip system can implement the functions of the terminal device or network device in the above method embodiments. As shown in Figure 14, the chip system includes a processor module, a storage module, a power supply module, and an RF / antenna module.

[0313] The processor module is used for various calculations. The CPU is responsible for executing various instructions, including those for applications, operating systems, and other software. The graphics processing unit (GPU) is mainly responsible for graphics processing, but the CPU can also handle some graphics tasks, such as rendering application interfaces. The modem is used to modulate or demodulate signals so that digital signals can be transmitted in space.

[0314] In the storage module, RAM is temporary storage space used to temporarily store data that is currently in use. For example, if the chip system is located in the phone, RAM can store open web pages, messages from chat applications, game status, etc. ROM is read-only storage space. For example, if the chip system is located in the phone, ROM can store system files, pre-installed applications, and firmware.

[0315] The power module is used to provide voltage and current to other modules to maintain the normal operation of the chip.

[0316] Radio frequency / antenna modules are used to amplify signals and radiate them into space, or to receive wireless signals in space.

[0317] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0318] Optionally, embodiments of this application also provide a computer program product storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0319] Optionally, embodiments of this application also provide a communication system, which includes the network device and terminal device described in the above method embodiments.

[0320] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0321] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0322] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: It is determined that the first time-frequency resource and the second time-frequency resource overlap; wherein, the first time-frequency resource is used to carry the Physical Uplink Control Channel (PUCCH), which includes scheduling request information, and the second time-frequency resource is used to carry the Physical Uplink Shared Channel (PUSCH); The PUSCH is transmitted on the second time-frequency resource, and all or part of the uplink information in the PUSCH is multiplied by elements in the orthogonal sequence.

2. The method according to claim 1, characterized in that, The PUSCH includes first information, which includes the scheduling request information.

3. The method according to claim 2, characterized in that, The first orthogonal frequency division multiplexing (OFDM) symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying the demodulation reference signal DMRS in the PUSCH. The third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

4. The method according to claim 3, characterized in that, If the number of bits of the first information does not exceed a first value, the first information is mapped in the PUSCH using a punched method; and / or, If the number of bits of the first information exceeds a first value, the first information is mapped in the PUSCH without punching holes.

5. The method according to claim 2, characterized in that, The first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

6. The method according to any one of claims 2-5, characterized in that, When the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

7. The method according to claim 1, characterized in that, The PUSCH includes first information, which does not include the scheduling request information, and the method further includes: A second message is sent on the fourth time-frequency resource, the second message being used to request uplink authorization.

8. The method according to claim 1, characterized in that, The PUSCH includes first information, which does not include the scheduling request information, and the method further includes: A cache status report is sent on the fifth time-frequency resource, the cache status report being used to indicate the amount of data cached by the terminal device.

9. The method according to any one of claims 2-8, characterized in that, The first information also includes uplink information in the PUCCH that is different from the scheduling request information.

10. A communication method, characterized in that, The method includes: Send configuration information to the terminal device. The configuration information is used to configure a first time-frequency resource and a second time-frequency resource. The first time-frequency resource and the second time-frequency resource overlap. The first time-frequency resource is used to carry the Physical Uplink Control Channel (PUCCH), which includes scheduling request information. The second time-frequency resource is used to carry the Physical Uplink Shared Channel (PUSCH). The PUSCH is received on the second time-frequency resource, and all or part of the uplink information in the PUSCH is multiplied by elements in the orthogonal sequence.

11. The method according to claim 10, characterized in that, The PUSCH includes first information, which includes the scheduling request information.

12. The method according to claim 11, characterized in that, The first OFDM symbol of the third time-frequency resource is the first OFDM symbol after the first group of consecutive OFDM symbols carrying the demodulation reference signal DMRS in the PUSCH. The third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

13. The method according to claim 11, characterized in that, The first ODFM symbol of the third time-frequency resource is the first ODFM symbol in the PUSCH that does not carry DMRS, wherein the third time-frequency resource is the time-frequency resource in the PUSCH that transmits the first information.

14. The method according to any one of claims 11-13, characterized in that, When the scheduling request information is an active scheduling request information, the first information includes the scheduling request information.

15. The method according to claim 10, characterized in that, The PUSCH includes first information, which does not include the scheduling request information, and the method further includes: The second information is received on the fourth time-frequency resource, and the second information is used to request uplink authorization.

16. The method according to claim 10, characterized in that, The PUSCH includes first information, which does not include the scheduling request information, and the method further includes: A cache status report is received on the fifth time-frequency resource, the cache status report being used to indicate the amount of data cached by the terminal device.

17. The method according to any one of claims 11-16, characterized in that, The first information also includes uplink information in the PUCCH that is different from the scheduling request information.

18. A communication device, characterized in that, The communication device includes a module or unit for implementing the method of any one of claims 1-9; or, the communication device includes a module or unit for implementing the method of any one of claims 10-17.

19. A communication device, characterized in that, The communication device includes: a processor and an interface circuit, the interface circuit being used to communicate with a device other than the communication device, and the processor being used to execute instructions stored in a memory; when the instructions are executed by the processor, the communication device is caused to perform the method of any one of claims 1-9, or to perform the method of any one of claims 10-17.

20. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a computer, cause the method of any one of claims 1-9 to be performed, or cause the method of any one of claims 10-17 to be performed.

21. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a computer, cause the method of any one of claims 1-9 to be performed, or cause the method of any one of claims 10-17 to be performed.

22. A communication system, characterized in that, The communication system includes a network device and a terminal device; wherein the terminal device is used to perform the method of any one of claims 1-9, and the network device is used to perform the method of any one of claims 10-17.

Images