Communication method, device, equipment, system and storage medium

Abstract

The invention relates to a communication method, device, equipment, system and a storage medium. The method comprises the following steps: a network device configures a sounding reference signal (SRS) resource set for codebook transmission for a terminal; the SRS resource set for codebook transmission comprises at least one SRS resource; the network equipment receives the SRS which is sent by the terminal on the at least one SRS resource and is used for codebook transmission; according to the SRS used for codebook transmission, the network device determines N PUSCH frequency hopping resources in a physical uplink shared channel PUSCH frequency domain resource and transmission precoding matrix indications TPMIs corresponding to the N PUSCH frequency hopping resources respectively; n is an integer greater than or equal to 2; and the network equipment sends downlink control information (DCI) to the terminal, the DCI is used for scheduling the PUSCH, and the DCI comprises the TPMIs corresponding to the N PUSCH frequency hopping resources respectively. By implementing the embodiments of the present disclosure, the uplink throughput can be improved, and the user experience can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of communications, and in particular, to a communication method, apparatus, device, system, and storage medium. Background Art

[0002] As terminals gradually support MIMO (Multiple-Input Multiple-Output), that is, support multi-antenna transmission, it becomes possible for terminals to perform transmission through precoding. PUSCH (Physical Uplink Shared Channel) precoding is also being standardized. In related technologies, a communication system supports PUSCH transmission based on a codebook, that is, PUSCH precoding transmission. However, currently, there are problems such as low throughput in PUSCH transmission based on a codebook. Summary of the Invention

[0003] Embodiments of the present disclosure provide a communication method, apparatus, device, system, and storage medium.

[0004] In a first aspect, embodiments of the present disclosure provide a communication method, which is executed by a network device. The method includes: configuring, for a terminal, a sounding reference signal SRS resource set for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource; receiving, from the terminal, the SRS for codebook transmission sent on the at least one SRS resource; determining, according to the SRS for codebook transmission, N PUSCH hopping resources in a physical uplink shared channel PUSCH frequency domain resource and a transmission precoding matrix indicator TPMI corresponding to each of the N PUSCH hopping resources; N is an integer greater than or equal to 2; and sending downlink control information DCI to the terminal, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH hopping resources.

[0005] In the above embodiment, by determining, according to the SRS for codebook transmission sent by the terminal, N PUSCH hopping resources in the PUSCH frequency domain resource and the TPMI corresponding to each of the N PUSCH hopping resources, it is convenient for the terminal to perform PUSCH precoding based on the codebook corresponding to each of the N TPMIs, so that the network device schedules the PUSCH to use frequency hopping transmission within a time slot and uses N TPMIs within the PUSCH scheduling bandwidth, which can well adapt to the fading channel in a high-frequency scenario (also called a strong frequency scenario), thereby improving the uplink throughput and enhancing the user experience.

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

[0007] In some embodiments in combination with some embodiments of the first aspect, the determining, according to the SRS for codebook transmission, N PUSCH hopping resources in the physical uplink shared channel PUSCH frequency-domain resource and transmission precoding matrix indication TPMI corresponding to each of the N PUSCH hopping resources includes: dividing the uplink partial bandwidth BWP into M bandwidth segments; M is an integer greater than or equal to N; according to the SRS for codebook transmission, performing PUSCH frequency-domain resource allocation and TPMI measurement within the M bandwidth segments to obtain the N PUSCH hopping resources in the PUSCH frequency-domain resource and the TPMI corresponding to each of the N PUSCH hopping resources.

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

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

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

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

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

[0013] Combined with some embodiments of the first aspect, in some embodiments, the method further includes: determining, according to the SRS for codebook transmission, an SRS resource indication SRI and / or a rank indication RI corresponding to the PUSCH frequency-domain resource; wherein the DCI further includes the RI and / or the SRI.

[0014] In the above embodiments, the network device sends an RI to the terminal, facilitating the terminal to perform PUSCH precoding according to the RI and the codebooks corresponding to the N TPMIs respectively, such that the network device schedules the PUSCH to use intra-slot frequency hopping for transmission and uses N TPMIs within the PUSCH scheduling bandwidth, which can well adapt to the fading channels in high-frequency scenarios (also called strong frequency scenarios), thereby improving the uplink throughput and enhancing the user experience.

[0015] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving 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 an intra-slot frequency hopping pattern based on the SRI and / or the TPMI.

[0016] In a second aspect, embodiments of the present disclosure provide a communication method, the method including: receiving a sounding reference signal SRS resource set configured by a network device for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource; on the at least one SRS resource, sending an SRS for codebook transmission to the network device; the SRS for codebook transmission is used by the network device to determine N PUSCH frequency hopping resources in a physical uplink shared channel PUSCH frequency-domain resource and transmission precoding matrix indicators TPMIs respectively corresponding to the N PUSCH frequency hopping resources; N is an integer greater than or equal to 2; receiving downlink control information DCI sent by the network device, the DCI being used to schedule the PUSCH, and the DCI including the TPMIs respectively corresponding to the N PUSCH frequency hopping resources.

[0017] In combination 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 pattern used by the PUSCH is intra-slot frequency hopping.

[0018] In combination with some embodiments of the second aspect, in some embodiments, the DCI further 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 according to the SRS for codebook transmission.

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

[0020] In a third aspect, embodiments of the present disclosure provide a communication device, including: a processing module, configured to configure, for a terminal, a sounding reference signal (SRS) resource set for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource; a transceiver module, configured to receive, from the terminal, the SRS for codebook transmission sent on the at least one SRS resource; the processing module is further configured to determine, according to the SRS for codebook transmission, N physical uplink shared channel (PUSCH) hopping resources in the PUSCH frequency-domain resources and transmission precoding matrix indicators (TPMIs) respectively corresponding to the N PUSCH hopping resources; 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, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMIs respectively corresponding to the N PUSCH hopping resources.

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

[0022] In combination with some embodiments of the third aspect, in some embodiments, the processing module is specifically configured to: divide an uplink partial bandwidth (BWP) into M segments of bandwidth; 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 segments of bandwidth, to obtain the N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMIs respectively corresponding to the N PUSCH hopping resources.

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

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

[0025] In some embodiments in combination with some embodiments of the third aspect, the processing module is further configured to: determine, according to the SRS for codebook transmission, an SRS resource indication SRI and / or a rank indication RI corresponding to the PUSCH frequency-domain resources; wherein the DCI further includes the RI and / or the SRI.

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

