Communication indication method, terminal, and access network device

Abstract

The present disclosure relates to a communication indication method, a terminal, and an access network device. The method comprises: acquiring an uplink (UL) subband configured by an access network device, and determining a frequency domain resource allocation (FDRA) field in downlink control information (DCI) used for scheduling a physical uplink shared channel (PUSCH) transmitted in the UL subband; and according to the FDRA field, determining a frequency domain resource used for uplink transmission in the UL subband. Communication efficiency is effectively improved.

Description

Communication indication methods, terminals and access network equipment Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication indication methods, terminals and access network equipment. Background Technology

[0002] The Release-18 (Rel-18) full-duplex enhancement project will study full-duplex solutions, such as enabling the network to simultaneously receive and transmit data within a single time slot. Currently, 3GPP has determined that the full-duplex enhancements in Rel-18 only apply to the base station, while the terminal side still only supports half-duplex, resulting in reduced communication efficiency.

[0003] Summary of the Invention

[0004] To address the problem of low communication efficiency in related technologies, embodiments of this disclosure propose a communication indication method, a terminal, and an access network device.

[0005] According to a first aspect of the present disclosure, a communication indication method is provided, the method comprising:

[0006] Determine the uplink subband (UL).

[0007] Receive downlink control information (DCI), which is used to schedule the physical uplink shared channel (PUSCH) transmitted in the UL subband;

[0008] The uplink frequency domain resources are determined based on the DCI, and the uplink frequency domain resources are the resources in the UL Subband used for uplink transmission.

[0009] The solution disclosed herein improves communication efficiency.

[0010] According to a second aspect of the embodiments of this disclosure, a communication indication method is provided, the method comprising:

[0011] Configure the uplink subband (UL) for the terminal;

[0012] A DCI is sent, which is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, which are resources in the UL subband used for uplink transmission.

[0013] According to a third aspect of the embodiments of this disclosure, a communication indication method is provided, the method comprising:

[0014] Network devices configure uplink subband (UL) for terminals;

[0015] The terminal determines the uplink subband UL Subband.

[0016] The network device sends a DCI, which is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband.

[0017] The terminal receives the DCI and determines the uplink frequency domain resources based on the DCI. The uplink frequency domain resources are the resources in the UL Subband used for uplink transmission.

[0018] According to a fourth aspect of the embodiments of this disclosure, a terminal is provided, comprising:

[0019] One or more processors;

[0020] The terminal is used to execute the method described in any one of the first aspects.

[0021] According to a fifth aspect of the embodiments of this disclosure, an access network device is provided, comprising:

[0022] One or more processors;

[0023] The access network device is used to perform the method described in any one of the second aspects.

[0024] According to a sixth aspect of the present disclosure, a communication system is provided, including a terminal and an access network device, wherein the terminal is configured to implement the method described in any one of the first aspects, and the access network device is configured to implement the method described in any one of the second aspects.

[0025] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform the method as described in any one of the first or second aspects. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0027] Figure 1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0028] Figure 1B is a schematic diagram of the frequency domain relationship between the UL subband and ULBWP configured in a base station in one possible embodiment.

[0029] Figure 1C is a schematic diagram of the frequency domain relationship between the UL subband and ULBWP configured in a base station in one possible embodiment.

[0030] Figure 2 is an exemplary interactive schematic diagram of a communication instruction method provided according to an embodiment of the present disclosure.

[0031] Figure 3A is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0032] Figure 3B is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0033] Figure 4A is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0034] Figure 4B is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0035] Figure 5 is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0036] Figure 6 is a flowchart illustrating a communication instruction method according to an embodiment of the present disclosure.

[0037] Figure 7A is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure.

[0038] Figure 7B is a schematic diagram of the structure of the access network device proposed in an embodiment of this disclosure.

[0039] Figure 8A is a schematic diagram of the structure of the communication device 8100 proposed in an embodiment of this disclosure.

[0040] Figure 8B is a schematic diagram of the structure of chip 8200 proposed in an embodiment of this disclosure.

[0041] Figure 9A is a schematic diagram of a BWP according to an embodiment of the present disclosure.

[0042] Figure 9B is a schematic diagram of a BWP according to an embodiment of the present disclosure.

[0043] Figure 9C is a schematic diagram of the BWP and UL Subband according to an embodiment of the present disclosure.

[0044] Figure 9D is a schematic diagram of the BWP and UL Subband according to an embodiment of the present disclosure. Detailed Implementation

[0045] This disclosure presents a communication indication method, a terminal, and an access network device.

[0046] In a first aspect, embodiments of this disclosure propose a communication indication method, the method comprising: determining an uplink subband (UL Subband); receiving downlink control information (DCI), the DCI being used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL Subband; and determining uplink frequency domain resources based on the DCI, the uplink frequency domain resources being resources in the UL Subband used for uplink transmission.

[0047] In the above embodiments, the terminal can determine the resources in the UL Subband used for uplink transmission, thus providing a solid technical foundation for achieving full-duplex operation. Furthermore, since the uplink frequency domain applied in the downlink slot is implemented by DCI, no new signaling is introduced, ensuring backward compatibility with existing standards and reducing the technical complexity of the terminal implementation.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine uplink frequency domain resources.

[0049] In the above embodiments, the terminal can determine uplink frequency domain resources based on the FDRA field allocated in the DCI, providing the necessary conditions for realizing full-duplex communication. Furthermore, since the FDRA field in the DCI is utilized, no new information or indication fields are added to the DCI, thus not increasing the DCI's occupation of communication resources and saving communication resources.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, determining uplink frequency domain resources based on DCI includes: determining uplink frequency domain resources according to a bitmap in the FDRA domain, wherein the uplink frequency domain resources include a set of resource blocks (RBG), and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resources.

[0051] In the above embodiments, the terminal can use the Bitmap in the FDRA field to indicate the RBG index corresponding to the RBG in the uplink frequency domain resource, providing the necessary conditions for realizing full-duplex communication. Furthermore, by utilizing the Bitmap to indicate the RBG index corresponding to the RBG, the corresponding RBG can be accurately indicated, improving the accuracy of determining the uplink frequency domain resource.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, determining uplink frequency domain resources based on the bitmap in the FDRA domain includes: mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the largest RBG index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence; or, mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the smallest RBG index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence.

[0053] In the above embodiments, the terminal can map the Bitmap in the FDRA domain to the RBG Index corresponding to the RBG in the UL BWP, providing the necessary conditions for realizing full-duplex communication. Furthermore, by using the Bitmap to indicate the RBG Index corresponding to the RBG, the corresponding RBG can be accurately indicated, improving the accuracy of determining uplink frequency domain resources in the UL BWP and avoiding resource waste.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, determining uplink frequency domain resources based on the bitmap in the FDRA domain further includes: mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the largest RBG index in the UL Subband, and mapping the other bits in the bitmap to other RBGs in sequence; or, mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the smallest RBG index in the UL Subband, and mapping the other bits in the bitmap to other RBGs in sequence.

[0055] In the above embodiments, the terminal can map the Bitmap in the FDRA domain to the RBG Index corresponding to the RBG in the UL Subband one-to-one, providing the necessary conditions for realizing full-duplex communication. Furthermore, since the Bitmap is used to indicate the RBG Index corresponding to the RBG, the corresponding RBG can be accurately indicated, improving the accuracy of determining uplink frequency domain resources in the UL Subband and avoiding resource waste.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission.

