Methods and apparatuses used in wireless communication

Abstract

Methods and apparatuses are disclosed for use in wireless communications. A communication node receives first information, second information and third information, the first information indicating at least one carrier for a first cell, the second information indicating at least a first downlink subband for a downlink frequency domain configuration of the first cell, and the third information indicating at least one uplink subband for an uplink frequency domain configuration of the first cell. If the first downlink subband is on an anchor carrier of the first cell, there is one uplink subband in the at least one uplink subband whose center frequency is the same as that of the first downlink subband. If the first downlink subband is not on the anchor carrier of the first cell, whether there is one uplink subband in the at least one uplink subband whose center frequency is the same as that of the first downlink subband depends on the configuration of the second information and the third information. The above method is beneficial to improve spectrum utilization.

Description

Technical Field

[0001] This application relates to transmission methods and apparatus in wireless communication systems, and more particularly to multi-carrier methods and apparatus. Background Technology

[0002] In existing NR systems, one or more Bandwidth Parts (BWPs) can be configured on a serving cell, with each BWP occupying at least one contiguous Resource Block (RB). For unpaired spectrum operations, when the index of a Downlink (DL) BWP is the same as the index of a UL (UL) BWP, the DL BWP and the UL BWP are associated. For unpaired spectrum operations, when the index of a DL BWP is the same as the index of a UL BWP, the UE does not expect to receive a configuration where the center frequency of the DL BWP is different from the center frequency of the UL BWP.

[0003] Existing carrier aggregation (CA) treats each component carrier (CC) as a serving cell. While existing carrier aggregation can improve the UE's service bandwidth and transmission rate, it has low efficiency in utilizing fragmented spectrum resources. Configuring multiple carriers for the same cell can not only leverage the advantages of existing carrier aggregation but also effectively improve the utilization efficiency of fragmented spectrum resources, making it an important evolution direction for future wireless communication technologies (such as 5G+ or 6G). Summary of the Invention

[0004] The inventors discovered through research that when a cell can be configured with multiple carriers, how to configure UL BWP and DL BWP for unpaired spectrum is a technical problem that needs to be solved.

[0005] To address the aforementioned issues, this application provides a solution. In the above description of the problems, UL BWP and DL BWP are used as examples. While it is beneficial to correspond the at least first downlink sub-interval and the at least one uplink sub-interval in this application to UL BWP and DL BWP, respectively, this application does not limit the correspondence between the at least first downlink sub-interval and the at least one uplink sub-interval in this application and UL BWP and DL BWP. Furthermore, using different definitions and / or names is beneficial for distinguishing from existing BWPs and avoiding impact on existing BWP operations. Moreover, using different definitions and / or names is also beneficial for enhancing specific functions in scenarios where multiple carriers are configured in a single cell.

[0006] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS38 series.

[0007] It should be noted that, unless otherwise specified, the embodiments and features in any node of this application can be applied to any other node. Furthermore, unless otherwise specified, the embodiments and features in any embodiment of this application can be arbitrarily combined with each other.

[0008] This application discloses a method used in a first node for wireless communication, characterized by comprising:

[0009] Receive first information, second information and third information, wherein the first information is a first cell indicating at least one carrier, the second information is a downlink frequency domain configuration of at least a first downlink sub-interval of the first cell, and the third information is an uplink frequency domain configuration of at least one uplink sub-interval of the first cell;

[0010] Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information.

[0011] The above method is designed for unpaired spectrum. Under the premise that the center frequency of one uplink sub-interval on the anchor carrier is the same as the center frequency of one downlink sub-interval, the center frequency of the uplink sub-interval in the at least one uplink sub-interval and the center frequency of the downlink sub-interval in the at least one first downlink sub-interval on the unanchor carrier can be flexibly configured. This is beneficial for adaptive adjustment of the uplink and downlink sub-intervals to better support uplink and downlink asymmetric services, improve spectrum utilization, and reduce the power consumption of the first node and / or the sender of the second information.

[0012] As one embodiment, the first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers. As one embodiment, the anchor carrier may be used to carry at least one of SIB1 (System Information Block 1) and broadcast synchronization signals.

[0013] As an example, the first cell may be configured with at most one anchor carrier and at most multiple non-anchor carriers; wherein the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0014] According to one aspect of this application, the at least first downlink sub-interval comprises a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there exists an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0015] The above methods are beneficial for balancing uplink and downlink transmission.

[0016] According to one aspect of this application, the downlink sub-interval or the uplink sub-interval is configured only on at least one non-anchor carrier of the first cell.

[0017] The above method can be configured with more uplink sub-intervals or more downlink sub-intervals as needed, which is beneficial for supporting asymmetric services.

[0018] According to one aspect of this application, the second information is configured with a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information is configured with a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

[0019] The above method, by identifying the at least first downlink sub-interval and the at least one uplink sub-interval, facilitates the operation and management of the at least first downlink sub-interval and the at least one uplink sub-interval.

[0020] According to one aspect of this application, it is characterized by comprising:

[0021] The first receiver receives a first signaling instruction, which indicates a first time-frequency resource block;

[0022] The first time-frequency resource block is used for PDSCH (Physical Downlink Shared Channel), and the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-interval, wherein the at least first downlink sub-interval includes multiple downlink sub-intervals.

[0023] The above method improves scheduling flexibility and increases downlink system capacity by scheduling multiple downlink sub-intervals.

[0024] As an example, the PDSCH carries a TB (Transport Block).

[0025] According to one aspect of this application, it is characterized by comprising:

[0026] The first receiver receives a first signaling instruction, which indicates a first time-frequency resource block;

[0027] The first time-frequency resource block is used for PUSCH (Physical Uplink Shared Channel), and the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-interval, wherein the at least one uplink sub-interval includes multiple uplink sub-intervals.

[0028] The above method, by scheduling multiple uplink sub-intervals, helps to improve scheduling flexibility and increase uplink system capacity.

[0029] As an example, the PUSCH carries a TB.

[0030] According to one aspect of this application, it is characterized by comprising:

[0031] Deactivate the first carrier;

[0032] When the first carrier is deactivated, the first operation is not performed for each downlink sub-interval on the first carrier. The first operation includes receiving DL-SCH (Downlink Shared Channel) or listening to PDCCH (Physical Downlink Control Channel).

[0033] The above method reduces the first operation on the deactivated carrier by deactivating the carrier, which is beneficial for network energy saving.

[0034] Typically, the first carrier is any non-anchor carrier of the first cell.

[0035] In the above method, the anchor carrier cannot be deactivated; the above method avoids the impact on the anchor carrier of the first cell and ensures transmission in the first cell.

[0036] According to one aspect of this application, it is characterized by comprising:

[0037] Deactivate the first carrier;

[0038] Wherein, when the first carrier is deactivated, the first operation is not performed for each downlink sub-interval on the first carrier, the first operation including at least one of receiving DL-SCH or listening to PDCCH; when the first carrier is deactivated, whether the first operation is performed for one downlink sub-interval of the at least first downlink sub-interval depends on whether the first carrier is the anchor carrier of the first cell, and the downlink sub-interval is not on the first carrier.

[0039] Wherein, the statement that whether the first operation is performed on one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell includes:

[0040] If the first carrier is not the anchor carrier of the first cell, the first operation is performed for the downlink sub-interval;

[0041] If the first carrier is the anchor carrier of the first cell, the first operation is not performed for the downlink sub-interval.

[0042] The above method reduces the number of first operations performed on multiple downlink sub-cells by deactivating the anchor carrier, further reducing the power consumption of the first node and the sender of the second information, and is also beneficial for the management of multiple downlink sub-cells.

[0043] According to one aspect of this application, it is characterized by comprising:

[0044] Before deactivating the first carrier, the second signaling is received;

[0045] The second signaling instruction indicates to deactivate the first carrier.

[0046] How to activate the first carrier is a problem that needs to be solved. The above method activates the first carrier by instructing it with the second signaling, which is beneficial to network control.

[0047] This application discloses a method used in a second node for wireless communication, characterized by comprising:

[0048] Send a first message, a second message, and a third message, wherein the first message indicates at least one carrier for a first cell, the second message configures at least a first downlink sub-interval in the downlink frequency domain of the first cell, and the third message configures at least one uplink sub-interval in the uplink frequency domain of the first cell.

[0049] Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information;

[0050] The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers.

[0051] or,

[0052] The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0053] According to one aspect of this application, the at least first downlink sub-interval comprises a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there exists an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0054] According to one aspect of this application, the downlink sub-interval or the uplink sub-interval is configured only on at least one non-anchor carrier of the first cell.

[0055] According to one aspect of this application, the second information is configured with a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information is configured with a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

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

[0057] Send a first signaling instruction, which indicates a first time-frequency resource block;

[0058] Wherein, the first time-frequency resource block is used for PDSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-interval, and the at least first downlink sub-interval includes multiple downlink sub-intervals;

[0059] or,

[0060] The first time-frequency resource block is used for PUSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-interval, and the at least one uplink sub-interval includes multiple uplink sub-intervals.

[0061] According to one aspect of this application, it is characterized by comprising:

[0062] Send a second signaling message;

[0063] Wherein, the second signaling instructs the deactivation of the first carrier; when the first carrier is deactivated, the receiver of the second information does not perform the first operation for each downlink sub-interval on the first carrier, the first operation including at least one of receiving DL-SCH or listening to PDCCH.

[0064] According to one aspect of this application, when the first carrier is deactivated, whether the receiver of the second information performs the first operation for one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell, and the one downlink sub-interval is not on the first carrier;

[0065] Wherein, whether the receiver of the second information performs the first operation for one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell, including:

[0066] If the first carrier is not the anchor carrier of the first cell, the receiver of the second information performs the first operation for the downlink sub-interval;

[0067] If the first carrier is the anchor carrier of the first cell, the receiver of the second information does not perform the first operation for the downlink sub-interval.

[0068] This application discloses a first node used for wireless communication, characterized in that it includes:

[0069] A first receiver receives first information, second information, and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is a configuration of at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0070] Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information;

[0071] The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers.

[0072] or,

[0073] The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0074] This application discloses a second node used for wireless communication, characterized by comprising:

[0075] The second transmitter transmits first information, second information, and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is a configuration of at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0076] Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information;

[0077] The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers.

[0078] or,

[0079] The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals. Attached Figure Description

[0080] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0081] Figure 1 A flowchart of a first node according to an embodiment of this application is shown;

[0082] Figure 2 A schematic diagram of a network architecture according to an embodiment of this application is shown;

[0083] Figure 3 A schematic diagram of an embodiment of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application is shown;

[0084] Figure 4 A schematic diagram of a first communication device and a second communication device according to an embodiment of this application is shown;

[0085] Figure 5 A flowchart illustrating a wireless signal transmission process according to an embodiment of this application is shown;

[0086] Figure 6 A flowchart illustrating a wireless signal transmission process according to another embodiment of this application is shown;

[0087] Figure 7 A flowchart illustrating a wireless signal transmission process according to yet another embodiment of this application is shown;

[0088] Figure 8 A flowchart illustrating whether a first operation is performed on a first downlink sub-interval according to an embodiment of this application is shown;

[0089] Figure 9 A schematic diagram illustrating whether, according to an embodiment of this application, there exists an uplink sub-interval whose center frequency is the same as that of the first downlink sub-interval, depending on whether the first downlink sub-interval is on the anchor carrier of the first cell;

[0090] Figure 10 A schematic diagram illustrating each downlink sub-interval associated with an uplink sub-interval according to an embodiment of this application is shown;

[0091] Figure 11 A schematic diagram is shown showing a non-anchor carrier configured with only downlink sub-intervals or only uplink sub-intervals according to an embodiment of this application;

[0092] Figure 12 A schematic diagram of the frequency domain identifier of the downlink sub-interval and the frequency domain identifier of the downlink sub-interval according to an embodiment of this application is shown;

[0093] Figure 13 A schematic diagram of a first frequency domain interval identifier and a second frequency domain interval identifier according to an embodiment of this application is shown;

[0094] Figure 14 A schematic diagram is shown according to an embodiment of the present application, in which at least a first downlink sub-interval belongs to a DLBWP and the at least one uplink sub-interval belongs to a UL BWP;

[0095] Figure 15 A schematic diagram of an RB on at least a first downlink sub-interval according to an embodiment of this application is shown;

