Power control method, and communication apparatus and device

Abstract

The present disclosure relates to a power control method, and a communication apparatus and device. The power control method comprises: a network device sending first configuration information to a terminal, wherein the first configuration information is used for configuring the terminal to support independent SRS power control in a plurality of power control adjustment states. In the embodiments of the present disclosure, a terminal is configured to support independent SRS power control in a plurality of power control adjustment states, such that the SRS power control independent of PUSCH power control is enhanced and extended to support the plurality of power control adjustment states, and the terminal can use different power control adjustment state parameters for power adjustment.

Description

Power control method, communication device and equipment Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a power control method, a communication device, and equipment. Background Art

[0002] The terminal sends a sounding reference signal (SRS), and the network equipment can measure the uplink channel characteristics based on the SRS. The terminal's SRS power control can be independent power control that is not associated with the physical uplink shared channel (PUSCH) power control.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a power control method, a communication device, and a device.

[0005] According to a first aspect of an embodiment of the present disclosure, a power control method is proposed, which is performed by a network device. The method includes:

[0006] First configuration information is sent to a terminal, where the first configuration information is used to configure the terminal to support independent power control of a sounding reference signal (SRS) in multiple power control adjustment states.

[0007] According to a second aspect of an embodiment of the present disclosure, a power control method is proposed, which is performed by a terminal. The method includes:

[0008] First configuration information sent by a network device is received, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0009] According to a third aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0010] The transceiver module is configured to send first configuration information to the terminal, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0011] According to a fourth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0012] The transceiver module is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0013] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0014] one or more processors;

[0015] The communication device is used to execute the method proposed in the first aspect or the second aspect.

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

[0017] According to a seventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method proposed in the first aspect or the second aspect.

[0018] According to an eighth aspect of the embodiments of the present disclosure, a computer program product is proposed, including a computer program, which implements the method proposed in the first aspect or the second aspect when executed by a communication device.

[0019] In the disclosed embodiment, the terminal is configured to support SRS independent power control in multiple power control adjustment states, thereby enhancing and extending SRS power control independent of PUSCH to support multiple power control adjustment states, and the terminal can use different power control adjustment state parameters for power adjustment. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] 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.

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

[0022] FIG1B is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0023] FIG1C is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0024] FIG1D is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0025] FIG2 is an interactive schematic diagram of a power control method provided according to an embodiment of the present disclosure.

[0026] FIG3A is a schematic flow chart of a power control method according to an embodiment of the present disclosure.

[0027] FIG3B is a flow chart of a power control method according to an embodiment of the present disclosure.

[0028] FIG4A is a flow chart of a power control method according to an embodiment of the present disclosure.

[0029] FIG4B is a flow chart of a power control method according to an embodiment of the present disclosure.

[0030] FIG5 is an interactive schematic diagram of a power control method provided according to an embodiment of the present disclosure.

[0031] FIG6A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0032] FIG6B is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0033] FIG7A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0034] FIG7B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] The embodiments of the present disclosure provide a power control method, a communication device, and a device.

[0036] In a first aspect, an embodiment of the present disclosure provides a power control method, which is performed by a network device. The method includes:

[0037] First configuration information is sent to a terminal, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0038] In the above embodiment, the terminal is configured to support SRS independent power control in multiple power control adjustment states, thereby enhancing and extending SRS power control independent of PUSCH to support multiple power control adjustment states. The terminal can use different power control adjustment state parameters for power adjustment.

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

[0040] Send downlink control information (DCI) to the terminal, wherein the DCI is a packet common DCI including at least one user information block, and the user information block corresponding to the terminal includes the transmission power control (TPC) of the terminal. The DCI may be a packet-common DCI including at least one user information block, and the user information block corresponding to the terminal may include information indication fields of TPC commands corresponding to different closed-loop indexes of the terminal; or the DCI may be a packet-common DCI including at least one user information block, and the user information block corresponding to the terminal may include information indication fields of TPC commands of the terminal; or the DCI may be a scheduling DCI including an information indication field of the TPC command of the terminal and an information indication field of the closed-loop index corresponding to the TPC command; or the DCI may be a scheduling DCI including information indication fields of TPC commands corresponding to different closed-loop indexes of the terminal; or the DCI may be a scheduling DCI including information indication fields of TPC commands of the terminal.

[0041] In the above embodiment, the TPC command is transmitted through DCI, and an optional implementation method of the TPC command indication method is provided. For example, the closed-loop index corresponding to the TPC command can be directly indicated through the closed-loop index indication field, or the closed-loop index corresponding to the TPC command can be implicitly indicated by extending the indication field of the TPC command, thereby determining the power control adjustment state (closed-loop parameter) associated with the TPC command.

[0042] In combination with some embodiments of the first aspect, in some embodiments, TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the DCI is DCI format 2-3, and the high-level parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the information element IE of SRS carrier switching is configured as 3.

[0044] In the above embodiment, the TPC command indication is implemented by DCI formats 2-3 when the power control adjustment state is extended to support multiple states. For example, by configuring cc_SetIndex=3 in the SRS_CarrierSwitching IE, SRS independent power control of a maximum of two power control adjustment states is supported.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the cc_IndexInOneCC_Set in the IE of the SRS carrier switching is configured as the index of the current component carrier (CC).

[0046] In the above embodiment, different from SRS carrier switching, in the scenario of SRS independent power control, it may not be necessary to configure a CC list, or if a CC list is configured, only the current CC may be configured in cc_IndexInOneCC_Set.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that the non-periodic SRS resource set is not triggered, or the high-level parameters are configured as a non-periodic SRS resource set on the CC of the fourth set.

[0048] In the above embodiment, the SRS request indication field may not be configured in DCI 2-3, and the current SRS request design may not be modified. Alternatively, if the SRS request indication field is configured, the redundant code points of the SRS request in the current SRS carrier switching scenario may be reused, so that DCI format 2-3 can support both SRS carrier switching and the indication of SRS independent power control without carrier switching.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the DCI is DCI format 2-3, and the high-level parameter srs-TPC-PDCCH-Group is configured as a first type, the first type is a type other than type A and type B, and the DCI is not configured with a corresponding CC_SetIndexlist.

[0050] In the above embodiment, by adding a new configuration type in the SRS-TPC-PDCCH-Group, the SRS independent power control function supporting multiple power control adjustment states can be decoupled from the SRS carrier switching function. For example, if the parameter srs-TPC-PDCCH-Group is configured as the first type (such as configuring srs-TPC-PDCCH-Group = type C), CC_SetIndexlist may not be configured in the SRS_CarrierSwitching IE.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that the non-periodic SRS resource set is not triggered, or the high-level parameter srs-TPC-PDCCH-Group is configured as the first type.

[0052] In the above embodiment, the SRS request indication field may not be configured in DCI 2-3, and the current SRS request design may not be modified. Alternatively, if the SRS request indication field is configured, the redundant code points of the SRS request in the current SRS carrier switching scenario may be reused, so that DCI format 2-3 can support both SRS carrier switching and the indication of SRS independent power control without carrier switching.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats:

[0054] DCI format 1-1;

[0055] DCI formats 1-2;

[0056] DCI format 0-1;

[0057] DCI formats 0-2;

[0058] DCI formats 2-3;

[0059] DCI format 2-X.

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

