Communication method, terminal, and network device

Abstract

A communication method, a terminal, and a network device. The method comprises: sending first information, the first information being used for indicating whether a terminal supports a first mode, and the first mode representing that a baseband digital port of the terminal is shared between digital ports of all antenna panels, wherein the terminal performs simultaneous transmission from multiple panels (STxMP) transmission on the basis of multiple pieces of downlink control information (M-DCI). By means of the method, the capability of the terminal is enhanced, so that the terminal supports the first mode during the STxMP transmission, thereby reducing terminal costs.

Description

Communication method, terminal, and network device Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to communication methods, terminals, and network equipment. Background Art

[0002] The terminal supports simultaneous transmission from multiple antenna panels (STxMP) to achieve higher uplink throughput and more reliable transmission performance.

[0003] Summary of the Invention

[0004] How to save terminal costs when the terminal performs simultaneous uplink multi-antenna panel transmission on the physical uplink shared channel.

[0005] The embodiments of the present disclosure provide a communication method, a terminal, and a network device.

[0006] According to the first aspect of an embodiment of the present disclosure, a communication method is proposed, which includes: sending first information, where the first information is used to indicate whether the terminal supports a first mode, and the first mode indicates that the baseband digital port of the terminal is shared among the digital ports of each antenna panel; wherein the terminal performs uplink multi-antenna panel simultaneous transmission STxMP transmission based on multiple downlink control information M-DCI.

[0007] According to the second aspect of an embodiment of the present disclosure, a communication method is proposed, which includes: receiving first information, the first information being used to indicate whether the terminal supports a first mode, the first mode indicating that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0008] According to the third aspect of an embodiment of the present disclosure, a communication method is proposed, which includes: a terminal sends first information to a network device, the first information is used to indicate that the terminal supports a first mode, the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel, and the first information is also used to indicate the SRS resource set information supported by the terminal; the network device sends RRC signaling, activation signaling or deactivation signaling to the terminal, the RRC signaling, activation signaling or deactivation signaling includes a first configuration, and the first configuration is used to configure the SRS resource set; the terminal sends the SRS resource set to the network device; the network device estimates the channel state information based on the SRS resource set; the network device sends multiple downlink control information M-DCI; the terminal sends a physical uplink shared channel PUSCH based on the M-DCI.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module for sending first information, the first information being used to indicate whether the terminal supports a first mode, the first mode indicating that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0010] According to the fifth aspect of the embodiment of the present disclosure, a network device is proposed, including: a transceiver module for receiving first information, the first information is used to indicate whether the terminal supports a first mode, the first mode indicating that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; wherein the processor is configured to execute the communication method of the first aspect.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; wherein the processor is configured to execute the communication method of the second aspect.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the communication method of the first aspect, and the network device is configured to implement the communication method of the second aspect.

[0014] According to a ninth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and wherein when the instructions are executed on a communication device, the communication device executes the communication method of the first aspect or the second aspect.

[0015] Through the solution provided by the embodiment of the present disclosure, by enhancing the terminal capabilities, the baseband digital port of the terminal is shared among the digital ports of each antenna panel, thereby achieving efficient STxMP transmission while saving terminal costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0017] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0018] FIG1B is a schematic diagram of a transmission scenario under S-DCI scheduling according to an embodiment of the present disclosure.

[0019] FIG1C is a schematic diagram of a transmission scenario under M-DCI scheduling according to an embodiment of the present disclosure.

[0020] FIG1D is a schematic diagram of a transmission scenario in a shared digital port mode according to an embodiment of the present disclosure.

[0021] FIG1E is a schematic diagram of a transmission scenario in a shared digital port mode according to an embodiment of the present disclosure.

[0022] FIG2 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0023] FIG3A is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0024] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure.

[0025] FIG4A is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0026] FIG4B is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0027] FIG5 is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0028] FIG6A is a schematic diagram of a terminal according to an embodiment of the present disclosure.

[0029] FIG6B is a schematic diagram of a network device according to an embodiment of the present disclosure.

[0030] Fig. 7A is a schematic diagram showing a communication device according to an exemplary embodiment.

[0031] FIG7B is a schematic diagram showing a chip structure according to an exemplary embodiment. DETAILED DESCRIPTION

[0032] The embodiments of the present disclosure provide a communication method, a terminal, and a network device.

[0033] In the first aspect, an embodiment of the present disclosure proposes a communication method, including: sending first information, the first information is used to indicate whether the terminal supports a first mode, the first mode indicating that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0034] In the above embodiment, by enhancing the terminal capability, the terminal supports the first mode when performing STxMP transmission based on M-DCI, thereby saving terminal cost and achieving efficient STxMP transmission.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the first information is further used to indicate support for codebook-based and / or non-codebook PUSCH transmission under the STxMP transmission scheme.

[0036] In the above embodiment, by enhancing the terminal capability, the terminal supports STxMP transmission based on the codebook PUSCH when using the first mode, thereby saving terminal cost and achieving efficient STxMP transmission.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the first information is also used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is also used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; wherein, the first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; wherein, the terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

[0038] In the above embodiment, the terminal indicates the time domain resources and frequency domain resources between different PUSCHs through the first information, so that the network device configures resources for the PUSCH transmission of the terminal based on the first information, thereby improving the PUSCH transmission efficiency.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

[0040] In the above embodiment, the terminal indicates the overlap of time domain resources and frequency domain resources between different PUSCHs through the first information, so that the network device configures resources for the PUSCH transmission of the terminal based on the first information, thereby improving the PUSCH transmission efficiency.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

[0042] In the above embodiment, the terminal indicates the overlap of time domain resources and frequency domain resources between different PUSCHs through the first information, so that the network device configures resources for the PUSCH transmission of the terminal based on the first information, thereby improving the PUSCH transmission efficiency.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support full overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

[0044] In the above embodiment, the terminal indicates the overlap of time domain resources and frequency domain resources between different PUSCHs through the first information, so that the network device configures resources for the PUSCH transmission of the terminal based on the first information, thereby improving the PUSCH transmission efficiency.

[0045] In combination with some embodiments of the first aspect, in some embodiments, when codebook-based PUSCH transmission is supported, the first information is further used to indicate whether the terminal supports different panels configuring different codebook subsets.

[0046] In the above embodiment, the terminal indicates through the first information whether it supports different panels to be configured with different codebook subsets, so that the network device configures codebook subsets for different panels based on the first information, thereby improving STxMP transmission efficiency.

[0047] In combination with some embodiments of the first aspect, in some embodiments, when supporting codebook-based PUSCH transmission, the first information is also used to indicate whether the terminal supports configuring SRS resources with different numbers of ports in the same SRS resource set, and SRS resources with different numbers of ports correspond to different transmission schemes of the terminal, and different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes CoresetPoolIndex.

[0048] In the above embodiment, the terminal indicates through the first information whether it supports configuring SRS resources with different port numbers in the same SRS resource set, so that the network device configures SRS resources for the SRS resource set of the terminal based on the first information, thereby improving STxMP transmission efficiency.

[0049] In combination with some embodiments of the first aspect, in some embodiments, when non-codebook-based PUSCH transmission is supported, the first information is further used to indicate the total number of SRS resource sets supported by the terminal.

[0050] In the above embodiment, the terminal indicates the total number of SRS resource sets supported by the terminal through the first information, so that the network device configures the SRS resource set for the terminal based on the first information, thereby improving STxMP transmission efficiency.

[0051] In combination with some embodiments of the first aspect, in some embodiments, when the number of SRS resource sets configured by the terminal is 2, the first information is further used to indicate the maximum number of SRS resources included in each SRS resource set.

[0052] In the above embodiment, the terminal indicates the maximum number of SRS resources included in each SRS resource set through the first information, so that the network device configures the number of SRS resources in the SRS resource set based on the first information, thereby improving STxMP transmission efficiency.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending second information, where the second information is used to indicate the reserved time interval between the terminal sending SRS resource sets to different panels based on the first mode.

