Communication methods and related apparatuses

Abstract

This application provides a communication method and related apparatus, relating to the field of communication technology. The method includes: transmitting first information, the first information being used to configure a first Channel Sounding Reference Signal (SRS) port, the first SRS port corresponding to a first Orthogonal Code (OCC), the first OCC having N time-domain units, where N is a positive integer; receiving a first SRS transmitted through the first SRS port; transmitting second information, the second information being used to instruct the OCC corresponding to the first SRS port to switch to a second OCC, the second OCC having M time-domain units, where M is a positive integer different from N; and receiving a second SRS transmitted through the first SRS port. In this application, the OCC of the SRS port can be flexibly adjusted based on actual conditions, ensuring SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods and related devices. Background Technology

[0002] A sounding reference signal (SRS) is an uplink reference signal sent by a terminal device to a network device. Upon receiving the SRS, the network device can obtain the uplink (UL) channel information from the terminal device to the network device. If the uplink and downlink channels are reciprocal (e.g., in a time-division duplex (TDD) system), the network device can also obtain the downlink channel information from the network device to the terminal device based on the SRS. After obtaining the channel information corresponding to the terminal device, the network device can perform data transmission resource scheduling, precoding, and other processing on the terminal device based on this information.

[0003] To improve SRS coverage, terminal devices can employ time-domain retransmission. For example, a terminal device can repeatedly transmit SRS over W time-domain symbols, and the network device can combine the SRS over W time-domain symbols, thereby effectively improving the SRS signal-to-noise ratio.

[0004] Currently, to improve the utilization of time-frequency resources, orthogonal cover codes (OCCs) can be used. Different terminal devices can be configured with mutually orthogonal OCCs, enabling multiple terminal devices to transmit SRS on the same time-frequency resources. However, the length of the OCC is related to interference and the power consumption of the terminal devices; therefore, how to manage OCC resources is a problem that needs to be considered. Summary of the Invention

[0005] This application discloses a communication method and related apparatus that can flexibly adjust the OCC of the SRS port based on actual conditions, ensuring SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

[0006] The first aspect discloses a communication method that can be applied to a network device, a module (e.g., a processor or chip) within the network device, or a logic module or software capable of implementing all or part of the functions of the network device. The following description, using an application to a network device as an example, includes: sending first information to configure a first channel sounding reference signal (SRS) port, the first SRS port corresponding to a first orthogonal code (OCC), the first OCC having N time-domain units, where N is a positive integer; receiving a first SRS transmitted through the first SRS port; sending second information to instruct the OCC corresponding to the first SRS port to switch to a second OCC, the second OCC having M time-domain units, where M is a positive integer different from N; and receiving a second SRS transmitted through the first SRS port.

[0007] In this embodiment, the network device can flexibly adjust the OCC used by the SRS port (e.g., switching the OCC used by the first SRS port from the first OCC to the second OCC), or flexibly adjust the OCC used by the terminal device based on the signal quality of the terminal device. This approach improves the flexibility of OCC resource scheduling. Furthermore, flexibly adjusting the OCC of the SRS port can ensure SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

[0008] In conjunction with the first aspect, in one possible implementation, third information is transmitted for configuring a second SRS port, which corresponds to a third OCC. The third OCC has N time-domain elements and is orthogonal to the first OCC. The non-OCC resources corresponding to the first SRS port and the second SRS port are the same. A third SRS transmitted through the second SRS port is received, where the third SRS has the same non-OCC resources as the first SRS. A fourth information is transmitted for instructing the OCC corresponding to the second SRS port to switch to a fourth OCC. The fourth OCC has M time-domain elements and is orthogonal to the second OCC. A fourth SRS transmitted through the second SRS port is received, where the fourth SRS has the same non-OCC resources as the second SRS, including time-frequency resources.

[0009] In this embodiment, the network device can also allocate non-OCC resources corresponding to the first SRS port to other SRS ports (such as the second SRS port), and can configure orthogonal OCCs for these SRS ports, thereby improving resource utilization. Furthermore, the first SRS port and the second SRS port can switch accordingly. When the first SRS port switches from the first OCC to the second OCC, the second SRS port can also switch from the third OCC to a fourth OCC orthogonal to the second OCC, thus ensuring the orthogonality between the first and second SRS ports.

[0010] In conjunction with the first aspect, in one possible implementation, the first OCC and the third OCC belong to a first OCC code group, which includes X OCCs, the number of time-domain units of the X OCCs is N, and the X OCCs are mutually orthogonal; the second OCC and the fourth OCC belong to a second OCC code group, which includes Y OCCs, the number of time-domain units of the Y OCCs is M, and the Y OCCs are mutually orthogonal; X and Y are integers greater than 2.

[0011] In this embodiment of the application, the network device can assign OCCs to the first SRS port and the second SRS port based on the first OCC code group and the second OCC code group, which can ensure the orthogonality between the first SRS port and the second SRS port.

[0012] In conjunction with the first aspect, in one possible implementation, the OCC corresponding to the paired port is an OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

[0013] In this embodiment, the paired ports can use OCCs from the same OCC code group, which ensures the orthogonality between the paired ports.

[0014] In conjunction with the first aspect, in one possible implementation, the first OCC code group and the second OCC code group are OCC code groups in a predefined table, which includes multiple OCC code groups. The OCCs in the same code group in the predefined table have the same number of time-domain units, and the OCCs in the same code group are mutually orthogonal.

[0015] In this embodiment of the application, multiple OCC code groups can be predefined for each time domain unit configuration, so that network devices can perform OCC allocation based on the predefined OCC code groups.

[0016] In conjunction with the first aspect, in one possible implementation, when N is 2 and M is 1, the first code group includes [+1+1] and [+1 -1], and the second code group includes [1 0] and [0 1]; when N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [00 1 0] and [0 0 0 1]; when N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1+1-1+1] and [+1-1-1+1-1+1+1 -1], the second code group includes [1 0 0 0 00 0 0], [0 1 0 0 0 0 0 0], [0 0 1 0 0 0 0 0 0][0 0 0 1 0 0 0 0], [0 0 0 0 1 0 0 0], [0 0 0 0 0 1 0 0], [0 0 0 0 0 0 1 0] and [0 0 0 0 0 0 0 1].

[0017] In conjunction with the first aspect, in one possible implementation, the first OCC and the third OCC belong to a first OCC code group, which includes X OCCs, the number of time-domain units of the X OCCs is N, the X OCCs are orthogonal to each other by a length of N, the first OCC code group includes multiple subcode groups, the fifth OCC in the first subcode group is composed of multiple L-length subcodes, the multiple L-length subcodes are orthogonal to the corresponding L-length portions of the OCCs in the remaining subcode groups, the multiple L-length subcodes include the second OCC and the fourth OCC, the first subcode group is any one of the multiple subcode groups, the first OCC and the third OCC belong to the first subcode group, and L is an integer greater than or equal to 2.

[0018] In this embodiment of the application, sub-code groups can be divided based on code groups. In this way, when the paired port corresponding to a certain sub-code group needs to switch OCC, the paired ports corresponding to other sub-code groups do not need to switch, thereby saving resource configuration overhead.

[0019] In conjunction with the first aspect, in one possible implementation, the paired ports corresponding to the first subcode group have an association relationship, which is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired port refers to the SRS port with the same corresponding non-OCC resources, and the non-OCC resources include time and frequency resources.

[0020] In this embodiment, the paired port corresponding to the first subcode group can simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC, which can ensure the orthogonality between the paired ports corresponding to the first subcode group.

[0021] In conjunction with the first aspect, in one possible implementation, the first OCC code group is an OCC code group in a predefined table.

[0022] In conjunction with the first aspect, in one possible implementation, when N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1], and [+1 -1-1+1], and the first code group includes subcode groups [+1+1+1+1], [+1+1 -1-1], and subcode groups [+1 -1+1 -1], [+1 -1-1+1]; when N is 8 and M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1 +1 -1-1], [+1 -1+1 -1-1 -1-1+1], [+1 -1+1 -1+1 -1+1 -1-1], [+1 -1+1 The first code group includes subcode groups [+1+1+1+1+1+1+1], [+1-1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1-1], [+1+1+1+1+1-1-1-1], [+1+1-1-1+1+1-1-1-1], [+1+1-1-1-1-1-1+1], [+1-1-1-1-1-1+1+1], [+1-1-1-1-1-1-1-1], [+1-1-1-1-1-1-1], and [+1-1-1-1+1-1-1+1], [+1-1-1-1-1-1+1-1], [+1-1-1-1-1-1+1], [+1-1-1-1-1+1- ...], [+1- -1]; When N is 8, M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], [+1 -1+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1-1+1], [+1 -1 -1+1+1 -1-1+1] and [+1 -1-1+1 -1+1+1 -1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], and subcode groups [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1+1 -1-1+1], [+1-1-1+1 -1+1+1 -1].

[0023] In conjunction with the first aspect, in one possible implementation, the number of time-domain units of the OCC corresponding to the SRS port is related to the signal quality information associated with the SRS port. Before sending the second information, the method further includes: determining the second OCC based on the signal quality information associated with the first SRS port.

[0024] In this embodiment, the network device can adjust the use of different lengths of OCC for the SRS port based on the signal quality information associated with the SRS port. This can ensure SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

[0025] In conjunction with the first aspect, in one possible implementation, the signal quality information defines multiple threshold intervals, with different threshold intervals corresponding to OCCs with different numbers of time-domain units; determining the second OCC based on the signal quality information associated with the first SRS port includes: determining a first threshold interval corresponding to the signal quality information associated with the first SRS port, the multiple threshold intervals including the first threshold interval, the first threshold interval corresponding to an OCC with a number of time-domain units of M; and determining the second OCC based on the first threshold interval.

[0026] In this embodiment, multiple threshold intervals and OCC lengths can be predefined. Then, the network device can quickly adjust the OCC used by the SRS port based on the signal quality information associated with the SRS port and the predefined multiple threshold intervals and OCC lengths.

[0027] In conjunction with the first aspect, in one possible implementation, the method further includes: in the event that the time-domain resources corresponding to the physical uplink shared channel (PUSCH) or the physical uplink control channel (PUCCH) collide with the time-domain resources corresponding to the first paired port, transmitting fifth information, the fifth information being used to instruct the abandonment of transmitting SRS through the SRS port in the first paired port for the time-domain resources in the collision, the first paired port including multiple SRS ports, the multiple SRS ports including the first SRS port, the multiple SRS ports corresponding to the same non-OCC resources, the non-OCC resources including time-frequency resources.

[0028] In this embodiment of the application, if the time domain resource corresponding to PUSCH or PUCCH collides with the time domain resource corresponding to the first paired port, the SRS port in the first paired port can be instructed to give up sending SRS on the colliding time domain resource, thus ensuring the successful transmission of PUSCH or PUCCH.

[0029] In conjunction with the first aspect, in one possible implementation, the method further includes: in the event that the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) partially collide with the time-domain resources corresponding to the first paired port, transmitting sixth information and seventh information, wherein the sixth information is used to instruct that the time-domain resources in the non-collision portion be transmitted via the first part of the SRS port in the first paired port, and the seventh information is used to instruct that the time-domain resources in the collision and the time-domain resources in the non-collision portion be abandoned and transmitted via the second part of the SRS port in the first paired port, wherein the first paired port includes a plurality of SRS ports, the plurality of SRS ports include the first SRS port, the plurality of SRS ports correspond to the same non-OCC resources, and the non-OCC resources include time-frequency resources.

[0030] In this embodiment, when the time-domain resources corresponding to PUSCH or PUCCH collide with the time-domain resources corresponding to the first paired port, the first part of the SRS port in the first paired port can be instructed to send SRS in the time-domain resources in the non-collision part, and the second part of the SRS port in the first paired port can be instructed to give up sending SRS in the collision time-domain resources and the non-collision time-domain resources. In this way, the successful transmission of PUSCH or PUCCH can be guaranteed, and the resource utilization rate can be improved.

[0031] The second aspect discloses a communication method, which can be applied to a terminal device, a module (e.g., a processor or chip) within the terminal device, or a logic module or software capable of implementing all or part of the terminal device's functions. The following description uses an application to a terminal device as an example. The communication method may include: receiving first information, which configures a first channel sounding reference signal (SRS) port, the first SRS port corresponding to a first orthogonal code (OCC), the first OCC having N time-domain units, where N is a positive integer; transmitting a first SRS through the first SRS port; receiving second information, which instructs the OCC corresponding to the first SRS port to switch to a second OCC, the second OCC having M time-domain units, where M is a positive integer different from N; and transmitting a second SRS through the first SRS port.

[0032] In this embodiment, based on relevant information (such as second information) issued by the network device, the terminal device can flexibly adjust the OCC used by the SRS port (e.g., switching the OCC used by the first SRS port from the first OCC to the second OCC). This approach improves the flexibility of OCC resource scheduling. Furthermore, flexibly adjusting the OCC of the SRS port can ensure SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

[0033] In conjunction with the second aspect, in one possible implementation, the first OCC belongs to a first OCC code group, which includes X OCCs, the number of time-domain units of the X OCCs is N, and the X OCCs are mutually orthogonal; the second OCC belongs to a second OCC code group, which includes Y OCCs, the number of time-domain units of the Y OCCs is M, and the Y OCCs are mutually orthogonal; X and Y are integers greater than 2.

[0034] In conjunction with the second aspect, in one possible implementation, the OCC corresponding to the paired port is the OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

[0035] In conjunction with the second aspect, in one possible implementation, the first OCC code group and the second OCC code group are OCC code groups in a predefined table. The predefined table includes multiple OCC code groups, and the OCCs in the same code group in the predefined table have the same number of time-domain units and are orthogonal to each other.

[0036] In this embodiment of the application, for each time domain unit configuration, a corresponding predefined table may be included. The network device can perform OCC allocation based on the predefined table, and the terminal device can look up the table based on the information sent by the network device.

[0037] In conjunction with the second aspect, in one possible implementation, when N is 2 and M is 1, the first code group includes [+1+1] and [+1 -1], and the second code group includes [1 0] and [0 1]; when N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [00 1 0] and [0 0 0 1]; when N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1+1-1+1] and [+1-1-1+1-1+1+1 -1], the second code group includes [1 0 0 0 00 0 0], [0 1 0 0 0 0 0 0], [0 0 1 0 0 0 0 0 0][0 0 0 1 0 0 0 0], [0 0 0 0 1 0 0 0], [0 0 0 0 0 1 0 0], [0 0 0 0 0 0 1 0] and [0 0 0 0 0 0 0 1].

[0038] In conjunction with the second aspect, in one possible implementation, the first OCC belongs to a first OCC code group, which includes X OCCs, the number of time-domain units of the X OCCs is N, the X OCCs are orthogonal to each other by a length of N, the first OCC code group includes multiple sub-code groups, the fifth OCC in the first sub-code group is composed of multiple L-length sub-codes, the multiple L-length sub-codes are orthogonal to the corresponding L-length portions of the OCCs in the remaining sub-code groups, the multiple L-length sub-codes include the second OCC, the first sub-code group is any one of the multiple sub-code groups, the first OCC belongs to the first sub-code group, and L is an integer greater than or equal to 2.

[0039] In conjunction with the second aspect, in one possible implementation, the paired ports corresponding to the first subcode group have an association relationship, which is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired ports refer to SRS ports with the same corresponding non-OCC resources, and the non-OCC resources include time and frequency resources.

[0040] In conjunction with the second aspect, in one possible implementation, the first OCC code group is an OCC code group in a predefined table.

[0041] In conjunction with the second aspect, in one possible implementation, when N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1], and [+1 -1-1+1]. This first code group includes sub-code groups [+1+1+1+1], [+1+1 -1-1], and [+1 -1+1 -1], and sub-code groups [+1 -1+1 -1], [+1 -1-1+1]. When N is 8 and M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1 -1-1 -1-1], [+1 -1+1 -1+1 -1+1 -1-1], [+1 -1+1 The first code group includes subcode groups [+1+1+1+1+1+1+1], [+1-1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1-1], [+1+1+1+1+1-1-1-1], [+1+1-1-1+1+1-1-1-1], [+1+1-1-1-1-1-1+1], [+1-1-1-1-1-1+1+1], [+1-1-1-1-1-1-1-1], [+1-1-1-1-1-1-1], and [+1-1-1-1+1-1-1+1], [+1-1-1-1-1-1+1-1], [+1-1-1-1-1-1+1], [+1-1-1-1-1+1- ...], [+1- -1]; When N is 8, M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], [+1 -1+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1-1+1], [+1 -1 -1+1+1 -1-1+1] and [+1 -1-1+1 -1+1+1 -1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], and subcode groups [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1+1 -1-1+1], [+1-1-1+1 -1+1+1 -1].