[0061] Second configuration information is sent to the terminal, where the second configuration information is used to configure whether SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

[0062] In the above embodiment, assuming that the DCI includes a TPC command indication field but does not include a closed-loop index indication field, whether the corresponding TPC command is used for the power control adjustment state with a closed-loop index of i0 or i1 may depend on the signaling configuration of the network device. For example, for SRS resource sets associated with / configured with different power control adjustment states on a CC, if the terminal is configured to "use the same TPC command" or "only one TPC command can be effective" through signaling, then the TPC command can be used for both the SRS resource set associated with the power control adjustment state with a closed-loop index of i0 and the SRS resource set associated with the power control adjustment state with a closed-loop index of i1, that is, the SRS resource sets associated with / configured with different power control adjustment states on a CC can use the same TPC command for power adjustment. The above configuration can clarify whether the TPC command corresponding to the CC can be used for multiple different power control adjustment states.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the SRS includes at least one of the following:

[0064] Periodic SRS;

[0065] Semi-continuous SRS;

[0066] Aperiodic SRS.

[0067] In the above embodiments, it is clear that this solution can be used for different types of SRS.

[0068] In a second aspect, an embodiment of the present disclosure provides a power control method, which is performed by a terminal. The method includes:

[0069] First configuration information sent by a network device is received, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

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

[0071] Receive DCI sent by the network device, wherein:

[0072] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, where the closed-loop index is used to determine a power control adjustment state associated with the TPC command; or

[0073] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0074] The DCI is a packet-common DCI, including at least one user information block, and the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal; or

[0075] The DCI is a scheduling DCI, including an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command; or

[0076] The DCI is a scheduling DCI, including an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0077] The DCI is a scheduling DCI, and includes an information indication field of a TPC command of the terminal.

[0078] In combination with some embodiments of the second aspect, in some embodiments, TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the DCI is DCI format 2-3, and the high-level parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the IE of SRS carrier switching is configured as 3.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the cc_IndexInOneCC_Set in the IE of the SRS carrier switching is configured as the index of the current CC.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that the non-periodic SRS resource set is not triggered, or the high-level parameters are configured as a non-periodic SRS resource set on the CC of the fourth set.

[0082] In combination with some embodiments of the second aspect, in some embodiments, the DCI is DCI format 2-3, and the high-level parameter srs-TPC-PDCCH-Group is configured as a first type, the first type is a type other than type A and type B, and the DCI is not configured with a corresponding CC_SetIndexlist.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that the non-periodic SRS resource set is not triggered, or the high-level parameter srs-TPC-PDCCH-Group is configured as the first type.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats:

[0085] DCI format 1-1;

[0086] DCI formats 1-2;

[0087] DCI format 0-1;

[0088] DCI formats 0-2;

[0089] DCI formats 2-3;

[0090] DCI format 2-X.

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

[0092] Receive second configuration information sent by the network device, where the second configuration information is used to configure whether SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the SRS includes at least one of the following:

[0094] Periodic SRS;

[0095] Semi-continuous SRS;

[0096] Aperiodic SRS.

[0097] In a third aspect, an embodiment of the present disclosure provides a communication device, including:

[0098] The transceiver module is configured to send first configuration information to the terminal, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0099] In a fourth aspect, an embodiment of the present disclosure provides a communication device, including:

[0100] The transceiver module is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0101] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including:

[0102] one or more processors;

[0103] The communication device is used to execute the method described in the optional implementation manner of the first aspect or the second aspect.

[0104] In a sixth aspect, an embodiment of the present disclosure proposes a communication system, comprising a terminal and a network device, wherein the network device is configured to implement the method described in the optional implementation manner of the first aspect, and the terminal is configured to implement the method described in the optional implementation manner of the second aspect.

[0105] In a seventh aspect, an embodiment of the present disclosure proposes a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the method described in the optional implementation of the first aspect or the second aspect.

[0106] In an eighth aspect, an embodiment of the present disclosure proposes a computer program product, including a computer program, which implements the method described in the optional implementation manner of the first aspect or the second aspect when executed by a communication device.

[0107] In a ninth 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 aspect or the second aspect.

[0108] It is understandable that the above-mentioned communication devices, communication equipment, communication systems, storage media, computer program products, 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.

[0109] The embodiments of the present disclosure provide a power control method, a communication device, and an apparatus. In some embodiments, the terms power control method, SRS transmission method, communication method, etc. can be used interchangeably.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.

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

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

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

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

[0122] 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.

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

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

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

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

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

[0128] 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.

[0129] FIG1A is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a terminal 101 and a network device 102 .

[0130] 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.

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

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

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

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

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

[0136] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0137] To improve cell edge coverage and provide more balanced service quality within the service area, multi-point coordination remains a key technical approach in NR systems. From a network perspective, deploying a large number of distributed access points with centralized baseband processing is more conducive to providing a balanced user experience rate and significantly reducing handover latency and signaling overhead. As frequency bands increase, a relatively denser deployment of access points is required to ensure network coverage. In high-frequency bands, with the increasing integration of active antenna equipment, modular active antenna arrays are becoming increasingly popular. Each TRP's antenna array can be divided into multiple relatively independent antenna panels, allowing the overall array configuration and port count to be flexibly adjusted based on deployment scenarios and service requirements. Antenna panels or TRPs can also be connected by optical fiber, enabling more flexible distributed deployment. In the millimeter wave band, as wavelengths decrease, the obstruction effect caused by obstacles such as people or vehicles becomes more significant. In this case, to ensure link robustness, collaboration between multiple TRPs or panels can be leveraged to transmit / receive from multiple beams at multiple angles, thereby mitigating the adverse effects of obstruction.

[0138] Based on the mapping of transmitted signal streams to multiple TRPs / panels, coordinated multi-point transmission technology can be categorized as coherent or incoherent. In coherent transmission, each data layer is mapped to multiple TRPs / panels using a weighted vector. In incoherent transmission, each data stream is mapped to only a subset of TRPs / panels. Coherent transmission places higher demands on synchronization between transmission points and the transmission capacity of the backhaul link, making it more sensitive to many non-ideal factors in real-world deployment conditions. In contrast, incoherent transmission is less susceptible to these factors and is therefore a key consideration for multi-point transmission technology.

[0139] For the uplink, the channel spatial characteristics actually passed through by the PUSCH channels for different TRPs are very different. Therefore, it is considered that the Quasi Co-Location Type D (QCL-D) of the PUSCH channels in different transmission directions is different.

[0140] NR versions R15 / 16 do not consider the multi-TRP (M-TRP) scenario, and the uplink is a single TRP transmission. R17 enhances the M-TRP uplink transmission under single DCI (S-DCI). The uplink PUSCH transmission includes transmission to the TRP directions of multiple base stations, and standardizes the collaborative transmission under the time-division multiplexing (TDM) transmission mode. Different repetitions of the same information on the PUSCH are sent to different collaborative TRPs of the base station through different transmission opportunities (TO) in the time domain. This method has relatively low requirements on terminal capabilities. Each transmission opportunity (TO) only needs to send PUSCH / physical uplink control channel (PUCCH) in the direction of one TRP, so it is not required to support the ability to send beams simultaneously, and the transmission cycle is relatively large.

