Method and apparatus used in node for wireless communication

Abstract

Disclosed in the present application are a method and apparatus used in a node for wireless communication. The method comprises: a first receiver receiving first signaling, wherein a first PUSCH depends on the first signaling; and a first transmitter reporting a first power headroom report, wherein the determination of the first power headroom report depends on whether the first PUSCH occupies a first-type symbol in the time domain, and the first-type symbol comprises a symbol that is indicated as a downlink symbol by uplink and downlink TDD configuration signaling and that is available for uplink transmission.

Description

A method and device used in a node for wireless communication Technical Field

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a transmission method and apparatus for wireless signals in a wireless communication system supporting a cellular network. Background Art

[0002] In existing NR (New Radio) systems, spectrum resources are statically divided into FDD (Frequency Division Duplex) and TDD (Time Division Duplex) spectrum. For TDD spectrum, both base stations and user equipment (UE) operate in half-duplex mode. This half-duplex mode avoids self-interference and mitigates the impact of cross-link interference (CLI), but it also leads to reduced resource utilization and increased latency. To address these issues, supporting flexible duplex modes or variable link directions (uplink, downlink, or flexible) in TDD or FDD spectrum has become a possible solution. The 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) 1#103e meeting agreed to research on duplex technologies, specifically the proposed Subband Non-Overlapping Full Duplex (SBFD) mode for gNB (NR Node B). In this mode, the same symbol will be used for uplink in part of the frequency resources and for downlink in another part of the frequency resources, thereby improving resource utilization and reducing latency.

[0003] Summary of the Invention

[0004] When symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission are configured to the UE, corresponding enhancement of power headroom reporting is a key issue that must be considered in system design; the present application discloses a solution to the above problem. It should be noted that the present application can be applied to a variety of wireless communication scenarios, such as scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex mode, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex mode) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other at will.

[0005] When necessary, for explanation of the terms in this application, reference may be made to the description of the TS37 series and TS38 series of specification protocols of 3GPP (3rd Generation Partner Project).

[0006] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0007] receiving a first signaling, where the first PUSCH depends on the first signaling;

[0008] Reporting the first power headroom report;

[0009] The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0010] As an embodiment, the problem to be solved by the present application includes: how to determine the first power headroom report based on the symbols occupied by the first PUSCH.

[0011] As an embodiment, the problems to be solved by the present application include: how to improve the flexibility of power headroom reporting or the efficiency of power headroom reporting when symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission are configured to the UE.

[0012] As an embodiment, the problem to be solved by this application includes: how to improve uplink transmission performance.

[0013] As an embodiment, the benefits of the above method include: being conducive to improving uplink transmission performance.

[0014] As an embodiment, the benefits of the above method include: improving the flexibility of power headroom reporting, or improving the efficiency of power headroom reporting.

[0015] As an embodiment, the above method provides a unified solution applicable to single serving cell configuration and multiple serving cell configuration, reducing the processing complexity of the UE.

[0016] As an embodiment, the advantages of the above method include: good compatibility with 3GPP standard protocols and small workload for standardization.

[0017] According to one aspect of the present application, the above method is characterized in that:

[0018] Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0019] As an embodiment, the benefits of the above method include: it is facilitating the selection of an appropriate PUSCH transmission form (actual PUSCH transmission or reference PUSCH transmission) according to the symbol type occupied by the first PUSCH to determine the first power headroom report, thereby improving the effect of the power headroom report.

[0020] According to one aspect of the present application, the above method is characterized in that:

[0021] The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

[0022] According to one aspect of the present application, the above method is characterized in that:

[0023] The first power headroom reporting is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0024] As an embodiment, the above method has the following benefits: improving the reporting flexibility of power headroom reporting based on reference PUSCH transmission, which helps the base station obtain more or more effective power headroom information.

[0025] As an embodiment, the above method has the following benefits: in a scenario where the first type of compliance is configured, the reporting performance of the power headroom when there is no applicable actual PUSCH transmission is improved.

[0026] According to one aspect of the present application, the above method is characterized in that:

[0027] The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index.

[0028] As an embodiment, the above method has the following benefits: improving the reporting flexibility of power headroom reporting based on reference PUSCH transmission, which helps the base station obtain more or more effective power headroom information.

[0029] As an embodiment, the above method has the following benefits: in a scenario where the first type of compliance is configured, the reporting performance of the power headroom when there is no applicable actual PUSCH transmission is improved.

[0030] According to one aspect of the present application, the above method is characterized in that:

[0031] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0032] According to one aspect of the present application, the above method is characterized in that:

[0033] The first power headroom report is reported on the first PUSCH.

[0034] As an embodiment, the benefits of the above method include: being conducive to reducing the transmission delay of the first power headroom report.

[0035] According to one aspect of the present application, the above method is characterized in that it includes:

[0036] Reporting the second power headroom report;

[0037] The first power headroom report and the second power headroom report are reported on the same PUSCH, and the first power headroom report and the second power headroom report are respectively for uplink transmission on different types of symbols.

[0038] As an embodiment, the above method has the following benefits: it helps the base station to obtain power headroom information for uplink transmission on different types of symbols in a timely manner.

[0039] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0040] Sending a first signaling, where the first PUSCH depends on the first signaling;

[0041] receiving a first power headroom report;

[0042] The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0043] According to one aspect of the present application, the above method is characterized in that:

[0044] Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0045] According to one aspect of the present application, the above method is characterized in that:

[0046] The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

[0047] According to one aspect of the present application, the above method is characterized in that:

[0048] The first power headroom reporting is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0049] According to one aspect of the present application, the above method is characterized in that:

[0050] The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index.

[0051] According to one aspect of the present application, the above method is characterized in that:

[0052] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0053] According to one aspect of the present application, the above method is characterized in that:

[0054] The first power headroom report is received on the first PUSCH.

[0055] According to one aspect of the present application, the above method is characterized in that it includes:

[0056] receiving a second power headroom report;

[0057] The first power headroom report and the second power headroom report are received on the same PUSCH, and the first power headroom report and the second power headroom report are respectively for uplink transmission on different types of symbols.

[0058] The present application discloses a first node used for wireless communication, characterized by comprising:

[0059] A first receiver receives a first signaling, wherein the first PUSCH depends on the first signaling;

[0060] A first transmitter reports a first power headroom report;

[0061] The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0062] The present application discloses a second node used for wireless communication, characterized by comprising:

[0063] A second transmitter sends a first signaling, where the first PUSCH depends on the first signaling;

[0064] a second receiver, receiving a first power headroom report;

[0065] The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0067] FIG1 shows a processing flow chart of a first node according to an embodiment of the present application;

[0068] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0069] FIG3 shows a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0070] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0071] FIG5 shows a signal transmission flow chart according to an embodiment of the present application;

[0072] FIG6 is a schematic diagram illustrating that the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain according to an embodiment of the present application;

[0073] FIG7 is a schematic diagram illustrating that the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain according to an embodiment of the present application;

[0074] FIG8 shows a schematic diagram illustrating a first power headroom reporting according to an embodiment of the present application;

[0075] FIG9 shows a schematic diagram illustrating a first power headroom reporting according to an embodiment of the present application;

[0076] FIG10 is a schematic diagram illustrating that the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain according to an embodiment of the present application;

[0077] FIG11 is a schematic diagram illustrating that the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain according to an embodiment of the present application;

[0078] FIG12 is a schematic diagram illustrating that the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain according to an embodiment of the present application;

[0079] FIG13 shows a schematic diagram illustrating a first type of symbol according to an embodiment of the present application;

[0080] FIG14 shows a schematic diagram illustrating a second power headroom reporting according to an embodiment of the present application;

[0081] FIG15 shows a structural block diagram of a processing device in a first node device according to an embodiment of the present application;

[0082] FIG16 shows a structural block diagram of a processing device in a second node device according to an embodiment of the present application. DETAILED DESCRIPTION

[0083] The technical solution of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other at will.

[0084] Example 1

[0085] Example 1 illustrates a processing flow chart of a first node according to an embodiment of the present application, as shown in FIG1 .

[0086] In embodiment 1, the first node in the present application receives a first signaling in step 101 ; and reports a first power headroom report in step 102 .

[0087] In embodiment 1, the first PUSCH depends on the first signaling; the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0088] As an embodiment, the first signaling is uplink scheduling signaling.

[0089] As an embodiment, the first signaling is DCI (Downlink control information).

[0090] As an embodiment, the first signaling is in DCI format.

[0091] As an embodiment, the advantages of the above method include: small scheduling delay.

[0092] As an embodiment, the first signaling is higher layer signaling.

[0093] As an embodiment, the first signaling is MAC CE.

[0094] As an embodiment, the first signaling includes at least one IE (Information Element).

[0095] As an embodiment, the first signaling is RRC signaling.

[0096] As an embodiment, the first signaling is RRC signaling.

[0097] As an embodiment, the benefits of the above method include: reducing scheduling signaling overhead.

[0098] As an embodiment, the first signaling includes configuration information of the first PUSCH.

[0099] As an embodiment, the first PUSCH is scheduled by the first signaling.

[0100] As an embodiment, the first PUSCH is triggered by the first signaling.

[0101] As an embodiment, the first PUSCH is a configured grant PUSCH (Physical uplink shared channel).

[0102] As an embodiment, the first PUSCH is a PUSCH repetition among multiple PUSCH repetitions.

[0103] As an embodiment, the first signaling indicates the time domain resources occupied by the first PUSCH.

[0104] As an embodiment, the first node reports a power headroom for a serving cell on the first PUSCH.

[0105] As an embodiment, the first node reports the power headroom for multiple serving cells on the first PUSCH.

