Communication method, apparatus, device, system and storage medium

Abstract

This disclosure relates to a communication method, apparatus, device, system, and storage medium. The method includes: a network device configuring a Sounding Reference Signal (SRS) resource set for codebook transmission to a terminal; the SRS resource set for codebook transmission includes at least one SRS resource; the network device receiving SRS for codebook transmission transmitted by the terminal on the at least one SRS resource; the network device determining, based on the SRS for codebook transmission, N PUSCH frequency hopping resources and the corresponding Transmission Precoding Matrix Indicators (TPMIs) in the Physical Uplink Shared Channel (PUSCH) frequency domain resources; where N is an integer greater than or equal to 2; and the network device sending Downlink Control Information (DCI) to the terminal, the DCI being used for PUSCH scheduling, and the DCI including the TPMIs corresponding to the N PUSCH frequency hopping resources. By implementing embodiments of this disclosure, uplink throughput can be improved, enhancing the user experience.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and more particularly to a communication method, apparatus, device, system, and storage medium. Background Technology

[0002] As terminals increasingly support MIMO (Multiple-Input Multiple-Output), meaning they support multiple antennas for transmission, it becomes possible for terminals to transmit via precoding. PUSCH (Physical Uplink Shared Channel) precoding is also being standardized. In related technologies, communication systems support codebook-based PUSCH transmission, i.e., PUSCH precoding transmission. However, current codebook-based PUSCH transmission suffers from low throughput and other issues. Summary of the Invention

[0003] This disclosure provides a communication method, apparatus, device, system, and storage medium.

[0004] In a first aspect, embodiments of this disclosure provide a communication method executed by a network device, the method comprising: configuring a Sounding Reference Signal (SRS) resource set for codebook transmission for a terminal; the SRS resource set for codebook transmission including at least one SRS resource; receiving SRS for codebook transmission transmitted by the terminal on the at least one SRS resource; determining, based on the SRS for codebook transmission, N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and a Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; wherein N is an integer greater than or equal to 2; and sending Downlink Control Information (DCI) to the terminal, the DCI being used to schedule the PUSCH, the DCI including the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0005] In the above embodiments, the network device determines the N PUSCH frequency hopping resources and the corresponding TPMIs of each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources based on the SRS sent by the terminal for codebook transmission. This facilitates the terminal to perform PUSCH precoding based on the codebooks corresponding to the N TPMIs. This allows the network device to schedule PUSCH to use frequency hopping transmission within the time slot and to use N TPMIs within the PUSCH scheduling bandwidth. This can well adapt to the fading channel in high-frequency scenarios (also called strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0006] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: sending indication information to the terminal, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0007] In conjunction with some embodiments of the first aspect, in some embodiments, determining the N PUSCH frequency hopping resources and the corresponding Transmission Precoding Matrix Indicator (TPMI) of each of the N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources according to the SRS for codebook transmission includes: dividing the uplink partial bandwidth (BWP) into M bandwidth segments; where M is an integer greater than or equal to N; and performing PUSCH frequency domain resource allocation and TPMI measurement within the M bandwidth segments according to the SRS for codebook transmission to obtain the N PUSCH frequency hopping resources and the corresponding TPMI of each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

[0008] In the above embodiments, the network device can segment the uplink BWP (such as PUSCH scheduling bandwidth), and perform PUSCH frequency domain resource allocation and TPMI measurement on each segment. This allows the network device to obtain N PUSCH frequency hopping resources and the corresponding TPMIs for each of the N PUSCH frequency hopping resources. This enables the network device to schedule PUSCH to use frequency hopping transmission within the time slot and use N TPMIs within the PUSCH scheduling bandwidth. This can well adapt to the fading channel in high-frequency scenarios (also called strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0009] In conjunction with some embodiments of the first aspect, in some embodiments, both N and M are 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the step of allocating PUSCH frequency domain resources and measuring TPMI within the M-segment bandwidth according to the SRS for codebook transmission, to obtain the N PUSCH frequency hopping resources and their respective TPMIs in the PUSCH frequency domain resources, includes: according to the SRS for codebook transmission, in Within the first bandwidth segment, allocate the first PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the first PUSCH frequency hopping resource to obtain the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource; according to the SRS used for codebook transmission, allocate the second PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the second PUSCH frequency hopping resource within the second bandwidth segment to obtain the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource.

[0010] In the above embodiment, the uplink BWP (such as PUSCH scheduling bandwidth) can be directly divided into two segments. PUSCH frequency domain resource allocation and TPMI measurement are performed on each segment, thereby obtaining two PUSCH frequency hopping resources and the corresponding TPMIs for each of the two PUSCH frequency hopping resources. This allows the network device to schedule PUSCH to use frequency hopping transmission within the time slot and use two TPMIs within the PUSCH scheduling bandwidth. This can well adapt to the fading channel in high-frequency scenarios (also called strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0011] In conjunction with some embodiments of the first aspect, in some embodiments, N is 2, and M is greater than N; the step of performing PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth according to the SRS for codebook transmission to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources includes: performing PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth according to the SRS for codebook transmission to obtain the M frequency hopping resources and the TPMI corresponding to each of the M frequency hopping resources; determining the N PUSCH frequency hopping resources from the M frequency hopping resources; and determining the TPMI corresponding to each of the N PUSCH frequency hopping resources from the TPMI corresponding to each of the M frequency hopping resources.

[0012] In the above embodiment, the uplink BWP (such as PUSCH scheduling bandwidth) can be directly divided into M (integer greater than 2) segments. PUSCH frequency domain resource allocation and TPMI measurement are performed on each segment to obtain M frequency hopping resources and their corresponding TPMIs in the PUSCH frequency domain resources. Two PUSCH frequency hopping resources are selected from these M frequency hopping resources, and two TPMIs corresponding to each of the M PUSCH frequency hopping resources are selected from their respective TPMIs. This allows the network device to schedule PUSCH using frequency hopping transmission within the time slot and use two TPMIs within the PUSCH scheduling bandwidth. This can well adapt to the fading channel in high-frequency scenarios (also called strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0013] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining an SRS resource indicator (SRI) and / or an RI corresponding to the PUSCH frequency domain resource based on the SRS used for codebook transmission; wherein the DCI further includes the RI and / or the SRI.

[0014] In the above embodiments, the network device sends RI to the terminal, which enables the terminal to perform PUSCH precoding based on the codebooks corresponding to RI and N TPMIs. This allows the network device to schedule PUSCH to use frequency hopping transmission within the time slot and to use N TPMIs within the PUSCH scheduling bandwidth. This can well adapt to the fading channel in high-frequency scenarios (also called strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0015] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a PUSCH sent by the terminal on the PUSCH frequency domain resource; wherein the PUSCH sent by the terminal is sent to the network device by the terminal using a frequency hopping mode of in-slot frequency hopping based on the SRI and / or the TPMI.