[0055] In the above embodiment, the terminal indicates the reserved time interval between different panels sending SRS resource sets through the second information, so that the network device determines the time interval between different panels sending SRS resource sets based on the second information, thereby improving STxMP transmission efficiency.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the time interval between when the terminal sends SRS resource sets to different panels based on the first mode is a preset value.

[0057] In the second aspect, an embodiment of the present disclosure proposes a communication method, including: receiving first information, the first information is used to indicate whether the terminal supports a first mode, the first mode indicating that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the first information is further used to indicate whether codebook-based and / or non-codebook PUSCH transmission is supported under the STxMP transmission scheme.

[0059] In combination with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is also used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; wherein, the first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; wherein, the terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support full overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

[0063] In combination with some embodiments of the second aspect, in some embodiments, when codebook-based PUSCH transmission is supported, the first information is further used to indicate whether the terminal supports different panels configuring different codebook subsets.

[0064] In combination with some embodiments of the second aspect, in some embodiments, when supporting codebook-based PUSCH transmission, the first information is also used to indicate whether the terminal supports configuring SRS resources with different port numbers in the same SRS resource set, and SRS resources with different port numbers correspond to different transmission schemes of the terminal, and different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes.

[0065] In combination with some embodiments of the second aspect, in some embodiments, when non-codebook-based PUSCH transmission is supported, the first information is used to indicate the total number of SRS resource sets supported by the terminal.

[0066] In combination with some embodiments of the second aspect, in some embodiments, when the number of SRS resource sets configured by the terminal is 2, the first information is also used to indicate the maximum number of SRS resources included in each SRS resource set.

[0067] In combination with some embodiments of the second aspect, in some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0069] Second information is sent, where the second information is used to instruct the terminal to send a reserved time interval between SRS resource sets to different panels based on the first mode.

[0070] In combination with some embodiments of the second aspect, in some embodiments, the time interval between the terminal sending SRS resource sets to different panels based on the first mode is a preset value.

[0071] In the third aspect, an embodiment of the present disclosure proposes a communication method, including: the terminal sends first information to a network device, the first information is used to indicate that the terminal supports a first mode, the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel, and the first information is also used to indicate the SRS resource set information supported by the terminal; the network device sends RRC signaling, activation signaling or deactivation signaling to the terminal, the RRC signaling, activation signaling or deactivation signaling includes a first configuration, and the first configuration is used to configure the SRS resource set; the terminal sends the SRS resource set to the network device; the network device estimates the channel state information based on the SRS resource set; the network device sends multiple downlink control information M-DCI; the terminal sends a physical uplink shared channel PUSCH based on the M-DCI.

[0072] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute optional implementation methods of the first and third aspects.

[0073] In a fifth aspect, an embodiment of the present disclosure proposes a network device, wherein the access network device includes at least one of a transceiver module and a processing module; wherein the access network device is used to execute optional implementation methods of the second and third aspects.

[0074] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, which includes: one or more processors; wherein the terminal is used to execute optional implementation methods of the first and third aspects.

[0075] In a seventh aspect, an embodiment of the present disclosure proposes a network device, which includes: one or more processors; wherein the network device is used to execute optional implementation methods of the second and third aspects.

[0076] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the optional implementation of the first and third aspects, and the network device is configured to execute the method described in the optional implementation of the second and third aspects.

[0077] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and third aspects, and the second and third aspects.

[0078] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and third aspects, and the second and third aspects.

[0079] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method as described in the first and third aspects, and the optional implementation of the second and third aspects.

[0080] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0081] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0082] The present disclosure provides a communication method. In some embodiments, the terms communication method and information processing method are interchangeable, and the terms information processing system and communication system are interchangeable.

[0083] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0084] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0085] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0086] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0087] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0088] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0089] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0090] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0091] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0092] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0093] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0094] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0095] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names 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.

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

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

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

[0099] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0101] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0102] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0103] As shown in FIG1A , a communication system 100 includes a terminal 101 and a core network device 102 .

[0104] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0105] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0106] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (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 base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

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

[0108] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0109] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0110] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0111] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0112] The 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, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), 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) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0113] With the development of communication technology, to ensure coverage, when network equipment (such as base stations) has multiple transmission reception points (TRPs), multiple TRPs (Multi-TRPs) or multiple antenna panels can be used to provide services to terminals. In addition, to provide more balanced service quality within the service area, Coordinated Multiple Point transmission (CoMP) technology has been introduced.

[0114] In a CoMP scenario, the antenna array of each TRP can be divided into several relatively independent panels, allowing the overall array configuration and port count to be flexibly adjusted based on deployment scenarios and service requirements. Panels or TRPs can also be connected by optical fiber, enabling more flexible distributed deployment. In the millimeter wave band, as wavelength decreases, the blocking effect caused by obstacles such as people or vehicles becomes more significant. In this case, to ensure link robustness, collaboration between multiple TRPs or panels can be leveraged to transmit / receive from multiple beams at multiple angles, thereby mitigating the adverse effects of blocking effects.

[0115] For the uplink, the physical uplink shared channel (PUSCH) for different TRPs may actually pass through channels with very different spatial characteristics. Therefore, it is considered that the Quasi Co-Loacted (QCL) type D of the PUSCH channel in different sending directions is different.

[0116] For the convenience of explanation, the QCL-Tyep indicated by TCI-State below is type D.

[0117] The above implementation scheme does not take into account the M-TRP scenario, and the uplink is a single TRP (Single-TRP, S-TRP) transmission. Certain embodiments of the present disclosure enhance the M-TRP uplink transmission under a single downlink control information (Single-Downlink Control Information, S-DCI), and the uplink PUSCH transmission is transmitted in the TRP direction of multiple network devices, and the collaborative transmission under the time division multiplexing (Time Division Multiplexing, TDM) transmission mode is standardized. The PUSCH is repeatedly sent to different TRPs of the network device through different transmission opportunities (Transmission Occasion, TO) in the time domain. This method has relatively low requirements on the terminal capability. Each TO only needs to send PUSCH to one TRP, so it is not required to support the ability to send beams simultaneously, and the transmission delay is relatively large.

[0118] In certain embodiments of the present disclosure, it is desired to transmit data to multiple TRPs simultaneously through multiple panels to increase the reliability and throughput of the transmission, and effectively reduce the transmission delay under multiple TRPs, but the terminal is required to have the ability to send multiple beams simultaneously. The transmission of PUSCH can be based on a single physical downlink control channel (Physical Downlink Control Channel, PDCCH), that is, multiple panels or multiple TRPs scheduled by S-DCI, as shown in Figure 1B. Among them, the terminal communicates with TPR1 of the network device through panel1, for example, receives the first precoding indication information (Transmit Precoding Matrix Indicator, TPMI) TPMI1 sent by TPR1, and sends one or more information related to the transport layer to TRP1, and communicates with TPR2 of the network device through panel2, for example, receives the second precoding indication information TPMI2 sent by TPR2, and sends one or more information related to the transport layer to TRP2. It can also be based on multiple panels or multiple TRPs scheduled by different PDCCHs, that is, multiple downlink control information (Multiple-Downlink Control Information, M-DCI), as shown in Figure 1C. Among them, the terminal communicates with TPR1 of the network device through panel1, for example, receives PDCCH1 sent by TRP1 and sends PUSCH1 to TRP1, and communicates with TPR2 of the network device through panel2, for example, receives PDCCH2 sent by TRP2 and sends PUSCH2 to TRP2.