[0042] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving fifth information in the event that the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) collide with the time-domain resources corresponding to the first paired port, the fifth information being used to instruct the abandonment of transmitting SRS through the SRS port in the first paired port for the time-domain resources in the collision, the first paired port including multiple SRS ports, the multiple SRS ports including the first SRS port, the multiple SRS ports corresponding to the same non-OCC resources, the non-OCC resources including time-frequency resources.

[0043] In this embodiment, if the time-domain resource corresponding to PUSCH or PUCCH collides with the time-domain resource corresponding to the first pairing port, the terminal device can receive the fifth information and, based on the fifth information, abandon sending SRS through the SRS port in the first pairing port, thus ensuring the successful transmission of PUSCH or PUCCH.

[0044] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving sixth information when the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) partially collide with the time-domain resources corresponding to the first paired port, the sixth information being used to instruct the time-domain resources in the non-collision portion to transmit SRS through a first portion of the SRS port in the first paired port; or receiving seventh information, the seventh information being used to instruct the abandonment of transmitting SRS through a second portion of the SRS port in the first paired port for both the colliding and non-collision time-domain resources, the first paired port including a plurality of SRS ports, the plurality of SRS ports including the first SRS port, the plurality of SRS ports corresponding to the same non-OCC resources, the non-OCC resources including time-frequency resources.

[0045] In this embodiment, if the time-domain resources corresponding to PUSCH or PUCCH partially collide with the time-domain resources corresponding to the first paired port, some of the paired ports in the first paired port can send SRS in the time-domain resources in the non-collision part. In this way, the successful transmission of PUSCH or PUCCH can be guaranteed, and the resource utilization rate can be improved.

[0046] It should be noted that the technical solutions of the first aspect and the second aspect of this application correspond to each other, and the relevant beneficial effects can be referred to each other.

[0047] The third aspect discloses a communication device that has the functions of the first aspect described above. For example, the communication device includes a module or unit that performs the methods of the first aspect or any possible implementation of the first aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0048] For example, the communication device disclosed in the third aspect above may be a network device or a chip in a network device.

[0049] The fourth aspect discloses a communication device that has the functions of the second aspect described above. For example, the communication device includes a module or unit that performs the methods of the second aspect or any possible implementation of the second aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0050] For example, the communication device disclosed in the fourth aspect above may be a terminal device or a chip in a terminal device.

[0051] The fifth aspect discloses a communication system comprising a network device and a terminal device, the network device being configured to implement the methods provided in the first aspect and any possible embodiments thereof, and the terminal device being configured to implement the methods provided in the second aspect and any possible embodiments thereof.

[0052] The sixth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or transmit data; the processor invokes computer programs or computer instructions stored in a memory to implement the methods provided in the first aspect and any possible embodiments thereof, or to implement the methods provided in the second aspect and any possible embodiments thereof.

[0053] As one possible implementation, the communication device disclosed in the sixth aspect above may include one or more processors.

[0054] Optionally, the communication device disclosed in the sixth aspect above further includes one or more memories.

[0055] The seventh aspect discloses a computer-readable storage medium storing a computer program or computer instructions that, when executed, implement the methods provided in the first aspect and any possible embodiments thereof, or implement the methods provided in the second aspect and any possible embodiments thereof.

[0056] The eighth aspect discloses a chip including a processor for executing a program stored in a memory, which, when executed, causes the chip to perform the methods provided in the first aspect and any possible embodiments thereof, or to perform the methods provided in the second aspect and any possible embodiments thereof.

[0057] As one possible implementation, the memory is located outside the chip.

[0058] The ninth aspect discloses a computer program product comprising computer program code that, when executed, causes the methods provided in the first aspect and any possible implementation thereof to be performed, or causes the methods provided in the second aspect and any possible implementation thereof to be performed.

[0059] It should be understood that the implementation and beneficial effects of the above-mentioned aspects or any possible implementation methods of this application can be referred to each other. Attached Figure Description

[0060] The accompanying drawings are provided to more clearly illustrate the technical solutions of the embodiments of this application. The drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0061] Figure 1 This is a schematic diagram of a comb tooth disclosed in an embodiment of this application;

[0062] Figure 2 This is a schematic diagram of a frequency hopping method disclosed in an embodiment of this application;

[0063] Figure 3 This is a schematic diagram of a time-domain repetition disclosed in an embodiment of this application;

[0064] Figure 4 This is a schematic diagram of a time-domain repetition scenario disclosed in an embodiment of this application;

[0065] Figure 5 This is a schematic diagram of the architecture of a communication system disclosed in an embodiment of this application;

[0066] Figure 6 This is a flowchart illustrating a communication method disclosed in an embodiment of this application;

[0067] Figure 7 This is a schematic diagram of an OCC switching scenario disclosed in an embodiment of this application;

[0068] Figure 8This is a schematic diagram of OCC switching in a collision scenario disclosed in an embodiment of this application;

[0069] Figure 9 This is a schematic diagram of the structure of a communication device disclosed in an embodiment of this application;

[0070] Figure 10 This is a schematic diagram of the hardware structure of a communication device disclosed in an embodiment of this application. Detailed Implementation

[0071] This application discloses a communication method and related apparatus that, while ensuring SRS coverage, reduces the overall power consumption of terminal devices and the overall SRS interference intensity of the network. The technical solutions in this application will be clearly and completely described below with reference to the accompanying drawings.

[0072] To better understand the embodiments of this application, the relevant content, terms or nouns involved in this application will be briefly introduced below.

[0073] I. Antenna Port

[0074] Antenna ports, also simply referred to as ports, can include demodulation reference signal (DMRS) ports, SRS ports, etc., depending on the reference signal they carry. SRS ports can be used to carry SRS signals, and each SRS port can correspond to one SRS. Different ports can be multiplexed using code division, frequency division, time division, or space division. In one possible implementation, an SRS resource can include... There are several SRS ports, each of which can be configured with time-frequency code resources. It should be understood that, typically, different SRS ports will occupy different time-frequency code resources to reduce mutual interference. Each SRS port can correspond to either a physical antenna or a virtual antenna of the terminal device. For example, the port carrying the reference signal can also be called a reference signal port. In this embodiment, the terminal device can also be referred to as a user equipment (UE).

[0075] II. Cyclic shift (CS)

[0076] For different SRS ports, code division multiplexing can be used to transmit on the same time-frequency resources. Specifically, by multiplying the SRS sequence in the frequency domain by a phase offset factor, an equivalent time-domain response with a cyclic shift can be achieved. Given that the maximum channel delay is often finite, appropriate cyclic shift offsets can achieve code division orthogonality between different SRS ports. In detail, the cyclic shift is applied to the transmitted sequence; applying a cyclic shift to the transmitted sequence is equivalent to shifting the signal in the time delay domain. Different signals with different shifts can achieve a multiplexing effect.

[0077] III. Comb Teeth

[0078] For different SRS ports, transmission can be performed on different frequency domain subcarriers using frequency division multiplexing (FDM). The comb divides the frequency domain subcarriers into multiple groups, with a fixed frequency domain spacing between adjacent subcarriers within each group. The comb offset (CO) is a method of distinguishing different subcarriers in the frequency domain; different CO values ​​represent different subcarrier groups or subcarrier positions in the frequency domain. SRS resources can achieve frequency division multiplexing between SRS ports by assigning different CO values ​​to different SRS ports. See also... Figure 1 , Figure 1 This is a schematic diagram of a comb tooth disclosed in an embodiment of this application. Figure 1 One cell in the array represents one subcarrier, such as... Figure 1 As shown, the comb teeth are subcarriers extracted at equal intervals in the frequency domain, where the extraction interval is called the comb tooth degree K. TC This is usually pre-configured by network devices, and its value is 2, 4, 8, etc. When K... TC When K is 2, the frequency domain can be divided into two comb teeth for frequency division multiplexing of two sets of SRS ports. TC When K is 4, the frequency domain can be divided into 4 comb teeth, providing frequency division multiplexing for 4 groups of SRS ports, and so on. TC When the value is 8, the frequency domain can be divided into 8 comb teeth, which can be used for frequency division multiplexing of 8 groups of SRS ports. Figure 1 The marked grid can represent the subcarrier positions occupied by the comb teeth with a comb tooth offset value of 0 under different comb tooth degrees.

[0079] IV. SRS Measurement Bandwidth and Frequency Hopping Bandwidth

[0080] The SRS measurement bandwidth is the total bandwidth used by network devices to measure the channel via SRS. At each SRS transmission moment, the terminal device can transmit signals across the entire measurement bandwidth or only a portion of it. When transmitting signals only on a portion of the measurement bandwidth, this is called frequency hopping transmission of SRS, and the length of the portion transmitted each time is called the frequency hopping bandwidth. In the case of frequency hopping transmission, through multiple SRS transmission moments, the network device can obtain the channel corresponding to the entire SRS measurement bandwidth. For example... Figure 2 As shown, Figure 2 One cell in the SRS can represent a sub-band in the frequency domain, such as a resource block (RB). The measurement bandwidth of SRS is 16RB, and the frequency hopping bandwidth of SRS is 4RB. The measurement bandwidth can be completed by sending 4 SRS signals.

[0081] V. Orthogonal cover code (OCC)

[0082] As the frequency band used for communication increases, large-scale signal fading also increases, leading to a decrease in the signal-to-noise ratio (SNR) of SRS and limiting SRS coverage. Currently, to improve SRS coverage, terminal devices can use time-domain repetition transmission. For example, a terminal device can repeatedly transmit SRS over W time-domain symbols, and the network device can combine the SRS over W time-domain symbols, thereby increasing the equivalent SRS power by W times and the SRS SNR by W times. However, this method consumes W times the time-domain resources of a single time-domain symbol transmission. In other words, this method reduces the total system capacity to 1 / W of the original. For example, assuming the original system could serve A UEs, after expanding the time-domain resources for each UE by W times, the system can now only serve A / W UEs. W is an integer greater than or equal to 2. For example, as... Figure 3 As shown, taking 4-symbol repetition as an example, the SRS equivalent power can be increased by 4 times, the SRS signal-to-noise ratio can be increased by 4 times, and the resource overhead will also increase by 4 times. It should be understood that time-domain symbols can be orthogonal frequency division multiplexing (OFDM) symbols.

[0083] In this embodiment, to ensure that the number of UEs served does not decrease while time-domain retransmission is repeated, OCC can be introduced. Configuring a W-length OCC on a W-length OFDM symbol for different UEs ensures that the number of UEs served does not decrease based on the original resources, and all UEs can still enjoy the technical benefits of time-domain retransmission. It should be understood that the OCCs used by different UEs occupying the same time-frequency resources should be orthogonal. For example, taking 4-symbol retransmission as an example, orthogonal OCCs can be assigned to UE1 to UE4, such as [+1+1+1 -1], [+1+1 -1+1], [+1 -1+1+1], and [-1+1+1+1]. Thus, through orthogonal OCCs, UE1 to UE4 can transmit SRS on the same time-frequency resources. For example, OCC can also be called orthogonal overlay code, OCC code, etc., without limitation.

[0084] Furthermore, in practical systems, considering the overhead of the reference signal and the performance of channel estimation, the number of available orthogonal SRS resources is often limited. However, there are many cells in the network, and terminal devices in each cell transmit SRS for channel measurement. This can lead to the limited orthogonal SRS resources being reused by multiple cells. For example, under one SRS resource allocation strategy, terminal devices in each cell may be allocated orthogonal SRS resources, while different cells may be allocated non-orthogonal SRS resources, resulting in SRS interference between cells. SRS resources can include time-domain resources, frequency-domain resources, OCC resources, etc.

[0085] When introducing OCC (Optical Cross-Connection) for SRS (Synchronous Retransmission), the number of time-domain retransmissions varies depending on the OCC length allocated to the terminal device. Consequently, the intensity of SRS interference caused / suffered by the terminal device may also differ. Generally speaking, the longer the OCC length allocated to the terminal device, the greater the intensity of SRS interference caused / suffered by the terminal device. For example, such as... Figure 4 As shown, Figure 4 The left side shows the case where UE1 and UE2 transmit SRS in a single time domain symbol, and UE3 repeatedly transmits SRS in two time domain symbols. For example, UE1 transmits SRS in time domain symbol 1, UE2 transmits SRS in time domain symbol 2, and UE3 repeatedly transmits SRS in both time domain symbols 1 and 2. In addition, UE1, UE2, and UE3 occupy the same resources other than time domain resources. In this case, there will be interference between UE1 and UE3 and between UE2 and UE3. Assume that the overall interference of UE1 and UE2 on UE3 is P. Figure 4The right side shows the scenario where UE1 to UE3 repeatedly transmit SRS in two time domain symbols (time domain symbol 1 and time domain symbol 2), and UE1, UE2, and UE3 occupy the same resources except for OCC resources. UE1 uses OCC [+1+1], UE2 uses OCC [+1-1], and UE3 does not use OCC. In this case, there will be interference between UE1 and UE3, and between UE2 and UE3. The overall interference from UE1 and UE2 to UE3 is 2P. It can be seen that compared to UE1 and UE2 transmitting SRS in a single time domain symbol, the interference intensity to UE3 in the neighboring cell increases when UE1 and UE2 repeatedly transmit SRS in two time domain symbols.

[0086] Furthermore, the length of the OCC is also related to the power consumption of the terminal device. The longer the OCC length used by the terminal device, the greater the power consumption required for the terminal device to transmit SRS. For example, if UE1 and UE2 can meet the coverage requirements by transmitting SRS using a single time-domain symbol, then repeatedly transmitting SRS using multiple time-domain symbols may lead to a waste of UE power consumption and cause UE3 to suffer greater SRS interference.

[0087] As discussed above, the length of an OCC (Optical Channel Control) is related to its coverage area, terminal device power consumption, and SRS interference intensity. Furthermore, terminal devices are mobile. Therefore, efficient OCC resource management is a crucial consideration.

[0088] In this embodiment, the network device can allocate an OCC of corresponding length to the terminal device based on the actual situation of the terminal device (such as the distance between the terminal device and the network device, path loss, etc.). Furthermore, considering the mobility of the terminal device, the network device can also flexibly adjust the OCC used by the terminal device based on the real-time situation of the terminal device (such as a decrease in the distance between the terminal device and the network device, a decrease in path loss, etc.). For example, when the distance between the terminal device and the network device decreases, the terminal device can use a shorter OCC. In this approach, because the network device considers the actual situation of the terminal device when allocating the OCC, and can flexibly adjust the OCC used by the terminal device based on changes in the terminal device's situation, it can ensure SRS coverage while reducing the overall power consumption of the terminal device and the overall SRS interference intensity of the network.

[0089] To better understand the embodiments of this application, the system architecture of the embodiments of this application will be described below.

[0090] Please see Figure 5 , Figure 5 This is a schematic diagram of the architecture of a communication system disclosed in an embodiment of this application. Figure 5As shown, the communication system may include one or more terminal devices. Figure 5 The example shows one and one or more network devices. Figure 5 (An example is given below). Terminal devices and network devices can communicate with each other. Communication from a terminal device to a network device can be called uplink communication / uplink transmission, and communication from a network device to a terminal device can be called downlink communication / downlink transmission. The terminal devices and access network devices will be introduced separately below.

[0091] Terminal equipment, also known as a terminal, mobile station (MS), mobile terminal (MT), customer premise equipment (CPE), etc., is a device with wireless communication / wireless transceiver functions that can provide users with voice and / or data connectivity services. Terminal devices can include handheld terminals, laptops, RSUs (roadside units), subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistants (PDAs), tablets, tags, wireless modems, other processing devices connected to wireless modems, handheld devices, laptop computers, cordless phones or wireless local loop (WLL) stations, machine-type communication (MTC) terminals, wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving vehicles, and remote surgery. Wireless terminals in medical surgery, smart grids, transportation safety, smart cities, or smart homes; flying devices (such as intelligent robots, hot air balloons, drones, airplanes, etc.); or other devices capable of accessing networks are also included. The embodiments of this application do not limit the form of the terminal device. Terminal devices can be fixed or mobile, deployed on land (including indoors or outdoors, handheld, wearable, or vehicle-mounted), on water (such as ships), or in the air (e.g., on airplanes, balloons, and satellites).