[0016] In a second aspect, embodiments of this disclosure provide a communication method, the method comprising: receiving a set of sounding reference signals (SRS) resources configured by a network device for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource; transmitting an SRS for codebook transmission to the network device on the at least one SRS resource; the SRS for codebook transmission being used by the network device to determine N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and a Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; wherein N is an integer greater than or equal to 2; and receiving downlink control information (DCI) transmitted by the network device, the DCI being used to schedule the PUSCH, the DCI including the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0017] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving indication information sent by the network device, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0018] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI further includes a Reference Indicator (RI) and / or an SRS Resource Indicator (SRI); wherein the RI and / or SRI are determined by the network device based on the SRS used for codebook transmission.

[0019] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: sending PUSCH to the network device on the PUSCH frequency domain resources using a frequency hopping mode of in-slot frequency hopping based on the SRI and / or the TPMI.

[0020] Thirdly, embodiments of this disclosure provide a communication apparatus, comprising: a processing module configured to configure a probe reference signal (SRS) resource set for codebook transmission for a terminal; the SRS resource set for codebook transmission includes at least one SRS resource; a transceiver module configured to receive SRS for codebook transmission transmitted by the terminal on the at least one SRS resource; the processing module is further configured to determine, based on the SRS for codebook transmission, N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and a Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; wherein N is an integer greater than or equal to 2; the transceiver module is further configured to send downlink control information (DCI) to the terminal, the DCI being used to schedule the PUSCH, the DCI including the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0021] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to: send indication information to the terminal, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0022] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is specifically used to: divide the uplink bandwidth BWP into M bandwidth segments; where M is an integer greater than or equal to N; according to the SRS for codebook transmission, perform PUSCH frequency domain resource allocation and TPMI measurement within the M bandwidth segments to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

[0023] In conjunction with some embodiments of the third aspect, in some embodiments, both N and M are 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the processing module is specifically used to: allocate the first PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the first PUSCH frequency hopping resource within the first segment bandwidth according to the SRS for codebook transmission, thereby obtaining the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource; and allocate the second PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the second PUSCH frequency hopping resource within the second segment bandwidth according to the SRS for codebook transmission, thereby obtaining the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource.

[0024] In conjunction with some embodiments of the third aspect, in some embodiments, N is 2, and M is greater than N; the processing module is specifically used to: according to the SRS for codebook transmission, perform PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth to obtain M frequency hopping resources in the PUSCH frequency domain resources and the TPMI corresponding to each of the M frequency hopping resources; determine the N PUSCH frequency hopping resources from the M frequency hopping resources; and determine the TPMI corresponding to each of the N PUSCH frequency hopping resources from the TPMI corresponding to each of the M PUSCH frequency hopping resources.

[0025] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is further configured to: determine the SRS resource indicator SRI and / or the RI corresponding to the PUSCH frequency domain resource based on the SRS for codebook transmission; wherein the DCI further includes the RI and / or the SRI.

[0026] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to: receive a PUSCH sent by the terminal on the PUSCH frequency domain resource; wherein the PUSCH sent by the terminal is sent to the network device by the terminal using a frequency hopping mode of in-slot frequency hopping based on the SRI and / or the TPMI.

[0027] Fourthly, embodiments of this disclosure also provide a communication apparatus, comprising: a transceiver module, configured to receive a set of probe reference signals (SRS) for codebook transmission configured by a network device; the SRS resource set for codebook transmission includes at least one SRS resource; the transceiver module is further configured to transmit SRS for codebook transmission to the network device on the at least one SRS resource; the SRS for codebook transmission is used by the network device to determine N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; the N is an integer greater than or equal to 2; the transceiver module is further configured to receive downlink control information (DCI) transmitted by the network device, the DCI being used to schedule the PUSCH, the DCI including the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0028] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to: receive indication information sent by the network device, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0029] In conjunction with some embodiments of the fourth aspect, in some embodiments, the DCI further includes a Reference Indicator (RI) and / or an SRS Resource Indicator (SRI); wherein the RI and / or the SRI are determined by the network device based on the SRS used for codebook transmission.

[0030] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to: transmit PUSCH to the network device on the PUSCH frequency domain resources using a frequency hopping mode of in-slot frequency hopping based on the SRI and / or the TPMI.

[0031] Fifthly, embodiments of this disclosure also propose a communication system, comprising:

[0032] A communication device configured to perform the communication method described in the first aspect above;

[0033] A communication device is configured to perform the communication method described in the second aspect above.

[0034] In a sixth aspect, embodiments of this disclosure also provide a communication device, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform an optional implementation of the first aspect described above.

[0035] In a seventh aspect, embodiments of this disclosure also provide a communication device, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform an optional implementation of the second aspect described above.

[0036] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform optional implementations of the first and second aspects described above.

[0037] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the optional implementations of the first, second, third, fourth, fifth, and sixth aspects.

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

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

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

[0041] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0042] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

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

[0044] Figure 2 This is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0045] Figure 3 This is an example diagram of an uplink BWP segmentation shown according to an embodiment of the present disclosure.

[0046] Figure 4A This is a flowchart illustrating a communication method according to an exemplary embodiment.

[0047] Figure 4B This is a flowchart illustrating a communication method according to an exemplary embodiment.

[0048] Figure 5A This is a flowchart illustrating a communication method according to an exemplary embodiment.

[0049] Figure 5B This is a flowchart illustrating a communication method according to an exemplary embodiment.

[0050] Figure 6 This is an interactive schematic diagram illustrating a communication method according to an exemplary embodiment.

[0051] Figure 7A This is a schematic diagram of the structure of the network device proposed in the embodiments of this disclosure;

[0052] Figure 7B This is a schematic diagram of the terminal structure proposed in the embodiments of this disclosure;

[0053] Figure 8A This is a schematic diagram of the structure of the communication device 8100 proposed in the embodiments of this disclosure;

[0054] Figure 8BThis is a schematic diagram of the structure of the chip 8200 proposed in the embodiments of this disclosure. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

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

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

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

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

[0060] In the embodiments disclosed herein, "multiple" refers to two or more.

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

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

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

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

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

[0066] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain. In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "when...", "if...", etc., can be used interchangeably.

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

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

[0069] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission and / or reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cellgroup," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0070] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

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

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

[0073] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of this disclosure. The communication system may include, but is not limited to, a network device and a terminal. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminals may be included. Figure 1 The communication system 100 shown is exemplified by including a network device 101 and a terminal 102.

[0074] In some embodiments, the terminal 102 described herein can be a user-side entity used for receiving or transmitting signals, such as a mobile phone. It can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal can be at least one of the following: a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of this disclosure do not limit the specific technology or device form used in the terminal.

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

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

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

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

