Resource allocation method, device and equipment

Abstract

Provided are a resource allocation method, apparatus and device, the method comprising: sending BWP frequency domain resource configuration information to a user equipment, the BWP frequency domain resource configuration information comprising a mapping relationship between a resource identifier and an SBFD frequency domain resource, the resource identifier comprising a BWP identifier and a carrier identifier; target BWP indication information is sent to the user equipment, so that the user equipment obtains a target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table, the target BWP configuration pair comprises a target BWP identifier and a target carrier identifier, and the SBFD frequency domain resource is configured based on the mapping relation between the resource identifier and the SBFD frequency domain resource. Determining a target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; the BWP activation configuration table comprises a mapping relation between the BWP indication information and the BWP configuration pair. According to the technical scheme, the resource utilization rate is increased.

Description

Resource allocation method, device and equipment Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a resource allocation method, apparatus, and device. Background Art

[0002] TDD (Time Division Duplex) systems are widely used in mobile communication systems, such as 5G systems.

[0003] In a TDD system, the frame structure is divided into DL (DownLink) slots, UL (UpLink) slots, and S (Special) slots. A DL slot includes multiple DL symbols, and downlink data is processed in the frequency domain resources corresponding to these DL symbols. A UL slot includes multiple UL symbols, and uplink data is processed in the frequency domain resources corresponding to these UL symbols. An F slot includes at least one F (Flexible) symbol. An F symbol can be used for DL, i.e., downlink data is processed in the frequency domain resources corresponding to the F symbol. An F symbol can also be used for UL, i.e., uplink data is processed in the frequency domain resources corresponding to the F symbol. An F symbol can also be used for GP (Guard Period), i.e., uplink and downlink switching is protected in the frequency domain resources corresponding to the F symbol.

[0004] The TDD system can operate in HD (Half Duplex) mode, that is, at the same time, the same frequency domain resources can only be used for UL or DL.

[0005] Summary of the Invention

[0006] The present application provides a resource allocation method, applied to a base station, the method comprising:

[0007] Sending BWP frequency domain resource configuration information to the user equipment, where the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier;

[0008] Send target BWP indication information to the user equipment, where the target BWP indication information is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table, where the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and based on a mapping relationship between the resource identifier and the SBFD frequency domain resource, determine the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between BWP indication information and BWP configuration pairs.

[0009] The present application provides a resource allocation method, applied to a user equipment, the method comprising:

[0010] Receive BWP frequency domain resource configuration information sent by the base station, where the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier;

[0011] receiving target BWP indication information sent by the base station, and obtaining a target BWP configuration pair corresponding to the target BWP indication information from the obtained BWP activation configuration table, the target BWP configuration pair including a target BWP identifier and a target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair;

[0012] Based on the mapping relationship between the resource identifier and the SBFD frequency domain resource, the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair is determined.

[0013] The present application provides a resource allocation method, applied to a base station, the method comprising:

[0014] Sending SBFD resource allocation information to a user equipment, where the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers within a carrier group, or SBFD frequency domain resources configured within each of the multiple carriers; wherein, among the SBFD frequency domain resources configured for multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots; and within the SBFD frequency domain resources configured within each of the multiple carriers, at least one set of opposite time slots exists within the carrier; wherein the opposite time slots include uplink time slots and downlink time slots;

[0015] Sending SBFD configuration information corresponding to the carrier to the user equipment; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or ineffective.

[0016] The present application provides a resource allocation method, applied to a user equipment, the method comprising:

[0017] Receive SBFD resource allocation information sent by a base station, where the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers within a carrier group, or SBFD frequency domain resources configured within each of the multiple carriers; wherein, among the SBFD frequency domain resources configured for multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots; and wherein, among the SBFD frequency domain resources configured within each of the multiple carriers, the carrier has at least one set of opposite time slots; wherein the opposite time slots include uplink time slots and downlink time slots;

[0018] Receive SBFD configuration information corresponding to a carrier sent by the base station; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or ineffective.

[0019] The present application provides a resource allocation device, applied to a base station, the device comprising:

[0020] Acquisition module, used to obtain BWP frequency domain resource configuration information;

[0021] A sending module, configured to send BWP frequency domain resource configuration information to a user equipment, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier;

[0022] The sending module is further used to send target BWP indication information to the user equipment, where the target BWP indication information is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table, where the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and based on a mapping relationship between the resource identifier and the SBFD frequency domain resource, determines the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between BWP indication information and BWP configuration pairs.

[0023] The present application provides a resource allocation device, applied to a user equipment, the device comprising:

[0024] A receiving module, configured to receive BWP frequency domain resource configuration information sent by a base station, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier;

[0025] The receiving module is further configured to receive target BWP indication information sent by the base station;

[0026] an acquisition module, configured to acquire a target BWP configuration pair corresponding to the target BWP indication information from the acquired BWP activation configuration table, the target BWP configuration pair including a target BWP identifier and a target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair;

[0027] The determining module is configured to determine, based on a mapping relationship between the resource identifier and the SBFD frequency domain resource, a target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair.

[0028] The present application provides a resource allocation device, applied to a base station, the device comprising:

[0029] An acquisition module is used to obtain SBFD resource allocation information;

[0030] a sending module, configured to send SBFD resource allocation information to a user equipment, where the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers within a carrier group, or SBFD frequency domain resources configured within each of the multiple carriers; wherein, among the SBFD frequency domain resources configured for multiple carriers within a carrier group, different carriers within the carrier group have at least one set of opposite time slots; and within the SBFD frequency domain resources configured within each of the multiple carriers, there is at least one set of opposite time slots within the carrier; wherein the opposite time slots include uplink time slots and downlink time slots;

[0031] The sending module is further configured to send SBFD configuration information corresponding to a carrier to the user equipment; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are effective or ineffective.

[0032] The present application provides a resource allocation device, applied to a user equipment, the device comprising:

[0033] A receiving module, configured to receive SBFD resource allocation information sent by a base station, the SBFD resource allocation information being used to indicate SBFD frequency domain resources configured for multiple carriers within a carrier group, or SBFD frequency domain resources configured within each of the multiple carriers; wherein, among the SBFD frequency domain resources configured for multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots; and within the SBFD frequency domain resources configured within each of the multiple carriers, at least one set of opposite time slots exists within the carrier; wherein the opposite time slots include uplink time slots and downlink time slots;

[0034] The receiving module is further configured to receive SBFD configuration information corresponding to a carrier sent by the base station; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or ineffective;

[0035] The determination module is configured to determine whether the SBFD frequency domain resources on the carrier are effective or ineffective based on the SBFD configuration information corresponding to the carrier.

[0036] The present application provides a base station, comprising: a processor and a machine-readable storage medium, wherein the machine-readable storage medium stores machine-executable instructions that can be executed by the processor; the processor is used to execute the machine-executable instructions to implement the resource allocation method of the above example.

[0037] The present application provides a user equipment, comprising: a processor and a machine-readable storage medium, wherein the machine-readable storage medium stores machine-executable instructions that can be executed by the processor; the processor is used to execute the machine-executable instructions to implement the resource allocation method of the above example.

[0038] As can be seen from the above technical solution, flexible BWP (BandWidth Part) configuration is used in multi-carrier networks. Flexible SBFD (Sub-Band Full Duplex) frequency domain resources (such as downlink and uplink frequency domain resources) are configured for UE (User Equipment) through BWP to support TDD system data transmission, thereby improving resource utilization. This improves network coverage and capacity, increases uplink transmission resources and cell coverage, reduces uplink transmission delay, and increases uplink transmission capacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] FIG1A is a flow chart of a resource allocation method in an example of the present application;

[0040] FIG1B is a flow chart of a resource allocation method in an example of the present application;

[0041] FIG2A is a flow chart of a resource allocation method in an example of the present application;

[0042] FIG2B is a flow chart of a resource allocation method in an example of the present application;

[0043] 3A-3F are schematic diagrams of BWP frequency domain resource configuration in an example of the present application;

[0044] 4A and 4B are schematic diagrams of BWP switching in an example of the present application;

[0045] FIG5A and FIG5B are schematic diagrams of SBFD frequency domain resource allocation in an example of the present application;

[0046] 6A and 6B are schematic diagrams of the structure of a resource allocation device in an example of the present application;

[0047] FIG7A is a schematic diagram of the structure of a base station in an example of the present application;

[0048] FIG7B is a schematic diagram of the structure of a user device in an example of the present application. DETAILED DESCRIPTION

[0049] The terms used in the embodiments of this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms "a," "the," and "the" used in this application and claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.

[0050] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" used may also be interpreted as "at the time of" or "when" or "in response to determining".

[0051] TDD systems can operate in HD mode, meaning that at the same time, the same frequency domain resources can only be used for UL or DL. To make more flexible use of frequency domain resources and improve resource utilization, TDD systems can also operate in FD (Full-Duplex) mode. That is, at the same time, the same frequency domain resources are used for both UL and DL, that is, uplink and downlink data are processed simultaneously on the same frequency domain resources.

[0052] In a TDD system, the frame structure is divided into DL slots, UL slots, and flexible slots (F slots). A DL slot consists of multiple DL symbols, and the frequency domain resources corresponding to these DL symbols process downlink data. A UL slot consists of multiple UL symbols, and the frequency domain resources corresponding to these UL symbols process uplink data. An F slot contains at least one F symbol, which can be used for DL, UL, or general purpose transmission.

[0053] In a TDD system, once the frame structure is determined, the UE can transmit and receive data according to the frame structure. For UEs using HD (Half Duplex) mode, the base station (such as a gNB) schedules the UE to transmit or receive according to the frame structure. For UEs using FD mode, the base station schedules the UE to transmit, receive, or both according to the frame structure. In summary, the base station can configure the frame structure and notify the UE of the frame structure so that the UE is aware of the frame structure and can correctly transmit and receive data.

[0054] From another perspective, after learning the frame structure, the UE can also learn about possible inter-UE interference, and thus use interference cancellation technology to reduce interference and improve communication reliability.

[0055] In one example, for a frame structure primarily used for uplink transmission, more UL time slots are typically configured. This results in fewer DL time slots, limiting the downlink transmission rate and increasing downlink data transmission latency. This increases downlink transmission latency, while also not utilizing downlink services. For a frame structure primarily used for downlink transmission, more DL time slots are typically configured. This results in fewer UL time slots, limiting the uplink transmission rate and increasing uplink data transmission latency. This increases uplink transmission latency, while also not utilizing uplink services.

[0056] The present application proposes a resource allocation method that uses a flexible BWP configuration in multiple carriers, by configuring flexible SBFD frequency domain resources (such as downlink subband resources and uplink subband resources) for the UE in the BWP. For example, it is possible to configure uplink subband resources using downlink time slots or flexible time slots, and transmit uplink data in the uplink subband resources, thereby transmitting uplink data through downlink time slots or flexible time slots, which can improve the uplink transmission rate and reduce the transmission delay of uplink data. In addition, it is also possible to configure downlink subband resources using uplink time slots or flexible time slots, and transmit downlink data in the downlink subband resources, thereby transmitting downlink data through uplink time slots or flexible time slots, which can improve the downlink transmission rate and reduce the transmission delay of downlink data.

[0057] In one example of the present application, a resource allocation method is proposed. The method can be applied to a base station. FIG1A is a flow chart of the resource allocation method. The method may include:

[0058] Step 111: Send BWP frequency domain resource configuration information to the UE. The BWP frequency domain resource configuration information may include a mapping relationship between a resource identifier and a SBFD frequency domain resource. The resource identifier may include a BWP identifier and a carrier identifier, that is, the BWP frequency domain resource configuration information may include a mapping relationship between the BWP identifier and the carrier identifier and the SBFD frequency domain resource.

[0059] Step 112: Send target BWP indication information to the UE. The target BWP indication information is used to enable the UE to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table. The target BWP configuration pair may include a target BWP identifier and a target carrier identifier. Based on a mapping relationship between a resource identifier and an SBFD frequency domain resource, the UE determines a target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier. The BWP activation configuration table may include a mapping relationship between the BWP indication information and the BWP configuration pair.

[0060] In one example of the present application, a resource allocation method is proposed. The method can be applied to a UE. FIG1B is a flow chart of the resource allocation method. The method may include:

[0061] Step 121: Receive BWP frequency domain resource configuration information sent by a base station, where the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource. The resource identifier may include a BWP identifier and a carrier identifier, that is, the BWP frequency domain resource configuration information may include a mapping relationship between the BWP identifier and the carrier identifier and the SBFD frequency domain resource.

[0062] Step 122: Receive target BWP indication information sent by the base station, and obtain a target BWP configuration pair corresponding to the target BWP indication information from the obtained BWP activation configuration table. The target BWP configuration pair may include a target BWP identifier and a target carrier identifier. The BWP activation configuration table may include a mapping relationship between the BWP indication information and the BWP configuration pair.

[0063] Step 123: Based on the mapping relationship between the resource identifier and the SBFD frequency domain resource, determine the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair.

[0064] In one example, with respect to the BWP identifier and carrier identifier in the BWP frequency domain resource configuration information, the BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier. The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier. Alternatively, the uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier. Alternatively, the downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier. Alternatively, the uplink BWP identifier and the downlink BWP identifier both correspond to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier.

[0065] In one example, with respect to the BWP identifier and carrier identifier in the BWP frequency domain resource configuration information, the BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, and the uplink BWP identifier is different from the downlink BWP identifier. The carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier. Alternatively, the BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier, and a second downlink BWP identifier, the first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier. The carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier correspond to the second carrier identifier.