[0141] In R17, in non-codebook and codebook-based M-TRP transmissions, the sounding reference signal resource indicator (SRS resource indicator, SRI) field in the DCI indicates the SRS resource in the SRS resource set. Since R17 supports two SRS resource sets, in non-codebook-based M-TRP PUSCH repeated transmissions, the DCI format 0_1 / 0_2 contains two SRI fields associated with the two SRS resource sets. Each SRI field is a TRP indication SRI. The design of the first SRI field is based on the R15 / 16 framework, and all repeated transmissions use the same number of layers. Among them, for non-codebook-based transmissions, the first SRI field is used to determine the elements in the second SRI field, and the second SRI field only contains the SRI combination associated with the number of layers indicated by the first SRI field. The number of bits N2 of the second SRI field is determined by the maximum number of code points for each rank among all ranks associated with the first SRI field.

[0142] The R18 enhancement goal is to achieve simultaneous collaborative transmission from multiple terminal panels to the TRPs of multiple base stations to increase transmission reliability and throughput, while effectively reducing transmission latency under multiple TRPs. However, this requires the terminal to have the ability to send multiple beams simultaneously. PUSCH transmission can be based on multiple panels / TRPs scheduled by a single PDCCH (S-DCI) or multiple panels / TRPs scheduled by different PDCCHs (M-DCI).

[0143] In actual deployments, the links between transmission points may be relatively ideal backhaul links supporting high throughput and very low backhaul latency, or they may be non-ideal backhaul links using xDSL (digital subscriber line), microwave, or relay. The M-DCI-based non-coherent joint transmission (NC-JT) solution was originally introduced primarily for non-ideal backhaul scenarios, but it can also be used in ideal backhaul scenarios.

[0144] Terminals are typically configured with multiple physical panels, and different panels may have different capabilities. For example, they may not all have the same number of SRS ports or the same maximum number of supported data transmission layers. For example, one panel may support up to two layers, while another may support up to four layers. The network scheduler determines whether the terminal is currently suitable for simultaneous uplink transmission on multiple panels. If the terminal is currently suitable for simultaneous uplink transmission on multiple panels and is scheduled, the network will directly or indirectly indicate the relevant transmission parameters, including the terminal's specific beam indication information, the number of data layers to be transmitted, the allocation of demodulation reference signal (DMRS) ports to be used, and precoding indication information.

[0145] The transmission schemes supported by R18 uplink simultaneous transmission STxMP for S-DCI-based PUSCH include:

[0146] Space Division Multiplexing (SDM): Different parts of a PUSCH transport block (TB) are sent on the same time-frequency resources to two different Transmission Resource Planes (TRPs) through their own corresponding DMRS ports or port combinations allocated on different panels. Different panels / TRPs / transmission opportunities (TOs) are associated with different Transmission Configuration Indication (TCI) states (i.e., beams).

[0147] Single Frequency Network (SFN) spatial division multiplexing: A TB of the PUSCH is sent on the same time-frequency resources to two different TRPs through the same DMRS port or port combination allocated on different panels. Different panels / TRPs / transmission opportunities (TOs) are associated with different TCI states (i.e., beams).

[0148] In the current research on multi-TRP transmission, the R19 research direction will continue to enhance uplink transmission. The focus is on multi-TRP deployment scenarios such as downlink single TRP (S-TRP) and uplink multi-TRP (M-TRP). In this scenario, by deploying multiple uplink receiving points, uplink coverage and throughput can be further improved at a lower network deployment cost, while avoiding complex network planning and downlink interference management coordination issues.

[0149] In the research of R19, one research direction is to improve the uplink coverage and throughput by deploying heterogeneous networks to achieve asymmetric multi-TRP transmission (downlink single TRP / uplink multi-TRP). Referring to Figures 1B to 1D, Figure 1B shows a system architecture in a scenario where an uplink receiving point is not deployed, Figure 1C shows a system architecture in a scenario where an uplink receiving point is deployed, and Figure 1D shows a system architecture for asymmetric multi-TRP transmission. Since the rated power of the macro base station and the micro node (UL TRP) is different, the terminal can receive downlink (DL) transmissions from the macro base station and transmit uplink (UL) to the macro base station or non-co-located micro node to maximize UL throughput. As an option to further reduce energy consumption, the micro node can reduce or even turn off DL transmissions, and the node is only used for uplink reception.

[0150] In the uplink-only (UL-only) scenario, the cell includes a master base station and multiple UL TRP receiving points. In order for the terminal to perform downlink S-TRP / uplink M-TRP transmission, the uplink M-TRP transmission can be completed in collaboration between the master base station and UL TRP, or in collaboration between different UL TRPs. In the asymmetric downlink S-TRP / uplink M-TRP scenario, in addition to the SRS with the function of beam management, which will be configured with power control independent of PUSCH, the SRS with the function of antenna switching needs to be sent to the master base station because it is used to obtain downlink CSI. Therefore, the transmission of SRS with different functional configurations may correspond to different TRPs, and the adjustment state parameters of the power control may be different.

[0151] The following introduces the first DCI format (such as DCI format 2-3) and related configuration signaling of SRS carrier switching that may be involved in the embodiments of the present disclosure.

[0152] The first DCI format is used to transmit a set of TPC commands for one or more UEs to perform SRS transmission. When transmitting the TPC commands, an SRS request may also be transmitted.

[0153] For ULs that do not schedule PUCCH and PUSCH, or for ULs where SRS power control is not linked to PUSCH power control, if the UE is configured with the higher-layer parameter srs-TPC-PDCCH-Group=typeA, a user information block will be configured for the UE in the first DCI format, and the following fields will be defined for the user information block:

[0154] (1) SRS request, consisting of 0 or 2 bits. The presence or absence of this field depends on the relevant definition in the protocol. If this field exists, the interpretation of this field is defined in Table 1 below.

[0155] (2) TPC command number 1, TPC command number 2, ..., TPC command number N, where each TPC command is used for a UL carrier provided by the higher layer parameter cc-IndexInOneCC-Set.

[0156] For ULs that do not schedule PUCCH and PUSCH, or for ULs where SRS power control is not linked to PUSCH power control, if the UE is configured with the higher-layer parameter srs-TPC-PDCCH-Group=typeB, one or more user information blocks (UIBs) will be configured for the UE in the first DCI format. Each UIB is for one UL carrier, and each UIB defines the following fields:

[0157] (1) SRS request, consisting of 0 or 2 bits. The presence or absence of this field depends on the relevant definition in the protocol. If this field exists, the interpretation of this field is defined in Table 1 below.

[0158] (2) TPC command, consisting of 2 bits.

[0159] Table 1

[0160] The first DCI format is used for the serving cell uplink carrier of the UE not configured with PUSCH / PUCCH transmission, or for the serving cell uplink carrier where the parameter srs-PowerControlAdjustmentStates indicates that SRS transmission and PUSCH transmission are in separate power control adjustment states.

[0161] The high-level parameter carrierSwitching can be configured:

[0162] (1) The configuration type of the first DCI format field, including typeA or typeB.

[0163] (2) For type A, the index of the serving cell set is provided by cc-SetIndex, the index of the serving cell in the serving cell set is provided by cc-IndexInOneCC-Set, and the first DCI format field includes the TPC command of each serving cell in the serving cell set and may also include the SRS request for SRS transmission in the serving cell set.