[0057] In the above embodiments, the terminal can determine the RBG corresponding to the position encoded as 1 in the Bitmap in the FDRA domain, providing a foundation for realizing full-duplex communication. Furthermore, since the encoded value of a specific position in the Bitmap is used to indicate whether the corresponding RB is used for uplink transmission, the RBG used for uplink transmission can be accurately indicated, improving the accuracy of the indication.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the Bitmap indicates a first frequency domain resource that is not located in the frequency domain range of the UL Subband, and the first RBG does not belong to the uplink frequency domain resource.

[0059] In the above embodiments, the terminal can use a Bitmap to determine a first frequency domain resource that is not located within the frequency domain range of the UL Subband, providing a foundation for realizing full-duplex communication. Furthermore, since the first frequency domain resource is not located within the frequency domain range of the UL Subband, its use can be avoided, preventing waste of communication resources and improving communication resource utilization.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining the RBG index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP based on the active uplink bandwidth portion Active UL BWP; or determining the RBG index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP based on the initial uplink bandwidth portion Initial UL BWP.

[0061] In the above embodiments, the terminal can determine the RBG Index corresponding to the RBG, providing the necessary conditions for realizing full-duplex communication. Furthermore, by utilizing the Active UL BWP and Initial UL BWP without introducing a new ULBWP, it is backward compatible with existing standards, reducing the technical complexity of the terminal implementation.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining the granularity of RBGs in the uplink bandwidth portion of the UL BWP based on the size of the Active UL BWP; or, determining the granularity of RBGs in the UL Subband based on the size of the Active UL BWP.

[0063] In the above embodiments, the terminal can determine the granularity of the RBG, providing the necessary conditions for realizing full-duplex communication. Furthermore, by utilizing the size of the Active UL BWP to determine the granularity of the RBG, it achieves backward compatibility with existing standards and reduces the technical complexity of the terminal implementation.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency domain resource allocation type for uplink transmission is resource allocation mode 0RAtype0.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI is any one of the following: DCI format 0-0; DCI format 0-1; DCI format 0-2; DCI format 0-3.

[0066] Secondly, embodiments of this disclosure propose a communication indication method, which includes: configuring an uplink subband (UL subband) for a terminal; and sending a DCI, wherein the DCI is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, which are resources in the UL subband used for uplink transmission.

[0067] In the above embodiments, the network device configures the UL Subband resources for uplink transmission for the terminal, thereby providing a solid technical foundation for achieving full-duplex operation. Furthermore, since the uplink frequency domain applied in the downlink slot is implemented by DCI, no new signaling is introduced, ensuring backward compatibility with existing standards and reducing the technical complexity of the network device implementation.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine uplink frequency domain resources.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, a bitmap in the FDRA domain is used to determine uplink frequency domain resources, wherein the uplink frequency domain resources include a set of resource blocks (RBG), and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resources.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the correspondence between the bitmap in the FDRA domain and the uplink frequency domain resources includes: mapping the highest bit of the bitmap in the FDRA domain to the RBG with the largest RBG Index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence; or, mapping the highest bit of the bitmap in the FDRA domain to the RBG with the smallest RBG Index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the correspondence between the bitmap in the FDRA domain and the uplink frequency domain resources further includes:

[0072] The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the largest RBG Index in the UL Subband, and the other bits in the bitmap are mapped to the other RBGs in sequence; or, the highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL Subband, and the other bits in the Bitmap are mapped to the other RBGs in sequence.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the Bitmap indicates a first frequency domain resource that is not located in the frequency domain range of the UL Subband, and the first RBG does not belong to the uplink frequency domain resource.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the RBG Index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP is determined by the active uplink bandwidth portion Active UL BWP; or, the RBG Index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP is determined by the initial uplink bandwidth portion Initial UL BWP.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: determining the granularity of RBGs in the uplink bandwidth portion of the UL BWP based on the size of the Active UL BWP; or, determining the granularity of RBGs in the UL Subband based on the size of the Active UL BWP.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the frequency domain resource allocation type for uplink transmission is resource allocation mode 0RAtype0.

[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI is any one of the following: DCI format 0-0; DCI format 0-1; DCI format 0-2; DCI format 0-3.

[0079] Thirdly, embodiments of this disclosure propose a communication indication method, the method comprising: a network device configuring an uplink subband (UL subband) for a terminal; the terminal determining the uplink subband (UL subband); the network device sending a Direct Access Channel (DCI), the DCI being used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband; the terminal receiving the DCI and determining uplink frequency domain resources based on the DCI, the uplink frequency domain resources being resources in the UL subband used for uplink transmission.

[0080] In conjunction with some embodiments of the third aspect, in some embodiments, the DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine uplink frequency domain resources.

[0081] In conjunction with some embodiments of the third aspect, in some embodiments, determining uplink frequency domain resources based on DCI includes: the terminal determining uplink frequency domain resources according to a bitmap in the FDRA domain, wherein the uplink frequency domain resources include a set of resource blocks (RBG), and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resources.

[0082] In conjunction with some embodiments of the third aspect, in some embodiments, determining uplink frequency domain resources based on the bitmap in the FDRA domain includes: the terminal mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the largest RBG index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence; or, the terminal mapping the most significant bit of the bitmap in the FDRA domain to the RBG with the smallest RBG index in the UL BWP, and mapping the other bits in the bitmap to other RBGs in sequence.

[0083] In conjunction with some embodiments of the third aspect, in some embodiments, determining uplink frequency domain resources based on the bitmap in the FDRA domain further includes: the terminal mapping the highest bit of the bitmap in the FDRA domain to the RBG with the largest RBG index in the UL Subband, and mapping the other bits in the bitmap to other RBGs in sequence; or, the terminal mapping the highest bit of the bitmap in the FDRA domain to the RBG with the smallest RBG index in the UL Subband, and mapping the other bits in the bitmap to other RBGs in sequence.

[0084] In conjunction with some embodiments of the third aspect, in some embodiments, the RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the Bitmap indicates a first frequency domain resource that is not located in the frequency domain range of the UL Subband, and the first RBG does not belong to the uplink frequency domain resource.

[0086] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: the terminal determining the RBG index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP based on the active uplink bandwidth portion Active UL BWP; or, the terminal determining the RBG index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP based on the initial uplink bandwidth portion Initial UL BWP.

[0087] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: determining the granularity of RBG in the uplink bandwidth portion of the UL BWP based on the size of the Active UL BWP; or, determining the granularity of RBG in the UL Subband based on the size of the Active UL BWP.

[0088] In conjunction with some embodiments of the third aspect, in some embodiments, the frequency domain resource allocation type for uplink transmission is resource allocation mode 0RAtype0.

[0089] In conjunction with some embodiments of the third aspect, in some embodiments, the DCI is any one of the following: DCI format 0-0; DCI format 0-1; DCI format 0-2; DCI format 0-3.

[0090] Fourthly, embodiments of this disclosure propose a terminal, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute the optional implementation of the first aspect.

[0091] Fifthly, embodiments of this disclosure provide an access network device, which includes at least one of a transceiver module and a processing module; wherein the access network device is used to execute the optional implementation of the second aspect.

[0092] In a sixth aspect, embodiments of this disclosure provide a terminal, which includes one or more processors; wherein the terminal is used to execute an optional implementation of the first aspect.

[0093] In a seventh aspect, embodiments of this disclosure provide an access network device, which includes one or more processors; wherein the access network device is configured to perform an optional implementation of the second aspect.

[0094] Eighthly, embodiments of this disclosure provide a communication system comprising: a terminal and an access network device; wherein the terminal is configured to perform the method described in the optional implementations of the first, fourth, and sixth aspects, and the access network device is configured to perform the method described in the optional implementations of the second, fifth, and seventh aspects.

[0095] Ninthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional implementations of the first, second, and third aspects.

[0096] In a tenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementations of the first, second, and third aspects.

[0097] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in optional implementations of the first, second, and third aspects.

[0098] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first, second, and third aspects above.

[0099] It is understood that the aforementioned terminals, access network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0100] This disclosure provides a communication indication method, a terminal, and an access network device. In some embodiments, the terms "communication indication method" and "information processing method" or "communication method" can be used interchangeably; the terms "communication indication device" and "information processing device" or "communication device" can be used interchangeably; and the terms "information processing system" or "communication system" can be used interchangeably.