[0066] In one example, an SBFD frequency-domain resource is a frequency-domain resource configured within a carrier indicated by a carrier identifier, and the SBFD frequency-domain resource is a frequency-domain resource corresponding to a BWP identifier. The SBFD frequency-domain resource corresponding to the uplink BWP identifier is different from the SBFD frequency-domain resource corresponding to the downlink BWP identifier, and the size of the SBFD frequency-domain resource corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency-domain resource corresponding to the downlink BWP identifier. The carriers indicated by different carrier identifiers are either SBFD intra-subband carriers or SBFD inter-subband carriers.

[0067] In one example, the base station may also send a BWP activation configuration table to the UE through an RRC (Radio Resource Control) message, and the UE may receive the BWP activation configuration table sent by the base station through the RRC message. Alternatively, the BWP activation configuration table may be pre-configured in the UE through the physical layer, and the UE may obtain the BWP activation configuration table pre-configured in the UE through the physical layer.

[0068] In one example, each BWP configuration pair in the BWP activation configuration table may include a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, and an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier. A target BWP configuration pair may include a target downlink BWP identifier and a target uplink BWP identifier, where the target downlink BWP identifier is the same as or different from the target uplink BWP identifier.

[0069] Furthermore, the target BWP configuration pair may include a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier may be the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

[0070] In one example, each BWP configuration pair in the BWP activation configuration table may include a first configuration sub-pair and a second configuration sub-pair. The first configuration sub-pair may include a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, and a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier. The second configuration sub-pair may include a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, and a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier.

[0071] The target BWP configuration pair may include a target first configuration sub-pair and a target second configuration sub-pair.

[0072] The target first configuration sub-pair may include a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier may be the same as or different from the target first uplink BWP identifier. The target first configuration sub-pair may include a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier may be the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier.

[0073] The target second configuration sub-pair may include a target second downlink BWP identifier and a target second uplink BWP identifier, and the target second downlink BWP identifier may be the same as or different from the target second uplink BWP identifier. The target second configuration sub-pair may include a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, and the carrier identifier corresponding to the target second downlink BWP identifier may be the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

[0074] In an example, the base station may send the BWP activation configuration to the UE via a DCI message (Downlink Control Information), and the UE receives the BWP activation configuration sent by the base station via the DCI message. Alternatively, the base station may send the BWP activation configuration to the UE via a MAC-CE (MAC Control Element) message, and the UE may receive the BWP activation configuration sent by the base station via the MAC-CE message. Alternatively, the base station may send the BWP activation configuration to the UE via an RRC message, and the UE may receive the BWP activation configuration sent by the base station via the RRC message. Of course, the above are just a few examples and are not limiting.

[0075] The BWP activation configuration may include target BWP indication information and a switch flag. If the switch flag is a first value, the UE obtains the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. If the switch flag is not a first value, the UE prohibits obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

[0076] Alternatively, the BWP activation configuration may include target BWP indication information. If the target BWP indication information is a target value, the UE is prohibited from obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. If the target BWP indication information is not a target value, the UE obtains the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

[0077] In one example, if the SBFD frequency domain resources used by the UE change during the BWP switching time, the base station can also obtain updated target BWP indication information corresponding to the changed SBFD frequency domain resources. The base station can send the updated target BWP indication information to the UE, and the UE can receive the updated target BWP indication information. The UE can obtain the target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

[0078] The base station may send the updated BWP activation configuration to the UE via a DCI message, a MAC-CE message, or an RRC message. In this way, the UE may receive the updated BWP activation configuration, which may include updated target BWP indication information.

[0079] As can be seen from the above technical solution, flexible BWP configuration is used on multiple carriers. Flexible SBFD frequency domain resources (such as downlink and uplink frequency domain resources) are configured for UEs through BWP to support TDD system data transmission. This improves resource utilization, network coverage, and network capacity, increases uplink transmission resources and cell coverage, reduces uplink transmission delay, and increases uplink transmission capacity.

[0080] In one example of the present application, a resource allocation method is proposed. The method can be applied to a base station. FIG2A is a flow chart of the resource allocation method. The method may include:

[0081] Step 211: Send SBFD resource allocation information to the UE. The SBFD resource allocation information indicates the SBFD frequency domain resources configured for multiple carriers within the carrier group, or the SBFD frequency domain resources configured for each of the multiple carriers. Among the SBFD frequency domain resources configured for multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots. Among the SBFD frequency domain resources configured for each of the multiple carriers, at least one set of opposite time slots exists within the carrier. Opposite time slots include uplink time slots and downlink time slots, i.e., one is an uplink time slot and the other is a downlink time slot.

[0082] Step 212: Send SBFD configuration information corresponding to the carrier to the UE; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are valid or invalid.

[0083] In one example of the present application, a resource allocation method is proposed. The method can be applied to a UE. FIG2B is a flow chart of the resource allocation method. The method may include:

[0084] Step 221: Receive SBFD resource allocation information sent by a base station. The SBFD resource allocation information indicates SBFD frequency domain resources configured for multiple carriers within a carrier group, or SBFD frequency domain resources configured for each of the multiple carriers. Among the SBFD frequency domain resources configured for the multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots. Among the SBFD frequency domain resources configured for each of the multiple carriers, at least one set of opposite time slots exists within the carrier.

[0085] Step 222: Receive SBFD configuration information corresponding to the carrier sent by the base station; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are valid or invalid.

[0086] In one example, the SBFD resource allocation information is used to indicate the SBFD frequency domain resources configured for multiple carriers within a carrier group, and may include but is not limited to: the SBFD resource allocation information may include a first allocation indication and a second allocation indication. For each carrier in the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as flexible time slots, and the second allocation indication is used to indicate that each flexible time slot is used as an uplink time slot or a downlink time slot. Or,

[0087] The SBFD resource allocation information may include a third allocation indication, and for each carrier in the plurality of carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot. Or,

[0088] The SBFD resource allocation information may include a fourth allocation indication and a fifth allocation indication. For a first carrier among the multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot. For a second carrier other than the first carrier (the second carrier may be one, two, or more than one), the fifth allocation indication is used to indicate an offset between the second carrier and the first carrier. The offset may be a time slot offset and / or a symbol offset.

[0089] In an example, the fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is valid, such as indicating that the offset is valid, or indicating that the offset is not valid.

[0090] In an example, when the base station sends SBFD configuration information corresponding to a carrier to the UE, when the UE receives the SBFD configuration information corresponding to the carrier sent by the base station, for a third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, then the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

[0091] Alternatively, for a third carrier among the multiple carriers, if the SBFD configuration information includes an indication of the failure of the SBFD frequency domain resources on the third carrier, the failure indication is used to indicate that the SBFD frequency domain resources on the third carrier have failed. In this case, the third carrier remains in an activated state, that is, it has not been deactivated. Because the SBFD frequency domain resources on the third carrier have failed, the configuration on the third carrier can be a default configuration (e.g., using a default frame structure of DL time slots and UL time slots), or the configuration on the third carrier can be the same as that of the primary carrier, that is, using the frame structure of the DL time slots and UL time slots of the primary carrier.

[0092] In an example, when the base station sends SBFD configuration information corresponding to a carrier to the UE, when the UE receives the SBFD configuration information corresponding to the carrier sent by the base station, for a fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, then the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

[0093] Alternatively, for the fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication of the fourth carrier, the activation indication is used to activate the fourth carrier. After the fourth carrier is activated, the SBFD frequency domain resources on the fourth carrier take effect directly, that is, after the base station sends SBFD resource allocation information to the UE, if the carrier corresponding to the SBFD resource allocation information is activated, the SBFD frequency domain resources on the carrier take effect directly.

[0094] It can be seen from the above technical solutions that flexible BWP configuration is used in multi-carriers, and flexible SBFD frequency domain resources (such as downlink frequency domain resources and uplink frequency domain resources) are configured for UE through BWP to support data transmission of TDD system, thereby improving resource utilization, improving network coverage and network capacity, increasing uplink transmission resources and cell coverage, reducing uplink transmission delay and increasing uplink transmission capacity.

[0095] The above technical solution of the present application is described below with reference to examples.

[0096] The TDD frame structure can be implemented through a combination of semi-static configuration and dynamic indication. Multiple SFCs (Slot Format Combinations) are defined in high-layer signaling using the SFI (Slot Format Indicator). For example, a base station can select slot formats that meet service requirements and add them to the SFC. Table 1 shows some of the slot formats, where D represents a DL symbol, U represents an UL symbol, and F represents a flexible symbol. Each SFC is identified by a fixed ID and contains one or more slot format types.

[0097] Table 1

[0098] After completing SFI configuration, the base station sends multiple slot format combinations to the UE in an RRC message. After configuring multiple slot format combinations via RRC signaling, the base station notifies the UE of the index of the currently used SFC via periodic PDCCH in DCI format 2_0. After correctly receiving the DCI format 2_0 information, the UE determines the slot format for each slot within a certain period based on the SFC index value. At this point, the base station and UE have completed the frame structure configuration through dynamic indication, enabling uplink and downlink data transmission.

[0099] As for resource allocation, it can be divided into time domain resource allocation and frequency domain resource allocation (taking the resource allocation of the downlink channel as an example). Time domain resource allocation: The Time domain resource assignment field in the DCI indicates the time domain position of the downlink channel. This field has a total of 4 bits, with values ​​of 0-15. Assuming the value is m, then m+1 indicates the row index of the time domain resource allocation table, and the information in this row indicates the time domain resources of the PDSCH. There are two ways of indication: one is to indicate three pieces of information: the time slot offset between the PDSCH and the PDCCH that schedules the PDSCH, the starting symbol of the PDSCH in the time slot, and the symbol length of the PDSCH. The other is to indicate the time slot offset between the PDSCH and the PDCCH that schedules the PDSCH, and a SLIV value. The user equipment calculates the starting symbol and the number of continuous symbols of the PDSCH based on the SLIV value.

[0100] Frequency domain resource allocation: The Frequency domain resource assignment field in the DCI indicates the frequency domain resource allocation for the downlink channel. PDSCH frequency domain resource allocation is divided into Type 0 and Type 1. Type 0 supports non-contiguous resource allocation to obtain frequency diversity gain, while Type 1 supports contiguous resource allocation, which can reduce the number of bits required for this field. DCI format 1_0 supports only Type 1.

[0101] Type 0: For non-contiguous resource allocation, an RBG is a VRB group consisting of P contiguous VRBs, where the number is determined by the higher-layer parameters rbg-Size and the bandwidth. In Type 0, the frequency domain resource assignment acts as a bitmap to indicate which RBGs are allocated to downlink channels. Each bit in the bitmap represents an RBG, with the highest bit corresponding to RBG0. Similarly, a bit set to 1 indicates that the RBG is allocated to a downlink channel, while a bit set to 0 indicates that it is not a downlink channel resource.

[0102] Type 1: The frequency domain resource indication field does not serve as a bitmap, but indicates a RIV (Resource Indicator Value) value, through which the UE calculates the starting RB and the number of occupied RBs.

[0103] In the TDD system, the frame structure is divided into UL time slots, DL time slots and flexible time slots (F time slots) according to time slots. The symbols in the flexible time slots can be configured as UL symbols, DL symbols and F symbols. F symbols can be used for UL, DL or GP. Among them, uplink data can be transmitted in the UL time slot, UL symbols or F symbols in the flexible time slot. Uplink data cannot be transmitted in the DL time slot, nor can it be transmitted in the DL symbols in the flexible time slot. Downlink data can be transmitted in the DL time slot, DL symbols or F symbols in the flexible time slot. Downlink data cannot be transmitted in the UL time slot, nor can it be transmitted in the UL symbols in the flexible time slot.

[0104] Full-duplex communication is achieved through SBFD. SBFD subband resources (frequency domain resources) are configured within the BWP. These subband resources include uplink and downlink subband resources. At the same time, data in different directions is transmitted using these SBFD subband resources. For example, SBFD subband resources are configured within the BWP of a DL time slot, and uplink data is transmitted using these SBFD subband resources, allowing uplink data to be transmitted within the DL time slot. SBFD subband resources are configured within the BWP of a DL symbol within a flexible time slot, and uplink data is transmitted using these SBFD subband resources, allowing uplink data to be transmitted within the DL symbol within the flexible time slot.

[0105] SBFD subband resources are configured in the BWP of the UL timeslot, and downlink data is transmitted through the SBFD subband resources. Downlink data is transmitted in the UL timeslot. SBFD subband resources are configured in the BWP of the UL symbol of the flexible timeslot, and downlink data is transmitted through the SBFD subband resources. Downlink data is transmitted in the UL symbol of the flexible timeslot.

[0106] In one example, SBFD subband resources can be frequency domain resources within an SBFD time slot or SBFD symbol. An SBFD symbol can be a symbol configured with an SBFD subband. The base station and UE can perform full-duplex communication on the SBFD subbands within these SBFD symbols. That is, uplink transmission, downlink transmission, or simultaneous uplink and downlink transmission can be performed on the SBFD subband resources.

[0107] SBFD subband resources can be explicitly designated as uplink, downlink, or flexible. When a SBFD subband resource is designated as flexible, uplink or downlink scheduling can be flexibly performed on the SBFD subband resource. If no SBFD subband resource is explicitly designated as flexible, it can be used for uplink or downlink data transmission. SBFD symbol configuration includes the following: which symbols in the DL time slot, UL time slot, and F time slot are used for SBFD transmission, as well as the implementation period and starting point.

[0108] SBFD subband resources indicated as uplink are called uplink subband resources, abbreviated as UL SB, meaning they are used for uplink. SBFD subband resources indicated as downlink are called downlink subband resources, abbreviated as DL SB, meaning they are used for downlink. Frequency domain resources indicated as guard subbands are called guard subband resources, abbreviated as GB, meaning they are used for guard subbands.