[0164] (3) For type B, the first DCI format field includes a TPC command for a serving cell index and may also include an SRS request for SRS transmission on the serving cell.

[0165] In some embodiments, the terms "carrier", "uplink carrier (UL carrier)", "component carrier (CC)", "cell", "serving cell" and the like may be used interchangeably.

[0166] The configuration signaling related to SRS carrier switching includes SRS-TPC-CommandConfigIE and SRS-CarrierSwitchingIE.

[0167] Optionally, an example of SRS-TPC-CommandConfigIE is as follows:

[0168] The current protocol can indicate an SRS TPC command independent of PUSCH to the terminal through DCI format 2-3, and the default SRS independent power control has only one power control adjustment state. In the disclosed embodiment, in an asymmetric M-TRP scenario, the SRS power control independent of PUSCH can be enhanced and extended to support multiple power control adjustment states (for example, supporting up to two power control adjustment states), and the current DCI format 2-3 related configuration method and corresponding signaling structure are mainly designed for SRS carrier switching. The configuration parameters for the SRS carrier switching function and the indication function for SRS independent power control currently need to be configured through the SRS_CarrierSwitching IE, which is difficult to decouple. Therefore, in the scenario where the terminal supports SRS independent power control with multiple power control adjustment states, it is necessary to further clarify the indication method of the TPC command.

[0169] FIG2 is an interactive diagram of a power control method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a power control method, which includes:

[0170] Step S2101: The network device sends first configuration information to the terminal.

[0171] In some embodiments, the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states. Optionally, the first configuration information includes configuration information for a DCI, and the DCI is configured to indicate that the terminal supports SRS independent power control in multiple power control adjustment states. For example, the first configuration information is used to configure the terminal to support SRS independent power control in a maximum of two power control adjustment states.

[0172] Optionally, the first configuration information is carried in a first signaling. Optionally, the network device sends a first signaling to the terminal, where the first signaling is used to configure the terminal to support SRS independent power control in multiple power control adjustment states. For example, the first signaling is used to configure the terminal to support SRS independent power control in a maximum of two power control adjustment states.

[0173] In the above embodiment, the terminal is configured to support SRS independent power control in multiple power control adjustment states through the first configuration information, thereby enhancing and extending the SRS power control independent of PUSCH to support multiple power control adjustment states, and the terminal can use different power control adjustment state parameters for power adjustment.

[0174] The name of the first configuration information is not limited, and may be, for example, "first configuration", "first signaling", "RRC signaling", "RRC configuration", etc.

[0175] Step S2102: The network device sends DCI to the terminal.

[0176] The DCI is used to transmit a TPC command. Optionally, the DCI may also be used to transmit an SRS request.

[0177] Optionally, since the terminal supports SRS independent power control in multiple power control adjustment states, it is necessary to further clarify to which power control adjustment state (closed-loop parameter) the TPC command transmitted by the DCI is associated, that is, the indication method of the TPC command needs to be further clarified.

[0178] In some embodiments, the above-mentioned DCI is a packet-common DCI (such as DCI format 2-3 or a new format type 2-X of packet-common DCI), including at least one user information block, wherein the user information block of a terminal includes an information indication field of the TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, and the closed-loop index is used to determine the power control adjustment state associated with the TPC command. For example, the user information block of a terminal includes a TPC command indication field and a closed-loop index indication field, the TPC command indication field corresponds to the TPC command of a CC, and the closed-loop index indication field is used to indicate the closed-loop index corresponding to the TPC command. Optionally, the closed-loop index indication field is 1 bit.

[0179] For example, assuming that the terminal supports SRS independent power control in two power control adjustment states, if the value of the closed-loop index indication field is 0, then the corresponding TPC command is associated with the power control adjustment state of closed-loop index (closedloopindex) = i0, and if the value of the closed-loop index indication field is 1, then the corresponding TPC command is associated with the power control adjustment state of closedloopindex = i1.

[0180] Since the above DCI is a group common DCI, one or more terminals read their respective corresponding user information blocks from the above DCI according to the configured start bit information to obtain their respective corresponding TPC commands and closed-loop indexes.

[0181] In some embodiments, the above-mentioned DCI is a packet-common DCI (such as DCI format 2-3 or a new format type 2-X of packet-common DCI), including at least one user information block, wherein the user information block of a terminal includes an information indication field of the TPC command corresponding to different closed-loop indexes of the terminal. For example, a user information block includes multiple TPC command indication fields, and the multiple TPC command indication fields correspond to the TPC commands of a CC, and the multiple TPC command indication fields respectively correspond to different closed-loop indexes. In the TPC command indication fields corresponding to different closed-loop indexes, whichever TPC command is valid, the TPC command is the TPC command indicated by the above-mentioned DCI.

[0182] For example, assuming that the terminal supports SRS independent power control with two power control adjustment states, a user information block includes two TPC command indication fields, which are respectively associated with the power control adjustment states of closedloopindex=i0 and closedloopindex=i1. For example, the TPC command in the first TPC command indication field is associated with the power control adjustment state of closedloopindex=i0, and the TPC command in the second TPC command indication field is associated with the power control adjustment state of closedloopindex=i1.

[0183] In the above embodiment, the TPC command indication field in a user information block is enhanced and expanded into multiple (eg, two) TPC command indication fields. According to the existing design, each TPC command indication field is 2 bits.

[0184] In some embodiments, the DCI is a scheduling DCI (e.g., DCI format 1-1 / 1-2 / 0-1 / 0-2), including a TPC command information indication field for a terminal and a closed-loop index information indication field corresponding to the TPC command. For example, the scheduling DCI includes a TPC command indication field and a closed-loop index indication field, where the TPC command indication field corresponds to a TPC command for a CC, and the closed-loop index indication field is used to indicate the closed-loop index corresponding to the TPC command.

[0185] In some embodiments, the DCI is a scheduling DCI (e.g., DCI format 1-1 / 1-2 / 0-1 / 0-2), and includes an information indication field for TPC commands corresponding to different closed-loop indexes of a terminal. For example, the scheduling DCI includes multiple TPC command indication fields, each of which corresponds to a TPC command of a CC, and each of which corresponds to a different closed-loop index.

[0186] In the above embodiment, the closed-loop index corresponding to the TPC command can be directly indicated by the closed-loop index indication field (1 bit), or the closed-loop index corresponding to the TPC command can be implicitly indicated by extending the indication field of the TPC command, thereby determining the power control adjustment state (closed-loop parameter) associated with the TPC command.

[0187] In some embodiments, the DCI is packet-common DCI (e.g., DCI format 2-3 or a new packet-common DCI format type 2-X), and includes at least one user information block, wherein the user information block of a terminal includes an information indication field for the TPC command of the terminal. For example, the user information block of a terminal includes a TPC command indication field. The TPC command indication field corresponds to the TPC command of a CC.

[0188] In some embodiments, the DCI is a scheduling DCI (e.g., DCI format 1-1 / 1-2 / 0-1 / 0-2), including a TPC command information indication field for a terminal. For example, the scheduling DCI includes a TPC command indication field. The TPC command indication field corresponds to a TPC command for a CC.

[0189] In the above embodiment, the DCI includes a TPC command indication field but does not include a closed-loop index indication field. In a scenario where the terminal supports SRS independent power control with multiple power control adjustment states, how the TPC command is associated with the power control adjustment state may depend on signaling configuration or pre-defined or default.

