WO2025166783A1 - Indication method for uplink transmission scheme, and terminal, network device, system and medium - Google Patents

Abstract

The present disclosure relates to an indication method for an uplink transmission scheme, and a terminal, a network device, a system and a medium. The method comprises: in a downlink STRP and uplink MTRP scenario, sending DCI to a terminal, wherein the DCI is configured to indicate that uplink transmission performed by the terminal is based on an STRP or an MTRP, the MTRP comprises at most three nodes, and the terminal supports uplink reception performed by at most two or three nodes. In the method of the present disclosure, the network device can dynamically indicate to the terminal that the uplink transmission is based on the STRP or the MTRPs, such that the terminal can perform uplink transmission to a plurality of nodes, thereby improving the uplink coverage and throughput.

Description

Uplink transmission scheme indication method, terminal, network equipment, system and medium Technical Field

The present disclosure relates to the field of communication technologies, and in particular to an indication method, terminal, network device, system, and medium for an uplink transmission scheme.

Background Art

In multi-transmission reception point (TRP) transmission, uplink transmission can be enhanced by deploying a single downlink transmission reception point (STRP) and multiple uplink transmission reception points (MTRP). The problem of determining the uplink transmission scheme between different uplink reception cooperation nodes must be solved.

Summary of the Invention

Embodiments of the present disclosure provide an uplink transmission scheme indication method, terminal, network device, system, and medium.

In a first aspect, an embodiment of the present disclosure provides a method for indicating an uplink transmission scheme, which is performed by a network device, and the method includes:

In the downlink STRP and uplink MTRP scenario, downlink control information (DCI) is sent to the terminal, and the DCI is used to indicate whether the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In a second aspect, an embodiment of the present disclosure provides a method for indicating an uplink transmission scheme, which is performed by a terminal, and the method includes:

In the downlink STRP and uplink MTRP scenario, a DCI sent by a network device is received, where the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In a third aspect, an embodiment of the present disclosure provides a network device, including:

The transceiver module is used to send DCI to the terminal in the downlink STRP and uplink MTRP scenarios, where the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes up to three nodes, and the terminal supports uplink reception of up to two nodes or three nodes.

In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

The transceiver module is used to receive the DCI sent by the network device in the downlink STRP and uplink MTRP scenarios, and the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

one or more processors;

The network device is configured to implement the method described in the first aspect.

In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

one or more processors;

The terminal is configured to implement the method described in the second aspect.

In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a network device and a terminal, wherein:

The network device is configured to implement the method according to the first aspect;

The terminal is configured to implement the method described in the second aspect.

In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

In the disclosed embodiment, the network device may dynamically indicate to the terminal that uplink transmission is based on STRP or MTRP, so that the terminal may perform uplink transmission to multiple nodes to improve uplink coverage and throughput.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

FIG1a is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

Figures 1b to 1h are schematic diagrams of multi-TRP scenarios provided according to an embodiment of the present disclosure;

FIG2 is an exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

3a to 3b are exemplary flowcharts of a method according to an embodiment of the present disclosure;

4a to 4b are exemplary flowcharts of a method according to an embodiment of the present disclosure;

FIG5a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG5b is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

FIG6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

FIG6 b is a schematic diagram of a communication device according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide an uplink transmission scheme indication method, terminal, network device, system, and medium.

In a first aspect, an embodiment of the present disclosure provides a method for indicating an uplink transmission scheme, which is performed by a network device, and the method includes:

In the downlink STRP and uplink MTRP scenario, DCI is sent to the terminal, where the DCI is used to indicate whether the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In the above embodiment, the network device can dynamically indicate to the terminal that uplink transmission is based on STRP or MTRP, so that the terminal can uplink transmit to multiple nodes to improve uplink coverage and throughput.

In conjunction with the embodiments of the first aspect, in some embodiments, when a terminal supports uplink reception of up to two nodes, the network device configures three sounding reference signal (SRS) resource sets for the terminal, and the DCI includes a transmission precoding matrix indicator (TPMI) field and two SRS resource indicator (SRI) fields;

When the terminal supports uplink reception of up to three nodes, the network device configures three SRS resource sets for the terminal, and the DCI includes three TPMI fields and three SRI fields.

In the above embodiment, the network device may adjust the number of configured SRS resource sets according to the number of uplink receiving nodes supported by the terminal, and may also adaptably adjust the number of TPMI fields or SRI fields in the DCI.

In combination with the embodiments of the first aspect, in some embodiments, DCI uses uplink DCI, corresponding to DCI format 0_1 or 1_2.

In the above embodiment, the used DCI may be enhanced, and uplink DCI may be used to indicate an uplink transmission scheme.

In conjunction with the embodiments of the first aspect, in some embodiments, at most one of the three SRS resource sets is configured with an associated channel state information reference signal (CSI-RS);

The uplink transmission is non-codebook based transmission.

In the above embodiment, the network device configures a CSI-RS for the master node at most, so that the master node can perform downlink transmission based on the configured CSI-RS.

In combination with the embodiments of the first aspect, in some embodiments, the DCI includes an SRS resource set indication field, and different code points of the SRS resource set indication field are used to indicate that the uplink transmission scheme is STRP or MTRP, and are also used to indicate the association between the transmission configuration indication (TCI) status and the SRS resource set.

In the above embodiment, the network device can dynamically indicate the uplink transmission scheme through the SRS resource set indication field of the DCI. The terminal can know which uplink transmission scheme to use for transmission based on the DCI to improve the uplink coverage performance.

In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

The radio resource control (RRC) signaling is sent to the terminal. The MTRP-based PUSCH transmission configured in the RRC signaling adopts one of the following transmission schemes: time division multiplexing (TDM) transmission scheme, uplink simultaneous transmission from multi-panel (STxMP) single frequency network (SFN) space division multiplexing transmission scheme, or STxMP space division multiplexing (SDM) transmission scheme.

In the above embodiment, the network device may configure a specific transmission scheme of PUSCH transmission of MTRP for the terminal through RRC, so as to instruct the terminal to apply one of the schemes for uplink transmission in an appropriate scenario.

In combination with the embodiments of the first aspect, in some embodiments, the code point corresponding to the SRS resource set indication field includes at least one of the following: a code point used to indicate that the uplink transmission is based on STRP, a code point used to indicate that the uplink transmission is based on MTRP, and a reserved code point.

In the above embodiment, the terminal determines whether to transmit based on STRP or MTRP based on the code point mapping of the enhanced SRS resource set indicator field.

In conjunction with the embodiments of the first aspect, in some embodiments, the SRS resource set indication field includes 3 bits, and the code point corresponding to the 3 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

A code point used to indicate that uplink transmission is based on MTRP and three nodes cooperate to transmit;

A reserved code point;

The transmission scheme is TDM or STxMP SFN.

In the above embodiment, when the transmission scheme is configured as TDM or STxMP SFN, the SRS resource set indication field can be enhanced with 3 bits. Different code points in this field can indicate whether the uplink transmission is based on STRP or MTRP, and can also indicate the SRS resource set associated with the TCI state in each STRP or MTRP transmission. This allows the terminal to determine the appropriate SRS resource set for uplink transmission in multiple TRP uplink transmissions.

In conjunction with the embodiments of the first aspect, in some embodiments, the SRS resource set indication field includes 3 bits, and the code point corresponding to the 3 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

Multiple reserved code points;