[0027] Fourth aspect, embodiments of the present disclosure further provide a communication device, including: a transceiver module, configured to receive a sounding reference signal SRS resource set 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 send, on the at least one SRS resource, an SRS for codebook transmission; the SRS for codebook transmission is used for the network device to determine N PUSCH hopping resources in physical uplink shared channel PUSCH frequency-domain resources and a transmission precoding matrix indication TPMI corresponding to each of the N PUSCH hopping resources; 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 hopping resources.

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

[0029] In some embodiments in combination with some embodiments of the fourth aspect, the DCI further includes a rank indicator (RI) and / or a sounding reference signal (SRS) resource indicator (SRI); wherein, the RI and / or the SRI are determined by the network device according to the SRS for codebook transmission.

[0030] In some embodiments in combination with some embodiments of the fourth aspect, the transceiver module is further configured to: based on the SRI and / or the TPMI, use a frequency hopping pattern of intra-slot frequency hopping to send a physical uplink shared channel (PUSCH) on the PUSCH frequency domain resource to the network device.

[0031] Fifth aspect, embodiments of the present disclosure further propose a communication system, including:

[0032] A communication device configured to execute the communication method described in the foregoing first aspect;

[0033] A communication device configured to execute the communication method described in the foregoing second aspect.

[0034] Sixth aspect, embodiments of the present disclosure further propose a communication device, including: one or more processors; wherein, the processor is configured to call instructions to cause the communication device to execute the optional implementation manners of the foregoing first aspect.

[0035] Seventh aspect, embodiments of the present disclosure further propose a communication device, including: one or more processors; wherein, the processor is configured to call instructions to cause the communication device to execute the optional implementation manners of the foregoing second aspect.

[0036] Eighth aspect, embodiments of the present disclosure propose a storage medium, where the storage medium stores instructions, and when the instructions run on a communication device, the communication device is caused to execute the optional implementation manners of the foregoing first aspect and second aspect.

[0037] Ninth aspect, embodiments of the present disclosure propose a program product, and when the program product is executed by a communication device, the communication device is caused to execute the methods described in the optional implementation manners of the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, and sixth aspect.

[0038] Tenth aspect, embodiments of the present disclosure propose a computer program, and when it runs on a computer, the computer is caused to execute the methods described in the optional implementation manners of the first aspect and second aspect.

[0039] Eleventh aspect, embodiments of the present disclosure provide a chip or a chip system. The chip or the chip system includes a processing circuit configured to execute the methods described in the optional implementation manners of the foregoing first aspect and second aspect.

[0040] Understandably, the above-mentioned network device, terminal, storage medium, program product, computer program, chip or chip system are all used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be elaborated here.

[0041] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present invention, and are used together with the specification to explain the principles of the present invention.

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

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

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

[0046] Figure 4A It is a flowchart of a communication method shown according to an exemplary embodiment.

[0047] Figure 4B It is a flowchart of a communication method shown according to an exemplary embodiment.

[0048] Figure 5A It is a flowchart of a communication method shown according to an exemplary embodiment.

[0049] Figure 5B It is a flowchart of a communication method shown according to an exemplary embodiment.

[0050] Figure 6 It is an interaction schematic diagram of a communication method shown according to an exemplary embodiment.

[0051] Figure 7A It is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;

[0052] Figure 7B It is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0053] Figure 8A It is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure;

[0054] Figure 8BIt is a schematic structural diagram of the chip 8200 proposed by an embodiment of the present disclosure. Detailed implementation manners

[0055] Here, exemplary embodiments will be described in detail, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present invention. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0056] The embodiments of the present disclosure are not exhaustive, but only schematic of some embodiments, and do not specifically limit the protection scope of the present disclosure. Without contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily. For example, the solution after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be arbitrarily exchanged. In addition, the optional implementation manners in an embodiment can be combined arbitrarily; furthermore, the embodiments can be combined arbitrarily. For example, some or all of the steps of different embodiments can be combined arbitrarily, and an embodiment can be arbitrarily combined with the optional implementation manners of other embodiments.

[0057] In each embodiment of the present disclosure, if there is no special explanation and logical conflict, the terms and / or descriptions between the embodiments are consistent and can be cited from each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0058] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and are not intended as a limitation to the present disclosure.

[0059] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "one", "a kind of", "the", "above-mentioned", "said", "the foregoing", "this", etc., can mean "one and only one", or can also mean "one or more", "at least one", etc. For example, in the case of using articles such as "a", "an", "the" in English in the translation, the noun after the article can be understood as a singular expression form or a plural expression form.

[0060] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0061] In some embodiments, terms such as "at least one of (at least one item, at least one)", "one or more", "a plurality of", "multiple", etc. may be interchangeable with each other.

[0062] In some embodiments, notations such as "at least one of A and B", "A and / or B", "in one case A, in another case B", "in response to one case A, in response to another case B", etc. may, depending on the circumstances, include the following technical solutions: In some embodiments, A (executing A independently of B); in some embodiments, B (executing B independently of A); in some embodiments, selecting to execute from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same is true when there are more branches such as A, B, C, etc.

[0063] In some embodiments, notations such as "A or B" may, depending on the circumstances, include the following technical solutions: In some embodiments, A (executing A independently of B); in some embodiments, B (executing B independently of A); in some embodiments, selecting to execute from A and B (A and B are selectively executed). The same is true when there are more branches such as A, B, C, etc.

[0064] The prefix words such as "first", "second", etc. in the embodiments of the present disclosure are only used to distinguish different described objects, and do not impose restrictions on the position, order, priority, quantity, content, etc. of the described objects. For the statements of the described objects, refer to the descriptions in the claims or the context of the embodiments. There should be no redundant restrictions due to the use of prefix words. For example, if the described object is "field", the ordinal numbers before "field" in "first field" and "second field" do not restrict the position or order between the "fields", and "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". Another example, if the described object is "level", the ordinal numbers before "level" in "first level" and "second level" do not restrict the priority between the "levels". Another example, the quantity of the described object is not restricted by the ordinal number and can be one or more. Taking "first device" as an example, the quantity of "device" therein can be one or more. In addition, the objects modified by different prefix words can be the same or different. For example, if the described object is "device", "first device" and "second device" can be the same device or different devices, and their types can be the same or different; another example, if the described object is "information", "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

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

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

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

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

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

