Method and apparatus in communication node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a communication node used for wireless communication. The communication node receives the first RRC message; transmitting first UE assistance information in response to the first set of conditions being satisfied; wherein the first UE auxiliary information comprises at least one of first frequency domain information or first time domain information; the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full duplex; the first condition set comprises at least the first RRC message enabling the first UE auxiliary information. The scheme provided by the invention is beneficial to network configuration and improves the resource utilization rate.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and more particularly to a method and device for reporting UE auxiliary information in full-duplex with non-overlapping sub-bands. Background Art

[0002] The existing NR (New Radio) system divides spectrum resources into FDD (Frequency Division Duplexing) spectrum and TDD (Time Division Duplexing) spectrum. For TDD spectrum, base stations and user equipment (UE) both work in half-duplex mode, which reduces resource utilization and increases latency. In response to these problems, the 3GPP (the 3rd Generation Partnership Project) RAN (Radio Access Network) 1#103e meeting passed the "Study on Evolution of NR Duplex Operation" research project (Study Item, SI), in which subband non-overlapping full duplex was proposed, supporting base station equipment to send and receive simultaneously on two subbands. In 3GPP Release 19, the WI (Work Item) for subband non-overlapping full duplex was further launched.

[0003] UE Assistance Information (UAI) can provide the network with UE preferred configuration information, and assist the base station in configuring the UE. For example, to solve the problem of internal overheating, when the UE detects internal overheating, the UE sends overheating assistance information to the network through the UE assistance information, and the auxiliary network configures according to the capability limitation information indicated by the UE in the overheating assistance information; wherein the overheating assistance information includes the maximum number of carriers, the maximum aggregated bandwidth, and the number of MIMO layers. For another example, the UE assistance information is used to send a preferred DRX (Discontinuous Reception) configuration to the network. Summary of the invention

[0004] The inventors have found through research that for sub-band non-overlapping full-duplex operation, if only relying on network configuration and network scheduling, it is not conducive to differentiated configuration of different UEs. Reporting the relevant information of the sub-band non-overlapping full-duplex through UE auxiliary information will bring certain performance gains; and the introduction of sub-band non-overlapping full-duplex will affect the reporting of overheating auxiliary information. Therefore, it is necessary to study the reporting of UE auxiliary information for sub-band non-overlapping full-duplex.

[0005] In response to the above problems, the present application provides a solution for UE auxiliary information reporting for sub-band non-overlapping full-duplex. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) or 5G+ or 6G systems, achieving technical effects similar to those of the NR system; further, although the present application provides a specific implementation method for sub-band non-overlapping full-duplex, the present application can also be used in scenarios such as sub-band overlapping full-duplex to achieve technical effects similar to those of sub-band non-overlapping full-duplex. Furthermore, adopting a unified design scheme for different scenarios can also help reduce hardware complexity and cost. Furthermore, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 port to achieve technical effects similar to those of the Uu air interface. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the V2X (Vehicle-to-Everything) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve similar technical effects in the terminal and base station scenario. Further, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, to achieve similar technical effects in the terminal and base station scenario. Further, although the original intention of this application is for the terrestrial network (Terrestrial Network, TN) scenario, this application is also applicable to the non-terrestrial network (Non-Terrestrial Network, NTN) communication scenario, to achieve similar technical effects in the TN scenario. In addition, the use of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

[0006] As an example, the interpretation of the terms in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

[0007] As an example, the interpretation of the terms in the present application refers to the definition of the TS37 series of specification protocols of 3GPP.

[0008] It should be noted that, 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 arbitrarily combined with each other.

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

[0010] Receiving a first RRC (Radio Resource Control) message;

[0011] In response to the first set of conditions being met, sending first UE assistance information; wherein the first UE assistance information indicates at least one of first frequency domain information or first time domain information;

[0012] At least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0013] As an embodiment, the problem to be solved by the present application includes: how to determine at least one of the first frequency domain information or the first time domain information included in the first UE auxiliary information.

[0014] As an embodiment, in the above method, at least one of the first frequency domain information or the first time domain information included in the first UE auxiliary information relies on sub-band non-overlapping full-duplex, thereby solving the above problem.

[0015] As an embodiment, the above method can assist the network to configure the sub-band non-overlapping full-duplex for the first node.

[0016] As an embodiment, the above method can assist the network to configure the sub-band non-overlapping full-duplex for the first node based on the first UE auxiliary information.

[0017] As an embodiment, the above method is beneficial for network configuration.

[0018] As an embodiment, the above method is advantageous for a full-duplex configuration with non-overlapping sub-bands.

[0019] As an embodiment, the above method is conducive to network optimization.

[0020] As an embodiment, the above method is conducive to improving resource utilization.

[0021] As an embodiment, the above method reduces unnecessary configuration.

[0022] As an embodiment, the above method improves configuration flexibility.

[0023] As an embodiment, the problem to be solved by the present application includes: how to determine whether to report UE auxiliary information.

[0024] As an embodiment, in the above method, as a response to the first set of conditions being met, first UE auxiliary information is sent, thereby solving the above problem.

[0025] As an embodiment, the characteristics of the above method include: sending the first UE auxiliary information only when the first condition set is met.

[0026] As an embodiment, the characteristics of the above method include: under the assumption that the first condition set is not satisfied, the first UE auxiliary information is not sent.

[0027] As an embodiment, the characteristics of the above method include: the first condition set is satisfied to trigger the sending of the first UE auxiliary information.

[0028] As an embodiment, the above method reduces unnecessary UE auxiliary information.

[0029] As an embodiment, the above method reduces signaling overhead.

[0030] As an embodiment, the problem to be solved by the present application includes: how to determine the first condition set.

[0031] As an embodiment, the above method solves the above problem by enabling the first UE auxiliary information through the first condition set including at least the first RRC message.

[0032] As an embodiment, the characteristics of the above method include: at least the first RRC message enables the first UE auxiliary information before sending the first UE auxiliary information.

[0033] As an embodiment, the characteristics of the above method include: the reporting of the first UE auxiliary information is controlled by the network.

[0034] As an embodiment, the above method is beneficial to network management.

[0035] As an embodiment, the above method reduces unnecessary reporting.

[0036] According to one aspect of the present application, the first condition set includes detecting internal overheating.

[0037] As an embodiment, the problem to be solved by the present application includes: how to determine the first condition set.

[0038] As an embodiment, the above method solves the above problem by having the first condition set include detecting internal overheating.

[0039] As an embodiment, the characteristics of the above method include: sending the first UE assistance information as a response to at least detecting internal overheating and the first RRC message enabling the first UE assistance information.

[0040] As an embodiment, the above method is helpful to solve the internal overheating problem.

[0041] According to one aspect of the present application, it is characterized in that the first condition set includes that the first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

[0042] As an embodiment, the problem to be solved by the present application includes: how to determine the first condition set.

[0043] As an embodiment, the above method solves the above problem by having the first condition set include that the first measurement result reaches a first threshold.

[0044] As an embodiment, the characteristics of the above method include: sending the first UE assistance information as a response to at least the first measurement result reaching a first threshold and the first RRC message enabling the first UE assistance information.

[0045] As an embodiment, the above method is helpful to reduce the reporting of UE auxiliary information.

[0046] As an embodiment, the above method is conducive to timely reporting of UE auxiliary information.

[0047] According to one aspect of the present application, it is characterized by comprising:

[0048] Along with the sending of the first UE auxiliary information, starting a first timer;

[0049] The first condition set includes that the first timer is not running.

[0050] According to one aspect of the present application, it is characterized by comprising:

[0051] Sending first UE capability information;

[0052] The first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex.

[0053] As an embodiment, the problem to be solved by the present application includes: how to notify the network that the UE supports full-duplex without sub-band overlap.

[0054] As an embodiment, the above method solves the above problem by indicating that the first node supports sub-band non-overlapping full-duplex through the first UE capability information.

[0055] As an embodiment, the above method reuses the existing protocol and is simple to implement.

[0056] According to one aspect of the present application, it is characterized by comprising:

[0057] receiving a second RRC message, wherein the second RRC message configures the first symbol as a downlink symbol;

[0058] Performing uplink transmission on the first symbol;

[0059] The performing of uplink transmission on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

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

[0061] Sending a first RRC message;

[0062] receiving first UE capability information; wherein the first UE capability information indicates that the first node supports subband non-overlapping full-duplex; receiving first UE auxiliary information;

[0063] Among them, the first UE auxiliary information indicates the relevant information of the sub-band non-overlapping full-duplex; as a response to the first condition set being met, the sender of the first UE capability information sends the first UE auxiliary information; the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0064] According to one aspect of the present application, the first condition set includes detecting internal overheating.

[0065] According to one aspect of the present application, it is characterized in that the first condition set includes that the first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

[0066] According to one aspect of the present application, it is characterized in that, along with the sending of the first UE auxiliary information, the recipient of the first RRC message starts a first timer; wherein, the first condition set includes that the first timer is not running.

[0067] According to one aspect of the present application, it is characterized by comprising:

[0068] Receiving first UE capability information;

[0069] The first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex.

[0070] According to one aspect of the present application, it is characterized by comprising:

[0071] Sending a second RRC message, wherein the second RRC message configures the first symbol as a downlink symbol;

[0072] performing uplink reception on the first symbol;

[0073] The performing of uplink reception on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

[0074] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0075] A first receiver receives a first RRC message;

[0076] The first transmitter sends first UE assistance information as a response to the first set of conditions being met, wherein the first UE assistance information indicates at least one of first frequency domain information or first time domain information;

[0077] At least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0078] The present application discloses a second node used for wireless communication, characterized in that it includes:

[0079] A second transmitter sends a first RRC message;

[0080] A second receiver receives first UE auxiliary information, wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information;