[0101] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0102] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0103] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0104] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0105] In the embodiments disclosed herein, "multiple" refers to two or more.

[0106] In some embodiments, the terms “at least one (at least one item, at least one)”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0107] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0108] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0109] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0110] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0111] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0112] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0113] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

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

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

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

[0117] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0119] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0120] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes a terminal 101 and an access network device 102.

[0121] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

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

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

[0124] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0125] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0126] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0127] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0128] In one possible embodiment, in a full-duplex communication scheme, the network side can simultaneously transmit and receive data within a single time slot. The full-duplex enhancement only applies to the gNB, while the terminal side still only supports half-duplex. The gNB can configure an uplink (UL) subband for uplink data transmission within a downlink (DL) time slot for full-duplex terminals and schedule the terminal's uplink data transmission within the time-frequency range of the UL subband. Generally, the size and frequency domain location of the uplink subband (UL) configured by the base station differ from the active UL bandwidth portion (BWP).

[0129] Figure 1B is a schematic diagram of the frequency domain relationship between the UL subband and ULBWP configured in a possible embodiment. As shown in Figure 1B, the frequency domain range occupied by the UL subband is completely contained within the frequency domain range of the ULBWP in multiple subband full duplex (SBFD) time slots.

[0130] Figure 1C is a schematic diagram of the frequency domain relationship between the UL subband and ULBWP configured in a possible embodiment. As shown in Figure 1C, in multiple subband full duplex (SBFD) time slots, the frequency domain range occupied by the UL subband is not completely included within the frequency domain range of the ULBWP, and a part of the UL subband exceeds the frequency domain range of the ULBWP.

[0131] In one possible embodiment, it was concluded regarding the transmission behavior of the SBFD-aware UE on the UL subband that the terminal does not expect to send uplink information outside the active UL BWP.

[0132] In one possible embodiment, the base station indicates the frequency domain resources occupied by the uplink data channel transmission through the Frequency Domain Resource Assignment (FDRA) field included in the downlink control information (DCI). The FDRA field indicates the frequency domain resources within the UL BWP.

[0133] In one possible embodiment, when the base station is configured with a Type 1 configured grant for transmission, the frequency domain resources occupied by the corresponding Physical Uplink Shared Channel (PUSCH) transmission need to be configured within the UL BWP.

[0134] In one possible embodiment, for other types of uplink transmissions, such as PUCCH, Sounding Reference Signal (SRS), the transmission resources also need to be configured within the frequency domain of the UL BWP.

[0135] However, since UL subband and UL BWP are not necessarily aligned in the frequency domain, when uplink transmission occurs on different slots, the available frequency domain resources differ if the slot contains SBFD slots and non-SBFD slots (non-subband full-duplex time slots). Currently, there is no clear solution for indicating uplink frequency domain resources on different slots using the same frequency domain resource indication information.

[0136] Figure 2 is a schematic diagram of the interaction of a communication system according to an embodiment of the present disclosure. As shown in Figure 2, the present disclosure relates to a communication indication method, which includes:

[0137] Step S2101: Terminal 101 sends capability indication information.

[0138] In some embodiments, the access network device 102 receives capability indication information.

[0139] In some embodiments, capability indication information is used to indicate that terminal 101 has half-duplex capability.

[0140] In some embodiments, capability indication information is used to indicate that terminal 101 has full-duplex capability.

[0141] In some embodiments, the capability indication information is used to indicate that the terminal 101 has either half-duplex capability or full-duplex capability.

[0142] In some embodiments, capability indication information is used to indicate that terminal 101 supports uplink communication on a subband full-duplex SBFD time slot.

[0143] In step S2102, network device 102 sends first information to terminal 101.

[0144] In some embodiments, terminal 101 receives first information.

[0145] In some embodiments, the first information is used to configure UL subband for terminal 101.

[0146] In some embodiments, the name of the first information is not limited, and it may be, for example, “UL subband configuration information”.

[0147] In some embodiments, the first information includes one or more fields that indicate the time-domain location and / or frequency-domain location of the UL subband.

[0148] In some embodiments, the UL subband can be configured semi-statically or dynamically, that is, the first information can be configured semi-statically or dynamically. When the first information is dynamically configured, the time-domain position and / or frequency-domain position of the UL subband is activated or deactivated based on the semi-static configuration. The first information can be a MAC CE.

[0149] In some embodiments, the frequency domain location or time domain location of the UL subband is known, for example, the frequency domain location or time domain location is statically configured. In this case, the first information is used to configure the non-statically configured time domain location or frequency domain location of the UL subband.

[0150] Step 2101 is an optional step; for example, both the frequency domain position and the time domain position are statically configured.

[0151] In some embodiments, when the access network device 102 is conducting full-duplex communication with the terminal 101, it sends first information.

[0152] In some embodiments, when performing full-duplex communication, the access network device 102 can simultaneously send and receive data within a single slot.

[0153] In some embodiments, the first information may be RRC signaling, MAC CE, or dynamic indication signaling.

[0154] In step S2103, terminal 101 determines the UL subband based on the first information.

[0155] In some embodiments, terminal 101 reads a specific field from the first information.

[0156] In some embodiments, terminal 101 determines the UL subband based on a specific field in the first information.

[0157] In some embodiments, terminal 101 reads a specific indication field from the first information.

[0158] In some embodiments, terminal 101 determines the UL subband based on a value in a specific indication field.

[0159] In some embodiments, terminal 101 receives first information via PDSCH or PDCCH.

[0160] In some embodiments, the first information may be carried by any one of the following signaling: RRC signaling, MAC CE, and dynamic indication signaling.

[0161] In step S2104, network device 102 sends second information to terminal 101.

[0162] In some embodiments, terminal 101 receives second information.

[0163] In some embodiments, the second information is used to schedule uplink transmissions.

[0164] In some embodiments, the second information is used to indicate "frequency domain resources in the UL subband used for uplink transmission".

[0165] In some embodiments, the name of the second information is not limited, and it may be, for example, "frequency domain resource configuration information".

[0166] In some embodiments, the second information includes the "FDRA domain".

[0167] In some embodiments, network device 102 sends a DCI, which includes second information.