[0190] In some embodiments, the network device sends second configuration information to the terminal, where the second configuration information is used to configure whether SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

[0191] Optionally, the second configuration information is carried in a second signaling. The network device sends the second signaling to the terminal, where the second signaling is used to configure whether SRS resource sets associated with / configured in different power control adjustment states of the terminal use the same TPC command, or whether only one TPC command is effective for the terminal.

[0192] The name of the second configuration information is not limited, and may be, for example, "second configuration", "second signaling", "RRC signaling", "RRC configuration", etc.

[0193] To illustrate this, assume that a user information block of the group common DCI (or the scheduling DCI) contains a TPC command indication field but does not contain a closed loop index indication field, and the terminal is configured through the first signaling to support SRS independent power control in two power control adjustment states. For SRS resource sets associated / configured with different power control adjustment states on a CC, such as SRS resource set A with a power control adjustment state associated with closedloopindex=i0 and SRS resource set B with a power control adjustment state associated with closedloopindex=i1, the terminal is configured through the second signaling to "whether to use the same TPC command" or "whether only one TPC command can be effective". If it is configured to "use the same TPC command" or "only one TPC command can be effective", the TPC command in the TPC command indication field can be used (associated) for each power control adjustment state, that is, SRS resource set A with a power control adjustment state associated with closedloopindex=i0 and SRS resource set B with a power control adjustment state associated with closedloopindex=i1 on the CC, and the same TPC command is used for power adjustment.

[0194] According to this embodiment, when the power control adjustment state associated with the TPC command is not directly or implicitly indicated in the DCI, it can be clarified through the above configuration whether the TPC command corresponding to the CC can be used for multiple different power control adjustment states.

[0195] In some embodiments, it may also be defined by default or in a protocol whether SRS resource sets associated with different power control adjustment states of a terminal use the same TPC command, or whether only one TPC command is effective for the terminal.

[0196] Optionally, TPC commands corresponding to different closed loop indices of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value. For example, a TPC command associated with a power control adjustment state of closedloopindex=i0 and a TPC command associated with a power control adjustment state of closedloopindex=i1 are configured with the same adjustment method.

[0197] In the above embodiment, the TPC command is transmitted to the terminal via the DCI, and some optional implementations of the TPC command indication method are provided.

[0198] In some embodiments, the DCI is in DCI format 2_3, and the higher layer parameter srs-TPC-PDCCH-Group is configured as type A (eg, srs-TPC-PDCCH-Group=typeA), and the cc_SetIndex in the SRS_CarrierSwitching IE is configured as 3.

[0199] In the above embodiment, the TPC command indication is implemented by DCI formats 2-3 when the power control adjustment state is extended to support multiple states. For example, by configuring cc_SetIndex=3 in the SRS_CarrierSwitching IE, SRS independent power control of a maximum of two power control adjustment states is supported.

[0200] In some embodiments, the cc_IndexInOneCC_Set in the SRS_CarrierSwitching IE may not be configured or may be configured as the index of the current CC.

[0201] In some embodiments, when the SRS-TPC-PDCCH-Group is configured as Type A, the DCI format described above does not include an SRS request information indication field. It is understood that the SRS request indication field in DCI formats 2-3 is primarily used to implement SRS carrier switching functionality to trigger SRS on other CCs. However, in the scenario of supporting SRS independent power control with multiple power control adjustment states in the embodiments of the present disclosure, the SRS request indication field may not be configured, and the current SRS request design may not be modified.

[0202] In some embodiments, when the srs-TPC-PDCCH-Group is configured as type A, the above-mentioned DCI is configured with an SRS request information indication field, and the first code point (codepoint) of the SRS request information indication field is configured to indicate "an untriggered non-periodic SRS resource set or a non-periodic SRS resource set on a CC (serving cell) whose high-level parameters are configured as the fourth set".

[0203] Optionally, the first code point may be "00". The disclosed embodiment may reuse redundant code points of SRS requests in the current SRS carrier switching scenario, so that DCI formats 2-3 can support both SRS carrier switching and SRS independent power control indication without carrier switching.

[0204] Optionally, in combination with the interpretation of the SRS request field defined in Table 1 above, the interpretation of the code point "00" of the SRS request field is as shown in Table 2.

[0205] Table 2

[0206] In some embodiments, the above-mentioned DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as the first type, which is a type other than type A and type B, and the above-mentioned DCI is not configured with a corresponding CC_SetIndexlist.

[0207] Optionally, a new configuration type, namely the first type (such as type C), is added to the high-layer parameter SRS-TPC-PDCCH-Group.

[0208] For srs-TPC-PDCCH-Group = type A, the SRS_CarrierSwitching IE needs to configure CC_SetIndexlist for carrier switching. By adding a new type to the SRS-TPC-PDCCH-Group, the SRS independent power control function that supports multiple power control adjustment states can be decoupled from the SRS carrier switching function. For example, if the parameter srs-TPC-PDCCH-Group is configured as the first type (such as configuring srs-TPC-PDCCH-Group = type C), CC_SetIndexlist does not need to be configured in the SRS_CarrierSwitching IE.

[0209] In some embodiments, when the srs-TPC-PDCCH-Group is configured as the first type, the DCI is not configured with an SRS request information indication field.

[0210] In some embodiments, when the srs-TPC-PDCCH-Group is configured as the first type, the above-mentioned DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that the non-periodic SRS resource set is not triggered, or the high-level parameter srs-TPC-PDCCH-Group is configured as the first type.

[0211] Optionally, the first code point may be "00". The disclosed embodiment may reuse redundant code points of SRS requests in the current SRS carrier switching scenario, so that DCI formats 2-3 can support both SRS carrier switching and SRS independent power control indication without carrier switching.

[0212] Optionally, in combination with the interpretation of the SRS request field defined in Table 1 above, the interpretation of the code point "00" of the SRS request field is as shown in Table 3.

[0213] Table 3

[0214] In some embodiments, the terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats:

[0215] DCI format 1-1;

[0216] DCI formats 1-2;

[0217] DCI format 0-1;

[0218] DCI formats 0-2;

[0219] DCI formats 2-3;

[0220] DCI format 2-X.

[0221] If the terminal does not support SRS carrier switching capability, it can indicate SRS independent power control by configuring DCI format 2-3, or it can indicate SRS independent power control by configuring other DCI (such as scheduling DCI (such as DCI format 1-1 / 1-2 / 0-1 / 0-2) or a new format type of packet common DCI (such as DCI format 2-X)). For the above DCI formats, the method for indicating the TPC command can refer to the description in the previous embodiment.

[0222] In some embodiments, the TPC command is transmitted via a scheduling DCI (e.g., DCI1-1 / 1-2 or DCI0-1 / 0-2), and the indication field of the scheduling DCI is configured via high-layer signaling, such as by configuring the indication field of the scheduling DCI by determining whether the newly added parameter {separate_SRS_TPC} is enabled. The scheduling DCI indicates the corresponding TPC command of the corresponding terminal in the SRS independent power control scenario.

[0223] In some embodiments, TPC commands are transmitted via a new format type 2-X of packet-common DCI, with higher-layer signaling independently configured for each terminal, such as the start bit information corresponding to each terminal. By defining a new packet-common DCI, this DCI can be shared by multiple users, improving efficiency. Furthermore, this DCI can be decoupled from carrier switching and used solely for SRS independent power control.