[0081] In which, as a response to the first condition set being met, the recipient of the first RRC message sends first UE auxiliary information; at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first condition set includes at least the first RRC message enabling the first UE auxiliary information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0083] Figure 1A flow chart showing transmission of a first RRC message and first UE assistance information according to an embodiment of the present application is shown;

[0084] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0085] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0086] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0087] Figure 5 A wireless signal transmission flow chart according to an embodiment of the present application is shown;

[0088] Figure 6 A schematic diagram showing that a first condition set includes detecting internal overheating according to an embodiment of the present application;

[0089] Figure 7 A schematic diagram showing a first condition set including a first measurement result reaching a first threshold according to an embodiment of the present application;

[0090] Figure 8 A schematic diagram of sub-band non-overlapping full-duplex according to an embodiment of the present application is shown;

[0091] Fig. 9 A schematic diagram showing a first frequency domain information dependent sub-band non-overlapping full-duplex according to an embodiment of the present application is shown;

[0092] Fig.10 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown;

[0093] Fig.11 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0094] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0095] Example 1

[0096] Embodiment 1 illustrates a flowchart of the transmission of the first RRC message and the first UE assistance information according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0097] In Example 1, the first node in the present application receives a first RRC message in step 101; in step 102, as a response to the first condition set being satisfied, sends first UE auxiliary information; wherein, the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein, the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0098] As an embodiment, in response to the first condition set being met, a UE assistance information (UE Assistance Information) process is initiated, and in the assistance information process, the first UE assistance information is sent.

[0099] As an embodiment, the first UE auxiliary information is transmitted via an uplink (Uplink, UL).

[0100] As an embodiment, the first UE auxiliary information is transmitted via a side link (Sidelink, SL).

[0101] As an embodiment, the first UE auxiliary information is an air interface message.

[0102] As an embodiment, the first UE auxiliary information is a UE specific message.

[0103] As an embodiment, the first UE auxiliary information is MAC (Medium Access Control) CE (Control Element).

[0104] As an embodiment, the above method is beneficial to shortening the delay compared with the RRC message.

[0105] As an embodiment, compared with RRC messages, the above method shortens the delay and saves PUCCH signaling overhead.

[0106] As an embodiment, the above method is conducive to dynamic configuration of full-duplex without sub-band overlap.

[0107] As an embodiment, the first UE auxiliary information is UCI (Uplink Control Information).

[0108] As an embodiment, the above method is beneficial to further shorten the delay compared with RRC messages and MAC CE.

[0109] As an embodiment, the above method is conducive to dynamic configuration of full-duplex without sub-band overlap.

[0110] As an embodiment, the first UE auxiliary information is an RRC (Radio Resource Control) message.

[0111] As an embodiment, the first UE auxiliary information includes at least one RRC field.

[0112] As an embodiment, the first UE auxiliary information is mapped to DCCH (Dedicated Control Channel).

[0113] As an embodiment, the first UE auxiliary information is mapped to SCCH (Sidelink Control Channel).

[0114] As an embodiment, the first UE auxiliary information is sent via SRB1 (Signalling Radio Bearer 1).

[0115] As an embodiment, the first UE auxiliary information is sent via SRB3 (Signalling Radio Bearer 3).

[0116] As an embodiment, the first UE auxiliary information indicates a capability configuration that the first node prefers.

[0117] As an embodiment, the first UE auxiliary information indicates a capability configuration that the first node prefers to be temporarily configured.

[0118] As an embodiment, the name of the first UE assistance information includes AssistanceInformation.

[0119] As an embodiment, the name of the first UE assistance information includes UEAssistanceInformation.

[0120] As an embodiment, the first UE assistance information includes a UEAssistanceInformation message.

[0121] As an embodiment, the first UE assistance information is a UEAssistanceInformation message.

[0122] As an embodiment, an RRC field in the first UE auxiliary information indicates the relevant information of the sub-band non-overlapping full-duplex.

[0123] As an embodiment, the first UE auxiliary information explicitly indicates at least one of the first frequency domain information or the first time domain information.

[0124] As an embodiment, the first UE auxiliary information implicitly indicates at least one of the first frequency domain information or the first time domain information.

[0125] As an embodiment, the first UE auxiliary information includes a first information block, and the first information block indicates at least one of the first frequency domain information or the first time domain information.

[0126] As an embodiment, the name of the first information block indicates that the sub-band is non-overlapping full-duplex.

[0127] As an embodiment, the name of the first information block includes sbfd.

[0128] As an embodiment, the name of the first information block includes sbfd-Preference.

[0129] As an embodiment, the name of the first information block includes sbfd-DeactivationPreference.

[0130] As an embodiment, the name of the first information block includes sbfd-ActivationPreference.

[0131] As an embodiment, the first UE assistance information includes an OverheatingAssistance IE, and the OverheatingAssistance IE indicates at least one of the first frequency domain information or the first time domain information.

[0132] As an embodiment, the at least one of the first frequency domain information or the first time domain information is the first frequency domain information.

[0133] As an embodiment, the at least one of the first frequency domain information or the first time domain information is the first time domain information.

[0134] As an embodiment, the at least one of the first frequency domain information or the first time domain information is the first frequency domain information and the first time domain information.

[0135] As an embodiment, the first UE auxiliary information includes at least one of the first frequency domain information or the first time domain information.

[0136] As an embodiment, the first UE auxiliary information explicitly indicates at least one of the first frequency domain information or the first time domain information.

[0137] As an embodiment, the first UE auxiliary information implicitly indicates at least one of the first frequency domain information or the first time domain information.

[0138] As an embodiment, the first UE auxiliary information requests deactivation of at least one of the first frequency domain information or the first time domain information.

[0139] As an embodiment, the first UE auxiliary information requests activation of at least one of the first frequency domain information or the first time domain information.

[0140] As an embodiment, the first UE auxiliary information indicates that the first node prefers to configure at least one of the first frequency domain information or the first time domain information.

[0141] As an embodiment, the first UE auxiliary information indicates that the first node prefers not to configure at least one of the first frequency domain information or the first time domain information.

[0142] As an embodiment, the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex, which means that the at least one of the first frequency domain information or the first time domain information is related to the sub-band non-overlapping full-duplex.

[0143] As an embodiment, the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex, which means that only when the first node is configured with the sub-band non-overlapping full-duplex, the first UE auxiliary information includes the at least one of the first frequency domain information or the first time domain information.

[0144] As an embodiment, the at least one of the first frequency domain information or the first time domain information relies on sub-band non-overlapping full-duplex, which means that the at least one of the first frequency domain information or the first time domain information is dedicated to the sub-band non-overlapping full-duplex.

[0145] As an embodiment, the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex, which means that the at least one of the first frequency domain information or the first time domain information overlaps with the time-frequency resources of the sub-band non-overlapping full-duplex.

[0146] As an embodiment, the at least one of the first frequency domain information or the first time domain information depends on the sub-band non-overlapping full-duplex, which means that the determination of the at least one of the first frequency domain information or the first time domain information depends on the sub-band non-overlapping full-duplex.

[0147] As an embodiment, the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex, which means that the value of at least one of the first frequency domain information or the first time domain information depends on the sub-band non-overlapping full-duplex.

[0148] As a sub-embodiment of the above embodiment, the value of the first frequency domain information does not include frequency domain information for non-overlapping full-duplex of the sub-bands.

[0149] As a sub-embodiment of the above embodiment, the value of the first time domain information does not include time domain information for non-overlapping full-duplex of the sub-bands.

[0150] As a sub-embodiment of the above embodiment, the value of the first frequency domain information only includes frequency domain information for non-overlapping full-duplex of the sub-bands.

[0151] As a sub-embodiment of the above embodiment, the value of the first time domain information only includes the time domain information for the non-overlapping full-duplex of the sub-bands.

[0152] As an embodiment, the first frequency domain information is configured with a bias of the first node.

[0153] As an embodiment, the first frequency domain information is temporarily configured with the bias of the first node.

[0154] As an embodiment, the first frequency domain information includes frequency resource configuration.

[0155] As an embodiment, the first frequency domain information includes a center frequency and a bandwidth.

[0156] As an embodiment, the first frequency domain information includes subcarrier spacing.

[0157] As an embodiment, the first frequency domain information includes bandwidth.

[0158] As an embodiment, the first frequency domain information is bandwidth.

[0159] As an embodiment, the first frequency domain information includes the number of carriers.

[0160] As an embodiment, the first frequency domain information is the number of carriers.

[0161] As an embodiment, the bandwidth is an aggregate bandwidth of an uplink (Uplink, UL).

[0162] As an embodiment, the bandwidth is an aggregate bandwidth of a downlink (Downlink, DL).

[0163] As an embodiment, the bandwidth is the maximum aggregate bandwidth of the uplink (UL).

[0164] As an embodiment, the bandwidth is the maximum aggregate bandwidth of the downlink (Downlink, DL).

[0165] As an embodiment, the bandwidth is the bandwidth occupied by the non-overlapping full-duplex sub-bands on one carrier.

[0166] As an embodiment, the carrier is an uplink carrier.

[0167] As an embodiment, the carrier is a downlink carrier.

[0168] As an embodiment, the carrier is a TDD (Time Division Duplex) carrier.

[0169] As an embodiment, the carrier is a carrier configured with non-overlapping sub-bands and full-duplex.

[0170] As an embodiment, the carrier is a TDD carrier configured with non-overlapping full-duplex subbands.

[0171] As an embodiment, the carrier refers to a component carrier (CC).

[0172] As an embodiment, the carrier refers to a secondary component carrier (Secondary Component Carrier).

[0173] As an embodiment, the carrier refers to carrier.

[0174] As an embodiment, the carrier refers to carrier.

[0175] As an embodiment, the carrier refers to a cell.

[0176] As an embodiment, the carrier refers to SCell (Secondary Cell).

[0177] As an embodiment, the carrier refers to a serving cell.

[0178] As an embodiment, the first time domain information is preferred by the first node.