[0168] In some embodiments, a bitmap in the FDRA domain is used to determine uplink frequency domain resources, wherein the uplink frequency domain resources include a set of resource blocks (RBG), and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resources.

[0169] In some embodiments, uplink frequency domain resources include: resource blocks (RBs), physical resource blocks (PRBs), PRB pairs, RB pairs, resource elements (REs), and other related frequency domain resources.

[0170] In some embodiments, terminal 101 receives the DCI described above. The DCI may be, for example, DCI format 0-0, DCI format 0-1, DCI format 0-2, or DCI format 0-3, but is not limited to these, and may also be any other DCI used for scheduling uplink transmission.

[0171] In some embodiments, the RBG index corresponding to the Resource Block Group (RBG) in the Active UL BWP is determined based on the active uplink bandwidth portion. Optionally, a unique RBGIndex is assigned to each RBG.

[0172] In some embodiments, the RBG Index corresponding to the Resource Block Set (RBG) in the Initial UL BWP is determined based on the Initial Uplink Bandwidth Part (UL BWP).

[0173] In some embodiments, the DCI format used for scheduling uplink transmissions has a fixed size and does not change depending on the slot type in which the uplink transmission it schedules is located.

[0174] In some embodiments, uplink transmission may be performed within the UL subband of the SBFD slot, or within the active UL BWP of the non-SBFD slot.

[0175] In some embodiments, the frequency domain resource allocation type for uplink transmission is Resource Assignment (RA) type 0.

[0176] In some embodiments, the allocation method of RAtype0 includes: the base station indicating the resource block set RBG for uplink transmission through the FDRA field in the DCI.

[0177] In some embodiments, the FDRA field includes a bitmap. The bitmap is used to indicate the RBG index corresponding to the RBG. These indicated RBGs are uplink frequency domain resources used by the terminal, or these indicated RBGs include uplink frequency domain resources used by the terminal.

[0178] In some embodiments, the granularity of the RBG in the UL BWP is determined by the size of the Active UL BWP.

[0179] In some embodiments, granularity refers to the number of RBs in the RBG.

[0180] In some embodiments, an RBG contains multiple resource blocks (RBs), and the specific number of RBs contained in each RBG is associated with the number of RBs contained in a BWP, as shown in Table 1:

[0181] Table 1

[0182] Optionally, when the number of RBs in the BWP is between 1 and 36, in configuration 1, each RBG contains 2 RBs, and the granularity of the RBG is 2 RBs; in configuration 2, each RBG contains 4 RBs, and the granularity of the RBG is 4 RBs.

[0183] In some embodiments, the frequency domain resources used for uplink transmission within the UL Subband are a set of resource blocks (RBGs), which are determined by a bitmap in the FDRA domain.

[0184] In some embodiments, the correspondence between RBG and Bitmap in the FDRA field includes: the highest bit of Bitmap in the FDRA field corresponds to the RBG with the largest RBG Index in UL BWP, and the other bits in Bitmap are mapped one-to-one with other RBGs in sequence; or, the highest bit of Bitmap in the FDRA field corresponds to the RBG with the smallest RBG Index in UL BWP, and the other bits in Bitmap are mapped one-to-one with other RBGs in sequence.

[0185] In some embodiments, the correspondence between RBG and Bitmap in the FDRA field includes: the highest bit of Bitmap in the FDRA field corresponds to the RBG with the largest RBG Index in the UL Subband, and the other bits in Bitmap are mapped one-to-one with other RBGs in sequence; or, the highest bit of Bitmap in the FDRA field corresponds to the RBG with the smallest RBG Index in the UL Subband, and the other bits in Bitmap are mapped one-to-one with other RBGs in sequence.

[0186] In some embodiments, the RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission, while the RBG corresponding to the position encoded as 0 in the Bitmap is not used for uplink transmission.

[0187] In some embodiments, the RBG corresponding to the position encoded as 0 in the Bitmap is used for uplink transmission, while the RBG corresponding to the position encoded as 1 in the Bitmap is not used for uplink transmission.

[0188] In some embodiments, if the frequency domain resources indicated by the Bitmap are outside the frequency domain range of the UL Subband, then the resources included in the UL Subband are used for uplink transmission, that is, the frequency domain resources not included in the frequency domain range of the UL Subband are not used for uplink transmission.

[0189] In some embodiments, terminal 101 has half-duplex capability, or full-duplex capability.

[0190] In some embodiments, in this embodiment, it is assumed that network device 102 transmits uplink data via DCI format 0-0, DCI format 0-1, DCI format 0-2, DCI format 0-3, or any other DCI scheduling terminal 101 used for scheduling uplink transmissions. The uplink transmission may be within the UL subband of an SBFD Slot or within the active UL BWP of a non-SBFD Slot; this patent does not impose any limitations.

[0191] Optionally, terminal 101 is a SBFD Aware UE that is aware of sub-band full-duplex.

[0192] Optionally, the FDRA field in the DCI used for uplink scheduling is determined based on the Active UL BWP or the Initial UL BWP. In summary, the DCI format used for scheduling uplink transmissions has a fixed size and does not change based on the slot type of the uplink transmission it schedules.

[0193] Optionally, the uplink frequency domain resource allocation type is RA type 0, meaning that network device 102 indicates the RBG used for uplink transmission through the FDRA field (Bitmap) in the DCI. In this embodiment, it is assumed that the RBG is still determined based on the size of the Active BWP. Two examples are shown in the figure below. That is, regardless of the relative relationship between the UL subband and the Active UL BWP, the granularity of the RBG is determined based on the Active UL BWP.

[0194] Optionally, the resource allocation of the SBFD Aware UE on the UL Subband includes: the most significant bit in the FDRA corresponds to the RBG with the largest RBG index in the UL BWP, or the most significant bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL BWP. The other bits are mapped one-to-one with the remaining RBGs.

[0195] Optionally, the resource allocation of the SBFD Aware UE on the UL Subband includes: the highest bit in the FDRA corresponds to the RBG with the largest RBG index in the UL Subband, or the highest bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL Subband. The other bits are mapped one-to-one with the remaining RBGs.

[0196] Optionally, the Active UL BWP contains 10 RBGs. Assume network device 102 schedules uplink transmission for the SBFD Aware UE on the UL subband within the SBFD slot. Assume the Bitmap in the FDRA information field of the DCI is 1110000000 or 0000111000, respectively indicating that the corresponding RBG#0, RBG#1, RBG#2 or RBG#4, RBG#5, RBG#6 in the active UL BWP are used for uplink transmission. Correspondingly, terminal 101 determines the resource location within the UL subband for uplink transmission based on the indication.

[0197] Optionally, if terminal 101 believes that the frequency domain resources indicated by the bitmap exceed the frequency domain range of the UL subband, only the resources included in the UL subband are used for the corresponding uplink transmission.

[0198] In step S2105, terminal 101 determines the UL subband intermediate frequency domain resources based on the second information.

[0199] The determination of UL subband mid-frequency domain resources by terminal 101 based on the second information can be referred to in step S2103 and other textual descriptions above, and will not be repeated here.

[0200] Optionally, if terminal 101 believes that the frequency domain resources indicated by the bitmap exceed the frequency domain range of the UL subband, only the resources included in the UL subband are used for the corresponding uplink transmission.