[0106] As an embodiment, the expression "reporting the first power headroom report" means: sending at least the first power headroom report on a PUSCH.

[0107] As an embodiment, reporting a power headroom report on a PUSCH means that information included in the power headroom report is transmitted via the PUSCH.

[0108] As an embodiment, the first power headroom report is reported on the first PUSCH.

[0109] As an embodiment, the first node multiplexes the MAC CE (Control Element(s)) carrying the first power headroom report and other MAC CEs or MAC SDUs (Service Data Unit(s)) into a transmission block, and the one transmission is passed to the physical layer and then sent through the first PUSCH.

[0110] As an embodiment, the first power headroom report is reported on a second PUSCH, and the second PUSCH and the first PUSCH are respectively on different serving cells.

[0111] As an embodiment, the first node multiplexes the MAC CE (Control Element(s)) carrying the first power headroom report and other MAC CEs or MAC SDUs into one transmission block, and the one transmission is passed to the physical layer and then sent through the second PUSCH.

[0112] As an embodiment, the second PUSCH is scheduled by the DCI format.

[0113] As an embodiment, the second PUSCH is a configuration-granted PUSCH.

[0114] As an embodiment, the time slot where the first PUSCH is located overlaps with the time slot where the second PUSCH is located.

[0115] As an embodiment, the time slot where the first PUSCH is located completely overlaps with the time slot where the second PUSCH is located.

[0116] As an embodiment, the time slot where a PUSCH is located refers to the serving cell where the PUSCH is located or the activated BWP.

[0117] As an embodiment, the first power headroom report (Power Headroom Report, PHR) is a power headroom level (power headroom level) indicated by a power headroom field.

[0118] As an embodiment, the first power headroom report includes a power headroom.

[0119] As an embodiment, the first power headroom reporting includes at least one field in a MAC CE for power headroom reporting.

[0120] As an embodiment, the first power headroom reporting is carried by a MAC CE used for power headroom reporting.

[0121] As an embodiment, the first power headroom report is carried by a single entry PHR MAC CE (Single Entry PHR MAC CE).

[0122] As an embodiment, the first power headroom report is carried by a multiple entry PHR MAC CE (Multiple Entry PHR MAC CE).

[0123] As an embodiment, the first power headroom report is a Type 1 power headroom report (Type 1 power headroom report).

[0124] As an embodiment, the first power headroom reporting is for PUSCH transmission.

[0125] As an embodiment, the first power headroom reporting is for an activated BWP of a carrier of a serving cell.

[0126] As an embodiment, the first power headroom report is for the serving cell where the first PUSCH is located.

[0127] As an embodiment, the statement "the determination of the first power margin reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain" means: whether the first power margin reporting is based on actual PUSCH transmission or based on reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0128] As an embodiment, the power headroom reporting based on actual PUSCH transmission includes the power headroom of actual PUSCH transmission.

[0129] As an embodiment, the power headroom reporting based on the reference PUSCH transmission includes the power headroom of the reference PUSCH transmission.

[0130] As an embodiment, the first power headroom report is for PUSCH transmission on the first type of symbols; whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0131] As an embodiment, the first power headroom report is for PUSCH transmission on the first type of symbol; the statement “determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbol in the time domain” means:

[0132] Whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission is related to whether the first PUSCH occupies the first type of symbols in the time domain; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom report is based on reference PUSCH transmission.

[0133] As an embodiment, the first power margin reporting is for PUSCH transmission on symbols other than the first category of symbols; whether the first power margin reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first category of symbols in the time domain.

[0134] As an embodiment, the first power headroom reporting is for PUSCH transmission on symbols other than the first type of symbols; the statement “determination of the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain” means:

[0135] Whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission is related to whether the first PUSCH occupies the first type of symbols in the time domain; when the first PUSCH occupies the first type of symbols in the time domain, the first power headroom report is based on reference PUSCH transmission.

[0136] As an embodiment, the first power headroom report is based on the reference PUSCH transmission; the statement "the determination of the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain" means: the path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0137] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission; the statement “determination of the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbol in the time domain” means:

[0138] The path loss estimate used to calculate the first power headroom report is related to whether the first PUSCH occupies the first type of symbol in the time domain; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the second reference signal resource index.

[0139] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission, and the alpha value used to calculate the first power headroom reporting is related to whether the first PUSCH occupies the first type of symbols in the time domain.

[0140] As an embodiment, the first power headroom report is based on a reference PUSCH transmission, and the PUSCH power control adjustment state (PUSCH power control adjustment state) used to calculate the first power headroom report is related to whether the first PUSCH occupies the first type of symbols in the time domain.

[0141] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission, and the alpha value used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0142] As an embodiment, the first power headroom report is based on a reference PUSCH transmission, and the PUSCH power control adjustment state (PUSCH power control adjustment state) used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0143] As an embodiment, when the information provided by the first power headroom report includes power headroom information of uplink transmission on the first type of symbols, the first power headroom report is for the uplink transmission on the first type of symbols.

[0144] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbols, and the receiving end of the first power headroom report can use the information provided by the first power headroom report to decide how to schedule uplink transmission on the first type of symbols.

[0145] As an embodiment, when the information provided by the first power headroom report includes power headroom information of uplink transmission on symbols other than the first category of symbols, the first power headroom report is for the uplink transmission on the symbols other than the first category of symbols.

[0146] As an embodiment, the first power headroom report is for uplink transmission on symbols other than the first category of symbols, and the receiving end of the first power headroom report can use the information provided by the first power headroom report to decide how to schedule uplink transmission on the symbols other than the first category of symbols.

[0147] As an embodiment, when the time domain resources allocated to a PUSCH include a symbol, the PUSCH occupies the symbol in the time domain; when the time domain resources allocated to a PUSCH do not include a symbol, the PUSCH does not occupy the symbol in the time domain.

[0148] As an embodiment, when the time domain resources occupied by a PUSCH include a symbol, the PUSCH occupies this symbol in the time domain; when the time domain resources occupied by a PUSCH do not include a symbol, the PUSCH does not occupy this symbol in the time domain.

[0149] As an embodiment, when the time domain resources allocated to a PUSCH overlap with a symbol, the PUSCH occupies the symbol in the time domain; when the time domain resources allocated to a PUSCH do not overlap with a symbol, the PUSCH does not occupy the symbol in the time domain.

[0150] As an embodiment, when a PUSCH overlaps with a symbol in the time domain, the PUSCH occupies the symbol in the time domain; when a PUSCH does not overlap with a symbol in the time domain, the PUSCH does not occupy the symbol in the time domain.

[0151] As an embodiment, from the perspective of the time domain: when at least part of a PUSCH is transmitted on a symbol, the PUSCH occupies the symbol in the time domain; otherwise, the PUSCH does not occupy the symbol in the time domain.

[0152] As an embodiment, the first PUSCH occupies only the first type of symbols in the time domain, or only occupies symbols other than the first type of symbols.

[0153] As an embodiment, the benefits of the above method include: reducing the complexity of system design.

[0154] As an embodiment, a symbol in the present application is a time domain symbol.

[0155] As an embodiment, a symbol in the present application is an OFDM (Orthogonal frequency division multiplex) symbol.

[0156] As an embodiment, a symbol in the present application is a symbol in a time slot.

[0157] As an embodiment, a symbol in the present application includes a time duration in the time domain.

[0158] Example 2

[0159] Example 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in FIG2 .

[0160] FIG2 illustrates a diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as an EPS (Evolved Packet System) 200 or some other suitable terminology. The EPS 200 may include one or more UEs (User Equipment) 201, an NG-RAN (Next Generation Radio Access Network) 202, an EPC (Evolved Packet Core) / 5G-CN (5G-Core Network) 210, a Home Subscriber Server (HSS) 220, and an Internet service provider 230. The EPS may interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented herein may be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes an NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol termination towards the UE 201. The gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitter receive node), or some other suitable terminology. The gNB 203 provides an access point to the EPC / 5G-CN 210 for the UE 201. Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things (NB-IoT) device, a machine-type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. Those skilled in the art may also refer to UE 201 as a mobile station, 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, or some other suitable terminology. The gNB 203 is connected to the EPC / 5G-CN 210 via an S1 / NG interface.The EPC / 5G-CN 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / UPF (User Plane Function) 211, other MME / AMF / UPF 214, the S-GW (Service Gateway) 212, and the P-GW (Packet Data Network Gateway) 213. The MME / AMF / UPF 211 is the control node that handles signaling between the UE 201 and the EPC / 5G-CN 210. Generally, the MME / AMF / UPF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through the S-GW 212, which itself is connected to the P-GW 213. The P-GW 213 provides UE IP address allocation and other functions. The P-GW 213 is connected to the Internet service 230. Internet services 230 include operator-specific Internet protocol services, which may include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0161] As an embodiment, the UE201 corresponds to the first node in this application.

[0162] As an embodiment, the gNB203 corresponds to the second node in this application.

[0163] As an embodiment, the UE201 corresponds to the first node in this application, and the gNB203 corresponds to the second node in this application.

[0164] As an embodiment, the gNB203 is a macrocellular base station.

[0165] As an embodiment, the gNB203 is a micro cell base station.

[0166] As an embodiment, the gNB203 is a picocell (PicoCell) base station.

[0167] As an embodiment, the gNB203 is a home base station (Femtocell).

[0168] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0169] As an embodiment, the gNB203 is a flying platform device.

[0170] As an embodiment, the gNB203 is a satellite device.

[0171] Example 3