[0070] In some embodiments, a "terminal" or "terminal device" may be referred to as a "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, obtaining data, information, etc. may comply with the laws and regulations of the country where it is located.

[0072] In some embodiments, data, information, etc. may be obtained after obtaining the consent of the user.

[0073] Figure 1 It is a schematic diagram of the architecture of a communication system shown according to an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal. Figure 1 The number and form of the devices shown are only for illustration and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, there may be two or more network devices and two or more terminals. Figure 1 The communication system 100 shown takes a network device 101 and a terminal 102 as an example.

[0074] In some embodiments, the terminal 102 herein may be an entity on the user side 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 may be at least one of an automobile with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), 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, and so on. Embodiments of the present disclosure do not limit the specific technologies and specific device forms adopted by the terminal.

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

[0076] In some embodiments, the technical solution of the present disclosure is applicable to the Open RAN architecture. At this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can become the internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0077] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU may also be referred to as a control unit. Adopting the CU-DU structure can split the protocol layer of the access network device, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU, and the CU centrally controls the DU, but it is not limited thereto.

[0078] It can be understood that the communication system described in the embodiments of the present disclosure is to more clearly illustrate the technical solution of the embodiments of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solution proposed in the embodiments of the present disclosure is equally applicable to similar technical problems.

[0079] The following embodiments of the present disclosure can be applied to Figure 1 the communication system 100 shown, or part of the main body, but it is not limited thereto. Figure 1 The main bodies shown are illustrative. The communication system may include Figure 1 all or part of the main bodies in Figure 1 or may include other main bodies outside

[0080] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the 4th generation mobile communication system (4G), the 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), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems extended based on them, etc. In addition, multiple systems can be combined (for example, a combination of LTE or LTE-A and 5G, etc.) and applied.

[0081] It should be noted that as terminals gradually support MIMO (Multiple-Input Multiple-Output), that is, support multi-antenna transmission, it becomes possible for terminals to perform transmission through precoding. The precoding of PUSCH (Physical Uplink Shared Channel) is also being standardized. In related technologies, the communication system supports PUSCH transmission based on a codebook, that is, PUSCH precoding transmission. The current protocol only standardizes the PUSCH precoding for the entire band (such as the PUSCH scheduling bandwidth), that is, the TPMI (Transmit precoding matrix indicator) and RI (rank indicator) sent using the same DCI (Downlink Control Information) within the PUSCH scheduling bandwidth. Even if the PUSCH is sent using the intra-slot frequency hopping method, the same TPMI is used for both segments of frequency hopping. The network device indicates information such as the TPMI to the terminal, and the terminal uses the codebook corresponding to the TPMI for precoding. The same TPMI codebook is used for all bandwidths, and the same TPMI codebook is also used for different frequency hopings. The base network device performs PUSCH reception and demodulation based on the assumption of full-band precoding.

[0082] In a strong frequency scenario (also called a high-frequency scenario), the fading characteristics at different frequency domain positions may be different. It is precisely for this consideration that the network device schedules the PUSCH to be sent using intra-slot frequency hopping. However, using the same TPMI codebook for all bandwidths (i.e., the PUSCH scheduling bandwidth) cannot well adapt to this fading channel and affects the user experience.

[0083] Therefore, the embodiments of the present disclosure propose a communication method and apparatus. The network device can determine N PUSCH frequency hopping resources and the TPMI corresponding to each of the N PUSCH frequency hopping resources in the PUSCH frequency domain resources according to the SRS for codebook transmission sent by the terminal, facilitating the terminal to perform PUSCH precoding based on the codebooks corresponding to the N TPMIs, enabling the network device to schedule the PUSCH to be sent using intra-slot frequency hopping and using N TPMIs within the PUSCH scheduling bandwidth, which can well adapt to the fading channel in the high-frequency scenario (also called the strong frequency scenario), thereby improving the uplink throughput and enhancing the user experience.

[0084] Figure 2 It is an interaction diagram of the communication method shown according to the embodiments of the present disclosure. As Figure 2 shown, the embodiments of the present disclosure related to the communication method can be applied to the communication system 100, and the above method includes but is not limited to the following steps.

[0085] Step S2101, the network device 101 sends indication information to the terminal 102.

[0086] In some embodiments, the above indication information can be sent by the network device 101 to the terminal 102. Correspondingly, the terminal 102 receives the indication information sent by the network device 101. In some embodiments, the terminal 102 can be a chip or a mobile terminal. In some embodiments, the terminal 102 herein can be an entity on the user side for receiving or transmitting signals, such as a mobile phone. It can also be called a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal can be at least one of an automobile with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, 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 smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present disclosure do not limit the specific technologies and specific device forms adopted by 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 above indication information may be RRC (Radio Resource Control) signaling, or MAC (Medium Access Control) CE (control element), or DCI. In some embodiments, the above indication information may be included in the RRC (Radio Resource Control) signaling, or MAC (Medium Access Control) CE (control element), or DCI. Exemplarily, the network device 101 may indicate, via the RRC signaling, or MAC CE, or DCI, that the hopping pattern used by the PUSCH is intra-slot hopping.

[0089] Step S2102: The network device 101 configures an SRS (Sounding Reference Signal) resource set for the terminal 102 for codebook transmission.

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

[0091] Exemplarily, the network device 101 may send an SRS resource configuration to the terminal 102. Correspondingly, the terminal receives the SRS resource configuration sent by the 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. Exemplarily, the above SRS resource set for codebook transmission may be one or multiple. That is, the network device 101 configures one SRS resource set for codebook transmission for the terminal 102, or may also configure multiple SRS resource sets for codebook transmission for the terminal 102. Each of the SRS resource sets for codebook transmission may include at least one SRS resource.

[0092] Step S2103: The terminal 102 sends an SRS for codebook transmission on at least one SRS resource.

[0093] In some embodiments, the above SRS for codebook transmission may be sent by the terminal 102 to the network device 101. Exemplarily, the terminal 102 sends an SRS for codebook transmission to the network device 101 on at least one SRS resource. Correspondingly, the network device 101 receives the SRS for codebook transmission sent by the terminal on at least one SRS resource.

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

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