[0079] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0080] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0081] It should be noted that as terminals gradually support MIMO (Multiple-Input Multiple-Output), i.e., multi-antenna transmission, it becomes possible for terminals to transmit via precoding, and PUSCH (Physical Uplink Shared Channel) precoding is also being standardized. In related technologies, communication systems support codebook-based PUSCH transmission, i.e., PUSCH precoding transmission. Current protocols only standardize full-band (e.g., PUSCH scheduling bandwidth) PUSCH precoding, meaning that within the PUSCH scheduling bandwidth, the same DCI (Downlink Control Information) is used to transmit the same TPMI (Transmit Precoding Matrix Indicator) and RI (Rank Indicator). Even if PUSCH uses intra-slot frequency hopping for transmission, the same TPMI is used for both frequency hopping segments. The network device instructs the terminal with information such as TPMI, and the terminal uses the codebook corresponding to the TPMI for precoding. All bandwidths use the same TPMI codebook, and different frequency hopping also use the same TPMI codebook. The base network device performs PUSCH reception and demodulation based on the full-band precoding assumption.

[0082] In high-frequency scenarios (also known as strong-frequency scenarios), the fading characteristics at different frequency locations may be different. It is based on this consideration that network devices schedule PUSCH to use intra-slot frequency hopping for transmission. However, using the same TPMI codebook for all bandwidths (i.e., PUSCH scheduling bandwidth) cannot be well adapted to this fading channel, affecting the user experience.

[0083] To address this, embodiments of this disclosure propose a communication method and apparatus. The network device can determine N PUSCH frequency hopping resources and their corresponding TPMIs based on the SRS sent by the terminal for codebook transmission. This facilitates PUSCH precoding by the terminal based on the codebooks corresponding to the N TPMIs. Furthermore, the network device schedules PUSCH transmission within time slots and utilizes N TPMIs within the PUSCH scheduling bandwidth. This effectively adapts to fading channels in high-frequency scenarios (also known as strong-frequency scenarios), thereby improving uplink throughput and enhancing user experience.

[0084] Figure 2 This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 2 As shown, the communication method disclosed herein can be applied to a communication system 100, and the method includes, but is not limited to, the following steps.

[0085] In step S2101, network device 101 sends instruction information to terminal 102.

[0086] In some embodiments, the aforementioned indication information may be sent from network device 101 to terminal 102, and correspondingly, terminal 102 receives the indication information sent by network device 101. In some embodiments, terminal 102 may be a chip or a mobile terminal. In some embodiments, terminal 102 in this document may be a user-side entity used for receiving or transmitting signals, such as a mobile phone. It may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal can be at least one of the following: a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of this disclosure do not limit the specific technology or device form used in the terminal.

[0087] In some embodiments, the above indication information is used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0088] In some embodiments, the aforementioned indication information may be RRC (Radio Resource Control) signaling, MAC (Medium Access Control) CE (control element), or DCI. In some embodiments, the aforementioned indication information may be included in RRC (Radio Resource Control) signaling, MAC (Medium Access Control) CE (control element), or DCI. For example, network device 101 may indicate through RRC signaling, MAC CE, or DCI that the frequency hopping mode used by PUSCH is intra-slot frequency hopping.

[0089] In step S2102, network device 101 configures an SRS (Sounding Reference Signal) resource set for codebook transmission for terminal 102.

[0090] In some embodiments, the SRS resource set for codebook transmission described above may include at least one SRS resource.

[0091] For example, network device 101 can send SRS resource configuration to terminal 102. Correspondingly, the terminal receives the SRS resource configuration sent by network device 101. The SRS resource configuration includes an SRS resource set for codebook transmission, which includes one or more SRS resources. For example, the aforementioned SRS resource set for codebook transmission can be one or more. That is, network device 101 can configure one SRS resource set for codebook transmission for terminal 102, or it can configure multiple SRS resource sets for codebook transmission for terminal 102. Each SRS resource set for codebook transmission can include at least one SRS resource.

[0092] In step S2103, terminal 102 sends an SRS for codebook transmission on at least one SRS resource.

[0093] In some embodiments, the SRS for codebook transmission described above may be sent by terminal 102 to network device 101. For example, terminal 102 sends SRS for codebook transmission to network device 101 on at least one SRS resource, and correspondingly, network device 101 receives the SRS for codebook transmission sent by terminal on at least one SRS resource.

[0094] In some embodiments, the SRS for codebook transmission sent by the terminal 102 can be used by the network device 101 to estimate the uplink (UL) channel, perform PUSCH resource allocation, and TPMI measurement.

[0095] In step S2104, network device 101 divides the uplink BWP (Bandwidth Part) into M bandwidth segments.

[0096] For example, network device 101 receives the SRS for codebook transmission sent by terminal 102, and estimates the uplink channel on the SRS for codebook transmission (i.e., the SRS resources sent by the terminal) to facilitate PUSCH resource allocation and TPMI measurement. When performing PUSCH resource allocation and TPMI measurement, network device 101 can divide the uplink BWP into M bandwidth segments. The uplink BWP can be understood as the PUSCH scheduling bandwidth, for example, it can be the uplink portion of the bandwidth configured by network device 101 for terminal 102 for PUSCH scheduling. This uplink BWP can be included in the SRS resource configuration. M can be an integer greater than or equal to 2.

[0097] For example, when terminal 102 sends multiple SRSs for codebook transmission, the network device can select the best SRS from the SRSs sent by the terminal and estimate the uplink channel on the best SRS.

[0098] In some embodiments, network device 101 can divide the uplink BWP into M bandwidth segments based on network implementation. For example, network device 101 can divide the uplink BWP into M bandwidth segments based on network policies. In one possible implementation, network device 101 can divide the uplink BWP into two bandwidth segments, such as a first bandwidth segment and a second bandwidth segment. The lengths of the first bandwidth segment and the second bandwidth segment can be the same or different, or the first bandwidth segment and the second bandwidth segment can partially overlap. In another possible implementation, network device 101 can divide the uplink BWP into M (e.g., an integer greater than 2, such as M=3) bandwidth segments. Alternatively, network device 101 can also divide the uplink BWP into other numbers of bandwidth segments; this disclosure does not limit this, nor will it elaborate further.

[0099] In step S2105, network device 101 performs PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth according to the SRS used for codebook transmission, and obtains the TPMI corresponding to each of the N PUSCH frequency hopping resources and the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

[0100] In some embodiments, N is an integer greater than or equal to 2, and M is an integer greater than or equal to N.

[0101] In some embodiments, N and M are both 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the network device 101 performs PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth according to the SRS used for codebook transmission, and obtains the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources. Possible implementations include: the network device 101 allocates the first PUSCH frequency hopping resource in the PUSCH frequency domain resources and measures the TPMI corresponding to the first PUSCH frequency hopping resource within the first segment bandwidth according to the SRS used for codebook transmission, and obtains the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource; according to the SRS used for codebook transmission, allocates the second PUSCH frequency hopping resource in the PUSCH frequency domain resources and measures the TPMI corresponding to the second PUSCH frequency hopping resource within the second segment bandwidth, and obtains the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource. The method of allocating PUSCH scheduling resource positions (such as scheduling RB positions) and measuring the corresponding TMPIs in each bandwidth segment according to the SRS used for codebook transmission can be implemented using existing allocation and measurement methods. In other words, the method of allocating PUSCH scheduling resource positions and measuring the corresponding TMPIs in each bandwidth segment according to the SRS used for codebook transmission can be implemented using existing allocation and measurement methods. This disclosure does not limit this, nor will it elaborate further.