[0201] In some embodiments, after determining the UL subband intermediate frequency domain resources, the terminal determines whether to use the UL subband intermediate frequency domain resources to perform uplink transmission based on other domains in the DCI.

[0202] In some embodiments, after determining the frequency domain resources in the UL subband, the terminal can determine whether to activate / deactivate these determined frequency domain resources based on the MAC CE. For example, the MAC CE includes a frequency activation domain, which is a FDRA domain used to activate / deactivate upper and lower frequency domain resources / RBG / RB. The FDRA domain may include a frequency activation bitmap, and the mechanism of the frequency activation bitmap is similar to that of the bitmap contained in the FDRA domain mentioned above, and will not be repeated here.

[0203] In some embodiments, terminal 101 has half-duplex capability, or full-duplex capability.

[0204] In some embodiments, in this embodiment, it is assumed that network device 102 transmits uplink data via DCI format 0-0, DCI format 0-1, DCI format 0-2, DCI format 0-3, or any other DCI scheduling terminal 101 used for scheduling uplink transmissions. The uplink transmission can be within the UL subband of an SBFD Slot or within the active UL BWP of a non-SBFD Slot.

[0205] Optionally, terminal 101 is a SBFD Aware UE that is aware of sub-band full-duplex.

[0206] Optionally, the FDRA field in the DCI used for uplink scheduling is determined based on the Active UL BWP or the Initial UL BWP. In summary, the DCI format used for scheduling uplink transmissions has a fixed size and does not change based on the slot type of the uplink transmission it schedules.

[0207] Optionally, the uplink frequency domain resource allocation type is RA type 0, meaning that network device 102 indicates the RBG used for uplink transmission through the FDRA field (Bitmap) in the DCI. In this embodiment, it is assumed that the RBG is still determined based on the size of the Active BWP. Two examples are shown in the figure below. That is, regardless of the relative relationship between the UL subband and the Active UL BWP, the granularity of the RBG is determined based on the Active UL BWP.

[0208] Optionally, the resource allocation for SBFD Aware UEs on the UL Subband includes:

[0209] The highest bit in the FDRA corresponds to the RBG with the largest RBG index in the UL BWP, or the highest bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL BWP. The other bits are mapped one-to-one with the remaining RBGs.

[0210] Optionally, the resource allocation for SBFD Aware UEs on the UL Subband includes:

[0211] The highest bit in the FDRA corresponds to the RBG with the largest RBG index in the UL Subband, or the highest bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL Subband. The other bits are mapped one-to-one with the remaining RBGs.

[0212] Optionally, the Active UL BWP contains 10 RBGs. Assume network device 102 schedules uplink transmission for the SBFD Aware UE on the UL subband within the SBFD slot. Assume the Bitmap in the FDRA information field of the DCI is 1110000000 or 0000111000, respectively indicating that the corresponding RBG#0, RBG#1, RBG#2 or RBG#4, RBG#5, RBG#6 in the active UL BWP are used for uplink transmission. Correspondingly, terminal 101 determines the resource location within the UL subband for uplink transmission based on the indication.

[0213] Optionally, if terminal 101 believes that the frequency domain resources indicated by the bitmap exceed the frequency domain range of the UL subband, only the resources included in the UL subband are used for the corresponding uplink transmission.

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

[0215] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0216] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

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

[0218] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0219] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0220] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0221] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0222] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0223] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0224] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0225] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0226] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0227] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0228] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, steps S2101+S2103 can be implemented as an independent embodiment, steps S2102+S2104 can be implemented as an independent embodiment, and steps S2101+S2102+S2103 can be implemented as an independent embodiment.

[0229] In some embodiments, other optional implementations described before or after the specification corresponding to FIG2 may be referred to.

[0230] Figure 3A is a flowchart illustrating a communication indication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication indication method, which includes:

[0231] Step S3101: Send capability indication information.

[0232] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0233] Step S3102: Obtain the first information.

[0234] The optional implementation of step S3102 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0235] In some embodiments, terminal 101 receives first information sent by network device 102, but is not limited thereto; it may also receive first information sent by other entities.

[0236] In some embodiments, terminal 101 obtains first information as defined by the protocol.

[0237] In some embodiments, terminal 101 obtains first information from upper layer(s).

[0238] In some embodiments, the terminal 101 processes the information to obtain the first information.

[0239] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the first information, or the above function is default or default.

[0240] In some embodiments, the first information is used to configure UL subband for terminal 101.

[0241] In some embodiments, the name of the first information is not limited, and it may be, for example, “UL subband configuration information”.

[0242] In some embodiments, the first information includes the UL subband configured by the network device 102 for the terminal 101.

[0243] In step S3103, terminal 101 determines the UL subband based on the first information.

[0244] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0245] In some embodiments, the first information is used to configure UL subband for terminal 101.

[0246] In some embodiments, ULsubband is the ULsubband configured for network device 102.

[0247] In some embodiments, the name of the first information is not limited, and it may be, for example, “UL subband configuration information”.

[0248] In some embodiments, the first information includes the UL subband configured by the network device 102 for the terminal 101.

[0249] Step S3104: Obtain the second information.

[0250] The optional implementation of step S3104 can be found in the optional implementation of step S2104 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0251] In some embodiments, terminal 101 receives second information sent by network device 102, but is not limited thereto; it may also receive second information sent by other entities.

[0252] In step S3105, terminal 101 determines the frequency domain resources in ULsubband based on the second information.

[0253] The optional implementation of step S3105 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0254] In some embodiments, terminal 101 determines the frequency domain resources in ULsubband used for uplink transmission based on the second information.

[0255] In some embodiments, the second information is used to indicate "frequency domain resources in the UL subband used for uplink transmission".

[0256] In some embodiments, the name of the second information is not limited, and it may be, for example, “DCI”, “frequency domain resource configuration information”, etc.

[0257] In some embodiments, the second information includes the "FDRA domain".

[0258] In some embodiments, the DCI includes second information. The DCI may be, for example, DCI format 0-0, DCI format 0-1, DCI format 0-2, or DCI format 0-3, but is not limited thereto, and may also be any other DCI used for scheduling uplink transmissions.

[0259] In step S3106, terminal 101 determines the FDRA domain based on the active UL BWP of the activated uplink bandwidth portion.

[0260] The optional implementation of step S3106 can be found in the optional implementation of step S2105 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0261] In step S3107, terminal 101 determines the FDRA domain based on the Initial UL BWP (Initial Uplink Bandwidth Part).

[0262] The optional implementation of step S3107 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0263] In some embodiments, the DCI format used for scheduling uplink transmissions has a fixed size and does not change depending on the slot type in which the uplink transmission it schedules is located.

[0264] In some embodiments, uplink transmission may be performed within the UL subband of the SBFD slot, or within the active UL BWP of the non-SBFD slot.

[0265] In some embodiments, the frequency domain resource allocation type for uplink transmission is Resource Assignment (RA) type 0.

[0266] In some embodiments, the allocation method of RAtype0 includes: the network device 102 indicating the resource block set RBG for uplink transmission through the FDRA field in the uplink DCI.

[0267] In some embodiments, the FDRA field contains a bitmap.

[0268] In step S3108, terminal 101 determines the granularity of RBG in the uplink bandwidth portion of UL BWP based on the size of the Active UL BWP.