[0172] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for a first communication node device (UE, gNB, or RSU in V2X) and a second communication node device (gNB, UE, or RSU in V2X), or the control plane 300 between two UEs, using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the first and second communication node devices, as well as the two UEs, via PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first communication node device between the second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling between the second communication node device and the first communication node device. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first communication node device and the second communication node device in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity. Although not shown in the figure, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0173] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0174] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0175] As an embodiment, the first signaling in the present application is generated in the RRC sublayer 306.

[0176] As an embodiment, the first signaling in the present application is generated in the MAC sublayer 302.

[0177] As an embodiment, the first signaling in this application is generated by the PHY301.

[0178] As an embodiment, the first power headroom report in the present application is generated in the MAC sublayer 302 .

[0179] As an embodiment, the second power headroom report in the present application is generated in the MAC sublayer 302 .

[0180] Example 4

[0181] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0182] The first communications device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 , and an antenna 420 .

[0183] The second communication device 450 includes a controller / processor 459 , a memory 460 , a data source 467 , a transmit processor 468 , a receive processor 456 , a multi-antenna transmit processor 457 , a multi-antenna receive processor 458 , a transmitter / receiver 454 and an antenna 452 .

[0184] During transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. During transmission from the first communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and allocation of radio resources to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0185] During transmission from the first communications device 410 to the second communications device 450, each receiver 454 at the second communications device 450 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the second communications device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communications device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the first communications device 410 to the second communications device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0186] During transmission from the second communication device 450 to the first communication device 410, a data source 467 is used at the second communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the first communication device 410 described in the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the first communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0187] During transmission from the second communication device 450 to the first communication device 410, the functionality at the first communication device 410 is similar to the reception functionality at the second communication device 450 described for transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to the multi-antenna receive processor 472 and the receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. The controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the second communication device 450 to the first communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0188] As an embodiment, the first node in the present application includes the second communication device 450 , and the second node in the present application includes the first communication device 410 .

[0189] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a relay node.

[0190] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a base station device.

[0191] As a sub-embodiment of the above embodiment, the first node is a relay node, and the second node is a base station device.

[0192] As a sub-embodiment of the above embodiment, the second communication device 450 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0193] As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0194] As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for using positive acknowledgement (ACK) and / or negative acknowledgement (NACK) protocols for error detection to support HARQ operations.

[0195] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives first signaling, a first PUSCH depends on the first signaling; reports a first power headroom report; wherein the determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbol in the time domain, the first type of symbol including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission.

[0196] As a sub-embodiment of the above embodiment, the second communication device 450 corresponds to the first node in this application.

[0197] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first signaling, and a first PUSCH depends on the first signaling; reporting a first power margin report; wherein, the determination of the first power margin report depends on whether the first PUSCH occupies a first type of symbol in the time domain, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0198] As a sub-embodiment of the above embodiment, the second communication device 450 corresponds to the first node in this application.

[0199] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends first signaling, a first PUSCH depends on the first signaling; receives a first power headroom report; wherein the determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbol in the time domain, the first type of symbol including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission.

[0200] As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the second node in this application.

[0201] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: sending a first signaling, a first PUSCH depending on the first signaling; receiving a first power headroom report; wherein, the determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbol in the time domain, the first type of symbol including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0202] As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the second node in this application.

[0203] As an embodiment, at least one of {the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, the data source 467} is used to receive the first signaling in this application.

[0204] As an embodiment, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, the memory 476} is used to send the first signaling in this application.

[0205] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to report the first power margin report in this application.

[0206] As an embodiment, at least one of {the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476} is used to receive the first power headroom report in this application.

[0207] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to report the second power headroom report in this application.

[0208] As an embodiment, at least one of {the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476} is used to receive the second power headroom report in this application.

[0209] Example 5

[0210] Embodiment 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. In FIG5, the first node U1 and the second node U2 communicate with each other via an air interface.

[0211] The first node U1 receives the first signaling in step S511; and reports the first power headroom report on the first PUSCH in step S512.

[0212] The second node U2 sends a first signaling in step S521; and receives a first power headroom report on a first PUSCH in step S522.

[0213] In embodiment 5, the first PUSCH depends on the first signaling; the determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbol in the time domain, the first type of symbol includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission, and the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0214] As a sub-embodiment of Example 5, whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission is related to whether the first PUSCH occupies the first type of symbols in the time domain; the first power headroom report is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom report is based on reference PUSCH transmission.

[0215] As a sub-embodiment of Example 5, whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission is related to whether the first PUSCH occupies the first type of symbols in the time domain; the first power headroom report is for uplink transmission on symbols other than the first type of symbols; when the first PUSCH occupies the first type of symbols in the time domain, the first power headroom report is based on reference PUSCH transmission.

[0216] As a sub-embodiment of Example 5, the first power headroom report is based on the reference PUSCH transmission, and the path loss estimate used to calculate the first power headroom report is related to whether the first PUSCH occupies the first type of symbol in the time domain; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the second reference signal resource index; the first reference signal resource index and the second reference signal resource index are configured separately.

[0217] As an embodiment, the first node U1 is the first node in this application.

[0218] As an embodiment, the second node U2 is the second node in this application.

[0219] As an embodiment, the first node U1 is a UE.

[0220] As an embodiment, the second node U2 is a base station.

[0221] As an embodiment, the air interface between the second node U2 and the first node U1 is a Uu interface.

[0222] As an embodiment, the air interface between the second node U2 and the first node U1 includes a cellular link.

[0223] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a base station device and a user equipment.

[0224] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a satellite device and a user equipment.

[0225] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a relay device and a user equipment.

[0226] As an embodiment, the first power headroom reporting is determined by the first node U1.

[0227] As an embodiment, the first node U1 also reports a second power headroom report, and the second node U2 also receives a second power headroom report; wherein, the first power headroom report and the second power headroom report are reported on the same PUSCH, and the first power headroom report and the second power headroom report are respectively for uplink transmission on different types of symbols.

[0228] Example 6

[0229] Embodiment 6 illustrates a schematic diagram illustrating that the determination of the first power headroom report according to an embodiment of the present application depends on whether the first PUSCH occupies the first type of symbols in the time domain, as shown in FIG6 .

[0230] In embodiment 6, the first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

[0231] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbols; when the first PUSCH occupies the first type of symbols in the time domain, the first power headroom report is based on actual PUSCH transmission.

[0232] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbols; when the first PUSCH occupies the first type of symbols in the time domain, the first node determines whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission.

[0233] As an embodiment, the statement in this application "the first node determines whether the first power headroom report is based on actual PUSCH transmission or based on reference PUSCH transmission" includes: the first node determines by itself whether the first power headroom report is based on actual PUSCH transmission or based on reference PUSCH transmission.

[0234] As an embodiment, the statement in this application that “the first node determines whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission” includes:

[0235] At least one PHR is triggered, and the PUSCH used to report the first power headroom report is scheduled by the first DCI format of the initial transmission of the scheduled transport block since the at least one PHR is triggered; if the reception of the first signaling is no later than the reception of the first DCI format, the first node determines that the first power headroom report is based on the actual PUSCH transmission; otherwise, the first node determines that the first power headroom report is based on the reference PUSCH transmission.

[0236] As an embodiment, the statement in this application that “the first node determines whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission” includes:

[0237] The PUSCH (configured grant) used to report the first power headroom report is a configured granted PUSCH; if the first signaling is received before the first symbol of the PUSCH used to report the first power headroom report minus the PUSCH preparation time, the first node determines that the first power headroom report is based on the actual PUSCH transmission; otherwise, the first node determines that the first power headroom report is based on the reference PUSCH transmission.

[0238] As an embodiment, the statement in this application that “the first node determines whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission” includes:

[0239] At least one PHR is triggered, and the PUSCH used to report the first power headroom report is scheduled by the first DCI format of the initial transmission of the scheduled transport block since the at least one PHR is triggered; if the first signaling is received no later than the first DCI format, the first node determines by itself whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission; otherwise, the first node determines that the first power headroom report is based on reference PUSCH transmission.

[0240] As an embodiment, the statement in this application that “the first node determines whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission” includes:

[0241] The PUSCH (configured grant) used to report the first power headroom report is a configured granted PUSCH; if the first signaling is received before the first symbol of the PUSCH used to report the first power headroom report minus the PUSCH preparation time, the first node determines by itself whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission; otherwise, the first node determines that the first power headroom report is based on reference PUSCH transmission.

[0242] As an embodiment, the statement "the first power headroom reporting is for uplink transmission on the first type of symbols" in the present application means: the first power headroom reporting is for PUSCH transmission on the first type of symbols.

[0243] As an embodiment, when the first power headroom reporting is based on actual PUSCH transmission, the first power headroom reporting is based on the transmission of the first PUSCH.

[0244] As an embodiment, when the first power headroom report is based on actual PUSCH transmission, the first power headroom report is calculated as: the difference (dB (decibel)) between the maximum available power of the first node and the 1.26th power of a first intermediate value; wherein, the first intermediate value is equal to the sum of 3 times the 0.4 power of the number of symbols occupied by the first PUSCH and 2 times the number of subcarriers occupied by the first PUSCH modulo a first reference value, and the first reference value is configured by RRC signaling.

[0245] As an embodiment, when the first power headroom report is based on the reference PUSCH transmission, the first power headroom report is calculated as: the difference (dB) between the maximum available power of the first node and the 1.26th power of the first intermediate value; wherein the first intermediate value is equal to the product of the 2.7th power of the RSRP measured according to a given reference signal and 0.8 plus the decimal part of the measured RSRP, modulo the first reference value, and the first reference value and the given reference signal are both configured by RRC signaling.

[0246] Example 7