[0092] The network devices involved in this application include access network devices. Access network devices are devices deployed in an access network that can wirelessly communicate with terminal devices, helping terminal devices achieve wireless access. Access network devices may include radio access network (RAN) devices, which may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, and balloon stations. In systems employing different radio access technologies, the names of the radio access network devices may differ. For example, in Long Term Evolution (LTE), there is the evolved NodeB (eNB or eNodeB), and in 5th Generation (5G) mobile communication systems, there is the next-generation NodeB (gNB) and ng-eNB (4G base stations accessing the 5G core network). Wireless access network equipment can also be wireless controllers in cloud radio access network (CRAN) scenarios, base station equipment in future networks, wireless access network equipment in future evolved public land mobile network (PLMN) networks, wearable devices, vehicle-mounted equipment, transmission and reception points (TRPs), radio network controllers (RNCs), home base stations (e.g., home evolved NodeB, or home Node B, HNB), base band units (BBUs), access points (APs) in wireless fidelity (WiFi) systems, etc.

[0093] In some deployments, such as open RAN (O-RAN) or ORAN systems, access network equipment (e.g., gNB) may include centralized units (CUs) and distributed units (DUs). Access network equipment may also include radio units (RUs). Access network equipment can communicate with the core network (CN) via a backhaul link and with the user equipment (UE) via an air interface (e.g., Uu interface). For example, the baseband unit (BBU) in the access network equipment can communicate with the core network via a backhaul link, and the radio unit can communicate with the UE via an air interface. Furthermore, the BBU can communicate with the RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU may include at least one centralized unit (CU) and at least one distributed unit (DU), and the CU and DU can communicate via a midhaul link. The CU can implement some of the functions of the access network equipment, the DU can implement some of the functions of the access network equipment, and the CU can be used to control the operation of one or more DUs. For example, the CU can implement the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, as well as the service data adaptation protocol (SDAP) layer. The DU can implement the functions of the radio link control (RLC) and media access control (MAC) layers, and can also implement some or all physical layer (PHY) layer functions (such as the higher physical layer, or higher PHY layer). The RU can be used to implement some physical layer functions (such as the lower physical layer, or lower PHY layer) and radio frequency functions. For detailed descriptions of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP).

[0094] In some examples, the CU can be split into the CU-control plane (CU-CP) and the CU-user plane (CU-UP). It should be understood that the above CU and DU configurations are merely examples, and the functions of the CU and DU can be configured as needed. For example, the CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. In the embodiments of this application, the CU can also be called O-CU (O-RANCU), the CU-CP can also be called O-CU-CP, and the CU-UP can also be called O-CU-UP.

[0095] The O-RAN system may also include a RAN intelligent controller (RIC). RICs can be divided into near-real-time RICs (near-RT RICs / nRT RICs) and non-real-time RICs (non-RT RICs / NRT RICs). Near-real-time RICs refer to the near-real-time portion, primarily used for near-real-time intelligent management of the RAN. Near-real-time RICs can achieve near-real-time control and optimization of O-RAN modules and resources through data collection and related operations. Non-real-time RICs refer to the non-real-time portion, primarily used for non-real-time intelligent management of RAN functions. Non-real-time RICs can implement AI / machine learning (ML) workflows, including model training and model updates. More detailed information about open radio access networks (such as interfaces) can be found in the relevant standards and will not be elaborated upon here.

[0096] It is understood that in some possible implementations, the access network device can be a CU, DU, CU-CP, CU-UP, RU, etc., or can be a device including at least one of CU, DU, CU-CP, CU-UP, RU, etc.

[0097] In some possible implementations, network devices can be divided into scheduling devices and transmitting devices. The scheduling device can be used to configure / schedule uplink and downlink resources, while the transmitting device can be used to transmit downlink signals and receive uplink signals based on the scheduled resources. For example, the scheduling device may include, but is not limited to, eNBs, gNBs, etc., and the transmitting device may include, but is not limited to, TRPs, remote radio heads (RRHs), etc.

[0098] It should be understood that Figure 5 The architecture shown is merely an illustrative example. Figure 5 The architecture shown may also include other devices / network elements, but this application embodiment does not limit this.

[0099] It is understood that the aforementioned network devices, terminal devices, etc., can be implemented in the form of hardware, computer software, or a combination of hardware and computer software. For example, the aforementioned network devices, terminal devices, etc., can be implemented by a single device, or by multiple devices working together, or by a functional module within a single device. This application embodiment does not specifically limit this.

[0100] It should be understood that the technical solutions provided in the embodiments of this application can be applied to various communication systems, such as fifth-generation (5G) communication systems, transitional systems between 5G and sixth-generation (6G) communication systems (which can also be called 5.5G communication systems), networks integrating multiple systems, multi-band communication systems, future communication systems, frequency division duplex (FDD) systems, time division duplex (TDD) systems, etc.

[0101] The technical solutions provided in this application are applicable to low-frequency scenarios (sub 6G), high-frequency scenarios (above 6G), homogeneous network scenarios, heterogeneous network scenarios, single-TRP scenarios, and multi-TRP scenarios.