[0096] Figure 16 A structural block diagram of a processing apparatus for a first node according to an embodiment of this application is shown;

[0097] Figure 17 A structural block diagram of a processing apparatus for a second node according to an embodiment of this application is shown;

[0098] Figure 18 A schematic diagram of TDD operation according to an embodiment of this application is shown. Detailed Implementation

[0099] The technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0100] Example 1

[0101] Example 1 illustrates a flowchart of a first node according to an embodiment of this application, as shown in the attached diagram. Figure 1 As shown.

[0102] In Embodiment 1, the first node in this application receives first information, second information, and third information in step 101. The first information indicates at least one carrier for a first cell; the second information configures at least one first downlink sub-interval in the downlink frequency domain of the first cell; and the third information configures at least one uplink sub-interval in the uplink frequency domain of the first cell. Both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum. Whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell. If the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval. If the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second and third information.

[0103] Typically, the first node is in the RRC_CONNECTED state.

[0104] As an example, the first cell is a serving cell.

[0105] As an example, the first cell is indicated by a ServCellIndex.

[0106] As an example, the first cell is a PCell (Primary Cell).

[0107] As an example, the first cell is a PSCell (Primary SCG (Secondary Cell Group) Cell, SCG primary cell).

[0108] As an example, the first cell is an SCell (Secondary Cell).

[0109] As an example, the first information is unicast. This method helps to improve configuration flexibility.

[0110] As an example, the first information is broadcast. This method reduces signaling overhead.

[0111] As one embodiment, the first information includes unicast information and broadcast information.

[0112] As an example, the first information is at least one RRC message.

[0113] As an example, the first information is at least one RRC field of at least one RRC message.

[0114] As a sub-implementation, the at least one RRC domain includes at least one ServingCellConfigCommonIE.

[0115] As a sub-implementation, the at least one RRC domain includes at least one ServingCellConfigCommonSIB IE.

[0116] As one example, the first information includes cell common messages.

[0117] As an example, the cell public message includes at least one RRC field of at least one system message.

[0118] As an example, the at least one system message includes a SIB1 message.

[0119] As an example, the at least one system message includes a SystemInformation message.

[0120] As one example, the first information includes UE-specific messages.

[0121] As an example, the UE-specific message includes at least one RRC field of at least one specific message.

[0122] As an example, the at least one dedicated message includes an RRC connection reconfiguration message.

[0123] As an example, the at least one dedicated message includes an RRC connection recovery (Resume) message.

[0124] As an example, the first information includes at least one MAC CE (Control Element).

[0125] As an example, the first information includes at least one DCI (Downlink Control Information).

[0126] As one embodiment, the at least one carrier includes multiple carriers, and the at least one carrier belongs to the same frequency band.

[0127] As one embodiment, the at least one carrier includes multiple carriers, and two of the at least one carriers belong to different frequency bands.

[0128] As an example, the first information includes frequency information for each of the at least one carrier.

[0129] As an example, the first information includes the frequency domain position and bandwidth of each of the at least one carrier.

[0130] As an example, the first information indicates the subcarrier spacing of each of the at least one carrier.

[0131] As an example, the subcarrier spacing of each of the at least one carrier is indicated by one SCS-SpecificCarrier IE in the first information.

[0132] As one embodiment, the first information includes at least one ServingCellConfigCommon IE or ServingCellConfigCommonSIB IE, which configures multiple carriers. The first information block includes at least one ServingCellConfig IE, which indicates the at least one carrier from the multiple carriers.

[0133] As one embodiment, the first information includes at least one ServingCellConfig IE, which configures the at least one carrier.

[0134] As one embodiment, the first information includes at least one RRC field, and each of the at least one RRC field included in the first information adds, modifies, or releases one or more carriers for the first cell.

[0135] As one example, the first information includes the identifier of the first cell.

[0136] As a sub-example, the identifier is a physical cell identifier (e.g., PhysCellId).

[0137] As a sub-implementation, the identifier is a serving cell index (e.g., ServCellIndex).

[0138] As one example, the first information includes the common downlink parameters of the first cell (e.g., DownlinkConfigCommon).

[0139] As one embodiment, the first information includes at least one of the following: the first cell's TDD uplink / downlink common configuration (e.g., TDD-UL-DL-ConfigCommon), the TA (Timing Advance) parameter (e.g., n-TimingAdvanceOffset), or the subcarrier spacing (e.g., SubcarrierSpacing).

[0140] As one embodiment, the at least one carrier is all the carriers configured for the first cell.

[0141] As one embodiment, the at least one carrier is a portion of the carriers configured for the first cell.

[0142] As an example, the at least one carrier is a carrier.

[0143] As one embodiment, the at least one carrier includes multiple carriers.

[0144] As one example, the number of carriers in the at least one carrier depends on the configuration of the first information.

[0145] As an example, the number of carriers included in the at least one carrier does not exceed Q1; Q1 is a positive integer greater than 1.

[0146] As a sub-implementation, Q1 is predefined.

[0147] As a sub-implementation, Q1 is configurable.

[0148] As one embodiment, each of the at least one carrier is indicated by an index. This method helps to improve the flexibility of carrier configuration or operation.

[0149] As a sub-implementation, the index of each of the at least one carrier is logical.

[0150] As a sub-implementation, the index of each of the at least one carrier includes a non-negative integer.

[0151] As a sub-implementation, the index of each of the at least one carriers is a non-negative integer.

[0152] As a sub-example, the index of each of the at least one carrier includes a positive integer.

[0153] As a sub-implementation, the index of each of the at least one carrier is a positive integer.

[0154] As a sub-example, the first information configures an index for each of the at least one carrier.

[0155] As a sub-example, the first information includes an index of each of the at least one carrier.

[0156] As an example, the at least one carrier includes multiple carriers, and any two carriers in the at least one carrier are spaced differently by the subcarrier spacing indicated by the first information.

[0157] As an example, the at least one carrier includes multiple carriers, and any two of the at least one carriers have different indices.

[0158] As an example, each carrier in this application occupies consecutive frequency resources.

[0159] As an example, each carrier in this application occupies either continuous or non-contiguous frequency resources. This method is beneficial for making full use of small-bandwidth frequency resources.

[0160] As an example, each carrier in this application corresponds to at least one component carrier.

[0161] As an example, each carrier in this application corresponds to at least one fragmented carrier.

[0162] As an example, each carrier in this application corresponds to at least one component carrier or fragment carrier.

[0163] As an example, the carrier in this application does not refer to BWP (Bandwidth Part).

[0164] As an example, the carrier in this application does not refer to RB (Resource Block).

[0165] As an example, the carrier in this application does not refer to RBG (Resource Block Group).

[0166] As one example, the second information is unicast. This method improves configuration flexibility.

[0167] As one example, the second information is broadcast. This method reduces signaling overhead.

[0168] As one embodiment, the second information includes unicast information and broadcast information.

[0169] As one example, the second information is at least one RRC message.

[0170] As one embodiment, the second information is at least one RRC field of at least one RRC message.

[0171] As a sub-implementation, the at least one RRC domain includes at least one DownlinkConfigCommonIE.

[0172] As a sub-implementation, the at least one RRC domain includes at least one DownlinkConfigCommonIE.

[0173] As a sub-implementation, the at least one RRC domain includes at least one DownlinkConfigCommonIE.

[0174] As a sub-implementation, the at least one RRC domain includes at least one DownlinkConfigCommonSIBIE.

[0175] As a sub-implementation, the at least one RRC domain includes at least one DownlinkConfig IE.

[0176] As one example, the second information includes cell common messages.

[0177] As an example, the cell public message includes at least one RRC field of at least one system message.

[0178] As an example, the at least one system message includes a SIB1 message.

[0179] As an example, the at least one system message includes a SystemInformation message.

[0180] As one example, the second information includes UE-specific messages.

[0181] As an example, the UE-specific message includes at least one RRC field of at least one specific message.

[0182] As an example, the at least one dedicated message includes an RRC connection reconfiguration message.

[0183] As an example, the at least one dedicated message includes an RRC connection recovery (Resume) message.

[0184] As an example, the second information includes at least one MAC CE.

[0185] As one example, the second information includes at least one DCI.

[0186] As one example, the third information is unicast. This method improves configuration flexibility.

[0187] As one example, the third information is broadcast. This method reduces signaling overhead.

[0188] As one example, the third information includes unicast information and broadcast information.

[0189] As an example, the third information is at least one RRC message.

[0190] As an example, the third information is at least one RRC field of at least one RRC message.

[0191] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfigCommon IE.

[0192] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfigCommon IE.

[0193] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfigCommon IE.

[0194] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfigCommonSIBIE.

[0195] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfig IE.

[0196] As a sub-implementation, the at least one RRC domain includes at least one UplinkConfig IE.

[0197] As one example, the third information includes cell common messages.

[0198] As an example, the cell public message includes at least one RRC field of at least one system message.

[0199] As an example, the at least one system message includes a SIB1 message.

[0200] As an example, the at least one system message includes a SystemInformation message.

[0201] As one example, the third information includes UE-specific messages.

[0202] As an example, the UE-specific message includes at least one RRC field of at least one specific message.

[0203] As an example, the at least one dedicated message includes an RRC connection reconfiguration message.

[0204] As an example, the at least one dedicated message includes an RRC connection recovery (Resume) message.

[0205] As an example, the third information includes at least one MAC CE.

[0206] As an example, the third information includes at least one DCI.

[0207] As one embodiment, the second information indicates the carrier in which each of the at least first downlink sub-intervals is located, and the third information indicates the carrier in which each of the at least one uplink sub-intervals is located.

[0208] As one embodiment, the second information indicates the frequency domain location and bandwidth of each downlink sub-interval in the at least first downlink sub-interval; the third information indicates the frequency domain location and bandwidth of each uplink sub-interval in the at least one uplink sub-interval.

[0209] As one embodiment, the second information includes at least one locationAndBandwidth field, wherein the at least one locationAndBandwidth field included in the second information configures the at least one first downlink sub-interval for the downlink frequency domain of the first cell respectively; the third information includes at least one locationAndBandwidth field, wherein the at least one locationAndBandwidth field included in the third information configures the at least one uplink sub-interval for the uplink frequency domain of the first cell respectively.

[0210] As one embodiment, the second information includes at least one RRC field, and each of the at least one RRC field included in the second information adds, modifies, or releases one or more downlink sub-intervals for the downlink frequency domain of the first cell; the third information includes at least one RRC field, and each of the at least one RRC field included in the third information adds, modifies, or releases one or more uplink sub-intervals for the uplink frequency domain of the first cell.

[0211] As an example, the downlink frequency domain of the first cell is used for downlink transmission of the first cell, and the uplink frequency domain of the first cell is used for uplink transmission of the first cell.

[0212] As an example, the downlink frequency domain of the first cell is used to transmit the downlink physical channel or downlink physical signal of the first cell, and the uplink frequency domain of the first cell is used to transmit the uplink physical channel or uplink physical signal of the first cell.

[0213] As one embodiment, the at least first downlink sub-interval includes only one downlink sub-interval.

[0214] As one embodiment, the at least first downlink sub-interval includes multiple downlink sub-intervals.

[0215] As one embodiment, each downlink sub-interval in the at least first downlink sub-interval includes at least one RB.

[0216] As an example, each downlink sub-interval in the at least first downlink sub-interval is continuous in the frequency domain.

[0217] As one embodiment, each downlink sub-interval in the at least first downlink sub-interval consists of a plurality of consecutive RBs in the frequency domain.

[0218] As one embodiment, the at least first downlink sub-interval includes a plurality of downlink sub-intervals, and any two downlink sub-intervals in the at least first downlink sub-interval are discontinuous in the frequency domain.

[0219] As one embodiment, the at least one uplink sub-interval includes only one uplink sub-interval.

[0220] As one embodiment, the at least one uplink sub-interval includes multiple uplink sub-intervals.

[0221] As an example, each of the at least one uplink sub-interval includes at least one RB.

[0222] As an example, each of the at least one uplink sub-interval is continuous in the frequency domain.

[0223] As an example, each of the at least one uplink sub-interval consists of a plurality of consecutive RBs in the frequency domain.

[0224] As an example, the at least one uplink sub-interval includes multiple uplink sub-intervals, and any two uplink sub-intervals in the at least one uplink sub-interval are discontinuous in the frequency domain.

[0225] As an example, the maximum number of the at least first downlink sub-intervals is predefined.