[0179] As an embodiment, the first time domain information includes time domain resources.

[0180] As an embodiment, the first time domain information includes downlink time domain resources.

[0181] As an embodiment, the first time domain information includes uplink time domain resources.

[0182] As an embodiment, the first time domain information includes the time domain resources of the non-overlapping full-duplex sub-band.

[0183] As an embodiment, the first time domain information includes a first time interval.

[0184] As an embodiment, the first time interval is a time interval of non-overlapping full-duplex sub-bands preferred by the first node.

[0185] As an embodiment, the first time interval is a time interval of non-overlapping full-duplex sub-bands preferred by the first node.

[0186] As an embodiment, the first time domain information includes the time domain length of the first time interval.

[0187] As an embodiment, the time domain length of the first time interval is a positive integer number of TDD cycles.

[0188] As an embodiment, the time domain length of the first time interval is a positive integer number of time slots.

[0189] As an embodiment, the time domain length of the first time interval is a positive integer number of symbols.

[0190] As an embodiment, the first time domain information includes the position of the first time interval.

[0191] As an embodiment, the position of the first time interval includes a start time and an end time of the first time interval.

[0192] As an embodiment, the position of the first time interval includes a start symbol and an end symbol of the first time interval.

[0193] As an embodiment, the first time domain information is for all downlink carriers.

[0194] As an embodiment, the first time domain information is for only one downlink carrier.

[0195] As an embodiment, the first time domain information is for all uplink carriers.

[0196] As an embodiment, the first time domain information is for only one uplink carrier.

[0197] As an embodiment, the first time domain information is for only one BWP (Bandwidth part).

[0198] As an embodiment, the first time domain information is for only the active BWP.

[0199] As an embodiment, the first time domain information is for UL (Uplink) BWP only.

[0200] As an embodiment, the first time domain information is for DL ​​(Downlink) BWP only.

[0201] As an embodiment, the preference refers to: preferred.

[0202] As an embodiment, the biased refers to: expected.

[0203] As an embodiment, the preference refers to: recommended.

[0204] As an embodiment, the biased refers to: requested.

[0205] As an embodiment, the biased refers to: biased towards being configured.

[0206] As an embodiment, the bias refers to: biased towards being temporarily configured.

[0207] As an embodiment, the first frequency domain information includes the transmission direction of the sub-band non-overlapping full-duplex; the transmission direction refers to one of the uplink or the downlink.

[0208] As an embodiment, the first frequency domain information includes a first sub-band and a second sub-band for non-overlapping full-duplex of the sub-bands; the first sub-band and the second sub-band are for non-overlapping full-duplex of the sub-bands.

[0209] As an embodiment, the first frequency domain information includes the transmission direction of the first sub-frequency band and the second sub-frequency band; the transmission direction refers to one of the uplink or the downlink.

[0210] As an embodiment, the first frequency domain information includes BWP-Id for full-duplex without overlapping sub-bands.

[0211] As an embodiment, the first frequency domain information includes ServCellIndex for full-duplex without overlapping sub-bands.

[0212] As an embodiment, the sub-band non-overlapping full-duplex is SBFD.

[0213] As an embodiment, the sub-band non-overlapping full-duplex refers to full-duplex on non-overlapping uplink sub-band and downlink sub-band.

[0214] As an embodiment, the sub-band non-overlapping full-duplex refers to full-duplex on non-overlapping uplink sub-bands and downlink sub-bands corresponding to downlink symbols.

[0215] As an embodiment, symbols configured as the sub-band non-overlapping full-duplex can be used for uplink and downlink.

[0216] As an embodiment, the symbol configured as the sub-band non-overlapping full-duplex can be configured with UL PRB (Physical Resource Block) and DL PRB.

[0217] As an embodiment, the sub-bands do not overlap full-duplex occupied TDD downlink symbols.

[0218] As an embodiment, the sub-bands do not overlap full-duplex occupied TDD flexible symbols.

[0219] As an embodiment, the subbands do not overlap full-duplex occupied TDD downlink symbols or TDD flexible symbols.

[0220] As an embodiment, the sub-band non-overlapping full-duplex relies on RRC configuration.

[0221] As an embodiment, the sub-bands are non-overlapping full-duplex dependent on UE capability.

[0222] As an embodiment, the sub-bands are configured in non-overlapping full-duplex on the carrier.

[0223] As an embodiment, the sub-band non-overlapping full-duplex configuration is on a TDD carrier.

[0224] As an embodiment, the sub-bands are non-overlapping full-duplex configured on the BWP.

[0225] As an embodiment, the sub-bands are non-overlapping full-duplex configured on the serving cell.

[0226] As an embodiment, the sub-band non-overlapping full-duplex is configured on a carrier of a service cell.

[0227] As an embodiment, the sub-band non-overlapping full-duplex is configured on a BWP of a carrier of a service cell.

[0228] As an embodiment, the first UE assistance information requests cancellation of the sub-band non-overlapping full-duplex operation.

[0229] As an embodiment, the first UE assistance information indicates a time interval for requesting to cancel the operation for the sub-band non-overlapping full-duplex.

[0230] As an embodiment, the first UE assistance information indicates a carrier requesting cancellation of the sub-band non-overlapping full-duplex operation.

[0231] As an embodiment, the first UE assistance information indicates a request to cancel the BWP for the sub-band non-overlapping full-duplex operation.

[0232] As an embodiment, the cancelling refers to: stopping.

[0233] As an embodiment, the cancelling refers to: pausing.

[0234] As an embodiment, the cancelling refers to: clearing.

[0235] As an embodiment, the cancellation means: not executing.

[0236] As an embodiment, the first UE auxiliary information requests to start the non-overlapping full-duplex operation for the sub-band.

[0237] As an embodiment, the first UE auxiliary information indicates a time interval for requesting to start the operation for the non-overlapping full-duplex sub-band.

[0238] As an embodiment, the first UE assistance information indicates a request to enable a carrier for the sub-band non-overlapping full-duplex operation.

[0239] As an embodiment, the first UE assistance information indicates a request to start a BWP for the sub-band non-overlapping full-duplex operation.

[0240] As an embodiment, the starting refers to: starting.

[0241] As an embodiment, the enabling refers to: restoring.

[0242] As an embodiment, the enabling refers to: configuring.

[0243] As an embodiment, the enabling refers to: executing.

[0244] As an embodiment, the enabling refers to: executing.

[0245] As an embodiment, the first RRC message is an RRCReconfiguration message.

[0246] As an embodiment, the first RRC message is an RRCResume message.

[0247] As an embodiment, the first RRC message is an RRCSetup message.

[0248] As an embodiment, the first RRC message includes a first RRC information block, and the first RRC information block enables the first UE auxiliary information.

[0249] As an embodiment, the first RRC information block is an otherConfig domain.

[0250] As an embodiment, the first RRC information block is an otherConfig domain, the otherConfig domain includes a domain whose name includes AssistanceConfig, and the domain whose name includes AssistanceConfig is set to setup.

[0251] As an embodiment, the domain whose name includes AssistanceConfig is an overheatingAssistanceConfig domain.

[0252] As an embodiment, the domain whose name includes AssistanceConfig is a sbfd-AssistanceConfig domain.

[0253] As an embodiment, the first RRC information block is an otherConfig domain, the otherConfig domain includes a domain whose name includes PreferenceConfig, and the domain whose name includes PreferenceConfig is set to setup.

[0254] As an embodiment, the domain whose name includes PreferenceConfig is an sbfd-PreferenceConfig domain.

[0255] As an embodiment, the first RRC message enabling the first UE auxiliary information includes: the first RRC message allows the first node to send the first UE auxiliary information.

[0256] As an embodiment, the first RRC message enabling the first UE auxiliary information includes: the first RRC message configuring the first node to support the first UE auxiliary information.

[0257] As an embodiment, the first RRC message enabling the first UE auxiliary information includes: the first node can send the first UE auxiliary information only under the condition that the first RRC message is received.

[0258] As an embodiment, the first RRC message enabling the first UE auxiliary information includes: under the assumption that the first RRC message is not received, the first node cannot send the first UE auxiliary information.

[0259] As an embodiment, the first RRC message is received after the first UE capability information is sent.

[0260] As an embodiment, the first RRC message is received before the first UE capability information is sent.

[0261] As an embodiment, the first condition set includes at least that the first RRC message enables the first UE assistance information and the first node supports the subband non-overlapping full-duplex.

[0262] Example 2

[0263] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2The network architecture 200 is described. The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or the network architecture 200 is a 5G+ network architecture, or the network architecture 200 is a 6G network architecture, or the network architecture 200 is a network architecture that 3GPP will continue to evolve in the future; the network architecture 200 may be called 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 may be called 6GS (6G System); the network architecture 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, core network 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220 and Internet service 230. The network architecture 200 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet switching services, but it will be readily understood by those skilled in the art that the various concepts presented throughout this application can be extended to networks or other cellular networks that provide circuit switching services. The RAN includes a node 203 and other nodes 204. The node 203 provides user and control plane protocol terminations toward the UE 201. The node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 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 (transmitting and receiving node) or some other suitable term. The core network 210 is a 5GC (5G Core Network, 5G core network) / EPC (Evolved Packet Core), or, the core network 210 is a 6GC; the node 203 provides an access point to the core network 210 for the UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, 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 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 UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. Node 203 is connected to the core network 210 via an S1 / NG interface. The core network 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is a control node that processes signaling between UE201 and the core network 210. In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which is itself connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet Service 230. Internet Service 230 includes operator-corresponding Internet Protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0264] As an embodiment, the UE 201 is a user equipment (User Equipment, UE).

[0265] As an embodiment, the UE201 is a base station device (BaseStation, BS).

[0266] As an embodiment, the UE 201 is a relay device.

[0267] As an embodiment, the UE201 is a gateway device.