[0102] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0103] It should be noted that the system architecture, network architecture, and business scenarios (or application 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 communication 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.

[0104] To better understand the embodiments of this application, the relevant OCC resources of the embodiments of this application will be described by way of example below.

[0105] The embodiments of this application mainly involve repeated transmission in the time domain. Therefore, the OCC in the embodiments of this application can be a time division orthogonal cover code (TD-OCC).

[0106] In some possible implementations, multiple OCC lengths can be predefined, such as through a protocol. When a network device assigns an OCC to a terminal device, it can do so based on the predefined OCCs, and subsequent adjustments can be made flexibly based on these predefined OCCs.

[0107] It should be noted that in this embodiment, the length of the OCC can be the number of non-zero elements in the OCC. For example, the length of OCC[+1+1] is 2, and the length of OCC[+1 0] is 1. It should also be noted that each element in the OCC can correspond to a time-domain unit in turn, and the time-domain unit corresponding to the zero element in the OCC is silent, which is equivalent to the terminal device not sending SRS to the time-domain unit corresponding to the zero element in the OCC. For example, two elements in OCC[+1+1] can correspond to a time-domain unit in turn, and two elements in OCC[+1 0] can correspond to a time-domain unit in turn, and the terminal device does not send SRS to the time-domain unit corresponding to the second element (the zero element). In this embodiment, the time-domain unit can be a time-domain symbol, such as an OFDM symbol. The length of the OCC can also be referred to as the number of time-domain units in the OCC.

[0108] In this embodiment, the SRS time-domain unit configuration can include various cases, such as 2, 4, 8, 16, etc. The SRS time-domain unit configuration refers to the number of time-domain units occupied by the SRS, which is its length in the time domain. Since one time-domain unit corresponds to one element in the OCC, the SRS time-domain unit configuration should correspond to the number of elements in the OCC. For example, when the SRS time-domain unit configuration is 2, the corresponding number of elements in the OCC is also 2; when the SRS time-domain unit configuration is 4, the corresponding number of elements in the OCC is also 4. Based on the relationship between the SRS time-domain unit configuration and the number of elements in the OCC, in some possible implementations, multiple OCC lengths can be predefined for each specific SRS time-domain unit configuration. It should be understood that the length of the OCC is less than or equal to the number of elements in the OCC.

[0109] The following examples, using time-domain unit configurations of 2, 4, and 8, illustrate several possible predefined tables.

[0110] When the SRS time-domain unit is configured to be 2, the OCC consists of two elements, in which case the length of the OCC is less than or equal to 2. That is, an OCC with a length less than or equal to 4 can be defined, such as an OCC with a length of 1 and an OCC with a length of 2. For example, one possible predefined table is shown in Table 1 below:

[0111] Table 1

[0112] TD-OCC Index <![CDATA[W t (0)]]> <![CDATA[W t (1)]]> 0 +1 +1 1 +1 -1 2 +1 0 3 0 +1

[0113] In Table 1 above, the length of the OCC corresponding to index 0 and index 1 is 2, and the OCC corresponding to index 0 is orthogonal to the OCC corresponding to index 1. The length of the OCC corresponding to index 2 and index 3 is 1, the OCC corresponding to index 2 is [+1 0], and the OCC corresponding to index 3 is [0+1]. Assuming that the time domain units configured for transmitting SRS are time domain unit 1 and time domain unit 2, if the OCC corresponding to index 2 is used, then only time domain unit 1 will transmit, and time domain unit 2 will not transmit. If the OCC corresponding to index 3 is used, then only time domain unit 2 will transmit, and time domain unit 1 will not transmit. In this way, the SRS transmitted based on the OCC corresponding to index 2 and the SRS transmitted based on the OCC corresponding to index 3 can be distinguished by time domain resources, or it can be understood that OCC [+1 0] and OCC [0+1] are orthogonal in the time domain. In this embodiment, "+1" in OCC can also be abbreviated to "1".

[0114] In some possible implementations, multiple types of UE or SRS ports can be defined, with different types of UE or SRS ports using OCCs of different lengths, as shown in Table 1. For example, taking a first type of UE or SRS port and a second type of UE or SRS port as examples, it can be specified that the first type of UE or SRS port uses OCCs corresponding to indices 0 and 1, while the second type of UE or SRS port uses OCCs corresponding to indices 2 and 3. The definition method for the UE or SRS port type is not limited; for example, it can be defined based on signal quality, the distance between the terminal device and the network device, etc. It is understood that each type of UE or SRS port can correspond to specific conditions, meaning that different conditions can use OCCs of different lengths (as shown in Table 1). For example, far-point UEs and near-point UEs can be defined. A far-point UE is a UE whose distance from the network device is greater than a first threshold, and a near-point UE is a UE whose distance from the network device is less than or equal to the first threshold. Far-point UEs use OCCs corresponding to indices 0 and 1, while near-point UEs use OCCs corresponding to indices 2 and 3.

[0115] It is understood that for SRS ports with identical non-OCC resources, orthogonal OCCs should be used. For example, assuming that SRS port 1 and SRS port 2 have the same non-OCC resources, SRS port 1 and SRS port 2 can use the OCCs corresponding to index 0 and index 1 respectively, or they can use the OCCs corresponding to index 2 and index 3 respectively. In this embodiment, SRS ports with identical non-OCC resources can be called paired ports. For example, SRS port 1 and SRS port 2 mentioned above can be paired ports. Non-OCC resources are resources other than OCC resources, including but not limited to time domain resources, frequency domain resources, spatial domain resources, cyclic shift, etc. In this embodiment, paired ports can also be called SRS paired ports, etc. In some possible implementations, for two SRS ports, if the resource configuration information issued by the network device is the same except for OCC, then these two SRS ports can be considered paired ports. In addition to OCC, the resource configuration information issued by network devices may also include configurations such as the number of time-domain units (e.g., the number of OFDM symbols), comb offset, comb degree, frequency hopping bandwidth, and measurement bandwidth. As one possible implementation, non-OCC resources may include other configurations besides OCC in the resource configuration information issued by network devices, such as one or more of the following: the number of time-domain units (e.g., the number of OFDM symbols), comb offset, comb degree, frequency hopping bandwidth, and measurement bandwidth.

[0116] In some possible implementations, when the OCC corresponding to an SRS port switches from an OCC of a first length to an OCC of a second length, the paired port corresponding to that SRS port can also switch accordingly, that is, switch from an OCC of the first length to an OCC of the second length, where the first length (e.g., 2) and the second length (e.g., 1) are different. For example, suppose SRS port 1 switches from the OCC corresponding to index 0 to the OCC corresponding to index 2. In this case, the paired port (SRS port 2) corresponding to SRS port 1 can switch from the OCC corresponding to index 1 to the OCC corresponding to index 3.

[0117] In this embodiment, under a certain time-domain unit configuration, OCCs of the same length and mutually orthogonal can form an OCC code group. For example, in Table 1 above, the OCCs corresponding to index 0 and index 1 can form an OCC code group, and the OCCs corresponding to index 2 and index 3 can form an OCC code group. Paired ports can use different OCCs from the same OCC code group. In this embodiment, the OCC code group can also be simply referred to as a code group.

[0118] When the SRS time-domain unit is configured to 4, the OCC includes 4 elements. In this case, the length of the OCC is less than or equal to 4. That is, OCCs with a length less than or equal to 4 can be defined, such as OCCs with a length of 1, OCCs with a length of 2, OCCs with a length of 4, etc. For example, a possible predefined table is shown in Table 2 below:

[0119] Table 2

[0120]

[0121]

[0122] In Table 2 above, the OCCs corresponding to indices 0 to 3 can form an OCC code group with a length of 4. The OCCs corresponding to indices 4 to 7 can form an OCC code group with a length of 2. The OCCs corresponding to indices 8 to 11 can form an OCC code group with a length of 1. Specifically, the OCCs corresponding to indices 4 and 5 are orthogonal in the first two elements, and the OCCs corresponding to indices 6 and 7 are orthogonal in the last two elements. Furthermore, the OCCs corresponding to indices 4 and 6, as well as those corresponding to indices 7, are orthogonal in the time domain, and the OCCs corresponding to indices 5 and 6, as well as those corresponding to indices 7, are also orthogonal in the time domain. In other words, if the paired port uses the OCCs corresponding to indices 4, 5, 6, and 7 to transmit SRS, the SRS transmitted based on the OCCs corresponding to indices 4 and 5 and the SRS transmitted based on the OCCs corresponding to indices 6 and 7 can be distinguished by time domain resources. SRS sent based on OCCs corresponding to indices 4 and 5, and SRS sent based on OCCs corresponding to indices 6 and 7, can be distinguished by the orthogonality of the non-zero element parts in the OCC.

[0123] Furthermore, the OCCs corresponding to indices 4 and 10, and 11, are orthogonal in the time domain. Similarly, the OCCs corresponding to indices 5, 10, and 11 are also orthogonal in the time domain. Therefore, the OCCs corresponding to indices 4, 5, 10, and 11 can be configured for use by the four paired ports. Likewise, the OCCs corresponding to indices 6, 8, and 9 are orthogonal in the time domain. The OCCs corresponding to indices 7, 8, and 9 are also orthogonal in the time domain. Therefore, the OCCs corresponding to indices 6, 7, 8, and 9 can be configured for use by the four paired ports. The OCCs corresponding to indices 5, 0, and 1 are partially orthogonal in the time domain, meaning the last two elements of the four OCC elements are orthogonal in the time domain. Additionally, the OCCs corresponding to indices 5, 0, and 1 are orthogonal in the non-zero element portion, meaning the first two elements of the four OCC elements are orthogonal. Similarly, index 7 is partially orthogonal in the time domain to the OCCs corresponding to index 0 and index 1, meaning the first two elements of the four elements of the OCC are orthogonal in the time domain. Furthermore, index 7 is orthogonal to the non-zero elements of the OCCs corresponding to index 0 and index 1, meaning the last two elements of the four elements of the OCC are orthogonal. Also, index 5 is orthogonal to the OCCs corresponding to index 7 in the time domain. Therefore, the OCCs corresponding to indices 0, 1, 5, and 7 can be configured for use by the four paired ports. Likewise, index 4 is partially orthogonal in the time domain to the OCCs corresponding to index 2 and index 3, and is orthogonal in the non-zero elements. Index 6 is partially orthogonal in the time domain to the OCCs corresponding to index 2 and index 3, and is orthogonal in the non-zero elements. Furthermore, index 4 is orthogonal to the OCCs corresponding to index 6 in the time domain. Therefore, the OCCs corresponding to indices 2, 3, 4, and 6 can be configured for use by the four paired ports.

[0124] As described above, in some possible implementations, under a certain SRS time-domain unit configuration, paired ports can use OCCs from different OCC code groups; that is, the OCCs used by paired ports can come from multiple OCC code groups. Specifically, for any two paired ports using OCCs from different code groups, the OCCs used by these two paired ports need to maintain time-domain orthogonality (e.g., OCCs corresponding to indices 4 and 10, or OCCs corresponding to indices 5 and 10, etc.), or they need to maintain partial time-domain orthogonality and partial orthogonality of non-zero elements (e.g., OCCs corresponding to indices 0 and 5, or OCCs corresponding to indices 1 and 5, etc.). Only in this way can the orthogonality of the paired ports be guaranteed.

[0125] In some possible implementations, multiple types of UE or SRS ports can be defined, with different types of UE or SRS ports using different lengths of OCC as shown in Table 2.

[0126] It is understandable that when an SRS port switches its OCC, the OCC corresponding to that SRS port may not be orthogonal to the OCCs of some or all of its paired ports. Therefore, to ensure orthogonality, some or all of the paired ports corresponding to that SRS port may also switch. It should be understood that switching in this embodiment can be understood as switching the OCC or updating the OCC, and switching / updating the OCC can be understood as switching to an OCC of different lengths. For example, assuming SRS ports 1 to 4 are paired ports, using OCCs corresponding to indices 4 to 7 respectively, if SRS port 1 switches from the OCC corresponding to index 4 to the OCC corresponding to index 0, in this case, SRS port 3 can switch from the OCC corresponding to index 6 to the OCC corresponding to index 1, while SRS ports 2 and 4 do not need to switch.

[0127] For example, in some possible implementations, when the OCC corresponding to an SRS port switches from an OCC of a first length to an OCC of a second length, some of the paired ports corresponding to that SRS port can switch accordingly, that is, switch from an OCC of the first length to an OCC of the second length. Some of the paired ports corresponding to that SRS port may not switch, even though the first length (e.g., 4) and the second length (e.g., 2) are different. For instance, assuming SRS ports 1 to 4 are paired ports, using OCCs corresponding to indices 0 to 3 respectively, if SRS port 1 switches from the OCC corresponding to index 0 to the OCC corresponding to index 4, then some of the paired ports corresponding to SRS port 1 (SRS port 2) can switch from the OCC corresponding to index 1 to the OCC corresponding to index 6, while some of the paired ports corresponding to SRS port 1 (SRS port 3 and SRS port 4) may not switch.

[0128] When the SRS time-domain unit is configured to 8, the OCC includes 8 elements. In this case, the length of the OCC is less than or equal to 8. That is, OCCs with a length less than or equal to 8 can be defined, such as OCCs with a length of 1, 2, 4, 8, etc. For example, a possible predefined table is shown in Table 3 below:

[0129] Table 3

[0130] TD-OCC Index <![CDATA[W t (0)]]> <![CDATA[W t (1)]]> <![CDATA[W t (2)]]> <![CDATA[W t (3)]]> <![CDATA[W t (4)]]> <![CDATA[W t (5)]]> <![CDATA[W t (6)]]> <![CDATA[W t (7)]]> 0 +1 +1 +1 +1 +1 +1 +1 +1 1 +1 +1 +1 +1 -1 -1 -1 -1 2 +1 +1 -1 -1 +1 +1 -1 -1 3 +1 +1 -1 -1 -1 -1 +1 +1 4 +1 -1 +1 -1 +1 -1 +1 -1 5 +1 -1 +1 -1 -1 +1 -1 +1 6 +1 -1 -1 +1 +1 -1 -1 +1 7 +1 -1 -1 +1 -1 +1 +1 -1 8 +1 +1 +1 +1 0 0 0 0 9 +1 +1 -1 -1 0 0 0 0 10 +1 -1 +1 -1 0 0 0 0 11 +1 -1 -1 +1 0 0 0 0 12 0 0 0 0 +1 +1 +1 +1 13 0 0 0 0 +1 +1 -1 -1 14 0 0 0 0 +1 -1 +1 -1 15 0 0 0 0 +1 -1 -1 +1 16 +1 +1 0 0 0 0 0 0 17 +1 -1 0 0 0 0 0 0 18 0 0 +1 +1 0 0 0 0 19 0 0 +1 -1 0 0 0 0 20 0 0 0 0 +1 +1 0 0 21 0 0 0 0 +1 -1 0 0 22 0 0 0 0 0 0 +1 +1 23 0 0 0 0 0 0 +1 -1 24 1 0 0 0 0 0 0 0 25 0 1 0 0 0 0 0 0 26 0 0 1 0 0 0 0 0 27 0 0 0 1 0 0 0 0 28 0 0 0 0 1 0 0 0 29 0 0 0 0 0 1 0 0 30 0 0 0 0 0 0 1 0 31 0 0 0 0 0 0 0 1

[0131] In Table 3 above, the OCCs corresponding to indices 0 to 7 can form an OCC code group with a length of 8. The OCCs corresponding to indices 8 to 15 can form an OCC code group with a length of 4. The OCCs corresponding to indices 16 to 23 can form an OCC code group with a length of 2. The OCCs corresponding to indices 24 to 31 can form an OCC code group with a length of 1.

[0132] Regarding Table 3 above, paired ports can use different OCCs within the same code group or OCCs from different code groups, but must meet the corresponding conditions, which can be referred to the above description. For example, the OCCs corresponding to indices 0, 1, 2, 3, 10, 11, 14, and 15 can be configured for use by 8 paired ports respectively; the OCCs corresponding to indices 4, 5, 6, 7, 8, 9, 12, and 13 can be configured for use by 8 paired ports respectively; the OCCs corresponding to indices 8, 9, 10, 11, 20, 21, 22, and 23 can be configured for use by 8 paired ports respectively; the OCCs corresponding to indices 12, 13, 14, 15, 16, 17, 18, and 19 can be configured for use by 8 paired ports respectively; the OCCs corresponding to indices 8, 9, 10, 11, 20, 21, 30, and 31 can be configured for use by 8 paired ports respectively, and so on.

[0133] In some possible implementations, multiple types of UE or SRS ports can be defined, with different types of UE or SRS ports using different lengths of OCC as shown in Table 3.

[0134] It is understood that the OCC example in the table above uses Walsh codes. In other possible implementations of this application, other types of OCC, such as Discrete Fourier Transform (DFT) codes, can also be used. For example, when the SRS time-domain unit is configured to 4, the predefined table corresponding to the DFT codes can be shown in Table 4 below:

[0135] Table 4

[0136] TD-OCC Index <![CDATA[W t (0)]]> <![CDATA[W t (1)]]> <![CDATA[W t (2)]]> <![CDATA[W t (3)]]> 0 1 1 1 1 1 1 -i -1 i 2 1 -1 1 -1 3 1 i -1 -i 4 1 1 0 0 5 1 -1 0 0 6 0 0 1 1 7 0 0 1 -1 8 1 0 0 0 9 0 1 0 0 10 0 0 1 0 11 0 0 0 1

[0137] As another example, when the SRS time-domain unit is configured to 8, the predefined table corresponding to the DFT code can be shown in Table 5 below:

[0138] Table 5

[0139]

[0140]

[0141] It should be understood that the tables 1 to 5 above are merely illustrative and do not constitute a limitation. In other possible embodiments of this application, tables 1 to 5 may include more or fewer OCCs. For example, table 2 above may not include OCCs of length 1 or OCCs of length 2. As another example, table 3 above may not include OCCs of length 1, OCCs of length 2, or OCCs of length 4. It should also be understood that under a certain SRS time-domain unit configuration, for a given OCC length, the OCCs in the OCC code group of that OCC length are not unique and may include multiple possible OCC combinations, any one of which can be used. For example, in table 1 above, the OCC code group of length 2 includes [+1+1] and [+1 -1], but the OCC code group of length 2 can also be other combinations, such as [-1 -1] and [+1 -1], [+1+1] and [-1+1], etc.

[0142] It should be noted that the above examples only use time-domain unit configurations of 2, 4, and 8 as examples. However, it should be understood that there can also be corresponding predefined tables for other SRS time-domain unit configurations (such as 12, 16, etc.). Among them, the predefined table corresponding to a certain SRS time-domain unit configuration can include two, three, four, or more OCC code groups.

[0143] In the examples above, for a specific time-domain unit configuration, the corresponding predefined table can include multiple OCC code groups, that is, OCCs of various lengths. However, in some other possible embodiments of this application, for a specific time-domain unit configuration, the corresponding predefined table can include one OCC code group, where the length of the OCCs in the OCC code group is the same as that time-domain unit configuration. That is, when the time-domain unit configuration is T, the length of the OCCs in the OCC code group is also T, where T is greater than or equal to 2. In this case, to facilitate flexible adjustment of the OCCs used by the terminal device, corresponding rules can be defined so that OCCs of other lengths (such as T / 2) can be configured based on the OCC code group.

[0144] For example, when the SRS time-domain unit is configured to be 2, the OCC includes two elements, in which case the length of the OCC is less than or equal to 2. Therefore, an OCC of length 2 can be defined in a predefined table. For example, one possible predefined table is shown in Table 6 below:

[0145] Table 6

[0146] TD-OCC Index <![CDATA[W t (0)]]> <![CDATA[W t (1)]]> 0 +1 +1 1 +1 -1

[0147] Table 6 above only includes OCCs of length 2. To support flexible switching of OCCs of different lengths (such as 1), the OCC [+1+1] corresponding to index 0 can be divided into two parts, that is, into two subcodes of length 1, corresponding to W respectively. t (0) and W t (1) Furthermore, these two 1-length subcodes are orthogonal in the time domain. This is equivalent to considering these two 1-length subcodes as [+1 0] and [0+1]. Further, to facilitate switching, the association relationship between OCCs of different lengths, such as 1-length and 2-length, can be specified. For example, the OCC corresponding to index 0 and the W of the OCC corresponding to index 0 can be specified. t (0) There is an association relationship, the OCC corresponding to index 1 and the W of the OCC corresponding to index 0. t (1) They have an association relationship. For example, assuming SRS port 1 and SRS port 2 are paired ports, SRS port 1 and SRS port 2 can use the OCCs corresponding to index 0 and index 1 respectively. When the network device indicates a switch to a 1-length OCC, SRS port 1 can use the W of the OCC corresponding to index 0. t (0) part, which is equivalent to using OCC[+1 0], SRS port 2 can use the W of the OCC corresponding to index 0. t (1) This is equivalent to using OCC[0+1]. Similarly, when the network device indicator switches back to a 2-length OCC, SRS port 1 can use the OCC corresponding to index 0, and SRS port 2 can use the OCC corresponding to index 1. It should be understood that the above division method is only an illustrative example and does not constitute a limitation.

[0148] As another example, when the SRS time-domain unit is configured to be 4, the OCC includes 4 elements. In this case, the length of the OCC is less than or equal to 4. Therefore, an OCC of length 4 can be defined in a predefined table. An example, a possible predefined table is shown in Table 7 below:

[0149] Table 7

[0150] TD-OCC Index <![CDATA[W t (0)]]> <![CDATA[W t (1)]]> <![CDATA[W t (2)]]> <![CDATA[W t (3)]]> 0 +1 +1 +1 +1 1 +1 +1 -1 -1 2 +1 -1 +1 -1 3 +1 -1 -1 +1

[0151] Table 7 above only includes OCCs of length 4. These 4 OCCs are orthogonal, meaning they are 4-length orthogonal. To support switching between OCCs of length 1, the OCC [+1+1+1+1] corresponding to index 0 can be divided into four parts, that is, into four subcodes of length 1, corresponding to W respectively. t (0), W t (1) W t (2) and W t(3) Furthermore, these four 1-length subcodes are orthogonal in the time domain. This is equivalent to considering these four 1-length subcodes as [+1 0 0 0], [0+1 0 0], [0 0+1 0], and [0 0 0+1]. Similarly, to support switching OCCs of length 2, the OCC [+1+1+1+1] corresponding to index 0 can be divided into two parts, that is, into two 2-length subcodes, corresponding to W respectively. t (0) and W t (1), and W t (2) and W t (3) Furthermore, these two 2-length subcodes are orthogonal in the time domain. This is equivalent to considering these two 2-length subcodes as [+1+1 0 0] and [0 0+1+1]. Similarly, the OCC [+1 -1+1 -1] corresponding to index 2 can also be divided into two parts, that is, into two 2-length subcodes, which are also orthogonal in the time domain. This is equivalent to considering these two 2-length subcodes as [+1 -1 0 0] and [0 0+1-1]. In addition, the W of OCC [+1+1+1+1]... t (0) and W t (1) Part of W with OCC[+1 -1+1 -1] t (0) and W t (1) Partially orthogonal to two lengths, W of OCC[+1+1+1+1] t (2) and W t (3) Part of W with OCC[+1 -1+1 -1] t (2) and W t (3) Partial 2-length orthogonal. That is to say, these four 2-length subcodes can be assigned to the four paired ports respectively.

[0152] Furthermore, to facilitate switching, the association relationships between OCCs of different lengths, such as 1, 2, and 4, can be defined. For example, the W of the OCC corresponding to index 0 can be specified. t (0), and W of the OCC corresponding to index 0 t (0) and W t (1) They have an association relationship, with the OCC corresponding to index 1 and the W of the OCC corresponding to index 0. t (1), and the W of the OCC corresponding to index 0 t (2) and W t (3) They have an association relationship, with the OCC corresponding to index 2 and the W of the OCC corresponding to index 0. t (2), and the W of the OCC corresponding to index 2 t (0) and W t(1) They have an association relationship, with the OCC corresponding to index 3 and the W of the OCC corresponding to index 0. t (3), and the W of the OCC corresponding to index 2 t (2) and W t (3) They have an association relationship. For example, assuming SRS ports 1 to 4 are paired ports, SRS ports 1 to 4 can use the OCCs corresponding to indices 0 to 3 respectively. When the network device indicates a switch to a 1-length OCC, SRS port 1 can use the W of the OCC corresponding to index 0. t (0) part, which is equivalent to using OCC[+1 0 0 0], SRS port 2 can use the W of the OCC corresponding to index 0. t (1) Part, which is equivalent to using OCC[0+1 0 0], SRS port 3 can use the W of the OCC corresponding to index 0. t (2) Part, which is equivalent to using OCC[0 0+1 0], SRS port 4 can use the W of the OCC corresponding to index 0. t (3) This is equivalent to using OCC[0 0 0+1]. Similarly, when the network device indicates a switch to a 2-length OCC, SRS port 1 can use the W of the OCC corresponding to index 0. t (0) and W t (1) Part, which is equivalent to using OCC[+1+1 0 0], SRS port 2 can use the W of the OCC corresponding to index 0. t (2) and W t (3) Part, which is equivalent to using OCC[0 0+1+1], SRS port 3 can use the W of the OCC corresponding to index 2. t (0) and W t (1) Part, which is equivalent to using OCC[+1 -1 0 0], SRS port 4 can use the W of the OCC corresponding to index 2. t (2) and W t (3) This is equivalent to using OCC[0 0+1 -1]. It should be understood that the above division method is only an illustrative example and does not constitute a limitation.

[0153] In this embodiment, sub-code groups can also be divided based on OCC code groups. For a T-length OCC in a predefined table, when dividing the T-length OCC into Z P-length sub-codes, if the Z P-length sub-codes are orthogonal to the corresponding P-length portion of a remaining OCC in the predefined table (i.e., the Z P-length sub-codes are orthogonal to the corresponding Z P-length portions (P-length sub-codes) of a remaining OCC), then these two OCC codes can belong to the same sub-code group; otherwise, they do not belong to the same sub-code group. P is an integer greater than or equal to 2 and less than or equal to T / 2, and T = Z * P. For example, assuming T is 4 and P is 2, for the four OCCs in Table 7 above, the OCCs corresponding to index 0 and index 1 can belong to the same sub-code group, and the OCCs corresponding to index 2 and index 3 can belong to the same sub-code group.

[0154] Optionally, based on the subcode group division, when specifying the association relationship between OCCs of different lengths, for cases where the length is greater than 1, the association relationship between OCCs of different lengths can be specified based on the subcode group. In one possible implementation, a T-length OCC in a subcode group can be divided into Z P-length subcodes, and multiple T-length OCCs in the subcode group can be associated with one of the Z P-length subcodes respectively. For example, taking Table 7 as an example, for the 2-length OCCs associated with the OCC corresponding to index 0 and the OCC corresponding to index 1, it is possible to choose to divide the OCC corresponding to index 0 or the OCC corresponding to index 1 into two 2-length subcodes, and then the OCC corresponding to index 0 and the OCC corresponding to index 1 can be associated with one each. For example, the OCC corresponding to index 0 can be associated with the W of the OCC corresponding to index 1. t (0) and W t (1) Association: The OCC corresponding to index 1 can be associated with the W of the OCC corresponding to index 1. t (2) and W t (3) Association. By defining the association relationship between OCCs of different lengths based on subcode groups, the impact of OCC switching between paired ports can be reduced, and the flexibility of OCC switching can be improved. For example, assuming SRS port 1 to SRS port 4 use OCCs corresponding to indices 0 to 3 respectively, the W of the OCC corresponding to index 0 is associated with the OCC corresponding to index 2. t (0) and W t (1) The W of the OCC corresponding to index 1 and the OCC corresponding to index 2. t (2) and W t (3) The W of the OCC corresponding to index 2 and the OCC corresponding to index 0. t (0) and W t (1) The W of the OCC corresponding to index 3 and the OCC corresponding to index 0. t (2) and W tIn case (3), when the network device instructs SRS port 1 to switch to a 2-length OCC, SRS port 1 can use the W of the OCC corresponding to index 2. t (0) and W t (1) Partially, and in order to maintain the orthogonality between SRS ports 1 to 4, SRS ports 2 to 4 will also be switched to OCCs of length 2. And if the OCC corresponding to index 0 is associated with the W of the OCC corresponding to index 0... t (0) and W t (1) The W of the OCC corresponding to index 1 and the OCC corresponding to index 0. t (2) and W t (3) The W of the OCC corresponding to index 2 is associated with the OCC corresponding to index 2. t (0) and W t (1) The W of the OCC corresponding to index 3 and the OCC corresponding to index 2. t (2) and W t (3) In this case, when the network device instructs SRS port 1 to switch to a 2-length OCC, SRS port 1 can use the W of the OCC corresponding to index 0. t (0) and W t (1) Partially, and in order to maintain the orthogonality between SRS ports 1 to SRS ports, SRS port 2 can use the W of the OCC corresponding to index 0. t (2) and W t (3) Part, while SRS port 2 and SRS port 3 can be left unswitched.

[0155] It should be noted that although the above examples illustrate two types of predefined tables—one type including multiple OCC code groups and the other including only one OCC code group—the underlying principles of these two types of predefined tables are similar and can be used as a reference. For example, for the first type of predefined table, the relationships between indices corresponding to OCCs of different lengths can also be specified. Taking Table 2 as an example, it can be specified that indices 0, 8, and 4 are related; indices 1, 9, and 6 are related; indices 2, 10, and 5 are related; and indices 3, 11, and 7 are related. In this way, network devices can switch between OCCs of different lengths based on these relationships.

[0156] The above content introduces the relevant predefined tables provided in the embodiments of this application. The overall solution of the embodiments of this application is described below in conjunction with the relevant predefined tables.

[0157] Please see Figure 6 , Figure 6This is a flowchart illustrating a communication method disclosed in an embodiment of this application. Figure 6 In this system, network equipment can flexibly adjust the use of different lengths of OCC (Optical Cross-Cut Corner) on terminal devices to ensure SRS (Supported Resistant Signaling) coverage while minimizing overall network interference and reducing overall power consumption of terminal devices. For example... Figure 6 As shown, the method may include, but is not limited to, the following steps:

[0158] 601. The network device sends first information to the first terminal device. The first information is used to configure the first SRS port. The first SRS port corresponds to the first OCC. The number of time domain units of the first OCC is N, where N is a positive integer.

[0159] It is understandable that when a terminal device accesses a cell, the network device can configure an SRS port for the terminal device. Configuring an SRS port for a terminal device includes configuring SRS port resources, including but not limited to one or more of the following: OCC resources (OCC codes), time-domain resources, frequency-domain resources, spatial-domain resources, and cyclic shift. In this embodiment, the SRS time-domain resource configuration for a cell can be fixed. SRS time-domain resource configuration can also be called SRS time-domain unit configuration. SRS time-domain unit configurations can include, but are not limited to, 2, 4, 8, 12, and 16. For example, when a cell's SRS time-domain unit configuration is 2, the network device can allocate two OCCs corresponding to the time-domain units to all terminal devices within the cell, and can adjust the terminal device's use of OCCs with a length of 1 or 2 according to actual conditions, as shown in Table 1 above. For example, when the SRS time domain unit of a cell is configured to 4, the network device can allocate 4 time domain units corresponding to the terminal devices in the cell to each terminal device. The terminal devices can adjust the OCC with a length of 1, 2 or 4 according to the actual situation, as shown in Table 2 above.

[0160] For example, when a first terminal device accesses a cell, the network device can configure an SRS port for the first terminal device based on the cell's SRS time-domain unit configuration (T). For instance, based on the cell's SRS time-domain unit configuration (T), the network device can send first information to the first terminal device. Correspondingly, the first terminal device can receive the first information from the network device. This first information can be used to configure a first SRS port, which corresponds to a first OCC. The time-domain unit configuration corresponding to the first OCC is T, and the number of time-domain units in the first OCC is N, where N is a positive integer and N is less than or equal to T. In some possible implementations, the network device can determine a corresponding predefined table based on the cell's SRS time-domain unit configuration (T), and then select a first OCC for the first terminal device from the corresponding predefined table. For example, when T is 4, the network device can determine that the corresponding predefined table is Table 2 mentioned above, and then select a first OCC for the first terminal device from the OCCs in Table 2, such as using the OCC corresponding to index 0 as the first OCC. It should be understood that the first information may include the resource configuration information of the first SRS port, such as OCC resources, time domain resources, frequency domain resources, spatial domain resources, cyclic shift, etc.

[0161] In some possible implementation manners, the network device may first determine the OCC length N allocated to the first terminal device, and then may determine the first OCC with the length of N, such as selecting the first OCC with the length of N from a corresponding predefined table. Exemplarily, in one possible implementation manner, multiple types of UEs or SRS ports may be predefined, and different types of UEs or SRS ports use OCCs with different lengths. Wherein, the definition manner for the UE or SRS port type is not limited. For example, it may be defined based on the signal quality information of the terminal device, the distance between the terminal device and the network device, etc. The signal quality information of the terminal device may include one or more of path loss, signal to noise ratio (SNR), signal to interference plus noise ratio (SINR), reference signal received power (RSRP), etc. Exemplarily, path loss, SNR, SINR, RSRP, etc. may be for a single time domain unit. It can be understood that each type of UE or SRS port may correspond to a specific condition, which is equivalent to that different conditions may be associated with OCCs with different lengths. For example, taking RSRP as an example, multiple RSRP intervals may be defined, and each RSRP interval is associated with a type of UE, that is, each RSRP interval is associated with an OCC length, or multiple RSRP cumulative distribution function (CDF) intervals may be defined, and each RSRP CDF interval is associated with a type of UE, that is, each RSRP CDF interval is associated with an OCC length, or the above two manners may be combined. For example, it may be predefined that there are a first type of UE and a second type of UE. The first type of UE is the UE whose RSRP CDF is in the last x1% (of the cell), or the UE with RSRP < y1 dB, and other UEs are the second type of UE. The OCC length associated with the first type of UE is 2, and the OCC length associated with the second type of UE is 1. The values of x1 and y1 are not limited. Based on this, the network device may perform initial SRS resource allocation based on the RSRP of the physical random access channel (PRACH) corresponding to the terminal device. For example, the network device may determine the initial OCC length N allocated to the first terminal device based on the RSRP of the PRACH of the first terminal device, and then may determine the first OCC with the length of N.

[0162] Because the selectable OCC length varies under different SRS time domain unit configurations, in some possible implementations, multiple types of UEs or SRS ports can be defined for different SRS time domain unit configurations. This means defining the relationship between the terminal device's signal quality information, the distance between the terminal device and the network device, and the OCC length. For example, for an SRS time domain unit configuration of 2, two types of UEs or SRS ports can be defined, corresponding to OCCs of length 1 and 2 respectively. For an SRS time domain unit configuration of 4, three types of UEs or SRS ports can be defined, corresponding to OCCs of length 1, 2, and 4 respectively. For an SRS time domain unit configuration of 8, three types of UEs or SRS ports can be defined, corresponding to OCCs of length 1, 2, 4, and 8 respectively.

[0163] Understandably, to improve resource utilization, network devices can also configure non-OCC resources corresponding to the first SRS port to other SRS ports. However, the OCCs corresponding to these SRS ports should be orthogonal to the OCC corresponding to the first SRS port (such as OCCs in the same code group or sub-code group). These ports are thus paired ports. For example, a network device can send third information to a second terminal device. This third information configures the second SRS port, which corresponds to a third OCC. The time-domain unit corresponding to the third OCC is configured as T, the number of time-domain units of the third OCC is N, the third OCC is orthogonal to the first OCC, and the non-OCC resources corresponding to the first and second SRS ports are the same. It should be understood that the third information may include resource configuration information for the second SRS port, such as OCC resources, time-domain resources, frequency-domain resources, spatial-domain resources, cyclic shifts, etc. The statement that the first SRS port and the second SRS port have the same non-OCC resources can be understood as follows: Except for OCC resources, all other resources corresponding to the first SRS port and the second SRS port are the same, including but not limited to time domain resources, frequency domain resources, spatial domain resources, and cyclic shift. In other words, in the resource configuration information issued to the network device, apart from OCC, the comb offset value, comb degree, frequency hopping bandwidth, measurement bandwidth, and other configuration information are all the same. It should be noted that the first terminal device and the second terminal device can be the same terminal device or different terminal devices. When the first terminal device and the second terminal device are the same terminal device, the first SRS port and the second SRS port correspond to two different SRS ports of the same terminal device. It should be understood that the above only describes the first SRS port and the second SRS port as paired ports, but paired ports may also include other SRS ports. The number of paired ports may be related to the time domain unit configuration. For example, when the SRS time domain unit is configured as 2, the number of paired ports is at most 2; when the SRS time domain unit is configured as 4, the number of paired ports is at most 4; and when the SRS time domain unit is configured as 8, the number of paired ports is at most 8.

[0164] In this embodiment, for a specific time-domain unit configuration, multiple corresponding OCC code groups may be included, as shown in Tables 1, 2, 3, 4, and 5 above. In this case, in some possible implementations, the OCCs corresponding to paired ports can be OCCs in the same OCC code group, and paired ports refer to SRS ports with the same non-OCC resources. That is, network devices can assign OCCs in the same code group to paired ports, such as the first SRS port and the second SRS port. The first OCC and the third OCC can belong to the first OCC code group, which can include X OCCs. The time-domain unit configuration corresponding to these X OCCs can be T, the number of time-domain units for these X OCCs is N, and these X OCCs are orthogonal to each other, where X is an integer greater than 2. In some possible implementations, the first OCC code group is an OCC code group in a predefined table. This predefined table includes multiple OCC code groups, and these multiple OCC code groups also include a second OCC code group. In this predefined table, the number of time-domain units for OCCs in the same code group is the same, and the OCCs in the same code group are orthogonal to each other. For example, there can be corresponding predefined tables for different SRS time domain unit configurations, such as Table 1, Table 2, Table 3, Table 4, Table 5, etc.

[0165] In some other possible implementations, the OCCs corresponding to the paired ports can be OCCs from different OCC code groups. Specifically, for any two paired ports using OCCs from different code groups, the OCCs used by these two paired ports need to maintain time-domain orthogonality, or need to maintain partial time-domain orthogonality and partial orthogonality of non-zero elements.

[0166] In this embodiment, for a specific time-domain unit configuration, a corresponding OCC code group (such as a first OCC code group) may be included. The length of the OCCs in this OCC code group can be the same as that of the time-domain unit configuration, as shown in Tables 6 and 7 above. In this case, to support flexible switching of OCCs of different lengths, OCCs of different lengths, such as 1-length and 2-length, can be divided based on the OCCs in the first OCC code group. Furthermore, the association relationship between OCCs of different lengths, such as 1-length and 2-length, can be specified. Further, the OCCs in the first OCC code group can be divided into multiple sub-code groups. Based on the division of sub-code groups, when specifying the association relationship between OCCs of different lengths, for cases where the length is greater than 1, the association relationship between OCCs of different lengths can be specified based on the sub-code groups. For the description of sub-code groups and the division of OCCs of different lengths, please refer to the relevant descriptions in the corresponding parts of Tables 6 and 7 above.

[0167] For example, the first OCC and the third OCC can belong to a first OCC code group. The first OCC code group can include X OCCs, the time-domain unit configuration corresponding to the X OCCs can be T, the number of time-domain units of the X OCCs is N, and the X OCCs are orthogonal to each other by a length of N, where X is an integer greater than 2. In some possible implementations, the first OCC code group is an OCC code group in a predefined table. It should be understood that for different SRS time-domain unit configurations, there can be corresponding predefined tables, such as Table 6 and Table 7 above.

[0168] It should be understood that SRS can be sent periodically. In this embodiment, the SRS time domain unit configuration can be the number of time domain units included in one SRS period. It should also be understood that when configuring the OCC of the SRS port for the terminal device, the network device can issue an OCC index (such as the indexes in the predefined tables mentioned above) to indicate the corresponding OCC. Accordingly, the terminal device can look up the table based on the corresponding time domain unit configuration and the index. Alternatively, the network device can issue an OCC index and the corresponding OCC length to determine the OCC of that OCC length associated with the OCC corresponding to that OCC index. For example, for Table 7 above, the OCC corresponding to index 0 can be associated with the W of the OCC corresponding to index 0. t (0) and W t (1) Partial association, therefore, the W of the OCC corresponding to index 0 can be indicated by sending index 0 and length 2. t (0) and W t (1) Part, equivalent to indicating OCC [+1+1 0 0]. It should be noted that since the network device is responsible for the overall scheduling of SRS resources, in some possible implementations, the network device can adjust the SRS time domain unit configuration of the SRS port as needed, and can reallocate the corresponding time domain resources and OCC resources to ensure the orthogonality of each SRS port. For example, for Table 7 above, the OCC corresponding to index 0 can be the same as the W of the OCC corresponding to index 0. t (0) and W t (1) Partial association: The OCC corresponding to index 1 can be associated with the W of the OCC corresponding to index 0. t (2) and W t (3) Partial association. In this case, the network device can send index 0 and SRS time domain unit configuration (2) to the terminal device corresponding to SRS port 1. Index 0 and SRS time domain unit configuration (2) can indicate the W of the OCC corresponding to index 0. t (0) and W t(1) In part, the time domain resources corresponding to SRS port 1 can be time domain symbol 1 and time domain symbol 2. The network device can also send index 1 and SRS time domain unit configuration (2) to the terminal device corresponding to SRS port 2. Index 1 and SRS time domain unit configuration (2) can indicate the W of the OCC corresponding to index 0. t (2) and W t (3) In this part, the time domain resources corresponding to SRS port 2 can be time domain symbols 3 and 4. Afterwards, if SRS port 1 and SRS port 2 need to switch to a 4-length OCC, the network device can send index 0 and SRS time domain unit configuration (4) to the terminal device corresponding to SRS port 1. Index 0 and SRS time domain unit configuration (4) can indicate the 4-length OCC corresponding to index 0. Similarly, it can send index 1 and SRS time domain unit configuration (4) to the terminal device corresponding to SRS port 2. Index 1 and SRS time domain unit configuration (4) can indicate the 4-length OCC corresponding to index 1. At this time, the time domain resources corresponding to SRS port 1 and SRS port 2 can be the same, such as time domain symbols 1 to 4. In this method, the SRS time domain unit configuration can be associated with the corresponding OCC length, that is, the SRS time domain unit configuration and the OCC length are the same.

[0169] 602. The first terminal device sends the first SRS through the first SRS port.

[0170] After receiving the first information from the network device, the first terminal device can send the first SRS through the first SRS port. Correspondingly, the network device can receive the first SRS sent by the first terminal device through the first SRS port. It should be understood that when the first terminal device sends the first SRS through the first SRS port, the OCC corresponding to the first SRS port is the first OCC.

[0171] Similarly, after receiving the third information from the network device, the second terminal device can send the third SRS through the second SRS port. Correspondingly, the network device can receive the third SRS sent by the second terminal device through the second SRS port. The third SRS uses the same non-OCC resources as the first SRS; that is, the third SRS and the first SRS can be sent using the same time-domain resources, frequency-domain resources, spatial-domain resources, cyclic sequences, etc. It should be understood that when the second terminal device sends the third SRS through the second SRS port, the OCC corresponding to the second SRS port is the third OCC.

[0172] 603. The network device sends second information to the first terminal device. The second information is used to indicate that the OCC corresponding to the first SRS port is switched to the second OCC. The number of time domain units of the second OCC is M, where M is a positive integer different from N.

[0173] In this embodiment, the network device can determine whether the OCC corresponding to the first SRS port needs to be switched to an OCC of other lengths based on real-time conditions. When it needs to be switched to an OCC of length M, the network device can send second information to the first terminal device. Accordingly, the first terminal device can receive the second information from the network device. The second information can be used to instruct the OCC corresponding to the first SRS port to switch to a second OCC. The time domain unit configuration corresponding to the second OCC can be T, and the number of time domain units of the second OCC is M, where M is a positive integer different from N.

[0174] In some possible implementations, when the OCC corresponding to the first SRS port switches to the second OCC, if the second OCC and the third OCC are not orthogonal, it will disrupt the orthogonality between the first and second SRS ports. In this case, the network device can also switch the OCC of the second SRS port. For example, the network device can send a fourth message to the second terminal device. Accordingly, the second terminal device can receive the fourth message from the network device. The fourth message can be used to instruct the OCC corresponding to the second SRS port to switch to the fourth OCC. The time domain unit configuration corresponding to the fourth OCC can be T, the number of time domain units of the fourth OCC is M, and the fourth OCC is orthogonal to the second OCC.

[0175] In the case of a specific time-domain unit configuration including multiple corresponding OCC code groups, the second OCC and the fourth OCC can belong to the second OCC code group. The second OCC code group includes Y OCCs, the time-domain unit configuration corresponding to the Y OCCs can be T, the number of time-domain units of the Y OCCs is M, the Y OCCs are orthogonal to each other, and Y is an integer greater than 2.

[0176] For example, when the time domain unit is configured to 2, and N is 2 and M is 1, the first code group may include [+1+1] and [+1 -1], and the second code group may include [1 0] and [0 1]. When the time domain unit is configured to 4, and N is 4 and M is 1, the first code group may include [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1], and the second code group may include [1 0 0 0], [0 1 0 0], [0 0 1 0] and [0 0 0 1]. When the time-domain unit is configured to be 8, and N is 8 and M is 1, the first code group can include [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1-1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1-1-1-1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1-1-1]. The second code group can include [1 0 00 0 0 0 0], [0 1 0 0 0 0 0 0], [0 0 1 0 0 0 0 0][0 0 0 1 0 0 0] [0], [0 0 0 0 1 0 0 0], [0 0 00 0 1 0 0], [0 0 0 0 0 0 1 0], and [0 0 0 0 0 0 0 1]. For example, the first OCC is [+1+1+1+1], the second OCC is [+1+1 -1-1], the third OCC is [10 0 0], and the fourth OCC is [0 1 0 0]. It should be understood that the above descriptions of the first and second code groups are merely illustrative and do not constitute a limitation. More detailed information can be found in Tables 1, 2, and 3 above, as well as the corresponding descriptions.

[0177] For a specific time-domain unit configuration, including a corresponding OCC code group, the first OCC code group can include multiple sub-code groups, that is, the X OCCs can be divided into multiple sub-code groups. The fifth OCC in the first sub-code group can be composed of multiple L-length sub-codes, each of which is orthogonal to the corresponding L-length portion of the OCCs in the remaining sub-code groups. These multiple L-length sub-codes include the second OCC and the fourth OCC. The first sub-code group is any one of these multiple sub-code groups, with the first OCC and the third OCC belonging to the first sub-code group, and L being an integer greater than or equal to 2.

[0178] It should be noted that the paired ports corresponding to the first subcode group can have an association relationship. This association relationship means that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. Paired ports refer to SRS ports with the same non-OCC resources. In other words, in order to maintain the orthogonality of paired ports, paired ports can use different OCCs in the first subcode group, or they can use multiple L-length subcodes corresponding to the fifth OCC.

[0179] For example, when the time domain unit is configured to 4, when N is 4 and M and L are 2, the first code group may include [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1]. The first code group may include sub-code groups [+1+1+1+1], [+1+1 -1-1], and sub-code groups [+1 -1+1 -1] and [+1 -1-1+1]. When the time-domain unit is configured to 8, and N is 8, M and L are 4, the first code group can include [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1-1+1-1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1-1-1], and the first code group can include the sub-code groups [+1+1+1+1+1+1+1+1+1] and [+1+1+1+1-1-1-1-1]. -1-1], [+1+1 -1-1 -1-1+1+1], subcode group [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], and subcode group [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1 -1+1 -1+1 -1]. When the time-domain unit is configured to 8, and N is 8, M and L are 2, the first code group can include [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1-1-1+1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1-1], and the first code group can include the sub-code groups [+1+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1- ...-1], [+1+1-1-1-1-1-1-1], [+1+1-1-1-1-1-1-1], [+1+1-1-1-1-1-1-1], [+1+1-1-1-1-1-1-1], [+1+1-1- -1-1 -1-1+1+1], and subcode groups [+1 -1+1 -1+1-1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1 -1+1 -1+1], [+1 -1-1+1 -1+1+1 -1].