[0109] For half-duplex UEs supporting SBFD, the UE can obtain the configuration of the SBFD subband resources. However, the UE can only receive DL data or transmit UL data at the same time (symbol), regardless of whether it is on the same carrier or on different carriers. For full-duplex UEs supporting SBFD, the UE can obtain the configuration of the SBFD subband resources. Moreover, the UE can receive DL data and transmit UL data at the same time (symbol), regardless of whether it is on the same carrier or on different carriers.

[0110] The base station configures SBFD subband resources for half-duplex or full-duplex UEs that support the SBFD function. SBFD subband resources are configured for the UE in DL time slots or DL ​​symbols. These SBFD subband resources are used to transmit UL data, meaning they can be uplink subband resources. DL symbols configured with SBFD subband resources are SBFD symbols. In addition to the uplink subband resources, SBFD symbols contain downlink subband resources and guard subband resources, with the guard subband resources located between the uplink and downlink subband resources.

[0111] SBFD subband resources are configured for the UE in a UL timeslot or UL symbol, and are used to transmit DL data. This means the SBFD subband resources can be downlink subband resources. UL symbols configured with SBFD subband resources are SBFD symbols. In addition to the downlink subband resources, SBFD symbols contain uplink subband resources and guard subband resources, with the guard subband resources located between the uplink and downlink subband resources.

[0112] SBFD subband resources are configured for the UE in the F time slot or F symbol, and the SBFD subband resources are used to transmit DL data (or UL data). That is, the SBFD subband resources can be downlink subband resources (or uplink subband resources). F symbols configured with SBFD subband resources are SBFD symbols. In addition to the downlink subband resources (or uplink subband resources), the SBFD symbols contain uplink subband resources (or downlink subband resources) and guard subband resources. The guard subband resources are located between the uplink subband resources and the downlink subband resources.

[0113] In one example, the base station in the subsequent embodiments is a full-duplex base station that can process both DL and UL data simultaneously. The UE in the subsequent embodiments is a half-duplex UE or a full-duplex UE that supports SBFD. Regardless of whether it is on the same carrier or different carriers, a half-duplex UE can only process either DL or UL data at a time and can access all SBFD configuration parameters. A full-duplex UE can simultaneously process both DL and UL data at a time, regardless of whether it is on the same carrier or different carriers, and can access all SBFD configuration parameters.

[0114] To support FD communication, SBFD subband resources may be semi-statically configured, such as semi-statically configured through RRC signaling, or dynamically configured, such as dynamically configured through DCI.

[0115] In TDD FD mode, a multi-carrier resource allocation method is proposed. This involves allocating resources for TDD full-duplex uplink and downlink physical channels in a multi-carrier scenario. This method primarily addresses resource allocation, scheduling, and activation in a multi-carrier scenario. The following describes this resource allocation method.

[0116] First, BWP frequency domain resource configuration, that is, SBFD resource allocation based on BWP.

[0117] The base station sends BWP frequency domain resource configuration information to the UE, and the UE receives the BWP frequency domain resource configuration information sent by the base station. The BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and an SBFD frequency domain resource (i.e., a frequency resource), and the resource identifier may include a BWP identifier and a carrier identifier.

[0118] In one example, for a TDD system, in a multi-carrier scenario, when a base station configures a BWP for a UE, the same downlink BWP identifier and uplink BWP identifier can be configured on different carriers. The frequency resources corresponding to the same downlink BWP identifier and uplink BWP identifier can be different, that is, the SBFD frequency domain resources corresponding to the uplink BWP identifier are different from the SBFD frequency domain resources corresponding to the downlink BWP identifier.

[0119] In an example, the size of the SBFD frequency domain resource corresponding to the uplink BWP identifier and the size of the SBFD frequency domain resource corresponding to the downlink BWP identifier may be different or the same.

[0120] In one example, an SBFD frequency domain resource is a frequency domain resource configured within a carrier indicated by a carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to a BWP identifier. The carriers indicated by different carrier identifiers are SBFD intra-band carriers (Intra-band CA) or SBFD inter-band carriers (Inter-band CA).

[0121] For example, when configuring BWP for a UE, the base station configures an uplink BWP identifier and a downlink BWP identifier. The uplink BWP identifier and the downlink BWP identifier can be the same, and the uplink BWP identifier corresponds to the first carrier identifier, while the downlink BWP identifier corresponds to the second carrier identifier. Based on this, the BWP frequency domain resource configuration information includes the mapping relationship between the uplink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, as well as the mapping relationship between the downlink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources.

[0122] Figure 3A illustrates asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario. Each carrier has a BWP, with both the uplink and downlink BWP identifiers being BWP1. The uplink BWP identifier is UL BWP1, and the downlink BWP identifier is DL BWP1. The same downlink and uplink BWP identifiers form a BWP pair. The second carrier identifier corresponding to DL BWP1 is CC1, and the downlink BWP is located in CC1. The first carrier identifier corresponding to UL BWP1 is CC2, and the uplink BWP is located in CC2.

[0123] The frequency resources corresponding to DL BWP1 and UL BWP1 can be different. For example, the base station allocates SBFD frequency-domain resources for DL ​​BWP1 on CC1. These SBFD frequency-domain resources start from PRB 0 to PRB 100. The base station allocates SBFD frequency-domain resources for UL BWP1 on CC2. These SBFD frequency-domain resources start from PRB 0 to PRB 100. Obviously, because the base station configures SBFD frequency-domain resources on different CCs, the frequency resources are different.

[0124] For example, when the base station configures BWP for the UE, it configures an uplink BWP identifier and a downlink BWP identifier. The uplink BWP identifier and the downlink BWP identifier can be the same, and the uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier simultaneously correspond to the second carrier identifier. Based on this, the BWP frequency domain resource configuration information includes the mapping relationship between the uplink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, the mapping relationship between the uplink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources, and the mapping relationship between the downlink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources.

[0125] Figure 3B illustrates asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario, with the DL BWP resource allocation being smaller than the UL BWP resource allocation. Both the uplink and downlink BWP identifiers are BWP1. The uplink BWP identifier is UL BWP1, and the downlink BWP identifier is DL BWP1. These identical downlink and uplink BWP identifiers form a BWP group. The second carrier identifier corresponding to DL BWP1 is CC2, and the downlink BWP is located on CC2. The first carrier identifier corresponding to UL BWP1 is CC1, and the second carrier identifier corresponding to UL BWP1 is CC2, meaning the uplink BWP is located on both CC1 and CC2.

[0126] The frequency resources corresponding to DL BWP1 and UL BWP1 can be different, and the size of the frequency resources corresponding to DL BWP1 and UL BWP1 can be different. For example, the frequency resources can partially overlap or not overlap. For example, the base station allocates SBFD frequency-domain resources to UL BWP1 on CC1. The SBFD frequency-domain resources are from the 0th PRB to the 100th PRB. The base station allocates SBFD frequency-domain resources to UL BWP1 on CC2. The SBFD frequency-domain resources are from the 0th PRB to the 50th PRB. The base station allocates SBFD frequency-domain resources to DL BWP1 on CC2. The SBFD frequency-domain resources are from the 51st PRB to the 100th PRB.

[0127] For example, when the base station configures BWP for the UE, it configures an uplink BWP identifier and a downlink BWP identifier. The uplink BWP identifier and the downlink BWP identifier can be the same, and the downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier simultaneously correspond to the second carrier identifier. Based on this, the BWP frequency domain resource configuration information includes the mapping relationship between the downlink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, the mapping relationship between the downlink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources, and the mapping relationship between the uplink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources.

[0128] Figure 3C illustrates asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario, with DL BWP resources being larger than UL BWP resources. Both the uplink and downlink BWP identifiers are BWP1. The uplink BWP identifier is UL BWP1, and the downlink BWP identifier is DL BWP1. These identical downlink and uplink BWP identifiers form a BWP group. The first carrier identifier corresponding to DL BWP1 is CC1, and the second carrier identifier corresponding to DL BWP1 is CC2, indicating that the downlink BWP is allocated on both CC1 and CC2. The second carrier identifier corresponding to UL BWP1 is CC2, indicating that the uplink BWP is allocated on CC2.

[0129] The frequency resources corresponding to DL BWP1 and UL BWP1 can be different, and the size of the frequency resources corresponding to DL BWP1 and UL BWP1 can be different. For example, the frequency resources can partially overlap or not overlap. For example, the base station allocates SBFD frequency-domain resources to DL BWP1 on CC1. The SBFD frequency-domain resources are from the 0th PRB to the 100th PRB. The base station allocates SBFD frequency-domain resources to UL BWP1 on CC2. The SBFD frequency-domain resources are from the 0th PRB to the 50th PRB. The base station allocates SBFD frequency-domain resources to DL BWP1 on CC2. The SBFD frequency-domain resources are from the 51st PRB to the 100th PRB.

[0130] For example, when the base station configures BWP for the UE, it configures an uplink BWP identifier and a downlink BWP identifier. The uplink BWP identifier and the downlink BWP identifier can be the same, and the uplink BWP identifier and the downlink BWP identifier correspond to the first carrier identifier at the same time, and the uplink BWP identifier and the downlink BWP identifier correspond to the second carrier identifier at the same time. Based on this, the BWP frequency domain resource configuration information includes the mapping relationship between the downlink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, the mapping relationship between the downlink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources, the mapping relationship between the uplink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, and the mapping relationship between the uplink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources.

[0131] Figure 3D illustrates asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario. The two carriers have the same SBFD configuration, and the resources of the two carriers belong to the same BWP. Both the uplink and downlink BWP identifiers are BWP1. The uplink BWP identifier is UL BWP1, and the downlink BWP identifier is DL BWP1. These two identifiers form a BWP group. The first carrier identifier corresponding to DL BWP1 and UL BWP1 is CC1, and the second carrier identifier corresponding to DL BWP1 and UL BWP1 is CC2. This means that the downlink BWP is on CC1 and CC2, and the uplink BWP is on CC1 and CC2.

[0132] The base station allocates SBFD frequency domain resources for UL BWP1 on CC1, which are from PRB 0 to PRB 50. The base station allocates SBFD frequency domain resources for DL ​​BWP1 on CC1, which are from PRB 51 to PRB 100.

[0133] The base station allocates SBFD frequency domain resources for UL BWP1 on CC2, which are from PRB 0 to PRB 50. The base station allocates SBFD frequency domain resources for DL ​​BWP1 on CC2, which are from PRB 51 to PRB 100.

[0134] For example, when configuring a BWP for a UE, the base station configures an uplink BWP identifier and a downlink BWP identifier. The uplink BWP identifier and the downlink BWP identifier can be different, and the uplink BWP identifier corresponds to the first carrier identifier, while the downlink BWP identifier corresponds to the second carrier identifier. Based on this, the BWP frequency domain resource configuration information includes the mapping relationship between the uplink BWP identifier, the first carrier identifier, and the SBFD frequency domain resources, as well as the mapping relationship between the downlink BWP identifier, the second carrier identifier, and the SBFD frequency domain resources.

[0135] Figure 3E illustrates asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario. The uplink BWP identifier is different from the downlink BWP identifier: UL BWP2, while the downlink BWP identifier is DL BWP1. The second carrier identifier corresponding to DL BWP1 is CC1, and the downlink BWP is located in CC1. The first carrier identifier corresponding to UL BWP2 is CC2, and the uplink BWP is located in CC2.

[0136] The base station allocates SBFD frequency domain resources from PRB 0 to PRB 100 for DL ​​BWP1 on CC1 and allocates SBFD frequency domain resources from PRB 0 to PRB 100 for UL BWP2 on CC2.

[0137] For example, when the base station configures BWP for the UE, it configures a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier, and a second downlink BWP identifier. The first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier. The first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier correspond to the second carrier identifier.

[0138] Based on this, the BWP frequency domain resource configuration information includes the first downlink BWP identifier, the mapping relationship between the first carrier identifier and the SBFD frequency domain resource, the first uplink BWP identifier, the mapping relationship between the first carrier identifier and the SBFD frequency domain resource, the second downlink BWP identifier, the mapping relationship between the second carrier identifier and the SBFD frequency domain resource, the second uplink BWP identifier, and the mapping relationship between the second carrier identifier and the SBFD frequency domain resource.

[0139] FIG3F shows a schematic diagram of asymmetric resource allocation for DL ​​and UL BWPs in a multi-carrier scenario. The two carriers have the same SBFD configuration, but the resources of the two carriers belong to different BWPs. The uplink BWP identifiers include UL BWP1 and UL BWP2, and the downlink BWP identifiers include DL BWP1 and DL BWP2.

[0140] UL BWP1 and DL BWP1 form a pair of BWP groups, and UL BWP2 and DL BWP2 form another pair of BWP groups. The first carrier identifier corresponding to DL BWP1 and UL BWP1 is CC1, and the second carrier identifier corresponding to DL BWP2 and UL BWP2 is CC2, that is, DL BWP1 is on CC1, DL BWP2 is on CC1, UL BWP1 is on CC1, and UL BWP2 is on CC1.

[0141] The base station allocates SBFD frequency domain resources for UL BWP1 on CC1, which are from PRB 0 to PRB 50. The base station allocates SBFD frequency domain resources for DL ​​BWP1 on CC1, which are from PRB 51 to PRB 100.

[0142] The base station allocates SBFD frequency domain resources for UL BWP2 on CC2, which are from PRB 0 to PRB 50. The base station allocates SBFD frequency domain resources for DL ​​BWP2 on CC2, which are from PRB 51 to PRB 100.

[0143] In one example, after configuring BWP frequency domain resources for a UE, the base station may send BWP frequency domain resource configuration information to the UE. The BWP frequency domain resource configuration information includes a mapping relationship between a BWP identifier (such as a downlink BWP identifier and an uplink BWP identifier), a carrier identifier, and a SBFD frequency domain resource.