[0119] Terminals are typically configured with multiple panels, and different panels may have different capabilities. For example, they may have different numbers of Sounding Reference Signal (SRS) ports and support different maximum data transmission layers. For example, one panel may support up to 2 layers, while another may support up to 4 layers. The network scheduler will determine whether the terminal is currently suitable for simultaneous uplink transmission of multiple panels. If the terminal is currently suitable for simultaneous uplink transmission of multiple panels and is scheduled, the network equipment will directly or indirectly indicate the relevant transmission parameters, including terminal-specific beam indication information, the number of data layers used for transmission, the allocation of demodulation reference signal (DMRS) ports used, and precoding indication information.

[0120] In certain embodiments of the present disclosure, the transmission schemes supported by uplink simultaneous transmission from multiple panels (STxMP) for PUSCH based on S-DCI include space division multiplexing (SDM) and single frequency network (SFN). The SDM scheme refers to that different parts of a transport block (TB) of PUSCH are respectively transmitted on the same time-frequency resources to two different TRPs through their respective corresponding DMRS ports or port combinations allocated on different panels, and different panels or different TRPs or different TOs are respectively associated with different TCI states, i.e. beams. The SFN scheme refers to that a TB of PUSCH is respectively transmitted on the same time-frequency resources to two different TRPs through the same DMRS ports or port combinations allocated on different panels, and different panels or different TRPs or different TOs are respectively associated with different TCI states, i.e. beams.

[0121] In some embodiments of the present disclosure, PUSCH uplink transmissions between a network device and a terminal include codebook-based and non-codebook-based uplink transmissions. The transmission scheme is generally selected based on whether reciprocity between the uplink and downlink channels holds. Regardless of the precoding mode, the terminal is required to transmit an SRS, allowing the network device to estimate uplink channel state information (CSI) based on the SRS.

[0122] In some embodiments, in codebook-based PUSCH transmission, the terminal needs to configure at most one SRS resource set. Among them, the SRS resource set can be configured with multiple SRS resources, and the network device will configure the SRS resource set according to the number of SRS resources (N SRS )feedback The SRS resource indicator (Sounding Reference Signal resource indicator, SRI) of the bit is used to select the SRS resource through the SRI indication, where: Indicates rounding up.

[0123] The following table 1 to table 3 are used as examples to provide the SRI indication method for multiple SRS resources. In Table 1 to Table 3, SRI(s) represents the number of SRI indications, N SRS The number of SRS resources.

[0124] Table 1

[0125] Table 2

[0126] Table 3

[0127] In some embodiments of the present disclosure, the network device determines the TPMI and number of transmission layers (Rank Indicator, RI) used by the terminal for actual transmission and notifies the terminal. The terminal's data in subsequent uplink transmissions needs to be precoded using the TPMI and RI specified by the network device. At the same time, the precoded data is mapped to the corresponding antenna port according to the spatial filtering (Spatial Relation Info) corresponding to the SRS resource indicated by the SRI.

[0128] Taking the following Table 4 as an example, Table 4 shows the precoding information and the number of layers in the codebook subset corresponding to 4 antenna ports and a maximum transmission layer number Rank of 1.

[0129] Table 4

[0130] Among them, Bit field mapped to index represents the bit field mapped to the index, codebookSubset represents the codebook subset, and the transmission capabilities of the codebook subset include: fullyAndPartialAndNonCoherent (fully coherent transmission), partialAndNonCoherent (partially coherent transmission), and nonCoherent (non-coherent transmission).

[0131] In Table 4 above, each TPMI is used to indicate a precoding. Table 5 below shows the codewords corresponding to single-layer transmission with 4 antenna ports.

[0132] Table 5

[0133] In other embodiments of the present disclosure, in non-codebook-based PUSCH transmission, the terminal sends a maximum number of SRS resources that can be transmitted simultaneously to the network device. Assuming that the network device performs an SRI indication to the terminal in time slot n, the corresponding SRS resource transmission is the most recent SRS transmission before time slot n. The terminal determines the limit of the precoding indication based on the maxRank in the high-level parameter PUSCH-Config, and the number of SRS resources indicated by the SRI is not greater than the maxRank. The network device can configure an associated CSI-RS resource for channel measurement for the SRS resource set used for non-codebook uplink transmission. The terminal obtains the precoding of the SRS transmission of the SRS resource set used for non-codebook uplink transmission based on the associated CSI-RS resource.

[0134] For non-codebook-based uplink transmission, in actual systems, it is generally necessary to measure the downlink CSI-RS configured. The terminal utilizes uplink and downlink reciprocity to obtain uplink channel information by measuring the downlink signal. The main process includes: the network configures the downlink CSI-RS associated with non-codebook-based transmission for the terminal to detect the downlink channel; the terminal selects the precoding matrix through downlink channel calculation and transmits the SRS in each precoding beam direction on the configured SRS resource set; the base station performs uplink channel detection on the SRS, and the network simultaneously schedules resources for the UE and notifies the UE via downlink signaling, selecting the beam in the precoding matrix through the SRI indicator; the terminal uses the modified precoding matrix to determine the actual precoding and the number of allowed layers to transmit the PUSCH; the terminal determines the precoding indicator limit based on the high-level parameter maxRank; the number of SRS resources indicated by the SRI is no greater than maxRank. To enable the network to modify the precoding matrix actually used by the terminal, for non-codebook-based transmission, the network needs to configure an SRS resource set for the terminal.

[0135] For non-codebook transmission schemes, the network device can configure one SRS resource set for the terminal, which includes 1 to 4 SRS resources, and each SRS resource includes one SRS port. When the network device configures multiple SRS resources for the terminal for non-codebook uplink transmission, the multiple SRS resources have the same time domain type, that is, all SRS resources are periodic SRS or semi-persistent SRS or non-periodic SRS. The network device can indicate to the terminal through SRI that one or more SRS resources are used for PUSCH precoding determination, and the number of SRS resources corresponding to SRI is the number of streams transmitted by PUSCH. When the network device configures only one SRS resource for non-codebook uplink transmission for the terminal, the SRI field is not included in the DCI used for uplink authorization.

[0136] The SRI indication field for non-codebook transmission is shown in Table 6, where Lmax is the transmission layer limit configured by the network device. The terminal determines the corresponding SRI table and the number of bits in the SRI indication field based on this parameter configuration.

[0137] Table 6

[0138] For uplink synchronous transmission of multiple panels, the coordinated transmission scheduling of a TB (Transport Block) of PUSCH based on a single DCI includes multiple different transmission schemes. Each transmission scheme is briefly described below.

[0139] One solution is SDM (Space Division Multiplexing): a PUSCH TB is transmitted on the same time-frequency resource to two different TRPs using DMRS ports or port combinations allocated on different panels. Different panels / TRPs / transmission opportunities (TO) are associated with different TCI (transmission configuration indicator) states, or beams. Based on this, SDM is further categorized into two types: SDM-A and SDM-B. In SDM-A, different portions of a PUSCH TB are transmitted on the same time-frequency resource to two different TRPs using DMRS ports or port combinations allocated on different panels. Different panels / TRPs / transmission opportunities (TO) are associated with different TCI states, or beams. In SDM-B, repetitions of the same PUSCH TB corresponding to different RV versions are transmitted on the same time-frequency resource to two different TRPs using DMRS ports or port combinations allocated on different panels. Different panels / TRPs / transmission opportunities (TO) are associated with different TCI states, or beams.

[0140] One solution is the SFN (Single Frequency Network) multiplexing solution: a TB of PUSCH is sent on the same time-frequency resources to two different TRPs through the same DMRS port or port combination allocated on different panels, and different Panes / TRPs / transmission opportunities TO are associated with different TCIstates or beams.

[0141] For simultaneous uplink PUSCH transmission based on multiple panels of a terminal, one or more of the above solutions may be supported.

[0142] In non-codebook and codebook-based M-TRP transmission, the SRI field in the DCI indicates the SRS resources in the SRS resource set. Since R17 supports two SRS resource sets, in non-codebook-based M-TRP PUSCH repeated transmission, the DCI format 0_1 / 0_2 contains two SRI fields associated with the two SRS resource sets. Each SRI field indicates SRI for one TRP. The design of the first SRI field is based on the R15 / 16 framework, and all repeated transmissions use the same number of layers.