[0268] As an embodiment, the node 203 corresponds to the second node in the present application.

[0269] As an embodiment, the node 203 is a base station device.

[0270] As an embodiment, the node 203 is a user equipment.

[0271] As an embodiment, the node 203 is a relay device.

[0272] As an embodiment, the node 203 is a gateway device.

[0273] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0274] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0275] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0276] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0277] As an embodiment, the user equipment supports transmission of a terrestrial network (Terrestrial Network).

[0278] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0279] As an embodiment, the user equipment supports full-duplex with non-overlapping sub-bands.

[0280] As an embodiment, the user equipment supports 3GPP Release19.

[0281] As an embodiment, the user equipment supports 3GPP Release 19 and protocol versions after 3GPP Release 19.

[0282] As an embodiment, the user equipment includes an aircraft.

[0283] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0284] As an embodiment, the user equipment includes a vessel.

[0285] As an embodiment, the user equipment includes an Internet of Things terminal.

[0286] As an embodiment, the user equipment includes a terminal of the industrial Internet of Things.

[0287] As an embodiment, the user equipment includes a device supporting low-latency and high-reliability transmission.

[0288] As an embodiment, the user equipment includes a test device.

[0289] As an embodiment, the user equipment includes a signaling tester.

[0290] As an embodiment, the user equipment includes IAB (Integrated Access and Backhaul)-MT (Mobile Termination).

[0291] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0292] As an embodiment, the base station device supports transmission of a terrestrial network.

[0293] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0294] As an embodiment, the base station device includes a Node B (NodeB, NB).

[0295] As an embodiment, the base station device includes a gNB.

[0296] As an embodiment, the base station device includes an eNB.

[0297] As an embodiment, the base station device includes ng-eNB.

[0298] As an embodiment, the base station device includes en-gNB.

[0299] As an embodiment, the base station device includes a CU (Centralized Unit).

[0300] As an embodiment, the base station device includes a DU (Distributed Unit).

[0301] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0302] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0303] As an embodiment, the base station device includes a micro cell base station.

[0304] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0305] As an embodiment, the base station device includes a home base station (Femtocell).

[0306] As an embodiment, the base station device includes a flying platform device.

[0307] As an embodiment, the base station device includes a satellite device.

[0308] As an embodiment, the base station device includes a testing device.

[0309] As an embodiment, the base station equipment includes a signaling tester.

[0310] As an embodiment, the base station device includes a gateway device.

[0311] As an embodiment, the base station device includes an IAB-node.

[0312] As an embodiment, the base station device includes an IAB-donor.

[0313] As an embodiment, the base station device includes an IAB-donor-CU.

[0314] As an embodiment, the base station device includes an IAB-donor-DU.

[0315] As an embodiment, the base station device includes an IAB-DU.

[0316] As an embodiment, the base station device includes IAB-MT.

[0317] As an embodiment, the relay device includes a relay.

[0318] As an embodiment, the relay device includes an L3 relay.

[0319] As an embodiment, the relay device includes an L2 relay.

[0320] As an embodiment, the relay device includes a router.

[0321] As an embodiment, the relay device includes a switch.

[0322] As an embodiment, the relay device includes a gateway device.

[0323] As an embodiment, the relay device includes user equipment.

[0324] As an embodiment, the relay device includes a base station device.

[0325] Example 3

[0326] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for the control plane 300 is shown in 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 as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. 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 inter-zone mobility support. 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 (Hybrid Automatic Repeat Request). 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. 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 using RRC signaling to configure the lower layers. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). In the user plane 350, the radio protocol architecture 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, but 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 a 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.

[0327] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0328] As an example, Figure 3The wireless protocol architecture in is applicable to the second node in this application.

[0329] As an embodiment, the first RRC message in the present application is generated in the RRC306.

[0330] As an embodiment, the first UE capability information in the present application is generated in the RRC306.

[0331] As an embodiment, the first UE auxiliary information in the present application is generated in the RRC306.

[0332] As an embodiment, the first UE auxiliary information in the present application is generated in the MAC302 or MAC352.

[0333] As an embodiment, the first UE auxiliary information in the present application is generated in the PHY301 or PHY351.

[0334] Example 4

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

[0336] The first 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.

[0337] The second communication 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 .

[0338] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In transmission from the second 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 radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first 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 410, 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), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing 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 domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier 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.

[0339] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through 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 and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication 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 codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the 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 L3 for L3 processing.

[0340] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used 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 function at the second communication device 410 described in the transmission from the second communication device 410 to the first 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0341] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0342] As an embodiment, the first 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, and the first communication device 450 at least: receives a first RRC message; sends first UE auxiliary information as a response to a first set of conditions being met; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first set of conditions includes at least the first RRC message enabling the first UE auxiliary information.

[0343] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first RRC message; sending first UE auxiliary information as a response to a first set of conditions being satisfied; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first set of conditions includes at least the first RRC message enabling the first UE auxiliary information.

[0344] As an embodiment, the second 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 second communication device 410 at least: sends a first RRC message; receives first UE auxiliary information; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein, as a response to the first condition set being met, the receiver of the first RRC message sends the first UE auxiliary information; the at least one of the first frequency domain information or the first time domain information depends on subband non-overlapping full-duplex; the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0345] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first RRC message; receiving first UE auxiliary information; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein, as a response to a first set of conditions being met, the recipient of the first RRC message sends the first UE auxiliary information; the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first set of conditions includes at least the first RRC message enabling the first UE auxiliary information.

[0346] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first RRC message.

[0347] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first RRC message.

[0348] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send first UE capability information.

[0349] As an embodiment, at least one of the antenna 420, the receiver 418, the receiving processor 470, and the controller / processor 475 is used to receive first UE capability information.

[0350] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send first UE assistance information.

[0351] As an embodiment, at least one of the antenna 420, the receiver 418, the receiving processor 470, and the controller / processor 475 is used to receive first UE assistance information.

[0352] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0353] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0354] As an embodiment, the first communication device 450 is a user equipment.

[0355] As an embodiment, the first communication device 450 is a base station device.

[0356] As an embodiment, the first communication device 450 is a relay device.

[0357] As an embodiment, the second communication device 410 is a user equipment.

[0358] As an embodiment, the second communication device 410 is a base station device.

[0359] As an embodiment, the second communication device 410 is a relay device.

[0360] Example 5

[0361] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0362] for First node U01 In step S5101, first UE capability information is sent; wherein the first UE capability information indicates that the first node supports sub-band non-overlapping full-duplex; in step S5102, a first RRC message is received; in step S5103, a second RRC message is received, and the second RRC message configures the first symbol as a downlink symbol; in step S5104, as a response to the first condition set being met, first UE auxiliary information is sent; wherein the first UE auxiliary information indicates at least one of the first frequency domain information or the first time domain information; in step S5105, a first timer is started along with the sending of the first UE auxiliary information; wherein the first condition set includes that the first timer is not running; in step S5106, uplink transmission is performed on the first symbol; wherein the uplink transmission performed on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

[0363] for Second node N02 In step S5201, the first UE capability information is received; in step S5202, the first RRC message is sent; in step S5203, the second RRC message is sent; in step S5204, the first UE auxiliary information is received; in step S5205, uplink reception is performed on the first symbol.

[0364] In Embodiment 5, at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0365] As an embodiment, the first node U01 and the second node N02 are connected wirelessly.

[0366] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0367] As an embodiment, the first node U01 and the second node N02 are connected via an IAB port.

[0368] As an embodiment, the first node U01 and the second node N02 are connected via a PC5 interface.

[0369] As an embodiment, the dashed box F5.1 is optional.

[0370] As an embodiment, the dotted box F5.1 does not exist.

[0371] As an embodiment, the dashed box F5.1 exists.

[0372] As an embodiment, the first UE capability information is a UECapabilityInformation message.

[0373] As an embodiment, the first UE capability information indicates UE capabilities supported by the first node.

[0374] As an embodiment, the first UE capability information indicates the UE wireless access capability of the first node.

[0375] As an embodiment, the first UE capability information is scheduled by the network.

[0376] As an embodiment, the first UE capability information is triggered by the first node.

[0377] As an embodiment, the first UE capability information is triggered by a UECapabilityEnquiry message.

[0378] As an embodiment, optionally, before the first UE capability information is received, a UECapabilityEnquiry message is received, and the UECapabilityEnquiry message triggers the first UE capability information.

[0379] As an embodiment, the first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex for FR1.

[0380] As an embodiment, the first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex for FR2.

[0381] As an embodiment, the first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex for 3GPP Release 19.

[0382] As an embodiment, the first UE capability information indicates that the first node supports reporting of auxiliary information for non-overlapping full-duplex of the subband.

[0383] As an embodiment, a field in the first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex, and the field is set to supported.

[0384] As a sub-embodiment of the above embodiment, the one domain is dedicated to full-duplex without overlapping sub-bands.

[0385] As a sub-embodiment of the above embodiment, the name of the domain includes sbfd.

[0386] As a sub-embodiment of the above embodiment, the name of the domain includes sbfd-r19.

[0387] As a sub-embodiment of the above embodiment, the domain belongs to a UE-NR-Capability in the first UE capability information.

[0388] As a sub-embodiment of the above embodiment, the one domain belongs to a domain in the first UE capability information whose name includes UE-NR-Capability.

[0389] As a sub-embodiment of the above embodiment, the one domain belongs to a UE-NR-Capability-v1900 domain in the first UE capability information.

[0390] As a sub-embodiment of the above embodiment, the one domain belongs to a UE-NR-Capability-v1910 domain in the first UE capability information.

[0391] As an embodiment, the first UE capability information indicates that the first node supports overheat assistance information.

[0392] As an embodiment, the first UE capability information includes an overheatingInd, and the overheatingInd is set to supported.

[0393] As an embodiment, the dashed box F5.2 is optional.