[0226] As an example, the maximum number of the at least first downlink sub-intervals is configurable.

[0227] As an example, the maximum number of the at least one uplink sub-interval is predefined.

[0228] As an example, the maximum number of the at least one uplink sub-interval is configurable.

[0229] As an example, the maximum number of the at least first downlink sub-intervals is equal to the maximum number of the at least one uplink sub-intervals.

[0230] As an example, the maximum number of the at least first downlink sub-intervals is not equal to the maximum number of the at least one uplink sub-intervals.

[0231] As one embodiment, each of the at least first downlink sub-intervals is on a carrier of the first cell, and each of the at least one uplink sub-intervals is on a carrier of the first cell.

[0232] As one embodiment, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; each downlink sub-interval in the at least first downlink sub-interval is on a carrier of the first cell, and at least two downlink sub-intervals in the at least first downlink sub-interval are on the same carrier.

[0233] Typically, the at least first downlink sub-interval includes multiple downlink sub-intervals; each downlink sub-interval in the at least first downlink sub-interval is on a carrier of the first cell, and any two downlink sub-intervals in the at least first downlink sub-interval are not on the same carrier.

[0234] As an example, the at least one uplink sub-interval includes a plurality of uplink sub-intervals; each of the at least one uplink sub-intervals is on a carrier of the first cell, and at least two of the at least one uplink sub-intervals are on the same carrier.

[0235] Typically, the at least one uplink sub-interval includes multiple uplink sub-intervals; each of the at least one uplink sub-intervals is on a carrier of the first cell, and any two uplink sub-intervals are not on the same carrier.

[0236] As an example, each downlink sub-interval in the at least first downlink sub-interval is active and not dormant; each uplink sub-interval in the at least one uplink sub-interval is active and not dormant; the downlink sub-interval can be activated / deactivated, and the downlink sub-interval can be dormant / not dormant.

[0237] As an example, the first downlink sub-interval being on the anchor carrier of the first cell means that the frequency resources corresponding to the first downlink sub-interval belong to the frequency resources corresponding to the anchor carrier of the first cell; the first downlink sub-interval not being on the anchor carrier of the first cell means that the frequency resources corresponding to the first downlink sub-interval do not overlap with the frequency resources corresponding to the anchor carrier of the first cell.

[0238] As an example, "the first downlink sub-interval on the anchor carrier of the first cell" means that the first downlink sub-interval is configured on the anchor carrier of the first cell; "the first downlink sub-interval not on the anchor carrier of the first cell" means that the first downlink sub-interval is configured on the non-anchor carrier of the first cell.

[0239] As an example, if the first downlink sub-interval is on the anchor carrier of the first cell, it is required that the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval.

[0240] As an example, as long as the first downlink sub-interval is on the anchor carrier of the first cell, there is one uplink sub-interval whose center frequency is the same as the center frequency of the first downlink sub-interval.

[0241] As an example, if the first downlink sub-interval is on the anchor carrier of the first cell, the network guarantees that there exists an uplink sub-interval with the same center frequency as the first downlink sub-interval.

[0242] As an example, if the first downlink sub-interval is on the anchor carrier of the first cell, the first node does not expect the center frequency of any of the at least one uplink sub-intervals to be different from the center frequency of the first downlink sub-interval.

[0243] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, it is not required that the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval.

[0244] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, at least the configuration of the second information and the third information is used to determine whether there is an uplink sub-interval with the same center frequency as the first downlink sub-interval.

[0245] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, whether there is an uplink sub-interval with the same center frequency as the first downlink sub-interval depends on the configuration of the second information and the third information.

[0246] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, the third information may configure the center frequency of one of the at least one uplink sub-intervals to the center frequency of the first downlink sub-interval configured by the second information. Alternatively, the third information may configure the center frequency of any of the at least one uplink sub-intervals to a center frequency other than the center frequency of the first downlink sub-interval configured by the second information.

[0247] As one example, the first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers;

[0248] As an example, the at least one carrier is a carrier, and the carrier is the anchor carrier.

[0249] As an example, the at least one carrier includes a plurality of carriers, one of the plurality of carriers is the anchor carrier, and at least one of the plurality of carriers is the non-anchor carrier.

[0250] As an example, the first cell is configured with at least one anchor carrier.

[0251] As an example, the first cell is configured with only one anchor carrier; the first cell is not configured with any non-anchor carriers.

[0252] As an example, the first cell being configured with a maximum of multiple non-anchor carriers means that the first cell is configured with a maximum of N1 non-anchor carriers, where N1 is an integer greater than 1.

[0253] As an example, N1 is predefined.

[0254] As an example, N1 is the default.

[0255] As an example, N1 is determined by the sender of the first information.

[0256] As an example, N1 is determined by the sender of the first information based on the recommendation of the first node.

[0257] As an example, N1 is determined by the sender of the first information based on the UE capabilities of the first node.

[0258] As an example, N1 is Q1-1.

[0259] As an example, Q1 is N1+1.

[0260] As an example, the first cell is configured with at least one non-anchor carrier.

[0261] As an example, the first cell is configured with at least 0 non-anchor carriers.

[0262] As an example, the first cell is configured with one anchor carrier and zero non-anchor carriers.

[0263] As an example, the first cell is configured with one anchor carrier and one non-anchor carrier.

[0264] As an example, the first cell is configured with one anchor carrier and multiple non-anchor carriers.

[0265] As an example, the non-anchor carrier is optional.

[0266] As an example, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0267] As one embodiment, the anchor carrier is used to carry at least one of SIB1 and the broadcast synchronization signal; whether the non-anchor carrier is used to carry at least one of the SIB1 and the broadcast synchronization signal depends on the network configuration.

[0268] As one embodiment, the anchor carrier is used to carry at least one of SIB1 and the broadcast synchronization signal; whether the non-anchor carrier is used to carry at least one of the SIB1 and the broadcast synchronization signal depends on the configuration of the second information.

[0269] As an example, at least one of the SIB1 and the broadcast synchronization signal is only the former of the two.

[0270] As an example, at least one of the SIB1 and the broadcast synchronization signal is only the latter of the two.

[0271] As an example, at least one of the SIB1 and the broadcast synchronization signal is both the SIB1 and the broadcast synchronization signal.

[0272] As an example, the broadcast synchronization signal is an SSB (SS / PBCH block).

[0273] As an example, the broadcast synchronization signal is CD (Cell Defining)-SSB.

[0274] As an example, the broadcast synchronization signal is a MIB (Master Information Block).

[0275] As an example, the broadcast synchronization signal includes the PSS (Primary Synchronization Signal).

[0276] As one example, the broadcast synchronization signal includes SSS (Secondary Synchronization Signal).

[0277] As one example, the broadcast synchronization signal includes PSS and PBCH (Physical Broadcast Channel).

[0278] As one example, the broadcast synchronization signal includes SSS and PBCH.

[0279] As one example, the broadcast synchronization signal includes a MIB.

[0280] As an example, the first cell may be configured with at most one anchor carrier and at most multiple non-anchor carriers; wherein the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0281] As an example, the anchor carrier refers to the master or primary frequency unit.

[0282] As an example, the anchor carrier refers to the initial carrier.

[0283] As an example, the anchor carrier is the carrier used to determine Point A.

[0284] As a sub-implementation, PointA is Common RB 0.

[0285] As a sub-implementation, PointA is the absolute frequency position of the reference resource block.

[0286] As an example, the anchor carrier refers to a frequency unit with an index of 0; wherein, the index of non-anchor frequency units is greater than 0. This method is beneficial for the identification and management of anchor frequency units.

[0287] As an example, the index of the anchor carrier is variable.

[0288] As an example, the anchor carrier is configured with cell-specific physical layer parameters of the first cell.

[0289] As a sub-example, only the anchor carrier of the first cell is configured with cell-specific physical layer parameters of the first cell.

[0290] As a sub-example, the anchor carrier and at least one non-carrier of the first cell are configured with cell-specific physical layer parameters of the first cell.

[0291] As a sub-example, only the cell-specific physical layer parameters of the first cell of the anchor carrier are applied.

[0292] As a sub-implementation, the cell-specific physical layer parameters of the first cell are configured by a designated information block; the designated information block includes at least one of PDCCH-ConfigCommon, SearchSpaceZero, pagingSearchSpace, searchSpaceSIB1, or PDSCH-ConfigCommon.

[0293] As a sub-example, the cell-specific physical layer parameters of the first cell are configured by a designated information block; the designated information block includes PDSCH-ConfigCommon.

[0294] As a sub-example, the cell-specific physical layer parameters of the first cell are applied to at least the PDCCH.

[0295] As a sub-example, the cell-specific physical layer parameters of the first cell are applied to the PDSCH (Physical Downlink Shared Channel).

[0296] Example 2

[0297] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of this application, as shown in the attached diagram. Figure 2 As shown. (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 a 5G+ network architecture, or a 6G network architecture, or a future evolution network architecture of 3GPP; the network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System), or 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 interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination toward UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), CU (Centralized Unit), DU (Distributed Unit), TRP (Transmitter Receiver Node), or some other suitable term. Instances of node 203 include NodeB (NB), gNB, eNB, ng-eNB, en-gNB, IAB network devices (e.g., IAB-node, IAB-donor, IAB-donor-CU, or IAB-donor-DU), testing devices, and signaling testers. Instances of node 203 may also include relay devices (e.g., L3 relay, L2 relay, or L1 relay), routers, switches, and gateway devices.The core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or the core network 210 is a 6GC; node 203 provides UE 201 with an access point to the core network 210. Examples of UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband IoT devices, IoT terminals, industrial IoT devices, machine-type communication devices, land vehicles, automobiles, ships, wearable devices (e.g., watches, rings, glasses, VR / XR devices), handsets, in-vehicle terminals, IAB terminal equipment (e.g., IAB-MT), test equipment, signaling testers, or any other similar functional devices. Those skilled in the art may also refer to UE201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. Node 203 is connected to the core network 210 via the 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 the control node that handles signaling between UE201 and the core network 210. In general, the MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through the S-GW / UPF212, which itself is connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 connects to Internet service 230.Internet services 230 include operator-compliant Internet protocol services, which may specifically include the Internet, intranets, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0298] As an example, the UE201 corresponds to the first node in this application.

[0299] As an example, the first node in this application includes the UE201.

[0300] As an example, UE201 is a UE.

[0301] As an example, the UE201 is a terminal.

[0302] As an example, the UE201 is a relay device.

[0303] As an example, the UE201 is a gateway device.

[0304] As an example, the UE201 supports configuring multiple carriers in a single cell.

[0305] As an example, the UE201 supports SCMC.

[0306] As an example, the UE201 supports TN.

[0307] As an example, the UE201 supports TN and NTN.

[0308] As an example, node 203 corresponds to the second node in this application.

[0309] As an example, the second node in this application includes node 203.

[0310] As one example, node 203 is a base station device.

[0311] As an example, node 203 is a UE.

[0312] As one example, node 203 is a relay device.

[0313] As one example, node 203 is a core network device.

[0314] As one example, the node 203 supports configuring multiple carriers in a single cell.

[0315] As an example, node 203 supports SCMC.

[0316] As an example, node 203 is a TN base station.

[0317] As an example, node 203 is an NTN base station.

[0318] As an example, the first node in this application includes the UE201, and the second node in this application includes the node203.

[0319] Typically, the first node in this application is a UE, and the second node in this application is a base station device.

[0320] Example 3

[0321] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and a control plane according to this application, as shown in the attached diagram. Figure 3 As shown. Figure 3 This is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3The radio protocol architecture for control plane 300 is illustrated using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (Physical Layer) signal processing functions. L1 layer will be referred to as PHY301 in this document. Layer 2 (L2 layer) 305 sits above PHY301 and includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. It also provides security through encrypted data packets and cross-area mobility support. The RLC sublayer 303 provides segmentation and reassembly of upper-layer packets, retransmission of lost packets, and packet reordering to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). MAC sublayer 302 provides multiplexing between the logical and transport channels. MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for acquiring 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) and Layer 2 (L2). The radio protocol architecture in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for Physical Layer 351, PDCP sublayer 354 in L2 Layer 355, RLC sublayer 353 in L2 Layer 355, and MAC sublayer 352 in L2 Layer 355. However, PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for the mapping between QoS streams and data radio bearers (DRBs) to support service diversity.

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

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