[0143] For non-codebook-based transmission, the first SRI field is used to determine the elements in the second SRI field, and the second SRI field only contains the SRI combinations associated with the number of layers indicated by the first SRI field. The number of bits N2 in the second SRI field is determined by the maximum number of codepoints per transmission layer across all transmission layers associated with the first SRI field.

[0144] In codebook-based M-TRP PUSCH repetitive transmissions, two TPMI fields are indicated in DCI formats 0_1 / 0_2. The first TPMI field is designed identically to the TPMI field in R15 / 16 (including the TPMI index and number of layers). The second TPMI field contains only the second TPMI index, and the number of layers is the same as the number of layers indicated in the first TPMI field. The first TPMI field is used to determine the elements in the second TPMI field, and the second TPMI field contains only the TPMI associated with the number of layers indicated in the first TPMI field. The number of bits, M2, in the second TPMI field is determined by the maximum number of codepoints per rank among all ranks associated with the first TPMI field.

[0145] The indication fields for dynamically indicating S-TRP and M-TRP transmission scheduling are shown in Table 7. In S-TRP, the first SRI / TPMI field can be associated with any SRS resource.

[0146] Table 7

[0147] In some embodiments of the present disclosure, the PUSCH transmission of STxMP will configure different SRS resource sets for PUSCH transmission in different TRP / panel / TCI states, with a total of two SRS resource sets configured. For the SDM mode of STxMP transmission, the terminal implementation can consider one of the following two implementations:

[0148] Method 1: Shared digital ports

[0149] Shared digital ports mean that the terminal's baseband digital ports are shared among various panels, that is, the number of baseband transmit links of the terminal is less than or equal to the total number of antenna ports of the panel. The baseband transmit link and both panels can be connected and transmitted on different panels dynamically according to each scheduling; the number of baseband transmit links corresponds to the total number of PUSCH ports. For the implementation of 4T+4T, the terminal can implement up to 4 transmit links to support the transmission requirements under S-TRP and M-TRP. As shown in Figure 1D, under S-TRP transmission, the terminal's four baseband digital ports are associated with the antenna ports of panel 0. As shown in Figure 1E, in the M-TRP transmission scenario, the terminal's two baseband digital ports are associated with the two antenna ports of panel 0, and the terminal's two baseband digital ports are associated with the two antenna ports of panel 1.

[0150] Method 2: Separate digital ports

[0151] Independent digital ports mean that the baseband digital ports are not shared between panels. That is, each baseband transmission link of the terminal has a fixed physical connection with different panels.

[0152] In some embodiments, the discussion of STxMP transmission supports PUSCH M-DCI-based SDM / SFN transmission. Considering differences in terminal processing and implementation, two terminal implementation structures are currently under consideration: separate and shared digital ports. However, there is no consensus on the implementation method for shared digital ports.

[0153] Based on this, an embodiment of the present disclosure provides a communication method, which enhances the terminal capabilities so that the terminal supports a shared digital port mode (hereinafter referred to as the first mode) when performing STxMP transmission based on M-DCI, thereby saving terminal costs and achieving efficient STxMP transmission.

[0154] In some embodiments of the present disclosure, terms such as "uplink", "uplink", "physical uplink", etc. can be used interchangeably, and terms such as "downlink", "downlink", "physical downlink", etc. can be used interchangeably.

[0155] In some embodiments of the present disclosure, terms such as "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", and "UL DCI" may be used interchangeably.

[0156] In some embodiments of the present disclosure, terms such as “physical uplink shared channel (PUSCH)” and “UL data” may be used interchangeably.

[0157] It is worth noting that the terminal in the embodiment of the present disclosure supports the STxMP transmission scheme, which will not be further described in the following embodiments of the present disclosure.

[0158] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0159] Step S2101 , the terminal 101 sends first information to the network device 102 .

[0160] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0161] In some embodiments, a network device receives first information.

[0162] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0163] In some embodiments, the first information is used to indicate whether the terminal supports the first mode. Optionally, the first information indicates whether the terminal supports the first mode using one bit. For example, if the bit value is 0, the terminal supports the first mode; if the bit value is 1, the terminal does not support the first mode.

[0164] In some embodiments, the name of the first information is not limited, and it can be, for example, "capability information" or "terminal information".

[0165] In some embodiments, the first information may be carried in RRC signaling. In some embodiments, the first information may be carried in terminal capability information (UE Capability Information).

[0166] In some embodiments, the first information is used to indicate whether the first mode supports STxMP transmission based on a codebook-based PUSCH.

[0167] In some embodiments, information indicating whether the first mode supports codebook-based PUSCH transmission and information indicating whether the terminal supports the first mode are carried in a first message and sent simultaneously. For example, the first message includes two bits, one bit indicating whether the terminal supports the first mode, and one bit indicating whether the first mode supports codebook-based PUSCH transmission.

[0168] In some embodiments, the information indicating whether the first mode supports codebook-based PUSCH transmission and the information indicating whether the terminal supports the first mode are carried in different messages and sent independently.

[0169] Optionally, the terminal indicates whether the terminal supports the first mode through the first information, and indicates whether the first mode supports the codebook-based PUSCH through the third information.

[0170] For example, the third information indicates, by 1 bit, whether the first mode supports STxMP transmission based on the codebook PUSCH. For example, if the value of this bit is 0, the first mode supports STxMP transmission based on the codebook PUSCH; if the value of this bit is 1, the first mode does not support STxMP transmission based on the codebook PUSCH.

[0171] In some embodiments, the name of the third information is not limited, and it may be, for example, "capability information" or the like.

[0172] Optionally, the first information and the third information are carried in the same message and sent simultaneously, or the first information and the third information are sent independently.

[0173] In some embodiments, the first information is further used to indicate time domain resources and frequency domain resources supported by different PUSCHs for PUSCH transmission by the terminal.

[0174] In some embodiments, the first information is further used to indicate the time domain resource relationship and frequency domain resource relationship supported by different PUSCHs for PUSCH transmission by the terminal.

[0175] In some embodiments, the first information is further used to indicate the overlap of time domain resources and frequency domain resources supported by different PUSCHs for PUSCH transmission by the terminal.

[0176] In some embodiments, taking the first PUSCH and the second PUSCH as an example, the time domain resource overlap between the first PUSCH and the second PUSCH includes at least one of the following: complete overlap of time domain resources; partial overlap of time domain resources; and no overlap of time domain resources.

[0177] The frequency domain resource overlap between the first PUSCH and the second PUSCH includes at least one of the following: complete frequency domain resource overlap; partial frequency domain resource overlap; and no frequency domain resource overlap.

[0178] Optionally, the first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI. Optionally, the terminal sends the first PUSCH and the second PUSCH based on an STxMP transmission scheme.

[0179] Optionally, the first information is used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete overlap. Optionally, the network device configures completely overlapping time domain resources and completely overlapping frequency domain resources for the first PUSCH and the second PUSCH based on the first information, and receives the first PUSCH and the second PUSCH based on the configured time-frequency resources, thereby improving the transmission efficiency of the PUSCH.

[0180] Optionally, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap. Optionally, the network device configures completely overlapping or partially overlapping time domain resources and completely non-overlapping frequency domain resources for the first PUSCH and the second PUSCH based on the first information, and receives the first PUSCH and the second PUSCH based on the configured time-frequency resources, thereby improving the transmission efficiency of the PUSCH.

[0181] Optionally, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap. Optionally, the network device configures completely overlapping time domain resources and partially overlapping frequency domain resources for the first PUSCH and the second PUSCH based on the first information, and receives the first PUSCH and the second PUSCH based on the configured time-frequency resources, thereby improving PUSCH transmission efficiency.