[0224] The SRS used in the embodiments of the present disclosure may be applied to at least one of the following:

[0225] Periodic SRS;

[0226] Semi-continuous SRS;

[0227] Aperiodic SRS.

[0228] Therefore, different types of SRS can use the above-mentioned signaling configuration and use DCI2_3 (or other DCI formats) for TPC command indication. For example, for periodic SRS and semi-persistent SRS, if an SRS resource set with the function of "beam management" or "antenna switching" is configured, the SRS power control independent of PUSCH can be configured by the above-mentioned method, and the corresponding closed-loop index indication field can be configured (or the closed-loop index indication field is not configured), and the corresponding TPC command can be indicated by DCI. For periodic SRS and semi-persistent SRS, if the corresponding TPC command is indicated by DCI format 2-3, the SRS request indication field is no longer configured when configuring DCI format 2-3.

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

[0230] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" may be used interchangeably. For example, a codebook may be a collection of one or more codewords / precoding matrices.

[0231] In some embodiments, terms such as "uplink", "uplink", "physical uplink", etc. can be used interchangeably, and terms such as "downlink", "downlink", "physical downlink", etc. can be used interchangeably.

[0232] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0233] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

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

[0235] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0236] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) state", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", "panel" and the like can be used interchangeably.

[0237] 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.

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

[0239] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, and step S2102 may be implemented as an independent embodiment.

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

[0241] FIG3A is a flow chart of a power control method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a power control method, which is executed by a network device and includes:

[0242] Step S3101: Send first configuration information.

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

[0244] In the above embodiment, the terminal is configured to support SRS independent power control in multiple power control adjustment states through the first configuration information, thereby enhancing and extending the SRS power control independent of PUSCH to support multiple power control adjustment states, and the terminal can use different power control adjustment state parameters for power adjustment.

[0245] FIG3B is a flow chart of a power control method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a power control method, which is executed by a network device and includes:

[0246] Step S3201, send DCI.

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

[0248] The DCI is used to transmit a TPC command to the terminal. Optionally, the DCI may also be used to transmit an SRS request.

[0249] In some embodiments, the DCI is a packet-common DCI including at least one user information block, wherein the user information block of a terminal includes an information indication field for a TPC command of the terminal and an information indication field for a closed-loop index corresponding to the TPC command. The closed-loop index is used to determine a power control adjustment state associated with the corresponding TPC command.

[0250] In some embodiments, the DCI is a packet-common DCI, including at least one user information block, and the user information block of a terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal.

[0251] In some embodiments, the above-mentioned DCI is a packet common DCI, which includes at least one user information block, and the user information block of a terminal includes an information indication field of a TPC command of the terminal.

[0252] In some embodiments, the above-mentioned DCI is a scheduling DCI, which includes an information indication field of a TPC command of a terminal and an information indication field of a closed-loop index corresponding to the TPC command.

[0253] In some embodiments, the DCI is a scheduling DCI, which includes an information indication field of a TPC command corresponding to different closed-loop indexes of a terminal.

[0254] In some embodiments, the above-mentioned DCI is a scheduling DCI, which includes an information indication field of a TPC command of a terminal.

[0255] In the above embodiment, the TPC command is transmitted to the terminal via the DCI, and some optional implementations of the TPC command indication method are provided.

[0256] In some embodiments, the optional implementation of step S3201 in FIG. 3B and the optional implementation of step S3101 in FIG. 3A may be arbitrarily combined.

[0257] FIG4A is a flow chart of a power control method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a power control method, which is executed by a terminal and includes:

[0258] Step S4101: Receive first configuration information.

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

[0260] The first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states. For example, the first configuration information is used to configure the terminal to support SRS independent power control in a maximum of two power control adjustment states.

[0261] In some embodiments, first configuration information is received from a network device. Optionally, the first configuration information is carried in a first signaling. Optionally, first signaling is received from a network device, the first signaling being used to configure a terminal to support SRS independent power control in multiple power control adjustment states. For example, the first signaling is used to configure the terminal to support SRS independent power control in a maximum of two power control adjustment states.

[0262] In the above embodiment, the terminal is configured to support SRS independent power control in multiple power control adjustment states through the first configuration information, thereby enhancing and extending the SRS power control independent of PUSCH to support multiple power control adjustment states, and the terminal can use different power control adjustment state parameters for power adjustment.

[0263] FIG4B is a flow chart of a power control method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a power control method, which is executed by a terminal and includes:

[0264] Step S4201, receive DCI.

[0265] In some embodiments, DCI sent by a network device is received.

[0266] The DCI is used to transmit a TPC command. Optionally, the DCI may also be used to transmit an SRS request.

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

[0268] In some embodiments, the DCI is a packet-common DCI including at least one user information block, wherein the user information block of a terminal includes an information indication field for a TPC command of the terminal and an information indication field for a closed-loop index corresponding to the TPC command. The closed-loop index is used to determine a power control adjustment state associated with the corresponding TPC command.

[0269] In some embodiments, the DCI is a packet-common DCI, including at least one user information block, and the user information block of a terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal.

[0270] In some embodiments, the above-mentioned DCI is a packet common DCI, which includes at least one user information block, and the user information block of a terminal includes an information indication field of a TPC command of the terminal.

[0271] In some embodiments, the above-mentioned DCI is a scheduling DCI, which includes an information indication field of a TPC command of a terminal and an information indication field of a closed-loop index corresponding to the TPC command.

[0272] In some embodiments, the DCI is a scheduling DCI, which includes an information indication field of a TPC command corresponding to different closed-loop indexes of a terminal.

[0273] In some embodiments, the above-mentioned DCI is a scheduling DCI, which includes an information indication field of a TPC command of a terminal.

[0274] In the above embodiment, the TPC command is received through DCI, and some optional implementations of the TPC command indication method are provided.

[0275] In some embodiments, the optional implementation of step S4201 in FIG. 4B and the optional implementation of step S4101 in FIG. 4A may be arbitrarily combined.

[0276] FIG5 is an interactive diagram of a power control method according to an embodiment of the present disclosure. As shown in FIG5 , an embodiment of the present disclosure relates to a power control method, which includes:

[0277] Step S5101: The network device sends first configuration information to the terminal.

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

[0279] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0280] According to the embodiment of the present disclosure, the signaling configuration of SRS power control and the indication of TPC command can be realized. The embodiment of the present disclosure is described below in conjunction with optional implementation methods.

[0281] First, the terminal is configured to support multiple (e.g., two) power control adjustment states for SRS independent power control and the corresponding TPC command is indicated via DCI2_3. The TPC command can support different SRS power control adjustment states (i.e., closed loop power control (CLPC) closed loop index).

[0282] Optionally, the higher layer parameter srs-TPC-PDCCH-Group is configured as typeA, and in an SRS independent power control scenario, cc_SetIndex=3 is configured in the SRS_CarrierSwitching IE to support SRS independent power control in two power control adjustment states.

[0283] Optionally, if cc_SetIndex=3 is configured in the SRS_CarrierSwitching IE, then only the current CC may be configured for cc_IndexInOneCC_Set.