[0394] As an embodiment, the dotted box F5.2 does not exist.

[0395] As a sub-embodiment of the above embodiment, the second RRC message is not received.

[0396] As a sub-embodiment of the above embodiment, the second RRC message is not sent by the second node.

[0397] As an embodiment, the dashed box F5.2 exists.

[0398] As a sub-embodiment of the above embodiment, in response to the second RRC message being received, the sub-band non-overlapping full-duplex is configured to take effect.

[0399] As a sub-embodiment of the above embodiment, in response to receiving a MAC CE after the second RRC message is received, the sub-band non-overlapping full-duplex is configured to take effect.

[0400] As a sub-embodiment of the above embodiment, in response to receiving a DCI after the second RRC message is received, the sub-band non-overlapping full-duplex is configured to take effect.

[0401] As a sub-embodiment of the above embodiment, the second RRC message precedes the first UE auxiliary information.

[0402] As a sub-embodiment of the above embodiment, before the UE auxiliary information, the sub-band non-overlapping full-duplex is configured.

[0403] As a sub-embodiment of the above embodiment, the second RRC message follows the first UE auxiliary information.

[0404] As a sub-embodiment of the above embodiment, the second RRC message depends on the first UE auxiliary information.

[0405] As a sub-embodiment of the above embodiment, the first UE auxiliary information triggers the second RRC message.

[0406] As a sub-embodiment of the above embodiment, before the UE auxiliary information, the sub-band non-overlapping full-duplex is configured.

[0407] As a sub-embodiment of the above embodiment, before the UE auxiliary information, the sub-band non-overlapping full-duplex is not configured.

[0408] As an embodiment, the second RRC message is cell common.

[0409] As an embodiment, the second RRC message is UE-specific (UE-specific).

[0410] As an embodiment, the second RRC message is for a serving cell.

[0411] As an embodiment, the second RRC message is for multiple service cells.

[0412] As an embodiment, the second RRC message is for a TDD service cell.

[0413] As an embodiment, the second RRC message is for a TDD carrier.

[0414] As an embodiment, the second RRC message is for a TDD uplink carrier.

[0415] As an embodiment, the second RRC message is for a TDD downlink carrier.

[0416] As an embodiment, the second RRC message is for a TDD uplink carrier and a TDD downlink carrier.

[0417] As an embodiment, the second RRC message configures TDD.

[0418] As an embodiment, the second RRC message configures the TDD time slot configuration.

[0419] As an embodiment, the second RRC message configures TDD symbol configuration.

[0420] As an embodiment, the second RRC message configures a TDD pattern.

[0421] As an embodiment, the second RRC message configures the downlink symbols of TDD.

[0422] As an embodiment, the second RRC message is an RRCReconfiguration message.

[0423] As an embodiment, the second RRC message is a TDD-UL-DL-ConfigCommon IE.

[0424] As an embodiment, the second RRC message is a TDD-UL-DL-ConfigDedicated IE.

[0425] As an embodiment, the second RRC message indicates that the first symbol is a downlink symbol.

[0426] As an embodiment, the first symbol is determined as a downlink symbol according to the second RRC message.

[0427] As an embodiment, the dashed box F5.3 is optional.

[0428] As an embodiment, the dotted box F5.3 does not exist.

[0429] As an embodiment, the dashed box F5.3 exists.

[0430] As an embodiment, when the dotted box F5.3 exists, the dotted box F5.2 exists.

[0431] As an embodiment, the time-frequency resources occupied by the uplink transmission are configured uplink grants (configured uplink grant).

[0432] As an embodiment, the type of time-frequency resources occupied by the uplink transmission is configured grantType 1.

[0433] As an embodiment, the type of time-frequency resources occupied by the uplink transmission is configured grantType 2.

[0434] As an embodiment, the time-frequency resources occupied by the uplink transmission are dynamically scheduled.

[0435] As an embodiment, the time-frequency resources occupied by the uplink transmission are scheduled by DCI, and the DCI is DCIFormat 1_0.

[0436] As an embodiment, the time-frequency resources occupied by the uplink transmission are scheduled by DCI, and the format of the DCI is used for the sub-band non-overlapping full-duplex.

[0437] As an embodiment, the time-frequency resources occupied by the uplink transmission are scheduled by DCI, and at least one field of the DCI is only used for the sub-band non-overlapping full-duplex.

[0438] As an embodiment, the performing uplink transmission refers to: sending PUSCH (Physical Uplink Shared Channel).

[0439] As an embodiment, the performing uplink transmission refers to: sending PUCCH (Physical Uplink Control Channel).

[0440] As an embodiment, the performing uplink transmission refers to: sending a PRACH (Physical Random Access Channel).

[0441] As an embodiment, the performing uplink transmission refers to: sending SRS (Semi-Persistent Scheduling).

[0442] As an embodiment, the uplink transmission does not support SRS.

[0443] As an embodiment, the performing uplink transmission refers to: sending any one of PUSCH or PUCCH or PRACH or SRS.

[0444] As an embodiment, the performing uplink transmission refers to: sending any one of PUSCH, PUCCH or PRACH.

[0445] As an embodiment, the uplink transmission is performed on the first symbol under the condition that the first symbol is configured for the sub-band non-overlapping full-duplex.

[0446] As an embodiment, when the first symbol is configured for the sub-band non-overlapping full-duplex, the uplink transmission is performed on the first symbol.

[0447] As an embodiment, the downlink transmission is performed on the first symbol under the condition that the first symbol is not configured for the sub-band non-overlapping full-duplex.

[0448] As an embodiment, under the condition that the first symbol is not configured for the sub-band non-overlapping full-duplex, the uplink transmission is not allowed to be performed on the first symbol.

[0449] As an embodiment, the uplink transmission is performed on a service cell of the first node; the service cell is configured with the sub-band non-overlapping full-duplex.

[0450] As an embodiment, the uplink transmission is on a carrier of the first node; the one carrier is configured with the sub-band non-overlapping full-duplex.

[0451] As an embodiment, the uplink transmission occupies only the first symbol in the time domain.

[0452] As an embodiment, the uplink transmission occupies multiple symbols in the time domain; the first symbol is one of the multiple symbols.

[0453] As an embodiment, the uplink transmission occupies at least one UL usable PRB; the at least one UL usable PRB overlaps with the first symbol in the time domain.

[0454] As an embodiment, the at least one UL usable PRB is configured by RRC.

[0455] As an embodiment, the at least one UL usable PRB is determined by the first node according to the RRC configuration.

[0456] As an embodiment, step S5105 is optional.

[0457] As an embodiment, step S5105 does not exist.

[0458] As an embodiment, along with the sending of the first UE assistance information, any timer with a name including T346 is not started.

[0459] As an embodiment, along with the sending of the first UE auxiliary information, T345 is not activated.

[0460] As an embodiment, step S5105 exists.

[0461] As an embodiment, the first timer is in the RRC sublayer.

[0462] As an embodiment, the first timer is T345.

[0463] As an embodiment, the first timer is T346b.

[0464] As an embodiment, the first timer is T346c.

[0465] As an embodiment, the name of the first timer includes T346.

[0466] As an embodiment, the value of the first timer is configured by an RRC domain.

[0467] As an embodiment, the name of the RRC domain includes overheatingIndicationProhibitTimer.

[0468] As an embodiment, the one RRC domain is overheatingIndicationProhibitTimer, and the first timer is T345.

[0469] As an embodiment, the one RRC domain is maxBW-PreferenceProhibitTimer, and the first timer is T346b.

[0470] As an embodiment, the one RRC domain is maxCC-PreferenceProhibitTimer, and the first timer is T346c.

[0471] As an embodiment, the name of the RRC domain includes sbfd.

[0472] As an embodiment, accompanying the sending of the first UE auxiliary information means: when the sending of the first UE auxiliary information is sent.

[0473] As an embodiment, accompanying the sending of the first UE auxiliary information means: before the sending of the first UE auxiliary information is delivered to a lower layer.

[0474] As an embodiment, accompanying the sending of the first UE auxiliary information means: when the sending of the first UE auxiliary information is set to be completed.

[0475] As an embodiment, accompanying the sending of the first UE auxiliary information means: after the first condition set is satisfied, and before initiating the sending of the first UE auxiliary information.

[0476] Example 6

[0477] Example 6 illustrates a schematic diagram in which the first condition set according to an embodiment of the present application includes detecting internal overheating. Figure 6 shown.

[0478] for First node U01 , in step S6101, internal overheating is detected; in step S6102, the first condition set is met.

[0479] In Example 6, the first condition set includes detection of internal overheating.

[0480] As an embodiment, a first receiver receives a first RRC message; a first transmitter sends first UE auxiliary information in response to at least detecting internal overheating and the first RRC message enabling the first UE auxiliary information; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex.

[0481] As an embodiment, the first set of conditions includes detecting internal overheating and the first RRC message enabling the first UE assistance information.

[0482] As an embodiment, the first condition set is that internal overheating is detected and the first RRC message enables the first UE assistance information.

[0483] As an embodiment, the first condition set is at least that internal overheating is detected and the first RRC message enables the first UE assistance information.

[0484] As an embodiment, the first node has the ability to provide overheat assistance information in RRC_CONNECTED.

[0485] As an embodiment, the first node is configured to report overheating auxiliary information.

[0486] As an embodiment, the first RRC message includes an otherConfig, the otherConfig includes an overheatingAssistanceConfig, and the overheatingAssistanceConfig is set to setup.

[0487] As an embodiment, the detection of internal overheating triggers the sending of the first UE auxiliary information.

[0488] As an embodiment, the detecting of internal overheating refers to: experiencing internal overheating.

[0489] As an embodiment, the detecting of internal overheating means that an overheating condition has been detected.

[0490] As an embodiment, the first node determines that internal overheating is detected based on UE implementation.

[0491] As an embodiment, the first node determines that internal overheating is detected when receiving an indication from a higher layer.