[0182] In some embodiments, the first information may include multiple bits, and the network device determines the overlap of time domain resources and frequency domain resources supported by different PUSCHs based on bit values.

[0183] For example, the first information includes 2 bits, the bit value is 00, and the time domain resources between different PUSCHs are fully overlapped, and the frequency domain resources are fully overlapped; the bit value is 01, and the time domain resources between different PUSCHs are fully overlapped, and the frequency domain resources are completely non-overlapping; the bit value is 10, and the time domain resources between different PUSCHs are partially overlapped, and the frequency domain resources are completely non-overlapping; the bit value is 11, and the time domain resources between different PUSCHs are fully overlapped, and the frequency domain resources are partially overlapped. The embodiment of the present disclosure is only for illustrative purposes. The first information can also indicate the overlap of time domain resources and frequency domain resources supported by different PUSCHs through a bitmap or table, which is not limited in the embodiment of the present disclosure.

[0184] In some embodiments, the information used to indicate the overlap of time domain resources and frequency domain resources between different PUSCHs for PUSCH transmission by the terminal and the information used to indicate whether the terminal supports the first mode are the same message.

[0185] For example, the terminal sends, through the first message, whether the terminal supports the first mode and the overlap of time domain resources and frequency domain resources between different PUSCHs for PUSCH transmission by the terminal.

[0186] In some embodiments, the information used to indicate the overlap of time domain resources and frequency domain resources between different PUSCHs and the information used to indicate whether the terminal supports the first mode are different information.

[0187] For example, the terminal indicates whether the terminal supports the first mode through the first information, and indicates the overlap of time domain resources and frequency domain resources between different PUSCHs for PUSCH transmission to the terminal through the fourth information.

[0188] In some embodiments, the name of the fourth information is not limited, and it can be, for example, "capability information" or "resource information".

[0189] In some embodiments, the first information and the fourth information are carried in the same message and sent simultaneously, or the first information and the fourth information are sent independently.

[0190] In some embodiments, the first information is further used to indicate whether the terminal supports different panels configuring different codebook subsets.

[0191] In some embodiments, the first information is further used to indicate whether the terminal supports different panels to configure different codebook subsets when the terminal performs STxMP transmission based on the codebook PUSCH.

[0192] For example, the codebook subset supported for configuration by panel 1 is a non-coherent codebook subset, and the codebook subset supported for configuration by panel 2 is a partially coherent codebook subset.

[0193] Optionally, the first information indicates, via 1 bit, whether the terminal supports different codebook subsets configured for different panels. For example, if the bit value is 0, the terminal supports different codebook subsets configured for different panels; if the bit value is 1, the terminal does not support different codebook subsets configured for different panels.

[0194] Optionally, the first information indicates whether the terminal supports different codebook subsets configured for different panels by indicating a codepoint. For example, if the codepoint indicated by the first information is 01, the codebook subset supported by panel 1 is a non-coherent codebook subset, and the codebook subset supported by panel 2 is a partially coherent codebook subset. For example, if the codepoint indicated by the first information is 11, the codebook subset supported by panel 1 is a non-coherent codebook subset, and the codebook subset supported by panel 2 is a non-coherent codebook subset.

[0195] In some embodiments, the information indicating whether the terminal supports different panels configured with different codebook subsets is the same information as the information indicating whether the terminal supports the first mode. For example, the terminal simultaneously sends, via the first information, whether the terminal supports the first mode and whether the terminal supports different panels configured with different codebook subsets.

[0196] In some embodiments, the information used to indicate whether the terminal supports different panels configured with different codebook subsets is different from the information used to indicate whether the terminal supports the first mode.

[0197] For example, the terminal indicates whether the terminal supports the first mode through the first information, and indicates whether the terminal supports different panels to configure different codebook subsets through the fifth information.

[0198] In some embodiments, the name of the fifth information is not limited, and it can be, for example, "capability information" or "codebook subset information".

[0199] In some embodiments, the fifth information is carried in the same message as the first information. Optionally, the first information and the fifth information are carried in the same message and sent simultaneously. Alternatively, the first information and the fifth information are sent independently.

[0200] In some embodiments, the first information is further used to indicate whether the terminal supports configuring SRS resources with different port numbers in one SRS resource set.

[0201] Optionally, the first information indicates, via one bit, whether the terminal supports configuring SRS resources with different numbers of ports in one SRS resource set. For example, if the value of this bit is 0, the terminal supports configuring SRS resources with different numbers of ports in one SRS resource set; if the value of this bit is 1, the terminal does not support configuring SRS resources with different numbers of ports in one SRS resource set.

[0202] Optionally, when the terminal supports configuring SRS resources with different port numbers in one SRS resource set, the first information may further indicate the port number of the SRS resources configured in one SRS resource set.

[0203] In some embodiments, the network device determines based on the first information that the terminal supports SRS resources with different port numbers configured in an SRS resource set, as well as the port number of SRS resources configured in an SRS resource set, and configures an SRS resource set for the terminal based on RRC signaling, and the port number of SRS resources included in one SRS resource set is different.

[0204] Optionally, different numbers of ports are configured for different SRS resources according to the index of the SRS resource. For example, the SRS resource with an index of 1 corresponds to 4 ports, and the SRS resource with an index of 2 corresponds to 2 ports.

[0205] Optionally, different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / CoresetPoolIndex.

[0206] Optionally, SRS resources with different numbers of ports in the same SRS resource set may correspond to different transmission schemes. For example, SRS resources with 4 ports in an SRS resource set are used for S-TRP transmission, and SRS resources with 2 ports are used for STxMP transmission.

[0207] Optionally, the information used to indicate whether the terminal supports configuring SRS resources with different numbers of ports in the same SRS resource set is the same information as the information used to indicate whether the terminal supports the first mode. For example, the terminal simultaneously sends, via the first information, whether the terminal supports the first mode and whether the terminal supports configuring SRS resources with different numbers of ports in the same SRS resource set.

[0208] Optionally, the information used to indicate whether the terminal supports configuring SRS resources with different numbers of ports in the same SRS resource set is different from the information used to indicate whether the terminal supports the first mode. For example, the terminal indicates whether it supports the first mode through the first information, and indicates whether it supports configuring SRS resources with different numbers of ports in the same SRS resource set through the sixth information.

[0209] Optionally, the name of the sixth information is not limited, and it can be, for example, "capability information" or "port information".

[0210] Optionally, the sixth information is carried in the same message as the first information. Optionally, the first information and the sixth information are carried in the same message and sent simultaneously. Alternatively, the first information and the sixth information are sent independently.

[0211] In some embodiments, the first information is further used to indicate the total number of SRS resource sets supported for configuration by the terminal.

[0212] In some embodiments, the first information is used to perform STxMP transmission based on a non-codebook PUSCH at the terminal, indicating the total number of SRS resource sets supported by the terminal.

[0213] In some embodiments, the first information includes a field for indicating the total number of SRS resource sets supported for configuration by the terminal, and the number carried in the field indicates the total number of SRS resource sets supported for configuration by the terminal.

[0214] Optionally, the total number of SRS resource sets supported for configuration by the terminal is 2 or 4.

[0215] Optionally, the terminal supports configuring 2 SRS resource sets for each panel / TRP / TCI state. Different SRS resource sets correspond to different transmission schemes of the terminal. The total number of SRS resource sets supported by the terminal is 4.

[0216] Optionally, the terminal supports configuring one SRS resource set for each panel / TRP / TCI state. The same SRS resource set is used for different transmission schemes of the terminal. Then the total number of SRS resource sets supported by the terminal is 2.

[0217] In some embodiments, when the number of SRS resource sets configured by the terminal is 2, the fifth information is further used to indicate the maximum number of SRS resources included in each SRS resource set.

[0218] Optionally, when the number of SRS resource sets configured in the terminal is 2, the SRS resources in each SRS resource set correspond to different transmission schemes.