[0180] The following is an example illustrating how to adjust the OCC corresponding to the SRS port of a network device.

[0181] In some possible implementations, multiple types of UE or SRS ports can be predefined, with different types of UE or SRS ports using different OCC lengths. The definition method for UE or SRS port types is not limited; for example, it can be based on the signal quality information of the terminal device, the signal quality information of the SRS port, the distance between the terminal device and the network device, etc. Signal quality information can include one or more of path loss, SNR, SINR, RSRP, etc. For example, since different UE or SRS ports use different OCCs, to accurately measure the signal quality of the UE or SRS port, the signal quality information can be specific to a single time-domain unit. It is understood that each type of UE or SRS port can correspond to specific conditions; that is, different conditions can be associated with different OCC lengths. Furthermore, since the selectable OCC length differs under different SRS time-domain unit configurations, in some possible implementations, multiple types of UE or SRS ports can be defined separately for different SRS time-domain unit configurations, that is, the correlation between the signal quality information of the terminal device, the distance between the terminal device and the network device, etc., and the OCC length can be defined separately.

[0182] Exemplarily, the number of time domain units of the OCC corresponding to the SRS port is related to the signal quality information associated with the SRS port. Based on this, the network device can determine the second OCC according to the signal quality information associated with the first SRS port, that is, determine to switch the first OCC to the second OCC. In a possible implementation manner, the signal quality information can be defined with multiple threshold intervals, and different threshold intervals can correspond to OCCs with different numbers of time domain units, that is, different threshold intervals can correspond to different OCC lengths. The multiple threshold intervals can include a first threshold interval, and the first threshold interval corresponds to an OCC with the number of time domain units being M. In this case, the network device can determine the first threshold interval corresponding to the signal quality information associated with the first SRS port, and then can determine the second OCC based on the first threshold interval. In the embodiments of this application, the multiple threshold intervals can further include a second threshold interval, and the second threshold interval can correspond to an OCC with the number of time domain units being N. In some possible implementation manners, for a threshold interval, when the signal quality information of the SRS port is within this threshold interval, using the OCC with the length corresponding to this threshold interval for this SRS port can ensure the coverage of this SRS port, and will not cause the actual coverage range to far exceed the coverage range required by the SRS. In this way, while ensuring the coverage of the SRS port, power consumption waste can be avoided, and the overall power consumption of the terminal device is relatively low. Generally, the larger the SNR, SINR, RSRP, etc. corresponding to a single time domain unit, the better the signal quality. Therefore, the corresponding OCC length can be smaller. On the contrary, the smaller the SNR, SINR, RSRP, etc. corresponding to a single time domain unit, the worse the signal quality. Therefore, the corresponding OCC length can be larger.