Among them, the transmission scheme is STxMP SDM.

In the above embodiment, when the transmission scheme is configured as STxMP SDM, the SRS resource set indicator field can be enhanced with 3 bits. The terminal can determine the appropriate SRS resource set for uplink transmission based on this field during uplink transmission of multiple TRPs.

In conjunction with the embodiments of the first aspect, in some embodiments, the SRS resource set indication field includes 4 bits, and the code point corresponding to the 4 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the two nodes;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted in a coordinated manner by three nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the three nodes;

Multiple reserved code points;

Among them, the transmission scheme is TDM.

In the above embodiment, when the transmission scheme is configured as TDM, the SRS resource set indication field can be enhanced with 4 bits. The terminal can determine the appropriate SRS resource set for uplink transmission based on this field in the uplink transmission of multiple TRPs.

In combination with the embodiments of the first aspect, in some embodiments, the uplink transmission is the transmission of a physical uplink shared channel (Physical Uplink Shared channel, PUSCH).

In the above embodiment, the terminal may determine a PUSCH transmission scheme based on the DCI to perform reasonable uplink transmission.

In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

Receive terminal capability information, where the capability information indicates uplink transmission supported by the terminal.

In the above embodiment, the network device receives the capability information of the terminal to obtain the uplink transmission capability supported by the terminal, so that the network device can perform reasonable configuration according to the capability of the terminal.

In a second aspect, an embodiment of the present disclosure provides a method for indicating an uplink transmission scheme, which is performed by a terminal, and the method includes:

In the downlink STRP and uplink MTRP scenario, a DCI sent by a network device is received, where the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In conjunction with the embodiments of the second aspect, in some embodiments, when the terminal supports uplink reception of a maximum of two nodes, the terminal is configured with three SRS resource sets, and the DCI includes two TPMI fields and two SRI fields;

When the terminal supports uplink reception of up to three nodes, the terminal is configured with three SRS resource sets, and the DCI includes three TPMI fields and three SRI fields.

In combination with the embodiments of the second aspect, in some embodiments, DCI uses uplink DCI, corresponding to DCI format 0_1 or 1_2.

In conjunction with the embodiments of the second aspect, in some embodiments, at most one of the three SRS resource sets is configured with an associated CSI-RS;

The uplink transmission is non-codebook based transmission.

In combination with the embodiments of the second aspect, in some embodiments, the DCI includes an SRS resource set indication field, and different code points of the SRS resource set indication field are used to indicate that the uplink transmission scheme is STRP or MTRP, and are also used to indicate the association relationship between the transmission configuration indication TCI state and the SRS resource set.

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

Receive RRC signaling sent by the network device, and configure MTRP-based PUSCH transmission in the RRC signaling to adopt one of the following transmission schemes: TDM transmission scheme, STxMP SFN transmission scheme, or STxMP SDM transmission scheme.

In conjunction with the embodiment of the second aspect, in some embodiments, the code point corresponding to the SRS resource set indication field includes at least one of the following: Indicates that the uplink transmission is based on the STRP code point. It is used to indicate that the uplink transmission is based on the MTRP code point. It is a reserved code point.

In conjunction with the embodiments of the second aspect, in some embodiments, the SRS resource set indication field includes 3 bits, and the code point corresponding to the 3 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

A code point used to indicate that uplink transmission is based on MTRP and three nodes cooperate to transmit;

A reserved code point;

Among them, the transmission mode is TDM or STxMP SFN.

In conjunction with the embodiments of the second aspect, in some embodiments, the SRS resource set indication field includes 3 bits, and the code point corresponding to the 3 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

Multiple reserved code points;

Among them, the transmission mode is STxMP SDM.

In conjunction with the embodiments of the second aspect, in some embodiments, the SRS resource set indication field includes 4 bits, and the code point corresponding to the 4 bits includes at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the two nodes;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted in a coordinated manner by three nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the three nodes;

Multiple reserved code points;

Among them, the transmission mode is TDM.

In combination with the embodiments of the second aspect, in some embodiments, the uplink transmission is transmission of a physical uplink shared channel PUSCH.

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

Send capability information to the network device. The capability information is used to indicate the uplink transmission supported by the terminal.

In a third aspect, an embodiment of the present disclosure provides a network device, including:

The transceiver module is used to send DCI to the terminal in the downlink STRP and uplink MTRP scenarios, where the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes up to three nodes, and the terminal supports uplink reception of up to two nodes or three nodes.

In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

The transceiver module is used to receive the DCI sent by the network device in the downlink STRP and uplink MTRP scenarios, and the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

one or more processors;

The network device is configured to implement the method described in the first aspect.

In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

one or more processors;

The terminal is configured to implement the method described in the second aspect.

In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a network device and a terminal, wherein:

The network device is configured to implement the method according to the first aspect;

The terminal is configured to implement the method described in the second aspect.

In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

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

In an eleventh 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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

In some embodiments, the terms “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 used interchangeably with “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 The terms "equal to", "not higher than", "lower than", etc. are interchangeable.

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.

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

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

In some embodiments, the term "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.

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

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

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.

FIG1a is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

As shown in FIG. 1 a , a communication system 100 includes a terminal 101 and a network device 102 .

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.

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

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 Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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 wireless fidelity (WiFi) system, but is not limited thereto.

In some embodiments, the technical solution of the present disclosure may be applicable 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 may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

In some embodiments, the access network device may be composed of a centralized unit (CU) and a distributed unit ( The CU-DU structure can be used to split the protocol layers of the access network device. Some functions of the protocol layers are centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or a group of devices, each including all or part of one or more network elements. A 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). Alternatively, a core network device refers to a network element with a specific function, such as an Access Management Function (AMF), a Service Management Function (SMF), and the like.

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 provided by 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 provided by the embodiment of the present disclosure is also applicable to similar technical problems.

The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1 a , or a partial body thereof, but are not limited thereto.

The entities shown in Figure 1a are examples. The communication system may include all or part of the entities in Figure 1a, or may include other entities outside Figure 1a. The number and form of the entities are arbitrary. The connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

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, the fourth generation mobile communication system (4G), the fifth 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), etc. ), Global System for Mobile communications (GSM (registered trademark)), CDMA 2000, 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 using other communication processing methods, and next-generation systems based on them, etc. Furthermore, combinations of multiple systems (for example, combinations of LTE or LTE-A with 5G) may also be applied.

In the disclosed embodiments, in uplink transmission, multi-antenna precoding for the PUSCH supports two different configuration modes: codebook-based transmission and non-codebook-based transmission. The selection of which mode to use can be based on whether reciprocity between the uplink and downlink channels holds. Regardless of the precoding mode, terminal 101 is required to transmit an SRS to facilitate network device 102 to estimate the uplink channel state CSI.

In some embodiments, in codebook-based transmission:

In the codebook-based PUSCH transmission in NR, the terminal 101 needs to be configured with at most one SRS resource set for codebook-based uplink transmission. The SRS resource set can be configured with multiple SRS resources, and the network side will feedback The SRS resource indication (SRI) of the bit is used to select the SRS resource through the SRI indication. Similarly, the network device 102 is based on the measurement of the uplink CSI. Finally, the network determines the TPMI and the transmission layer number indication (Rank Indicator, RI) used for the actual transmission of the terminal and notifies the terminal 101. The data of the terminal 101 in the subsequent uplink transmission needs to be precoded using the PMI and RI specified by the network side. At the same time, the precoded data is mapped to the corresponding antenna port according to the spatial filter SpatialRelationInfo corresponding to the SRS resource indicated by the SRI. Different SRSs will be transmitted using different spatial filters. Therefore, the precoded data of the terminal 101 needs to be filtered by the spatial filter used by the SRS indicated by the SRI. In this way, the transmission of uplink data from a single layer to full rank can be supported.