[0096] Exemplarily, after receiving the above SRS for codebook transmission sent by the terminal 102, the network device 101 estimates the uplink channel on the above SRS for codebook transmission (i.e., the SRS resource sent by the terminal), facilitating PUSCH resource allocation and TPMI measurement. When performing PUSCH resource allocation and TPMI measurement, the network device 101 can divide the uplink BWP into M segments of bandwidth. Among them, the above uplink BWP can be understood as the PUSCH scheduling bandwidth. For example, it can be the uplink partial bandwidth configured by the network device 101 for the terminal 102 to schedule PUSCH, and this uplink BWP can be included in the above SRS resource configuration. Among them, M can be an integer greater than or equal to 2.

[0097] Exemplarily, when there are multiple SRSs for codebook transmission sent by the terminal 102, the network device can select an optimal SRS from the SRSs sent by the terminal and estimate the uplink channel on this optimal SRS.

[0098] In some embodiments, the network device 101 can divide the uplink BWP into M segments of bandwidth based on the network implementation. Exemplarily, the network device 101 can divide the uplink BWP into M segments of bandwidth based on network policies. In one possible implementation, the network device 101 can divide the uplink BWP into 2 segments of bandwidth, such as the first segment of bandwidth and the second segment of bandwidth. The lengths of the first segment of bandwidth and the second segment of bandwidth can be the same or different, or the first segment of bandwidth and the second segment of bandwidth can partially overlap. In another possible implementation, the network device 101 can divide the uplink BWP into M (such as an integer greater than 2, for example, M is 3) segments of bandwidth. Or, the network device 101 can also divide the uplink BWP into other numbers of segments of bandwidth. Here, the present disclosure does not make a limitation on this and will not elaborate further.

[0099] Step S2105, the network device 101 performs PUSCH frequency-domain resource allocation and TPMI measurement within the M segments of bandwidth according to the SRS for codebook transmission, and obtains N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping 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, both N and M are 2; the above M segments of bandwidth include a first segment of bandwidth and a second segment of bandwidth, and the above N PUSCH hopping resources include a first PUSCH hopping resource and a second PUSCH hopping resource; the network device 101 performs PUSCH frequency-domain resource allocation and TPMI measurement within the M segments of bandwidth according to the SRS for codebook transmission, and possible implementation manners for obtaining the N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping resources include: the network device 101 allocates the first PUSCH hopping resource in the PUSCH frequency-domain resources within the first segment of bandwidth and measures the TPMI corresponding to the first PUSCH hopping resource according to the SRS for codebook transmission, so as to obtain the first PUSCH hopping resource and the TPMI corresponding to the first PUSCH hopping resource; according to the SRS for codebook transmission, the second PUSCH hopping resource in the PUSCH frequency-domain resources is allocated within the second segment of bandwidth and the TPMI corresponding to the second PUSCH hopping resource is measured, so as to obtain the second PUSCH hopping resource and the TPMI corresponding to the second PUSCH hopping resource. Among them, the technical means of allocating the PUSCH scheduling resource position (such as the scheduling RB position) and measuring the corresponding TMPI within each segment of bandwidth according to the SRS for codebook transmission can be implemented by using existing allocation and measurement manners. That is to say, the implementation manner of allocating the PUSCH scheduling resource position and measuring the corresponding TMPI within each segment of bandwidth according to the SRS for codebook transmission can be implemented by using existing allocation and measurement manners. Herein, the present disclosure does not make any limitation thereto and will not elaborate further.

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

[0103] In some embodiments, N may be 2, and M is greater than N; the network device 101 performs PUSCH frequency-domain resource allocation and TPMI measurement within M segments of bandwidth according to the SRS for codebook transmission, and possible implementation manners for obtaining N PUSCH hopping resources and the TPMI corresponding to each of the N PUSCH hopping resources in the PUSCH frequency-domain resources include: the network device 101 performs PUSCH frequency-domain resource allocation and TPMI measurement within M segments of bandwidth according to the SRS for codebook transmission, obtains M hopping resources and the TPMI corresponding to each of the M hopping resources in the PUSCH frequency-domain resources; the network device 101 determines N PUSCH hopping resources from the M hopping resources, and determines the TPMI corresponding to each of the N PUSCH hopping resources from the TPMI corresponding to each of the M PUSCH hopping resources.