[0284] Optionally, if the srs-TPC-PDCCH-Group is configured as type A, for the SRS request indication field, in one implementation, the SRS request indication field is not configured, and the current SRS request design remains unchanged. In another implementation, the SRS request indication field is configured, and the definition of the indication field is enhanced. For example, the code point "00" in the indication field is configured to indicate "an aperiodic SRS resource set is not triggered, or an aperiodic SRS resource set is used on a CC (serving cell) with higher-layer parameters configured as the fourth set." Optionally, the interpretation of the code point "00" can be found in Table 2.

[0285] Optionally, if the SRS-TPC-PDCCH-Group is configured as type A, for the TPC command indication, in one implementation, the user information block corresponding to a terminal in DCI format 2-3 includes only the TPC command and closed loop index (CLI) indication for one CC. When the CLI indication is 0, the corresponding TPC command is associated with the power control adjustment state of closedloopindex=i0. When the CLI indication is 1, the corresponding TPC command is associated with the power control adjustment state of closedloopindex=i1. In another implementation, the user information block corresponding to a terminal in DCI format 2-3 includes a TPC command indication field corresponding to closedloopindex={i0,i1}, i.e., a TPC command indication field corresponding to closedloopindex=i0 and a TPC command indication field corresponding to closedloopindex=i1, each of which is 2 bits. TPC commands associated with different CLIs are configured with the same adjustment method, i.e., both use cumulative values ​​or absolute values ​​for power adjustment.

[0286] Optionally, a new type is added and configured in the higher-layer parameter srs-TPC-PDCCH-Group, and the new type is recorded as typeC, for example, srs-TPC-PDCCH-Group is configured as typeC.

[0287] Optionally, if the srs-TPC-PDCCH-Group is configured as type C, the corresponding CC_SetIndexlist is not defined and configured in the SRS_CarrierSwitching IE.

[0288] Optionally, if the srs-TPC-PDCCH-Group is configured as type C, in one implementation, the SRS request indication field is not configured. In another implementation, the SRS request indication field is configured, and the definition of the indication field is enhanced. For example, the code point "00" in the indication field is configured to indicate "an aperiodic SRS resource set is not triggered, or the higher-layer parameter srs-TPC-PDCCH-Group is configured as type C." Optionally, the interpretation of the code point "00" can be referred to as shown in Table 3.

[0289] Optionally, if the SRS-TPC-PDCCH-Group is configured as type C, for the TPC command indication, in one implementation, the user information block corresponding to a terminal in DCI format 2-3 includes only the TPC command and closed loop index (CLI) indication for one CC. When the CLI indication is 0, the corresponding TPC command is associated with the power control adjustment state of closedloopindex=i0. When the CLI indication is 1, the corresponding TPC command is associated with the power control adjustment state of closedloopindex=i1. In another implementation, the user information block corresponding to a terminal in DCI format 2-3 includes a TPC command indication field corresponding to closedloopindex={i0,i1}, i.e., a TPC command indication field corresponding to closedloopindex=i0 and a TPC command indication field corresponding to closedloopindex=i1, each of which is 2 bits. TPC commands associated with different CLIs are configured with the same adjustment method, i.e., both use cumulative values ​​or absolute values ​​for power adjustment.

[0290] Optionally, if the terminal does not support SRS carrier switching capability, it can configure other DCIs (such as scheduling DCI (such as DCI1-1 / 1-2 or DCI0-1 / 0-2) or grouped common DCI new format type 2-X) to indicate that the terminal supports SRS independent power control in multiple power control adjustment states, and configure the indication field of other DCIs through high-level signaling, such as whether the newly added parameter {separate_SRS_TPC} is enabled.

[0291] Optionally, if indication is performed through scheduling DCI, the indication field of the scheduling DCI may include 2 TPC command indication fields for SRS independent power control, or the indication field of the scheduling DCI may include 1 TPC command indication field and 1 CLI indication field.

[0292] Optionally, if the new format type 2-X of the grouped common DCI is used for indication, high-layer signaling is independently configured for each terminal, such as configuring the start bit information corresponding to each terminal. Optionally, the indication field of DCI 2-X can include two TPC command indication fields for independent SRS power control, or the indication field of DCI 2-X can include one TPC command indication field and one CLI indication field.

[0293] For a user information block of the packet common DCI (or scheduling DCI) that contains one TPC command indication field but does not contain a CLI indication field, if "use the same TPC command" or "only one TPC command can be effective" is configured through signaling, the SRS resource sets associated / configured with different power control adjustment states on the corresponding CC use the same TPC command for power adjustment.

[0294] The embodiments of the present disclosure provide how to configure SRS independent power control and how to indicate TPC commands in an asymmetric M-TRP scenario.

[0295] 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.

[0296] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0297] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0298] FIG6A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. As shown in FIG6A , a communication device 6100 may include:

[0299] The transceiver module 6101 is configured to send first configuration information to the terminal, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0300] Optionally, the transceiver module 6101 is further configured to send downlink control information DCI to the terminal, wherein:

[0301] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, where the closed-loop index is used to determine a power control adjustment state associated with the TPC command; or

[0302] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0303] The DCI is a packet-common DCI, including at least one user information block, and the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal; or

[0304] The DCI is a scheduling DCI, including an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command; or

[0305] The DCI is a scheduling DCI, including an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0306] The DCI is a scheduling DCI, and includes an information indication field of a TPC command of the terminal.

[0307] Optionally, TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

[0308] Optionally, the DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the SRS carrier switching information element IE is configured as 3.

[0309] Optionally, cc_IndexInOneCC_Set in the SRS carrier switching IE is configured as the index of the current CC.

[0310] Optionally, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that a non-periodic SRS resource set is not triggered, or the high-level parameters are configured as a non-periodic SRS resource set on the CC of the fourth set.

[0311] Optionally, the DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as the first type, the first type is a type other than type A and type B, and the DCI is not configured with a corresponding CC_SetIndexlist.

[0312] Optionally, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that a non-periodic SRS resource set is not triggered, or the high-level parameter srs-TPC-PDCCH-Group is configured as the first type.

[0313] Optionally, the terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats:

[0314] DCI format 1-1;

[0315] DCI formats 1-2;

[0316] DCI format 0-1;

[0317] DCI formats 0-2;

[0318] DCI formats 2-3;

[0319] DCI format 2-X.

[0320] Optionally, the transceiver module 6101 is also configured to send second configuration information to the terminal, and the second configuration information is used to configure whether the SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

[0321] Optionally, the SRS includes at least one of the following:

[0322] Periodic SRS;

[0323] Semi-continuous SRS;

[0324] Aperiodic SRS.

[0325] FIG6B is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. As shown in FIG6B , the communication device 6200 may include:

[0326] The transceiver module 6201 is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

[0327] Optionally, the transceiver module 6201 is further configured to receive DCI sent by the network device, wherein:

[0328] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, where the closed-loop index is used to determine a power control adjustment state associated with the TPC command; or

[0329] The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0330] The DCI is a packet-common DCI, including at least one user information block, and the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal; or

[0331] The DCI is a scheduling DCI, including an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command; or

[0332] The DCI is a scheduling DCI, including an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or

[0333] The DCI is a scheduling DCI, and includes an information indication field of a TPC command of the terminal.

[0334] Optionally, TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

[0335] Optionally, the DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the SRS carrier switching IE is configured as 3.

[0336] Optionally, cc_IndexInOneCC_Set in the SRS carrier switching IE is configured as the index of the current CC.