[0102] For example, network device 101 can directly divide the uplink BWP (such as PUSCH scheduling bandwidth) into two segments, and perform PUSCH frequency domain resource allocation and TPMI measurement on each segment, thereby obtaining two PUSCH frequency hopping resources and the TPMI corresponding to each of the two PUSCH frequency hopping resources, so that the network device schedules PUSCH to use frequency hopping transmission within the time slot and uses two TPMIs within the PUSCH scheduling bandwidth.

[0103] In some embodiments, N can be 2, and M is greater than N. The possible implementation of the network device 101 performing PUSCH frequency domain resource allocation and TPMI measurement within an M-segment bandwidth based on the SRS used for codebook transmission to obtain N PUSCH frequency hopping resources and their respective TPMIs includes: the network device 101 performing PUSCH frequency domain resource allocation and TPMI measurement within an M-segment bandwidth based on the SRS used for codebook transmission to obtain M frequency hopping resources and their respective TPMIs; the network device 101 determining N PUSCH frequency hopping resources from the M frequency hopping resources, and determining the TPMIs corresponding to each of the N PUSCH frequency hopping resources from the TPMIs corresponding to each of the M frequency hopping resources.

[0104] For example, network device 101 can directly divide the uplink BWP (such as PUSCH scheduling bandwidth) into M (an integer greater than 2) segments, perform PUSCH frequency domain resource allocation and TPMI measurement on each segment, obtain M frequency hopping resources and their corresponding TPMIs in the PUSCH frequency domain resources, select 2 PUSCH frequency hopping resources from the M frequency hopping resources, and select the TPMIs corresponding to the 2 PUSCH frequency hopping resources from the TPMIs corresponding to the M frequency hopping resources, so that the network device schedules PUSCH frequency hopping transmission within the time slot and uses two TPMIs within the PUSCH scheduling bandwidth. For example, network device 101 can be implemented based on the network to select 2 PUSCH frequency hopping resources from the M frequency hopping resources, and can be implemented based on the network to select the TPMIs corresponding to the 2 PUSCH frequency hopping resources from the TPMIs corresponding to the M frequency hopping resources.

[0105] It should be noted that in some embodiments, N can also be an integer greater than 2. For example, when the PUSCH can support more than 2 frequency hoppings in the future, the network device 101 can perform PUSCH frequency domain resource allocation and TPMI measurement within the M-band bandwidth according to the SRS used for codebook transmission, to obtain M frequency hopping resources in the PUSCH frequency domain resources and the TPMI corresponding to each of the M frequency hopping resources; the network device 101 determines N PUSCH frequency hopping resources from the M frequency hopping resources, and determines the TPMI corresponding to each of the N PUSCH frequency hopping resources from the TPMI corresponding to each of the M PUSCH frequency hopping resources.

[0106] It is worth noting that the aforementioned TPMI can be used for precoder selection in PUSCH, where TPMI is used for precoding indication of codebook-based uplink transmission.

[0107] In step S2106, network device 101 determines the RI corresponding to SRI and / or PUSCH frequency domain resources based on the SRS used for codebook transmission.

[0108] In some embodiments, network device 101 can also calculate the RI corresponding to the PUSCH frequency domain resources based on the SRS used for codebook transmission. N PUSCH frequency hopping resources in the PUSCH frequency domain resources correspond to one RI. For example, after receiving the aforementioned SRS for codebook transmission sent by terminal 102, network device 101 estimates the uplink channel on the aforementioned SRS for codebook transmission (i.e., the SRS resources sent by the terminal), and performs PUSCH frequency domain resource allocation and TPMI measurement within the M-band bandwidth, network device 101 can also calculate the RI corresponding to the PUSCH frequency domain resources.

[0109] In some embodiments, network device 101 may determine SRI based on SRS used for codebook transmission. For example, the SRI determined by network device 101 is an SRS resource indication used by network device 101 to calculate TPMI and / or RI.

[0110] In step S2107, network device 101 sends DCI to terminal 102.

[0111] In some embodiments, the aforementioned DCI may be sent by network device 101 to terminal 102 to provide the terminal with the necessary information to perform codebook-based uplink transmission. Accordingly, terminal 102 may receive the DCI sent by network device 101.

[0112] In some embodiments, the DCI can be used to schedule PUSCH.

[0113] In some embodiments, the DCI may include the TPMI corresponding to each of the N PUSCH frequency hopping resources. For example, step S2106 is optional; in different embodiments, one or more of these steps may be omitted or substituted.

[0114] In some embodiments, the DCI may include TPMIs corresponding to each of the N PUSCH frequency hopping resources, and also includes RI and / or SRI (SRS resource indicator). For example, the DCI may include TPMIs corresponding to each of the N PUSCH frequency hopping resources, and also includes RI. For example, if multiple resources are configured for SRS, they can be marked with SRI, then the DCI may include TPMIs corresponding to each of the N PUSCH frequency hopping resources, and also includes RI and SRI.

[0115] In step S2108, terminal 102 receives DCI and sends PUSCH on the PUSCH frequency domain resource.

[0116] In some embodiments, the PUSCH sent by terminal 102 may be sent to network device 101 by terminal 102 using a frequency hopping mode of intra-slot frequency hopping based on SRI and / or TPMI. For example, upon receiving the aforementioned DCI sent by network device 101, terminal 102 sends PUSCH to network device 101 on the PUSCH frequency domain resources, based on the SRI and / or TPMI in the DCI, using a frequency hopping mode of intra-slot frequency hopping. Correspondingly, network device 101 receives the PUSCH sent by the terminal on the PUSCH frequency domain resources.

[0117] For example, terminal 102 receives a DCI, which includes TPMIs corresponding to N PUSCH frequency hopping resources, such as TPMI 1 corresponding to the first PUSCH frequency hopping resource and TPMI 2 corresponding to the second PUSCH frequency hopping resource. The DCI may also include SRI and / or RI. Terminal 102 sends PUSCH to network device 101 using an in-slot frequency hopping mode on the PUSCH frequency domain resource, based on TPMI 1, TPMI 2, SRI and / or RI in the DCI. For example, when terminal 102 sends PUSCH on the first PUSCH frequency hopping resource, it performs PUSCH precoding based on the codebook corresponding to TPMI 1; when sending PUSCH on the second PUSCH frequency hopping resource, it performs PUSCH precoding based on the codebook corresponding to TPMI 2.