[0247] Embodiment 7 illustrates a schematic diagram illustrating that the determination of the first power headroom report according to an embodiment of the present application depends on whether the first PUSCH occupies the first type of symbols in the time domain, as shown in FIG7 .

[0248] In embodiment 7, the first power headroom reporting is for uplink transmission on symbols other than the first type of symbols; when the first PUSCH occupies the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

[0249] As an embodiment, the first power headroom report is for uplink transmission on symbols other than the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom report is based on actual PUSCH transmission.

[0250] As an embodiment, the first power headroom report is for uplink transmission on symbols other than the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first node determines whether the first power headroom report is based on actual PUSCH transmission or reference PUSCH transmission.

[0251] As an embodiment, the statement in this application that "the first power headroom reporting is for uplink transmission on symbols other than the first category of symbols" means that the first power headroom reporting is for PUSCH transmission on symbols other than the first category of symbols.

[0252] As an embodiment, when the first power headroom reporting is based on actual PUSCH transmission, the first power headroom reporting is based on the transmission of the first PUSCH.

[0253] Example 8

[0254] Embodiment 8 illustrates a schematic diagram illustrating a first power headroom reporting according to an embodiment of the present application, as shown in FIG8 .

[0255] In embodiment 8, the first power headroom reporting is based on actual PUSCH transmission, and the first power headroom reporting is calculated as:

[0256] Wherein, the PH is the power headroom to be reported, the P CMAX is the maximum output power configured by the UE in the PUSCH transmission opportunity occupied by the first PUSCH, the P O is a configurable parameter, the is the bandwidth allocated to the PUSCH transmission opportunity occupied by the first PUSCH (expressed in the number of resource blocks), the α is a configurable parameter, the PL is a downlink path loss estimate calculated by the first node based on the configured reference signal, and the f is the PUSCH power control adjustment state for the PUSCH transmission opportunity occupied by the first PUSCH; The K s =1.25, described The C is the number of code blocks transmitted on the first PUSCH, and the K r is the size of the code block r, the N RE is the number of resource particles determined.

[0257] As an embodiment, the advantages of the above method include: high accuracy of power headroom reporting.

[0258] As an embodiment, the above method has the following advantages: fully utilizing the relevant parameters or definitions of the existing power headroom reporting in 3GPP, having good compatibility and low workload for standardization.

[0259] As an embodiment, the μ is configurable.

[0260] As an embodiment, the μ is a subcarrier spacing configuration.

[0261] As an embodiment, the μ is the subcarrier spacing configuration of the BWP (Bandwidth part) where the first PUSCH is located.

[0262] As an embodiment, the μ is the subcarrier spacing configuration of the BWP where a PUSCH other than the first PUSCH is located.

[0263] As an embodiment, the μ is configured by RRC signaling.

[0264] As an embodiment, the P O It is configured by RRC signaling.

[0265] As an embodiment, the P O It is the sum of two components, which are respectively configured by the p0 parameter in a P0-PUSCH-AlphaSet and p0-NominalWithGrant.

[0266] As an embodiment, the P O It is the sum of two components, which are configured by the p0 parameter in p0-PUSCH-Alpha and p0-NominalWithGrant respectively.

[0267] As an embodiment, the α is an alpha parameter in a P0-PUSCH-AlphaSet.

[0268] As an embodiment, the α is the alpha parameter in p0-PUSCH-Alpha.

[0269] As an embodiment, the described The number of symbols of the PUSCH transmission opportunity occupied by the first PUSCH, is the number of subcarriers in PUSCH symbol j excluding DM-RS (Demodulation reference signal(s)) subcarriers and PTRS (Phase-tracking reference signal(s)) samples.

[0270] As an embodiment, the PL=referenceSignalPower−RSRP of higher layer filtering, and the referenceSignalPower and higher layer filter configuration are both configured by higher layer signaling.

[0271] As a sub-embodiment of the above embodiment, the RSRP filtered by a higher layer is obtained by performing L3 (layer 3) filtering on multiple RSRPs obtained by measuring a configured reference signal.

[0272] As an embodiment, f is configurable.

[0273] As an embodiment, f is determined based on a TPC (Transmit power control) command value.

[0274] As an embodiment, f is a TPC command value.

[0275] As an embodiment, f is equal to the TPC command value in the first signaling.

[0276] As an embodiment, the f is indicated by DCI.

[0277] As an embodiment, the first PUSCH is on the activated BWP b0 of the carrier f0 of the serving cell c0.

[0278] As an embodiment, the P O and α are both configured for the activated BWP b0 of the carrier f0 of the serving cell c0.

[0279] As an embodiment, the P O and α are configured for the activated UL BWP (Uplink Bandwidth part) of the carrier f0 of the serving cell c0.

[0280] As an embodiment, the reference signal used to calculate the PL is configured for the activated DL BWP (Downlink Bandwidth part) of the carrier f0 of the serving cell c0.

[0281] Example 9

[0282] Embodiment 9 illustrates a schematic diagram illustrating a first power headroom reporting according to an embodiment of the present application, as shown in FIG9 .

[0283] In embodiment 9, the first power headroom reporting is based on reference PUSCH transmission, and the first power headroom reporting is calculated as:

[0284] Wherein, the PH1 is the power headroom to be reported, the It is when MPR=0dB、A-MPR=0dB、P-MPR=0dB、ΔT C = 0dB, the maximum output power of the UE configuration, the P O,1 is a configurable parameter, α1 is a configurable parameter, PL1 is a downlink path loss estimate calculated by the first node according to the configured reference signal, and f1 is a PUSCH power control adjustment state.

[0285] As an embodiment, the advantages of the above method include: high accuracy of power headroom reporting.

[0286] As an embodiment, the above method has the following advantages: fully utilizing the relevant parameters or definitions of the existing power headroom reporting in 3GPP, having good compatibility and low workload for standardization.

[0287] As an embodiment, f1 is configurable.

[0288] As an embodiment, the f1 is for the transmission opportunity occupied by the reference PUSCH transmission assumed by the first node.

[0289] As an embodiment, the f1 is for the PUSCH transmission opportunity occupied by the PUSCH used to report the first power headroom report.

[0290] As an embodiment, f1 is determined based on a TPC command value.

[0291] As an embodiment, f1 is a TPC command value.

[0292] As an embodiment, the f1 is equal to the TPC command value in the first signaling.

[0293] As an embodiment, the f1 is indicated by DCI.

[0294] As an embodiment, the MPR, the A-MPR, and the P-MPR are different types of maximum power reduction.

[0295] As an embodiment, the MPR, the A-MPR, the P-MPR and the ΔTC For definitions, see TS38.101-1, TS38.101-2 and TS38.101-3.

[0296] As an embodiment, the PL1=referenceSignalPower−RSRP of higher layer filtering, and the referenceSignalPower and higher layer filter configuration are both configured by higher layer signaling.

[0297] As a sub-embodiment of the above embodiment, the RSRP filtered by a higher layer is obtained by performing L3 (layer 3) filtering on multiple RSRPs obtained by measuring a configured reference signal.

[0298] As an embodiment, the P O,1 It is configured by RRC signaling.

[0299] As an embodiment, the P O,1 It is the sum of two components, which are respectively configured by the p0 parameter in a P0-PUSCH-AlphaSet and p0-NominalWithGrant.

[0300] As an embodiment, the P O,1 It is the sum of two components, which are configured by the p0 parameter in p0-PUSCH-Alpha and p0-NominalWithGrant respectively.

[0301] As an embodiment, the α1 is an alpha parameter in a P0-PUSCH-AlphaSet.

[0302] As an embodiment, the α1 is the alpha parameter in p0-PUSCH-Alpha.

[0303] As an embodiment, the first PUSCH is on the activated BWP b0 of the carrier f0 of the serving cell c0.

[0304] As an embodiment, the P O,1 and α1 are both configured for the activated BWP b0 of the carrier f0 of the serving cell c0.

[0305] As an embodiment, the P O,1 and α1 are both configured for the activated UL BWP of the carrier f0 of the serving cell c0.

[0306] As an embodiment, the reference signal used to calculate the PL1 is configured for the activated DL BWP of the carrier f0 of the serving cell c0.

[0307] Example 10

[0308] Embodiment 10 illustrates a schematic diagram illustrating that the determination of the first power headroom report according to an embodiment of the present application depends on whether the first PUSCH occupies the first type of symbols in the time domain, as shown in FIG10 .

[0309] In embodiment 10, the first power headroom reporting is based on reference PUSCH transmission, and the path loss estimate used to calculate the first power headroom reporting is related to whether the first PUSCH occupies the first type of symbols in the time domain.

[0310] As an embodiment, the first power headroom reporting is based on a reference PUSCH transmission, and the path loss estimation used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0311] As an embodiment, the first node determines that the first power headroom reporting is based on a reference PUSCH transmission according to an algorithm defined by the manufacturer.

[0312] As an embodiment, the first node reports two power headroom reports on the same PUSCH, the two power headroom reports are both for the same service cell, one of the two power headroom reports is based on actual PUSCH transmission, and the other of the two power headroom reports is based on reference PUSCH transmission; the first power headroom report is the power headroom report based on reference PUSCH transmission among the two power headroom reports.

[0313] As an embodiment, a reference PUSCH transmission is a PUSCH transmission assumed by the first node for determining power headroom reporting.

[0314] As an embodiment, when the first node determines that the first power headroom report is based on a reference PUSCH transmission, calculation of the first power headroom report does not depend on the time-frequency resources occupied by the actually scheduled PUSCH.

[0315] As an embodiment, when the first node determines that the first power headroom report is based on a reference PUSCH transmission, calculation of the first power headroom report does not depend on the spatial configuration of the actually scheduled PUSCH.