[0183] For example, taking RSRP as an example, multiple RSRP intervals can be defined, and each RSRP interval is associated with a type of UE / SRS port, that is, each RSRP interval is associated with an OCC length. Or multiple RSRP CDF intervals can be defined, and each RSRP CDF interval is associated with a type of UE / SRS port, that is, each RSRP CDF interval is associated with an OCC length. Or the above two methods can be combined. For example, the first type of SRS port and the second type of SRS port can be predefined. The first type of SRS port is the UE with the RSRP CDF in the (cell) last x1%, or the UE with RSRP < y1 dB. Other SRS ports are the second type of SRS port. The OCC length associated with the first type of SRS port is 2, and the OCC length associated with the second type of SRS port is 1. The values of x1 and y1 are not limited. The above RSRP can also be replaced with SNR, SINR, etc.

[0184] It is understandable that when a network device determines whether to switch the OCC of a first SRS port based on the signal quality information associated with that first SRS port, it can do so based on the signal quality information currently associated with the first SRS port. For example, a first terminal device can periodically send SRS signals through the first SRS port, and the network device can periodically receive the SRS signals sent by the first terminal device through the first SRS port, and can periodically determine whether to switch the OCC of the first SRS port based on the signal quality information associated with the first SRS port.

[0185] It should be understood that switching between multiple paired ports can affect each other. When any one of the paired ports switches its OCC, it may cause that paired port to become non-orthogonal to one or more of the remaining paired ports. Therefore, in one possible implementation, the network device can determine whether to switch the OCC of all or some of the paired ports based on the signal quality information associated with the multiple paired ports. That is, the network device can comprehensively consider the signal quality information associated with the multiple paired ports and then make an OCC switching decision. In some possible implementations, when determining multiple OCC lengths based on the signal quality information associated with the multiple paired ports, the largest OCC length among these multiple OCC lengths can be used as the target length, and then all the paired ports can use the target length OCC. For example, assuming SRS port 1 and SRS port 2 are paired ports, using the OCCs corresponding to indices 0 and 1 in Table 1 respectively, i.e., [+1+1] and [+1-1], if the RSRPs of SRS port 1 and SRS port 2 measured by the network device in a certain period are P1 and P2 respectively, and P1 belongs to the predefined RSRP interval 1 with an OCC length of 1, and P2 belongs to the predefined RSRP interval 2 with an OCC length of 2, then the network device can use length 2 as the target length, and SRS port 1 and SRS port 2 do not need to switch OCCs. It should be understood that in some cases, when the network device comprehensively considers the signal quality information associated with multiple paired ports and makes an OCC switching decision, it may only switch some of the paired ports. For example, assuming SRS ports 1 to 4 are paired ports, and the OCCs corresponding to indices 0 to 3 in Table 2 are used respectively, if the RSRPs of SRS ports 1 to 4 measured by the network device in a certain period are P1, P2, P3, and P4 respectively, and P1 and P2 belong to the predefined RSRP interval 1, the OCC length corresponding to RSRP interval 1 is 2, and P3 and P4 belong to the predefined RSRP interval 2, the OCC length corresponding to RSRP interval 2 is 4, in this case, the network device can use length 2 as the target length of SRS ports 1 and 2, and SRS ports 1 and 2 can be switched to the OCCs corresponding to indices 4 and 6 in Table 2 respectively, while SRS ports 3 and 4 do not need to switch OCCs.

[0186] It should be noted that the above description of network devices adjusting the OCC corresponding to SRS ports is merely an illustrative example. In some possible implementations, network devices need to consider more information when making OCC handover decisions, such as the interference situation in the local cell and the interference situation in neighboring cells (e.g., the interference of multiple paired ports to neighboring cells). Alternatively, in some possible situations (e.g., when the network device determines that each paired port needs to use an OCC of different lengths), the network device can reallocate non-OCC resources to the paired ports, such as reallocating time-domain resources, so that each SRS port can guarantee good signal quality and minimize overall network interference while ensuring coverage.

[0187] 604. The first terminal device sends the second SRS through the first SRS port.

[0188] After receiving the second information from the network device, the first terminal device can switch the OCC corresponding to the first SRS port to the second OCC, and the first terminal device can send the second SRS through the first SRS port. Correspondingly, the network device can receive the second SRS sent by the first terminal device through the first SRS port. It should be understood that when the first terminal device sends the second SRS through the first SRS port, the OCC corresponding to the second SRS port is the second OCC.

[0189] Similarly, after receiving the fourth information from the network device, the second terminal device can send the fourth SRS through the second SRS port. Correspondingly, the network device can receive the fourth SRS sent by the second terminal device through the second SRS port. The non-OCC resource corresponding to the fourth SRS is the same as that corresponding to the second SRS. It should be understood that when the second terminal device sends the fourth SRS through the second SRS port, the OCC corresponding to the second SRS port is the fourth OCC.

[0190] For example, please see Figure 7 , Figure 7 This is a schematic diagram illustrating an OCC switching scenario disclosed in an embodiment of this application. Figure 7 As shown, the paired ports of UE1 and UE2 can use OCCs of length 1 or 2 as shown in Table 1. For example, when the distance to the network device is small (e.g., SRS-RSRP is less than the first threshold), a length 1 OCC can be used. When the distance to the network device is large (e.g., SRS-RSRP is greater than or equal to the first threshold), a length 2 OCC can be used. In this way, as UE1 and UE2 move, different lengths of OCCs can be flexibly switched. While ensuring OCC coverage, the overall power consumption of the terminal device can be kept low, and the overall network interference level can be reduced, such as reducing interference to terminal devices in neighboring cells.

[0191] It is understandable that the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) may collide with the time-domain resources corresponding to the SRS port. Furthermore, the collision can occur in two ways: a complete collision or a partial collision. For example, if the time-domain resources corresponding to the SRS port are time-domain units 1, 2, 3, and 4, and the time-domain resources corresponding to the PUSCH or PUCCH are also time-domain units 1, 2, 3, and 4, then it is a complete collision. If the time-domain resources corresponding to the PUSCH or PUCCH are time-domain units 1 and 2, then it is a partial collision, meaning a collision occurs between time-domain units 1 and 2, but not between time-domain units 3 and 4. It should be understood that the collision between the time-domain resources corresponding to PUSCH or PUCCH and the time-domain resources corresponding to the SRS port can be a collision between the time-domain resources corresponding to a certain SRS cycle of the SRS port.

[0192] In some possible implementations of this application, when the time-domain resources corresponding to PUSCH or PUCCH collide (completely or partially) with the time-domain resources corresponding to multiple paired ports, all of the multiple paired ports abandon transmitting SRS. For example, when the time-domain resources corresponding to PUSCH or PUCCH collide with the time-domain resources corresponding to the first paired port, the network device sends a fifth message, such as sending the fifth message to the terminal device (e.g., the first terminal device) corresponding to the first paired port. The fifth message can be used to instruct that the collapsing time-domain resources should be abandoned so that SRS can be transmitted through the SRS port in the first paired port. The first paired port includes multiple SRS ports, including the first SRS port, and the non-OCC resources corresponding to these multiple SRS ports are the same. For example, the network device can send the fifth message to the first terminal device, which can be used to instruct that the collapsing time-domain resources should be abandoned so that SRS can be transmitted through the first SRS port. Accordingly, the first terminal device can receive the fifth message from the network device, and subsequently, the first terminal device can abandon the collapsing time-domain resources and transmit SRS through the first SRS port.

[0193] In other possible implementations, when the time-domain resources corresponding to PUSCH or PUCCH partially collide with the time-domain resources corresponding to multiple paired ports, some of the paired ports may abandon sending SRS, while others may send SRS on the uncollided portion of the time-domain resources. For example, when the time-domain resources corresponding to PUSCH or PUCCH partially collide with the time-domain resources corresponding to the first paired port, the network device sends a sixth and a seventh message, such as sending the sixth message to the terminal device corresponding to the first part of the SRS port and sending the seventh message to the terminal device corresponding to the second part of the SRS port. The sixth message can be used to instruct that SRS be sent through the first part of the SRS ports in the uncollided portion of the time-domain resources. The seventh message is used to instruct that SRS be abandoned on the collided and uncollided time-domain resources through the second part of the SRS ports in the first paired port. The first paired port includes multiple SRS ports, including the first SRS port, and the non-OCC resources corresponding to these multiple SRS ports are the same. For example, the network device can send a sixth message to the first terminal device, which can be used to instruct the transmission of SRS through the first SRS port for time-domain resources in the non-collision portion. Accordingly, the first terminal device can receive the sixth message from the network device, and subsequently, the first terminal device can transmit SRS through the first SRS port for the time-domain resources in the non-collision portion. Alternatively, the network device can send a seventh message to the first terminal device, which can be used to instruct the abandonment of transmitting SRS through the first SRS port for both the collapsing and non-collision time-domain resources. Accordingly, the first terminal device can receive the seventh message from the network device, and subsequently, the first terminal device can abandon transmitting SRS through the first SRS port for both the collapsing and non-collision time-domain resources.