[0118] For example, such as Figure 3 As shown, network device 101 configures an SRS resource set for codebook transmission for terminal 102. Terminal 102 transmits the SRS for codebook transmission in slot N. Network device 101 will allocate the bandwidth configured for the terminal (e.g., PUSCH scheduling bandwidth, etc.) Figure 3The bandwidth (BWPSize) is divided into two segments, and the PUSCH scheduling resource location and corresponding TPMI are measured within each segment, such as TPMI 1 and TPMI 2. Network device 101 sends a DCI to terminal 102, which includes TPMI 1 and TPMI 2, and may also include RI and / or SRI. TPMI 1 may be the TPMI corresponding to the first PUSCH frequency hopping resource, and TPMI 2 may be the TPMI corresponding to the second PUSCH frequency hopping resource. Upon receiving the DCI, terminal 102 sends PUSCH to network device 101 on slot M, based on TPMI 1, TPMI 2, SRI, and / or RI in the DCI, using the frequency hopping mode of in-slot frequency hopping. For example, when terminal 102 sends PUSCH on the first PUSCH frequency hopping resource, it performs PUSCH precoding based on the codebook corresponding to TPMI 1; when sending PUSCH on the second PUSCH frequency hopping resource, it performs PUSCH precoding based on the codebook corresponding to TPMI 2.

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

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

[0121] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0122] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0123] The method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2108. For example, step S2102 + step S2103 + step S2104 + step S2105 + step S2107 can be implemented as an independent embodiment, step S2101 + step S2102 + step S2103 + step S2104 + step S2105 + step S2107 can be implemented as an independent embodiment, step S2102 + step S2103 + step S2104 + step S2105 + step S2106 + step S2107 can be implemented as an independent embodiment, step S2102 + step S2103 + step S2104 + step S2105 + step S2107 + step S2108 can be implemented as an independent embodiment, and step S2101 + step S2102 + step S2103 + step S2108 can be implemented as an independent embodiment. Steps S2104, S2105, S2106, and S2107 can be implemented as independent embodiments, as can steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, and S2108, but are not limited thereto.

[0124] In some embodiments, steps S2101 and S2102 may be performed in an alternate order or simultaneously.

[0125] In some embodiments, steps S2101, S2106, and S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0126] In some embodiments, steps S2106 and S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0127] In some embodiments, steps S2101 and S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0128] In some embodiments, steps S2101 and S2106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0129] In some embodiments, step S2108 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0130] In some embodiments, step S2106 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0131] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0132] In some embodiments, see Figure 2 Other optional implementation methods described before or after the corresponding instruction manual.

[0133] Figure 4A This is a flowchart illustrating a communication method according to an exemplary embodiment, such as... Figure 4A As shown, this method is used in network device 101 and may include, but is not limited to, the following steps.

[0134] Step S4101: Send instruction information to terminal 102.

[0135] For optional implementations of step S4101, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2101, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0136] Step S4102: Configure the SRS resource set for codebook transmission for terminal 102.

[0137] For optional implementations of step S4102, please refer to [link / reference]. Figure 2Optional implementation methods of step S2102, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0138] Step S4103: Receive terminal 102 sends SRS for codebook transmission on at least one SRS resource.

[0139] In some embodiments, the SRS for codebook transmission described above may be sent by terminal 102 to network device 101. For example, terminal 102 sends SRS for codebook transmission to network device 101 on at least one SRS resource, and correspondingly, network device 101 receives the SRS for codebook transmission sent by terminal on at least one SRS resource.

[0140] For optional implementations of step S4103, please refer to Figure 2 Optional implementation methods of step S2103, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0141] Step S4104: Divide the uplink BWP into M bandwidth segments.

[0142] For optional implementations of step S4104, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2104, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0143] Step S4105: Based on the SRS used for codebook transmission, perform PUSCH frequency domain resource allocation and TPMI measurement within the M-segment bandwidth to obtain the TPMI corresponding to each of the N PUSCH frequency hopping resources and the N PUSCH frequency hopping resources in the PUSCH frequency domain.

[0144] For optional implementations of step S4105, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2105, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0145] Step S4106: Determine the RI corresponding to the SRI and / or PUSCH frequency domain resources based on the SRS used for codebook transmission.

[0146] For optional implementations of step S4106, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2106, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0147] Step S4107: Send DCI to terminal 102.

[0148] Optional implementations of step S4107 can be found in [reference needed]. Figure 2 Optional implementation methods of step S2107, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0149] Step S4108: Receive the PUSCH sent by the receiving terminal on the PUSCH frequency domain resource.

[0150] In some embodiments, the PUSCH sent by the terminal 102 may be sent by the terminal 102 to the network device 101 using a frequency hopping mode based on SRI and / or TPMI and using intra-slot frequency hopping.

[0151] For optional implementations of step S4108, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2108, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0152] The method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4108. For example, steps S4102 + S4103 + S4104 + S4105 + S4107 can be implemented as an independent embodiment, steps S4101 + S4102 + S4103 + S4104 + S4105 + S4107 can be implemented as an independent embodiment, steps S4102 + S4103 + S4104 + S4105 + S4106 + S4107 can be implemented as an independent embodiment, steps S4102 + S4103 + S4104 + S4105 + S4107 + S4108 can be implemented as an independent embodiment, and steps S4101 + S4102 + S4103 + S4107 + S4108 can be implemented as an independent embodiment. Steps S4104, S4105, S4106, and S4107 can be implemented as independent embodiments, as can steps S4101, S4102, S4103, S4104, S4105, S4106, S4107, and S4108, but are not limited thereto.

[0153] In some embodiments, steps S4101 and S4102 may be performed in an alternate order or simultaneously.

[0154] In some embodiments, steps S4101, S4106, and S4108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0155] In some embodiments, steps S4106 and S4108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0156] In some embodiments, steps S4101 and S4108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0157] In some embodiments, steps S4101 and S4106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0158] In some embodiments, step S4108 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0159] In some embodiments, step S4106 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0160] In some embodiments, step S4101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0161] Figure 4B This is a flowchart illustrating a communication method according to an exemplary embodiment, such as... Figure 4B As shown, this method is used in network device 101 and may include, but is not limited to, the following steps.

[0162] Step S4201: Configure a probe reference signal (SRS) resource set for codebook transmission for the terminal; the SRS resource set for codebook transmission includes at least one SRS resource.

[0163] Step S4202: Receive the SRS for codebook transmission sent by the receiving terminal on at least one SRS resource.

[0164] Step S4203: Based on the SRS used for codebook transmission, determine the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources; N is an integer greater than or equal to 2.

[0165] In some embodiments, the possible implementation of determining the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources according to the SRS used for codebook transmission includes: dividing the uplink bandwidth BWP into M bandwidth segments; M is an integer greater than or equal to N; and performing PUSCH frequency domain resource allocation and TPMI measurement within the M bandwidth segments according to the SRS used for codebook transmission to obtain the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