[0269] The optional implementation of step S3108 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0270] In step S3109, terminal 101 determines the set of resource blocks (RBG) for uplink transmission within the UL Subband based on the bitmap in the FDRA domain.

[0271] The optional implementation of step S3109 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0272] In step S3110, terminal 101 maps the highest bit of Bitmap in FDRA field to the RBG with the largest RBG Index in UL BWP, and maps the other bits in Bitmap to other RBGs in sequence.

[0273] The optional implementation of step S3110 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0274] Step S3111: The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL BWP, and the other bits in the Bitmap are mapped to other RBGs in sequence.

[0275] The optional implementation of step S3111 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0276] In step S3112, terminal 101 maps the highest bit of Bitmap in FDRA field to the RBG with the largest RBG Index in UL Subband, and maps the other bits in bitmap to other RBGs in sequence.

[0277] The optional implementation of step S3112 can be found in the optional implementation of step S2104 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0278] In step S3113, terminal 101 maps the highest bit of Bitmap in FDRA field to the RBG with the smallest RBG Index in UL Subband, and maps the other bits in Bitmap to other RBGs in sequence.

[0279] The optional implementation of step S3113 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0280] In step S3114, terminal 101 determines that the RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission, and determines that the RBG corresponding to the position encoded as 0 in the Bitmap is not used for uplink transmission.

[0281] The optional implementation of step S3114 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0282] In step S3115, terminal 101 determines that the RBG corresponding to the position encoded as 0 in the Bitmap is used for uplink transmission, and determines that the RBG corresponding to the position encoded as 1 in the Bitmap is not used for uplink transmission.

[0283] The optional implementation of step S3115 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0284] In step S3116, terminal 101 determines that the resources included in the UL Subband are used for uplink transmission.

[0285] The optional implementation of step S3116 can be found in the optional implementation of step S2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0286] In some embodiments, the frequency domain resources indicated by the Bitmap extend beyond the frequency domain range of the UL Subband.

[0287] In some embodiments, terminal 101 has half-duplex capability, or full-duplex capability.

[0288] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3116. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, step S3103 may be implemented as an independent embodiment, step S3104 may be implemented as an independent embodiment, S3101+S3102 may be implemented as an independent embodiment, and step S3101+S3102+S3102 may be implemented as an independent embodiment, but is not limited thereto.

[0289] In some embodiments, steps S3105 and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0290] In some embodiments, steps S3109, S3110, S3111, and S3112 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0291] Figure 3B is a flowchart illustrating a communication indication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication indication method, which includes:

[0292] Step S3201: Determine the FDRA domain.

[0293] The optional implementation of step 3201 can be found in the optional implementation of step S2105 in Figure 2, steps S3106 to S3107 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0294] Step S3202: Determine the frequency domain resources used for uplink transmission.

[0295] The optional implementations of step S3202 can be found in step 2105 of Figure 2, the optional implementations of steps 3108 to 3116 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0296] The communication method involved in the embodiments of this disclosure may include at least one of steps S3201 and S3202. For example, step S3201 may be implemented as a separate embodiment, and step S3202 may be implemented as a separate embodiment, but are not limited thereto.

[0297] Figure 4A is a flowchart illustrating a communication indication method according to an embodiment of the present disclosure. As shown in Figure 4A, the present disclosure relates to a communication indication method, which includes:

[0298] Step S4101, network device 102 receives capability indication information.

[0299] The optional implementation of step S4101 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0300] In step S4102, network device 102 sends first information to terminal 101.

[0301] In some embodiments, terminal 101 receives first information.

[0302] In some embodiments, the first information is used to configure UL subband for terminal 101.

[0303] In some embodiments, the name of the first information is not limited, and it may be, for example, “UL subband configuration information”.

[0304] The optional implementation of step S4102 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0305] In some embodiments, network device 102 sends first information to terminal 101, but is not limited thereto; it may also send first information to other entities.

[0306] In step S4103, network device 102 sends second information to terminal 101.

[0307] The optional implementation of step S4103 can be found in the optional implementation of step S2104 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0308] The communication method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4103. For example, step S4101 may be implemented as a standalone embodiment, step S4102 may be implemented as a standalone embodiment, and step S4101+S4102 may be implemented as a standalone embodiment, but is not limited thereto.

[0309] In some embodiments, steps S4105 and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0310] In some embodiments, steps S3109, S3110, S3111, and S3112 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0311] Figure 4B is a flowchart illustrating a communication indication method according to an embodiment of the present disclosure. As shown in Figure 4B, the present disclosure relates to a communication indication method, which includes:

[0312] Step S4201: Configure the uplink subband UL subband.

[0313] In an optional embodiment, step S4201 includes a lower-level solution. Optional implementations of step S4201 can be found in step S2101 of Figure 2, optional implementations of step S4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0314] Step S4202 indicates the frequency domain resources used for uplink transmission.

[0315] In an optional embodiment, step S4202 includes a lower-level solution. Optional implementations of step S4202 can be found in step S2103 of Figure 2, optional implementations of step S4102 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0316] The communication method involved in the embodiments of this disclosure may include at least one of steps S4201 and S4202. For example, step S4201 may be implemented as a standalone embodiment, step S4202 may be implemented as a standalone embodiment, and step S4201+S4202 may be implemented as a standalone embodiment, but is not limited thereto.

[0317] Figure 5 is an interactive schematic diagram of a communication indication method according to an embodiment of the present disclosure. As shown in Figure 5, the present disclosure relates to a communication indication method, which includes:

[0318] Step S5101: The network device configures the uplink subband (UL subband) for the terminal.

[0319] The optional implementations of step S5101 can be found in the optional implementations of steps S2101 and S2102 in Figure 2, steps S4201 and S4202 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0320] Step S5102: The terminal determines the uplink subband UL.

[0321] The optional implementation of step S5102 can be found in step S2102 in Figure 2, the optional implementation of steps S3101 and S3102 in Figure 3, and other related parts in the embodiments involved in Figures 2, 3 and 4, which will not be repeated here.

[0322] In step S5103, the network device sends a DCI, which is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband.

[0323] The optional implementation of step S5103 can be found in the optional implementation of step S2103 in Figure 2, step S4203 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0324] In step S5104, the terminal receives the DCI and determines the uplink frequency domain resources based on the DCI. These uplink frequency domain resources are the resources in the UL Subband used for uplink transmission.

[0325] The optional implementation of step S5104 can be found in step S2104 of Figure 2, steps S3104 to S3116 of Figure 3, and other related parts in the embodiments involved in Figures 2 and 3, which will not be repeated here.

[0326] In some embodiments, the above methods may include the methods of the embodiments described above on the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0327] Figure 6 is a schematic diagram illustrating a communication indication method according to an embodiment of the present disclosure. As shown in Figure 6, the present disclosure relates to a communication indication method, which includes:

[0328] Step S6101: The base station schedules the uplink transmission of the terminal through DCI.

[0329] Optionally, the DCI can be DCI format 0-0, DCI format 0-1, DCI format 0-2, DCI format 0-3, or any other DCI used for scheduling uplink transmission.

[0330] Optionally, uplink transmission can be performed within the UL subband of the SBFD Slot or within the active UL BWP of the non-SBFD Slot.

[0331] Optionally, the terminal is an SBFD Aware UE that is aware of subband full-duplex.