[0194] It should be understood that when instructing the first part of the SRS ports in the first pairing ports to send SRS in the time domain resources of the non-collision portion, in order to ensure the orthogonality between the first part of the SRS ports, the network device may also indicate a temporary OCC for the first part of the SRS ports.

[0195] For example, please see Figure 8Assuming SRS ports 1 through 4 are paired ports, each using the OCC corresponding to indices 0 through 3 in Table 2, and the time-domain resources corresponding to SRS ports 1 through 4 include time-domain unit 1, time-domain unit 2, time-domain unit 3, and time-domain unit 4, if the time-domain resources corresponding to PUSCH or PUCCH collide with the time-domain resources corresponding to multiple paired ports (e.g., collision between time-domain unit 1 and time-domain unit 2), then two of the SRS ports 1 through 4 can be allowed to send SRS in the uncollapsed portion of the time-domain resources (time-domain unit 3 and time-domain unit 4). For example, SRS ports 1 and 2 can be allowed to send SRS in time-domain units 3 and 4, while SRS ports 3 and 4 can abandon sending SRS in time-domain units 1 through 4. Furthermore, the network device can indicate temporary OCCs for SRS ports 1 and 2, such as switching SRS ports 1 and 2 to the OCCs corresponding to indices 6 and 7 in Table 2, respectively. Alternatively, the network device can indicate the two long OCCs corresponding to time domain unit 3 and time domain unit 4, namely [+1+1] and [+1 -1].

[0196] It should be noted that the first, second, third, fourth, fifth, sixth, and seventh information mentioned above can be carried in RRC messages, MAC control elements (MAC CE), or downlink control information (DCI), etc., and this application embodiment does not limit this.

[0197] In the above processing flow, network devices can flexibly adjust the use of different lengths of OCC on the SRS port based on the real-time status of the terminal device / terminal device's SRS port. While ensuring coverage, this can reduce the overall power consumption of the terminal device and reduce the overall network interference.

[0198] It is understood that the technical solutions provided in this application can be used in the architecture of open access networks. The operations performed by the aforementioned network devices can be executed by one or more nodes such as CU, DU, CU-CP, CU-UP, and RIC (e.g., near-RT RIC, Non-RT RIC). Information sent by the terminal device to the network device can be sent to nodes such as CU, DU, CU-CP, CU-UP, or RIC (e.g., near-RT RIC, Non-RT RIC), and this application does not limit this. For example, the network device can send relevant information, such as the aforementioned first information, to the terminal device through CU, DU, CU-CP, CU-UP, or RIC.

[0199] It should be noted that the relevant information and descriptions in the different embodiments described above can be referenced interchangeably. It should also be noted that although the above description focuses on the interaction between the UE and the network device, in some possible implementations, the UE and the network device can also be other communication devices, which are not limited here.

[0200] It should be understood that the above Figure 6 The above processing flow is illustrated primarily using terminal devices (such as the first terminal device) and network devices as the executing entities for the interaction, but this application does not limit the executing entities for this interaction. For example, Figure 6 The terminal device in this context can also be a chip, chip system, or processor that supports the implementation of this method on the terminal device; it can also be a logic module or software that can implement all or part of the terminal device. For example, Figure 6 The network device in the text can also be a chip, chip system, or processor that supports the implementation of the method on the network device, or it can be a logic module or software that can implement all or part of the functions of the network device.

[0201] The foregoing mainly describes the communication methods provided in the embodiments of this application. It is understood that, in order to achieve the corresponding functions, the aforementioned terminal devices and network devices may include hardware structures and / or software modules corresponding to the execution of each function. Based on the units and steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by 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 the embodiments of this application.

[0202] This application embodiment can divide terminal devices and network devices into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one 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; other division methods may be used in actual implementation.

[0203] When dividing each function into modules according to its corresponding function. Figure 9A possible structural schematic diagram of a communication device 900 is shown. The communication device 900 includes a communication unit 901. The communication device 900 may also include a processing unit 902. Optionally, the communication unit 901 may also be referred to as a transceiver unit, an output unit, or an interface unit, etc. In one possible implementation, the communication unit 901 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc. In one possible design, the communication device 900 may be the aforementioned network device, or it may be a component within the network device (e.g., a processor, chip, chip system, circuit, or functional module), or it may be a processing system within the network device, etc.

[0204] When the communication device 900 is used in the above Figure 6 The network device functions as illustrated in the embodiments shown, for example:

[0205] The communication unit 901 is used to send first information, which is used to configure a first channel sounding reference signal (SRS) port, the first SRS port corresponds to a first orthogonal mask (OCC), and the number of time-domain units of the first OCC is N, where N is a positive integer.

[0206] The communication unit 901 is also used to receive the first SRS transmitted through the first SRS port;

[0207] The communication unit 901 is also used to send second information, which is used to instruct the OCC corresponding to the first SRS port to switch to the second OCC, wherein the number of time domain units of the second OCC is M, and M is a positive integer different from N;

[0208] The communication unit 901 is also used to receive a second SRS transmitted through the first SRS port.

[0209] In one possible implementation, the communication unit 901 is further configured to send third information, which configures a second SRS port corresponding to a third OCC. The third OCC has N time-domain units and is orthogonal to the first OCC. The non-OCC resources corresponding to the first SRS port and the second SRS port are the same. The communication unit 901 is further configured to receive a third SRS sent through the second SRS port, which has the same non-OCC resources corresponding to the first SRS. The communication unit 901 is further configured to send fourth information, which instructs the OCC corresponding to the second SRS port to switch to a fourth OCC. The fourth OCC has M time-domain units and is orthogonal to the second OCC. The communication unit 901 is further configured to receive a fourth SRS sent through the second SRS port, which has the same non-OCC resources corresponding to the second SRS, including time-frequency resources.

[0210] In one possible implementation, the first OCC and the third OCC belong to a first OCC code group, which includes X OCCs, each with N time-domain units, and the X OCCs are mutually orthogonal. The second OCC and the fourth OCC belong to a second OCC code group, which includes Y OCCs, each with M time-domain units, and the Y OCCs are mutually orthogonal. X and Y are integers greater than 2.

[0211] In one possible implementation, the OCC corresponding to the paired port is the OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

[0212] In one possible implementation, the first OCC code group and the second OCC code group are OCC code groups in a predefined table. The predefined table includes multiple OCC code groups, and the OCCs in the same code group in the predefined table have the same number of time-domain units and are orthogonal to each other.

[0213] In one possible implementation, when N is 2 and M is 1, the first code group includes [+1+1] and [+1 -1], and the second code group includes [1 0] and [0 1]; when N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [0 0 1 0] and [0 0 0 1]; when N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [ ... The second code group includes [1 0 0 0 0 0 0 0 0], [01 0 0 0 0 0 0], [0 0 1 0 0 0 0 0 0][0 0 0 0 0][0 0 0 1 0 0 0 0 0], [0 0 0 0 0 1 0 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0], and [0 0 0 0 0 0 1].

[0214] In one possible implementation, the first OCC and the third OCC belong to a first OCC code group, which includes X OCCs, each with N time-domain units. The X OCCs are orthogonal to each other by a length of N. The first OCC code group includes multiple sub-code groups. The fifth OCC in the first sub-code group is composed of multiple L-length sub-codes, which are orthogonal to the corresponding L-length portions of the OCCs in the remaining sub-code groups. The multiple L-length sub-codes include the second OCC and the fourth OCC. The first sub-code group is any one of the multiple sub-code groups. The first OCC and the third OCC belong to the first sub-code group, where L is an integer greater than or equal to 2.

[0215] In one possible implementation, the paired ports corresponding to the first subcode group have an association relationship, which is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired ports refer to SRS ports with the same non-OCC resources, and the non-OCC resources include time and frequency resources.

[0216] In one possible implementation, the first OCC code group is an OCC code group in a predefined table.

[0217] In one possible implementation, when N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1], and [+1 -1-1+1]. This first code group includes sub-code groups [+1+1+1+1], [+1+1 -1-1], and [+1 -1+1 -1], and [+1 -1-1+1]. When N is 8 and M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1 -1-1+1+1 -1-1-1], [+1 -1+1 -1-1-1+1+1], [+1 -1+1 -1+1-1+1 -1-1], [+1 -1+1] The first code group includes subcode groups [+1+1+1+1+1+1+1], [+1+1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1], [+1+1+1+1+1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1-1+1], [+1-1-1-1-1-1+1+1], [+1-1-1-1-1-1-1], [+1-1-1-1-1-1-1], and [+1-1-1-1+1-1-1+1], [+1- ...], [+1-1-1-1-1], [+1-1-1-1-1], [+1-1 -1]; When N is 8, M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1-1-1 -1-1+1+1], [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1] and [+1 -1-1+1 -1+1+1 -1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], and subcode groups [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1 -1+1 -1+1], [+1 -1-1+1 -1+1+1 -1].

[0218] In one possible implementation, the number of time-domain units of the OCC corresponding to the SRS port is related to the signal quality information associated with the SRS port. Before sending the second information, the processing unit 902 is used to determine the second OCC based on the signal quality information associated with the first SRS port.

[0219] In one possible implementation, the signal quality information defines multiple threshold intervals, and different threshold intervals correspond to OCCs with different numbers of time-domain units. The processing unit 902 determines the second OCC based on the signal quality information associated with the first SRS port by: determining a first threshold interval corresponding to the signal quality information associated with the first SRS port, wherein the multiple threshold intervals include the first threshold interval, and the first threshold interval corresponds to an OCC with a number of time-domain units of M; and determining the second OCC based on the first threshold interval.

[0220] In one possible implementation, the communication unit 901 is further configured to send fifth information when the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) collide with the time-domain resources corresponding to the first paired port. The fifth information is used to indicate that the collided time-domain resources should be abandoned so that SRS can be sent through the SRS port in the first paired port. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

[0221] In one possible implementation, the communication unit 901 is further configured to send a sixth message and a seventh message when the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) collide with the time-domain resources corresponding to the first paired port. The sixth message is used to instruct that the time-domain resources in the non-collision portion be sent through the first part of the SRS port in the first paired port, and the seventh message is used to instruct that the time-domain resources in the collision portion and the time-domain resources in the non-collision portion be abandoned and sent through the second part of the SRS port in the first paired port. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

[0222] For details on the operation of each unit in the aforementioned communication device 900, please refer to the above. Figure 6 The descriptions of the network devices in the illustrated embodiments are not repeated here.

[0223] In another possible design, the communication device 900 may be the aforementioned terminal device, or a component of the terminal device (e.g., a processor, chip, chip system, circuit, or functional module), or a processing system of the terminal device, etc.

[0224] When the communication device 900 is used in the above Figure 6 The functions of the terminal device (first terminal device) in the illustrated embodiment are exemplified as follows:

[0225] The communication unit 901 is used to receive first information, which is used to configure a first channel sounding reference signal (SRS) port, the first SRS port corresponds to a first orthogonal mask (OCC), and the number of time-domain units of the first OCC is N, where N is a positive integer.

[0226] The communication unit 901 is also used to send the first SRS through the first SRS port;

[0227] The communication unit 901 is also used to receive second information, which is used to instruct the OCC corresponding to the first SRS port to switch to the second OCC, wherein the number of time domain units of the second OCC is M, and M is a positive integer different from N;

[0228] The communication unit 901 is also used to send a second SRS through the first SRS port.

[0229] In one possible implementation, the first OCC belongs to a first OCC code group, which includes X OCCs, the number of time-domain units of the X OCCs is N, and the X OCCs are mutually orthogonal; the second OCC belongs to a second OCC code group, which includes Y OCCs, the number of time-domain units of the Y OCCs is M, and the Y OCCs are mutually orthogonal; X and Y are integers greater than 2.

[0230] In one possible implementation, the OCC corresponding to the paired port is the OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

[0231] In one possible implementation, the first OCC code group and the second OCC code group are OCC code groups in a predefined table. The predefined table includes multiple OCC code groups, and the OCCs in the same code group in the predefined table have the same number of time-domain units and are orthogonal to each other.

[0232] In one possible implementation, when N is 2 and M is 1, the first code group includes [+1+1] and [+1 -1], and the second code group includes [1 0] and [0 1]; when N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1] and [+1 -1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [0 0 1 0] and [0 0 0 1]; when N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [ ... The second code group includes [1 0 0 0 0 0 0 0 0], [01 0 0 0 0 0 0], [0 0 1 0 0 0 0 0 0][0 0 0 0 0][0 0 0 1 0 0 0 0 0], [0 0 0 0 0 1 0 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0 0 0 0], [0 0 0 0 0 1 0], and [0 0 0 0 0 0 1].

[0233] In one possible implementation, the first OCC belongs to a first OCC code group, which includes X OCCs, each with N time-domain units. The X OCCs are orthogonal to each other by a length of N. The first OCC code group includes multiple sub-code groups. The fifth OCC in the first sub-code group is composed of multiple L-length sub-codes, which are orthogonal to the corresponding L-length portions of the OCCs in the remaining sub-code groups. The multiple L-length sub-codes include the second OCC. The first sub-code group is any one of the multiple sub-code groups, and the first OCC belongs to the first sub-code group. L is an integer greater than or equal to 2.

[0234] In one possible implementation, the paired ports corresponding to the first subcode group have an association relationship, which is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired ports refer to SRS ports with the same non-OCC resources, and the non-OCC resources include time and frequency resources.

[0235] In one possible implementation, the first OCC code group is an OCC code group in a predefined table.

[0236] In one possible implementation, when N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1 -1-1], [+1 -1+1 -1], and [+1 -1-1+1]. This first code group includes sub-code groups [+1+1+1+1], [+1+1 -1-1], and [+1 -1+1 -1], and [+1 -1-1+1]. When N is 8 and M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1 -1-1+1+1 -1-1-1], [+1 -1+1 -1-1-1+1+1], [+1 -1+1 -1+1-1+1 -1-1], [+1 -1+1] The first code group includes subcode groups [+1+1+1+1+1+1+1], [+1+1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1], [+1+1+1+1+1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1-1+1], [+1-1-1-1-1-1+1+1], [+1-1-1-1-1-1-1], [+1-1-1-1-1-1-1], and [+1-1-1-1+1-1-1+1], [+1- ...], [+1-1-1-1-1], [+1-1-1-1-1], [+1-1 -1]; When N is 8, M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1-1-1 -1-1+1+1], [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1] and [+1 -1-1+1 -1+1+1 -1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1+1], [+1+1+1+1 -1-1 -1-1], [+1+1 -1-1+1+1 -1-1], [+1+1 -1-1 -1-1+1+1], and subcode groups [+1 -1+1 -1+1 -1+1 -1], [+1 -1+1 -1-1+1 -1+1], [+1 -1-1+1+1 -1-1+1], [+1 -1-1+1 -1+1 -1+1], [+1 -1-1+1 -1+1+1 -1].

[0237] In one possible implementation, the communication unit 901 is further configured to receive fifth information when the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) collide with the time-domain resources corresponding to the first paired port. The fifth information is used to instruct the abandonment of sending SRS through the SRS port in the first paired port for the time-domain resources that collide. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

[0238] In one possible implementation, the communication unit 901 is further configured to receive sixth information when the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) partially collide with the time-domain resources corresponding to the first paired port. The sixth information is configured to instruct the time-domain resources in the non-collision portion to transmit SRS through the first part of the SRS port in the first paired port; or, to receive seventh information, the seventh information is configured to instruct the abandonment of transmitting SRS through the second part of the SRS port in the first paired port for both the colliding and non-collision time-domain resources. The first paired port includes multiple SRS ports, the multiple SRS ports include the first SRS port, and the non-OCC resources corresponding to the multiple SRS ports are the same, including time-frequency resources.