The following Tables 1-1 to 1-3 exemplify methods for indicating SRI for multiple SRS resources.

Table 1-1 corresponds to the SRI indication of PUSCH transmission based on the codebook when ul-FullPowerTransmission is not configured, or ul-FullPowerTransmission = fullpowerMode1, or ul-FullPowerTransmission = fullpowerMode2, or ul-FullPowerTransmission = fullpower and N _SRS = 2.

Table 1-1

Table 1-2 corresponds to the SRI indication of codebook-based PUSCH transmission when ul-FullPowerTransmission=fullpowerMode2 and N _SRS =3.

Table 1-2

Table 1-3 corresponds to the SRI indication of codebook-based PUSCH transmission when ul-FullPowerTransmission=fullpowerMode2 and N _SRS =4.

Table 1-3

Table 1-4 below provides examples of TPMI indication methods. Table 1-4 shows the signaling indication methods for TPMI and RI for single-layer transmission using four antenna ports as an example, indicating different UE capabilities. Table 1-4 applies to the following situations: if the transform precoder is disabled, the precoding information and layer number information for four antenna ports are displayed, maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured, or ul-FullPowerTransmission is configured as fullpowerMode2 or fullpower.

Table 1-4

Optionally, not all terminals 101 can calibrate their antenna ports to enable coherent transmission. The codebook design for uplink transmission needs to consider the coherent transmission capability of the terminal's antenna. The NR system defines three types of terminal antenna coherent transmission capabilities:

Full Coherent: All antennas of the terminal can transmit coherently;

Partial coherent: Antennas in the same coherent transmission pair of the terminal can transmit coherently, but antennas in the coherent transmission pairs cannot transmit coherently.

Non-coherent: The terminal does not have an antenna for coherent transmission.

Optionally, the NR system allows the network device 102 to configure up to two SRS resources for the terminal 101 for channel detection based on codebook uplink transmission. The two SRS resources contain the same number of SRS antenna ports and have the same time domain type, that is, the two SRS resources are periodic SRS or semi-continuous SRS or non-periodic SRS. The NR system does not support the network device 102 to indicate multiple SRS resources for the terminal for codebook-based uplink transmission. When the network device 102 configures two SRS resources for the terminal 101 for codebook-based uplink transmission, the network device 102 indicates an SRS resource corresponding to TPMI/TRI (transmission precoding indication or transmission rank indication) to the terminal through SRI.

In some embodiments, in non-codebook based transmissions:

For non-codebook based uplink transmission, the terminal 101 sends a capability of the maximum number of SRS resources that can be transmitted simultaneously to the network device 102. Assuming that the network device 102 performs an SRI indication to the terminal 101 in time slot n, the corresponding SRS resource transmission is the most recent SRS transmission before time slot n. The terminal 101 can determine the limitation of the precoding indication according to 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 102 can configure an associated CSI-RS resource for channel measurement for the SRS resource set used for non-codebook based 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.

For non-codebook based uplink transmission, it is generally necessary to measure the CSI-RS configured for downlink. Terminal 101 uses uplink and downlink reciprocity to obtain uplink channel information by measuring the downlink signal. The main processes include:

The network, such as the network device 102, configures the associated downlink CSI-RS for non-codebook based transmission for downlink channel sounding by the terminal 101;

Terminal 101 selects a precoding matrix by calculating the downlink channel, and simultaneously transmits SRS in each precoding beam direction on the configured SRS resource set;

The network device 102 performs uplink channel detection on the SRS. The network also schedules resources for the terminal 101 and notifies the terminal 101 via downlink signaling. The network also selects a beam in the precoding matrix using an SRI indication.

Terminal 101 uses the modified precoding matrix to determine the actual precoding and the number of allowed layers for PUSCH transmission. Terminal 101 determines the precoding indication limit based on the higher-layer parameter maxRank, and 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 terminal 101, for non-codebook-based transmission, the network needs to configure an SRS resource set for terminal 101.

Optionally, for a non-codebook transmission scheme, the network device 102 may configure one SRS resource set for the terminal 101, comprising 1 to 4 SRS resources, each of which comprises one SRS port. When the network device 102 configures multiple SRS resources for the terminal 101 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 102 may indicate to the terminal 101 through SRI that one or more SRS resources are used for determination of PUSCH precoding, and the number of SRS resources corresponding to the SRI is the number of streams transmitted by the PUSCH. When the network device 102 configures only one SRS resource for the terminal 101 for non-codebook uplink transmission, the SRI domain is not included in the DCI used for uplink authorization.

The following Tables 1-5 to 1-8 exemplify specific methods for indicating the SRI indication field for non-codebook transmission, where Lmax is the transmission layer limit configured by the network device 102, and the terminal 101 determines the corresponding table of SRI and the number of bits of the SRI indication field based on this parameter configuration.

Table 1-5 is applicable to the SRI indication of non-codebook based PUSCH transmission when L _max =1.

Table 1-5

Table 1-6 is applicable to the SRI indication of non-codebook based PUSCH transmission when L _max =2.

Table 1-6

Table 1-7 is applicable to the SRI indication of non-codebook based PUSCH transmission when L _max =3.

Table 1-7

Table 1-8 is applicable to the SRI indication of non-codebook based PUSCH transmission when L _max =4.

Table 1-8

In the disclosed embodiments, in order to improve the coverage at the cell edge and provide a more balanced quality of service within the service area, multi-point TRP collaboration or simply multi-point collaboration is still an important technical means in the NR system. From the perspective of network morphology, network deployment with a large number of distributed access points plus baseband centralized processing will be more conducive to providing a balanced user experience rate and significantly reduce the latency and signaling overhead caused by handover. With the increase in frequency bands, relatively dense access point deployment is also required from the perspective of ensuring network coverage. In high frequency bands, as the integration of active antenna equipment increases, modular active antenna arrays will be more inclined to be used.

In some embodiments, the antenna array of each TRP can be divided into several relatively independent antenna panels, so the shape and number of ports of the entire array can be flexibly adjusted according to the deployment scenario and business needs. The antenna panels or TRPs can also be connected by optical fiber for more flexible distributed deployment. In the millimeter wave band, as the wavelength decreases, the blocking effect caused by obstacles such as human bodies or vehicles will be more significant. In this case, from the perspective of ensuring the robustness of the link connection, it is also possible to utilize the collaboration between multiple TRPs or panels to transmit or receive from multiple beams at multiple angles, thereby reducing the adverse effects of the blocking effect.

In some embodiments, coordinated multi-point transmission technology can be divided into coherent transmission and incoherent transmission, depending on the mapping relationship between the transmitted signal streams and multiple TRPs or panels. In coherent transmission, each data layer is mapped to multiple TRPs or panels using a weighted vector. In incoherent transmission, each data stream is only mapped to a subset of TRPs or panels. Coherent transmission places higher demands on the synchronization between transmission points and the transmission capacity of the backhaul link, and is therefore more sensitive to many non-ideal factors in real-world deployment conditions. In contrast, incoherent transmission is less affected by these factors.