[0324] As an example, the first information in this application is generated in the RRC306.

[0325] As an example, a portion of the first information in this application is generated in the RRC306.

[0326] As a sub-example, part of the first information in this application is generated by the MAC302 or MAC352.

[0327] As a sub-implementation, part of the first information in this application is generated in the PHY301 or PHY351.

[0328] As an example, the second information in this application is generated in the RRC306.

[0329] As an example, a portion of the second information in this application is generated in the RRC306.

[0330] As a sub-example, part of the second information in this application is generated in the MAC302 or MAC352.

[0331] As a sub-implementation, part of the second information in this application is generated in the PHY301 or PHY351.

[0332] As an example, the third information in this application is generated in the RRC306.

[0333] As an example, a portion of the third information in this application is generated in the RRC306.

[0334] As a sub-example, part of the third information in this application is generated in MAC302 or MAC352.

[0335] As a sub-implementation, part of the third information in this application is generated in the PHY301 or PHY351.

[0336] As an example, the first signaling in this application is generated in the RRC306.

[0337] As an example, the first signaling in this application is generated in MAC302 or MAC352.

[0338] As an example, the first signaling in this application is generated in the PHY301 or PHY351.

[0339] As an example, the second signaling in this application is generated in the RRC306.

[0340] As an example, the second signaling in this application is generated in MAC302 or MAC352.

[0341] As an example, the second signaling in this application is generated in the PHY301 or PHY351.

[0342] Example 4

[0343] Example 4 shows schematic diagrams of a first communication device and a second communication device according to this application, as shown in the appendix. Figure 4 As shown. Figure 4 This is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in the access network.

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

[0345] The second communication device 410 includes a controller / processor 475, a memory 476, a receiver processor 470, a transmitter processor 416, a multi-antenna receiver processor 472, a multi-antenna transmitter processor 471, a transmitter / receiver 418, and an antenna 420.

[0346] In the 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 L2 layer functionality. In the 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 retransmitting 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). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 471 into an radio frequency stream, which is then provided to different antennas 420.

[0347] 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 radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 456. The receiver processor 456 and the multi-antenna receiver processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 454. The receiver processor 456 uses a Fast Fourier Transform (FFT) to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations 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 receiver processor 456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 458 after multi-antenna detection to recover any spatial stream destined for the first communication device 450. Symbols on each spatial stream are demodulated and recovered in the receive processor 456, generating soft decisions. The receive 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 over 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 Layer 2. The controller / processor 459 may be associated with a memory 460 storing program code and data. The memory 460 may be referred to as computer-readable media. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover upper-layer data packets from the core network. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.

[0348] 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 functions 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, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmitting lost packets and signaling to the second communication device 410. Transmit processor 468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 457, the stream is provided to different antennas 452 via transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by multi-antenna transmit processor 457 into a radio frequency symbol stream before providing it to antenna 452.

[0349] 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 receiving 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 radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 472 and the receiving processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the L1 layer functions. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as computer-readable media. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between the transmission and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper-layer data packets from the UE 450. Upper-layer packets from the controller / processor 475 can be provided to the core network.

[0350] As one 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 with the at least one processor, and the first communication device 450 at least: receives first information, second information, and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is an uplink frequency domain configuration of at least one uplink sub-interval for the first cell; wherein the at least one first downlink sub-interval and the at least one uplink sub-interval are both on unpaired spectrum; and whether there exists a center frequency of one of the at least one uplink sub-intervals that is... The fact that the center frequencies of the first downlink sub-intervals are the same depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; wherein, the first cell is configured with at most one anchor carrier, and the first cell is configured with at most multiple non-anchor carriers; or, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0351] As one embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving first information, second information, and third information, wherein the first information indicates at least one carrier for a first cell, the second information configures at least one first downlink sub-interval in the downlink frequency domain of the first cell, and the third information configures at least one uplink sub-interval in the uplink frequency domain of the first cell; wherein the at least first downlink sub-interval and the at least one uplink sub-interval are both on unpaired spectrum; whether there exists a center frequency of the at least one uplink sub-interval that is the same as the center frequency of the first downlink sub-interval depends on... Whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; wherein, the first cell is configured with at most one anchor carrier, and the first cell is configured with at most multiple non-anchor carriers; or, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0352] As one 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 with the at least one processor. The second communication device 410 at least: transmits first information, second information, and third information, wherein the first information indicates at least one carrier for a first cell, the second information configures at least one first downlink sub-interval in the downlink frequency domain of the first cell, and the third information configures at least one uplink sub-interval in the uplink frequency domain of the first cell; wherein the at least first downlink sub-interval and the at least one uplink sub-interval are both on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first... The downlink sub-interval is on the anchor carrier of the first cell, and one of the at least one uplink sub-intervals has the same center frequency as the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether one of the at least one uplink sub-intervals has the same center frequency as the first downlink sub-interval depends on the configuration of the second information and the third information; wherein, the first cell is configured with at most one anchor carrier, and the first cell is configured with at most multiple non-anchor carriers; or, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0353] As one embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: transmitting first information, second information, and third information, wherein the first information indicates at least one carrier for a first cell, the second information configures at least one first downlink sub-interval in the downlink frequency domain of the first cell, and the third information configures at least one uplink sub-interval in the uplink frequency domain of the first cell; wherein the at least first downlink sub-interval and the at least one uplink sub-interval are both on unpaired spectrum; whether there exists a center frequency of the at least one uplink sub-interval that is the same as the center frequency of the first downlink sub-interval depends on... Whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; wherein, the first cell is configured with at most one anchor carrier, and the first cell is configured with at most multiple non-anchor carriers; or, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0354] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive first information, second information, and third information; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the first information, the second information, and the third information.

[0355] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive the first signaling; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the first signaling.

[0356] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive the second signaling; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the second signaling.

[0357] As one embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive PDSCH on the first time-frequency resource block; at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to transmit PDSCH on the first time-frequency resource block.

[0358] As one embodiment, at least one of the antenna 452, the transmitter 454, the transmitter processor 468, and the controller / processor 459 is used to transmit PUSCH on the first time-frequency resource block; at least one of the antenna 420, the receiver 418, the receiver processor 470, and the controller / processor 475 is used to receive PUSCH on the first time-frequency resource block.

[0359] As an example, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to perform the first operation.

[0360] As an example, at least one of the antenna 452, the transmitter 454, the transmitter processor 468, and the controller / processor 459 is used to perform the second operation.

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

[0362] As an example, the first node in this application includes the first communication device 450.

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

[0364] As an example, the second node in this application includes the second communication device 410.

[0365] As one embodiment, the first communication device 450 includes a user equipment.

[0366] As one embodiment, the first communication device 450 includes a relay device.

[0367] As an example, the first communication device 450 is a user equipment.

[0368] As an example, the first communication device 450 is a terminal.

[0369] As one embodiment, the second communication device 410 includes a base station device.

[0370] As one embodiment, the second communication device 410 includes a relay device.

[0371] As one embodiment, the second communication device 410 is a base station device.

[0372] Example 5

[0373] Example 5 illustrates a wireless signal transmission flowchart according to an embodiment of this application, as shown in the attached diagram. Figure 5 As shown. It should be noted that the order in this example does not limit the order of signal transmission and implementation in this application.

[0374] for First node U01 In step S5101, first information is received; in step S5102, second information is received; and in step S5103, third information is received.

[0375] for Second node N02 In step S5201, the first information is sent; in step S5202, the second information is sent; and in step S5203, the third information is sent.

[0376] In Embodiment 5, the first information indicates at least one carrier for a first cell, the second information configures at least one first downlink sub-interval in the downlink frequency domain of the first cell, and the third information configures at least one uplink sub-interval in the uplink frequency domain of the first cell; wherein, the at least one first downlink sub-interval and the at least one uplink sub-interval are both on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information.

[0377] As an example, the first node U01 includes a UE.

[0378] As an example, the first node U01 is a UE.

[0379] As an example, the first node U01 is a terminal.

[0380] As one embodiment, the first node U01 includes a relay device.

[0381] As one embodiment, the second node N02 includes a base station device.

[0382] As one example, the second node N02 is a base station device.

[0383] As an example, the second node N02 is a relay device.

[0384] Typically, the first node U01 is a UE; the second node N02 is a base station device.

[0385] As an example, the number of carriers included in the at least one carrier does not exceed Q1; Q1 is a positive integer greater than 1.

[0386] As an example, Q1 is predefined.

[0387] As an example, Q1 is determined by the second node itself.

[0388] As an example, before step S5101, the first node sends UE capability information (attached). Figure 5 (Not shown), the UE capability information indicates the Q1.

[0389] As an example, before step S5101, the first node sends UE assistance information (attached). Figure 5 (Not shown), the UE assistance information indicates the Q1.

[0390] As an example, the first cell being configured with a maximum of multiple non-anchor carriers means that the first cell is configured with a maximum of N1 non-anchor carriers, where N1 is an integer greater than 1.

[0391] As an example, N1 is predefined.

[0392] As an example, N1 is determined by the second node itself.

[0393] As an example, the first node sends UE capability information (attached). Figure 5 (Not shown), the UE capability information indicates the N1.

[0394] As an example, the first node sends a UE assistance information (attached) Figure 5 (Not shown), the UE assistance information indicates the N1.

[0395] As one example, the first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers;

[0396] As an example, the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0397] As one embodiment, the first cell may be configured with at most one anchor carrier and at most multiple non-anchor carriers; wherein the anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0398] As an example, steps S5101, S5102, and S5103 are executed simultaneously.

[0399] As an example, step S5101 is performed before step S5101 and step S5101.

[0400] As an example, in step S5101, at least a portion of the first information is received before the time when any of the second information is received in step S5102 and before the time when any of the third information is received in step S5103.

[0401] As an example, the at least first downlink sub-interval includes only the first downlink sub-interval; the first downlink sub-interval is on the anchor carrier of the first cell, and the center frequency of one of the at least one uplink sub-intervals configured by the third information is the same as the center frequency of the first downlink sub-interval configured by the second information.

[0402] As one embodiment, the at least first downlink sub-interval includes a first downlink sub-interval and a second downlink sub-interval, wherein the first downlink sub-interval is on the anchor carrier of the first cell, and the second downlink sub-interval is on a non-anchor carrier of the first cell; wherein, the center frequency of one uplink sub-interval configured by the third information is the same as the center frequency of the first downlink sub-interval configured by the second information, and the center frequency of one uplink sub-interval configured by the third information is the same as the center frequency of the second downlink sub-interval configured by the second information.

[0403] As one embodiment, the at least first downlink sub-interval includes a first downlink sub-interval and a third downlink sub-interval, the first downlink sub-interval being on the anchor carrier of the first cell, and the third downlink sub-interval being on a non-anchor carrier of the first cell; wherein, the center frequency of one of the at least one uplink sub-intervals configured by the third information is the same as the center frequency of the first downlink sub-interval configured by the second information, and the center frequency of any one of the at least one uplink sub-intervals configured by the third information is different from the center frequency of the third downlink sub-interval configured by the second information.

[0404] As one embodiment, the at least first downlink sub-interval includes a first downlink sub-interval, a second downlink sub-interval, and a third downlink sub-interval. The first downlink sub-interval is on the anchor carrier of the first cell, and the second downlink sub-interval and the third downlink sub-interval are on a non-anchor carrier of the first cell. Specifically, the center frequency of one uplink sub-interval configured by the third information is the same as the center frequency of the first downlink sub-interval configured by the second information; the center frequency of one uplink sub-interval configured by the third information is the same as the center frequency of the second downlink sub-interval configured by the second information; and the center frequency of any one uplink sub-interval configured by the third information is different from the center frequency of the third downlink sub-interval configured by the second information.

[0405] Example 6

[0406] Example 6 illustrates a wireless signal transmission flowchart according to another embodiment of this application, as shown in the attached diagram. Figure 6 As shown.

[0407] for First node U01 In step S6101, a first signaling is received, the first signaling indicating a first time-frequency resource block; in step S6102, a PUSCH is sent on the first time-frequency resource block; in step S6103, a PDSCH is received on the first time-frequency resource block.

[0408] for Second node N02 In step S6201, the first signaling is sent; in step S6202, the PUSCH is received on the first time-frequency resource block; in step S6203, the PDSCH is sent on the first time-frequency resource block.