[0316] As an embodiment, the statement "the first power headroom reporting is based on reference PUSCH transmission" includes: calculation of the first power headroom reporting does not depend on the time-frequency resources occupied by the actually scheduled PUSCH.

[0317] As an embodiment, the statement "the first power headroom reporting is based on a reference PUSCH transmission" includes: calculation of the first power headroom reporting does not depend on the spatial configuration of the actually scheduled PUSCH.

[0318] As an embodiment, the first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the first reference signal; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the second reference signal; both the first reference signal and the second reference signal are configurable.

[0319] As an embodiment, the first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index; the first reference signal resource index is different from the second reference signal resource index.

[0320] As an embodiment, the path loss estimation in the present application is a downlink path loss estimation.

[0321] Example 11

[0322] Embodiment 11 illustrates a schematic diagram illustrating that the determination of the first power headroom report according to an embodiment of the present application depends on whether the first PUSCH occupies the first type of symbols in the time domain, as shown in FIG11 .

[0323] In embodiment 11, the first power headroom report is based on reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the second reference signal resource index.

[0324] As an embodiment, the first power headroom report is based on the reference PUSCH transmission, and the path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbol in the time domain; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the first reference signal; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on the second reference signal; both the first reference signal and the second reference signal are configurable.

[0325] As an embodiment, the first power headroom reporting is based on the reference PUSCH transmission, and the power headroom calculated for the first power headroom reporting is linearly correlated with the PL (from a dB perspective); the PL is a downlink path loss estimate; when the first PUSCH occupies the first type of symbol in the time domain, the PL is obtained based on the first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the PL is obtained based on the second reference signal resource index; the first reference signal resource index is different from the second reference signal resource index.

[0326] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission, and the first power headroom reporting is calculated as:

[0327] Wherein, the PH is the power headroom to be reported, the It is when MPR=0dB、A-MPR=0dB、P-MPR=0dB、ΔT C = 0dB, the maximum output power of the UE configuration, the P Ois a configurable parameter, α is a configurable parameter, f is the PUSCH power control adjustment state; the PL is a downlink path loss estimate; when the first PUSCH occupies the first type of symbol in the time domain, the PL is obtained based on the first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the PL is obtained based on the second reference signal resource index; the first reference signal resource index is different from the second reference signal resource index.

[0328] As an embodiment, the advantages of the above method include: high accuracy of power headroom reporting.

[0329] As an embodiment, the above method has the following advantages: fully utilizing the relevant parameters or definitions of the existing power headroom reporting in 3GPP, having good compatibility and low workload for standardization.

[0330] As an embodiment, f is configurable.

[0331] As an embodiment, f is for the transmission opportunity occupied by the reference PUSCH transmission assumed by the first node.

[0332] As an embodiment, the f is for the PUSCH transmission opportunity occupied by the PUSCH used to report the first power headroom report.

[0333] As an embodiment, f is determined based on a TPC command value.

[0334] As an embodiment, f is a TPC command value.

[0335] As an embodiment, f is equal to the TPC command value in the first signaling.

[0336] As an embodiment, the f is indicated by DCI.

[0337] As an embodiment, when the first PUSCH occupies the first type of symbols in the time domain, f is a first power control adjustment state; when the first PUSCH does not occupy the first type of symbols in the time domain, f is a second power control adjustment state.

[0338] As an embodiment, the first power control adjustment state and the second power control adjustment state are configured separately.

[0339] As an embodiment, the first power control adjustment state and the second power control adjustment state are different power control adjustment states.

[0340] As an embodiment, the first power control adjustment state and the second power control adjustment state are configured as the same power control adjustment state.

[0341] As an embodiment, the MPR, the A-MPR, and the P-MPR are different types of maximum power reduction.

[0342] As an embodiment, the MPR, the A-MPR, the P-MPR and the ΔT C For definitions, see TS38.101-1, TS38.101-2 and TS38.101-3.

[0343] As an embodiment, the PL=referenceSignalPower–higher layer filtered RSRP (higher layer filtered RSRP), the referenceSignalPower and the higher layer filter configuration are both configured by higher layer signaling, and the higher layer filtered RSRP is based on measurements performed on the reference signal resource corresponding to the first reference signal resource index (when the first PUSCH occupies the first type of symbol in the time domain) or the reference signal resource corresponding to the second reference signal resource index (when the first PUSCH does not occupy the first type of symbol in the time domain).

[0344] As an embodiment, the RSRP filtered by a higher layer is obtained by filtering multiple RSRPs obtained by measuring at least a first reference signal (when the first PUSCH occupies the first type of symbol in the time domain) or at least a second reference signal (when the first PUSCH does not occupy the first type of symbol in the time domain) through L3 (layer 3); the first reference signal is transmitted on the reference signal resource corresponding to the first reference signal resource index, and the second reference signal is transmitted on the reference signal resource corresponding to the second reference signal resource index.

[0345] As an embodiment, the P O It is configured by RRC signaling.

[0346] As an embodiment, the P O The determination is related to whether the first PUSCH occupies the first type of symbols in the time domain.

[0347] As an embodiment, when the first PUSCH occupies the first type of symbol in the time domain, Oand the P when the first PUSCH does not occupy the first type of symbol in the time domain O They are configured by different RRC signaling.

[0348] As an embodiment, the P O It is the sum of two components, which are respectively configured by a p0 parameter in a P0-PUSCH-AlphaSet and p0-NominalWithGrant.

[0349] As an embodiment, the P O It is the sum of two components, which are configured by the p0 parameter in p0-PUSCH-Alpha and p0-NominalWithGrant respectively.

[0350] As an embodiment, the α is an alpha parameter in a P0-PUSCH-AlphaSet.

[0351] As an embodiment, the α is the alpha parameter in p0-PUSCH-Alpha.

[0352] As an embodiment, when the first PUSCH occupies the first type of symbols in the time domain, the α is a first alpha parameter; when the first PUSCH does not occupy the first type of symbols in the time domain, the α is a second alpha parameter.

[0353] As an embodiment, the first alpha parameter is an alpha parameter in a P0-PUSCH-AlphaSet.

[0354] As an embodiment, the first alpha parameter is the alpha parameter in p0-PUSCH-Alpha.

[0355] As an embodiment, the second alpha parameter is an alpha parameter in a P0-PUSCH-AlphaSet.

[0356] As an embodiment, the second alpha parameter is the alpha parameter in p0-PUSCH-Alpha.

[0357] As an embodiment, the first alpha parameter and the second alpha parameter are configured separately.

[0358] As an embodiment, the first PUSCH is on the activated BWP b0 of the carrier f0 of the serving cell c0.

[0359] As an embodiment, the PO and α are both configured for the activated BWP b0 of the carrier f0 of the serving cell c0.

[0360] As an embodiment, the P O and α are both configured for the activated UL BWP of the carrier f0 of the serving cell c0.

[0361] As an embodiment, the reference signal used to calculate the PL is configured for the activated DL BWP of the carrier f0 of the serving cell c0.

[0362] As an embodiment, the first reference signal and the second reference signal are configured separately.

[0363] As an embodiment, the first reference signal is transmitted on the reference signal resource corresponding to the first reference signal resource index, and the second reference signal is transmitted on the reference signal resource corresponding to the second reference signal resource index.

[0364] As an embodiment, the first reference signal is a CSI-RS (Channel state information reference signal).

[0365] As an embodiment, the first reference signal resource index is a CSI-RS resource index (CSI-RS resource index).

[0366] As an embodiment, the first reference signal is an SS / PBCH block.

[0367] As an embodiment, the first reference signal resource index is an SS / PBCH block index.

[0368] As an embodiment, the second reference signal is a CSI-RS.

[0369] As an embodiment, the second reference signal resource index is a CSI-RS resource index (CSI-RS resource index).

[0370] As an embodiment, the second reference signal is an SS / PBCH block.

[0371] As an embodiment, the second reference signal resource index is an SS / PBCH block index.

[0372] As an embodiment, the first reference signal resource index is different from the second reference signal resource index.

[0373] As an embodiment, the first reference signal resource index and the second reference signal resource index are respectively allocated and configured.

[0374] As an embodiment, the first reference signal resource index and the second reference signal resource index are indexes of different reference signal resources respectively.

[0375] As an embodiment, the first reference signal resource index and the second reference signal resource index are respectively indicated by different pusch-PathlossReferenceRS-Ids.

[0376] As an embodiment, the first reference signal is configured to occupy the first type of symbols in the time domain.

[0377] As an embodiment, the second reference signal is configured to occupy symbols other than the first type of symbols in the time domain.

[0378] As an embodiment, the first power headroom report is based on the reference PUSCH transmission, and the power headroom calculated for the first power headroom report (from the dB perspective) is equal to the sum of the 2.3th power of the PL and 6.7 times the number of bits reserved for the first power headroom report; the PL is a downlink path loss estimate; when the first PUSCH occupies the first type of symbol in the time domain, the PL is obtained based on the second reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the PL is obtained based on the first reference signal resource index; the first reference signal resource index is different from the second reference signal resource index.

[0379] Example 12

[0380] Embodiment 12 illustrates a schematic diagram illustrating that the determination of the first power headroom report according to an embodiment of the present application depends on whether the first PUSCH occupies the first type of symbols in the time domain, as shown in FIG12 .

[0381] In embodiment 12, the first power headroom report is for uplink transmission on the first type of symbol; when the first PUSCH does not occupy the first type of symbol in the time domain, the determination of the transmit power of the first PUSCH depends on the bandwidth allocated to the first PUSCH and the first path loss estimate, and the calculation of the first power headroom report depends on the bandwidth allocated to the first PUSCH and the second path loss estimate, and the second path loss estimate is different from the first path loss estimate; when the first PUSCH occupies the first type of symbol in the time domain, the determination of the transmit power of the first PUSCH and the calculation of the first power headroom report depend on the same path loss estimate.