[0144] Second, the BWP activation configuration table. The base station and UE can pre-configure the same BWP activation configuration table, for example, by pre-configuring the BWP activation configuration table at the physical layer of the base station and UE. Alternatively, the base station can obtain the BWP activation configuration table and send it to the UE via an RRC message, for example, by broadcasting the BWP activation configuration table to multiple UEs via an RRC message.

[0145] In one example, a BWP activation configuration table (also known as a BWP matching pair activation indication table) may include a mapping between BWP indication information and BWP configuration pairs. For each BWP configuration pair in the BWP activation configuration table, the BWP configuration pair may include a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, and an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier. The downlink BWP identifier and the uplink BWP identifier may be the same or different. The carrier identifier corresponding to the downlink BWP identifier and the carrier identifier corresponding to the uplink BWP identifier may be the same or different.

[0146] See Table 2, which is an example of a BWP activation configuration table. The BWP activation configuration table provides 16 BWP configuration pairs, which are indicated by 4-bit BWP indication information.

[0147] Table 2

[0148] As can be seen from Table 2, BWP indication information can be represented by 4 bits, and each BWP indication information corresponds to a BWP configuration pair. The BWP configuration pair is used to indicate the downlink BWP identifier and the carrier identifier corresponding to the downlink BWP identifier, and the uplink BWP identifier and the carrier identifier corresponding to the uplink BWP identifier.

[0149] In one example, the BWP activation configuration table (also called the BWP matching pair activation indication table) may include a mapping relationship between BWP indication information and BWP configuration pairs. For each BWP configuration pair in the BWP activation configuration table, the BWP configuration pair may include a first configuration sub-pair and a second configuration sub-pair.

[0150] The first configuration subpair may include a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, and a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier. The first downlink BWP identifier and the first uplink BWP identifier may be the same or different. The carrier identifier corresponding to the first downlink BWP identifier and the carrier identifier corresponding to the first uplink BWP identifier may be the same or different.

[0151] The second configuration subpair may include a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, a second uplink BWP identifier, and a carrier identifier corresponding to the second uplink BWP identifier. The second downlink BWP identifier and the second uplink BWP identifier may be the same or different. The carrier identifier corresponding to the second downlink BWP identifier and the carrier identifier corresponding to the second uplink BWP identifier may be the same or different.

[0152] Table 3 shows an example of a BWP activation configuration table. The table provides four BWP configuration pairs, each indicated by a 4-bit BWP indication. While this example uses only four BWP configuration pairs, the number of BWP configuration pairs can be greater than four, and there is no limit to this.

[0153] Table 3

[0154] As can be seen from Table 3, the BWP indication information is represented by 4 bits, and the BWP indication information corresponds to a BWP configuration pair. The BWP configuration pair includes a first configuration sub-pair and a second configuration sub-pair. The first configuration sub-pair indicates the downlink BWP identifier and the carrier identifier corresponding to the downlink BWP identifier, and the uplink BWP identifier and the carrier identifier corresponding to the uplink BWP identifier. The second configuration sub-pair indicates the downlink BWP identifier and the carrier identifier corresponding to the downlink BWP identifier, and the uplink BWP identifier and the carrier identifier corresponding to the uplink BWP identifier.

[0155] Third, BWP activation configuration, that is, the base station can trigger the UE to obtain the target BWP configuration pair through the BWP activation configuration, and determine the target SBFD frequency domain resources associated with the target BWP configuration pair.

[0156] In one example, the BWP activation configuration process may include the following steps:

[0157] Step S11: The base station sends a BWP activation configuration to the UE. The BWP activation configuration includes target BWP indication information, such as any BWP indication information in the BWP activation configuration table, such as 0000 or 0001.

[0158] In one example, the base station sends the BWP activation configuration to the UE via a DCI message, and the UE receives the BWP activation configuration via the DCI message. Alternatively, the base station sends the BWP activation configuration to the UE via a MAC-CE message, and the UE receives the BWP activation configuration via the MAC-CE message. Alternatively, the base station sends the BWP activation configuration to the UE via an RRC message, and the UE receives the BWP activation configuration via the RRC message.

[0159] Step S12: After receiving the BWP activation configuration, the UE obtains a target BWP configuration pair corresponding to the target BWP indication information (located in the BWP activation configuration) from the BWP activation configuration table. The target BWP configuration pair may include a target BWP identifier and a target carrier identifier.

[0160] In an example, the UE can obtain a target BWP configuration pair from the BWP activation configuration table in Table 2. The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier, where the target downlink BWP identifier is the same as or different from the target uplink BWP identifier. The target BWP configuration pair also includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier, where the carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

[0161] In an example, the UE can obtain a target BWP configuration pair from the BWP activation configuration table in Table 3. The target BWP configuration pair includes a target first configuration subpair and a target second configuration subpair. The target first configuration subpair includes a target first downlink BWP identifier, a target first uplink BWP identifier, a carrier identifier corresponding to the target first downlink BWP identifier, and a carrier identifier corresponding to the target first uplink BWP identifier. The target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier. The carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier.

[0162] The target second configuration subpair may include a target second downlink BWP identifier, a target second uplink BWP identifier, a carrier identifier corresponding to the target second downlink BWP identifier, and a carrier identifier corresponding to the target second uplink BWP identifier. The target second downlink BWP identifier and the target second uplink BWP identifier may be the same or different. The carrier identifier corresponding to the target second downlink BWP identifier and the carrier identifier corresponding to the target second uplink BWP identifier may be the same or different.

[0163] In one example, the BWP activation configuration may include a switch flag and the target BWP indication information. If the switch flag is a first value, the UE may obtain the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table, i.e., may execute step S12. If the switch flag is not a first value, the UE may prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table, i.e., may not execute step S12 and subsequent steps.

[0164] For example, the switch flag and target BWP indication information can be carried in the DCI message, such as a DCI message including a bandwidth part indicator and a switch flag. If the switch flag is 00 (not the first value), the bandwidth part indicator is used to indicate the original BWP switch. If the switch flag is 01 (not the first value), the bandwidth part indicator is used to indicate the BWP of SBFD in a single-carrier scenario. There are no restrictions on the processing of the switch flags 00 and 01.

[0165] If the switch flag is 10 (e.g., 10 is the first value), the Bandwidth part indicator is used for the BWP indication of SBFD in the multi-carrier case. That is, the Bandwidth part indicator serves as the target BWP indication information, and the target BWP indication information is used to indicate the target BWP configuration pair.

[0166] See Table 4, which is an example of a DCI message, and the content of this DCI message is not limited.

[0167] Table 4

[0168] In one example, the BWP activation configuration may include target BWP indication information. If the target BWP indication information is a target value (e.g., any value other than the BWP indication information in Table 2 or Table 3), the UE is prohibited from obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table, i.e., step S12 and subsequent steps may not be performed. Alternatively, if the target BWP indication information is not a target value (e.g., any value in Table 2 or Table 3), the UE obtains the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table, i.e., step S12 may be performed.

[0169] For example, a new Bandwidth part indicator for SBFD for multiple carriers IE is added to the DCI message to distinguish the Bandwidth part indicator. See Table 5 for an example of a DCI message.

[0170] Table 5

[0171] Step S13: The UE determines the target SBFD frequency domain resources associated with the target BWP configuration pair based on the BWP frequency domain resource configuration information. For example, since the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and the BWP frequency domain resource configuration information includes a mapping relationship between the BWP identifier, the carrier identifier, and the SBFD frequency domain resources, the UE can determine the target SBFD frequency domain resources associated with the target BWP identifier and the target carrier identifier based on the mapping relationship between the BWP identifier, the carrier identifier, and the SBFD frequency domain resources.

[0172] Step S14: The UE transmits data based on the target SBFD frequency domain resources.

[0173] For example, if the target SBFD frequency domain resources include the BWP frequency domain resources of the uplink BWP, the UE may send data, such as application data or signals, on the BWP frequency domain resources of the uplink BWP.

[0174] For example, if the target SBFD frequency domain resources include the BWP frequency domain resources of the downlink BWP, the UE may receive data, such as application data or signals, on the BWP frequency domain resources of the downlink BWP.

[0175] Step S15: The base station determines the target SBFD frequency domain resources associated with the target BWP configuration pair (ie, the target BWP configuration pair corresponding to the UE) based on the BWP frequency domain resource configuration information.

[0176] Step S16: The base station transmits data to the UE based on the target SBFD frequency domain resources.

[0177] For example, if the target SBFD frequency domain resources include the BWP frequency domain resources of the uplink BWP, the base station may receive data, such as application data or signals, on the BWP frequency domain resources of the uplink BWP.

[0178] If the target SBFD frequency domain resources include the BWP frequency domain resources of the downlink BWP, the base station may send data, such as application data or signals, on the BWP frequency domain resources of the downlink BWP.

[0179] Fourth, switching the BWP activation configuration. After the base station sends the BWP activation configuration to the UE, if the SBFD frequency domain resources used by the UE change during the BWP switching time, the base station can also obtain the updated BWP activation configuration. The updated BWP activation configuration includes updated target BWP indication information, which corresponds to the changed SBFD frequency domain resources.

[0180] The base station sends the updated BWP activation configuration to the UE. The UE retrieves the target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table. Based on the BWP frequency domain resource configuration information, the UE determines the target SBFD frequency domain resources associated with the target BWP configuration pair. The base station sends the updated BWP activation configuration to the UE via a DCI message, a MAC-CE message, or an RRC message.

[0181] 4A is a schematic diagram of single BWP switching in a multi-carrier scenario, illustrating activation and switching of a single BWP pair. DL BWP#1 (downlink BWP1) is on CC1, UL BWP#1 (uplink BWP1) is on CC1, BWP#2 (downlink BWP2 and uplink BWP2) are on CC2, DL BWP#3 (downlink BWP3) is on CC3, and UL BWP#3 (uplink BWP1) is on CC3.

[0182] DL BWP#1 and UL BWP#1 have asymmetric frequency domain resource allocation, DL BWP#3 and UL BWP#3 have asymmetric frequency domain resource allocation, DL BWP#3 and UL BWP#3 have non-contiguous resource allocation, and DL BWP and UL BWP of BWP#2 occupy the same frequency domain resource allocation.

[0183] As shown in Figure 4A , during the BWP switching time, the base station first activates DL BWP#1 and UL BWP#1 on CC1 via a DCI message. Then, the base station notifies the UE via a DCI message to switch DL BWP#1 and UL BWP#1 on CC1 to BWP#2 on CC2. Finally, the base station notifies the UE via a DCI message to switch BWP#2 on CC2 to DL BWP#3 and UL BWP#3 on CC3.

[0184] The horizontal axis is Time / Event, the vertical axis is Frequency, and BWP-In activity Timer Expiry indicates that the DCI activity timer has expired, that is, switching is performed within the BWP switching time.

[0185] 4B is a schematic diagram of multiple BWP switching in a multi-carrier scenario, showing the activation and switching of multiple BWP matching pairs. DL BWP#1 (downlink BWP1) is on CC1, UL BWP#1 (uplink BWP1) is on CC1, BWP#2 (downlink BWP2 and uplink BWP2) are on CC2, DL BWP#3 (downlink BWP3) is on CC3, and UL BWP#3 (uplink BWP1) is on CC3.

[0186] DL BWP#1 and UL BWP#1 have asymmetric frequency domain resource allocation, DL BWP#3 and UL BWP#3 have asymmetric frequency domain resource allocation. DL BWP#3 and UL BWP#3 have non-contiguous resource allocation. DL BWP and UL BWP of BWP#2 occupy the same frequency domain resource allocation.

[0187] During the BWP switching time, the base station activates DL BWP#1 and UL BWP#1 on CC1 and BWP#2 on CC2 through a DCI message. The base station notifies the UE through a DCI message to switch DL BWP#1 and UL BWP#1 on CC1 and BWP#2 on CC2 to DL BWP#3 and UL BWP#3 on CC3.

[0188] In one example, based on the processes of BWP frequency domain resource configuration, BWP activation configuration table, BWP activation configuration, and BWP activation configuration switching, a BWP-based SBFD frequency domain resource allocation and activation method can be implemented in a multi-carrier scenario. When configuring a single BWP or multiple BWPs, SBFD BWP matching pair activation is supported, such as the base station activating SBFD by indicating the BWP activation configuration.

[0189] If a carrier is deactivated, if the base station deactivates a carrier through DCI, the SBFD configuration on the carrier becomes invalid. If the base station activates a carrier through DCI, the DL / UL configuration takes effect, but the SBFD configuration does not take effect. It is necessary to use 1 bit to indicate whether the BWP-based SBFD configuration is effective.

[0190] In one example, in a BWP-based SBFD resource configuration and activation method, the base station can configure the DL / UL resources on each carrier into the same or different BWP pairs. The base station can semi-statically or dynamically configure one-to-one or one-to-many DL / UL BWP matching groups (with the same or different DL / UL BWP center frequencies). The base station can dynamically configure SBFD resources by activating / switching multiple BWPs or DL / UL BWP matching pairs. The base station can dynamically adjust SBFD configuration parameters by introducing carrier-based BWP activation parameters / BWP deactivation parameters in DCI messages.

[0191] In the above process, the BWP-based SBFD frequency domain resource allocation and activation method in the multi-carrier case is introduced. This embodiment also involves a carrier-based SBFD frequency domain resource allocation and activation method in the multi-carrier case. The carrier-based SBFD frequency domain resource allocation and activation method is described below.

[0192] Fifth, in the case of multi-carrier, carrier-based SBFD frequency domain resource allocation and activation.