Optionally, uplink PUSCH transmissions are sent to multiple TRPs of network devices 102. In collaborative transmission using a TDM transmission mode, different repetitions of the same PUSCH message can be sent to different TRPs of network devices 102 at different transmission opportunities (TOs) in the time domain. This method places relatively low demands on the capabilities of terminal 101. Each TO only needs to send PUSCH or PUCCH in the direction of one TRP, does not require support for simultaneous beam transmission, and has a relatively large transmission latency. For the uplink, PUSCH channels for different TRPs may actually traverse channels with significantly different spatial characteristics. Therefore, it is assumed that the spatial reception parameters of PUSCH channels in different transmission directions, such as Quasi Co-Location-type D (QCL-D), are different.

Releases 15 (R15) and 16 did not consider MTRP scenarios, and uplink transmission was based on a single TRP. R17 enhances MTRP uplink transmission under single DCI (S-DCI), such as cooperative transmission under TDM transmission.

In R17's non-codebook and codebook-based MTRP transmissions, 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 MTRP PUSCH repeated transmissions, the DCI format 0_1 or 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.

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 contains only 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 rank among all ranks associated with the first SRI field.

In codebook-based MTRP PUSCH repetitive transmissions, two TPMI fields are indicated in DCI format 0_1 or 0_2. The first TPMI field is identical to the TPMI field in R15/16 (including the TPMI index and number of layers), while 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.

The main enhancement goal of Release 18 is to achieve simultaneous collaborative transmission in multiple TRP directions through multiple antenna panels of the terminal to increase transmission reliability and throughput, while effectively reducing transmission latency under multiple TRPs. However, this requires terminal 101 to have the ability to send multiple beams simultaneously. PUSCH transmission can be based on multiple panels to multiple TRPs scheduled by a single physical downlink control channel (PDCCH), namely S-DCI, as shown in Figure 1b, or it can be based on multiple panels/TRPs scheduled by different PDCCHs, namely multi-DCI (M-DCI), as shown in Figure 1c.

In Figure 1b, a single DCI schedules TPMI1 and TPMI2 directly or indirectly to terminal 101. Terminal 101 uses panel 1 (panel 1) to send one or more layers of uplink data to TRP1 based on TPMI1. Terminal 101 uses panel 2 to send one or more layers of uplink data to TRP2 based on TPMI2. In Figure 1c, TRP1 sends the first DCI to terminal 101 via PDCCH1, scheduling terminal 101 to send PUSCH1 to TRP1 using panel 1. TRP2 sends the second DCI to terminal 101 via PDCCH2, scheduling terminal 101 to send PUSCH2 to TRP2 using panel 2.

Optionally, the above TRP1 and TRP2 can be two TRPs in the same cell, or two TRPs in different cells.

In actual deployments, the links between transmission points may be relatively ideal backhaul links that support high throughput and very low backhaul latency, or they may be non-ideal backhaul links using microwave and relay methods. The M-DCI-based non-coherent-joint transmission (NC-JT) transmission scheme was originally introduced mainly for non-ideal backhaul situations, but this scheme can also be used in ideal backhaul situations.

In R18, the transmission schemes supported by uplink simultaneous transmission STxMP for S-DCI-based PUSCH include:

SDM spatial division multiplexing scheme: As shown in Figure 1d, different parts of a PUSCH TB are transmitted on the same time-frequency resources to two different TRPs through corresponding DMRS ports or port combinations allocated on different panels. Different panels, TRPs, or transmission opportunities (TOs) are associated with different TCI states, i.e., beams.

SFN spatial division multiplexing scheme: As shown in Figure 1e, a PUSCH TB is transmitted on the same time-frequency resources to two different Transmission Point Relays (TRPs) using the same Demodulation Reference Signal (DMRS) port or port combination allocated on different panels. Different panels/TRPs/transmission opportunities (TOs) are associated with different TCI states, or beams.

PUCCH also supports SFN MTRP transmission.

In the disclosed embodiments, downlink beam indication is accomplished by indicating the TCI state to the user. The TCI state is associated with a downlink reference signal, and the user will use the same receive beam as the reference signal to receive data or control information. The beams for each uplink channel or signal are determined by indicating spatial relationship information (SRI) to the UE. The user transmits uplink data using the same beam as the reference signal associated with the spatial information or the SRS corresponding to the SRI. Due to the different uplink and downlink beam management mechanisms, different parameter information must be configured for uplink and downlink beam management, such as the TCI state for downlink beam indication and the spatial relationship information for uplink beam indication.

In R17, a unified TCI framework is designed for uplink beam management and downlink beam management to reduce signaling overhead and increase the flexibility of beam management.

In the unified TCI framework for uplink and downlink in Release 17, two mechanisms are designed for beam indication: joint DL/UL beam indication and separate DL/UL beam indication. For Frequency Range 2 (FR2), terminals are required to support beam correspondence. Generally, the optimal downlink receive beam is also the optimal uplink transmit beam. In this case, joint beam indication is used to indicate a joint TCI state to the user. The associated reference signal indicating QCL Type D information is used to determine both the downlink and uplink transmit beams. However, there are special cases where the optimal downlink beam cannot be considered equivalent to the uplink transmit beam, such as when considering Maximum Permissible Exposure (MPE) or network flexibility. In these cases, separate beam indication is used to indicate the downlink and uplink transmit beams to the user.

In some embodiments, considering the flexibility and complexity of beam information configuration and indication, NR has designed a multi-layer beam indication method. Unified TCI state follows this method, that is, indication is performed through RRC+MAC-CE+DCI. Among them:

The RRC configures or reconfigures a set of reference signal indices to form an optional TCI state resource pool for describing beam characteristics. For uplink, a maximum of 64 TCI states are supported, and for downlink data channels, a maximum of 128 TCI states are supported.

MAC-CE signaling is used to activate or deactivate the TCI state. The activated reference signal indices will be dynamically combined and configured into the associated TCI or reference signal set.

A TCI status code point is indicated through the TCI status indication field in the DL DCI signaling, and up to 8 TCI filling code points can be selected.

In some embodiments, the downlink TCI state or joint TCI state indicated for the terminal 101 in R17 is used to determine the downlink transmission beam, and the indicated uplink TCI state or joint TCI state is used to determine the uplink beam, where the downlink beam refers to the user-specific PDSCH and the beam of all/part of the PDCCH in a carrier CC, and the uplink beam refers to the uplink transmit spatial filter based on the dynamically authorized/configurable authorized PUSCH and all or part of the dedicated PUCCH resources of a CC.

Optionally, a TCI state pool is used for the downlink TCI state and the joint TCI state in the independent beam indication.

Optionally, in the case of joint beam indication, the TCI field only needs to indicate one joint TCI state, which is used to determine both uplink and downlink transmission beams. However, in the case of independent beam indication, the downlink transmission beam and the uplink transmission beam are no longer the same and need to be indicated separately. In addition, there are the following three scenarios: it is necessary to indicate both the downlink transmission beam and the uplink transmission beam for the user, it is only necessary to indicate the downlink transmission beam for the user, and it is only necessary to indicate the uplink transmission beam for the user. For this reason, it is stipulated that in the case of independent beam indication, the mapping relationship between the TCI field and the TCI state in DCI format (formats) 1_1 or 1_2 is as follows:

One code point in the TCI field can correspond to both a downlink TCI state and an uplink TCI state;

One code point in the TCI field corresponds to only one downlink TCI state. In this case, the user maintains the current UL TCI state.

One code point in the TCI field corresponds to only one uplink TCI state. At this time, the user maintains the current DL TCI state unchanged.

In R18, the unified TCI framework is enhanced for MTRP scenarios, and can simultaneously indicate the uplink and downlink TCI state information corresponding to up to two collaborative TRPs through the TCI state code point in the DCI.

In the disclosed embodiments, uplink transmission of multiple TRPs is further enhanced in R19. In the multi-TRP deployment scenario of downlink STRP/uplink MTRP, asymmetric multi-TRP transmission (downlink single TRP/uplink multiple TRPs) can be implemented by deploying heterogeneous networks to improve UL coverage and throughput. The macro node (macro gNB) and micro node UL TRP in the multi-TRP have different power ratings. Terminal 101 can receive DL transmissions from the macro gNB, but transmit UL to the macro gNB or non-co-located micro node UL TRP to maximize UL throughput. As an option to further reduce energy consumption, the micro node can reduce or even shut down DL transmissions. Unlike the small cell node, the cell node is only used for uplink reception (UL only).

Referring to Figures 1f to 1h, Figure 1f illustrates the functions of a macro node, which can perform downlink transmission (DL) and uplink reception (UL). Figures 1g and 1h illustrate the functional differences between a UL-only node and a macro node. A UL-only node can only perform uplink reception (UL), while the macro node performs downlink transmission (DL), and the macro node can perform uplink reception.

Optionally, a backhaul connection may be provided between the macro node and the UL Rx Node, such as in the ideal backhaul scenario. The corresponding UL transmission scheme may include:

STRP scenario:

Select macro gNB, or select an uplink receive TRP (UL TRP).

MTRP scenario:

Option 1 (Alt. 1): select macro gNB and one UL TRP.

Alt.2. Select two UL TRPs;

Alt.3. Select macro gNB and two UL TRPs

In conjunction with the description of the preceding embodiments, in scenarios involving UL-only nodes, a cell includes a master gNB, such as a macro gNB, and multiple UL Transmitted Receiving Points (TRPs). For terminal 101 to perform downlink STRP/MTRP transmission, network device 102 must perform uplink or downlink beam management and ultimately indicate the beam information used for data or signal transmission to the terminal via the existing RRC+MAC-CE+DCI configuration method. Uplink MTRP transmission can be coordinated between the master gNB and the UL TRP, or between different UL TRPs. Determining the possible coordination methods and specific uplink transmission schemes for different channels between different coordinating nodes remains a specific issue that needs to be addressed.

FIG2 is an interactive diagram of a method for indicating an uplink transmission scheme according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for indicating an uplink transmission scheme, the method comprising:

Step S2101 : Terminal 101 sends capability information to network device 102 .

Optionally, the network device 102 may include multiple nodes, such as three nodes. The three nodes may include a master node and two uplink receiving nodes (UL TRPs), and the master node may be a macro gNB.

Optionally, the capability information is used to indicate the uplink transmission supported by the terminal 101, for example, whether the terminal 101 only supports single-point transmission (DPS or STRP); for another example, the terminal 101 supports uplink reception of up to two nodes, or supports uplink reception of up to three nodes.

For example, network device 102 includes three nodes: macro gNB, UL TRP1, and UL TRP2. When terminal 101 supports uplink reception of at most two nodes, the two nodes may be any two of the three nodes included in network device 102. When terminal 101 supports uplink reception of at most three nodes, it supports uplink reception of the three nodes included in network device 102.

In some implementations, in the aforementioned UL only scenario or in the downlink STRP and uplink MTRP scenario, the terminal 101 may execute step S2101 to report the uplink transmission capability supported by itself.

In some embodiments, the terminal may report capability information related to supported PUSCH transmission.

In some embodiments, the network device 102 receives the capability information and may perform corresponding configuration or instructions based on the capability of the terminal 101 .

Optionally, the capability information may also include panel information of the terminal 101. The terminal 101 is generally configured with multiple physical panels, and the capabilities of different panels may also be different. For example, they may have different numbers of SRS ports, and the maximum number of data transmission layers they support may not be the same. For example, one panel supports a maximum of 2 layers of transmission, while another panel supports a maximum of 4 layers of transmission. The scheduler of the network device 102 will determine whether the terminal 101 is currently suitable for simultaneous uplink transmission of multiple panels. If the terminal 101 is currently suitable for simultaneous uplink transmission of multiple panels and is scheduled at the same time, the network will directly or indirectly indicate relevant transmission parameters, including terminal-specific beam indication information, the number of data layers used for transmission, the allocation of DMRS ports used, and precoding indication information, etc.

Step S2102 , the network device 102 sends RRC signaling to the terminal 101 .

Optionally, the MTRP-based PUSCH transmission configured in the RRC signaling adopts one of the following transmission schemes: TDM transmission scheme, STxMP SFN transmission scheme, or STxMP SDM transmission scheme.

In some embodiments, RRC signaling may also be used to configure other information, such as an SRS resource set, TCI status, or power control information.

Step S2103 , the network device 102 sends DCI to the terminal 101 .

Optionally, the DCI is used to indicate whether the uplink transmission of the terminal is based on STRP or MTRP.

Optionally, the network device 102 may send the DCI in a scenario of downlink STRP and uplink MTRP.

In some embodiments, the DCI is used to indicate a transmission scheme of the PUSCH.

In some embodiments, when the uplink transmission is based on STRP, the terminal 101 may transmit uplink to a node, which may be a master node or a macro node macro gNB; or the node may be an uplink receiving node (UL TRP).

In some embodiments, when uplink transmission is based on MTRP, such as when terminal 101 supports uplink reception of up to two or three nodes, terminal 101 may perform uplink transmission to two or three nodes. The two or three nodes may include a master node, or all of them may be UL TRPs.

In some embodiments, when the terminal supports uplink reception of up to two nodes, the network device configures three SRS resource sets for the terminal, and the DCI includes two TPMI fields and two SRI fields;

When the terminal supports uplink reception of up to three nodes, the network device configures three SRS resource sets for the terminal, and the DCI includes three TPMI fields and three SRI fields.

Optionally, each node corresponds to an SRS resource set.

Optionally, each SRI field indicates the SRI for a node. For example, when the DCI includes two SRI fields, 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 rank among all ranks associated with the first SRI field.

Optionally, each TPMI field indicates precoding information for a node. For example, when the DCI includes two TPMI fields, the first TPMI field is used to determine elements in the second TPMI field, and the second TPMI field only includes TPMI associated with the number of layers indicated by the first TPMI field.

In some embodiments, the DCI uses uplink DCI, corresponding to DCI format 0_1 or 1_2.

Optionally, the uplink DCI is DCI used for scheduling uplink.

In some embodiments, at most one of the three SRS resource sets is configured with an associated CSI-RS; wherein the uplink transmission is a non-codebook based transmission.

Optionally, in non-codebook based transmission, a node capable of performing downlink transmission needs to be configured with a CSI-RS.

Optionally, when the nodes supported by terminal 101 for uplink reception include the master node, one of the three SRS resource sets is configured with an associated CSI-RS. If the nodes supported by terminal 101 for uplink reception do not include the master node, the three SRS resource sets may not be configured with an associated CSI-RS.