[0382] As an embodiment, the benefits of the above method include: it is helpful to reduce the amount of calculation on the UE side by utilizing the relationship between the transmit power of the first PUSCH and the first power headroom reporting.

[0383] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbol; when the first PUSCH does not occupy the first type of symbol in the time domain, the first power headroom report is calculated as:

[0384] The transmit power of the first PUSCH is determined as:

[0385] Wherein, the PH is the power headroom to be reported, the P CMAX is the maximum output power configured by the UE, the P O is a configurable parameter, the is the bandwidth allocated to the PUSCH transmission opportunity occupied by the first PUSCH (expressed in the number of resource blocks), the α is a configurable parameter, the PL is a second path loss estimate, and the f is the PUSCH power control adjustment state for the PUSCH transmission opportunity occupied by the first PUSCH; The K s =1.25, described The C is the number of code blocks transmitted on the first PUSCH, and the K r is the size of the code block r, the N RE is the number of determined resource particles; the P CMAX,1 is the maximum output power configured by the UE in the PUSCH transmission opportunity occupied by the first PUSCH, the P O,1is a configurable parameter, α1 is a configurable parameter, PL1 is a first path loss estimate, and f1 is a PUSCH power control adjustment state for the PUSCH transmission opportunity occupied by the first PUSCH.

[0386] As an embodiment, the μ is configurable.

[0387] As an embodiment, the μ is a subcarrier spacing configuration.

[0388] As an embodiment, the μ is the subcarrier spacing configuration of the BWP (Bandwidth part) where the first PUSCH is located.

[0389] As an embodiment, the μ is the subcarrier spacing configuration of the BWP where a PUSCH other than the first PUSCH is located.

[0390] As an embodiment, the μ is configured by RRC signaling.

[0391] As an embodiment, the P CMAX It is the P CMAX,1 .

[0392] As an embodiment, the P CMAX is the maximum output power configured by the UE in the PUSCH transmission opportunity occupied by the first PUSCH, the P CMAX and the P CMAX,1 They are configured for the first category of symbols and symbols other than the first category of symbols respectively.

[0393] As an embodiment, the P O It is the P O,1 .

[0394] As an embodiment, the P O and the P O,1 They are configured separately.

[0395] As an embodiment, the α is the α1.

[0396] As an embodiment, the α and the α1 are configured separately.

[0397] As an embodiment, said f is said f1.

[0398] As an embodiment, the f and the f1 are configured for the first category of symbols and symbols other than the first category of symbols, respectively.

[0399] As an embodiment, the second path loss estimate and the first path loss estimate are downlink path loss estimates calculated based on different configured reference signals.

[0400] As an embodiment, the reference signal used to calculate the second path loss estimate occupies the first type of symbols in the time domain.

[0401] As an embodiment, the reference signal used to calculate the first path loss estimate occupies symbols other than the first type of symbols in the time domain.

[0402] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbol; when the first PUSCH occupies the first type of symbol in the time domain, the first power headroom report is calculated as:

[0403] The transmit power of the first PUSCH is determined as:

[0404] Wherein, the PH is the power headroom to be reported, the P CMAX is the maximum output power configured by the UE in the PUSCH transmission opportunity occupied by the first PUSCH, the P O is a configurable parameter, the is the bandwidth allocated to the PUSCH transmission opportunity occupied by the first PUSCH (expressed in the number of resource blocks), the α is a configurable parameter, the PL is the same path loss estimate, and the f is the PUSCH power control adjustment state for the PUSCH transmission opportunity occupied by the first PUSCH; The K s =1.25, described The C is the number of code blocks transmitted on the first PUSCH, and the K r is the size of the code block r, the N RE is the number of resource particles determined.

[0405] As an embodiment, the PL is a downlink path loss estimate calculated based on a configured reference signal.

[0406] As an embodiment, the PL is a downlink path loss estimate calculated based on a configured reference signal occupying the first type of symbols in the time domain.

[0407] Example 13

[0408] Example 13 illustrates a schematic diagram of the first type of symbols according to an embodiment of the present application, as shown in Figure 13.

[0409] In embodiment 13, the first type of symbols includes symbols indicated as downlink symbols by uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0410] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling but available for uplink transmission to send uplink physical channels / signals, thereby improving the flexibility of uplink scheduling.

[0411] As an embodiment, the benefits of the above method include: facilitating support for full-duplex operation (sub-band non-overlapping or other types).

[0412] As an embodiment, the uplink and downlink TDD configuration signaling includes higher layer signaling.

[0413] As an embodiment, the uplink and downlink TDD configuration signaling includes semi-static signaling.

[0414] As an embodiment, the uplink and downlink TDD configuration signaling includes cell common signaling.

[0415] As an embodiment, the uplink and downlink TDD configuration signaling includes UE group common signaling.

[0416] As an embodiment, the uplink and downlink TDD configuration signaling includes UE-specific signaling.

[0417] As an embodiment, the uplink and downlink TDD configuration signaling includes RRC signaling.

[0418] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more RRC IEs.

[0419] As an embodiment, the uplink and downlink TDD configuration signaling includes multiple RRC IEs.

[0420] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more fields of each RRC IE in multiple RRC IEs.

[0421] As an embodiment, the uplink and downlink TDD configuration signaling is an RRC IE.

[0422] As an embodiment, the uplink and downlink TDD configuration signaling is one or more fields in an RRC IE.

[0423] As an embodiment, the uplink and downlink TDD configuration signaling is signaling indicating the link direction of the symbol.

[0424] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationCommon, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0425] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon but available for uplink transmission to send uplink physical channels / signals, thereby improving the flexibility of uplink scheduling.

[0426] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationDedicated, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0427] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationDedicated but available for uplink transmission to send uplink physical channel / signal numbers, thereby improving the flexibility of uplink scheduling.

[0428] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0429] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated but can be used for uplink transmission to send uplink physical channels / signals, thereby improving the flexibility of uplink scheduling.

[0430] As an embodiment, any of the first-category symbols are symbols that can be used for uplink transmission.

[0431] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUSCH (Physical Uplink Shared CHannel) transmission.

[0432] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission and PUCCH (Physical Uplink Control CHannel) transmission.

[0433] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission and SRS (Sounding Reference Signal) transmission.

[0434] As an embodiment, the expression "available for uplink transmission" means: available for PUSCH transmission, PUCCH transmission, and SRS transmission.

[0435] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission, PUCCH transmission, PRACH (Physical Random Access CHannel) transmission and SRS transmission.

[0436] As an embodiment, the expression "available for uplink transmission" means: available for transmission of UL-SCH (UpLink Shared CHannel(s)).

[0437] As an embodiment, the first symbol is a symbol indicated as a downlink symbol by the uplink and downlink TDD configuration signaling; if the first symbol can be used for uplink transmission, the first symbol is the first type of symbol; otherwise, the first symbol is not the first type of symbol.

[0438] As an embodiment, the symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling are not the first type of symbols.

[0439] As an embodiment, the first type of symbols are symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0440] As an embodiment, there is at least one symbol determined as a flexible symbol by uplink and downlink TDD configuration signaling and belongs to the first category of symbols.

[0441] As an embodiment, whether a symbol determined as a flexible symbol by the uplink / downlink TDD configuration signaling is the first type of symbol is indicated by a first information block.

[0442] As an embodiment, the first information block is carried by higher layer signaling.

[0443] As an embodiment, the first information block is carried by RRC (Radio Resource Control) signaling.

[0444] As an embodiment, the first information block includes information in at least one RRC IE (Information Element).

[0445] As an embodiment, the first information block includes part or all of the fields included in an RRC IE.

[0446] As an embodiment, the first information block includes part or all of the fields included in each RRC IE in multiple RRC IEs.

[0447] As an embodiment, the first information block includes part or all of the fields included in a SIB (System Information Block).

[0448] As an embodiment, the first information block includes part or all of the fields included in the MIB (Master Information Block).

[0449] As an embodiment, the first information block includes part or all of the fields included in SIB1 (System Information Block 1).

[0450] As an embodiment, the first information block includes part or all of the fields included in RMSI (Remaining Minimum System Information).

[0451] As an embodiment, the first information block is cell-common.

[0452] As an embodiment, the first information block is cell-specific.

[0453] As an embodiment, the first information block is group-common.

[0454] As an embodiment, the first information block is user equipment (UE)-dedicated.

[0455] As an embodiment, the first information block is configured per subband.

[0456] As an embodiment, the first information block is configured per BWP (BandWidth Part).

[0457] As an embodiment, the name of the RRC signaling carrying the first information block includes "SBFD".

[0458] As an embodiment, the name of the RRC signaling carrying the first information block includes "subband".

[0459] As an embodiment, the name of the RRC signaling carrying the first information block includes "duplex".

[0460] As an embodiment, the first information block is carried by a MAC CE (Medium Access Control layer Control Element).

[0461] As an embodiment, the first information block includes information in at least one MAC CE.

[0462] As an embodiment, the first information block is carried by dynamic signaling.

[0463] As an embodiment, the first information block is carried by physical layer signaling.

[0464] As an embodiment, the first information block is carried by DCI (Downlink Control Information).

[0465] As an embodiment, the first information block includes information in at least one RRC IE and information in at least one DCI.

[0466] As an embodiment, the first information block includes part or all of the fields in a DCI format.