[0104] Exemplarily, the network device 101 may directly divide the uplink BWP (such as the 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 hopping resources and the TPMI corresponding to each of the M hopping resources in the PUSCH frequency-domain resources, select 2 PUSCH hopping resources from the M hopping resources, and select the TPMI corresponding to each of the 2 PUSCH hopping resources from the TPMI corresponding to each of the M PUSCH hopping resources, so that the network device schedules the PUSCH to use frequency hopping transmission within a time slot and uses two TPMIs within the PUSCH scheduling bandwidth. Exemplarily, the network device 101 may be network-implemented to select 2 PUSCH hopping resources from the M hopping resources, and may be network-implemented to select the TPMI corresponding to each of the 2 PUSCH hopping resources from the TPMI corresponding to each of the M PUSCH hopping resources.

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

[0106] It is worth noting that the above TPMI can be used for pre-coder selection of PUSCH, where the TPMI is used for pre-coding indication of codebook-based uplink transmission.

[0107] Step S2106, the network device 101 determines the RI corresponding to the SRI and / or the PUSCH frequency-domain resource according to the SRS for codebook transmission.

[0108] In some embodiments, the network device 101 may also calculate the RI corresponding to the PUSCH frequency-domain resource according to the SRS for codebook transmission. One RI corresponds to N PUSCH hopping resources in the PUSCH frequency-domain resource. Exemplarily, after receiving the above-mentioned SRS for codebook transmission sent by the terminal 102, the network device 101 estimates the uplink channel on the above-mentioned SRS for codebook transmission (i.e., the SRS resource sent by the terminal), and in addition to performing PUSCH frequency-domain resource allocation and TPMI measurement within M segments of bandwidth, the network device 101 may also calculate the RI corresponding to the PUSCH frequency-domain resource.

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

[0110] Step S2107, the network device 101 sends DCI to the terminal 102.

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

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

[0113] In some embodiments, the DCI may include the TPMI corresponding to each of the above N PUSCH hopping resources. Exemplarily, the above step S2106 is optional, and in different embodiments, one or more of these steps may be omitted or replaced.

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

[0115] Step S2108, after receiving the DCI, the terminal 102 sends a PUSCH on the PUSCH frequency-domain resource.

[0116] In some embodiments, the PUSCH sent by the above terminal 102 may be sent by the terminal 102 to the network device 101 in a frequency hopping pattern using in-slot frequency hopping based on the SRI and / or TPMI. Exemplarily, after receiving the above DCI sent by the network device 101, the terminal 102 sends the PUSCH to the network device 101 in a frequency hopping pattern using in-slot frequency hopping based on the SRI and / or TPMI in the PUSCH frequency domain resource. Correspondingly, the network device 101 receives the PUSCH sent by the terminal in the PUSCH frequency domain resource.

[0117] Exemplarily, the terminal 102 receives a DCI, where the DCI includes the TPMI corresponding to each of the N PUSCH frequency hopping resources, such as the TPMI 1 corresponding to the first PUSCH frequency hopping resource and the TPMI 2 corresponding to the second PUSCH frequency hopping resource. The DCI may further include the SRI and / or RI. The terminal 102 sends the PUSCH to the network device 101 in a frequency hopping pattern using in-slot frequency hopping based on the TPMI 1, TPMI 2, SRI, and / or RI in the DCI in the PUSCH frequency domain resource. Exemplarily, when the terminal 102 sends the PUSCH on the first PUSCH frequency hopping resource, PUSCH precoding is performed based on the codebook corresponding to the TPMI 1, and when the terminal 102 sends the PUSCH on the second PUSCH frequency hopping resource, PUSCH precoding is performed based on the codebook corresponding to the TPMI 2.

[0118] For example, as Figure 3 shown, the network device 101 configures an SRS resource set for codebook transmission for the terminal 102. The terminal 102 sends the SRS for codebook transmission (codebook SRS) in slot N (time slot N). The network device 101 will configure the bandwidth for the terminal (such as the PUSCH scheduling bandwidth, such as Figure 3Divide the BWPSize into two segments of bandwidth, and measure the PUSCH scheduling resource location and the corresponding TPMI within each segment of bandwidth, such as measuring TPMI 1 and TPMI 2. The network device 101 sends DCI to the terminal 102. The DCI includes TPMI 1 and TPMI 2, and may also include RI and / or SRI. Among them, 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. The terminal 102 receives the DCI and, on slot M (time slot M), based on TPMI 1, TPMI 2, SRI, and / or RI in the DCI, uses the frequency hopping mode of in-slot frequency hopping to send PUSCH to the network device 101. Exemplarily, when the terminal 102 sends PUSCH on the first PUSCH frequency hopping resource, it performs PUSCH precoding based on the codebook corresponding to TPMI 1, and 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", "send down", "transmit", "two-way transmission", "send and / or receive" may be replaced with each other.

[0120] In some embodiments, "acquire", "obtain", "get", "receive", "transmit", "two-way transmission", "send and / or receive" may be replaced with each other, and it can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, self-processing to obtain, self-implementation, etc.

[0121] In some embodiments, terms such as "uplink", "uplink link", "physical uplink" may be replaced with each other, terms such as "downlink", "downlink link", "physical downlink" may be replaced with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" may be replaced with each other.

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

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

[0124] In some embodiments, steps S2101 and S2102 may be executed in reverse order or simultaneously.

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

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

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

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

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

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

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

[0132] In some embodiments, reference may be made to Figure 2 other optional implementation manners described before or after the corresponding specification.

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

[0134] Step S4101, sending indication information to terminal 102.

[0135] Optional implementation manners of step S4101 may be referred to Figure 2 the optional implementation manners of step S2101, and Figure 2 other related parts in the involved embodiments will not be elaborated here.

[0136] Step S4102, configuring an SRS resource set for codebook transmission for terminal 102.

[0137] Optional implementation manners of step S4102 may be referred to Figure 2Alternative implementation of step S2102, and Figure 2 Other related parts in the involved embodiments will not be elaborated here.

[0138] Step S4103: The receiving terminal 102 receives the SRS for codebook transmission sent on at least one SRS resource.

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

[0140] The alternative implementation of step S4103 can refer to Figure 2 the alternative implementation of step S2103, and Figure 2 Other related parts in the involved embodiments will not be elaborated here.

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

[0142] The alternative implementation of step S4104 can refer to Figure 2 the alternative implementation of step S2104, and Figure 2 Other related parts in the involved embodiments will not be elaborated here.

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

[0144] The alternative implementation of step S4105 can refer to Figure 2 the alternative implementation of step S2105, and Figure 2 Other related parts in the involved embodiments will not be elaborated here.

[0145] Step S4106: According to the SRS for codebook transmission, determine the SRI and / or the RI corresponding to the PUSCH frequency-domain resources.

[0146] The alternative implementation of step S4106 can refer to Figure 2 the alternative implementation of step S2106, and Figure 2 Other related parts in the involved embodiments will not be elaborated here.

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

[0148] For the optional implementation of step S4107, reference can be made to Figure 2 the optional implementation of step S2107 in Figure 2 and other related parts in the embodiments involved. Details are not elaborated herein.

[0149] Step S4108: The receiving terminal receives the PUSCH sent on the PUSCH frequency-domain resource.

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

[0151] For the optional implementation of step S4108, reference can be made to Figure 2 the optional implementation of step S2108 in Figure 2 and other related parts in the embodiments involved. Details are not elaborated herein.

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

[0153] In some embodiments, step S4101 and step S4102 may be executed in an exchanged 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 replaced in different embodiments.

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

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

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

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

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

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

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

[0162] Step S4201: Configure for the terminal a sounding reference signal (SRS) resource set for codebook transmission; 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 terminal on at least one SRS resource.

[0164] Step S4203: Determine, according to the SRS for codebook transmission, N physical uplink shared channel (PUSCH) frequency-domain hopping resources in the PUSCH frequency-domain resources and the transmission precoding matrix indicator (TPMI) corresponding to each of the N PUSCH frequency-domain hopping resources; N is an integer greater than or equal to 2.

[0165] In some embodiments, the possible implementation manners of determining N PUSCH hopping resources and the transmission precoding matrix indication (TPMI) corresponding to each of the N PUSCH hopping resources in the physical uplink shared channel (PUSCH) frequency-domain resources according to the sounding reference signal (SRS) for codebook transmission include: dividing the uplink partial 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 for codebook transmission, so as to obtain the N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping resources.

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

[0167] In some embodiments, N is 2 and M is greater than N; the possible implementation manners of performing PUSCH frequency-domain resource allocation and TPMI measurement within the M bandwidth segments according to the SRS for codebook transmission, so as to obtain the N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping resources include: performing PUSCH frequency-domain resource allocation and TPMI measurement within the M bandwidth segments according to the SRS for codebook transmission, so as to obtain M hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the M hopping resources; determining N PUSCH hopping resources from the M hopping resources; and determining the TPMI corresponding to each of the N PUSCH hopping resources from the TPMI corresponding to each of the M PUSCH hopping resources.

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

[0169] In some embodiments, the network device sends indication information to the terminal, and the indication information is used to indicate that the hopping pattern used by the PUSCH is intra-slot hopping.

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

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

[0172] For the implementation manner of the method on the network device side in this embodiment, reference may be made to the relevant descriptions of the steps on the network device side above Figure 2 and will not be elaborated here.

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

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

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

[0176] For the optional implementation manner of step S5101, reference may be made to Figure 2 the optional implementation manner of step S2101 in Figure 2 and other related parts in the involved embodiments, and will not be elaborated here.

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

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

[0179] For the optional implementation manner of step S5102, reference may be made to Figure 2 the optional implementation manner of step S2102 in Figure 2 and other related parts in the involved embodiments, and will not be elaborated here.

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

[0181] In some embodiments, the above SRS for codebook transmission is used for the network device to determine N PUSCH hopping resources in the PUSCH frequency-domain resource and the transmission precoding matrix indication (TPMI) corresponding to each of the N PUSCH hopping resources. Exemplarily, the network device performs PUSCH frequency-domain resource allocation and TPMI measurement within M segments of bandwidth based on the SRS for codebook transmission, where the M segments of bandwidth are obtained by segmenting the uplink BWP. Optional implementation manners can be referred to the Figure 2 optional implementation manners of step S2104 and step S2105, and Figure 2 other related parts in the embodiments involved, which will not be elaborated here.

[0182] Optional implementation manners of step S5103 can be referred to the Figure 2 optional implementation manners of step S2103, and Figure 2 other related parts in the embodiments involved, which will not be elaborated here.

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

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

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

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

[0187] Optional implementation manners of step S5104 can be referred to the Figure 2 optional implementation manners of step S2107, and Figure 2 other related parts in the embodiments involved, which will not be elaborated here.

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

[0189] Optional implementation manners of step S5105 can be referred to the Figure 2 optional implementation manners of step S2108, and Figure 2Other related parts in the embodiments involved will not be elaborated here.

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

[0191] In some embodiments, step S5101 and step S5102 may be executed in reverse order or simultaneously.

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

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

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

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

[0196] Step S5201, receiving a sounding reference signal SRS resource set configured by a network device for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource.

[0197] Step S5202, sending, on at least one SRS resource, an SRS for codebook transmission to the network device; the SRS for codebook transmission is used by the network device to determine N PUSCH hopping resources and the transmission precoding matrix indicator TPMI corresponding to each of the N PUSCH hopping resources in the physical uplink shared channel PUSCH frequency domain resource; N is an integer greater than or equal to 2.

[0198] Step S5203: Receive the 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 hopping resources.

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

[0200] In some embodiments, the above DCI further includes the rank indication (RI) and / or the sounding reference signal (SRS) resource indication (SRI); wherein, the RI and / or the SRI are determined by the network device according to the SRS for codebook transmission.

[0201] In some embodiments, the terminal uses the intra-slot hopping mode based on the SRI and / or the TPMI to send the PUSCH on the PUSCH frequency-domain resources to the network device.

[0202] For the implementation manner of the method on the terminal side in this embodiment, reference may be made to the relevant description of the steps on the terminal side in the above Figure 2 and details are not described herein again.

[0203] Figure 6 FIG. is an interaction diagram of a communication method shown according to an exemplary embodiment. As Figure 6 shown, the method is executed by the communication system 100 and may include but is not limited to the following steps.

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

[0205] For the optional implementation manner of step S6101, reference may be made to Figure 2 the optional implementation manner of step S2102 in Figure 2 and other related parts in the involved embodiments, and details are not described herein again.

[0206] Step S6102: The terminal 102 sends the SRS for codebook transmission to the 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 N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping resources; N is an integer greater than or equal to 2.

[0208] For the optional implementation manner of step S6102, reference may be made to Figure 2 the optional implementation manner of step S2103 in Figure 2 and other related parts in the involved embodiments, and details are not described herein again.

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

[0210] For the optional implementation of step S6103, reference can be made to Figure 2 the optional implementations of step S2104 and step S2105 in Figure 2 and other related parts in the embodiments involved. Details are not described herein again.

[0211] Step S6104: The network device 101 sends DCI to the terminal 102. The DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH hopping resources.

[0212] For the optional implementation of step S6104, reference can be made to Figure 2 the optional implementation of step S2107 in Figure 2 and other related parts in the embodiments involved. Details are not described herein again.

[0213] In some embodiments, the above method may include the methods described in the embodiments on the network device side, terminal side, etc. Details are not described herein again.

[0214] Embodiments of the present disclosure also propose a device for implementing any of the above methods. For example, a device is proposed. The above device includes units or modules for implementing each step performed by the network device in any of the above methods. Another device is also proposed, including units or modules for implementing each step performed by the terminal in any of the above methods.

[0215] It should be understood that the division of each unit or module in the above device is only a division of logical functions. In actual implementation, it can be fully or partially integrated into a physical entity, or physically separated. In addition, the units or modules in the device can be implemented in the form of a processor calling software. For example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or the functions of each unit or module of the above device. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside or outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be implemented through the design of the hardware circuits. The above hardware circuits can be understood as one or more processors. For example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are implemented through the design of the logical relationship of the components in the circuit. Again, in another implementation, the above hardware circuit can be implemented through a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured through a configuration file, so as to implement the functions of some or all of the above units or modules. All units or modules of the above device can be fully implemented in the form of a processor calling software, or fully implemented in the form of hardware circuits, or partially implemented in the form of a processor calling software, and the remaining part is implemented in the form of hardware circuits.

[0216] In the embodiments of the present disclosure, a processor is a circuit with information processing capabilities. In one implementation, the processor can be a circuit with instruction reading and running 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), etc.; in another implementation, the processor can achieve certain functions through the logical relationship of hardware circuits, and the logical relationship of the above hardware circuits is fixed or can be reconstructed. For example, the processor is a hardware circuit implemented by 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 to implement the configuration of 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. In addition, 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), a Deep learning Processing Unit (DPU), etc.