[0337] Optionally, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that a non-periodic SRS resource set is not triggered, or the high-level parameters are configured as a non-periodic SRS resource set on the CC of the fourth set.

[0338] Optionally, the DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as the first type, the first type is a type other than type A and type B, and the DCI is not configured with a corresponding CC_SetIndexlist.

[0339] Optionally, the DCI is not configured with an SRS request information indication field; or, the DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that a non-periodic SRS resource set is not triggered, or the high-level parameter srs-TPC-PDCCH-Group is configured as the first type.

[0340] Optionally, the terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats:

[0341] DCI format 1-1;

[0342] DCI formats 1-2;

[0343] DCI format 0-1;

[0344] DCI formats 0-2;

[0345] DCI formats 2-3;

[0346] DCI format 2-X.

[0347] Optionally, the transceiver module 6201 is also configured to receive second configuration information sent by the network device, and the second configuration information is used to configure whether the SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

[0348] Optionally, the SRS includes at least one of the following:

[0349] Periodic SRS;

[0350] Semi-continuous SRS;

[0351] Aperiodic SRS.

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

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

[0354] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 7100 is used to perform any of the above methods.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A power control method, characterized in that: Executed by a network device, the method includes: First configuration information is sent to a terminal, where the first configuration information is used to configure the terminal to support independent power control of a sounding reference signal (SRS) in multiple power control adjustment states.

2. The method according to claim 1, characterized in that The method further comprises: Sending downlink control information DCI to the terminal, wherein: The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a transmission power control (TPC) command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, where the closed-loop index is used to determine a power control adjustment state associated with the TPC command; or The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or The DCI is a packet-common DCI, including at least one user information block, and the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal; or The DCI is a scheduling DCI, including an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command; or The DCI is a scheduling DCI, including an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or The DCI is a scheduling DCI, and includes an information indication field of a TPC command of the terminal.

3. The method according to claim 2, characterized in that The TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

4. The method according to claim 2 or 3, characterized in that The DCI is in DCI format 2-3, the higher layer parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the information element IE of SRS carrier switching is configured as 3.

5. The method according to claim 4, characterized in that The cc_IndexInOneCC_Set in the SRS carrier switching IE is configured as the index of the current component carrier CC.

6. The method according to claim 4 or 5, characterized in that The DCI is not configured with an SRS request information indication field; or, The DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that an aperiodic SRS resource set is not triggered, or a high-layer parameter is configured as an aperiodic SRS resource set on a CC of a fourth set.

7. The method according to claim 2 or 3, characterized in that The DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as the first type, which is a type other than type A and type B. The DCI is not configured with a corresponding CC_SetIndexlist.

8. The method according to claim 7, characterized in that The DCI is not configured with an SRS request information indication field; or, The DCI is configured with an SRS request information indication field, and a first code point of the SRS request information indication field is configured to indicate that an aperiodic SRS resource set is not triggered, or a higher layer parameter srs-TPC-PDCCH-Group is configured as the first type.

9. The method according to claim 2 or 3, characterized in that The terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats: DCI format 1-1; DCI formats 1-2; DCI format 0-1; DCI formats 0-2; DCI formats 2-3; DCI format 2-X.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Sending second configuration information to the terminal, wherein the second configuration information is used to configure the associated different power control adjustment of the terminal Whether the SRS resource sets in the state use the same TPC command, or whether only one TPC command is valid for configuring the terminal.

11. The method according to any one of claims 1 to 10, characterized in that The SRS includes at least one of the following: Periodic SRS; Semi-continuous SRS; Aperiodic SRS.

12. A power control method, characterized in that: Executed by a terminal, the method includes: First configuration information sent by a network device is received, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

13. The method according to claim 12, characterized in that The method further comprises: Receive DCI sent by the network device, wherein: The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command, where the closed-loop index is used to determine a power control adjustment state associated with the TPC command; or The DCI is a packet-common DCI, including at least one user information block, where the user information block corresponding to the terminal includes an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or The DCI is a packet-common DCI, including at least one user information block, and the user information block corresponding to the terminal includes an information indication field of a TPC command of the terminal; or The DCI is a scheduling DCI, including an information indication field of a TPC command of the terminal and an information indication field of a closed-loop index corresponding to the TPC command; or The DCI is a scheduling DCI, including an information indication field of a TPC command corresponding to different closed-loop indexes of the terminal; or The DCI is a scheduling DCI, and includes an information indication field of a TPC command of the terminal.

14. The method according to claim 13, wherein: The TPC commands corresponding to different closed-loop indexes of the same terminal are configured with the same adjustment method, which is power adjustment based on a cumulative value or an absolute value.

15. The method according to claim 13 or 14, characterized in that The DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as type A, and the cc_SetIndex in the SRS carrier switching IE is configured as 3.

16. The method according to claim 15, characterized in that The cc_IndexInOneCC_Set in the SRS carrier switching IE is configured as the index of the current CC.

17. The method according to claim 15 or 16, characterized in that The DCI is not configured with an SRS request information indication field; or, The DCI is configured with an SRS request information indication field, and the first code point of the SRS request information indication field is configured to indicate that an aperiodic SRS resource set is not triggered, or a high-layer parameter is configured as an aperiodic SRS resource set on a CC of a fourth set.

18. The method according to claim 13 or 14, characterized in that The DCI is DCI format 2-3, and the high-layer parameter srs-TPC-PDCCH-Group is configured as the first type, which is a type other than type A and type B. The DCI is not configured with a corresponding CC_SetIndexlist.

19. The method according to claim 18, characterized in that The DCI is not configured with an SRS request information indication field; or, The DCI is configured with an SRS request information indication field, and a first code point of the SRS request information indication field is configured to indicate that an aperiodic SRS resource set is not triggered, or a higher layer parameter srs-TPC-PDCCH-Group is configured as the first type.

20. The method according to claim 13 or 14, characterized in that The terminal does not support SRS carrier switching capability, and the DCI is in one of the following formats: DCI format 1-1; DCI formats 1-2; DCI format 0-1; DCI formats 0-2; DCI formats 2-3; DCI format 2-X.

21. The method according to any one of claims 12 to 20, characterized in that: The method further comprises: Receive second configuration information sent by the network device, where the second configuration information is used to configure whether SRS resource sets associated with different power control adjustment states of the terminal use the same TPC command, or to configure whether only one TPC command is effective for the terminal.

22. The method according to any one of claims 12 to 21, characterized in that The SRS includes at least one of the following: Periodic SRS; Semi-continuous SRS; Aperiodic SRS.

23. A communication device, characterized in that: include: The transceiver module is configured to send first configuration information to the terminal, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

24. A communication device, characterized in that: include: The transceiver module is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure the terminal to support SRS independent power control in multiple power control adjustment states.

25. A communication device, characterized in that: include: one or more processors; The communication device is configured to execute the method according to any one of claims 1 to 22.

26. A communication system, characterized in that: The invention comprises a terminal and a network device, wherein the network device is configured to implement the method according to any one of claims 1 to 11, and the terminal is configured to implement the method according to any one of claims 12 to 22.

27. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 22.

28. A computer program product comprising a computer program, characterized in that When the computer program is executed by a communication device, the method according to any one of claims 1 to 22 is implemented.

Images