[0193] In one example, the base station can configure SBFD frequency domain resources for multiple carriers within a carrier group. The base station can send SBFD resource allocation information to the UE, where the SBFD resource allocation information indicates the SBFD frequency domain resources configured for the multiple carriers within the carrier group. Among the SBFD frequency domain resources configured for the multiple carriers within the carrier group, different carriers within the carrier group have at least one set of opposite time slots. The opposite time slots include uplink time slots and downlink time slots, i.e., the time slots of one carrier are uplink time slots, and the time slots of the other carrier are downlink time slots.

[0194] For example, if a carrier group includes two carriers (a first carrier and a second carrier), if time slot k of the first carrier is an uplink time slot and time slot k of the second carrier is a downlink time slot, then time slot k is an opposite time slot. That is, different carriers in the carrier group have a set of opposite time slots k, and time slot k can be any time slot.

[0195] 5A is a schematic diagram of SBFD frequency domain resource allocation based on multiple carriers. SBFD frequency domain resources are formed on multiple carriers, such as CC1 and CC2.

[0196] In one example, before multiple carriers within a carrier group form SBFD frequency domain resources, different carriers within the carrier group can be in the same time slot. For example, as shown in Figure 5A , time slot 0 of CC1 and time slot 0 of CC2 are both DL slots (i.e., downlink time slots), time slot 1 of CC1 and time slot 1 of CC2 are both DL slots, time slot 2 of CC1 and time slot 2 of CC2 are both DL slots, time slot 3 of CC1 and time slot 3 of CC2 are both UL slots (i.e., uplink time slots), and time slot 4 of CC1 and time slot 4 of CC2 are both UL slots.

[0197] To create SBFD frequency-domain resources across multiple carriers within a carrier group, different carriers within the carrier group have at least one set of opposite time slots. For example, as shown in Figure 5A , time slot 0 of CC1 is a DL slot, while time slot 0 of CC2 is a UL slot. Time slot 1 of CC1 is a DL slot, while time slot 1 of CC2 is a UL slot. Time slot 2 of CC1 is a DL slot, while time slot 2 of CC2 is a UL slot. Time slot 3 of CC1 is a UL slot, while time slot 3 of CC2 is a DL slot. Time slot 4 of CC1 is a UL slot, while time slot 4 of CC2 is a DL slot.

[0198] Of course, the above example uses five sets of opposite time slots. To form SBFD frequency domain resources across multiple carriers, at least one set of opposite time slots is sufficient. For example, time slot k can be an opposite time slot. Time slot k can be any time slot, and the other time slots can be opposite or the same time slot.

[0199] In an example, to form SBFD frequency domain resources on multiple carriers, the following method can be used:

[0200] Method 1: Set the time slots on different carriers (such as CC1 and CC2, where CC1 and CC2 belong to intra-band CA) as flexible time slots. Then, use the SFI to specify whether the flexible time slot is a DL time slot or a UL time slot. When using the SFI to specify whether the flexible time slot is a DL time slot or a UL time slot, at least one set of opposite time slots must exist on different carriers, thereby forming SBFD frequency domain resources across multiple carriers.

[0201] For example, when a base station sends SBFD resource allocation information to a UE, the SBFD resource allocation information includes a first allocation indicator and a second allocation indicator. For each of multiple carriers, the first allocation indicator configures all timeslots included in that carrier as flexible timeslots, i.e., setting timeslots on different carriers as flexible timeslots. The second allocation indicator indicates whether each flexible timeslot is an uplink timeslot or a downlink timeslot, i.e., using the SFI to specify whether the flexible timeslot is a DL timeslot or an UL timeslot.

[0202] When the second allocation indication is used to indicate that each flexible time slot is used as an uplink time slot or a downlink time slot, it is necessary to ensure that different carriers have at least one set of opposite time slots, such as using the time slot structure of FIG. 5A for indication.

[0203] Method 2: SBFD frequency domain resources are formed across multiple carriers by configuring different DL / UL configurations (i.e., different DL time slots or UL time slots) for different carriers (e.g., CC1 and CC2, where CC1 and CC2 belong to intra-band CA). When configuring DL time slots or UL time slots for different carriers, it is necessary to ensure that at least one set of opposite time slots exists between different carriers, thereby forming SBFD frequency domain resources across multiple carriers.

[0204] For example, when the base station sends SBFD resource allocation information to the UE, the SBFD resource allocation information may include a third allocation indication. For each carrier among the multiple carriers, the third allocation indication (such as DL / UL configuration) is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot.

[0205] When each time slot is configured as an uplink time slot or a downlink time slot through the third allocation indication, it is necessary to ensure that different carriers have at least one set of opposite time slots, such as indicated by the time slot structure of FIG. 5A .

[0206] Method 3: By setting an offset, the DL / UL configuration on each carrier is differentiated, enabling multiple carriers to form SBFD frequency domain resources. When setting the offset, it is necessary to ensure that different carriers have at least one set of opposite time slots. The offset can be a slot offset and / or a symbol offset.

[0207] For example, when a base station sends SBFD resource allocation information to a UE, the SBFD resource allocation information may include a fourth allocation indication and a fifth allocation indication. For a first carrier among multiple carriers (the first carrier can be any carrier), the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot. As shown in Figure 5A , assuming the first carrier is CC1, the fourth allocation indication uses the time slot structure of Figure 5A , i.e., indicating the five time slots as DL, DL, DL, UL, and UL, respectively.

[0208] For a second carrier other than the first carrier (the second carrier may be at least one), the fifth allocation indication is used to indicate an offset between the second carrier and the first carrier. For example, the fifth allocation indication may be an RRC message, and the offset is set via the RRC message. For example, for each second carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

[0209] The offset may be a slot offset and / or a symbol offset. When the offset is a slot offset and a symbol offset, the maximum value of the symbol offset is the total number of symbols in a slot. When the offset is a symbol offset, the maximum value of the symbol offset may be limited to the total number of symbols in a slot, or may be unlimited, i.e., not limited to the total number of symbols in a slot.

[0210] Assuming that the time slot offset is m, and the time slot offset m represents a rightward shift of m time slots. Then, time slot 0 of the first carrier and time slot 0+m of the second carrier have the same time slot. For example, if both are uplink time slots or both are downlink time slots, time slot 1 of the first carrier and time slot 1+m of the second carrier have the same time slot, and so on. Assuming that the time slot offset is m, and the time slot offset m represents a leftward shift of m time slots, then time slot 0 of the first carrier and time slot 0-m of the second carrier have the same time slot, time slot 1 of the first carrier and time slot 1-m of the second carrier have the same time slot, and so on.

[0211] For example, assuming that the 5 time slots of the first carrier are DL, DL, DL, UL, and UL, and the time slot offset m indicates a shift to the right by 2 time slots, time slot 0 of the first carrier and time slot 2 of the second carrier have the same time slot, and time slot 2 of the second carrier is DL. Time slot 1 of the first carrier and time slot 3 of the second carrier have the same time slot, and time slot 3 of the second carrier is DL. Time slot 2 of the first carrier and time slot 4 of the second carrier have the same time slot, and time slot 4 of the second carrier is DL. Time slot 3 of the first carrier and time slot 0 of the second carrier (that is, counting from the last time slot to the first time slot) have the same time slot, and time slot 0 of the second carrier is UL. Time slot 4 of the first carrier and time slot 1 of the second carrier have the same time slot, and time slot 1 of the second carrier is UL. In summary, the 5 time slots of the second carrier are UL, UL, DL, DL, and DL.

[0212] Here, assuming that the symbol offset is n, and the symbol offset n represents a rightward shift of n symbols, then the symbol 0 of the first carrier and the symbol 0+n of the second carrier have the same symbol. For example, if both are uplink symbols or both are downlink symbols, the symbol 1 of the first carrier and the symbol 1+n of the second carrier have the same symbol, and so on. Assuming that the symbol offset is n, and the symbol offset n represents a leftward shift of n symbols, then the symbol 0 of the first carrier and the symbols 0-n of the second carrier have the same time slot, the symbol 1 of the first carrier and the symbols 1-n of the second carrier have the same time slot, and so on.

[0213] Assuming the slot offset is m and the symbol offset is n, slot offset m represents a rightward shift of m slots, and symbol offset n represents a rightward shift of n symbols. Then, slot 0 of the first carrier and slot 0+m of the second carrier are the same slot, slot 1 of the first carrier and slot 1+m of the second carrier are the same slot, symbol 0 of the first carrier and symbol 0+n of the second carrier have the same sign, symbol 1 of the first carrier and symbol 1+n of the second carrier have the same sign, and so on.

[0214] Assuming the slot offset is m and the symbol offset is n, slot offset m indicates a left shift of m slots, and symbol offset n indicates a left shift of n symbols. Then, slot 0 of the first carrier coincides with slots 0-m of the second carrier, slot 1 of the first carrier coincides with slots 1-m of the second carrier, symbol 0 of the first carrier coincides with symbols 0-n of the second carrier, symbol 1 of the first carrier coincides with symbols 1-n of the second carrier, and so on.

[0215] In an example, the fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is valid, such as indicating that the offset is valid, or indicating that the offset is not valid.

[0216] In summary, it can be seen that the fifth allocation indication may include an effective indication bit. If the effective indication bit indicates that the offset between the second carrier and the first carrier is effective, such as the effective indication bit is a first value, the fifth allocation indication also includes the offset between the second carrier and the first carrier (such as a time slot offset and / or a symbol offset). If the effective indication bit indicates that the offset between the second carrier and the first carrier is not effective, such as the effective indication bit is a second value, the fifth allocation indication may not include the offset between the second carrier and the first carrier.

[0217] This completes carrier-based SBFD frequency domain resource allocation. The base station configures SBFD frequency domain resources on multiple carriers within the carrier group and sends SBFD resource allocation information to the UE. The UE receives the SBFD resource allocation information, which indicates the SBFD frequency domain resources configured on multiple carriers.

[0218] After completing carrier-based SBFD frequency domain resource allocation, carrier-based SBFD frequency domain resources may also be activated or deactivated. For example, for each carrier, the base station may send SBFD configuration information corresponding to that carrier to the UE. The UE receives this SBFD configuration information, which indicates whether the SBFD frequency domain resources on that carrier are enabled or disabled. Activation indicates activation of the SBFD frequency domain resources on that carrier, while deactivation indicates deactivation of the SBFD frequency domain resources on that carrier.

[0219] For example, when the base station sends SBFD configuration information to the UE, for the third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

[0220] When the base station sends SBFD configuration information to the UE, for the fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

[0221] For example, to minimize the impact on legacy UEs, the following method can be used to activate and deactivate SBFD frequency domain resources and carriers: If the base station deactivates a carrier via DCI, the SBFD configuration on that carrier becomes invalid. Specifically, the base station sends SBFD configuration information to the UE via DCI. This SBFD configuration information includes a carrier deactivation indication. This deactivation indication is used to deactivate the carrier and indicates that the SBFD frequency domain resources on that carrier have become invalid.

[0222] If the base station activates a carrier through DCI, the DL / UL configuration on the carrier will take effect, but the SBFD configuration on the carrier will not take effect. 1 bit can be used to indicate whether the SBFD configuration is effective. In this way, the base station can flexibly control whether the SBFD configuration is effective based on the user characteristics and user volume of the cell. That is, the base station sends SBFD configuration information to the UE through DCI. The SBFD configuration information includes an activation indication of the carrier, and the activation indication is used to activate the carrier. The SBFD configuration information also includes a 1-bit effectiveness indication. If the effectiveness indication is a first value (such as 1), it indicates that the SBFD frequency domain resources on the carrier are effective; if the effectiveness indication is a second value (such as 0), it indicates that the SBFD frequency domain resources on the carrier are not effective.

[0223] For example, referring to Table 6, an example of a carrier-based SBFD configuration activation indication (SBFD configuration enabling, that is, a validity indication in the SBFD configuration information) in a multi-carrier case is shown.

[0224] Table 6

[0225] In one example, for the above-mentioned method 3, the fifth allocation indication is used to indicate whether the offset between the second carrier and the first carrier is effective. Based on this, the fifth allocation indication can also be used to implicitly indicate whether the SBFD configuration is effective. For example, if the fifth allocation indication is used to indicate that the offset between the second carrier and the first carrier is effective, the fifth allocation indication implicitly indicates that the SBFD frequency domain resources on the second carrier are effective. If the fifth allocation indication is used to indicate that the offset between the second carrier and the first carrier is not effective, the fifth allocation indication implicitly indicates that the SBFD frequency domain resources on the second carrier are not effective.

[0226] For example, see Table 7, which shows an example of a carrier-based ca-offset configuration activation indication (ca-offset enabling) in a multi-carrier scenario. The ca-offset configuration activation indication is used to indicate whether the offset (such as the time slot offset and / or the symbol offset) between the second carrier and the first carrier is effective or not, and the ca-offset configuration activation indication is used to indicate whether the SBFD frequency domain resource on the second carrier is effective or not.

[0227] Table 7

[0228] When the ca-offset configuration activation indication is used to indicate that the offset between the second carrier and the first carrier is effective, the offset between the second carrier and the first carrier (such as the time slot offset and / or symbol offset) may also be indicated. The offset for each carrier may be sent to the UE via an RRC message or pre-configured, or may be configured via a DCI message. A common set of offsets may be used for several carriers, or a separate offset may be configured for each carrier.

[0229] For example, taking the offset as a time slot offset, see Table 8, which shows the carrier-based ca-slotoffset configuration parameter (i.e., time slot offset) in a multi-carrier case.

[0230] Table 8

[0231] For refSCS15kHz, the time slot offset can be -2, -1, 0, 1, 2, where -2 means two time slots offset to the left, 2 means two time slots offset to the right, and so on. For refSCS30KHz, the time slot offset can be -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, and so on.