[0217] Figure 7A is a schematic structural diagram of the network device proposed in the embodiments of the present disclosure. As 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 for the terminal a sounding reference signal (SRS) resource set for codebook transmission; the SRS resource set for codebook transmission includes at least one SRS resource; the transceiver module 7102 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, according to the SRS for codebook transmission, N PUSCH hopping resources in the physical uplink shared channel (PUSCH) frequency-domain resource and the transmission precoding matrix indicator (TPMI) corresponding to each of the N PUSCH hopping resources; N is an integer greater than or equal to 2; the transceiver module 7102 is further configured to send downlink control information (DCI) to the terminal, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH hopping resources. Optionally, the transceiver module is configured to perform at least one of the sending and / or receiving and other 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 herein. Optionally, the processing module is configured 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 herein.

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

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

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

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

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

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

[0224] Figure 7B is a schematic structural diagram of the terminal proposed by the embodiments of the present disclosure. As Figure 7BAs shown in the figure, the terminal 7200 may include at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the above-mentioned transceiver module 7201 is configured to receive a sounding reference signal (SRS) resource set 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, on at least one SRS resource, an SRS for codebook transmission to the network device; the SRS for codebook transmission is used for the network device to determine N physical uplink shared channel (PUSCH) frequency-domain resources and transmission precoding matrix indicators (TPMIs) corresponding to the N PUSCH frequency-hopping resources respectively; 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, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMIs corresponding to the N PUSCH frequency-hopping resources respectively. Optionally, the above-mentioned transceiver module is configured to perform at least one of the sending and / or receiving and other communication steps (such as step S2103, step S2108, but not limited thereto) performed by the terminal 102 in any of the above methods, which will not be elaborated here. Optionally, the above-mentioned processing module is configured to perform at least one of the other steps performed by the 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, where the indication information is used to indicate that the hopping pattern used by the PUSCH is intra-slot hopping.