[0492] As an embodiment, the first node determines that internal overheating is detected when receiving an indication from a lower layer.

[0493] As an embodiment, when the internal overheating reaches the overheating threshold, it is determined that the internal overheating is detected; and the first RRC message includes an overheating threshold.

[0494] As an embodiment, when the temperature reaches the overheating threshold, it is determined that internal overheating is detected; the first RRC message includes an overheating threshold.

[0495] As an embodiment, the first UE auxiliary information is sent in response to the detection of internal overheating.

[0496] As an example, the phrase in response to detecting internal overheating means: when internal overheating is detected.

[0497] As an example, the phrase in response to detecting internal overheating means: upon detecting internal overheating.

[0498] As an example, the phrase in response to detecting internal overheating refers to: accompanying the detection of internal overheating.

[0499] As an example, the phrase in response to detecting internal overheating refers to: when an overheating condition is met.

[0500] As an example, the phrase in response to detecting internal overheating means: after at least detecting internal overheating.

[0501] As an example, the phrase in response to detecting internal overheating refers to if the overheating condition has been detected.

[0502] As an embodiment, when the internal overheating is detected, the first timer is not running.

[0503] As an embodiment, the first timer is not configured.

[0504] As an embodiment, the first timer is not running.

[0505] As an embodiment, the first timer is a T345.

[0506] As an embodiment, the maximum running time of the first timer is configured by an overheatingIndicationProhibitTimer field.

[0507] As an embodiment, the first node tends to reduce the operation for the sub-band non-overlapping full-duplex.

[0508] As an embodiment, the first node tends to reduce the configuration for the sub-band non-overlapping full-duplex.

[0509] As an embodiment, the first UE auxiliary information is an RRC message.

[0510] As an embodiment, the first UE assistance information is a UEAssistanceInformation message.

[0511] As an embodiment, the first UE assistance information includes an OverheatingAssistance IE, and the OverheatingAssistance IE indicates the first frequency domain information.

[0512] As an embodiment, the name of the OverheatingAssistance IE includes OverheatingAssistance.

[0513] As an embodiment, the first frequency domain information is a maximum aggregated bandwidth; the maximum aggregated bandwidth depends on the non-overlapping full-duplex of the sub-bands.

[0514] As a sub-embodiment of the above embodiment, the first node tends to temporarily reduce the maximum aggregate bandwidth.

[0515] As a sub-embodiment of the above embodiment, the first frequency domain information is for full-duplex without overlapping of the sub-bands.

[0516] As a subsidiary embodiment of the above sub-embodiment, the first frequency domain information is the maximum aggregate bandwidth that the first node prefers to be temporarily configured for full-duplex without overlapping the sub-bands.

[0517] As a subsidiary embodiment of the above sub-embodiment, a field in the OverheatingAssistance IE whose name includes reducedBW indicates the first frequency domain information; the first frequency domain information is the maximum aggregate bandwidth that the first node prefers to be temporarily configured for full-duplex without overlapping the sub-bands.

[0518] As a sub-embodiment of the above embodiment, the first frequency domain information is not for non-overlapping full-duplex of the sub-bands.

[0519] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregation bandwidth of the downlink.

[0520] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers that the first node prefers to be temporarily configured with.

[0521] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers temporarily configured by the first node for full-duplex without overlapping sub-bands.

[0522] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers temporarily configured by the first node without the sub-band non-overlapping full-duplex.

[0523] As a subsidiary embodiment of the above sub-embodiment, if a DL BWP is for non-overlapping full-duplex of the sub-band, the reducedBW-DL does not include the bandwidth of the one DL BWP; the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0524] As a subsidiary embodiment of the above sub-embodiment, the reducedBW-DL includes the bandwidth of one DL BWP only when the one DL BWP is for non-overlapping full-duplex of the sub-band; the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers temporarily configured by the first node for non-overlapping full-duplex of the sub-band.

[0525] As a sub-embodiment of the above embodiment, the reducedBW-DL in the OverheatingAssistance IE indicates the first frequency domain information; the first frequency domain information is the maximum aggregate bandwidth of all downlink carriers that the first node prefers to be temporarily configured.

[0526] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregation bandwidth of the uplink.

[0527] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers that the first node prefers to be temporarily configured with.

[0528] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers temporarily configured by the first node for full-duplex without overlapping sub-bands.

[0529] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers temporarily configured by the first node without the sub-band non-overlapping full-duplex.

[0530] As a subsidiary embodiment of the above sub-embodiment, if a DL BWP is for non-overlapping full-duplex of the sub-band, the reducedBW-UL does not include the bandwidth of the UL BWP; the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0531] As a subsidiary embodiment of the above sub-embodiment, the reducedBW-UL includes the bandwidth of the one UL BWP only when one DL BWP is for non-overlapping full-duplex of the sub-band; the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers temporarily configured by the first node for non-overlapping full-duplex of the sub-band.

[0532] As a sub-embodiment of the above embodiment, the reducedBW-UL in the OverheatingAssistance IE indicates the first frequency domain information; the first frequency domain information is the maximum aggregate bandwidth of all uplink carriers that the first node prefers to be temporarily configured.

[0533] As an embodiment, the first frequency domain information is the maximum number of carriers; the maximum number of carriers depends on the non-overlapping full-duplex of the sub-bands.

[0534] As an embodiment, the maximum number of carriers refers to the maximum number of secondary component carriers.

[0535] As an embodiment, the maximum number of carriers includes the maximum number of secondary cells.

[0536] As an embodiment, the maximum number of carriers includes the maximum number of component carriers.

[0537] As an embodiment, the maximum number of carriers includes the maximum number of service cells.

[0538] As a sub-embodiment of the above embodiment, the first node tends to temporarily reduce the maximum number of carriers.

[0539] As a sub-embodiment of the above embodiment, the first frequency domain information is for full-duplex without overlapping of the sub-bands.

[0540] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers that the first node prefers to be temporarily configured for the purpose of non-overlapping full-duplex of the sub-bands.

[0541] As a sub-embodiment of the above embodiment, a field in the name of the OverheatingAssistance IE including reducedCC indicates the first frequency domain information; the first frequency domain information is the maximum number of carriers that the first node prefers to be temporarily configured for the non-overlapping full-duplex of the sub-band.

[0542] As a sub-embodiment of the above embodiment, the first frequency domain information is not for non-overlapping full-duplex of the sub-bands.

[0543] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers in the downlink.

[0544] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the downlink that the first node prefers to be temporarily configured.

[0545] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the downlink that the first node prefers to be temporarily configured for the purpose of non-overlapping full-duplex of the sub-bands.

[0546] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the downlink that the first node prefers to be temporarily configured without the sub-band non-overlapping full-duplex.

[0547] As a subsidiary embodiment of the above sub-embodiment, if a downlink carrier is for non-overlapping full-duplex of the sub-band, the reducedCCsDL does not include the downlink carrier; the first frequency domain information is the maximum number of carriers of the downlink that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0548] As a subsidiary embodiment of the above sub-embodiment, the reducedCCsDL includes a downlink carrier only when the carrier of the downlink is for non-overlapping full-duplex of the sub-band; the first frequency domain information is the maximum number of carriers of the downlink that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0549] As a sub-embodiment of the above embodiment, the reducedCCsDL in the OverheatingAssistance IE indicates the first frequency domain information; the first frequency domain information is the maximum number of downlink carriers that the first node prefers to be temporarily configured with.

[0550] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the uplink.

[0551] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of uplink carriers that the first node prefers to be temporarily configured with.

[0552] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the uplink that the first node prefers to be temporarily configured for full-duplex without overlapping the sub-bands.

[0553] As a sub-embodiment of the above embodiment, the first frequency domain information is the maximum number of carriers of the uplink that the first node prefers to be temporarily configured without the sub-band non-overlapping full-duplex.

[0554] As a subsidiary embodiment of the above sub-embodiment, if an uplink carrier is for non-overlapping full-duplex of the sub-band, the reducedCCsUL does not include the one uplink carrier; the first frequency domain information is the maximum number of carriers of the uplink that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0555] As a subsidiary embodiment of the above sub-embodiment, the reducedCCsUL includes the one uplink carrier only when the one uplink carrier is for non-overlapping full-duplex of the sub-band; the first frequency domain information is the maximum number of carriers of the uplink that the first node prefers to be temporarily configured for non-overlapping full-duplex of the sub-band.

[0556] As a sub-embodiment of the above embodiment, the reducedCCsUL in the OverheatingAssistance IE indicates the first frequency domain information; the first frequency domain information is the maximum number of uplink carriers that the first node prefers to be temporarily configured.

[0557] Example 7

[0558] Embodiment 7 illustrates a schematic diagram of a first condition set including a first measurement result reaching a first threshold according to an embodiment of the present application. Figure 7 shown.

[0559] for First node U01 In step S7101, the first measurement result reaches a first threshold; in step S7102, the first condition set is satisfied.

[0560] In Embodiment 7, the first condition set includes: a first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

[0561] As an embodiment, a first receiver receives a first RRC message; a first transmitter sends first UE auxiliary information in response to at least a first measurement result reaching a first threshold and the first RRC message enabling the first UE auxiliary information; wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information; wherein the at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first measurement result is for an uplink; and the first threshold is configurable.

[0562] As an embodiment, the first UE auxiliary information includes the first information block, and the first information block indicates at least one of the first frequency domain information or the first time domain information.

[0563] As an embodiment, the first UE assistance information requests cancellation of the sub-band non-overlapping full-duplex operation.

[0564] As an embodiment, the first UE auxiliary information requests to start the non-overlapping full-duplex operation for the sub-band.

[0565] As an embodiment, the first condition set includes that the first measurement result reaches a first threshold and the first RRC message enables the first UE auxiliary information.