[0332] Optionally, the base station performs full-duplex operation in the downlink time slot of the time division duplex (TDD) band, that is, it schedules downlink data and uplink data simultaneously.

[0333] Figure 9A is a schematic diagram of BWP according to an embodiment of the present disclosure. As shown in Figure 9A, the frequency domain resources used for uplink and downlink transmission in the same time slot can be categorized into three cases:

[0334] Case 1: The frequency domain resources used for DL ​​transmission and UL transmission within the DL slot are independent of each other and do not overlap.

[0335] Case 2: The frequency domain resources used for DL ​​transmission and UL transmission within the DL slot completely overlap;

[0336] Case 3: The frequency domain resources used for DL ​​transmission and UL transmission within the DL slot partially overlap.

[0337] Optionally, the current system's TDD UL-DL configuration is DDDDDSUUU, where D represents the DL slot and U represents the UL slot, and the bandwidth of the DL BWP in the DL slot is different from the bandwidth of the UL BWP in the UL slot. For the TDD band, the center frequencies of the DL BWP and UL BWP need to be aligned. Figure 9B is a schematic diagram of the BWP according to an embodiment of this disclosure. As shown in Figure 9B, the center frequencies of the DL BWP and UL BWP are aligned.

[0338] In step S6102, the terminal determines the RBG Index corresponding to the FDRA field carried in the DCI that schedules the uplink transmission within the UL subband.

[0339] Optionally, the terminal determines the RBG Index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP based on the active uplink bandwidth portion Active UL BWP; or,

[0340] Optionally, the terminal determines the RBG Index corresponding to the Resource Block Set (RBG) in the Initial UL BWP based on the Initial Uplink Bandwidth Part (Initial UL BWP).

[0341] Optionally, the RBG Index corresponds to the FDRA field in the DCI.

[0342] Optionally, each bit in the bitmap of the FDRA field corresponds to an RBG Index.

[0343] Optionally, each bit in the bitmap of the FDRA field corresponds to multiple RBG indices.

[0344] Optionally, the DCI format used for scheduling uplink transmissions has a fixed size and does not change depending on the slot type of the uplink transmission it schedules.

[0345] In step S6103, the terminal determines the frequency domain resources used for uplink transmission based on the FDRA domain carried in the DCI.

[0346] Optionally, the frequency domain resource allocation type for uplink transmission is RA type 0, that is, the access network device uses the Bitmap in the FDRA field of the uplink DCI to indicate the RBG used for uplink transmission.

[0347] Optionally, RBG is still determined based on the size of the Active BWP.

[0348] Optionally, regardless of the relative relationship between the UL subband and the Active UL BWP, the granularity of the RBG is determined based on the Active UL BWP.

[0349] The highest bit in the FDRA corresponds to the RBG with the largest RBG index in the UL BWP, or the highest bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL BWP. The other bits are mapped one-to-one with the remaining RBGs.

[0350] Optionally, the resource allocation for SBFD Aware UEs on the UL Subband includes:

[0351] The highest bit in the FDRA corresponds to the RBG with the largest RBG index in the UL Subband, or the highest bit in the FDRA corresponds to the RBG with the smallest RBG index in the UL Subband. The other bits are mapped one-to-one with the remaining RBGs.

[0352] Figure 9C is a schematic diagram of BWP and UL Subband according to an embodiment of the present disclosure. As shown in Figure 9C, the highest bit in FDRA corresponds to the RBG with the largest RBG Index in UL BWP, and the other bits are mapped one-to-one with the remaining RBGs. That is, the highest bit in Bitmap corresponds to RBG#0, and the remaining bits correspond to RBG#1 to RBG#N respectively.

[0353] In one possible embodiment, a portion of the frequency domain range of the UL Subband lies within the UL BWP. The UL BWP contains 10 RBGs, and the Bitmap in the FDRA information field of the DCI is 1110000000. The RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission. Therefore, RBG#0, RBG#1, and RBG#2 are determined as resource locations used for uplink transmission.

[0354] Figure 9D is a schematic diagram of BWP and UL Subband according to an embodiment of the present disclosure. As shown in Figure 9D, the highest bit in FDRA corresponds to the RBG with the largest RBG Index in UL BWP, and the other bits are mapped one-to-one with the remaining RBGs. That is, the highest bit in Bitmap corresponds to RBG#0, and the remaining bits correspond to RBG#1 to RBG#N respectively.

[0355] A portion of the frequency domain of the UL Subband lies within the UL BWP. The UL BWP contains 10 RBGs, and the Bitmap in the FDRA information field of the DCI is 0000111000. The RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission. Therefore, RBG#4, RBG#5, and RBG#6 are determined as resource locations used for uplink transmission. Correspondingly, terminal 101 determines the resource locations within the UL subband used for uplink transmission according to the instructions.

[0356] Optionally, the resource allocation for SBFD Aware UEs on the UL Subband includes:

[0357] Optionally, the Active UL BWP contains 10 RBGs. Assume network device 102 schedules uplink transmission for the SBFD Aware UE on the UL subband within the SBFD slot. Assume the Bitmap in the FDRA information field of the DCI is 1110000000 or 0000111000, respectively indicating that the corresponding RBG#0, RBG#1, RBG#2 or RBG#4, RBG#5, RBG#6 in the active UL BWP are used for uplink transmission. Correspondingly, terminal 101 determines the resource location within the UL subband for uplink transmission based on the indication.

[0358] Optionally, if terminal 101 believes that the frequency domain resources indicated by the bitmap exceed the frequency domain range of the UL subband, only the resources included in the UL subband are used for the corresponding uplink transmission.

[0359] The communication method involved in the embodiments of this disclosure may include at least one of steps S6101 to S6103. For example, step S6101 may be implemented as an independent embodiment, step S6102 may be implemented as an independent embodiment, step S6103 may be implemented as an independent embodiment, step S6102+S6103 may be implemented as an independent embodiment, and step S6101+S6102+S6103 may be implemented as an independent embodiment, but is not limited thereto.

[0360] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0361] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0362] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0363] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0364] Figure 7A is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 7A, the terminal 7100 may include at least one of a transceiver module 7101, a processing module 7102, etc. In some embodiments, the transceiver module is used to obtain the uplink subband (UL subband) configured by the access network device and determine the frequency domain resource allocation (FDRA) field in the downlink control information (DCI) used for scheduling the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband. The processing module is used to determine the frequency domain resources used for uplink transmission within the UL subband based on the FDRA field.

[0365] Optionally, the transceiver module is used to perform at least one of the communication steps (such as step 2102, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps (such as step 2104, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be described in detail here.

[0366] Figure 7B is a schematic diagram of the structure of an access network device according to an embodiment of this disclosure. As shown in Figure 7B, the access network device 7200 may include a transceiver module 7201. In some embodiments, the transceiver module is used to configure an uplink subband (UL subband) for a terminal device. The FDRA field carried in the DCI indicates the frequency domain resources used by the terminal device for uplink transmission within the UL subband.

[0367] Optionally, the transceiver module is used to perform at least one of the communication steps (such as step 2101, step 2103, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be described in detail here.

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

[0369] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0370] Figure 8A is a schematic diagram of the structure of the communication device 8100 proposed in an embodiment of this disclosure. The communication device 8100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0371] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 8100 is used to execute any of the above methods.

[0372] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may also be located outside the communication device 8100.

[0373] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceivers 8103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 2101, 2103, but not limited thereto), and the processor 8101 performs at least one of other steps (e.g., steps 2102, 2104, but not limited thereto).

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