[0409] As an example, step S6101 is performed after receiving the first information, the second information, and the third information.

[0410] As an example, the first signaling is an RRC message.

[0411] As an example, the first signaling includes an RRC message and a MAC CE.

[0412] As an example, the first signaling includes an RRC message and a DCI.

[0413] As an example, the first signaling is a DCI.

[0414] As one embodiment, the DCI includes an FDRA (Frequency Domain Resource Assignment) field, which indicates the frequency domain resources of the first time-frequency resource block. This method can adapt to changes in the number of downlink sub-intervals overlapping with the first time-frequency resource block, especially when the number of downlink sub-intervals overlapping with the first time-frequency resource block is large, thus reducing the overhead of the FDRA field.

[0415] As one embodiment, the DCI includes multiple FDRA fields, which indicate the frequency domain resources of the first time-frequency resource block. This method is simple to implement and is particularly suitable for scenarios where the frequency domain resources of the first time-frequency resource block are discontinuous.

[0416] As an example, the first time-frequency resource block is used for PUSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-interval, and the at least one uplink sub-interval includes multiple uplink sub-intervals.

[0417] As a sub-implementation, the first signaling scheduler is PUSCH.

[0418] As a sub-implementation, the PUSCH carries a TB (Transport Block).

[0419] As a sub-implementation, the PUSCH carries a TB and a retransmission of the TB.

[0420] As a sub-implementation, block F6.1 exists, while block F6.2 does not exist; wherein, the first time-frequency resource block is used for PUSCH.

[0421] As an example, the first time-frequency resource block is used for PDSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-interval, and the at least first downlink sub-interval includes multiple downlink sub-intervals.

[0422] As a sub-implementation, the first signaling scheduler is PDSCH.

[0423] As a sub-implementation, the PDSCH carries a TB.

[0424] As a sub-implementation, the PDSCH carries a TB and a retransmission of the TB.

[0425] As a sub-implementation, block F6.2 exists, while block F6.1 does not exist; wherein, the first time-frequency resource block is used for PDSCH.

[0426] In a specific implementation, the network can allocate frequency domain resources on multiple downlink sub-intervals of multiple carriers to the first time-frequency resource block, or it can allocate frequency domain resources on multiple uplink sub-intervals of multiple carriers to the first time-frequency resource block; or, the network can allocate frequency domain resources on multiple downlink sub-intervals of multiple carriers to the first time-frequency resource block, but it cannot allocate frequency domain resources on multiple downlink sub-intervals of multiple carriers to the first time-frequency resource block.

[0427] Example 7

[0428] Example 7 illustrates a wireless signal transmission flowchart according to yet another embodiment of this application, as shown in the attached diagram. Figure 7 As shown.

[0429] for First node U01 In step S7101, when the first carrier is activated, a first operation is performed for each downlink sub-interval in the at least first downlink sub-interval on the first carrier; in step S7102, when the first carrier is activated, a second operation is performed for each uplink sub-interval in the at least first downlink sub-interval on the first carrier; in step S7103, a second signaling is received, wherein the second signaling indicates deactivation of the first carrier; in step S7104, the first carrier is deactivated; in step S7105, when the first carrier is deactivated, the first operation is not performed for each downlink sub-interval on the first carrier; in step S7106, when the first carrier is deactivated, the second operation is not performed for each uplink sub-interval on the first carrier.

[0430] for Second node N02 In step S7201, the first signaling is sent; in step S7202, the PUSCH is received on the first time-frequency resource block; in step S7203, the PDSCH is sent on the first time-frequency resource block.

[0431] In Example 7, the first operation includes at least one of receiving DL-SCH or listening to PDCCH.

[0432] As an example, step S7101 is performed after receiving the first information, the second information, and the third information.

[0433] As an example, step S7102 is performed after receiving the first information, the second information, and the third information.

[0434] As an example, step S7103 is performed after receiving the first information, the second information, and the third information.

[0435] As an example, when the first carrier is activated, a first operation is performed for each downlink sub-interval of the at least first downlink sub-interval on the first carrier, and a second operation is performed for each uplink sub-interval of the at least first downlink sub-interval on the first carrier; when the first carrier is deactivated, the first operation is not performed for each downlink sub-interval on the first carrier, and the second operation is not performed for each uplink sub-interval on the first carrier.

[0436] As an example, performing the first operation for a downlink sub-interval includes receiving DL-SCH on the downlink sub-interval or listening to PDCCH on the downlink sub-interval, whichever is the former.

[0437] As one embodiment, performing the first operation for a downlink sub-interval includes receiving a DL-SCH on the downlink sub-interval or listening to a PDCCH on the downlink sub-interval, whichever is the latter.

[0438] As an example, performing the first operation for a downlink sub-interval includes receiving DL-SCH on the downlink sub-interval and listening to PDCCH on the downlink sub-interval.

[0439] As an example, performing the second operation for an uplink sub-interval includes transmitting UL-SCH (Uplink Shared Channel) or PUCCH (Physical Uplink Control Channel) on the uplink sub-interval (if the uplink sub-interval is configured with PUCCH) or RACH (Random Access Channel) on the uplink sub-interval (if the uplink sub-interval is configured with PRACH) or SRS (Sounding Reference Signal) on the uplink sub-interval (if the uplink sub-interval is configured with SRS) or reporting CSI (Channel State Information) for the uplink sub-interval.

[0440] As an example, performing the second operation for an uplink sub-interval includes transmitting a UL-SCH on the uplink sub-interval and transmitting a PUCCH on the uplink sub-interval (if the uplink sub-interval is configured with a PUCCH).

[0441] As an example, performing the second operation for an uplink sub-interval includes sending a UL-SCH and reporting a CSI for the uplink sub-interval on the uplink sub-interval.

[0442] As an example, when step S7101 is executed, the first carrier is activated; when step S7105 is executed, the first carrier is deactivated.

[0443] As an example, the dashed box F7.1 exists.

[0444] As a sub-implementation, the second signaling is received before the first carrier is deactivated.

[0445] As a sub-implementation, the second signaling is an RRC signaling. This method avoids overly dynamic carrier activation / deactivation, which helps ensure transmission continuity.

[0446] As a sub-implementation, the second signaling is a MAC CE. This method, through dynamic carrier activation / deactivation, benefits energy saving for both the first and second nodes, and balances signaling overhead and latency.

[0447] As a sub-implementation, the second signaling is a DCI. This method facilitates dynamic carrier activation / deactivation, improves energy efficiency for both the first and second nodes, and reduces latency.

[0448] As a sub-implementation, the receipt of the second signaling triggers the deactivation of the first carrier.

[0449] As a sub-implementation, the first carrier is deactivated in response to the receipt of the second signaling.

[0450] As a sub-implementation, the second signaling indicates the index of the first carrier.

[0451] As a sub-implementation, the second signaling instructs the activation of multiple carriers, where the first carrier is any one of the multiple carriers. This method activates multiple carriers using the same signaling, saving signaling overhead.

[0452] As an example, the dashed box F7.1 does not exist.

[0453] As a sub-implementation, a timer expiration triggers the deactivation of the first carrier.

[0454] As a sub-implementation, the first carrier is deactivated in response to the expiration of the timer.

[0455] As a sub-implementation, the timer expires in the MAC sublayer.

[0456] As a sub-example, the name of the timer includes DeactivationTimer.

[0457] As a sub-example, the timer is a CarrierDeactivationTimer.

[0458] As a sub-example, the value of the timer is configurable.

[0459] As an example, steps S7102 and S7106 are present.

[0460] As an example, when step S7102 is executed, the first carrier is activated; when step S7106 is executed, the first carrier is deactivated.

[0461] As an example, steps S7102 and S7106 are not present.

[0462] As an example, the first carrier is any non-anchor carrier of the first cell.

[0463] As a sub-implementation, the anchor carrier cannot be deactivated.

[0464] As a sub-implementation, the anchor carrier is always active.

[0465] As a sub-implementation, the anchor carrier cannot be activated / deactivated.

[0466] As an example, the first carrier is any carrier other than the anchor carrier of the first cell.

[0467] As an example, the first cell is not a PCell.

[0468] As an example, the first cell is SCell.

[0469] As an example, the first cell is a PSCell or an SCell.

[0470] Example 8

[0471] Example 8 illustrates a flowchart illustrating whether a first operation is performed on a first downlink sub-interval according to an embodiment of this application, as shown in the attached diagram. Figure 8 As shown.

[0472] for First node U01 In step S8101, when the first carrier is deactivated, it is determined whether the first carrier is the anchor carrier of the first cell; if the first carrier is not the anchor carrier of the first cell, proceed to step S8102; if the first carrier is the anchor carrier of the first cell, proceed to step S8103; in step S8102, the first operation is performed for the first downlink sub-interval; in step S8103, the first operation is not performed for the first downlink sub-interval.

[0473] As an example, step S8101 triggers step S8102.

[0474] As an example, step S8101 is performed after receiving the first information, the second information, and the third information.

[0475] As an example, the appendix Figure 7 Step S7104 can replace step S8101.

[0476] As an example, in the appendix Figure 7 After step S7104, step S8102 is executed.

[0477] In embodiment 8, when the first carrier is deactivated, whether the first operation is performed for one of the downlink sub-intervals of the at least first downlink sub-interval depends on whether the first carrier is the anchor carrier of the first cell, and the downlink sub-interval is not on the first carrier;

[0478] Wherein, the statement that whether the first operation is performed on one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell includes:

[0479] If the first carrier is not the anchor carrier of the first cell, the first operation is performed for the downlink sub-interval;

[0480] If the first carrier is the anchor carrier of the first cell, the first operation is not performed for the downlink sub-interval.

[0481] As an example, when the first carrier is deactivated, whether the second operation is performed for one of the at least one uplink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell, and the one uplink sub-interval is not on the first carrier;

[0482] Wherein, the statement that whether the first operation is performed on one of the at least one uplink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell includes:

[0483] If the first carrier is not the anchor carrier of the first cell, the second operation is performed for the one uplink sub-interval;

[0484] If the first carrier is the anchor carrier of the first cell, the second operation is not performed for the one uplink sub-interval.

[0485] In Example 8, when the first carrier is deactivated, the carrier in which the downlink sub-interval is located is not deactivated.

[0486] In Example 8, when the first carrier is deactivated, the carrier in which the uplink sub-interval is located is not deactivated.

[0487] As an example, only the first carrier of the at least one carrier is deactivated.

[0488] As an example, multiple carriers in the at least one carrier are deactivated.

[0489] As an example, the first cell is a SCell.

[0490] As an example, the anchor carrier of the first cell can be deactivated only if the first cell is an SCell.

[0491] As a sub-implementation, the anchor carrier on PCell cannot be deactivated.

[0492] As a sub-implementation, the anchor carrier on PSCell cannot be deactivated.

[0493] As an example, the first cell is either a SCell or a PSCell.

[0494] As a sub-implementation, the anchor carrier of the first cell can be deactivated only if the first cell is an SCell or a PSCell.

[0495] As a sub-implementation, the anchor carrier on PCell cannot be deactivated.

[0496] Example 9

[0497] Example 9 illustrates a schematic diagram illustrating whether, according to an embodiment of this application, there exists an uplink sub-interval whose center frequency is the same as that of the first downlink sub-interval, depending on whether the first downlink sub-interval is on the anchor carrier of the first cell. In the appendix... Figure 9 In the diagram, the vertical axis represents frequency, blank boxes represent carrier waves, boxes filled with vertical lines represent the first downlink sub-interval, and boxes filled with horizontal lines represent uplink sub-intervals with the same center frequency as the first downlink sub-interval.

[0498] In the appendix Figure 9 In (a), the first downlink sub-interval is on the anchor carrier of the first cell, and there is an uplink sub-interval whose center frequency is the same as that of the first downlink sub-interval.

[0499] As an example, the first information is that the first cell indicates only one carrier, and the one carrier is the anchor carrier of the cell.

[0500] As one embodiment, the first information indicates multiple carriers for the first cell, the multiple carriers including the anchor carrier and at least one non-anchor carrier.

[0501] As one embodiment, the second information indicates that the first downlink sub-interval is on the anchor carrier of the first cell.

[0502] In the appendix Figure 9In (b), the first downlink sub-interval is on a non-anchor carrier of the first cell, and one of the at least one uplink sub-intervals has the same center frequency as the first downlink sub-interval.