[0166] In some embodiments, N and M are both 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the possible implementation of allocating PUSCH frequency domain resources and measuring TPMI within the M-segment bandwidth according to the SRS used for codebook transmission to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources includes: allocating the first PUSCH frequency hopping resource in the PUSCH frequency domain resources and measuring the TPMI corresponding to the first PUSCH frequency hopping resource within the first segment bandwidth according to the SRS used for codebook transmission to obtain the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource; allocating the second PUSCH frequency hopping resource in the PUSCH frequency domain resources and measuring the TPMI corresponding to the second PUSCH frequency hopping resource within the second segment bandwidth according to the SRS used for codebook transmission to obtain the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource.

[0167] In some embodiments, N is 2, and M is greater than N; the possible implementation of the above-mentioned allocation of PUSCH frequency domain resources and TPMI measurement within the M-segment bandwidth according to the SRS used for codebook transmission to obtain N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources includes: allocating PUSCH frequency domain resources and measuring TPMI within the M-segment bandwidth according to the SRS used for codebook transmission to obtain M frequency hopping resources and the TPMI corresponding to each of the M frequency hopping resources; determining N PUSCH frequency hopping resources from the M frequency hopping resources; and determining the TPMI corresponding to each of the N PUSCH frequency hopping resources from the TPMI corresponding to each of the M PUSCH frequency hopping resources.

[0168] Step S4204: Send downlink control information (DCI) to the terminal. The DCI is used to schedule PUSCH. The DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0169] In some embodiments, the network device sends an indication message to the terminal, which indicates that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0170] In some embodiments, the network device determines the RI corresponding to the SRI and / or PUSCH frequency domain resources based on the SRS used for codebook transmission; wherein, the DCI further includes the RI and / or SRS resource indication SRI.

[0171] In some embodiments, the network device receives a PUSCH sent by the terminal on the PUSCH frequency domain resource; wherein the PUSCH sent by the terminal is a frequency hopping mode sent to the network device by the terminal based on SRI and / or TPMI using in-slot frequency hopping.

[0172] The implementation of the network device-side method in this embodiment can be found in the above description. Figure 2 The relevant descriptions of the steps on the network device side are not repeated here.

[0173] Figure 5A This is a flowchart illustrating a communication method according to an exemplary embodiment, such as... Figure 5A As shown, this method is used in terminal 102 and may include, but is not limited to, the following steps.

[0174] Step S5101: Receive instruction information sent by network device 101.

[0175] In some embodiments, the above-mentioned indication information may be sent by network device 101 to terminal 102, and correspondingly, terminal 102 receives the indication information sent by network device 101.

[0176] For optional implementations of step S5101, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2101, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0177] Step S5102: Receive SRS resource configuration sent by network device 101.

[0178] In some embodiments, network device 101 may send SRS resource configuration to terminal 102. Accordingly, terminal receives the SRS resource configuration sent by network device 101. The SRS resource configuration includes an SRS resource set for codebook transmission, and the SRS resource set for codebook transmission includes one or more SRS resources.

[0179] Optional implementations of step S5102 can be found in [reference]. Figure 2 Optional implementation methods of step S2102, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0180] Step S5103: Send an SRS for codebook transmission on at least one SRS resource.

[0181] In some embodiments, the SRS for codebook transmission described above is used by the network device to determine the N PUSCH frequency hopping resources and the Transport Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources. For example, the network device obtains the TPMI by performing PUSCH frequency domain resource allocation and TPMI measurement within an M-segment bandwidth based on the SRS for codebook transmission, where the M-segment bandwidth is obtained by segmenting the uplink BWP. Optional implementations can be found in [link to optional implementations]. Figure 2 Optional implementation methods of steps S2104 and S2105, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0182] For optional implementations of step S5103, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2103, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0183] Step S5104: Receive DCI sent by network device 101.

[0184] In some embodiments, the aforementioned DCI may be sent by network device 101 to terminal 102 to provide the terminal with the necessary information to perform codebook-based uplink transmission. Accordingly, terminal 102 may receive the DCI sent by network device 101.

[0185] In some embodiments, the DCI can be used to schedule PUSCH.

[0186] In some embodiments, the DCI may include the TPMI corresponding to each of the N PUSCH frequency hopping resources. In some embodiments, the DCI may include the TPMI corresponding to each of the N PUSCH frequency hopping resources, and may also include RI and / or SRI.

[0187] For optional implementations of step S5104, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2107, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0188] Step S5105: Send PUSCH on the PUSCH frequency domain resource.

[0189] For optional implementations of step S5105, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2108, and Figure 2Other related parts in the embodiments involved will not be described in detail here.

[0190] The method involved in the embodiments of this disclosure may include at least one of steps S5101 to S5105. For example, steps S5102 + S5103 + S5104 can be implemented as an independent embodiment, steps S5101 + S5102 + S5103 + S5104 can be implemented as an independent embodiment, steps S5102 + S5103 + S5104 + S5105 can be implemented as an independent embodiment, and steps S5101 + S5102 + S5103 + S5104 + S5105 can be implemented as an independent embodiment, but are not limited thereto.

[0191] In some embodiments, steps S5101 and S5102 may be performed in an alternate order or simultaneously.

[0192] In some embodiments, steps S5101 and S5105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0193] In some embodiments, step S5105 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0194] In some embodiments, step S5101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0195] Figure 5B This is a flowchart illustrating a communication method according to an exemplary embodiment, such as... Figure 5B As shown, this method is used in terminal 102 and may include, but is not limited to, the following steps.

[0196] Step S5201: Receive the probe reference signal (SRS) resource set configured by the network device for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource.

[0197] Step S5202: On at least one SRS resource, an SRS for codebook transmission is sent to the network device; the SRS for codebook transmission is used by the network device to determine the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources and the N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources; N is an integer greater than or equal to 2.

[0198] Step S5203: Receive downlink control information (DCI) sent by the network device. The DCI is used to schedule PUSCH. The DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources.

[0199] In some embodiments, the terminal receives indication information sent by the network device, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0200] In some embodiments, the DCI described above further includes a Reference Indicator (RI) and / or an SRS Resource Indicator (SRI); wherein the RI and / or SRI are determined by the network device based on the SRS used for codebook transmission.

[0201] In some embodiments, the terminal sends PUSCH to the network device on the PUSCH frequency domain resources using a frequency hopping mode with in-slot frequency hopping based on SRI and / or TPMI.

[0202] The implementation of the terminal-side method in this embodiment can be found in the above description. Figure 2 The relevant descriptions of the steps on the terminal side will not be repeated here.

[0203] Figure 6 This is an interactive schematic diagram illustrating a communication method according to an exemplary embodiment, such as... Figure 6 As shown, the method is executed by the communication system 100 and may include, but is not limited to, the following steps.