[0239] For details on the operation of each unit in the aforementioned communication device 900, please refer to the above. Figure 6 The description of the terminal device in the illustrated embodiment will not be repeated here.

[0240] Figure 10 The diagram illustrates a possible hardware structure of a communication device 1000 provided in an embodiment of this application. The communication device 1000 may include a communication interface 1004 and at least one processor 1002. Optionally, it may also include a bus 1003. Further optionally, it may include at least one memory 1001, wherein the memory 1001, processor 1002, and communication interface 1004 can be connected via the bus 1003.

[0241] The memory 1001 provides storage space, which can store data such as the operating system and computer programs. The memory 1001 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0242] Processor 1002 is a module that performs arithmetic and / or logical operations. Specifically, it can be one or a combination of processing modules such as a central processing unit (CPU), graphics processing unit (GPU), microprocessor unit (MPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), complex programmable logic device (CPLD), coprocessor (assisting the CPU in completing corresponding processing and applications), and microcontroller unit (MCU). For example, processor 1002 can be used to process communication protocols and communication data.

[0243] The communication interface 1004 is used to receive and / or transmit data to external sources. Optionally, the communication interface 1004 may also include a transmitter (such as an RF transmitter, antenna, etc.) and / or a receiver coupled to the interface. For example, the communication interface 1004 may include a control circuit and an antenna. The control circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. When data needs to be transmitted wirelessly, the processor 1002 performs baseband processing on the data to be transmitted and outputs a baseband signal to the control circuit. The control circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the control circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1002. The processor 1002 converts the baseband signal back into data and processes the data.

[0244] In one possible implementation, the control circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the control circuitry and antenna can be arranged in a remote manner, independent of the communication device.

[0245] In one design, the communication device 1000 can be used to perform the aforementioned... Figure 6 The embodiments shown illustrate the functions of the network devices. For details, please refer to the above. Figure 6 The relevant descriptions of network equipment will not be elaborated here.

[0246] In another design, the communication device 1000 can be used to perform the aforementioned... Figure 6 The embodiments shown illustrate the functions of the terminal device. For details, please refer to the above. Figure 6 The relevant descriptions of the terminal devices will not be elaborated here.

[0247] In one possible design, memory 1001 may store instructions, which may be computer programs. These computer programs run on processor 1002 and cause communication device 1000 to perform operations performed by the terminal device or network device in any of the above method embodiments. For details, please refer to the above description. Figure 6 The relevant descriptions in the document will not be repeated here.

[0248] It should be noted that, Figure 10 The communication device 1000 shown is merely one implementation of the embodiments of this application. In actual applications, the communication device 1000 may include more or fewer components, which is not limited here.

[0249] It should be understood that the transmission in the embodiments of this application can be direct or indirect. Direct transmission means that one device or module directly sends information / data to the corresponding device or module, while indirect transmission means that one device or module sends information / data to the corresponding device or module through other devices or modules.

[0250] In this application, the words "exemplarily," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "example" is intended to present the concept in a concrete manner.

[0251] In this embodiment, "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 specific implementation, 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. Simultaneously, 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. Furthermore, the specific instruction method can also be various combinations of the above-mentioned instruction methods.

[0252] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" can refer to the fact that the device (e.g., a terminal device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., a terminal device) to have a judgment action when implementing it, nor do they mean that there are other limitations.

[0253] To facilitate a clear description of the technical solutions in 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" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0254] Unless otherwise specified or there is a logical conflict, the terms and / or descriptions in different embodiments of this application are consistent and can be referenced and combined with each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0255] Obviously, the embodiments described above are only some embodiments of this application, and not all embodiments. The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily indicate the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described herein can be combined with other embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application. The terms "first," "second," "third," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects and are not used to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, it may include a series of steps or units, or optionally, steps or units not listed, or optionally other steps or units inherent to these processes, methods, products, or devices. It is also understandable that, for an architecture with multiple devices or modules, if one device or module generates a piece of information and another device or module uses that information, there are multiple ways for the other device to obtain that information. For example, the device or module that generated the information may send the information directly to the device or module that used the information (equivalent to direct sending), or the device or module that generated the information may send the information to the device or module that used the information through other devices or modules (equivalent to indirect sending).

[0256] It is understood that the accompanying drawings show only the parts relevant to this application and not all of them. It should be understood that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subroutine, etc.

[0257] The terms “component,” “module,” “system,” “unit,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a unit can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or distributed between two or more computers. Furthermore, these units can be executed from various computer-readable media on which various data structures are stored. For example, a unit can communicate via local and / or remote processes based on signals having one or more data packets (e.g., data from a second unit interacting with another unit between a local system, a distributed system, and / or a network; for example, the Internet interacting with other systems via signals).

[0258] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to network devices, the method includes: Send first information, the first information is used to configure the first channel sounding reference signal (SRS) port, the first SRS port corresponds to the first orthogonal mask (OCC), and the number of time domain units of the first OCC is N, where N is a positive integer; Receive the first SRS sent through the first SRS port; Send a second message, which is used to instruct the OCC corresponding to the first SRS port to switch to the second OCC, wherein the number of time domain units of the second OCC is M, and M is a positive integer different from N; Receive the second SRS sent through the first SRS port.

2. The method according to claim 1, characterized in that, The method further includes: Send a third message, which is used to configure a second SRS port, the second SRS port corresponds to a third OCC, the number of time domain units of the third OCC is N, the third OCC is orthogonal to the first OCC, and the non-OCC resources corresponding to the first SRS port and the second SRS port are the same. Receive a third SRS sent through the second SRS port, wherein the third SRS is the same as the non-OCC resource corresponding to the first SRS; Send a fourth message, which is used to indicate that the OCC corresponding to the second SRS port is switched to the fourth OCC. The fourth OCC has M time domain units and is orthogonal to the second OCC. Receive a fourth SRS sent through the second SRS port, wherein the fourth SRS has the same non-OCC resource as the second SRS, and the non-OCC resource includes time and frequency resources.

3. The method according to claim 2, characterized in that, The first OCC and the third OCC belong to the first OCC code group, which includes X OCCs, each with N time-domain units, and the X OCCs are mutually orthogonal. The second OCC and the fourth OCC belong to the second OCC code group, which includes Y OCCs, each with M time-domain units, and the Y OCCs are mutually orthogonal. X and Y are integers greater than 2.

4. The method according to claim 3, characterized in that, The OCC corresponding to the paired port is the OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

5. The method according to claim 3 or 4, characterized in that, The first OCC code group and the second OCC code group are OCC code groups in a predefined table. The predefined table includes multiple OCC code groups. The OCCs in the same code group in the predefined table have the same number of time-domain units, and the OCCs in the same code group are mutually orthogonal.

6. The method according to any one of claims 3-5, characterized in that, When N is 2 and M is 1, the first code group includes [+1+1] and [+1-1], and the second code group includes [1 0] and [0 1]. When N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1-1-1], [+1-1+1-1] and [+1-1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [0 0 1 0] and [0 0 0 1]; When N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1+1-1]. The second code group includes [1 0 0 0 0 0 0 0], [0 1 0 00 0 0 0], [0 0 1 0 0 00 0], [0 ... [1 0 0 0], [0 0 0 0 0 1 00], [0 0 0 0 0 0 1 0] and [0 0 0 0 0 0 1].

7. The method according to claim 2, characterized in that, The first OCC and the third OCC belong to the first OCC code group, which includes X OCCs. The number of time-domain units of the X OCCs is N, and the X OCCs are orthogonal to each other by a length of N. The first OCC code group includes multiple sub-code groups. The fifth OCC in the first sub-code group is composed of multiple L-length sub-codes. The multiple L-length sub-codes are orthogonal to the corresponding L-length portions of the OCCs in the remaining sub-code groups. The multiple L-length sub-codes include the second OCC and the fourth OCC. The first sub-code group is any one of the multiple sub-code groups. The first OCC and the third OCC belong to the first sub-code group, and L is an integer greater than or equal to 2.

8. The method according to claim 7, characterized in that, The paired ports corresponding to the first subcode group have an association relationship. The association relationship is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired ports refer to SRS ports with the same non-OCC resources. The non-OCC resources include time and frequency resources.

9. The method according to claim 7 or 8, characterized in that, The first OCC code group is an OCC code group in a predefined table.

10. The method according to any one of claims 7-9, characterized in that, When N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1-1-1], [+1-1+1-1] and [+1-1-1+1], and the first code group includes sub-code groups [+1+1+1+1], [+1+1-1-1], and sub-code groups [+1-1+1-1] and [+1-1-1+1]; When N is 8, M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1+1-1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1-1+1-1], and [+1-1-1+1+1-1-1-1+1], [+1-1-1+1-1+1-1+1+1]; When N is 8 and M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1] and [+1-1-1+1-1+1+1-1] The first code group includes subcode groups [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], and subcode groups [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1], [+1-1-1+1-1+1+1-1].

11. The method according to any one of claims 1-10, characterized in that, The number of time-domain units of the OCC corresponding to the SRS port is related to the signal quality information associated with the SRS port. Before sending the second information, the method further includes: The second OCC is determined based on the signal quality information associated with the first SRS port.

12. The method according to claim 11, characterized in that, The signal quality information is defined with multiple threshold ranges, and different threshold ranges correspond to different numbers of time-domain units (OCCs). Determining the second OCC based on the signal quality information associated with the first SRS port includes: Determine a first threshold interval corresponding to the signal quality information associated with the first SRS port, wherein the plurality of threshold intervals include the first threshold interval, and the first threshold interval corresponds to an OCC with a time domain unit number of M; The second OCC is determined based on the first threshold range.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: In the event of a collision between the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) and the time-domain resources corresponding to the first paired port, a fifth message is sent. The fifth message is used to indicate that the time-domain resources in the collision should be abandoned and SRS should be sent through the SRS port in the first paired port. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

14. The method according to any one of claims 1-12, characterized in that, The method further includes: In the event of a partial collision between the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) and the time-domain resources corresponding to the first paired port, a sixth and a seventh message are transmitted. The sixth message is used to instruct that the time-domain resources in the non-collision portion be transmitted via the first part of the SRS port in the first paired port. The seventh message is used to instruct that the time-domain resources in the collision portion and the time-domain resources in the non-collision portion be abandoned and transmitted via the second part of the SRS port in the first paired port. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

15. A communication method, characterized in that, Applied to a terminal device, the method includes: Receive first information, the first information is used to configure a first channel sounding reference signal (SRS) port, the first SRS port corresponds to a first orthogonal mask (OCC), and the number of time-domain units of the first OCC is N, where N is a positive integer; Send the first SRS through the first SRS port; Receive second information, which is used to indicate that the OCC corresponding to the first SRS port is switched to the second OCC, and the number of time domain units of the second OCC is M, where M is a positive integer different from N; The second SRS is sent through the first SRS port.

16. The method according to claim 15, characterized in that, The first OCC belongs to the first OCC code group, which includes X OCCs, each with N time-domain units, and the X OCCs are mutually orthogonal. The second OCC belongs to the second OCC code group, which includes Y OCCs, each with M time-domain units, and the Y OCCs are mutually orthogonal. X and Y are integers greater than 2.

17. The method according to claim 16, characterized in that, The OCC corresponding to the paired port is the OCC in the same OCC code group, and the paired port refers to the SRS port with the same non-OCC resource.

18. The method according to claim 16 or 17, characterized in that, The first OCC code group and the second OCC code group are OCC code groups in a predefined table. The predefined table includes multiple OCC code groups. The OCCs in the same code group in the predefined table have the same number of time-domain units, and the OCCs in the same code group are mutually orthogonal.

19. The method according to any one of claims 16-18, characterized in that, When N is 2 and M is 1, the first code group includes [+1+1] and [+1-1], and the second code group includes [1 0] and [0 1]. When N is 4 and M is 1, the first code group includes [+1+1+1+1], [+1+1-1-1], [+1-1+1-1] and [+1-1-1+1], and the second code group includes [1 0 0 0], [0 1 0 0], [0 0 1 0] and [0 0 0 1]; When N is 8 and M is 1, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1+1-1]. The second code group includes [1 0 0 0 0 0 0 0], [0 1 0 00 0 0 0], [0 0 1 0 0 00 0], [0 ... [1 0 0 0], [0 0 0 0 0 1 00], [0 0 0 0 0 0 1 0] and [0 0 0 0 0 0 1].

20. The method according to claim 15, characterized in that, The first OCC belongs to the first OCC code group, which includes X OCCs. The number of time-domain units of the X OCCs is N. The X OCCs are orthogonal to each other by a length of N. The first OCC code group includes multiple sub-code groups. The fifth OCC in the first sub-code group is composed of multiple L-length sub-codes. The multiple L-length sub-codes are orthogonal to the corresponding L-length portions of the OCCs in the remaining sub-code groups. The multiple L-length sub-codes include the second OCC. The first sub-code group is any one of the multiple sub-code groups. The first OCC belongs to the first sub-code group. L is an integer greater than or equal to 2.

21. The method according to claim 20, characterized in that, The paired ports corresponding to the first subcode group have an association relationship. The association relationship is that the paired ports corresponding to the first subcode group simultaneously use the OCC in the first subcode group or simultaneously use multiple L-length subcodes corresponding to the fifth OCC. The paired ports refer to SRS ports with the same non-OCC resources. The non-OCC resources include time and frequency resources.

22. The method according to claim 20 or 21, characterized in that, The first OCC code group is an OCC code group in a predefined table.

23. The method according to any one of claims 20-22, characterized in that, When N is 4 and M and L are 2, the first code group includes [+1+1+1+1], [+1+1-1-1], [+1-1+1-1] and [+1-1-1+1], and the first code group includes sub-code groups [+1+1+1+1], [+1+1-1-1], and sub-code groups [+1-1+1-1] and [+1-1-1+1]; When N is 8, M and L are 4, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], and [+1-1-1+1-1+1+1-1]. The first code group includes subcode groups [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1-1+1-1], and [+1-1-1+1+1-1-1-1+1], [+1-1-1+1-1+1-1+1+1]; When N is 8 and M and L are 2, the first code group includes [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1] and [+1-1-1+1-1+1+1-1] The first code group includes subcode groups [+1+1+1+1+1+1+1+1], [+1+1+1+1-1-1-1-1], [+1+1-1-1+1+1-1-1], [+1+1-1-1-1-1+1+1], and subcode groups [+1-1+1-1+1-1+1-1], [+1-1+1-1-1+1-1+1], [+1-1-1+1+1-1-1+1], [+1-1-1+1-1+1-1+1], [+1-1-1+1-1+1+1-1].

24. The method according to any one of claims 15-23, characterized in that, The method further includes: In the event of a collision between the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) and the time-domain resources corresponding to the first paired port, a fifth message is received. The fifth message is used to indicate that the time-domain resources involved in the collision should be abandoned so that SRS can be transmitted through the SRS port in the first paired port. The first paired port includes multiple SRS ports, and the multiple SRS ports include the first SRS port. The non-OCC resources corresponding to the multiple SRS ports are the same, and the non-OCC resources include time-frequency resources.

25. The method according to any one of claims 15-23, characterized in that, The method further includes: In the event of a partial collision between the time-domain resources corresponding to the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH) and the time-domain resources corresponding to the first paired port, a sixth message is received. This sixth message instructs that the uncollided portion of the time-domain resources be used to transmit SRS through the first portion of the SRS port in the first paired port; or... The seventh message is received, which is used to indicate that the time-domain resources in the collision and the time-domain resources in the non-collision part are abandoned and sent through the second part of the SRS port in the first pairing port. The first pairing port includes multiple SRS ports, the multiple SRS ports include the first SRS port, and the non-OCC resources corresponding to the multiple SRS ports are the same, the non-OCC resources include time-frequency resources.

26. A communication system, characterized in that, The method includes network devices and terminal devices, wherein the network devices are used to implement the method according to any one of claims 1-14, and the terminal devices are used to implement the method according to any one of claims 15-25.

27. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1-25.

28. A communication device, characterized in that, The device includes a processor and a transceiver, the transceiver being used to send and receive information, and the processor being used to enable the communication device to implement the method as described in any one of claims 1-25.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or computer instructions that are executed by a processor to implement the method as described in any one of claims 1-25.

30. A computer program product, characterized in that, The computer program product includes computer program code or computer instructions, which, when executed, implement the method described in any one of claims 1-25.

Images