[0467] As an embodiment, the first information block includes part or all of the fields in DCI format 2_X, where X is a non-negative integer.

[0468] As an embodiment, X is one of 0 to 8.

[0469] As an embodiment, the first information block is used to configure SBFD (SubBand non-overlapping Full Duplex) time slots or symbols.

[0470] As an embodiment, the first information block is used to configure a time slot or symbol supporting full duplex.

[0471] As an embodiment, whether the symbol used for SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) reception is the first type of symbol is configured by the first information block.

[0472] As an embodiment, the above method has the following benefits: it is helpful to ensure the reception performance of the SS / PBCH block through reasonable configuration.

[0473] As an embodiment, the symbols used for SS / PBCH block (synchronization signal and physical broadcast channel block) reception are not the first type of symbols.

[0474] As an embodiment, the first information block is received before the uplink and downlink TDD configuration signaling.

[0475] As an embodiment, the first information block is received after the uplink and downlink TDD configuration signaling.

[0476] As an embodiment, the first information block and the uplink and downlink TDD configuration signaling are received simultaneously.

[0477] As an embodiment, there is at least one symbol determined as a flexible symbol by uplink and downlink TDD configuration signaling that does not belong to the first category of symbols.

[0478] Example 14

[0479] Embodiment 14 illustrates a schematic diagram illustrating a second power headroom reporting according to an embodiment of the present application, as shown in FIG14 .

[0480] In embodiment 14, the first node also reports a second power headroom report; wherein the first power headroom report and the second power headroom report are reported on the same PUSCH, and the first power headroom report and the second power headroom report are respectively for uplink transmission on different types of symbols.

[0481] As an embodiment, the first power headroom reporting is for uplink transmission on the first type of symbols, and the second power headroom reporting is for uplink transmission on symbols other than the first type of symbols.

[0482] As an embodiment, the second power headroom reporting is for uplink transmission on the first type of symbols, and the first power headroom reporting is for uplink transmission on symbols other than the first type of symbols.

[0483] As an embodiment, the expression "reporting the second power headroom report" means: sending at least the second power headroom report on a PUSCH.

[0484] As an embodiment, the second power headroom report is reported on the first PUSCH.

[0485] As an embodiment, the first node multiplexes the MAC CE (Control Element(s)) carrying the second power headroom report and other MAC CEs or MAC SDUs into one transmission block, and the one transmission is passed to the physical layer and then sent through the first PUSCH.

[0486] As an embodiment, the second power headroom report is reported on a second PUSCH, and the second PUSCH and the first PUSCH are respectively on different serving cells.

[0487] As an embodiment, the first node multiplexes the MAC CE (Control Element(s)) carrying the second power headroom report and other MAC CEs or MAC SDUs into one transmission block, and the one transmission is passed to the physical layer and then sent through the second PUSCH.

[0488] As an embodiment, the first power headroom report and the second power headroom report are carried by the same MAC CE.

[0489] As an embodiment, the second power headroom report (Power Headroom Report, PHR) is a power headroom level (power headroom level) indicated by a power headroom field.

[0490] As an embodiment, the second power headroom report includes a power headroom.

[0491] As an embodiment, the second power headroom reporting includes at least one field in a MAC CE for power headroom reporting.

[0492] As an embodiment, the second power headroom reporting is carried by a MAC CE used for power headroom reporting.

[0493] As an embodiment, the second power headroom report is carried by a single entry PHR MAC CE (Single Entry PHR MAC CE).

[0494] As an embodiment, the second power headroom report is carried by a multiple entry PHR MAC CE (Multiple Entry PHR MAC CE).

[0495] As an embodiment, the second power headroom report is a Type 1 power headroom report (Type 1 power headroom report).

[0496] As an embodiment, the second power headroom reporting is for PUSCH transmission.

[0497] As an embodiment, the second power headroom reporting is for an activated BWP of a carrier of a serving cell.

[0498] As an embodiment, the second power headroom report is for the serving cell where the first PUSCH is located.

[0499] As an embodiment, the first power headroom report and the second power headroom report are both for the same serving cell.

[0500] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission, and the second power headroom reporting is based on reference PUSCH transmission.

[0501] As an embodiment, the first power headroom reporting is based on reference PUSCH transmission, and the second power headroom reporting is based on actual PUSCH transmission.

[0502] As an embodiment, the reference signal based on which the path loss estimate for calculating a power headroom report is based is transmitted on a symbol of the symbol type for which the power headroom report is intended.

[0503] As an embodiment, the second power headroom reporting is based on actual PUSCH transmission, and the second power headroom reporting is calculated as:

[0504] Wherein, the PH2 is the power headroom to be reported, the P CMAX,2 is the maximum output power configured by the UE in the PUSCH transmission opportunity occupied by the first PUSCH, the P O,2 is a configurable parameter, the is the bandwidth allocated to the PUSCH transmission opportunity occupied by the first PUSCH (expressed in the number of resource blocks), the α2 is a configurable parameter, the PL2 is a downlink path loss estimate calculated by the first node based on the configured reference signal, and the f2 is the PUSCH power control adjustment state for the PUSCH transmission opportunity occupied by the first PUSCH; The K s =1.25, described The C is the number of code blocks transmitted on the first PUSCH, and the K r is the size of the code block r, the N RE is the number of resource particles determined.

[0505] As an embodiment, the μ is configurable.

[0506] As an embodiment, the μ is a subcarrier spacing configuration.

[0507] As an embodiment, the μ is the subcarrier spacing configuration of the BWP (Bandwidth part) where the first PUSCH is located.

[0508] As an embodiment, the μ is the subcarrier spacing configuration of the BWP where a PUSCH other than the first PUSCH is located.

[0509] As an embodiment, the μ is configured by RRC signaling.

[0510] As an embodiment, the P O,2 It is configured by RRC signaling.

[0511] As an embodiment, the P O,2 It is the sum of two components, which are respectively configured by the p0 parameter in a P0-PUSCH-AlphaSet and p0-NominalWithGrant.

[0512] As an embodiment, the P O,2 It is the sum of two components, which are configured by the p0 parameter in p0-PUSCH-Alpha and p0-NominalWithGrant respectively.

[0513] As an embodiment, the α2 is an alpha parameter in a P0-PUSCH-AlphaSet.

[0514] As an embodiment, the α2 is the alpha parameter in p0-PUSCH-Alpha.

[0515] As an embodiment, the described The number of symbols of the PUSCH transmission opportunity occupied by the first PUSCH, is the number of subcarriers excluding DMRS subcarriers and PTRS samples in PUSCH symbol j.

[0516] As an embodiment, the PL2=referenceSignalPower−RSRP of higher layer filtering, and the referenceSignalPower and higher layer filter configuration are both configured by higher layer signaling.

[0517] As a sub-embodiment of the above embodiment, the RSRP filtered by a higher layer is obtained by performing L3 (layer 3) filtering on multiple RSRPs obtained by measuring a configured reference signal.

[0518] As an embodiment, f2 is configurable.

[0519] As an embodiment, f2 is determined based on a TPC command value.

[0520] As an embodiment, f2 is a TPC command value.

[0521] As an embodiment, f2 is equal to the TPC command value in the first signaling.

[0522] As an embodiment, the f2 is indicated by DCI.

[0523] As an embodiment, the first PUSCH is on the activated BWP b0 of the carrier f0 of the serving cell c0.

[0524] As an embodiment, the P O,2and α are both configured for the activated BWP b0 of the carrier f0 of the serving cell c0.

[0525] As an embodiment, the P O,2 and α are both configured for the activated UL BWP of the carrier f0 of the serving cell c0.

[0526] As an embodiment, the reference signal used to calculate the PL2 is configured for the activated DL BWP of the carrier f0 of the serving cell c0.

[0527] As an embodiment, the second power headroom reporting is based on reference PUSCH transmission, and the second power headroom reporting is calculated as:

[0528] Wherein, the PH2 is the power headroom to be reported, the It is when MPR=0dB、A-MPR=0dB、P-MPR=0dB、ΔT C = 0dB, the maximum output power of the UE configuration, the P O,2 is a configurable parameter, α2 is a configurable parameter, PL2 is a downlink path loss estimate calculated by the first node according to the configured reference signal, and f2 is a PUSCH power control adjustment state.

[0529] As an embodiment, f2 is configurable.

[0530] As an embodiment, f2 is for the transmission opportunity occupied by the reference PUSCH transmission assumed by the first node.

[0531] As an embodiment, f2 is for the PUSCH transmission opportunity occupied by the PUSCH used to report the first power headroom report.

[0532] As an embodiment, the MPR, the A-MPR, and the P-MPR are different types of maximum power reduction.

[0533] As an embodiment, the MPR, the A-MPR, the P-MPR and the ΔT C For definitions, see TS38.101-1, TS38.101-2 and TS38.101-3.

[0534] As an embodiment, the PL2=referenceSignalPower−RSRP of higher layer filtering, and the referenceSignalPower and higher layer filter configuration are both configured by higher layer signaling.

[0535] As an embodiment, the RSRP filtered by a higher layer is obtained by filtering multiple RSRPs obtained by measuring the configured reference signal through L3 (layer 3).

[0536] As an embodiment, the P O,2 It is configured by RRC signaling.

[0537] As an embodiment, the P O,2 It is the sum of two components, which are respectively configured by the p0 parameter in a P0-PUSCH-AlphaSet and p0-NominalWithGrant.

[0538] As an embodiment, the P O,2 It is the sum of two components, which are configured by the p0 parameter in p0-PUSCH-Alpha and p0-NominalWithGrant respectively.

[0539] As an embodiment, the α2 is an alpha parameter in a P0-PUSCH-AlphaSet.