[0566] As an embodiment, the first condition set is that the first measurement result reaches a first threshold and the first RRC message enables the first UE auxiliary information.

[0567] As an embodiment, the first condition set is that at least the first measurement result reaches a first threshold and the first RRC message enables the first UE assistance information.

[0568] As an embodiment, the first measurement result is the amount of uplink data.

[0569] As a sub-embodiment of the above embodiment, the uplink data volume includes an expected uplink data volume.

[0570] As a sub-embodiment of the above embodiment, the uplink data volume includes a pending uplink data volume.

[0571] As a sub-embodiment of the above embodiment, the data volume of the uplink includes the data volume of PDCP PDU (Protocol Data Unit) and RLC PDU.

[0572] As a sub-embodiment of the above embodiment, the data volume of the uplink includes the data volume of PDCP PDU and RLC PDU.

[0573] As a sub-embodiment of the above embodiment, the first threshold is at least 1 byte.

[0574] As a sub-embodiment of the above embodiment, the first threshold is at least 1 bit.

[0575] As an embodiment, the first measurement result is the transmission delay of the uplink.

[0576] As a sub-embodiment of the above embodiment, the uplink transmission delay is the transmission delay of the uplink data packet.

[0577] As a sub-embodiment of the above embodiment, the uplink transmission delay is the transmission delay of the uplink PDU.

[0578] As a sub-embodiment of the above embodiment, the uplink transmission delay is the transmission delay of the uplink PDCP PDU.

[0579] As a sub-embodiment of the above embodiment, the uplink transmission delay is the transmission delay of the uplink RLC PDU.

[0580] As a sub-embodiment of the above embodiment, the uplink transmission delay is the air interface delay of the uplink.

[0581] As a sub-embodiment of the above embodiment, the first threshold is at least 1 millisecond.

[0582] As a sub-embodiment of the above embodiment, the first threshold is at least 1 symbol.

[0583] As a sub-embodiment of the above embodiment, the first threshold is at least 1 time slot.

[0584] As an embodiment, the first measurement result is the coverage quality of the uplink.

[0585] As a sub-embodiment of the above embodiment, the first measurement result is determined by prediction.

[0586] As a sub-embodiment of the above embodiment, the first measurement result is determined by prediction based on AI / ML.

[0587] As a sub-embodiment of the above embodiment, the first measurement result is determined by wireless signal measurement.

[0588] As a sub-embodiment of the above embodiment, the first measurement result is determined by data packet statistics.

[0589] As a sub-embodiment of the above embodiment, the first measurement result is determined by measuring a downlink.

[0590] As a sub-embodiment of the above embodiment, the first measurement result is determined by measuring the uplink.

[0591] As a sub-embodiment of the above embodiment, the coverage quality of the uplink is CLI (Cross Link Interface).

[0592] As a sub-embodiment of the above embodiment, the uplink coverage quality is the uplink packet loss rate.

[0593] As a sub-embodiment of the above embodiment, the uplink coverage quality is RSRP.

[0594] As a sub-embodiment of the above embodiment, the coverage quality of the uplink is the number of retransmissions.

[0595] As a sub-embodiment of the above embodiment, the uplink coverage quality is the value of a counter.

[0596] As a sub-embodiment of the above embodiment, the first threshold is a constant.

[0597] As a sub-embodiment of the above embodiment, the first threshold is a RSRP (Reference Signal Received Power) threshold.

[0598] As a sub-embodiment of the above embodiment, the first threshold is BLER.

[0599] As a sub-embodiment of the above embodiment, the first threshold is a CLI level.

[0600] As an embodiment, the first measurement result reaching the first threshold means that: the first measurement result is equal to or greater than the first threshold.

[0601] As an embodiment, the first measurement result reaching a first threshold means that: the first measurement result is greater than the first threshold.

[0602] As an embodiment, the first measurement result reaching the first threshold means that: the first measurement result is equal to or less than the first threshold.

[0603] As an embodiment, the first measurement result reaching a first threshold means that: the first measurement result is less than the first threshold.

[0604] As an embodiment, the first measurement result reaching the first threshold means that: the first measurement result is equal to the first threshold.

[0605] As an embodiment, the first UE auxiliary information is MAC CE.

[0606] As an embodiment, the first UE auxiliary information is UCI (Uplink Control Information).

[0607] As an embodiment, the first UE auxiliary information is an RRC message.

[0608] Example 8

[0609] Embodiment 8 illustrates a schematic diagram of sub-band non-overlapping full-duplex according to an embodiment of the present application, as shown in the attached Figure 8 As shown in the attached Figure 8 In the figure, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain; the equal dashed line boxes correspond to downlink symbols or flexible symbols in the time domain, and the equal dashed line boxes correspond to DL BWP in the frequency domain; the dot-dash line boxes correspond to uplink symbols in the time domain, and the dot-dash line boxes correspond to UL BWP in the frequency domain; the boxes filled with slashes represent uplink time-frequency resources of sub-band non-overlapping full-duplex; the boxes filled with crosses represent downlink time-frequency resources of sub-band non-overlapping full-duplex; the uplink time-frequency resources of sub-band non-overlapping full-duplex belong to the downlink symbols or flexible symbols corresponding to the equal dashed line boxes in the time domain; the uplink time-frequency resources of sub-band non-overlapping full-duplex belong to UL BWP in the frequency domain; the downlink time-frequency resources of sub-band non-overlapping full-duplex belong to the downlink symbols or flexible symbols corresponding to the equal dashed line boxes in the time domain; the downlink time-frequency resources of sub-band non-overlapping full-duplex belong to DL BWP in the frequency domain.

[0610] As an embodiment, the downlink time-frequency resources of the full-duplex with non-overlapping sub-bands and the uplink time-frequency resources of the full-duplex with non-overlapping sub-bands occupy the same time domain resources.

[0611] As an embodiment, the frequency domain resources occupied by the sub-band non-overlapping full-duplex downlink time-frequency resources and the sub-band non-overlapping full-duplex uplink time-frequency resources are continuous.

[0612] As an embodiment, the frequency domain resources occupied by the downlink time-frequency resources of the full-duplex with non-overlapping sub-bands and the uplink time-frequency resources of the full-duplex with non-overlapping sub-bands are not continuous.

[0613] As an embodiment, the DL BWP and the UL BWP are active BWPs.

[0614] As an embodiment, the center frequency of the DL BWP is the same as the center frequency of the UL BWP.

[0615] As an embodiment, the bandwidth of the DL BWP is the same as the bandwidth of the UL BWP.

[0616] As an embodiment, the bandwidth of the DL BWP is different from the bandwidth of the UL BWP.

[0617] As an embodiment, the DL BWP and the UL BWP belong to the same carrier.

[0618] As an embodiment, the DL BWP and the UL BWP belong to the same serving cell.

[0619] As an embodiment, the equal dashed line boxes correspond to downlink symbols in the time domain.

[0620] As an embodiment, the equal dashed line boxes correspond to flexible symbols in the time domain.

[0621] As an embodiment, the equal dashed boxes correspond to downlink symbols and flexible symbols in the time domain.

[0622] As an embodiment, the sub-band non-overlapping full-duplex is periodic in the time domain.

[0623] As an embodiment, the sub-band non-overlapping full-duplex uplink time-frequency resources include SBFD UL PRBs.

[0624] As an embodiment, the SBFD UL PRB is a UL usable PRB.

[0625] As an embodiment, the SBFD UL PRB is used for the sub-band non-overlapping full-duplex uplink transmission.

[0626] As an embodiment, the sub-band non-overlapping full-duplex uplink time-frequency resources include SBFD DL PRBs.

[0627] As an embodiment, the SBFD DL PRB is a DL usable PRB.

[0628] As an embodiment, the SBFD DL PRB is used for the sub-band non-overlapping full-duplex downlink transmission.

[0629] As an embodiment, the SBFD UL PRB and the SBFD DL PRB occupy consecutive PRBs.

[0630] As an embodiment, the SBFD UL PRB and the SBFD DL PRB occupy non-contiguous PRBs.

[0631] As an embodiment, the SBFD UL PRB shares all configurations of the active UL BWP; the SBFD DLPRB shares all configurations of the active DL BWP.

[0632] As an embodiment, the SBFD UL PRB shares a part of the configuration of the active UL BWP; the SBFD DLPRB shares a part of the configuration of the active DL BWP.

[0633] As an embodiment, the partial configuration is MCS configuration.

[0634] As an embodiment, the partial configuration is time domain resource configuration.

[0635] As an embodiment, the partial configuration is a power configuration.

[0636] As an embodiment, the partial configuration is frequency domain resource configuration.

[0637] As an embodiment, the SBFD UL PRB and active UL BWP are configured independently; the SBFD DL PRB and active DL BWP are configured independently.

[0638] As an embodiment, the sub-band non-overlapping full-duplex uplink time-frequency resources and the sub-band non-overlapping full-duplex downlink time-frequency resources do not overlap.

[0639] As an embodiment, the sub-band non-overlapping frequency domain resources of the full-duplex uplink time-frequency resources include SBFDUL subband.

[0640] As an embodiment, the frequency domain resources of the sub-band non-overlapping full-duplex downlink time-frequency resources include SBFDDL subband.

[0641] As an embodiment, the frequency domain resources of the sub-band non-overlapping full-duplex uplink time-frequency resources do not exceed the ULBWP.

[0642] As an embodiment, the frequency domain resources of the sub-band non-overlapping full-duplex downlink time-frequency resources do not exceed the DLBWP.

[0643] As an embodiment, optionally, the sub-band non-overlapping full-duplex uplink time-frequency resources and the sub-band non-overlapping full-duplex downlink time-frequency resources are continuous in the frequency domain.

[0644] As an embodiment, optionally, the sub-band non-overlapping full-duplex uplink time-frequency resources and the sub-band non-overlapping full-duplex downlink time-frequency resources are not continuous in the frequency domain.