[0219] Optionally, the maximum number of SRS resources included in each SRS resource set is determined based on the maximum number of transmission layers for S-TRP transmission performed by the terminal and the maximum number of transmission layers for STxMP transmission performed by the terminal.

[0220] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of layer transmissions for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3.

[0221] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4.

[0222] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5.

[0223] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

[0224] Optionally, the information indicating the total number of SRS resource sets supported by the terminal is the same as the information indicating whether the terminal supports the first mode. For example, the terminal simultaneously sends whether the terminal supports the first mode and the total number of SRS resource sets supported by the terminal through the first information.

[0225] Optionally, the information used to indicate the total number of SRS resource sets supported by the terminal is different from the information used to indicate whether the terminal supports the first mode. For example, the terminal indicates whether the terminal supports the first mode through the first information and indicates the total number of SRS resource sets supported by the terminal through the seventh information.

[0226] Optionally, the name of the seventh information is not limited, and it can be, for example, "capability information" or "port information".

[0227] Optionally, the seventh information and the first information are carried in the same information. Optionally, the first information and the seventh information are carried in the same information and sent simultaneously. Alternatively, the first information and the seventh information are sent independently.

[0228] Step S2102: The terminal sends second information to the network device.

[0229] In some embodiments, the network device receives the second information.

[0230] In some embodiments, the terminal supports a first mode in which different SRS resource sets cannot be sent simultaneously through different panels and can only be sent in a time-division manner. Optionally, the terminal needs to switch between different panels on the antenna port that sends different SRS resources. In this case, the terminal needs to report the time of switching between different panels.

[0231] Optionally, the second information is used to instruct the terminal to send a time interval (GAP) that actually needs to be reserved between SRS resource sets to different panels based on the first mode.

[0232] Optionally, the time interval corresponds to a time unit including a symbol (OFDM), a time slot, and a subslot. Optionally, the terms "moment", "time point", "time", and "time position" can be used interchangeably, and the terms "duration", "period", "time window", "window", and "time" can be used interchangeably.

[0233] In some embodiments, the time interval is predefined in the protocol. Alternatively, the time interval is sent by the terminal to the network device and then configured by the network device.

[0234] In some embodiments, the name of the second information is not limited, and it can be, for example, "time domain information", "capability information", "GAP value", etc.

[0235] In some embodiments, the second information is used to instruct the terminal to send the minimum GAP or the maximum GAP reserved between SRS resource sets to different panels based on the first mode.

[0236] Optionally, the second information is further used to indicate parameters for determining the GAP. The network device determines the actual GAP value based on the minimum GAP or the maximum GAP and the parameters for determining the GAP. For example, the GAP value of the terminal is different under different modulation modes.

[0237] In some embodiments, the time interval at which the terminal sends the SRS resource set to different panels based on the first mode is a preset value.

[0238] Optionally, the terminal does not send the second information to the network device, and the preset value is 0. The time interval for the terminal to send the SRS resource set to different panels based on the first mode is 0, that is, the terminal continuously sends the SRS resource set.

[0239] Optionally, the terminal does not send the second information to the network device, and the preset value is based on a protocol provision.

[0240] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2102. For example, step S2101 may be implemented as an independent embodiment, and step S2102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0241] In some embodiments, steps S2101 and S2102 may be executed in an interchanged order or simultaneously.

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

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

[0244] In some embodiments, if the capabilities of the terminal change, the first information need only carry information corresponding to the changed capabilities. For example, if the terminal's capability changes from supporting codebook-based PUSCH for STxMP transmission to not supporting codebook-based PUSCH for STxMP transmission, the terminal may send first information to indicate that the first mode does not support codebook-based PUSCH for STxMP transmission. For another example, if the total number of SRS resource sets supported by the terminal changes, the terminal may send first information to indicate the total number of SRS resource sets supported by the terminal.

[0245] In some embodiments, the first information indicates some capabilities of the terminal, and the other capabilities of the terminal may be determined based on a protocol or predefined. For example, if the first information only indicates that the terminal supports the first mode, the network device defaults to the terminal using the first mode to support codebook-based or non-codebook PUSCH transmission.

[0246] In some embodiments, when the terminal capability changes, the terminal sends the first information.

[0247] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0248] FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a communication method, which includes:

[0249] Step S3101, sending the first information.

[0250] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0251] In some embodiments, the terminal 101 sends the first information to the network device 102, but is not limited thereto and the first information may also be sent to other entities.

[0252] In some embodiments, the first information is used by the network device 102 to determine whether the terminal 101 supports the first mode.

[0253] Step S3102, sending the second information.

[0254] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0255] In some embodiments, the terminal 101 sends the second information to the network device 102, but is not limited thereto and the second information may also be sent to other entities.

[0256] In some embodiments, the second information is used by the network device 102 to determine the time interval that actually needs to be reserved between the terminal 101 sending SRS resource sets to different antenna panels based on the first mode.

[0257] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3102. For example, step S3101 may be implemented as an independent embodiment, and step S3102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0258] In some embodiments, steps S3101 and S3102 may be executed in an interchanged order or simultaneously.

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

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

[0261] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0262] Step S3201, sending the first message

[0263] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0264] In some embodiments, the first information is used to indicate whether the terminal supports the first mode, and the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal performs uplink multi-antenna panel simultaneous transmission STxMP transmission based on multiple downlink control information M-DCI.

[0265] In some embodiments, the first information is further used to indicate whether codebook-based and / or non-codebook PUSCH transmission is supported under the STxMP transmission scheme.

[0266] In some embodiments, the first information is also used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is also used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; wherein, the first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; wherein, the terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

[0267] In some embodiments, the first information is further used to indicate that time domain resources between the first PUSCH and the second PUSCH support complete overlap, and frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

[0268] In some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

[0269] In some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

[0270] In some embodiments, when codebook-based PUSCH transmission is supported, the first information is further used to indicate whether the terminal supports different panels to configure different codebook subsets.

[0271] In some embodiments, when codebook-based PUSCH transmission is supported, the first information is also used to indicate whether the terminal supports configuring SRS resources with different port numbers in the same SRS resource set, and SRS resources with different port numbers correspond to different transmission schemes of the terminal, and different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes CoresetPoolIndex.

[0272] In some embodiments, when non-codebook-based PUSCH transmission is supported, the first information is further used to indicate the total number of SRS resource sets supported for configuration by the terminal.

[0273] In some embodiments, when the number of SRS resource sets configured by the terminal is 2, the first information is further used to indicate the maximum number of SRS resources included in each SRS resource set.

[0274] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

[0275] In some embodiments, the method further includes: sending second information, where the second information is used to indicate a reserved time interval between the sending of SRS resource sets to different panels by the terminal based on the first mode.

[0276] In some embodiments, the time interval between the terminal sending the SRS resource sets to different panels based on the first mode is a preset value.

[0277] In the embodiment of the present disclosure, step S3201 may be combined with step S3102 of FIG. 3A .

[0278] FIG4A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0279] Step S4101, obtain first information.

[0280] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0281] In some embodiments, the network device 102 receives the first information sent by the terminal 101, but is not limited thereto and may also receive the first information sent by other entities.

[0282] In some embodiments, the network device 102 performs processing to obtain the first information.

[0283] In some embodiments, step S4101 is omitted, and the network device 102 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0284] Optionally, the first information is used to indicate whether the terminal 101 supports the first mode. For optional implementations, please refer to the optional implementations of step S2101 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0285] Step S4102, obtaining second information.

[0286] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0287] In some embodiments, the network device 102 receives the second information sent by the terminal 101, but is not limited thereto and may also receive the second information sent by other entities.

[0288] In some embodiments, the network device 102 performs processing to obtain the second information.

[0289] In some embodiments, step S4102 is omitted, and the network device 102 autonomously implements the function indicated by the second information, or the above function is default or by default.