[0232] For example, taking the offset as a symbol offset, see Table 9, which shows the carrier-based ca-symboloffset configuration parameter (ie, symbol offset) in a multi-carrier case.

[0233] Table 9

[0234] The symbol offset can be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, or 13, and the symbol offset indicates the number of symbols shifted to the left or the number of symbols shifted to the right.

[0235] Sixth, in the case of multi-carrier, carrier-based SBFD frequency domain resource allocation and activation.

[0236] In one example, a base station can configure SBFD frequency domain resources within each of multiple carriers. The base station can send SBFD resource allocation information to the UE, where the SBFD resource allocation information indicates the SBFD frequency domain resources configured within each carrier. The SBFD frequency domain resources configured within each carrier include at least one set of opposite time slots within the carrier, which can include uplink time slots and downlink time slots.

[0237] Figure 5B shows a schematic diagram of multi-carrier SBFD frequency domain resource allocation. For each carrier in the multi-carrier system, SBFD frequency domain resources can be allocated within each carrier. For example, SBFD frequency domain resources can be allocated within CC1 and CC2.

[0238] In one example, before each carrier forms the SBFD frequency domain resources, the carriers have the same time slots. For example, the time slots in the carriers are DL slot, DL slot, DL slot, UL slot, and UL slot in sequence.

[0239] To create SBFD frequency-domain resources within a carrier, at least one set of opposite time slots exists within the carrier. For example, as shown in Figure 5B , time slot 0 of CC1 is a DL slot and a UL slot, time slot 1 of CC1 is a DL slot and a UL slot, time slot 2 of CC1 is a DL slot and a UL slot, time slot 3 of CC1 is a DL slot and a UL slot, and time slot 4 of CC1 is a DL slot and a UL slot. Time slot 0 of CC2 is a DL slot and a UL slot, time slot 1 of CC2 is a DL slot and a UL slot, time slot 2 of CC2 is a DL slot and a UL slot, time slot 3 of CC2 is a DL slot and a UL slot, and time slot 4 of CC2 is a DL slot and a UL slot.

[0240] This completes carrier-based SBFD frequency domain resource allocation. The base station configures SBFD frequency domain resources within each carrier and sends SBFD resource allocation information to the UE. The UE receives the SBFD resource allocation information, which indicates the SBFD frequency domain resources configured within each carrier.

[0241] After completing carrier-based SBFD frequency domain resource allocation, carrier-based SBFD frequency domain resources may also be activated or deactivated. For example, for each carrier, the base station may send SBFD configuration information corresponding to that carrier to the UE. The UE receives this SBFD configuration information, which indicates whether the SBFD frequency domain resources on that carrier are enabled or disabled. Activation indicates activation of the SBFD frequency domain resources on that carrier, while deactivation indicates deactivation of the SBFD frequency domain resources on that carrier.

[0242] For example, when the base station sends SBFD configuration information to the UE, for the third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

[0243] When the base station sends SBFD configuration information to the UE, for the fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

[0244] For example, if SBFD is configured for each carrier, the base station independently controls whether the SBFD configuration is effective for each carrier. If the base station deactivates a carrier via DCI, the SBFD configuration for that carrier becomes invalid. If the base station activates a carrier via DCI, the DL / UL configuration for that carrier takes effect, but the SBFD configuration for that carrier does not. A single bit can be used to indicate whether the SBFD configuration is effective. This allows the base station to flexibly control whether the SBFD configuration is effective based on the characteristics and number of users in the cell.

[0245] For example, the base station can send the SBFD configuration for each carrier to the UE via an RRC message. The base station can independently activate or deactivate the SBFD configuration for each carrier.

[0246] In summary, for carrier-based SBFD frequency domain resource allocation and activation, SBFD resource parameters can be independently configured for each carrier. Then, using the SBFD configuration activation / deactivation parameters introduced in the DCI message, the base station can flexibly control the SBFD configuration on each carrier.

[0247] As can be seen from the above technical solutions, flexible BWP configuration is used in multi-carriers, and flexible SBFD frequency domain resources (such as downlink frequency domain resources and uplink frequency domain resources) are configured for UEs through BWP to support data transmission in TDD systems. Resource utilization, network coverage and network capacity are improved, uplink transmission resources and cell coverage are increased, uplink transmission delay is reduced and uplink transmission capacity is increased. Without affecting the 5G system, flexible BWP configuration is used in multi-carriers, activation and switching can configure flexible DL / UL frequency domain resources for UEs to support simultaneous transmission and reception of base stations / UEs in TDD systems, which can increase uplink transmission resources and cell coverage, reduce transmission delay and increase uplink transmission capacity.

[0248] Based on the same inventive concept, a resource allocation device, a base station and a UE corresponding to the above-mentioned resource allocation method are also provided. Since the principles of solving the problem by the base station and the UE are similar to those of the resource allocation method, the implementation of the base station and the UE can refer to the implementation of the resource allocation method, and the repeated parts will not be repeated.

[0249] Based on the same application concept as the above method, this application proposes an example of a resource allocation device, which is applied to a base station. FIG6A is a schematic structural diagram of the device, and the device includes:

[0250] An acquisition module 611 is used to acquire BWP frequency domain resource configuration information; a sending module 612 is used to send the BWP frequency domain resource configuration information to a user equipment, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; the sending module 612 is also used to send a target BWP indication information to the user equipment, wherein the target BWP indication information is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table, wherein the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and based on the mapping relationship between the resource identifier and the SBFD frequency domain resource, determines the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between BWP indication information and BWP configuration pairs.

[0251] Based on the same application concept as the above method, this application proposes an example of a resource allocation device applied to a user equipment. FIG6B is a schematic structural diagram of the device, and the device includes:

[0252] The receiving module 621 is used to receive BWP frequency domain resource configuration information sent by the base station, and the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; the receiving module 621 is also used to receive target BWP indication information sent by the base station; the acquiring module 622 is used to acquire a target BWP configuration pair corresponding to the target BWP indication information from the acquired BWP activation configuration table, and the target BWP configuration pair includes a target BWP identifier and a target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair; the determining module 623 is used to determine the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair based on the mapping relationship between the resource identifier and the SBFD frequency domain resource.

[0253] In one example, the BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier. The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier. Alternatively, the uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier. Alternatively, the downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier. Alternatively, the uplink BWP identifier and the downlink BWP identifier both correspond to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier.

[0254] In one example, the BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier being different from the downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier. Alternatively, the BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier, and a second downlink BWP identifier, the first uplink BWP identifier being the same as the first downlink BWP identifier, the second uplink BWP identifier being the same as the second downlink BWP identifier, the first uplink BWP identifier being different from the second uplink BWP identifier, and the first downlink BWP identifier being different from the second downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier corresponding to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier corresponding to the second carrier identifier.

[0255] In one example, the SBFD frequency domain resource is a frequency domain resource configured within the carrier indicated by the carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to the BWP identifier. The SBFD frequency domain resource corresponding to the uplink BWP identifier is different from the SBFD frequency domain resource corresponding to the downlink BWP identifier, and the size of the SBFD frequency domain resource corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency domain resource corresponding to the downlink BWP identifier. The carriers indicated by different carrier identifiers are SBFD intra-subband carriers or SBFD inter-subband carriers.

[0256] In one example, for the base station, the sending module 612 is further configured to send the BWP activation configuration table to the user equipment via an RRC message. For the user equipment, the receiving module 621 is further configured to obtain the BWP activation configuration table pre-configured in the user equipment via the physical layer; or receive the BWP activation configuration table sent by the base station via an RRC message.

[0257] In one example, each BWP configuration pair in the BWP activation configuration table includes a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, and an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier. The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier, and the target downlink BWP identifier is the same as or different from the target uplink BWP identifier.

[0258] The target BWP configuration pair includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

[0259] In one example, each BWP configuration pair in the BWP activation configuration table includes a first configuration sub-pair and a second configuration sub-pair. The first configuration sub-pair includes a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, and a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier. The second configuration sub-pair includes a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, and a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier.

[0260] The target BWP configuration pair includes a target first configuration sub-pair and a target second configuration sub-pair. The target first configuration sub-pair includes a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier. The target first configuration sub-pair includes a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier.

[0261] The target second configuration subpair includes a target second downlink BWP identifier and a target second uplink BWP identifier, where the target second downlink BWP identifier is the same as or different from the target second uplink BWP identifier. The target second configuration subpair includes a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, where the carrier identifier corresponding to the target second downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

[0262] In one example, for the base station, the sending module 612 is specifically configured to send the target BWP indication information to the user equipment by: sending the BWP activation configuration to the user equipment via a DCI message; or sending the BWP activation configuration to the user equipment via a MAC-CE message; or sending the BWP activation configuration to the user equipment via an RRC message. For the user equipment, the receiving module 621 is specifically configured to receive the target BWP indication information sent by the base station by: receiving the BWP activation configuration sent by the base station via a DCI message; or receiving the BWP activation configuration sent by the base station via a MAC-CE message; or receiving the BWP activation configuration sent by the base station via an RRC message.

[0263] The BWP activation configuration includes the target BWP indication information and a switch flag. If the switch flag is a first value, the user equipment is instructed to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table. The acquisition module 622 is further configured to obtain a target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

[0264] If the switch flag is not the first value, it instructs the user equipment to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. The acquisition module 622 is further used to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. Or,

[0265] The BWP activation configuration includes the target BWP indication information. If the target BWP indication information is a target value, the user equipment is instructed to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. The acquisition module 622 is further configured to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

[0266] If the target BWP indication information is not a target value, the user equipment is instructed to obtain the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table. The acquisition module 622 is further configured to obtain the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

[0267] In one example, for a base station, the acquiring module 611 is further configured to, if the SBFD frequency domain resources used by the user equipment change within the BWP switching time, acquire updated target BWP indication information, where the updated target BWP indication information corresponds to the changed SBFD frequency domain resources. The sending module 612 is further configured to send the updated target BWP indication information to the user equipment, where the updated target BWP indication resource is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

[0268] For the user equipment, the receiving module 621 is also used to receive the updated target BWP indication information sent by the base station within the BWP switching time, and the updated target BWP indication information corresponds to the changed SBFD frequency domain resources; the acquisition module 622 is also used to obtain the target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

[0269] Based on the same application concept as the above method, an example of the present application proposes a resource allocation device, which is applied to a base station, and the device includes: an acquisition module, which is used to obtain SBFD resource allocation information; a sending module, which is used to send SBFD resource allocation information to a user equipment, wherein the SBFD resource allocation information is used to indicate the SBFD frequency domain resources configured for multiple carriers in a carrier group, or the SBFD frequency domain resources configured in each carrier among the multiple carriers; wherein, in the SBFD frequency domain resources configured for multiple carriers in the carrier group, there is at least one group of opposite time slots for different carriers in the carrier group; wherein, in the SBFD frequency domain resources configured in each carrier among the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein, the opposite time slots include uplink time slots and downlink time slots; the sending module is also used to send the SBFD configuration information corresponding to the carrier to the user equipment; wherein, the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are effective or invalid.

[0270] Based on the same application concept as the above method, an example of the present application proposes a resource allocation device, which is applied to a user equipment, and the device includes: a receiving module, which is used to receive SBFD resource allocation information sent by a base station, and the SBFD resource allocation information is used to indicate the SBFD frequency domain resources configured for multiple carriers in a carrier group, or the SBFD frequency domain resources configured in each carrier among the multiple carriers; wherein, in the SBFD frequency domain resources configured for multiple carriers in the carrier group, there is at least one group of opposite time slots for different carriers in the carrier group; wherein, in the SBFD frequency domain resources configured in each carrier among the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein, the opposite time slots include uplink time slots and downlink time slots; the receiving module is also used to receive SBFD configuration information corresponding to the carrier sent by the base station; wherein, the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are effective or invalid; and a determination module is used to determine whether the SBFD frequency domain resources on the carrier are effective or invalid based on the SBFD configuration information corresponding to the carrier.

[0271] In one example, the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers within a carrier group, including: the SBFD resource allocation information includes a first allocation indication and a second allocation indication, for each carrier in the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as flexible time slots, and the second allocation indication is used to indicate that each flexible time slot is used as an uplink time slot or a downlink time slot. Or,

[0272] The SBFD resource allocation information includes a third allocation indication. For each carrier among the multiple carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot.

[0273] Alternatively, the SBFD resource allocation information includes a fourth allocation indication and a fifth allocation indication. For a first carrier among multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot; for a second carrier other than the first carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

[0274] In an example, the fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is effective.

[0275] In one example, for a third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

[0276] In one example, for a fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are valid or not.

[0277] Based on the same application concept as the above method, a base station is proposed in an example of the present application, as shown in Figure 7A. The base station may include a processor 711 and a machine-readable storage medium 712, and the machine-readable storage medium 712 stores machine-executable instructions that can be executed by the processor 711; the processor 711 is used to execute the machine-executable instructions to implement the subband resource determination method disclosed in the above example of the present application.

[0278] In one example, the processor 711 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 711 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 711 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 711 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen.

[0279] In one example, the base station may optionally include a peripheral device interface 713 and at least one peripheral device. The processor 711 and the peripheral device interface 713 may be connected via a bus or signal lines. Each peripheral device may be connected to the peripheral device interface 713 via a bus, signal lines, or circuit boards. The peripheral device may include at least one of a radio frequency circuit 714 and a power supply 715.

[0280] The radio frequency circuit 714 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 714 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 714 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. Optionally, the radio frequency circuit 714 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a user identity module card, etc. The radio frequency circuit 714 can communicate with user equipment via at least one wireless communication protocol. Such wireless communication protocols include, but are not limited to, the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G, and 5G), a wireless local area network, and / or a WiFi (Wireless Fidelity) network.