[0645] As an embodiment, optionally, the time domain resources of the uplink time-frequency resources of the sub-band non-overlapping full-duplex are the same as the time domain resources of the downlink time-frequency resources of the sub-band non-overlapping full-duplex.

[0646] As an embodiment, optionally, the time domain resources of the uplink time-frequency resources of the sub-band non-overlapping full-duplex are different from the time domain resources of the downlink time-frequency resources of the sub-band non-overlapping full-duplex.

[0647] As an embodiment, the sub-band non-overlapping full-duplex uplink time-frequency resources are only used for uplink transmission; the sub-band non-overlapping full-duplex downlink time-frequency resources are only used for downlink transmission.

[0648] As an embodiment, the first symbol in the present application overlaps with the time domain resources corresponding to the equal dashed line box in the time domain.

[0649] As an embodiment, the dashed-line box corresponds to a downlink symbol in the time domain; the first symbol in the present application is a downlink symbol corresponding to the dashed-line box.

[0650] As an embodiment, this embodiment does not limit the specific implementation form of the sub-band non-overlapping full-duplex.

[0651] As an embodiment, this embodiment does not limit the position and size of the time-frequency resources of the full-duplex with non-overlapping sub-bands.

[0652] As an embodiment, this embodiment does not limit the sizes of UL BWP and DL BWP.

[0653] Example 9

[0654] Embodiment 9 illustrates a schematic diagram of a first frequency domain information dependent sub-band non-overlapping full-duplex according to an embodiment of the present application, as shown in the attached Fig. 9 As shown in the attached Fig. 9 In the figure, the dotted box represents the first bit map, and the solid box 901, 902 and 903 respectively represent a bit of the first bit map; the bit 901 is set to 1; the bit 902 is set to 0; and the bit 903 is set to 0.

[0655] In embodiment 9, the first frequency domain information depends on the sub-band non-overlapping full-duplex; the first frequency domain information depends on the sub-band non-overlapping full-duplex and includes: the first frequency domain information includes a first bit map, and the first bit map indicates that the first node prefers to use the carrier of the sub-band non-overlapping full-duplex.

[0656] As an embodiment, if one bit in the first bit map is set to 1, it indicates that the carrier corresponding to the one bit is the carrier that the first node prefers to use with non-overlapping sub-band full-duplex; if one bit in the first bit map is set to 0, it indicates that the carrier corresponding to the one bit is not the carrier that the first node prefers to use with non-overlapping sub-band full-duplex.

[0657] As an embodiment, any bit in the first bit map corresponds to a carrier.

[0658] As an embodiment, any bit of at least one bit in the first bit map corresponds to a carrier.

[0659] As an embodiment, bits other than the at least one bit in the first bit map are reserved.

[0660] As an embodiment, bits other than the at least one bit in the first bit map do not correspond to any carrier.

[0661] As an embodiment, any two bits in the first bitmap correspond to different carriers.

[0662] As an embodiment, the size of the first bitmap is variable.

[0663] As an embodiment, the size of the first bitmap is fixed.

[0664] As an embodiment, the size of the first bitmap is 16.

[0665] As an embodiment, the size of the first bitmap is no greater than 16.

[0666] As an embodiment, the carrier corresponding to each bit in the first bitmap is a carrier configured for the first node.

[0667] As an embodiment, the carrier corresponding to each bit in the first bitmap indicates the carrier of the common configuration of the full-duplex with non-overlapping sub-bands.

[0668] As an embodiment, the bit 901 is set to 1 to indicate that the carrier corresponding to the bit 901 is the carrier with non-overlapping sub-bands that the first node prefers to use in full-duplex mode.

[0669] As an embodiment, the bit 902 and the bit 903 are set to 0 to indicate that the carriers corresponding to the bit 902 and the bit 903 are not the carriers that the first node prefers to use for the sub-band non-overlapping full-duplex.

[0670] As an embodiment, the bit 902 and the bit 903 respectively indicate a carrier.

[0671] As an embodiment, the bit 902 indicates a carrier and the bit 903 is reserved.

[0672] As an embodiment, the attached Fig. 9 The size of the first bitmap is not limited and the value of each bit in the first bitmap is not limited.

[0673] Example 10

[0674] Embodiment 10 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.10 As shown in the attached Fig.10 In the embodiment, the processing device 1200 in the first node includes a first receiver 1001 and a first transmitter 1002.

[0675] A first receiver 1001 receives a first RRC message;

[0676] The first transmitter 1002 sends first UE assistance information as a response to the first condition set being satisfied, wherein the first UE assistance information indicates at least one of first frequency domain information or first time domain information;

[0677] In Embodiment 10, at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

[0678] As an embodiment, the first condition set includes detecting internal overheating.

[0679] As an embodiment, the first condition set includes: a first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

[0680] As an embodiment, the first transmitter 1002 starts a first timer along with the sending of the first UE auxiliary information; wherein the first condition set includes that the first timer is not running.

[0681] As an embodiment, the first transmitter 1002 sends first UE capability information;

[0682] The first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex.

[0683] As an embodiment, the first receiver 1001 receives a second RRC message, and the second RRC message configures a first symbol as a downlink symbol; the first transmitter 1002 performs uplink transmission on the first symbol; wherein, the uplink transmission performed on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

[0684] As an embodiment, the first receiver 1001 includes the attached Figure 4 At least one of the antenna 452 or the receiver 454 or the multi-antenna receive processor 458 or the receive processor 456 or the controller / processor 459 or the memory 460 or the data source 467.

[0685] As an embodiment, the first receiver 1001 includes the attached Figure 4 At least an antenna 452 and a receiver 454.

[0686] As an embodiment, the first transmitter 1002 includes the attached Figure 4 At least one of the antenna 452 or the transmitter 454 or the multi-antenna transmit processor 457 or the transmit processor 468 or the controller / processor 459 or the memory 460 or the data source 467.

[0687] As an embodiment, the first transmitter 1002 includes the attached Figure 4 At least antenna 452 and transmitter 454.

[0688] Embodiment 11

[0689] Embodiment 11 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.11 As shown in the attached Fig.11 In the embodiment, the processing device 1100 in the second node includes a second transmitter 1101 and a second receiver 1102.

[0690] The second transmitter 1101 sends a first RRC message;

[0691] The second receiver 1102 receives first UE auxiliary information, wherein the first UE auxiliary information indicates at least one of first frequency domain information or first time domain information;

[0692] In Example 11, in response to a first set of conditions being satisfied, the recipient of the first RRC message sends first UE auxiliary information; at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first set of conditions includes at least the first RRC message enabling the first UE auxiliary information.

[0693] As an embodiment, the first condition set includes detecting internal overheating.

[0694] As an embodiment, the first condition set includes: a first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

[0695] As an embodiment, along with the sending of the first UE auxiliary information, the recipient of the first RRC message starts a first timer; wherein, the first condition set includes that the first timer is not running.

[0696] As an embodiment, the second receiver 1102 receives first UE capability information; wherein the first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex.

[0697] As an embodiment, the second transmitter 1101 sends a second RRC message, and the second RRC message configures the first symbol as a downlink symbol; the second receiver 1102 performs uplink reception on the first symbol; wherein, the uplink reception performed on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

[0698] As an embodiment, the second transmitter 1101 includes the attached Figure 4 At least one of the antenna 420 or the transmitter 418 or the multi-antenna transmit processor 471 or the transmit processor 416 or the controller / processor 475 or the memory 476.

[0699] As an embodiment, the second transmitter 1101 includes the attached Figure 4 At least antenna 420 and transmitter 418.

[0700] As an embodiment, the second receiver 1102 includes the attached Figure 4 At least one of the antenna 420 or the receiver 418 or the multi-antenna reception processor 472 or the reception processor 470 or the controller / processor 475 or the memory 476.

[0701] As an embodiment, the second receiver 1102 includes the attached Figure 4At least an antenna 420 and a receiver 418.

[0702] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed 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, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0703] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first RRC message; The first transmitter sends first UE assistance information as a response to the first set of conditions being met, wherein the first UE assistance information includes at least one of first frequency domain information or first time domain information; At least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

2. The first node according to claim 1, characterized in that: The first condition set includes detection of internal overheating.

3. The first node according to claim 1 or 2, characterized in that: The first condition set includes that the first measurement result reaches a first threshold; the first measurement result is for an uplink; and the first threshold is configurable.

4. The first node according to any one of claims 1 to 3, characterized in that: include: The first transmitter, along with the sending of the first UE auxiliary information, starts a first timer; The first condition set includes that the first timer is not running.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first transmitter sends first UE capability information; The first UE capability information indicates that the first node supports the sub-band non-overlapping full-duplex.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first receiver receives a second RRC message, where the second RRC message configures the first symbol as a downlink symbol; The first transmitter performs uplink transmission on the first symbol; The performing of uplink transmission on the first symbol depends on the first symbol being configured for the sub-band non-overlapping full-duplex.

7. A method in a first node for wireless communication, characterized in that: include: receiving a first RRC message; In response to the first set of conditions being met, sending first UE assistance information; wherein the first UE assistance information includes at least one of first frequency domain information or first time domain information; At least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; and the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first RRC message; A second receiver receives first UE auxiliary information, wherein the first UE auxiliary information includes at least one of first frequency domain information or first time domain information; In which, as a response to the first condition set being met, the recipient of the first RRC message sends first UE auxiliary information; at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

9. A method in a second node for wireless communication, characterized in that: include: Sending a first RRC message; Receive first UE assistance information; wherein the first UE assistance information includes at least one of first frequency domain information or first time domain information; In which, as a response to the first condition set being met, the recipient of the first RRC message sends first UE auxiliary information; at least one of the first frequency domain information or the first time domain information depends on sub-band non-overlapping full-duplex; the first condition set includes at least the first RRC message enabling the first UE auxiliary information.

Images