[0503] As one embodiment, the first information indicates multiple carriers for the first cell, the multiple carriers including the anchor carrier and the non-anchor carrier.

[0504] As an example, the second information indicates that the first downlink sub-interval is on the non-anchor carrier of the first cell.

[0505] In the appendix Figure 9 In (c), the first downlink sub-interval is on a non-anchor carrier of the first cell, and none of the at least one uplink sub-intervals has the same center frequency as the first downlink sub-interval.

[0506] As an example, for the first downlink sub-interval, there is an associated uplink sub-interval in the at least one uplink sub-interval; the first downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0507] As an example, only the downlink sub-interval is configured on the non-anchor carrier.

[0508] As a sub-implementation, only the first downlink sub-interval is configured on the non-anchor carrier.

[0509] As one embodiment, the first information indicates multiple carriers for the first cell, the multiple carriers including the anchor carrier and the non-anchor carrier.

[0510] As an example, the second information indicates that the first downlink sub-interval is on the non-anchor carrier of the first cell.

[0511] It is worth noting that the appendix... Figure 9 The number of carriers in the first cell is not limited. Furthermore, the number of downlink sub-intervals on each carrier is not limited. Furthermore, the number of uplink sub-intervals on each carrier is not limited.

[0512] Example 10

[0513] Example 10 illustrates a schematic diagram of each downlink sub-interval associated with an uplink sub-interval according to an embodiment of this application. In the appendix... Figure 10In the diagram, the vertical axis represents frequency, blank boxes represent carriers, vertically filled boxes represent downlink sub-intervals, and horizontally filled boxes represent uplink sub-intervals. For a downlink sub-interval on the anchor carrier of the first cell, the center frequency of the downlink sub-interval is the same as the center frequency of the associated uplink sub-interval. For a downlink sub-interval on the non-anchor carrier #1 of the first cell, the center frequency of the downlink sub-interval is different from the center frequency of the associated uplink sub-interval. For a downlink sub-interval on the non-anchor carrier #2 of the first cell, the center frequency of the downlink sub-interval is the same as the center frequency of the associated uplink sub-interval.

[0514] In embodiment 10, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there is an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0515] As an example, the number of the plurality of downlink sub-intervals is equal to the number of the at least one uplink sub-interval.

[0516] As one embodiment, the number of the plurality of downlink sub-intervals is no greater than the number of the at least one uplink sub-interval. This method is beneficial for improving uplink capacity.

[0517] As a sub-implementation, the number of the at least one uplink sub-interval can be equal to or greater than the number of the plurality of downlink sub-intervals.

[0518] As a sub-implementation, if the number of the at least one uplink sub-interval is greater than the number of the plurality of downlink sub-intervals, only the uplink sub-interval is configured on at least one non-anchor carrier of the first cell.

[0519] As a sub-example, one of the at least one uplink sub-intervals is not associated with any of the downlink sub-intervals in the at least first downlink sub-interval.

[0520] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, and the center frequency of the uplink sub-interval associated with the first downlink sub-interval is configured to be different from the center frequency of the first downlink sub-interval by the second information and the third information, the uplink sub-interval associated with the first downlink sub-interval does not overlap with the first downlink sub-interval in the frequency domain. This method helps to avoid interference.

[0521] As a sub-implementation, it is stipulated that the uplink sub-interval associated with the first downlink sub-interval does not overlap with the first downlink sub-interval in the frequency domain.

[0522] As a sub-implementation, the first node does not expect the uplink sub-interval associated with the first downlink sub-interval to overlap with the first downlink sub-interval in the frequency domain.

[0523] As a sub-implementation, the network ensures that the uplink sub-interval associated with the first downlink sub-interval does not overlap with the first downlink sub-interval in the frequency domain.

[0524] As an example, if the first downlink sub-interval is not on the anchor carrier of the first cell, and the center frequency of the uplink sub-interval associated with the first downlink sub-interval is configured to be different from the center frequency of the first downlink sub-interval by the second information and the third information, whether the uplink sub-interval associated with the first downlink sub-interval overlaps with the first downlink sub-interval in the frequency domain depends on the configuration of the second information and the third information. This method is beneficial for improving configuration flexibility and spectrum utilization.

[0525] As a sub-implementation, the uplink sub-interval associated with the first downlink sub-interval overlaps with the first downlink sub-interval in the frequency domain (the appended...). Figure 10 (Not shown).

[0526] As a sub-implementation, the uplink sub-interval associated with the first downlink sub-interval does not overlap with the first downlink sub-interval in the frequency domain.

[0527] As an example, the at least one carrier of the first cell includes the anchor carrier and the non-anchor carrier #1.

[0528] As an example, the at least one carrier of the first cell includes the anchor carrier and the non-anchor carrier #2.

[0529] As an example, the at least one carrier of the first cell includes the anchor carrier, non-anchor carrier #1, and non-anchor carrier #2.

[0530] It is worth noting that the appendix... Figure 10 In this context, #1 and #2 merely represent different non-anchor carriers, not carrier indices; furthermore, the attached... Figure 10 The number of carriers in the first cell is not limited. Furthermore, the number of downlink sub-intervals on each carrier is not limited. Furthermore, the number of uplink sub-intervals on each carrier is not limited. Furthermore, the number of the at least one uplink sub-interval is not limited to whether it is the same as the number of the at least one downlink sub-interval.

[0531] Example 11

[0532] Example 11 illustrates a schematic diagram of a non-anchor carrier configured with only downlink sub-intervals or only uplink sub-intervals according to an embodiment of this application, as shown in the attached diagram. Figure 11 As shown. In the appendix Figure 11 In the diagram, the vertical axis represents frequency, blank boxes represent carriers, vertically filled boxes represent downlink sub-intervals, and horizontally filled boxes represent uplink sub-intervals. For a downlink sub-interval on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the downlink sub-interval. Only the uplink sub-interval is configured on the non-anchor carrier #1 of the first cell. Only the downlink sub-interval is configured on the non-anchor carrier #2 of the first cell.

[0533] In Example 11, at least one non-anchor carrier of the first cell is configured with either the downlink sub-interval or the uplink sub-interval.

[0534] As an example, the downlink sub-interval is configured only on at least one non-anchor carrier of the first cell.

[0535] As one embodiment, the at least first downlink sub-interval includes multiple downlink sub-intervals; only the downlink sub-interval is configured on at least one non-anchor carrier of the first cell.

[0536] As an example, the uplink sub-interval is configured only on at least one non-anchor carrier of the first cell.

[0537] As one embodiment, the at least first downlink sub-interval includes only the first downlink sub-interval; the uplink sub-interval is configured only on each non-anchor carrier of the first cell.

[0538] As an example, the downlink sub-interval is configured only on at least one non-anchor carrier of the first cell, and the uplink sub-interval is configured only on at least one non-anchor carrier of the first cell.

[0539] As one embodiment, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; only the downlink sub-interval is configured on at least one non-anchor carrier of the first cell, and only the uplink sub-interval is configured on at least one non-anchor carrier of the first cell.

[0540] As an example, the downlink sub-interval may be configured only on the non-anchor carrier of the first cell, but the uplink sub-interval may not be configured only on the non-anchor carrier of the first cell.

[0541] As a sub-example, the uplink sub-interval configured only is not supported on a non-anchor carrier of the first cell.

[0542] As a sub-implementation, the uplink sub-interval can only be configured if the downlink sub-interval is configured on a non-anchor carrier of the first cell.

[0543] As an example, the uplink sub-interval may be configured only on the non-anchor carrier of the first cell, but the downlink sub-interval may not be configured only on the non-anchor carrier of the first cell.

[0544] As an example, the non-anchor carrier of the first cell may be configured with only one of the downlink sub-intervals or the uplink sub-intervals.

[0545] As an example, both the downlink sub-interval and the uplink sub-interval on a non-anchor carrier of the first cell are configurable.

[0546] As an example, whether the downlink sub-interval is configured on a non-anchor carrier of the first cell depends on the configuration of the second information.

[0547] As an example, whether the uplink sub-interval is configured on a non-anchor carrier of the first cell depends on the configuration of the third information.

[0548] As an example, the uplink sub-interval on a non-anchor carrier of the first cell is configurable.

[0549] As an example, the downlink sub-interval on a non-anchor carrier of the first cell is configurable.

[0550] As an example, the at least one carrier of the first cell includes the anchor carrier and the non-anchor carrier #1.

[0551] As an example, the at least one carrier of the first cell includes the anchor carrier and the non-anchor carrier #2.

[0552] As an example, the at least one carrier of the first cell includes the anchor carrier, non-anchor carrier #1, and non-anchor carrier #2.

[0553] It is worth noting that the appendix... Figure 11 In this context, #1 and #2 merely represent different non-anchor carriers, not carrier indices; furthermore, the attached... Figure 11 The number of carriers in the first cell is not limited. Furthermore, the number of downlink sub-intervals on each carrier is not limited. Furthermore, the number of uplink sub-intervals on each carrier is not limited. Furthermore, the specific configuration of the uplink and downlink sub-intervals on each carrier is not limited.

[0554] Example 12

[0555] Example 12 illustrates a schematic diagram of the frequency domain identifier of a downlink sub-interval and the frequency domain identifier of the downlink sub-interval according to an embodiment of this application, as shown in the attached diagram. Figure 12 As shown. In the appendix Figure 12 In this configuration, downlink sub-interval #1 is configured with frequency domain identifier #11, and downlink sub-interval #2 is configured with frequency domain identifier #12; uplink sub-interval #1 is configured with frequency domain identifier #21, and downlink sub-interval #2 is configured with frequency domain identifier #22; frequency domain identifier #11 and frequency domain identifier #21 are equal, and the center frequency of downlink sub-interval #1 is the same as the center frequency of uplink sub-interval #1; frequency domain identifier #12 and frequency domain identifier #22 are not equal, and the center frequency of downlink sub-interval #2 is different from the center frequency of uplink sub-interval #2.

[0556] In Embodiment 12, the second information configures a frequency domain identifier for each downlink sub-interval in the at least first downlink sub-interval; the third information configures a frequency domain identifier for each uplink sub-interval in the at least one uplink sub-interval; if the frequency domain identifier of one uplink sub-interval in the at least one uplink sub-interval is equal to the frequency domain identifier of one downlink sub-interval in the at least first downlink sub-interval, the center frequency of the uplink sub-interval is the same as the center frequency of the downlink sub-interval.

[0557] As an example, the frequency domain identifier of the downlink sub-interval is an integer that is not less than 0 and not greater than M1; wherein, M1 is an integer greater than 1.

[0558] As an example, the frequency domain identifier of the uplink sub-interval is an integer that is not less than 0 and not greater than M2; wherein, M2 is an integer greater than 1.

[0559] As an example, M1 and M2 are equal.

[0560] As an example, M1 and M2 are not equal.

[0561] As one embodiment, the at least first downlink sub-interval includes multiple downlink sub-intervals, and the frequency domain identifiers of any two downlink sub-intervals in the at least first downlink sub-interval are not equal.

[0562] As an example, the at least one uplink sub-interval includes multiple uplink sub-intervals, and the frequency domain identifiers of any two uplink sub-intervals are not equal.

[0563] As one embodiment, the second information indicates the frequency domain identifier of each downlink sub-interval in the at least first downlink sub-interval; the third information indicates the frequency domain identifier of each uplink sub-interval in the at least one uplink sub-interval.

[0564] As an example, if the frequency domain identifier of one of the at least one uplink sub-intervals is equal to the frequency domain identifier of one of the at least one first downlink sub-intervals, the first node does not expect the center frequency of the one uplink sub-interval to be configured differently from the center frequency of the one downlink sub-interval.

[0565] As an example, if the frequency domain identifier of one of the at least one uplink sub-intervals is equal to the frequency domain identifier of one of the at least one first downlink sub-intervals, the network guarantees that the center frequency of the uplink sub-interval is the same as the center frequency of the downlink sub-interval.

[0566] As an example, each downlink sub-interval in the at least first downlink sub-interval is a DL BWP, and the frequency domain identifier of the downlink sub-interval is the identifier of the DL BWP; each uplink sub-interval in the at least one uplink sub-interval is a UL BWP, and the frequency domain identifier of the uplink sub-interval is the identifier of the UL BWP.