[0540] As an embodiment, the α2 is the alpha parameter in p0-PUSCH-Alpha.

[0541] As an embodiment, the first PUSCH is on the activated BWP b0 of the carrier f0 of the serving cell c0.

[0542] As an embodiment, the P O,2 and α2 are both configured for the activated BWP b0 of the carrier f0 of the serving cell c0.

[0543] As an embodiment, the P O,2 and α2 are both configured for the activated UL BWP of the carrier f0 of the serving cell c0.

[0544] As an embodiment, the reference signal used to calculate the PL2 is configured for the activated DL BWP of the carrier f0 of the serving cell c0.

[0545] As an embodiment, the P CMAX It is the P CMAX,2.

[0546] As an embodiment, the P CMAX and the P CMAX,2 They are configured for the first category of symbols and symbols other than the first category of symbols respectively.

[0547] As an embodiment, the P O It is the P O,2 .

[0548] As an embodiment, the P O and the P O,2 They are configured separately.

[0549] As an embodiment, the α is the α2.

[0550] As an embodiment, the α and the α2 are configured separately.

[0551] As an embodiment, said f is said f2.

[0552] As an embodiment, the f and the f2 are configured for the first category of symbols and symbols other than the first category of symbols, respectively.

[0553] Example 15

[0554] Embodiment 15 illustrates a structural block diagram of a processing device in a first node device, as shown in FIG15. In FIG15, the first node device processing device A00 includes a first receiver A01 and a first transmitter A02.

[0555] As an embodiment, the first node device A00 is a user equipment.

[0556] As an embodiment, the first node device A00 is a relay node.

[0557] As an embodiment, the first node device A00 is a vehicle-mounted communication device.

[0558] As an embodiment, the first node device A00 is a UE with relevant configuration supporting full-duplex operation (non-overlapping sub-bands or other types).

[0559] As an embodiment, the first receiver A01 includes at least one of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0560] As an embodiment, the first receiver A01 includes at least the first five of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0561] As an embodiment, the first receiver A01 includes at least the first four of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0562] As an embodiment, the first receiver A01 includes at least the first three of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0563] As an embodiment, the first receiver A01 includes at least the first two of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0564] As an embodiment, the first transmitter A02 includes at least one of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0565] As an embodiment, the first transmitter A02 includes at least the first five of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0566] As an embodiment, the first transmitter A02 includes at least the first four of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0567] As an embodiment, the first transmitter A02 includes at least the first three of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0568] As an embodiment, the first transmitter A02 includes at least the first two of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0569] As an embodiment, the first receiver A01 receives a first signaling, and the first PUSCH depends on the first signaling; the first transmitter A02 reports a first power margin report; wherein, the determination of the first power margin report depends on whether the first PUSCH occupies a first type of symbol in the time domain, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0570] As an embodiment, whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0571] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom report is based on the reference PUSCH transmission.

[0572] As an embodiment, the first power headroom reporting is based on a reference PUSCH transmission, and the path loss estimation used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0573] As an embodiment, the first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index.

[0574] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0575] As an embodiment, the first power headroom report is reported on the first PUSCH.

[0576] As an embodiment, the first transmitter A02 reports a second power margin report; wherein, the first power margin report and the second power margin report are reported on the same PUSCH, and the first power margin report and the second power margin report are respectively for uplink transmission on different types of symbols.

[0577] Example 16

[0578] Embodiment 16 illustrates a structural block diagram of a processing device in a second node device, as shown in FIG16. In FIG16, the second node device processing device B00 includes a second transmitter B01 and a second receiver B02.

[0579] As an embodiment, the second node device B00 is a base station.

[0580] As an embodiment, the second node device B00 is a satellite device.

[0581] As an embodiment, the second node device B00 is a relay node.

[0582] As an embodiment, the second node device B00 is a base station supporting full-duplex operation (non-overlapping sub-bands or other types).

[0583] As an embodiment, the second node device B00 is a base station that only supports half-duplex operation.

[0584] As an embodiment, the second node device B00 is one of a test device, a test equipment, and a test instrument.

[0585] As an embodiment, the second transmitter B01 includes at least one of the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0586] As an embodiment, the second transmitter B01 includes at least the first five of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0587] As an embodiment, the second transmitter B01 includes at least the first four of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0588] As an embodiment, the second transmitter B01 includes at least the first three of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0589] As an embodiment, the second transmitter B01 includes at least the first two of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0590] As an embodiment, the second receiver B02 includes at least one of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0591] As an embodiment, the second receiver B02 includes at least the first five of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0592] As an embodiment, the second receiver B02 includes at least the first four of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0593] As an embodiment, the second receiver B02 includes at least the first three of the antenna 420, receiver 418, multi-antenna receiving processor 472, receiving processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0594] As an embodiment, the second receiver B02 includes at least the first two of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0595] As an embodiment, the second transmitter B01 sends a first signaling, and the first PUSCH depends on the first signaling; the second receiver B02 receives a first power headroom report; wherein, the determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbol in the time domain, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0596] As an embodiment, whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0597] As an embodiment, the first power headroom report is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom report is based on the reference PUSCH transmission.

[0598] As an embodiment, the first power headroom reporting is based on a reference PUSCH transmission, and the path loss estimation used to calculate the first power headroom reporting depends on whether the first PUSCH occupies the first type of symbols in the time domain.

[0599] As an embodiment, the first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index.

[0600] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0601] As an embodiment, the first power headroom report is received on the first PUSCH.

[0602] As an embodiment, the second receiver B02 receives a second power headroom report; wherein, the first power headroom report and the second power headroom report are received on the same PUSCH, and the first power headroom report and the second power headroom report are respectively for uplink transmissions on different types of symbols.

[0603] Those skilled in the art will appreciate that all or part of the steps in the above method can be performed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, the various module units in the above embodiment can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The first node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The second node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The user equipment, UE, or terminal in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The base station equipment or base station or network side equipment in this application includes but is not limited to macro cell base stations, micro cell base stations, home base stations, relay base stations, eNB, gNB, transmission receiving nodes TRP, GNSS, relay satellites, satellite base stations, aerial base stations, test devices, test equipment, test instruments and other equipment.

[0604] Those skilled in the art will appreciate that the present invention may be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should be considered in all respects as illustrative and not restrictive. The scope of the invention is determined by the appended claims, not the foregoing description, and all modifications that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first signaling, wherein the first PUSCH depends on the first signaling; A first transmitter reports a first power headroom report; The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

2. The first node according to claim 1, characterized in that: Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

3. The first node according to claim 1 or 2, characterized in that: The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

4. The first node according to claim 1, characterized in that: The first power headroom report is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

5. The first node according to claim 1 or 4, characterized in that: The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index; the first reference signal resource index and the second reference signal resource index are configured separately.

6. The first node according to any one of claims 1 to 5, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

7. The first node according to any one of claims 1 to 6, characterized in that: The first power headroom report is reported on the first PUSCH.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first signaling, wherein the first PUSCH depends on the first signaling; A second receiver receives a first power headroom report; The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

9. The second node according to claim 8, characterized in that: Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

10. The second node according to claim 8 or 9, characterized in that: The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

11. The second node according to claim 8, characterized in that: The first power headroom report is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

12. The second node according to claim 8 or 11, characterized in that: The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index; the first reference signal resource index and the second reference signal resource index are configured separately.

13. The second node according to any one of claims 8 to 12, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

14. The second node according to any one of claims 8 to 13, characterized in that: The first power headroom report is reported on the first PUSCH.

15. A method in a first node for wireless communication, characterized in that: include: receiving a first signaling, the first PUSCH depending on the first signaling; Reporting a first power headroom report; The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

16. The method in the first node according to claim 15, characterized in that: Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

17. The method in the first node according to claim 15 or 16, characterized in that: The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

18. The method in the first node according to claim 15, characterized in that: The first power headroom report is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

19. The method in the first node according to claim 15 or 18, characterized in that: The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index; the first reference signal resource index and the second reference signal resource index are configured separately.

20. The method in the first node according to any one of claims 15 to 19, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

21. The method in the first node according to any one of claims 15 to 20, characterized in that: The first power headroom report is reported on the first PUSCH.

22. A method in a second node for wireless communication, characterized in that: include: Sending a first signaling, where the first PUSCH depends on the first signaling; Receiving a first power headroom report; The determination of the first power headroom report depends on whether the first PUSCH occupies a first type of symbols in the time domain, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

23. The method in the second node according to claim 22, characterized in that: Whether the first power headroom reporting is based on actual PUSCH transmission or reference PUSCH transmission depends on whether the first PUSCH occupies the first type of symbols in the time domain.

24. The method in the second node according to claim 22 or 23, characterized in that: The first power headroom reporting is for uplink transmission on the first type of symbols; when the first PUSCH does not occupy the first type of symbols in the time domain, the first power headroom reporting is based on reference PUSCH transmission.

25. The method in the second node according to claim 22, characterized in that: The first power headroom report is based on a reference PUSCH transmission, and a path loss estimate used to calculate the first power headroom report depends on whether the first PUSCH occupies the first type of symbols in the time domain.

26. The method in the second node according to claim 22 or 25, characterized in that: The first power headroom report is based on a reference PUSCH transmission; when the first PUSCH occupies the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a first reference signal resource index; when the first PUSCH does not occupy the first type of symbol in the time domain, the path loss estimate used to calculate the first power headroom report is obtained based on a second reference signal resource index; the first reference signal resource index and the second reference signal resource index are configured separately.

27. The method in the second node according to any one of claims 22 to 26, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

28. The method in the second node according to any one of claims 22 to 27, characterized in that: The first power headroom report is reported on the first PUSCH.

Images