[0226] In some embodiments, the DCI further includes a rank indicator (RI) and / or an SRS resource indicator (SRI); where the RI and / or the SRI are determined by the network device according to the SRS for codebook transmission.

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

[0228] In some embodiments, the transceiver module may include a sending module and / or a receiving module, and the sending module and the receiving module may be separate or integrated together. Optionally, the transceiver module may be replaced with a transceiver.

[0229] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the above-mentioned multiple sub-modules respectively perform all or part of the steps required to be performed by the processing module. Optionally, the processing module may be replaced with a processor.

[0230] Figure 8AIt is a schematic structural diagram of a communication device 8100 proposed by an embodiment of the present disclosure. The communication device 8100 may be a network device (such as an access network device, a core network device, etc.), or a terminal (such as a user equipment, etc.), or a chip, a chip system, or a processor, etc. that supports the network device to implement any of the above methods, or a chip, a chip system, or a processor, etc. that supports the terminal to implement any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments, and for details, reference can be made to the descriptions in the above method embodiments.

[0231] As Figure 8A shown, the communication device 8100 includes one or more processors 8101. The processor 8101 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to execute any of the above methods. Optionally, one or more processors 8101 are used to call 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 transceivers 8103 perform at least one of the communication steps such as sending and / or receiving in the above methods (such as step S2101, step S2107, step S2103, step S2108, but not limited thereto), and the processor 8101 performs at least one of the other steps (such as step S2102, step S2104, step S2105, step S2106, but not limited thereto). In an alternative embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and the transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver machine, transceiver circuit, interface circuit, interface, etc. may be replaced with each other, terms such as transmitter, transmitter unit, transmitter machine, transmitter circuit, etc. may be replaced with each other, and terms such as receiver, receiver unit, receiver machine, receiver circuit, etc. may be replaced with each other.

[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 also be outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 can be used to receive data from the memory 8102 or other devices and can be used to send data to the memory 8102 or other devices. For example, the interface circuit 8104 can read the data stored in the memory 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 the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be subject to Figure 8A restrictions. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit (IC), or chip, or chip system or subsystem; (2) a collection of one or more ICs. Optionally, the above IC collection may also include 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, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0235] Figure 8B is a schematic structural diagram of the chip 8200 proposed in the embodiments of the present disclosure. For the case where the communication device 8100 may be a chip or a chip system, reference may be made to Figure 8B the schematic structural diagram of the chip 8200 shown, but not limited thereto.

[0236] The chip 8200 includes one or more processors 8201. The chip 8200 is used to execute any of the above methods.

[0237] In some embodiments, the 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, the chip 8200 further includes one or more memories 8203 for storing data. Optionally, all or part of the memories 8203 can be outside the chip 8200. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive data from the memory 8203 or other devices, and the interface circuit 8202 can be used to send data to the memory 8203 or other devices. For example, the interface circuit 8202 can read the data stored in the memory 8203 and send the data to the 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 (such as step S2101, step S2107, step S2103, step S2108, but not limited thereto). The interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method means, for example, 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 the other steps (such as step S2102, step S2104, step S2105, step S2106, but not limited thereto).

[0239] The present disclosure also provides a storage medium. Instructions are stored on the above storage medium. When the above instructions run on the communication device 8100, the communication device 8100 is caused to execute any of the above methods. Optionally, the above storage medium is an electronic storage medium. Optionally, the above storage medium is a computer-readable storage medium, but not limited thereto. It can also be a storage medium readable by other devices. Optionally, the above storage medium can be a non-transitory storage medium, but not limited thereto. It can also be a transitory storage medium.

[0240] The present disclosure also provides a program product. When the above program product is executed by the communication device 8100, the communication device 8100 is caused to execute any of the above methods. Optionally, the above program product is a computer program product.

[0241] The present disclosure also provides a computer program. When it runs on a computer, the computer is caused to execute any of the above methods.

[0242] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the processes or functions described in the embodiments of the present disclosure are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a high-definition digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0243] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present disclosure.

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