[0281] The power supply 715 is used to supply power to various components in the base station. The power supply 715 can be alternating current, direct current, a disposable battery, or a rechargeable battery.

[0282] Based on the same application concept as the above method, a user equipment is proposed in an example of the present application, as shown in Figure 7B. The user equipment may include a processor 721 and a machine-readable storage medium 722, and the machine-readable storage medium 722 stores machine-executable instructions that can be executed by the processor 721; the processor 721 is used to execute the machine-executable instructions to implement the subband resource determination method disclosed in the above example of the present application.

[0283] In one example, the processor 721 may include one or more processing cores, such as a quad-core processor, an octal-core processor, etc. The processor 721 may be implemented in at least one hardware form selected from the group consisting of a DSP, an FPGA, and a PLA. The processor 721 may also include a main processor and a coprocessor.

[0284] In one example, the user device further includes a peripheral device interface 723 and at least one peripheral device. The processor 721 and the peripheral device interface 723 may be connected via a bus or signal lines. Each peripheral device may be connected to the peripheral device interface 723 via a bus, signal lines, or circuit boards. The peripheral device may include at least one of a radio frequency circuit 724, a touch screen display 725, a camera 726, and a power supply 727.

[0285] The radio frequency circuit 724 is used to receive and transmit RF signals, also known as electromagnetic signals. The radio frequency circuit 724 communicates with the communication network and other communication devices via electromagnetic signals. The radio frequency circuit 724 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. Optionally, the radio frequency circuit 724 includes an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a subscriber identity module card, and the like. The radio frequency circuit 724 can communicate with the base station via at least one wireless communication protocol. Such wireless communication protocols include, but are not limited to, the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks, a wireless local area network, and / or WiFi.

[0286] The display screen 725 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, and any combination thereof. When the display screen 725 is a touch screen display, the display screen 725 also has the ability to collect touch signals on or above the surface of the display screen 725. The touch signals can be input as control signals to the processor 721 for processing. In this case, the display screen 725 can also be used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards.

[0287] In some embodiments, the display screen 725 can be one, set on the front panel of the user device; in other embodiments, the display screen 725 can be at least two, set on different surfaces of the user device or in a folding design; in still other embodiments, the display screen 725 can be a flexible display screen, set on a curved surface or a folding surface of the user device. The display screen 725 can even be set into a non-rectangular irregular shape, that is, a special-shaped screen. The display screen 725 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0288] The camera assembly 726 is used to capture images or videos. Optionally, the camera assembly 726 includes a front camera and a rear camera. Typically, the front camera is set on the front panel of the user device, and the rear camera is set on the back of the user device. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, the fusion of the main camera and the wide-angle camera to realize panoramic shooting and VR (Virtual Reality) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 726 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cold light flash, which can be used for light compensation at different color temperatures.

[0289] Power supply 727 is used to power various components in the user device. Power supply 727 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 727 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0290] Based on the same application concept as the above method, an example of this application also provides a machine-readable storage medium, on which a number of computer instructions are stored. When the computer instructions are executed by a processor, the resource allocation method disclosed in the above example of this application can be implemented.

[0291] The machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, a storage drive (such as a hard disk drive), a solid-state drive, any type of storage disk (such as a CD, DVD, etc.), or similar storage media, or a combination thereof.

[0292] The systems, devices, modules, or units described in the above embodiments may be implemented by a computer entity or by a product having certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email transceiver, game console, tablet computer, wearable device, or any combination of these devices.

[0293] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included within the scope of the claims of the present application.

Claims

1. A resource allocation method, characterized in that: Applied to a base station, the method comprises: Sending BWP frequency domain resource configuration information to the user equipment, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; Sending target BWP indication information to the user equipment, wherein the target BWP indication information is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table, wherein the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and based on a mapping relationship between the resource identifier and the SBFD frequency domain resource, determining a target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair.

2. The method according to claim 1, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier, wherein: The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The uplink BWP identifier and the downlink BWP identifier correspond to the first carrier identifier at the same time, and the uplink BWP identifier and the downlink BWP identifier correspond to the second carrier identifier at the same time.

3. The method according to claim 1, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, and the uplink BWP identifier is different from the downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier and a second downlink BWP identifier, the first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier correspond to the second carrier identifier.

4. The method according to any one of claims 1 to 3, characterized in that: The SBFD frequency domain resource is a frequency domain resource configured in the carrier indicated by the carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to the BWP identifier; The SBFD frequency domain resources corresponding to the uplink BWP identifier are different from the SBFD frequency domain resources corresponding to the downlink BWP identifier, and the size of the SBFD frequency domain resources corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency domain resources corresponding to the downlink BWP identifier; The carriers indicated by different carrier identifiers are SBFD intra-subband carriers or SBFD inter-subband carriers.

5. The method according to claim 1, characterized in that Before sending the target BWP indication information to the user equipment, the method further includes: The BWP activation configuration table is sent to the user equipment through an RRC message.

6. The method according to claim 1 or 5, characterized in that: Each BWP configuration pair in the BWP activation configuration table includes a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier; The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier, and the target downlink BWP identifier is the same as or different from the target uplink BWP identifier; The target BWP configuration pair includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

7. The method according to claim 1 or 5, characterized in that: Each BWP configuration pair in the BWP activation configuration table includes a first configuration sub-pair and a second configuration sub-pair; the first configuration sub-pair includes a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier; the second configuration sub-pair includes a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier; Wherein, the target BWP configuration pair includes a target first configuration sub-pair and a target second configuration sub-pair; The target first configuration sub-pair includes a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier; the target first configuration sub-pair includes a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier; The target second configuration sub-pair includes a target second downlink BWP identifier and a target second uplink BWP identifier, and the target second downlink BWP identifier is the same as or different from the target second uplink BWP identifier; the target second configuration sub-pair includes a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, and the carrier identifier corresponding to the target second downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

8. The method according to claim 1, characterized in that: The sending the target BWP indication information to the user equipment includes: sending a BWP activation configuration to the user equipment through a DCI message; or sending a BWP activation configuration to the user equipment through a MAC-CE message; or sending a BWP activation configuration to the user equipment through an RRC message; wherein: The BWP activation configuration includes the target BWP indication information and a switch flag bit; if the switch flag bit is a first value, the user equipment is instructed to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table; if the switch flag bit is not the first value, the user equipment is instructed to prohibit obtaining a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table; Or, the BWP activation configuration includes the target BWP indication information; if the target BWP indication information is a target value, the user equipment is instructed to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; if the target BWP indication information is not a target value, the user equipment is instructed to obtain the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

9. The method according to claim 1, characterized in that: After sending the target BWP indication information to the user equipment, the method further includes: Within the BWP switching time, if the SBFD frequency domain resources used by the user equipment change, acquiring updated target BWP indication information, where the updated target BWP indication information corresponds to the changed SBFD frequency domain resources; The updated target BWP indication information is sent to the user equipment, where the updated target BWP indication resource is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

10. A resource allocation method, characterized in that: Applied to user equipment, the method includes: Receive BWP frequency domain resource configuration information sent by a base station, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; receiving the target BWP indication information sent by the base station, and acquiring a target BWP configuration pair corresponding to the target BWP indication information from the acquired BWP activation configuration table, wherein the target BWP configuration pair includes a target BWP identifier and a target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair; Based on the mapping relationship between the resource identifier and the SBFD frequency domain resource, the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair is determined.

11. The method according to claim 10, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier, wherein: The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The uplink BWP identifier and the downlink BWP identifier correspond to the first carrier identifier at the same time, and the uplink BWP identifier and the downlink BWP identifier correspond to the second carrier identifier at the same time.

12. The method according to claim 10, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, and the uplink BWP identifier is different from the downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier and a second downlink BWP identifier, the first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier correspond to the second carrier identifier.

13. The method according to any one of claims 10 to 12, characterized in that: The SBFD frequency domain resource is a frequency domain resource configured in the carrier indicated by the carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to the BWP identifier; The SBFD frequency domain resources corresponding to the uplink BWP identifier are different from the SBFD frequency domain resources corresponding to the downlink BWP identifier, and the size of the SBFD frequency domain resources corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency domain resources corresponding to the downlink BWP identifier; The carriers indicated by different carrier identifiers are SBFD intra-subband carriers or SBFD inter-subband carriers.

14. The method according to claim 10, characterized in that Before receiving the target BWP indication information sent by the base station, the method further includes: Acquire the BWP activation configuration table preconfigured in the user equipment through the physical layer; or, The BWP activation configuration table sent by the base station is received through an RRC message.

15. The method according to claim 10 or 14, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier; The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier. The identifier is the same as or different from the target uplink BWP identifier; The target BWP configuration pair includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

16. The method according to claim 10 or 14, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a first configuration sub-pair and a second configuration sub-pair; the first configuration sub-pair includes a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier; the second configuration sub-pair includes a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier; Wherein, the target BWP configuration pair includes a target first configuration sub-pair and a target second configuration sub-pair; The target first configuration sub-pair includes a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier; the target first configuration sub-pair includes a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier; The target second configuration sub-pair includes a target second downlink BWP identifier and a target second uplink BWP identifier, and the target second downlink BWP identifier is the same as or different from the target second uplink BWP identifier; the target second configuration sub-pair includes a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, and the carrier identifier corresponding to the target second downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

17. The method according to claim 10, characterized in that The receiving the target BWP indication information sent by the base station includes: receiving the BWP activation configuration sent by the base station through a DCI message; or, receiving the BWP activation configuration sent by the base station through a MAC-CE message; or, receiving the BWP activation configuration sent by the base station through an RRC message; wherein: The BWP activation configuration includes the target BWP indication information and a switch flag; If the switch flag bit is a first value, the user equipment obtains a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table; If the switch flag bit is not the first value, the user equipment is prohibited from obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; Or, the BWP activation configuration includes the target BWP indication information; If the target BWP indication information is a target value, the user equipment is prohibited from obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; If the target BWP indication information is not a target value, the user equipment obtains a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table.

18. The method according to claim 10, characterized in that After receiving the target BWP indication information sent by the base station, the method further includes: During the BWP switching time, receiving updated target BWP indication information sent by the base station, wherein the updated target BWP indication information corresponds to the changed SBFD frequency domain resources; and acquiring a target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

19. A resource allocation method, characterized in that: Applied to a base station, the method comprises: Sending SBFD resource allocation information to a user equipment, wherein the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured by multiple carriers in a carrier group, or SBFD frequency domain resources configured in each of the multiple carriers; wherein, in the SBFD frequency domain resources configured by multiple carriers in the carrier group, different carriers in the carrier group have at least one group of opposite time slots; in the SBFD frequency domain resources configured in each of the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein the opposite time slots include uplink time slots and downlink time slots; Sending SBFD configuration information corresponding to the carrier to the user equipment; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or ineffective.

20. The method according to claim 19, characterized in that The SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers in a carrier group, including: The SBFD resource allocation information includes a first allocation indication and a second allocation indication, and for each carrier among the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as Flexible time slots, and the second allocation indication is used to indicate that each Flexible time slot is used as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a third allocation indication, and for each carrier among the multiple carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a fourth allocation indication and a fifth allocation indication, and for a first carrier among multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot; for a second carrier other than the first carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

21. The method according to claim 20, characterized in that The fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is effective.

22. The method according to claim 19, characterized in that When sending the SBFD configuration information corresponding to the carrier to the user equipment, for a third carrier among the multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

23. The method according to claim 19, characterized in that When sending the SBFD configuration information corresponding to the carrier to the user equipment, for a fourth carrier among the multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

24. A resource allocation method, characterized in that: Applied to user equipment, the method includes: Receive SBFD resource allocation information sent by a base station, where the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers in a carrier group, or SBFD frequency domain resources configured in each of the multiple carriers; wherein, in the SBFD frequency domain resources configured for multiple carriers in the carrier group, different carriers in the carrier group have at least one group of opposite time slots; in the SBFD frequency domain resources configured in each of the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein the opposite time slots include uplink time slots and downlink time slots; SBFD configuration information corresponding to a carrier sent by the base station is received; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or ineffective.

25. The method according to claim 24, characterized in that The SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers in a carrier group, including: The SBFD resource allocation information includes a first allocation indication and a second allocation indication, and for each carrier among the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as Flexible time slots, and the second allocation indication is used to indicate that each Flexible time slot is used as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a third allocation indication, and for each carrier among the multiple carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a fourth allocation indication and a fifth allocation indication, and for a first carrier among multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot; for a second carrier other than the first carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

26. The method according to claim 25, characterized in that The fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is effective.

27. The method according to claim 24, characterized in that When receiving SBFD configuration information corresponding to the carrier sent by the base station, for a third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

28. The method according to claim 24, characterized in that When receiving the SBFD configuration information corresponding to the carrier sent by the base station, for a fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

29. A resource allocation device, characterized in that: Applied to a base station, the device comprises: An acquisition module is used to obtain BWP frequency domain resource configuration information; A sending module, configured to send BWP frequency domain resource configuration information to a user equipment, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; The sending module is further used to send target BWP indication information to the user equipment, and the target BWP indication information is used to enable the user equipment to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table, and the target BWP configuration pair includes a target BWP identifier and a target carrier identifier, and based on the mapping relationship between the resource identifier and the SBFD frequency domain resource, determines the target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair.

30. The device according to claim 29, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier, wherein: The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The uplink BWP identifier and the downlink BWP identifier correspond to the first carrier identifier at the same time, and the uplink BWP identifier and the downlink BWP identifier correspond to the second carrier identifier at the same time.

31. The device according to claim 29, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, and the uplink BWP identifier is different from the downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier and a second downlink BWP identifier, the first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, the second uplink BWP identifier and the second downlink BWP identifier correspond to the first carrier identifier, The second downlink BWP identifier corresponds to the second carrier identifier.