[0567] As an example, the at least first downlink sub-interval belongs to a DL BWP, and the at least one uplink sub-interval belongs to a UL BWP.

[0568] As an example, only the downlink sub-interval is configured on at least one non-anchor carrier of the first cell; the frequency domain identifier of the only configured downlink sub-interval is different from the frequency domain identifier of any of the at least one uplink sub-interval.

[0569] As an example, only the uplink sub-interval is configured on at least one non-anchor carrier of the first cell; the frequency domain identifier of the only configured uplink sub-interval is different from the frequency domain identifier of any downlink sub-interval in the at least first downlink sub-interval.

[0570] As one embodiment, the second information configures a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information configures a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

[0571] As an example, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there is an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier; the frequency domain identifier of each downlink sub-interval is equal to the frequency domain identifier of the associated uplink sub-interval.

[0572] It is worth noting that the appendix... Figure 12 In this context, #11, #12, #21, and #22 represent different frequency domain identifiers, not their values; #1 and #2 represent different uplink and downlink sub-intervals, not their indices; furthermore, the appended... Figure 12 There is no limit to the number of uplink sub-intervals and frequency domain identifiers, nor is there a limit to the number of downlink sub-intervals and frequency domain identifiers.

[0573] Example 13

[0574] Example 13 illustrates a schematic diagram of a first frequency domain interval identifier and a second frequency domain interval identifier according to an embodiment of this application, as shown in the attached diagram. Figure 13 As shown.

[0575] In embodiment 13, the second information is to configure a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information is to configure a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

[0576] As an example, the first frequency domain interval identifier is a non-negative integer.

[0577] As a sub-implementation, the first frequency domain interval identifier is a non-negative integer not greater than P1; where P1 is an integer greater than 1.

[0578] As an example, the first frequency domain interval identifier is a positive integer.

[0579] As a sub-implementation, the first frequency domain interval identifier is a positive integer not greater than P1; P1 is an integer greater than 1.

[0580] As a sub-implementation, the frequency domain interval identifier 0 is reserved.

[0581] As a sub-implementation, the frequency domain interval identifier 0 is not used.

[0582] As a sub-implementation, the frequency domain interval identifier 0 is not configured for the at least first downlink sub-interval.

[0583] As an example, the second frequency domain interval identifier is a non-negative integer.

[0584] As a sub-implementation, the second frequency domain interval identifier is a non-negative integer not greater than P2; where P2 is an integer greater than 1.

[0585] As an example, the second frequency domain interval identifier is a positive integer.

[0586] As a sub-implementation, the second frequency domain interval identifier is a positive integer not greater than P2; where P2 is an integer greater than 1.

[0587] As a sub-implementation, the frequency domain interval identifier 0 is reserved.

[0588] As a sub-implementation, the frequency domain interval identifier 0 is not used.

[0589] As a sub-implementation, the frequency domain interval identifier 0 is not configured for the at least one uplink sub-interval.

[0590] As an example, P1 and P2 are equal.

[0591] As an example, P1 and P2 are not equal.

[0592] As an example, the at least first downlink sub-interval is linked with the at least one uplink sub-interval.

[0593] As an example, if a downlink sub-interval has the same identifier as an uplink sub-interval, the downlink sub-interval is associated with the uplink sub-interval.

[0594] As one embodiment, the at least first downlink sub-interval is paired with the at least one uplink sub-interval.

[0595] As an example, if a downlink sub-interval has the same identifier as an uplink sub-interval, the downlink sub-interval is paired with the uplink sub-interval.

[0596] As an example, the BWP switching is common for the at least first downlink sub-interval and the at least one uplink sub-interval; wherein the at least first downlink sub-interval belongs to a DL BWP and the at least one uplink sub-interval belongs to a UL BWP.

[0597] As an example, if the identifier of a downlink sub-interval is equal to that of an uplink sub-interval, the BWP handover is common to both the downlink and uplink sub-intervals.

[0598] It is worth noting that the appendix... Figure 13 There is no limit to the number of downlink sub-intervals that are configured with the first frequency domain interval identifier, nor is there a limit to the number of uplink sub-intervals that are configured with the second frequency domain interval identifier.

[0599] Example 14

[0600] Example 14 illustrates a schematic diagram according to an embodiment of this application, showing that at least a first downlink sub-interval belongs to a DL BWP and the at least one uplink sub-interval belongs to a UL BWP, as shown in the attached diagram. Figure 14 As shown.

[0601] In Example 14, the at least first downlink sub-interval belongs to a DL BWP, and the at least one uplink sub-interval belongs to a UL BWP.

[0602] As an example, the at least first downlink sub-interval is the DL BWP, and the at least one uplink sub-interval is the UL BWP.

[0603] As an example, the at least first downlink sub-interval is at least a portion of the RB of the DL BWP, and the at least one uplink sub-interval is at least a portion of the RB of the UL BWP.

[0604] As one embodiment, the second information configures a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information configures a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier; wherein, the first frequency domain interval identifier is the identifier of the DL BWP; and the second frequency domain interval identifier is the identifier of the UL BWP.

[0605] As a sub-implementation, the first frequency domain interval identifier is a positive integer not greater than P1; P1 is an integer greater than 1; the second frequency domain interval identifier is a positive integer not greater than P2; P2 is an integer greater than 1.

[0606] As a sub-implementation, the at least first downlink sub-interval is not initialBWP; the frequency domain interval identifier 0 is used for initialBWP.

[0607] As a sub-implementation, the at least one uplink sub-interval is not initialBWP; the frequency domain interval identifier 0 is used for initialBWP.

[0608] As a sub-example, P1 and P2 are equal.

[0609] As a sub-example, P1 is maxNrofBWPs, and P2 is maxNrofBWPs.

[0610] As a sub-example, P1 and P2 are not equal.

[0611] As a sub-implementation, the second information includes a BWP-Downlink IE, which configures the first frequency domain interval identifier.

[0612] As a sub-implementation, the second information includes a BWP-Id field, which configures the first frequency domain interval identifier.

[0613] As a sub-implementation, the third information includes a BWP-Uplink IE, which configures the second frequency domain interval identifier.

[0614] As a sub-implementation, the third information includes a BWP-Id field, which configures the second frequency domain interval identifier.

[0615] As one embodiment, the second information includes a BWP-Downlink IE, which configures the at least first downlink sub-interval for the downlink frequency domain of the first cell.

[0616] As one embodiment, the second information includes a BWP-DownlinkCommon IE, which configures the at least first downlink sub-interval for the downlink frequency domain of the first cell.

[0617] As one embodiment, the second information includes a BWP IE, which configures the at least first downlink sub-interval for the downlink frequency domain of the first cell.

[0618] As an example, the third information includes a BWP-Uplink IE, which configures the at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0619] As an example, the third information includes a BWP-UplinkCommon IE, which configures the at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0620] As an example, the third information includes a BWP IE, which configures the at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0621] Example 15

[0622] Example 15 illustrates a schematic diagram of at least a first downlink sub-interval of an embodiment of this application, as shown in the attached diagram. Figure 15 As shown. In the appendix Figure 15 In the carrier #1, downlink sub-interval #1 is composed of i consecutive RBs (j to j+i-1); carrier #2 is composed of ki consecutive RBs (j+i to +k-1).

[0623] In embodiment 15, the at least first downlink sub-interval is a plurality of downlink sub-intervals, and each downlink sub-interval in the at least first downlink sub-interval consists of at least one consecutive RB (Resource Block); wherein, the indices of the RBs of any two adjacent downlink sub-intervals in the at least first downlink sub-interval are consecutive.

[0624] As an example, the index of any RB is a non-negative integer.

[0625] As a sub-implementation, the index of an RB can be any one of a positive integer or 0.

[0626] As a sub-example, the RB with index 0 is the RB with the lowest frequency in the at least one downlink sub-interval.

[0627] As a sub-example, the RB with index 0 is on the carrier with the lowest frequency.

[0628] As a sub-example, the RB with index 0 is located in the lowest frequency downlink sub-interval in the at least first downlink sub-interval.

[0629] As a sub-example, the RB with index 0 is on the anchor carrier.

[0630] As a sub-example, the RB with index 0 is in the downlink sub-interval on the anchor carrier in the at least first downlink sub-interval.

[0631] As a sub-example, the RB with index 0 is on the carrier with the smallest index.

[0632] As a sub-example, the RB with index 0 is located in the downlink sub-interval with the smallest frequency domain identifier in the at least first downlink sub-interval.

[0633] As an example, the index of any RB is an integer.

[0634] As a sub-example, the index of an RB can be any one of a positive integer, 0, or a negative integer.

[0635] As a sub-example, the RB with the smallest index is the RB with the lowest frequency in the at least one downlink sub-interval.

[0636] As a sub-implementation, the carrier in which the RB with index 0 is located is configurable.

[0637] As an alternative embodiment, the RB with index 0 can be configured on the anchor carrier or on the non-anchor carrier.

[0638] As a sub-example, the RB with index 0 is on the anchor carrier.

[0639] As a sub-example, the RB with index 0 is in the downlink sub-interval on the anchor carrier in the at least first downlink sub-interval.

[0640] As a sub-example, the RB with index 0 is on the carrier with the smallest index.

[0641] As a sub-example, the RB with index 0 is located in the downlink sub-interval with the smallest frequency domain identifier in the at least first downlink sub-interval.

[0642] As an example, the RB is a PRB (Physical Resource Block).

[0643] As an example, the RB corresponds to a series of consecutive REs (Resource Elements).

[0644] As an example, the larger the index of an RB, the higher the frequency domain corresponding to that RB.

[0645] As one embodiment, each downlink sub-interval on the at least first downlink sub-interval consists of a plurality of RBs.

[0646] As one embodiment, the first time-frequency resource block indicated by the first signaling corresponds to a plurality of consecutive RBs, the plurality of RBs being located on at least two downlink sub-intervals.

[0647] As a sub-implementation, the index of the starting RB of the plurality of RBs is not less than j and not greater than j+i-1, and the index of the ending RB of the plurality of RBs is not less than j+i and not greater than j+k-1.

[0648] As an example, Appendix Figure 15 Only the RB on the at least first downlink sub-interval is shown. For the at least one uplink sub-interval, when the at least one uplink sub-interval includes multiple uplink sub-intervals, a similar approach can be used (replacing the downlink sub-interval with the uplink sub-interval), which will not be elaborated here.

[0649] As a sub-implementation, the first time-frequency resource block indicated by the first signaling corresponds to a plurality of consecutive RBs, the plurality of RBs being located on at least two uplink sub-intervals.

[0650] As a sub-implementation, the index of the starting RB of the plurality of RBs is not less than j and not greater than j+i-1, and the index of the ending RB of the plurality of RBs is not less than j+i and not greater than j+k-1.

[0651] It is worth noting that the appendix... Figure 15 In this context, #1 and #2 simply represent different carriers and are carrier indices; #1 and #2 only represent different downlink sub-intervals, not downlink sub-interval indices; furthermore, the attached... Figure 15 The diagram only shows two downlink sub-intervals on two carriers. In practical applications, the number of downlink sub-intervals is not limited, for example, more than two. Furthermore, in practical applications, it is not limited that the two downlink sub-intervals are on different carriers. For example, downlink sub-interval #1 and downlink sub-interval #2 can be on the same carrier and downlink sub-interval #1 and downlink sub-interval #2 are not contiguous.

[0652] Example 16

[0653] Example 16 illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of this application; as shown in the appendix. Figure 16 As shown. In the appendix Figure 16 In the first node, the processing device 1500 includes a first receiver 1601, a first processor 1602, and a first transmitter 1603.

[0654] The first receiver 1601 receives first information, second information and third information, wherein the first information is a first cell indicating at least one carrier, the second information is a downlink frequency domain configuration of at least a first downlink sub-interval of the first cell, and the third information is an uplink frequency domain configuration of at least one uplink sub-interval of the first cell.

[0655] In Example 16, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information.

[0656] The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers.

[0657] or,

[0658] The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0659] As one embodiment, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there is an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0660] As an example, at least one non-anchor carrier of the first cell is configured with either the downlink sub-interval or only the uplink sub-interval.

[0661] As one embodiment, the second information configures a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information configures a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