[0204] In step S6101, network device 101 configures an SRS resource set for codebook transmission for terminal 102; the SRS resource set for codebook transmission includes at least one SRS resource.

[0205] For optional implementations of step S6101, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2102, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0206] In step S6102, terminal 102 sends an SRS for codebook transmission to network device on at least one SRS resource.

[0207] In some embodiments, the SRS for codebook transmission is used by the network device to determine the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources; N is an integer greater than or equal to 2.

[0208] For optional implementations of step S6102, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2103, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0209] In step S6103, network device 101 determines the TPMI corresponding to each of the N PUSCH frequency hopping resources and the N PUSCH frequency hopping resources in the PUSCH frequency domain resources according to the SRS used for codebook transmission; N is an integer greater than or equal to 2.

[0210] For optional implementations of step S6103, please refer to [link / reference]. Figure 2 Optional implementation methods of steps S2104 and S2105, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0211] In step S6104, network device 101 sends DCI to terminal 102. DCI is used to schedule PUSCH. DCI includes TPMI corresponding to each of N PUSCH frequency hopping resources.

[0212] For optional implementations of step S6104, please refer to [link / reference]. Figure 2 Optional implementation methods of step S2107, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0213] In some embodiments, the above methods may include the methods described in the embodiments on the network device side, terminal side, etc., which will not be repeated here.

[0214] This disclosure also provides embodiments of an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the network device in any of the above methods. Furthermore, another apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods.

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

[0216] In this embodiment, the processor is a circuit with information processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0217] Figure 7A This is a schematic diagram of the network device proposed in an embodiment of this disclosure. Figure 7AAs shown, the network device 7100 may include at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the processing module 7102 is configured to configure a sounding reference signal (SRS) resource set for codebook transmission for the terminal; the SRS resource set for codebook transmission includes at least one SRS resource; the transceiver module 7101 is configured to receive the SRS for codebook transmission sent by the terminal on at least one SRS resource; the processing module 7102 is further configured to determine, based on the SRS for codebook transmission, N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; N is an integer greater than or equal to 2; the transceiver module 7101 is further configured to send downlink control information (DCI) to the terminal, the DCI being used for PUSCH scheduling, and the DCI including the TPMI corresponding to each of the N PUSCH frequency hopping resources. Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2101, step S2107, but not limited thereto) performed by the network device 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps (such as step S2102, step S2104, step S2105, step S2106, but not limited thereto) performed by the terminal 102 in any of the above methods, which will not be elaborated here.

[0218] In some embodiments, the transceiver module 7101 is further configured to: send indication information to the terminal, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0219] In some embodiments, the processing module 7102 is specifically used to: divide the uplink bandwidth BWP into M bandwidth segments; M is an integer greater than or equal to N; according to the SRS used for codebook transmission, perform PUSCH frequency domain resource allocation and TPMI measurement within the M bandwidth segments to obtain the TPMI corresponding to each of the N PUSCH frequency hopping resources and the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

[0220] In some embodiments, N and M are both 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the processing module 7102 is specifically used to: allocate the first PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the first PUSCH frequency hopping resource in the first segment bandwidth according to the SRS used for codebook transmission, to obtain the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource; allocate the second PUSCH frequency hopping resource in the PUSCH frequency domain resources and measure the TPMI corresponding to the second PUSCH frequency hopping resource in the second segment bandwidth according to the SRS used for codebook transmission, to obtain the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource.

[0221] In some embodiments, N is 2 and M is greater than N; the processing module 7102 is specifically used to: allocate PUSCH frequency domain resources and measure TPMI within the M-segment bandwidth according to the SRS used for codebook transmission, to obtain M frequency hopping resources in the PUSCH frequency domain resources and the TPMI corresponding to each of the M frequency hopping resources; determine N PUSCH frequency hopping resources from the M frequency hopping resources; and determine the TPMI corresponding to each of the N PUSCH frequency hopping resources from the TPMI corresponding to each of the M PUSCH frequency hopping resources.

[0222] In some embodiments, the processing module 7102 is further configured to: determine the RI corresponding to the SRI and / or PUSCH frequency domain resources based on the SRS used for codebook transmission; wherein the DCI further includes the RI and / or SRS resource indication SRI.

[0223] In some embodiments, the transceiver module 7101 is further configured to: receive a PUSCH sent by the terminal on the PUSCH frequency domain resource; wherein the PUSCH sent by the terminal is sent to the network device by the terminal using a frequency hopping mode of in-slot frequency hopping based on SRI and / or TPMI.

[0224] Figure 7B This is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. For example... Figure 7BAs shown, terminal 7200 may include at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the transceiver module 7201 is configured to receive a set of sounding reference signals (SRS) for codebook transmission configured by a network device; the SRS resource set for codebook transmission includes at least one SRS resource; the transceiver module 7201 is further configured to send an SRS for codebook transmission to the network device on at least one SRS resource; the SRS for codebook transmission is used by the network device to determine N PUSCH frequency hopping resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources; N is an integer greater than or equal to 2; the transceiver module 7201 is further configured to receive downlink control information (DCI) sent by the network device, the DCI is used to schedule PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources. Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2103, step S2108, but not limited thereto) performed by terminal 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by terminal 102 in any of the above methods, which will not be elaborated here.

[0225] In some embodiments, the transceiver module 7201 is further configured to: receive indication information sent by the network device, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

[0226] In some embodiments, the DCI further includes a Name Indicator (RI) and / or an SRS Resource Indicator (SRI); wherein the RI and / or SRI are determined by the network device based on the SRS used for codebook transmission.

[0227] In some embodiments, the transceiver module 7201 is further configured to: send PUSCH to the network device on the PUSCH frequency domain resources using a frequency hopping mode with in-slot frequency hopping based on the SRI and / or the TPMI.

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

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

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

[0231] like Figure 8A As shown, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 8100 can be used to execute any of the above methods. Optionally, one or more processors 8101 can be used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0232] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2107, S2103, S2108, but not limited thereto), and the processor 8101 performs at least one of other steps (e.g., steps S2102, S2104, S2105, S2106, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0233] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing data. Optionally, all or part of the memories 8102 may be located outside the communication device 8100. In optional embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8102 and can be used to receive data from the memories 8102 or other devices, and to send data to the memories 8102 or other devices. For example, the interface circuits 8104 can read data stored in the memories 8102 and send the data to the processor 8101.

[0234] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in this disclosure is not limited thereto, and the structure of the communication device 8100 may vary. Figure 8A The limitations. The communication device can be a standalone device or part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0235] Figure 8B This is a schematic diagram of the structure of chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to... Figure 8B The diagram shown is a schematic of the structure of chip 8200, but it is not limited to this.

[0236] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the methods described above.

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

[0238] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2107, S2103, and S2108, but not limited thereto). For example, the interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of other steps (e.g., steps S2102, S2104, S2105, and S2106, but not limited thereto).

[0239] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

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

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