[0290] Optionally, the first information is used to indicate the time interval reserved between the SRS resource sets sent by the terminal 101 to different panels based on the first mode. Optional implementations thereof can be found in the optional implementations of step S2102 of FIG. 2 and other related parts of the embodiment involved in FIG.

[0291] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0292] In some embodiments, steps S4101 and S4102 may be executed in an interchanged order or simultaneously.

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

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

[0295] FIG4B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0296] Step S4201, receiving first information.

[0297] The optional implementation of step S4201 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0298] In some embodiments, the first information is used to indicate whether the terminal supports the first mode, and the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes the uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

[0299] The first information is also used to indicate whether codebook-based and / or non-codebook PUSCH transmission is supported under the STxMP transmission scheme.

[0300] In some embodiments, the first information is also used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is also used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; wherein, the first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; wherein, the terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

[0301] In some embodiments, the first information is further used to indicate that time domain resources between the first PUSCH and the second PUSCH support complete overlap, and frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

[0302] In some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

[0303] In some embodiments, the first information is further used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

[0304] In some embodiments, when codebook-based PUSCH transmission is supported, the first information is further used to indicate whether the terminal supports different panels to configure different codebook subsets.

[0305] In some embodiments, when codebook-based PUSCH transmission is supported, the first information is also used to indicate whether the terminal supports configuring SRS resources with different port numbers in the same SRS resource set, SRS resources with different port numbers correspond to different transmission schemes of the terminal, and different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes.

[0306] In some embodiments, when non-codebook based PUSCH transmission is supported, the first information is used to indicate the total number of SRS resource sets supported for configuration by the terminal.

[0307] In some embodiments, when the number of SRS resource sets configured by the terminal is 2, the first information is further used to indicate the maximum number of SRS resources included in each SRS resource set.

[0308] In some embodiments, the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or the maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or the maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

[0309] In some embodiments, the method further comprises:

[0310] Second information is sent, where the second information is used to instruct the terminal to send a reserved time interval between SRS resource sets to different panels based on the first mode.

[0311] In some embodiments, the time interval between the terminal sending the SRS resource sets to different panels based on the first mode is a preset value.

[0312] FIG5A is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0313] Step S5101: Terminal 101 sends first information to network device 102.

[0314] The optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3A, step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2, 3A, and 4A, which will not be repeated here.

[0315] In some embodiments, the first information is used to indicate that the terminal supports a first mode, and the first mode indicates that a baseband digital port of the terminal is shared among digital ports of various panels.

[0316] In some embodiments, the first information is further used to indicate SRS resource set information supported by the terminal.

[0317] Optionally, in a case where the terminal supports codebook-based PUSCH transmission, the SRS resource set information includes whether the terminal supports configuring SRS resources with different port numbers in one SRS resource set.

[0318] Optionally, in a case where the terminal supports codebook-based PUSCH transmission, the SRS resource set information includes the total number of SRS resource sets supported by the terminal.

[0319] In step S5102 , the network device 102 sends RRC signaling, activation signaling, or deactivation signaling to the terminal 101 .

[0320] In some embodiments, the RRC signaling, activation signaling, or deactivation signaling includes a first configuration.

[0321] Optionally, the first configuration is used to configure an SRS resource set.

[0322] Step S5103 : Terminal 101 sends an SRS resource set to network device 102 .

[0323] In step S5104, the network device 102 estimates the channel state information based on the SRS resource set.

[0324] Step S5105: The network device 102 sends M-DCI to the terminal 101.

[0325] In step S5106, the terminal 101 sends a PUSCH based on the M-DCI.

[0326] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0327] The present disclosure also provides a communication method, as described below:

[0328] How to enhance the terminal capability definition to support the shared digital ports implementation for STxMP transmission? The specific terminal capability definitions that need to be enhanced for M-DCI implementation include at least one of the following:

[0329] In some embodiments, terminal capability reporting corresponding to codebook-based PUSCH transmission:

[0330] In one implementation, M-DCI PUSCH+PUSCH STxMP transmission based on CB using shared digital ports mode is supported, corresponding to complete overlap of time and frequency domain resources between PUSCHs;

[0331] In one implementation, M-DCI PUSCH+PUSCH STxMP transmission based on CB using shared digital ports mode is supported, corresponding to overlapping / partial overlapping of time-frequency resources between PUSCHs, and no overlap of frequency domain resources;

[0332] In one embodiment, M-DCI PUSCH+PUSCH STxMP transmission based on CB using shared digital ports mode is supported, corresponding to complete overlap of time-frequency resources between PUSCHs and partial overlap of frequency domain resources;

[0333] In one embodiment, whether M-DCI SDM / SFN transmission based on CB using shared digital ports mode supports different coherence capabilities for different panels

[0334] In one embodiment, it supports configuring SRS resources with different numbers of SRS ports in the same SRS resource set when using the shared digital ports mode based on CB transmission;

[0335] In some embodiments, the terminal capability reporting corresponding to the non-codebook PUSCH transmission

[0336] In one implementation, M-DCI PUSCH+PUSCH STxMP transmission based on NCB using shared digital ports mode is supported, corresponding to complete overlap of time and frequency domain resources between PUSCHs;

[0337] In one embodiment, the shared digital ports mode is used to support M-DCI PUSCH+PUSCH STxMP transmission based on NCB, corresponding to overlapping / partial overlapping of time-frequency resources between PUSCHs, and no overlap of frequency domain resources;

[0338] In one embodiment, M-DCI PUSCH+PUSCH STxMP transmission based on NCB using shared digital ports mode is supported, corresponding to complete overlap of time-frequency resources between PUSCHs and partial overlap of frequency domain resources;

[0339] In one embodiment, the configuration of associated CSI-RS resources for STxMP transmission based on NCB using shared digital ports mode is supported;

[0340] In one embodiment, the total number of configured SRS resource sets supported by NCB-based M-DCI PUSCH+PUSCH STxMP transmission is {2, 4}

[0341] In one implementation, the total number of SRS resource sets configured for M-DCI SDM / SFN transmission based on NCB is supported: {2, 4}.

[0342] Optionally, if the number of SRS resource sets corresponding to the reported NCB-based M-DCI SDM / SFN transmission is 2, the maximum number of SRS resources contained in each SRS resource set actually supported is reported at the same time; {3, 4, 5, 6}, specifically corresponding to the cases where the S-TRP maxRank configuration is 2 and 4 respectively, and the STxMP maxRank is 1 or 2;

[0343] In some embodiments, time domain GAP capability reporting:

[0344] In this mode, different SRS resource sets cannot be sent simultaneously through different panels, and can only be sent in time domain. For some terminals, it may be necessary to switch antenna ports between panels. Here, the processing capability of the terminal is reported.

[0345] In some embodiments, the reporting terminal uses a shared digital ports mode to send the minimum GAP value between SRS resource sets.

[0346] Optionally, configure the default value to 0;

[0347] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0348] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may 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 the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein 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 within the device or a memory 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 realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by 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 by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0349] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. 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 and implementing the hardware circuit configuration 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.

[0350] Figure 6A is a structural diagram of the terminal proposed in an embodiment of the present disclosure. As shown in Figure 6A, the terminal 6100 may include: a transceiver module 6101. In some embodiments, the above-mentioned transceiver module is used to send a first information, and the first information is used to indicate whether the terminal supports a first mode, and the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information. Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step S2102, but not limited to this) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0351] Figure 6B is a structural diagram of the network device proposed in an embodiment of the present disclosure. As shown in Figure 6B, the network device 6200 may include: a transceiver module 6201. In some embodiments, the above-mentioned transceiver module is used to receive first information, and the first information is used to indicate whether the terminal supports the first mode, and the first mode indicates that the baseband digital port of the terminal is shared between the digital ports of each antenna panel panel; wherein the terminal performs uplink multi-antenna panel simultaneous transmission STxMP transmission based on multiple downlink control information. Optionally, the above-mentioned transceiver module is used to perform at least one of the communication steps such as sending and / or receiving (for example, step S2102, but not limited to this) performed by the network device 102 in any of the above methods, which will not be repeated here.

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