[0245] As mentioned above, the above is only the specific implementation manner of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present disclosure and should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that, The method is executed by a network device, and the method includes: Configuring a sounding reference signal (SRS) resource set for codebook transmission for a terminal; the SRS resource set for codebook transmission includes at least one SRS resource; Receiving the SRS for codebook transmission sent by the terminal on the at least one SRS resource; Determining, according to the SRS for codebook transmission, N physical uplink shared channel (PUSCH) frequency-domain hopping resources in the PUSCH frequency-domain resources and transmission precoding matrix indicators (TPMIs) respectively corresponding to the N PUSCH frequency-domain hopping resources; N is an integer greater than or equal to 2; Sending downlink control information (DCI) to the terminal, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMIs respectively corresponding to the N PUSCH frequency-domain hopping resources; 2. The method according to claim 1, wherein The method further includes: Sending indication information to the terminal, where the indication information is used to indicate that the hopping pattern used by the PUSCH is intra-slot hopping; 3. The method according to claim 1, wherein The determining, according to the SRS for codebook transmission, N physical uplink shared channel (PUSCH) frequency-domain hopping resources in the PUSCH frequency-domain resources and transmission precoding matrix indicators (TPMIs) respectively corresponding to the N PUSCH frequency-domain hopping resources includes: Dividing an uplink partial bandwidth (BWP) into M bandwidth segments; M is an integer greater than or equal to N; 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-domain hopping resources in the PUSCH frequency-domain resources and the TPMIs respectively corresponding to the N PUSCH frequency-domain hopping resources; 4. The method according to claim 3, wherein Both N and M are 2; the M bandwidth segments include a first bandwidth segment and a second bandwidth segment, and the N PUSCH frequency-domain hopping resources include a first PUSCH frequency-domain hopping resource and a second PUSCH frequency-domain hopping resource; the performing, according to the SRS for codebook transmission, PUSCH frequency-domain resource allocation and TPMI measurement within the M bandwidth segments, to obtain the N PUSCH frequency-domain hopping resources in the PUSCH frequency-domain resources and the TPMIs respectively corresponding to the N PUSCH frequency-domain hopping resources includes: Allocating the first PUSCH frequency-domain hopping resource in the PUSCH frequency-domain resources within the first bandwidth segment according to the SRS for codebook transmission and measuring the TPMI corresponding to the first PUSCH frequency-domain hopping resource, to obtain the first PUSCH frequency-domain hopping resource and the TPMI corresponding to the first PUSCH frequency-domain hopping resource; Allocating the second PUSCH frequency-domain hopping resource in the PUSCH frequency-domain resources within the second bandwidth segment according to the SRS for codebook transmission and measuring the TPMI corresponding to the second PUSCH frequency-domain hopping resource, to obtain the second PUSCH frequency-domain hopping resource and the TPMI corresponding to the second PUSCH frequency-domain hopping resource.

5. The method according to claim 3, characterized in that N is 2, and M is greater than N; according to the SRS for codebook transmission, performing PUSCH frequency-domain resource allocation and TPMI measurement within the M frequency bands, to obtain the N PUSCH hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the N PUSCH hopping resources, including: According to the SRS for codebook transmission, performing PUSCH frequency-domain resource allocation and TPMI measurement within the M frequency bands, to obtain M hopping resources in the PUSCH frequency-domain resources and the TPMI corresponding to each of the M hopping resources; Determining the N PUSCH hopping resources from the M hopping resources; Determining the TPMI corresponding to each of the N PUSCH hopping resources from the TPMI corresponding to each of the M PUSCH hopping resources.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: According to the SRS for codebook transmission, determining an SRS resource indication SRI and / or a rank indication RI corresponding to the PUSCH frequency-domain resources; Wherein, the DCI further includes the RI and / or the SRI.

7. The method according to claim 6, wherein The method further includes: Receiving a PUSCH sent by the terminal on the PUSCH frequency-domain resources; wherein, the PUSCH sent by the terminal is sent by the terminal to the network device using a hopping pattern of intra-slot hopping based on the SRI and / or the TPMI.

8. A communication method, characterized in that, The method includes: Receiving a sounding reference signal SRS resource set for codebook transmission configured by a network device; the SRS resource set for codebook transmission includes at least one SRS resource; On the at least one SRS resource, sending an SRS for codebook transmission to the network device; the SRS is used for the network device to determine N PUSCH hopping resources in physical uplink shared channel PUSCH frequency-domain resources and the transmission precoding matrix indication TPMI corresponding to each of the N PUSCH hopping resources; N is an integer greater than or equal to 2; Receiving a 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 hopping resources.

9. The method according to claim 8, wherein The method further includes: Receiving indication information sent by the network device, the indication information is used to indicate that the hopping pattern used by the PUSCH is intra-slot hopping.

10. The method according to claim 8 or 9, characterized in that, The DCI further includes a rank indication RI and / or an SRS resource indication SRI; wherein, the RI and / or the SRI are determined by the network device according to the SRS for codebook transmission.

11. The method according to claim 10, characterized in that, The method further includes: Based on the SRI and / or the TPMI, using a hopping pattern of intra-slot hopping to send a PUSCH to the network device on the PUSCH frequency-domain resources.

12. A communication device, characterized in that, Includes: A processing module, configured to configure a sounding 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 an SRS for codebook transmission sent by the terminal on the at least one SRS resource; The processing module is further configured to determine, according to the SRS for codebook transmission, N PUSCH hopping resources in the physical uplink shared channel PUSCH frequency-domain resource and a transmission precoding matrix indicator TPMI corresponding to each of the N PUSCH hopping resources; 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, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH hopping resources.

13. A communication device, characterized in that, Comprising: A transceiver module, configured to receive a sounding reference signal SRS resource set 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 send, on the at least one SRS resource, an SRS for codebook transmission to the network device; the SRS for codebook transmission is used for the network device to determine N PUSCH hopping resources in the physical uplink shared channel PUSCH frequency-domain resource and a transmission precoding matrix indicator TPMI corresponding to each of the N PUSCH hopping resources; 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, where the DCI is used to schedule the PUSCH, and the DCI includes the TPMI corresponding to each of the N PUSCH hopping resources.

14. A communication device, characterized in that, Comprising: One or more processors; Wherein, the processor is configured to call instructions to cause the communication device to execute the communication method according to any one of claims 1-7, 8-11.

15. A communication system, characterized in that, Comprising: A communication device, configured to execute the communication method according to any one of claims 1-7; A communication device, configured to execute the communication method according to any one of claims 8-11.

16. A storage medium, the storage medium stores instructions, characterized in that, When the instructions run on the communication device, the communication device is caused to execute the communication method according to any one of claims 1-7, 8-11.

Images