In some embodiments, the DCI includes an SRS resource set indicator field (SRS resource set indicator). Different code points of the SRS resource set indicator field are used to indicate whether the uplink transmission scheme is STRP or MTRP, and are also used to indicate the association between the transmission configuration indication TCI state and the SRS resource set.

Optionally, each node is configured or indicated with a corresponding TCI state.

Optionally, the code point corresponding to the SRS resource set indication field includes at least one of the following: a code point used to indicate that uplink transmission is based on STRP, a code point used to indicate that uplink transmission is based on MTRP, and a reserved code point.

Optionally, when the uplink transmission scheme is different, the mapping indicated by the SRS resource set indication field is different.

In one example, if the uplink transmission scheme is TDM or STxMP SFN, the SRS resource set indication field may include 3 bits. The code points should include at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

A code point used to indicate that uplink transmission is based on MTRP and three nodes cooperate to transmit;

A reserved code point.

For example, as shown in Table 2-1, codepoints 0 to 2 indicate that the uplink transmission is based on STRP, meaning that a single node is performing uplink reception. The corresponding TCI state for this node is TCI state #1. Different codepoints indicate that the SRS resource set IDs corresponding to TCI state #1 are different. Codepoints 3 to 5 indicate that the uplink transmission is based on MTRP, with two nodes performing uplink reception. The corresponding TCI states for the two nodes are TCI state #1 and TCI state #2, respectively. Different codepoints indicate that the SRS resource set IDs corresponding to the two TCI states are different. Codepoints 6 to 7 are reserved.

Table 2-1

Among them, the two uplink receiving nodes can be recorded as the first TRP (or TRP1) and TRP2, TRP1 corresponds to TCI state#1, and TRP2 corresponds to TCI state#2.

The codepoint in the SRS resource set indicator field determines whether transmission is based on STRP or MTRP. For example, in TDM or STxMP SFN modes, the codepoint can also be used to determine the associated SRI or TPMI field. In STRP, the first SRI/TPMI field can be associated with any SRS resource. In MTRP, the first SRI/TPMI field is associated with the first SRS resource set, and the second SRI/TPMI field is associated with the second SRS resource set.

Table 2-2

Here, “/” represents or.

For another example, as shown in Table 2-3, codepoints 0 to 2 are used to indicate that the uplink transmission is based on STRP transmission, meaning that a single node performs uplink reception. The TCI state corresponding to this node is TCI state #1. Different codepoints indicate that the SRS resource set IDs corresponding to TCI state #1 are different. Codepoints 3 to 5 are used to indicate that the uplink transmission is based on MTRP transmission, with two nodes performing uplink reception. The TCI states corresponding to the two nodes are TCI state #1 and TCI state #2, respectively. Different codepoints indicate that the SRS resource set IDs corresponding to the two TCI states are different. Codepoint 6 is used to indicate that the uplink transmission is based on MTRP transmission, supporting three nodes performing uplink reception. The TCI states corresponding to the three nodes are TCI state #1, TCI state #2, and TCI state #3, respectively. Codepoint 7 is a reserved codepoint.

Table 2-3

Among them, the three uplink receiving nodes can be recorded as TRP1, TRP2 and TRP3, TRP1 corresponds to TCI state#1, TRP2 corresponds to TCI state#2, and TRP3 corresponds to TCI state#3.

Among them, whether the transmission is based on STRP or MTRP is determined based on the code point of the SRS resource set indicator field. As shown in Table 2-4, in TDM or STxMP SFN mode, the associated SRI field or TPMI field can also be determined based on the code point. In STRP, the first SRI/TPMI field can be associated with any SRS resource. In MTRP, the first SRI/TPMI field is associated with the first SRS resource set, and the second SRI/TPMI field is associated with the second SRS resource set. Alternatively, in MTRP corresponding to code point 6, the first SRI/TPMI field is associated with the first SRS resource set, the second SRI/TPMI field is associated with the second SRS resource set, and the third SRI/TPMI field is associated with the second SRS resource set.

Table 2-4

In another example, if the uplink transmission scheme is TDM, the SRS resource set indication field may also include 4 bits. The code points corresponding to the 4 bits include at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the two nodes;

Multiple code points used to indicate that the uplink transmission is based on MTRP and is transmitted in a coordinated manner by three nodes, wherein each of the multiple code points is also used to indicate the uplink reception order of the three nodes;

Multiple reserved code points;

Among them, the transmission scheme is TDM.

Optionally, the TDM scheme needs to indicate the transmission order.

For example, as shown in Table 2-5, compared with the example in Table 2-3, this example supports indicating the uplink reception order. The meaning of the code points can be referred to the description of the corresponding example in Table 2-2. Code points 9 to 11 are used to indicate MTRP transmission that supports uplink reception of three nodes.

Table 2-5

Among them, the three uplink receiving nodes can be recorded as TRP1, TRP2 and TRP3, TRP1 corresponds to TCI state#1, TRP2 corresponds to TCI state#2, and TRP3 corresponds to TCI state#3.

Among them, whether the transmission is based on STRP or MTRP is determined based on the code point of the SRS resource set indicator field. As shown in Table 2-6, the associated SRI field or TPMI field can also be determined based on the code point. In STRP, the first SRI/TPMI field can be associated with any SRS resource. In MTRP, the first SRI/TPMI field is associated with the first SRS resource set, and the second SRI/TPMI field is associated with the second SRS resource set. Alternatively, in MTRP corresponding to code points 9 to 11, the first SRI/TPMI field is associated with the first SRS resource set, the second SRI/TPMI field is associated with the second SRS resource set, and the third SRI/TPMI field is associated with the second SRS resource set.

Table 2-6

In another example, if the transmission scheme is STxMP SDM, the SRS resource set indication field may include 3 bits. The code points corresponding to the 3 bits include at least one of the following:

Used to indicate that the uplink transmission is based on multiple STRP code points, and the TCI states corresponding to the multiple code points have different associations with the SRS resource set;

Multiple code points used to indicate that the uplink transmission is based on MTRP and coordinated transmission between two nodes, where each of the multiple code points is also used to indicate the association between the TCI states corresponding to the two nodes and the three SRS resource sets;

Multiple reserved code points.

For example, as shown in Table 2-7, code points 0 to 2 indicate that the transmission scheme is based on STRP, and code points 3 to 5 indicate that the transmission scheme is based on MTRP.

Table 2-7

Among them, the two uplink receiving nodes can be recorded as TRP1 and TRP2, TRP1 corresponds to TCI state#1, and TRP2 corresponds to TCI state#2.

The codepoint in the SRS resource set indicator field determines whether the transmission is based on STRP or MTRP. As shown in Table 2-8, the codepoint can also be used to determine the associated SRI or TPMI field. In STRP, the first SRI/TPMI field can be associated with any SRS resource. In MTRP, the first SRI/TPMI field is associated with the first SRS resource set, and the second SRI/TPMI field is associated with the second SRS resource set.

Table 2-8

In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", and "field" can be used interchangeably.

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.

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

In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

In some embodiments, terms such as "component carrier (CC)", "cell", "frequency carrier", and "carrier frequency" can be used interchangeably.