32. The device according to any one of claims 29 to 31, characterized in that The SBFD frequency domain resource is a frequency domain resource configured in the carrier indicated by the carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to the BWP identifier; The SBFD frequency domain resources corresponding to the uplink BWP identifier are different from the SBFD frequency domain resources corresponding to the downlink BWP identifier, and the size of the SBFD frequency domain resources corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency domain resources corresponding to the downlink BWP identifier; The carriers indicated by different carrier identifiers are SBFD intra-subband carriers or SBFD inter-subband carriers.

33. The device according to claim 29, characterized in that The sending module is further used to send the BWP activation configuration table to the user equipment through an RRC message.

34. The device according to claim 29 or 33, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier; The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier, and the target downlink BWP identifier is the same as or different from the target uplink BWP identifier; The target BWP configuration pair includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

35. The device according to claim 29 or 33, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a first configuration sub-pair and a second configuration sub-pair; the first configuration sub-pair includes a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier; the second configuration sub-pair includes a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier; Wherein, the target BWP configuration pair includes a target first configuration sub-pair and a target second configuration sub-pair; The target first configuration sub-pair includes a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier; the target first configuration sub-pair includes a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier; The target second configuration sub-pair includes a target second downlink BWP identifier and a target second uplink BWP identifier, and the target second downlink BWP identifier is the same as or different from the target second uplink BWP identifier; the target second configuration sub-pair includes a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, and the carrier identifier corresponding to the target second downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

36. The device according to claim 29, characterized in that When the sending module sends the target BWP indication information to the user equipment, it is specifically used to: send the BWP activation configuration to the user equipment through a DCI message; or send the BWP activation configuration to the user equipment through a MAC-CE message; or send the BWP activation configuration to the user equipment through an RRC message; wherein: The BWP activation configuration includes the target BWP indication information and a switch flag bit; if the switch flag bit is a first value, the user equipment is instructed to obtain a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table; if the switch flag bit is not the first value, the user equipment is instructed to prohibit obtaining a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table; Or, the BWP activation configuration includes the target BWP indication information; if the target BWP indication information is a target value, the user equipment is instructed to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; if the target BWP indication information is not a target value, the user equipment is instructed to obtain the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table.

37. The device according to claim 29, characterized in that The acquisition module is further configured to acquire updated target BWP indication information if the SBFD frequency domain resources used by the user equipment change within the BWP switching time, wherein the updated target BWP indication information corresponds to the changed SBFD frequency domain resources; The sending module is further used to send updated target BWP indication information to the user equipment, and the updated target BWP indication resource is used to enable the user equipment to obtain the target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

38. A resource allocation device, characterized in that: Applied to user equipment, the device comprises: A receiving module, configured to receive BWP frequency domain resource configuration information sent by a base station, wherein the BWP frequency domain resource configuration information includes a mapping relationship between a resource identifier and a SBFD frequency domain resource; wherein the resource identifier includes a BWP identifier and a carrier identifier; The receiving module is further used to receive the target BWP indication information sent by the base station; an acquisition module, configured to acquire a target BWP configuration pair corresponding to the target BWP indication information from the acquired BWP activation configuration table, wherein the target BWP configuration pair includes a target BWP identifier and a target carrier identifier; wherein the BWP activation configuration table includes a mapping relationship between the BWP indication information and the BWP configuration pair; The determination module is configured to determine, based on a mapping relationship between the resource identifier and the SBFD frequency domain resource, a target SBFD frequency domain resource associated with the target BWP identifier and the target carrier identifier in the target BWP configuration pair.

39. The device according to claim 38, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, the uplink BWP identifier is the same as the downlink BWP identifier, and the carrier identifier includes a first carrier identifier and a second carrier identifier, wherein: The uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The uplink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The downlink BWP identifier corresponds to the first carrier identifier, and the uplink BWP identifier and the downlink BWP identifier both correspond to the second carrier identifier; or, The uplink BWP identifier and the downlink BWP identifier correspond to the first carrier identifier at the same time, and the uplink BWP identifier and the downlink BWP identifier correspond to the second carrier identifier at the same time.

40. The device according to claim 38, characterized in that The BWP identifier includes an uplink BWP identifier and a downlink BWP identifier, and the uplink BWP identifier is different from the downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the uplink BWP identifier corresponds to the first carrier identifier, and the downlink BWP identifier corresponds to the second carrier identifier; or, The BWP identifier includes a first uplink BWP identifier, a first downlink BWP identifier, a second uplink BWP identifier and a second downlink BWP identifier, the first uplink BWP identifier is the same as the first downlink BWP identifier, the second uplink BWP identifier is the same as the second downlink BWP identifier, the first uplink BWP identifier is different from the second uplink BWP identifier, and the first downlink BWP identifier is different from the second downlink BWP identifier; the carrier identifier includes a first carrier identifier and a second carrier identifier, the first uplink BWP identifier and the first downlink BWP identifier correspond to the first carrier identifier, and the second uplink BWP identifier and the second downlink BWP identifier correspond to the second carrier identifier.

41. The device according to any one of claims 38 to 40, characterized in that The SBFD frequency domain resource is a frequency domain resource configured in the carrier indicated by the carrier identifier, and the SBFD frequency domain resource is a frequency domain resource corresponding to the BWP identifier; The SBFD frequency domain resources corresponding to the uplink BWP identifier are different from the SBFD frequency domain resources corresponding to the downlink BWP identifier, and the size of the SBFD frequency domain resources corresponding to the uplink BWP identifier is different from or the same as the size of the SBFD frequency domain resources corresponding to the downlink BWP identifier; The carriers indicated by different carrier identifiers are SBFD intra-subband carriers or SBFD inter-subband carriers.

42. The device according to claim 38, characterized in that The receiving module is further used to obtain the BWP activation configuration table pre-configured in the user equipment through the physical layer; or, receive the BWP activation configuration table sent by the base station through an RRC message.

43. The device according to claim 38 or 42, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a downlink BWP identifier and a carrier identifier corresponding to the downlink BWP identifier, an uplink BWP identifier and a carrier identifier corresponding to the uplink BWP identifier; The target BWP configuration pair includes a target downlink BWP identifier and a target uplink BWP identifier, and the target downlink BWP identifier is the same as or different from the target uplink BWP identifier; The target BWP configuration pair includes a carrier identifier corresponding to the target downlink BWP identifier and a carrier identifier corresponding to the target uplink BWP identifier. The carrier identifier corresponding to the target downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target uplink BWP identifier.

44. The device according to claim 38 or 42, characterized in that Each BWP configuration pair in the BWP activation configuration table includes a first configuration sub-pair and a second configuration sub-pair; the first configuration sub-pair includes a first downlink BWP identifier and a carrier identifier corresponding to the first downlink BWP identifier, a first uplink BWP identifier and a carrier identifier corresponding to the first uplink BWP identifier; the second configuration sub-pair includes a second downlink BWP identifier and a carrier identifier corresponding to the second downlink BWP identifier, a second uplink BWP identifier and a carrier identifier corresponding to the second uplink BWP identifier; Wherein, the target BWP configuration pair includes a target first configuration sub-pair and a target second configuration sub-pair; The target first configuration sub-pair includes a target first downlink BWP identifier and a target first uplink BWP identifier, and the target first downlink BWP identifier is the same as or different from the target first uplink BWP identifier; the target first configuration sub-pair includes a carrier identifier corresponding to the target first downlink BWP identifier and a carrier identifier corresponding to the target first uplink BWP identifier, and the carrier identifier corresponding to the target first downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target first uplink BWP identifier; The target second configuration sub-pair includes a target second downlink BWP identifier and a target second uplink BWP identifier, and the target second downlink BWP identifier is the same as or different from the target second uplink BWP identifier; the target second configuration sub-pair includes a carrier identifier corresponding to the target second downlink BWP identifier and a carrier identifier corresponding to the target second uplink BWP identifier, and the carrier identifier corresponding to the target second downlink BWP identifier is the same as or different from the carrier identifier corresponding to the target second uplink BWP identifier.

45. The device according to claim 38, characterized in that When the receiving module receives the target BWP indication information sent by the base station, it is specifically used to: receive the BWP activation configuration sent by the base station through a DCI message; or, receive the BWP activation configuration sent by the base station through a MAC-CE message; or, receive the BWP activation configuration sent by the base station through an RRC message; wherein: The BWP activation configuration includes the target BWP indication information and a switch flag; If the switch flag bit is the first value, the acquisition module is further used to acquire the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; If the switch flag bit is not the first value, the acquisition module is further used to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; Or, the BWP activation configuration includes the target BWP indication information; If the target BWP indication information is a target value, the acquisition module is further used to prohibit obtaining the target BWP configuration pair corresponding to the target BWP indication information from the BWP activation configuration table; If the target BWP indication information is not a target value, the acquisition module is further configured to acquire a target BWP configuration pair corresponding to the target BWP indication information from a BWP activation configuration table.

46. ​​The device according to claim 38, characterized in that The receiving module is further used to receive the updated target BWP indication information sent by the base station within the BWP switching time, and the updated target BWP indication information corresponds to the changed SBFD frequency domain resources; the acquisition module is further used to obtain the target BWP configuration pair corresponding to the updated target BWP indication information from the BWP activation configuration table.

47. A resource allocation device, characterized in that: Applied to a base station, the device comprises: An acquisition module, used to obtain SBFD resource allocation information; A sending module, configured to send SBFD resource allocation information to a user equipment, wherein the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured by multiple carriers in a carrier group, or SBFD frequency domain resources configured in each of the multiple carriers; wherein, in the SBFD frequency domain resources configured by multiple carriers in a carrier group, different carriers in the carrier group have at least one group of opposite time slots; and in the SBFD frequency domain resources configured in each of the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein the opposite time slots include uplink time slots and downlink time slots; The sending module is further used to send SBFD configuration information corresponding to the carrier to the user equipment; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resources on the carrier are effective or ineffective.

48. The device according to claim 47, characterized in that The SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers in a carrier group, including: The SBFD resource allocation information includes a first allocation indication and a second allocation indication, and for each carrier among the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as Flexible time slots, and the second allocation indication is used to indicate that each Flexible time slot is used as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a third allocation indication, and for each carrier among the multiple carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a fourth allocation indication and a fifth allocation indication, and for a first carrier among multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot; for a second carrier other than the first carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

49. The device according to claim 48, characterized in that The fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is effective.

50. The device according to claim 47, characterized in that When sending the SBFD configuration information corresponding to the carrier to the user equipment, for a third carrier among the multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

51. The device according to claim 47, characterized in that When sending the SBFD configuration information corresponding to the carrier to the user equipment, for a fourth carrier among the multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

52. A resource allocation device, characterized in that: Applied to user equipment, the device comprises: A receiving module, configured to receive SBFD resource allocation information sent by a base station, wherein the SBFD resource allocation information is used to indicate SBFD frequency domain resources configured by multiple carriers in a carrier group, or SBFD frequency domain resources configured in each of the multiple carriers; wherein, in the SBFD frequency domain resources configured by multiple carriers in the carrier group, different carriers in the carrier group have at least one group of opposite time slots; and in the SBFD frequency domain resources configured in each of the multiple carriers, there is at least one group of opposite time slots in the carrier; wherein the opposite time slots include uplink time slots and downlink time slots; The receiving module is further used to receive SBFD configuration information corresponding to the carrier sent by the base station; wherein the SBFD configuration information is used to indicate whether the SBFD frequency domain resource on the carrier is effective or invalid; The determination module is used to determine whether the SBFD frequency domain resources on the carrier are effective or ineffective based on the SBFD configuration information corresponding to the carrier.

53. The device according to claim 52, characterized in that The SBFD resource allocation information is used to indicate SBFD frequency domain resources configured for multiple carriers in a carrier group, including: The SBFD resource allocation information includes a first allocation indication and a second allocation indication, and for each carrier among the multiple carriers, the first allocation indication is used to configure all time slots included in the carrier as Flexible time slots, and the second allocation indication is used to indicate that each Flexible time slot is used as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a third allocation indication, and for each carrier among the multiple carriers, the third allocation indication is used to configure each time slot included in the carrier as an uplink time slot or a downlink time slot; Or, the SBFD resource allocation information includes a fourth allocation indication and a fifth allocation indication, and for a first carrier among multiple carriers, the fourth allocation indication is used to configure each time slot included in the first carrier as an uplink time slot or a downlink time slot; for a second carrier other than the first carrier, the fifth allocation indication is used to indicate the offset between the second carrier and the first carrier.

54. The device according to claim 53, characterized in that The fifth allocation indication is further used to indicate whether the offset between the second carrier and the first carrier is effective.

55. The device according to claim 52, characterized in that When receiving SBFD configuration information corresponding to the carrier sent by the base station, for a third carrier among multiple carriers, if the SBFD configuration information includes a deactivation indication of the third carrier, the deactivation indication is used to deactivate the third carrier, and the deactivation indication is used to indicate that the SBFD frequency domain resources on the third carrier are invalid.

56. The device according to claim 52, characterized in that When receiving the SBFD configuration information corresponding to the carrier sent by the base station, for a fourth carrier among multiple carriers, if the SBFD configuration information includes an activation indication and a validity indication of the fourth carrier, the activation indication is used to activate the fourth carrier, and the validity indication is used to indicate whether the SBFD frequency domain resources on the fourth carrier are effective or not.

57. A base station, characterized in that: include: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; The processor is used to execute machine executable instructions to implement the method described in any one of claims 1-9 and 19-23.

58. A user equipment, characterized in that: include: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; The processor is used to execute machine executable instructions to implement the method described in any one of claims 10-18 and 24-28.

Images