[0242] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0243] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0244] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0245] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is performed by a network device, and the method includes: Configure a probe reference signal (SRS) resource set for codebook transmission for the terminal; the SRS resource set for codebook transmission includes at least one SRS resource; Receive the SRS for codebook transmission sent by the terminal on the at least one SRS resource; Based on the SRS used for codebook transmission, determine N PUSCH frequency hopping resources in the physical uplink shared channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; where N is an integer greater than or equal to 2. Send downlink control information (DCI) to the terminal. The DCI is used to schedule the PUSCH. The DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources. The step of determining, based on the SRS used for codebook transmission, N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources, includes: The uplink bandwidth BWP is divided into M bandwidth segments; where M is an integer greater than or equal to N. According to the SRS used for codebook transmission, PUSCH frequency domain resource allocation and TPMI measurement are performed in each bandwidth segment of the M-segment bandwidth to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

2. The method as described in claim 1, characterized in that, The method further includes: Send indication information to the terminal, the indication information being used to indicate that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

3. The method as described in claim 1, characterized in that, Both N and M are 2; the M-segment bandwidth includes a first segment bandwidth and a second segment bandwidth, and the N PUSCH frequency hopping resources include a first PUSCH frequency hopping resource and a second PUSCH frequency hopping resource; the step of allocating PUSCH frequency domain resources and measuring TPMI within each segment of the M-segment bandwidth according to the SRS used for codebook transmission, to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources, includes: According to the SRS used for codebook transmission, the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource are allocated in the first bandwidth segment, and the first PUSCH frequency hopping resource is measured to obtain the first PUSCH frequency hopping resource and the TPMI corresponding to the first PUSCH frequency hopping resource. According to the SRS used for codebook transmission, the second PUSCH frequency hopping resource in the PUSCH frequency domain resource is allocated within the second bandwidth, and the TPMI corresponding to the second PUSCH frequency hopping resource is measured to obtain the second PUSCH frequency hopping resource and the TPMI corresponding to the second PUSCH frequency hopping resource.

4. The method as described in claim 1, characterized in that, The N is 2, and the M is greater than the N; the step of allocating PUSCH frequency domain resources and measuring TPMI in each bandwidth segment of the M bandwidth segments according to the SRS used for codebook transmission, to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources, includes: According to the SRS used for codebook transmission, PUSCH frequency domain resource allocation and TPMI measurement are performed within the M-segment bandwidth to obtain the M frequency hopping resources in the PUSCH frequency domain resources and the TPMI corresponding to each of the M frequency hopping resources. The N PUSCH frequency hopping resources are determined from the M frequency hopping resources; From the TPMIs corresponding to the M PUSCH frequency hopping resources, determine the TPMIs corresponding to the N PUSCH frequency hopping resources.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Based on the SRS used for codebook transmission, determine the SRS resource indicator SRI and / or the rank indicator RI corresponding to the PUSCH frequency domain resource; The DCI further includes the RI and / or the SRI.

6. The method as described in claim 5, characterized in that, The method further includes: The terminal receives the PUSCH sent by the terminal on the PUSCH frequency domain resource; wherein the PUSCH sent by the terminal is sent to the network device by the terminal using the frequency hopping mode of in-slot frequency hopping based on the SRI and / or the TPMI.

7. A communication method, characterized in that, The method includes: The network device receives a set of probe reference signals (SRS) resources configured for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource. On the at least one SRS resource, an SRS for codebook transmission is sent to the network device; the SRS for codebook transmission is used by the network device to determine N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; where N is an integer greater than or equal to 2. Receive downlink control information (DCI) sent by the network device. The DCI is used to schedule the PUSCH. The DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources. The SRS used for codebook transmission is also used by the network device to perform PUSCH frequency domain resource allocation and TPMI measurement in each bandwidth segment of the M-segment bandwidth, to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources; the M-segment bandwidth is obtained by the network device by segmenting the uplink bandwidth BWP, and M is an integer greater than or equal to N.

8. The method as described in claim 7, characterized in that, The method further includes: The system receives indication information sent by the network device, which indicates that the frequency hopping mode used by the PUSCH is intra-slot frequency hopping.

9. The method as described in claim 7 or 8, characterized in that, The DCI also includes a Rank Indicator (RI) and / or an SRS Resource Indicator (SRI); wherein the RI and / or the SRI are determined by the network device based on the SRS used for codebook transmission.

10. The method as described in claim 9, characterized in that, The method further includes: Based on the SRI and / or the TPMI, the PUSCH is sent to the network device on the PUSCH frequency domain resources using the frequency hopping mode of in-slot frequency hopping.

11. A communication device, characterized in that, include: The processing module is used to configure the probe reference signal (SRS) resource set for codebook transmission for the terminal; The SRS resource set for codebook transmission includes at least one SRS resource; A transceiver module is used to receive SRS for codebook transmission sent by the terminal on the at least one SRS resource; The processing module is further configured to determine, based on the SRS used for codebook transmission, N PUSCH frequency hopping resources in the physical uplink shared channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; wherein N is an integer greater than or equal to 2. The transceiver module is also used to send downlink control information (DCI) to the terminal. The DCI is used to schedule the PUSCH. The DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources. The processing module is further configured to: The uplink bandwidth BWP is divided into M bandwidth segments; where M is an integer greater than or equal to N. According to the SRS used for codebook transmission, PUSCH frequency domain resource allocation and TPMI measurement are performed in each bandwidth segment of the M-segment bandwidth to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources.

12. A communication device, characterized in that, include: The transceiver module is used to receive the Sounding Reference Signal (SRS) resource set configured by the network device for codebook transmission; The SRS resource set for codebook transmission includes at least one SRS resource; The transceiver module is further configured to send an SRS for codebook transmission to the network device on the at least one SRS resource; the SRS for codebook transmission is used by the network device to determine N PUSCH frequency hopping resources in the Physical Uplink Shared Channel (PUSCH) frequency domain resources and the Transmission Precoding Matrix Indicator (TPMI) corresponding to each of the N PUSCH frequency hopping resources; where N is an integer greater than or equal to 2. The transceiver module is further configured to receive downlink control information (DCI) sent by the network device. The DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources. The SRS used for codebook transmission is also used by the network device to perform PUSCH frequency domain resource allocation and TPMI measurement in each bandwidth segment of the M-segment bandwidth, to obtain the N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources; the M-segment bandwidth is obtained by the network device by segmenting the uplink bandwidth BWP, and M is an integer greater than or equal to N.

13. A communication device, characterized in that, include: One or more processors; The processor is used to invoke instructions to cause the communication device to perform the communication method as described in any one of claims 1-6 and 7-10.

14. A communication system, characterized in that, include: A communication device is configured to perform the communication method according to any one of claims 1-6; A communication device configured to perform the communication method according to any one of claims 7-10.

15. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-6 and 7-10.

Images