In some embodiments, "certain,""preset,""preset,""set,""directed" The terms "indicated", "a certain", "any", "first", etc. can be used interchangeably, and "specific A", "predetermined A", "preset A", "set A", "indicate A", "a certain A", "any A", "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or the first A, etc., but are not limited to this.

In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.

In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and/or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

The method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2103; for example, the method includes step S2103.

In some embodiments, at least one of steps S2101 and S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

FIG3a is a flow chart of a method for indicating an uplink transmission scheme according to an embodiment of the present disclosure. As shown in FIG3a, the embodiment of the present disclosure relates to a method for indicating an uplink transmission scheme, which is executed by the network device 102 and includes:

Step S3101, obtaining capability information.

In some embodiments, the implementation of step S3101 refers to the optional implementation of step S2101 and is not repeated here.

Step S3102, sending RRC signaling.

In some embodiments, the implementation of step S3102 refers to the optional implementation of step S2102 and is not repeated here.

Step S3103, send DCI.

In some embodiments, the implementation of step S3103 refers to the optional implementation of step S2103 and is not repeated here.

The method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3103.

In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 a .

FIG3b is a flow chart of a method for indicating an uplink transmission scheme according to an embodiment of the present disclosure. As shown in FIG3b, the embodiment of the present disclosure relates to a method for indicating an uplink transmission scheme, which is executed by the network device 102 and includes:

Step S3201, send DCI.

In some embodiments, the implementation of step S3201 refers to the optional implementation of step S2103 and is not repeated here.

In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 b .

FIG4a is a flow chart of a method for indicating an uplink transmission scheme according to an embodiment of the present disclosure. As shown in FIG4a, the embodiment of the present disclosure relates to a method for indicating an uplink transmission scheme, which is executed by terminal 101 and includes:

Step S4101: Send capability information.

In some embodiments, the implementation of step S4101 refers to the optional implementation of step S2101 and is not repeated here.

Step S4102: Obtain RRC signaling.

In some embodiments, the implementation of step S4102 refers to the optional implementation of step S2102 and is not repeated here.

Step S4103, obtain DCI.

In some embodiments, the implementation of step S4103 refers to the optional implementation of step S2103 and is not repeated here.

The method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4103.

In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 a .

FIG4b is a flow chart of a method for indicating an uplink transmission scheme according to an embodiment of the present disclosure. As shown in FIG4b , the embodiment of the present disclosure relates to a method for indicating an uplink transmission scheme, which is executed by terminal 101 and includes:

Step S4201, obtain DCI.

In some embodiments, the implementation of step S4201 refers to the optional implementation of step S2102 and is not repeated here.

In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 b .

The present disclosure provides a beam indication method applicable to UL-only scenarios to solve the problem of how to determine the uplink transmission scheme in UL-only scenarios. The specific method is as follows:

Example 1:

Dynamically indicates DPS or MTRP.

Optionally, the terminal capability indicates whether the UE can only support DPS.

Alternatively, DPS may also be referred to as STRP.

Example 2:

Based on Example 1, for the PUSCH transmission scheme, the association relationship between TRP and SRS can be defined.

Optionally, the association between the TCI state and the SRS resource set is indicated by the SRS resource set.

Example 3:

Based on Example 1 and/or Example 2, a method for dynamically switching and indicating between transmission schemes:

The network device supports dynamic collaboration indication between up to 3 TRPs.

The maximum number of nodes supported by the terminal for cooperative transmission is:

1) Maximum is 2

2) Maximum is 3

For PUSCH channel:

Configure 3 SRS resource sets for collaborative TRP configuration

Function is codebook;

In the case of non-codebook function, the configuration restriction is added: at most one resource set in the SRS resource set can be configured with the associated CSI-RS.

For the RRC-configured transmission schemes TDM, STxMP SFN, or STxMP SDM, the SRS resource set indicator is supported using the extensions shown in Tables 2-1 to 2-4, respectively.

Optionally, for the TDM solution, 3 bits may be used for indication, refer to Table 2-1 to Table 2-2, where code point 6 in Table 2-2 is used to support joint reception of 3 nodes at the same time.

Optionally, the TDM scheme can be indicated with 4 bits, see Table 2-3, and also supports the indication of the sending order, where code points 9-1 0 are used to support joint reception of 3 nodes at the same time.

Optionally, STxMP SFN can use a 3-bit indication method in the TDM scheme.

Optionally, the STxMP SDM can be indicated using 3 bits, see Table 2-4.

In the embodiments of the present disclosure, corresponding solutions are considered based on different collaborative node ranges for determining the DPS and MTRP schemes in the UL-only scenario, to support dynamic transmission scheme indication through enhanced MTRP configuration and SRS resource set indicator design.

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.

It should be understood that the division of the various units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or 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 may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits. The above-mentioned hardware circuits may be understood as one or more processors. For example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above-mentioned units or modules may be implemented by designing the logical relationship between the components in the circuit. For another example, in another implementation, the above-mentioned hardware circuit may be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured through a configuration file, thereby implementing the functions of some or all of the above-mentioned units or modules. All units or modules of the above-mentioned devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by the processor calling software, and the remaining part by hardware circuits.

In the embodiment of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor may 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 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 to implement 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 for artificial intelligence. The designed hardware circuit can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.

Figure 5a is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 5a, terminal 5100 may include: at least one of: a transceiver module 5101, a processing module 5102, etc. In some embodiments, the processing module 5102 is configured to receive DCI sent by a network device in a downlink STRP and uplink MTRP scenario, wherein the DCI is configured to indicate whether the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes.

Optionally, the transceiver module 5101 is configured to execute at least one of the communication steps of sending and/or receiving performed by the terminal 101 in any of the above methods, which are not described in detail here. Optionally, the processing module 5102 is configured to execute at least one of the other steps performed by the terminal 101 in any of the above methods, which are not described in detail here.

Figure 5b is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 5b, network device 5200 may include: at least one of: a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is configured to send a DCI to the terminal in a downlink STRP and uplink MTRP scenario, where the DCI is configured to indicate whether the terminal's uplink transmission is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception from a maximum of two nodes or three nodes.

Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps of sending and/or receiving performed by the network device 102 in any of the above methods, which are not described in detail here. Optionally, the processing module 5202 is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

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.

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.

Figure 6a is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 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 implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above methods. Communication device 6100 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.

As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps, such as sending and/or receiving, in the above-described method, and the processor 6101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and/or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface 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.

In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and may be configured to receive data from the memories 6103 or other devices, or to send data to the memories 6103 or other devices. For example, the interface circuits 6104 may read data stored in the memories 6103 and send the data to the processor 6101.

The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6a. 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 and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a car Carrier equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.; (6) Others, etc.

FIG6b is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6b , but the present disclosure is not limited thereto.

The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.

In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and/or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and/or receiving, in the above-described method means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

The modules and/or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and/or devices, which is not limited here.

The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 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 transient storage medium.

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

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.

Industrial Applicability

The network equipment can dynamically instruct the terminal that uplink transmission is based on STRP or MTRP, so that the terminal can transmit uplink to multiple nodes to improve uplink coverage and throughput.

Claims (31)