[0375] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0377] Figure 8B is a schematic diagram of the structure of chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of chip 8200 shown in Figure 8B, but it is not limited thereto.

[0378] Chip 8200 includes one or more processors 8201, which are used to perform any of the above methods.

[0379] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to memory 8203, and the interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and the interface circuit 8202 can be used to send signals to memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201.

[0380] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 2101, 2103, but not limited thereto), and the processor 8201 performs at least one of the other steps (e.g., steps 2102, 2104, but not limited thereto).

[0381] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0382] In some embodiments, chip 8200 further includes one or more memories 8203 for storing instructions. Optionally, all or part of the memories 8203 may be located outside of chip 8200.

[0383] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0384] This disclosure also provides a program product that, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0385] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication indication method, characterized in that, The method includes: Determine the uplink subband (UL). Receive downlink control information (DCI), which is used to schedule the physical uplink shared channel (PUSCH) transmitted in the UL subband; The uplink frequency domain resources are determined based on the DCI, and the uplink frequency domain resources are the resources in the UL Subband used for uplink transmission.

2. The method according to claim 1, characterized in that, The DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine the uplink frequency domain resources.

3. The method according to claim 2, characterized in that, The determination of uplink frequency domain resources based on the DCI includes: The uplink frequency domain resource is determined based on the bitmap in the FDRA domain, wherein the uplink frequency domain resource includes a resource block set RBG, and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resource.

4. The method according to claim 3, characterized in that, The step of determining the uplink frequency domain resources based on the bitmap in the FDRA domain includes: The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the largest RBG Index in the UL BWP, and the other bits of the Bitmap are mapped sequentially to other RBGs; or, The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL BWP, and the other bits in the Bitmap are mapped to other RBGs in sequence.

5. The method according to claim 3, characterized in that, The step of determining the uplink frequency domain resource based on the bitmap in the FDRA domain further includes: The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the largest RBG Index in the UL Subband, and the other bits in the bitmap are mapped sequentially to other RBGs; or, The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL Subband, and the other bits in the Bitmap are mapped to other RBGs in sequence.

6. The method according to any one of claims 3-5, characterized in that, The RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission.

7. The method according to any one of claims 3-6, characterized in that, The Bitmap indicates a first frequency domain resource, which includes a first RBG. The first RBG is not located in the frequency domain range of the UL Subband and does not belong to the uplink frequency domain resource.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The RBG index corresponding to the resource block set RBG in the active uplink bandwidth portion UL BWP is determined based on the active uplink bandwidth portion; or, The RBGIndex corresponding to the resource block set RBG in the Initial UL BWP is determined based on the Initial Uplink Bandwidth Part.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: The granularity of RBG in the uplink bandwidth portion of the UL BWP is determined based on the size of the Active UL BWP; Alternatively, the granularity of the RBG in the UL Subband can be determined based on the size of the Active UL BWP.

10. The method according to any one of claims 1-9, characterized in that, The frequency domain resource allocation type for the uplink transmission is resource allocation mode 0RAtype0.

11. The method according to any one of claims 1-10, characterized in that, The DCI is any one of the following: DCI format 0-0; DCI format 0-1; DCI format 0-2; DCI format 0-3.

12. A communication indication method, characterized in that, The method includes: Configure the uplink subband (UL) for the terminal; Send a DCI, wherein the DCI is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, which are resources in the UL subband used for uplink transmission.

13. The method according to claim 12, characterized in that, The DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine the uplink frequency domain resources.

14. The method according to claim 13, characterized in that, The bitmap in the FDRA field is used to determine the uplink frequency domain resource, wherein the uplink frequency domain resource includes a resource block set RBG, and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resource.

15. The method according to claim 14, characterized in that, The correspondence between the bitmap in the FDRA domain and the uplink frequency domain resources includes: The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the largest RBG Index in the UL BWP, and the other bits of the Bitmap are mapped sequentially to other RBGs; or, The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL BWP, and the other bits in the Bitmap are mapped to other RBGs in sequence.

16. The method according to claim 14, characterized in that, The correspondence between the bitmap in the FDRA domain and the uplink frequency domain resources also includes: The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the largest RBG Index in the UL Subband, and the other bits in the bitmap are mapped sequentially to other RBGs; or, The highest bit of the Bitmap in the FDRA field is mapped to the RBG with the smallest RBG Index in the UL Subband, and the other bits in the Bitmap are mapped to other RBGs in sequence.

17. The method according to any one of claims 14-16, characterized in that, The RBG corresponding to the position encoded as 1 in the Bitmap is used for uplink transmission.

18. The method according to any one of claims 14-17, characterized in that, The Bitmap indicates a first frequency domain resource, which includes a first RBG. The first RBG is not located in the frequency domain range of the UL Subband and does not belong to the uplink frequency domain resource.

19. The method according to any one of claims 12-18, characterized in that, The RBGIndex corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP is determined by the active uplink bandwidth portion Active UL BWP; or, The RBG Index corresponding to the resource block set RBG in the uplink bandwidth portion UL BWP is determined by the Initial Uplink Bandwidth Portfolio (Initial UL BWP).

20. The method according to any one of claims 12-19, characterized in that, The method further includes: The granularity of RBG in the uplink bandwidth portion of the UL BWP is determined based on the size of the Active UL BWP; Alternatively, the granularity of the RBG in the UL Subband can be determined based on the size of the Active UL BWP.

21. The method according to any one of claims 12-20, characterized in that, The frequency domain resource allocation type for the uplink transmission is resource allocation mode 0RAtype0.

22. The method according to any one of claims 1-21, characterized in that, The DCI is any one of the following: DCI format 0-0; DCI format 0-1; DCI format 0-2; DCI format 0-3.

23. A communication indication method, characterized in that, The method includes: Network devices configure uplink subband (UL) for terminals; The terminal determines the uplink subband (UL Subband); The network device sends a DCI, which is used to schedule the Physical Uplink Shared Channel (PUSCH) transmitted in the UL subband. The terminal receives the DCI and determines the uplink frequency domain resources based on the DCI. The uplink frequency domain resources are the resources in the UL Subband used for uplink transmission.

24. The method according to claim 23, characterized in that, The DCI includes a Frequency Domain Resource Allocation (FDRA) domain, which is used to determine the uplink frequency domain resources.

25. The method according to claim 24, characterized in that, The determination of uplink frequency domain resources based on the DCI includes: The terminal determines the uplink frequency domain resource based on the bitmap in the FDRA domain, wherein the uplink frequency domain resource includes a resource block set RBG, and the bitmap is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resource.

26. A terminal, characterized in that, include: One or more processors; The terminal is used to execute the method according to any one of claims 1-11.

27. An access network device, characterized in that, include: One or more processors; The access network device is used to perform the method according to any one of claims 13-22.

28. A communication system, characterized in that, The device includes a terminal and an access network device, wherein the terminal is configured to implement the method of any one of claims 1-11, and the access network device is configured to implement the method of any one of claims 12-22.

29. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1-11 or 12-22.

Images