[0353] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0354] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0355] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., 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. The communication device 7100 is used to perform any of the above methods.

[0356] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0357] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2102, but not limited thereto), and the processor 7101 performs at least one of the other steps (e.g., step S2102, but not limited thereto).

[0358] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0359] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0360] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 8A. 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 a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0361] 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0362] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.

[0363] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.

[0364] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method, such as step S2102, but not limited to this), and the processor 7201 performs other steps, such as at least one of the steps S2102, but not limited to this.

[0365] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0366] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0367] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0368] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0369] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: The method comprises: Sending first information, where the first information is used to indicate whether the terminal supports a first mode, where the first mode indicates that a baseband digital port of the terminal is shared between digital ports of each antenna panel; The terminal executes a multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

2. The method according to claim 1, characterized in that The first information is also used to indicate that codebook-based and / or non-codebook PUSCH transmission is supported under the STxMP transmission scheme.

3. The method according to claim 1 or 2, characterized in that: The first information is further used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is further used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; The first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; The terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

4. The method according to any one of claims 1 to 3, characterized in that The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

5. The method according to any one of claims 1 to 3, characterized in that: The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

6. The method according to any one of claims 1 to 3, characterized in that: The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

7. The method according to any one of claims 1 to 6, characterized in that: In the case of supporting codebook-based PUSCH transmission, the first information is further used to indicate whether the terminal supports configuring different codebook subsets for different panels.

8. The method according to any one of claims 1 to 7, characterized in that When supporting codebook-based PUSCH transmission, the first information is also used to indicate whether the terminal supports configuring SRS resources with different port numbers in one SRS resource set, the SRS resources with different port numbers correspond to different transmission schemes of the terminal, and the different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes CoresetPoolIndex.

9. The method according to any one of claims 1 to 6, characterized in that: In the case of supporting non-codebook based PUSCH transmission, the first information is further used to indicate the total number of SRS resource sets supported for configuration by the terminal.

10. The method according to claim 9, characterized in that When the number of SRS resource sets configured by the terminal is 2, the first information is also used to indicate the maximum number of SRS resources included in each SRS resource set.

11. The method according to claim 10, characterized in that The maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or The maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or The maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or The maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: Sending second information, where the second information is used to indicate a time interval reserved between sending SRS resource sets to different panels by the terminal based on the first mode.

13. The method according to any one of claims 1 to 12, characterized in that The time interval between when the terminal sends SRS resource sets to different panels based on the first mode is a preset value.

14. A communication method, characterized in that: The method comprises: receiving first information, where the first information is used to indicate whether the terminal supports a first mode, where the first mode indicates that a baseband digital port of the terminal is shared between digital ports of each antenna panel; The terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

15. The method according to claim 14, characterized in that The first information is also used to indicate whether codebook-based and / or non-codebook PUSCH transmission is supported under the STxMP transmission scheme.

16. The method according to claim 14 or 15, characterized in that The first information is further used to indicate the time domain resources and / or frequency domain resources of the first PUSCH and the second PUSCH; or, the first information is further used to indicate the time domain resource relationship and / or frequency domain resource relationship between the first PUSCH and the second PUSCH; The first PUSCH and the second PUSCH are PUSCHs scheduled by M-DCI; The terminal sends the first PUSCH and the second PUSCH based on the STxMP transmission scheme.

17. The method according to any one of claims 14 to 16, characterized in that The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete overlap.

18. The method according to any one of claims 14 to 16, characterized in that The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap or partial overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support complete non-overlap.

19. The method according to any one of claims 14 to 16, characterized in that The first information is also used to indicate that the time domain resources between the first PUSCH and the second PUSCH support complete overlap, and the frequency domain resources between the first PUSCH and the second PUSCH support partial overlap.

20. The method according to any one of claims 14 to 19, characterized in that In the case of supporting codebook-based PUSCH transmission, the first information is further used to indicate whether the terminal supports different panels configuring different codebook subsets.

21. The method according to any one of claims 14 to 20, characterized in that When supporting codebook-based PUSCH transmission, the first information is also used to indicate whether the terminal supports configuring SRS resources with different port numbers in one SRS resource set, the SRS resources with different port numbers correspond to different transmission schemes of the terminal, and the different SRS resource sets correspond to PUSCH transmissions associated with different TRP / panel / TCI states / control resource set pool indexes.

22. The method according to any one of claims 14 to 19, characterized in that In the case of supporting non-codebook based PUSCH transmission, the first information is used to indicate the total number of SRS resource sets supported for configuration by the terminal.

23. The method according to claim 22, characterized in that When the number of SRS resource sets configured by the terminal is 2, the first information is also used to indicate the maximum number of SRS resources included in each SRS resource set.

24. The method according to claim 23, characterized in that The maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 3; or The maximum number of transmission layers for S-TRP transmission by the terminal is 2, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 4; or The maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 1, and the maximum number of SRS resources included in each SRS resource set is 5; or The maximum number of transmission layers for S-TRP transmission by the terminal is 4, the maximum number of transmission layers for STxMP transmission by the terminal is 2, and the maximum number of SRS resources included in each SRS resource set is 6.

25. The method according to any one of claims 14 to 24, characterized in that The method further comprises: Sending second information, where the second information is used to indicate a time interval reserved between sending SRS resource sets to different panels by the terminal based on the first mode.

26. The method according to any one of claims 14 to 25, characterized in that The time interval between when the terminal sends SRS resource sets to different panels based on the first mode is a preset value.

27. A communication method, characterized in that: The method comprises: The terminal sends first information to the network device, where the first information is used to indicate that the terminal supports a first mode, where the first mode indicates that a baseband digital port of the terminal is shared between digital ports of each antenna panel panel, and the first information is also used to indicate SRS resource set information supported by the terminal; The network device sends RRC signaling, activation signaling, or deactivation signaling to the terminal, where the RRC signaling, activation signaling, or deactivation signaling includes a first configuration, where the first configuration is used to configure an SRS resource set; The terminal sends an SRS resource set to the network device; The network device estimates the channel state information based on the SRS resource set; The network device sends multiple downlink control information M-DCI to the terminal; The terminal sends a physical uplink shared channel PUSCH based on the M-DCI.

28. The method according to claim 27, characterized in that In the case where the terminal supports codebook-based PUSCH transmission, the SRS resource set information includes whether the terminal supports configuring SRS resources with different port numbers in one SRS resource set.

29. The method according to claim 27, characterized in that In the case where the terminal supports codebook-based PUSCH transmission, the SRS resource set information includes the total number of SRS resource sets supported by the terminal.

30. A terminal, characterized in that: include: A transceiver module, used for sending first information, where the first information is used for indicating whether the terminal supports a first mode, where the first mode indicates that a baseband digital port of the terminal is shared among digital ports of each antenna panel panel; The terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

31. A network device, characterized in that: include: A transceiver module, configured to receive first information, wherein the first information is used to indicate whether the terminal supports a first mode, wherein the first mode indicates that a baseband digital port of the terminal is shared between digital ports of each antenna panel panel; The terminal executes an uplink multi-antenna panel simultaneous transmission STxMP transmission scheme based on multiple downlink control information M-DCI.

32. A terminal, characterized in that: include: one or more processors; The processor is used to execute the communication method according to any one of claims 1 to 13.

33. A network device, characterized in that: include: one or more processors; The processor is used to execute the communication method described in any one of claims 14-26.

34. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the communication method according to any one of claims 1 to 13, and the network device is configured to implement the communication method according to any one of claims 14 to 26.

35. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1-13 and 14-26.

Images