A method for indicating an uplink transmission scheme, performed by a network device, the method comprising: In the scenario of downlink single transmission receiving point STRP and uplink multiple transmission receiving point MTRP, downlink control information DCI is sent to the terminal, and the DCI is used to indicate whether the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes. The method according to claim 1, wherein When the terminal supports uplink reception of a maximum of two nodes, the network device configures three sounding reference signal SRS resource sets for the terminal, and the DCI includes two transmission precoding matrix indication TPMI fields and two SRS resource indication SRI fields; When the terminal supports uplink reception of a maximum of three nodes, the network device configures three SRS resource sets for the terminal, and the DCI includes three TPMI fields and three SRI fields. The method according to claim 2, wherein The DCI uses uplink DCI, corresponding to DCI format 0_1 or 1_2. The method according to claim 2, wherein At most one of the three SRS resource sets is configured with an associated channel state information reference signal CSI-RS; The uplink transmission is non-codebook based transmission. The method according to claim 2, wherein The DCI includes an SRS resource set indication field, and different code points of the SRS resource set indication field are used to indicate that the uplink transmission scheme is the STRP or the MTRP, and are also used to indicate the association relationship between the transmission configuration indication TCI state and the SRS resource set. The method according to claim 5, wherein the method further comprises: Send radio resource control RRC signaling to the terminal, wherein the MTRP-based PUSCH transmission configured in the RRC signaling adopts one of the following transmission schemes: time division multiplexing TDM transmission scheme, uplink multi-antenna panel simultaneous transmission STxMP single frequency network SFN transmission scheme or STxMP space division multiplexing SDM transmission scheme. The method according to claim 6, wherein The code point corresponding to the SRS resource set indication field includes at least one of the following: a code point used to indicate that the uplink transmission is based on the STRP, a code point used to indicate that the uplink transmission is based on the MTRP, and a reserved code point. The method according to claim 7, wherein The SRS resource set indication field includes 3 bits, and the code points corresponding to the 3 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; Multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is further used to indicate an association between TCI states corresponding to the two nodes and three SRS resource sets; A code point for indicating that the uplink transmission is based on the MTRP and is transmitted in a coordinated manner by three nodes; A reserved code point; Among them, the transmission scheme is TDM or STxMP SFN. The method according to claim 7, wherein The SRS resource set indication field includes 3 bits, and the code points corresponding to the 3 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; Multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is further used to indicate an association between TCI states corresponding to the two nodes and three SRS resource sets; Multiple reserved code points; Among them, the transmission scheme is STxMP SDM. The method according to claim 7, wherein The SRS resource set indication field includes 4 bits, and the code points corresponding to the 4 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is further used to indicate an uplink reception order of the two nodes; multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted in a collaborative manner by three nodes, wherein each of the multiple code points is further used to indicate an uplink reception order of the three nodes; Multiple reserved code points; The transmission scheme is TDM. The method according to any one of claims 1 to 10, wherein The uplink transmission is the transmission of the physical uplink shared channel PUSCH. The method according to any one of claims 1 to 10, wherein the method further comprises: Capability information of the terminal is received, where the capability information is used to indicate uplink transmission supported by the terminal. A method for indicating an uplink transmission scheme, performed by a terminal, the method comprising: In the scenario of downlink single transmission receiving point STRP and uplink multiple transmission receiving point MTRP, the DCI sent by the network device is received, and the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes. The method of claim 13, wherein When the terminal supports uplink reception of a maximum of two nodes, the terminal is configured with three SRS resource sets, and the DCI includes two TPMI fields and two SRI fields; When the terminal supports uplink reception of a maximum of three nodes, the terminal is configured with three SRS resource sets, and the DCI includes three TPMI fields and three SRI fields. The method of claim 14, wherein The DCI uses uplink DCI, corresponding to DCI format 0_1 or 1_2. The method of claim 14, wherein At most one of the three SRS resource sets is configured with an associated CSI-RS; The uplink transmission is non-codebook based transmission. The method of claim 14, wherein The DCI includes an SRS resource set indication field, and different code points of the SRS resource set indication field are used to indicate that the uplink transmission scheme is the STRP or the MTRP, and are also used to indicate the association relationship between the transmission configuration indication TCI state and the SRS resource set. The method of claim 17, further comprising: Receive RRC signaling sent by the network device, where the MTRP-based PUSCH transmission configured in the RRC signaling adopts one of the following transmission schemes: TDM transmission scheme, STxMP SFN transmission scheme or STxMP SDM transmission scheme. The method of claim 18, wherein The code point corresponding to the SRS resource set indication field includes at least one of the following: a code point used to indicate that the uplink transmission is based on the STRP, a code point used to indicate that the uplink transmission is based on the MTRP, and a reserved code point. The method of claim 19, wherein The SRS resource set indication field includes 3 bits, and the code points corresponding to the 3 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; Multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is further used to indicate an association between TCI states corresponding to the two nodes and three SRS resource sets; A code point for indicating that the uplink transmission is based on the MTRP and is transmitted in a coordinated manner by three nodes; A reserved code point; Among them, the transmission mode is TDM or STxMP SFN. The method of claim 19, wherein The SRS resource set indication field includes 3 bits, and the code points corresponding to the 3 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; Multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted collaboratively by two nodes, wherein each of the multiple code points is further used to indicate an association between TCI states corresponding to the two nodes and three SRS resource sets; Multiple reserved code points; Among them, the transmission method is STxMP SDM. The method of claim 19, wherein The SRS resource set indication field includes 4 bits, and the code points corresponding to the 4 bits include at least one of the following: Used to indicate that the uplink transmission is based on multiple code points of the STRP, and the TCI states corresponding to the multiple code points have different association relationships with SRS resource sets; It is used to indicate that the uplink transmission is based on the MTRP and the two nodes cooperate to transmit multiple code points, wherein each of the multiple code points The code point is also used to indicate the uplink reception order of the two nodes; multiple code points for indicating that the uplink transmission is based on the MTRP and is transmitted in a collaborative manner by three nodes, wherein each of the multiple code points is further used to indicate an uplink reception order of the three nodes; Multiple reserved code points; Wherein, the transmission mode is TDM. The method according to any one of claims 13 to 22, wherein The uplink transmission is the transmission of the physical uplink shared channel PUSCH. The method according to any one of claims 13 to 22, wherein the method further comprises: Send capability information to the network device, where the capability information is used to indicate uplink transmission supported by the terminal. A network device, comprising: The transceiver module is used to send DCI to the terminal in a scenario where the downlink single transmission receiving point STRP and the uplink multiple transmission receiving point MTRP are used. The DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes. A terminal, comprising: The transceiver module is used to receive the DCI sent by the network device in the scenario of downlink single transmission receiving point STRP and uplink multiple transmission receiving point MTRP, and the DCI is used to indicate that the uplink transmission of the terminal is based on STRP or MTRP, wherein the MTRP includes a maximum of three nodes, and the terminal supports uplink reception of a maximum of two nodes or three nodes. A network device, comprising: one or more processors; The network device is configured to implement the method according to any one of claims 1 to 12. A terminal, comprising: one or more processors; The terminal is configured to implement the method according to any one of claims 13 to 24. A communication system includes a network device and a terminal, wherein: The network device is configured to implement the method according to any one of claims 1 to 12; The terminal is configured to implement the method according to any one of claims 13 to 24. A storage medium stores instructions, wherein: When the instruction is executed on a communication device, the communication device is caused to perform the method according to any one of claims 1 to 12 or any one of claims 13 to 24. A program product, wherein When the program product is executed by a communication device, the communication device is caused to execute the method according to any one of claims 1 to 12 or any one of claims 13 to 24.