[0662] As one embodiment, the first receiver 1601 receives a first signaling, the first signaling indicating a first time-frequency resource block; wherein, the first time-frequency resource block is used for PDSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-intervals, the at least first downlink sub-intervals including multiple downlink sub-intervals; or, the first time-frequency resource block is used for PUSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-intervals, the at least one uplink sub-interval including multiple uplink sub-intervals.

[0663] As an example, the first transmitter 1603 transmits PUSCH on the first time-frequency resource block; the first time-frequency resource block is used for PUSCH.

[0664] As one embodiment, the first receiver 1601 receives PDSCH on the first time-frequency resource block; the first time-frequency resource block is used for PDSCH.

[0665] As one embodiment, the first processor 1602 deactivates the first carrier; wherein, when the first carrier is deactivated, a first operation is not performed for each downlink sub-interval on the first carrier, the first operation including at least one of receiving DL-SCH or listening to PDCCH.

[0666] As one embodiment, when the first carrier is deactivated, whether the first operation is performed for one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell, and the downlink sub-interval is not on the first carrier; wherein, the step of whether the first operation is performed for one of the at least first downlink sub-intervals depending on whether the first carrier is the anchor carrier of the first cell includes: if the first carrier is not the anchor carrier of the first cell, performing the first operation for the downlink sub-interval; if the first carrier is the anchor carrier of the first cell, not performing the first operation for the downlink sub-interval.

[0667] As one embodiment, the first receiver 1601 receives a second signaling before deactivating the first carrier; wherein the second signaling indicates deactivation of the first carrier.

[0668] As one embodiment, the first receiver 1601 includes the appendix to this application. Figure 4 The antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, or data source 467 are at least one of these.

[0669] As one embodiment, the first receiver 1601 includes the appendix to this application. Figure 4 At least antenna 452 and receiver 454 are included.

[0670] As one embodiment, the first transmitter 1602 includes the appendix to this application. Figure 4 The antenna 452 or transmitter 454 or multi-antenna transmitter processor 457 or transmitter processor 468 or controller / processor 459 or memory 460 or data source 467 is at least one of them.

[0671] As one embodiment, the first transmitter 1602 includes the appendix to this application. Figure 4 At least antenna 452 and transmitter 454 are included.

[0672] As an example, the first node includes a UE.

[0673] As one embodiment, the first node includes a relay device.

[0674] As an example, the first node is a UE.

[0675] As an example, the first node is a terminal.

[0676] Example 17

[0677] Example 17 illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of this application; as shown in the appendix. Figure 17 As shown. In the appendix Figure 17 In the second node, the processing device 1700 includes a second transmitter 1701 and a second receiver 1702.

[0678] The second transmitter 1701 transmits first information, second information and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is a configuration of at least one uplink sub-interval for the uplink frequency domain of the first cell.

[0679] In Example 17, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information.

[0680] The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers.

[0681] or,

[0682] The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

[0683] As one embodiment, the at least first downlink sub-interval includes a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there is an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

[0684] As an example, at least one non-anchor carrier of the first cell is configured with either the downlink sub-interval or only the uplink sub-interval.

[0685] As one embodiment, the second information configures a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information configures a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

[0686] As one embodiment, the second transmitter 1701 sends a first signaling instruction, the first signaling instruction indicating a first time-frequency resource block; wherein, the first time-frequency resource block is used for PDSCH, the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-intervals, the at least first downlink sub-intervals including multiple downlink sub-intervals; or, the first time-frequency resource block is used for PUSCH, the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-intervals, the at least one uplink sub-interval including multiple uplink sub-intervals.

[0687] As one embodiment, the second receiver 1702 receives PUSCH on the first time-frequency resource block; the first time-frequency resource block is used for PUSCH.

[0688] As one embodiment, the second transmitter 1701 transmits PDSCH on the first time-frequency resource block; the first time-frequency resource block is used for PDSCH.

[0689] As one embodiment, the second transmitter 1701 sends a second signaling instruction; wherein the second signaling instruction indicates deactivation of the first carrier; when the first carrier is deactivated, the receiver of the second information does not perform a first operation for each downlink sub-interval on the first carrier, the first operation including at least one of receiving DL-SCH or listening to PDCCH.

[0690] As one embodiment, when the first carrier is deactivated, whether the receiver of the second information performs the first operation for one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell, and the downlink sub-interval is not on the first carrier; wherein, whether the receiver of the second information performs the first operation for one of the at least first downlink sub-intervals depending on whether the first carrier is the anchor carrier of the first cell includes: if the first carrier is not the anchor carrier of the first cell, the receiver of the second information performs the first operation for the downlink sub-interval; if the first carrier is the anchor carrier of the first cell, the receiver of the second information does not perform the first operation for the downlink sub-interval.

[0691] As one embodiment, the second transmitter 1701 includes the appendix to this application. Figure 4 The antenna 420, transmitter 418, multi-antenna transmitter processor 471, transmitter processor 416, controller / processor 475, or memory 476 are at least one of them.

[0692] As one embodiment, the second transmitter 1701 includes the appendix to this application. Figure 4 At least antenna 420 and transmitter 418 are included.

[0693] As one embodiment, the second receiver 1702 includes the appendix to this application. Figure 4 The antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, or memory 476 are at least one of them.

[0694] As one embodiment, the second receiver 1702 includes the appendix to this application. Figure 4 At least antenna 420 and receiver 418 are included.

[0695] As one example, the second node is a base station device.

[0696] As one embodiment, the second node includes a base station device.

[0697] As one embodiment, the second node includes a relay device.

[0698] Example 18

[0699] Example 18 illustrates a schematic diagram of TDD operation according to one embodiment of this application. In the appendix... Figure 18In the diagram, the horizontal axis represents time, the vertical axis represents frequency, the vertically filled boxes represent downlink sub-intervals, and the horizontally filled boxes represent uplink sub-intervals. For a downlink sub-interval on the anchor carrier of the first cell, the center frequency of the downlink sub-interval is the same as the center frequency of the associated uplink sub-interval. Only uplink sub-intervals are configured on the non-anchor carrier #1. Only downlink sub-intervals are configured on the non-anchor carrier #2. The center frequency of a downlink sub-interval on the non-anchor carrier #3 is different from the center frequency of the associated uplink sub-interval. The center frequency of a downlink sub-interval on the non-anchor carrier #4 is the same as the center frequency of the associated uplink sub-interval. D represents downlink transmission time, and U represents uplink transmission time.

[0700] In Example 18, the first node is configured with the TDD configuration of the first cell.

[0701] As an example, the first node operates in TDD.

[0702] As an example, the first node receives a signaling instruction indicating the TDD configuration of the first cell.

[0703] As a sub-implementation, the signaling is a ServingCellConfigCommon.

[0704] As a sub-implementation, the signaling is a TDD-UL-DL-ConfigDedicated.

[0705] As a sub-implementation, the signaling is a ServingCellConfigCommon.

[0706] As a sub-implementation, the signaling is a ServingCellConfig.

[0707] As one embodiment, the first cell includes the attached Figure 18 The anchor carrier, and only one of the non-anchor carrier #1, the non-anchor carrier #2, the non-anchor carrier #3, and the non-anchor carrier #4.

[0708] As one embodiment, the first cell includes the attached Figure 18 The anchor carrier in the above, and only two of the non-anchor carrier #1, the non-anchor carrier #2, the non-anchor carrier #3, and the non-anchor carrier #4 exist.

[0709] As one embodiment, the first cell includes the attached Figure 18The anchor carrier, and only three of the non-anchor carriers #1, #2, #3, and #4 exist.

[0710] As one embodiment, the first cell includes the attached Figure 18 The anchor carrier, as well as the non-anchor carrier #1, the non-anchor carrier #2, the non-anchor carrier #3, and the non-anchor carrier #4, all exist.

[0711] It is worth noting that the appendix... Figure 18 There are no restrictions on the ratio of uplink and downlink times, the number of non-anchor carriers, the frequencies of anchor and non-anchor carriers, or the bandwidth of each downlink sub-interval and each uplink sub-interval. Furthermore, the appendix... Figure 18 There are also restrictions on flexible symbols, guard intervals, and uplink / downlink switching times (not shown).

[0712] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, laptops, vehicle-mounted communication devices, wireless sensors, internet cards, IoT terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablets, and other wireless communication devices. The base stations or system equipment 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), TRP (Transmitter Receiver Point), and other wireless communication equipment.

[0713] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A first node used for wireless communication, characterized in that, include: A first receiver receives first information, second information, and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is a configuration of at least one uplink sub-interval for the uplink frequency domain of the first cell. Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers. or, The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

2. The first node according to claim 1, characterized in that, The at least first downlink sub-interval includes a plurality of downlink sub-intervals; for each of the plurality of downlink sub-intervals, there is an associated uplink sub-interval in the at least one uplink sub-interval; each downlink sub-interval and the associated uplink sub-interval are on the same carrier.

3. The first node according to claim 1, characterized in that, The first cell has at least one non-anchor carrier configured with either the downlink sub-interval or the uplink sub-interval.

4. The first node according to any one of claims 1 to 3, characterized in that, The second information configures a first frequency domain interval identifier for the at least first downlink sub-interval, and the third information configures a second frequency domain interval identifier for the at least one uplink sub-interval; the first frequency domain interval identifier is equal to the second frequency domain interval identifier.

5. The first node according to any one of claims 1 to 4, characterized in that, include: The first receiver receives a first signaling instruction, which indicates a first time-frequency resource block; Wherein, the first time-frequency resource block is used for PDSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two downlink sub-intervals in the at least first downlink sub-interval, and the at least first downlink sub-interval includes multiple downlink sub-intervals; or, The first time-frequency resource block is used for PUSCH, and the frequency domain resources of the first time-frequency resource block belong to at least two uplink sub-intervals in the at least one uplink sub-interval, and the at least one uplink sub-interval includes multiple uplink sub-intervals.

6. The first node according to any one of claims 1 to 5, characterized in that, include: The first processor deactivates the first carrier. When the first carrier is deactivated, the first operation is not performed for each downlink sub-interval on the first carrier. The first operation includes at least one of receiving DL-SCH or listening to PDCCH.

7. The first node according to claim 6, characterized in that, When the first carrier is deactivated, whether the first operation is performed for one of the downlink sub-intervals of the at least first downlink sub-interval depends on whether the first carrier is the anchor carrier of the first cell, and the downlink sub-interval is not on the first carrier; Wherein, the statement that whether the first operation is performed on one of the at least first downlink sub-intervals depends on whether the first carrier is the anchor carrier of the first cell includes: If the first carrier is not the anchor carrier of the first cell, the first operation is performed for the downlink sub-interval; If the first carrier is the anchor carrier of the first cell, the first operation is not performed for the downlink sub-interval.

8. A method used in a first node of wireless communication, characterized in that, include: Receive first information, second information and third information, wherein the first information is a first cell indicating at least one carrier, the second information is a downlink frequency domain configuration of at least a first downlink sub-interval of the first cell, and the third information is an uplink frequency domain configuration of at least one uplink sub-interval of the first cell; Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers. or, The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

9. A second node used for wireless communication, characterized in that, include: The second transmitter transmits first information, second information, and third information, wherein the first information is an indication of at least one carrier for a first cell, the second information is a downlink frequency domain configuration of at least one first downlink sub-interval for the first cell, and the third information is a configuration of at least one uplink sub-interval for the uplink frequency domain of the first cell. Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers. or, The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

10. A method used in a second node of wireless communication, characterized in that, include: Send a first message, a second message, and a third message, wherein the first message indicates at least one carrier for a first cell, the second message configures at least a first downlink sub-interval in the downlink frequency domain of the first cell, and the third message configures at least one uplink sub-interval in the uplink frequency domain of the first cell. Wherein, both the at least first downlink sub-interval and the at least one uplink sub-interval are on unpaired spectrum; whether the center frequency of one of the at least one uplink sub-intervals is the same as the center frequency of the first downlink sub-interval depends on whether the first downlink sub-interval is on the anchor carrier of the first cell; if the first downlink sub-interval is on the anchor carrier of the first cell, the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval; if the first downlink sub-interval is not on the anchor carrier of the first cell, whether the center frequency of one of the at least one uplink sub-interval is the same as the center frequency of the first downlink sub-interval depends on the configuration of the second information and the third information; The first cell may be configured with at most one anchor carrier, and the first cell may be configured with at most multiple non-anchor carriers. or, The anchor carrier is used to carry at least one of SIB1 and broadcast synchronization signals.

Images