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 method, terminal and access network equipment Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication indication method, a terminal, and an access network device. Background Art

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

[0003] Summary of the Invention

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

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

[0006] Determine the uplink subband UL Subband;

[0007] receiving downlink control information DCI, where the DCI is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband;

[0008] An uplink frequency domain resource is determined based on the DCI, where the uplink frequency domain resource is a resource used for uplink transmission in a UL Subband.

[0009] The solution disclosed herein improves communication efficiency.

[0010] According to a second aspect of an embodiment of the present disclosure, a communication indication method is proposed, the method comprising:

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

[0012] Sending DCI, where the DCI is used to schedule a physical uplink shared channel (PUSCH) transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, where the uplink frequency domain resources are resources used for uplink transmission in the UL subband.

[0013] According to a third aspect of an embodiment of the present disclosure, a communication indication method is proposed, the method including:

[0014] The network device configures an uplink subband UL subband for the terminal;

[0015] The terminal determines the uplink subband UL Subband

[0016] The network device sends a DCI, where the DCI is used to schedule a physical uplink shared channel (PUSCH) transmitted in the UL subband;

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

[0018] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0019] one or more processors;

[0020] The terminal is used to execute any one of the methods in the first aspect.

[0021] According to a fifth aspect of an embodiment of the present disclosure, an access network device is provided, including:

[0022] one or more processors;

[0023] The access network device is used to execute any one of the methods described in the second aspect.

[0024] According to the sixth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising 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 an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method as described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0028] FIG1B is a schematic diagram of a frequency domain relationship between a UL subband and a ULBWP configured by a base station in a possible embodiment.

[0029] FIG1C is a schematic diagram of a frequency domain relationship between a UL subband and a ULBWP configured by a base station in a possible embodiment.

[0030] FIG2 is an exemplary interaction diagram of a communication indication method provided according to an embodiment of the present disclosure.

[0031] FIG3A is a flow chart illustrating a communication indication method according to an embodiment of the present disclosure.

[0032] FIG3B is a flow chart of a communication indication method according to an embodiment of the present disclosure.

[0033] FIG4A is a flow chart illustrating a communication indication method according to an embodiment of the present disclosure.

[0034] FIG4B is a flow chart of a communication indication method according to an embodiment of the present disclosure.

[0035] FIG5 is a flow chart of a communication indication method according to an embodiment of the present disclosure.

[0036] FIG6 is a flow chart of a communication indication method according to an embodiment of the present disclosure.

[0037] FIG7A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure.

[0038] FIG7B is a schematic structural diagram of an access network device proposed in an embodiment of the present disclosure.

[0039] FIG8A is a schematic structural diagram of a communication device 8100 proposed in an embodiment of the present disclosure.

[0040] FIG8B is a schematic structural diagram of a chip 8200 according to an embodiment of the present disclosure.

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

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

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

[0044] FIG9D is a schematic diagram showing BWP and UL Subband according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0045] The embodiments of the present disclosure provide a communication indication method, a terminal, and an access network device.

[0046] In a first aspect, an embodiment of the present disclosure proposes a communication indication method, which includes: determining an uplink subband UL Subband; receiving downlink control information DCI, which is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband; and determining an uplink frequency domain resource based on the DCI, which is a resource used for uplink transmission in the UL Subband.

[0047] In the above embodiment, the terminal can determine the resources within the UL subband used for uplink transmission, thereby providing a solid technical foundation for achieving full-duplex. Furthermore, because the uplink frequency domain used in the downlink slot is implemented by DCI, no new signaling is introduced, maintaining forward compatibility with existing standards and reducing the technical implementation complexity of the terminal.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine uplink frequency domain resources.

[0049] In the above embodiment, the terminal can determine the uplink frequency domain resources based on the frequency domain resource allocation FDRA field in the DCI, providing the necessary conditions for achieving full-duplex communication. Furthermore, because the FDRA field in the DCI is utilized, no new information or indication field is added to the DCI, and the communication resource usage of the DCI is not increased, thus saving communication resources.

[0050] In combination with some embodiments of the first aspect, in some embodiments, determining the uplink frequency domain resources based on DCI includes: determining the uplink frequency domain resources according to the bit map Bitmap in the FDRA domain, wherein the uplink frequency domain resources include a resource block set RBG, and the bit map is used to indicate the RBG Index corresponding to the RBG in the uplink frequency domain resources.

[0051] In the above embodiment, the terminal can indicate the RBG index corresponding to the RBG in the uplink frequency domain resources based on the bitmap in the FDRA field, providing the necessary conditions for achieving full-duplex communication. Furthermore, because 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 the uplink frequency domain resources.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the uplink frequency domain resources are determined according to the bitmap Bitmap in the FDRA domain, including: corresponding 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 the other RBGs in sequence one by one; or, corresponding 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 the other RBGs in sequence one by one.

[0053] In the above embodiment, the terminal can associate the bitmap in the FDRA field with the RBG index corresponding to the RBG in the UL BWP, providing the necessary conditions for full-duplex communication. Furthermore, because 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 the uplink frequency domain resources in the UL BWP and avoiding resource waste.

[0054] In combination with some embodiments of the first aspect, in some embodiments, determining the uplink frequency domain resources based on the bitmap Bitmap in the FDRA domain also includes: corresponding 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 the other RBGs in sequence one by one; or, corresponding 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 the other RBGs in sequence one by one.

[0055] In the above embodiment, the terminal can associate the bitmap in the FDRA field with the RBG index corresponding to the RBG in the UL subband, providing the necessary conditions for full-duplex communication. Furthermore, because 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 the uplink frequency domain resources in the UL subband and avoiding resource waste.

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

[0057] In the above embodiment, the terminal can determine the RBG corresponding to the position coded as 1 in the bitmap in the FDRA field, providing a basis for achieving full-duplex communication. Furthermore, because the coded value at a specific bitmap position 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 combination with some embodiments of the first aspect, in some embodiments, the Bitmap indicates a first frequency domain resource, the first frequency domain resource is not located in the frequency domain range of the UL Subband, and the first RBG does not belong to an uplink frequency domain resource.

[0059] In the above embodiment, the terminal can use the bitmap to determine the first frequency domain resource that is not within the frequency domain range of the UL subband, providing a basis for achieving full-duplex communication. Furthermore, because the first frequency domain resource is not within the frequency domain range of the UL subband, the use of the first frequency domain resource can be avoided, thereby avoiding waste of communication resources and improving communication resource utilization.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining the RBG index Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the activated uplink bandwidth part Active UL BWP; or, determining the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the initial uplink bandwidth part Initial UL BWP.

[0061] In the above embodiment, the terminal can determine the RBG Index corresponding to the RBG, providing the necessary conditions for achieving full-duplex communication. Furthermore, since the Active UL BWP and Initial UL BWP are utilized, no new UL BWP is introduced, which is forward compatible with existing standards and reduces the technical implementation complexity of the terminal.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining the granularity of RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP; or determining the granularity of RBG in the UL Subband according to the size of the Active UL BWP.

[0063] In the above embodiment, the terminal can determine the granularity of the RBG, which provides the necessary conditions for achieving full-duplex communication. Furthermore, since the size of the Active UL BWP is used to determine the granularity of the RBG, it is forward compatible with existing standards and reduces the technical implementation complexity of the terminal.

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

[0065] In combination 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] In the second aspect, an embodiment of the present disclosure proposes a communication indication method, which includes: configuring an uplink subband UL subband for a terminal; sending DCI, wherein the DCI is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, which are resources used for uplink transmission in the UL Subband.

[0067] In the above embodiment, the network device configures uplink transmission resources in the UL subband for the terminal, thereby providing a solid technical foundation for achieving full-duplex. Furthermore, because the uplink frequency domain used in the downlink slot is implemented by DCI, no new signaling is introduced, maintaining forward compatibility with existing standards and reducing the technical implementation complexity of the network device.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine uplink frequency domain resources.

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

[0070] In combination with some embodiments of the second aspect, in some embodiments, the correspondence between the bitmap Bitmap in the FDRA domain and the uplink frequency domain resources includes: corresponding 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 the other RBGs in sequence one by one; or, corresponding 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 the other RBGs in sequence one by one.

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

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

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

[0074] In combination with some embodiments of the second aspect, in some embodiments, the Bitmap indicates the first frequency domain resource, the first frequency domain resource 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 combination with some embodiments of the second aspect, in some embodiments, the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined by the activated uplink bandwidth part Active UL BWP; or, the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined by the initial uplink bandwidth part Initial UL BWP.

[0076] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: determining the granularity of RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP; or determining the granularity of RBG in the UL Subband according to the size of the Active UL BWP.

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

[0078] In combination 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] In a third aspect, an embodiment of the present disclosure proposes a communication indication method, which includes: a network device configures an uplink subband UL subband for a terminal; the terminal determines the uplink subband UL Subband; the network device sends DCI, which is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband; the terminal receives the DCI and determines uplink frequency domain resources based on the DCI, which are resources in the UL Subband used for uplink transmission.

[0080] In combination with some embodiments of the third aspect, in some embodiments, the DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine uplink frequency domain resources.

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

[0082] In combination with some embodiments of the third aspect, in some embodiments, the uplink frequency domain resources are determined according to the bitmap Bitmap in the FDRA domain, including: the terminal corresponds the highest bit of the Bitmap in the FDRA domain to the RBG with the largest RBG Index in the UL BWP, and maps the other bits in the Bitmap to the other RBGs in sequence one by one; or, the terminal corresponds the highest bit of the Bitmap in the FDRA domain to the RBG with the smallest RBG Index in the UL BWP, and maps the other bits in the Bitmap to the other RBGs in sequence one by one.

[0083] In combination with some embodiments of the third aspect, in some embodiments, determining the uplink frequency domain resources based on the bitmap Bitmap in the FDRA domain also includes: the terminal corresponds the highest bit of the Bitmap in the FDRA domain to the RBG with the largest RBG Index in the UL Subband, and maps the other bits in the bitmap to the other RBGs in sequence one by one; or, the terminal corresponds the highest bit of the Bitmap in the FDRA domain to the RBG with the smallest RBG Index in the UL Subband, and maps the other bits in the Bitmap to the other RBGs in sequence one by one.

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

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

[0086] In combination with some embodiments of the third aspect, in some embodiments, the method also includes: the terminal determines the RBG index Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the activated uplink bandwidth part Active UL BWP; or, the terminal determines the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the initial uplink bandwidth part Initial UL BWP.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: determining the granularity of RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP; or determining the granularity of RBG in the UL Subband according to the size of the Active UL BWP.

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

[0089] In combination 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] In a fourth aspect, an embodiment of the present disclosure proposes 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 method of the first aspect.

[0091] In a fifth aspect, an embodiment of the present disclosure proposes 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 method of the second aspect.

[0092] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, which includes: one or more processors; wherein the terminal is used to execute the optional implementation method of the first aspect.

[0093] In a seventh aspect, an embodiment of the present disclosure proposes an access network device, which includes: one or more processors; wherein the access network device is used to execute the optional implementation method of the second aspect.

[0094] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and an access network device; wherein the terminal is configured to execute the method described in the optional implementation of the first aspect, the fourth aspect, and the sixth aspect, and the access network device is configured to execute the method described in the optional implementation of the second aspect, the fifth aspect, and the seventh aspect.

[0095] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0096] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the second aspect, and the optional implementation of the third aspect.

[0097] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the second aspect, and the optional implementation of the third aspect.

[0098] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0099] It is understandable that the above-mentioned terminals, access network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0100] The present disclosure provides a communication indication method, terminal, and access network device. In some embodiments, the terms "communication indication method," "information processing method," and "communication method" are interchangeable; the terms "communication indication device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0101] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0102] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0103] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0104] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0105] In the embodiments of the present disclosure, “plurality” refers to two or more.

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

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

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

[0109] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0110] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0111] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0112] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

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

[0114] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, 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", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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", "bandwidth part (BWP)", etc.

[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, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0119] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

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

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

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

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

[0124] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0125] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0126] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0127] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0128] In one possible embodiment, in a full-duplex communication scenario, the network can simultaneously transmit and receive data within a single timeslot. This full-duplex enhancement applies only to the gNB, while the terminal still supports only half-duplex. The gNB can configure an uplink (UL) subband for uplink data transmission within a downlink (DL) timeslot for a full-duplex terminal 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 UL subband configured by the base station differ from the active UL bandwidth part (BWP).

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

[0130] FIG1C is a schematic diagram of the frequency domain relationship between the UL subband and the ULBWP configured by the base station in a possible embodiment. As shown in FIG1C , in multiple subband full-duplex (SBFD) time slots, the frequency domain range occupied by the UL subband is not completely contained in the frequency domain range of the ULBWP, and a portion of the UL subband exceeds the frequency domain range of the ULBWP.

[0131] In a possible embodiment, a conclusion is reached regarding the transmission behavior of an SBFD-aware UE on a UL subband, that is, the terminal does not expect to send uplink information outside the active UL BWP.

[0132] In a possible embodiment, the base station indicates the frequency domain resources occupied by the uplink data channel transmission through a frequency domain resource allocation field (FDRA) included in downlink control information (DCI), and the FDRA field indicates the frequency domain resources within the UL BWP.

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

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

[0135] However, because UL subbands and UL BWPs are not necessarily aligned in the frequency domain, when uplink transmissions are transmitted in different slots, if the slots include SBFD slots and non-SBFD slots, the available frequency resources will differ. Currently, there is no clear solution for using the same frequency resource indication information to indicate uplink frequency resources in different slots.

[0136] FIG2 is a schematic diagram of an interaction of a communication system according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of 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, the capability indication information is used to indicate that the terminal 101 has half-duplex capability.

[0140] In some embodiments, the capability indication information is used to indicate that the 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, the capability indication information is used to indicate that the terminal 101 supports uplink communication in a sub-band full-duplex (SBFD) timeslot.

[0143] Step S2102 , the network device 102 sends first information to the terminal 101 .

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

[0145] In some embodiments, the first information is used to configure a UL subband for the 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, where the one or more fields are used to indicate a time domain position and / or a frequency domain position of the UL subband.

[0148] In some embodiments, the UL subband may be semi-statically configured or dynamically configured, that is, the first information is semi-statically configured or dynamically configured. 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 using the first information. The first information may be a MAC CE.

[0149] In some embodiments, the frequency domain position or time domain position of the UL subband is known, for example, the frequency domain position or time domain position is statically configured. In this case, the first information is used to configure the non-statically configured time domain position or frequency domain position 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, the first information is sent when the access network device 102 performs full-duplex communication with the terminal 101 .

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

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

[0154] Step S2103: Terminal 101 determines a UL subband according to the first information.

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

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

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

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

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

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

[0161] Step S2104 , the network device 102 sends second information to the terminal 101 .

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

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

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

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

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

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

[0168] In some embodiments, the bitmap in the FDRA field is used to determine uplink frequency domain resources, wherein the uplink frequency domain resources include resource block sets RBGs, wherein 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, the terminal 101 receives the DCI, which 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 for scheduling uplink transmission.

[0171] In some embodiments, the RBG index corresponding to the resource block group (RBG) in the uplink bandwidth part UL BWP is determined according to the active uplink bandwidth part Active UL BWP. Optionally, a corresponding unique RBGIndex is assigned to each RBG.

[0172] In some embodiments, the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined according to the initial uplink bandwidth part Initial UL BWP.

[0173] In some embodiments, the DCI format used for scheduling uplink transmission has a fixed size and does not change due to the different slot types in which the uplink transmission it schedules is located.

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

[0175] In some embodiments, the frequency domain resource allocation type of uplink transmission is resource assignment (RA) type0.

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

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

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

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

[0180] In some embodiments, an RBG includes multiple resource blocks (RBs). The number of RBs included in each RBG is associated with the number of RBs included in a BWP. The specific association is shown in Table 1:

[0181] Table 1

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

[0183] In some embodiments, the frequency domain resources used for uplink transmission in the UL Subband are resource block sets RBGs, and the RBGs are determined by a bitmap Bitmap in the FDRA field.

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

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

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

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

[0188] In some embodiments, if the frequency domain resources indicated by the Bitmap exceed the frequency domain range of the UL Subband, 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 has full-duplex capability.

[0190] In some embodiments, in this embodiment, it is assumed that network device 102 schedules uplink transmission of terminal 101 using DCI format 0-0, DCI format 0-1, DCI format 0-2, DCI format 0-3, or any other DCI format for scheduling uplink transmission. The uplink transmission can be within the UL subband of the SBFD slot or within the active UL BWP of the non-SBFD slot, and this patent does not impose any limitations.

[0191] Optionally, the terminal 101 is a terminal SBFD Aware UE that can perceive sub-band full-duplex.

[0192] Optionally, the FDRA field in the DCI for uplink scheduling is determined according to the Active UL BWP or the Initial UL BWP. In short, the DCI format for scheduling uplink transmission has a fixed size and does not change due to the different slot types of the uplink transmission it schedules.

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

[0194] 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 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.

[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 that network device 102 schedules an SBFD-Aware UE for uplink transmission on a UL subband within the SBFD slot. Assume that the bitmap in the FDRA information field in the DCI is 1110000000 or 0000111000, 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. Accordingly, terminal 101 determines the resource location for uplink transmission within the UL subband based on the indication.

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

[0198] Step S2105: The terminal 101 determines the frequency domain resources in the UL subband according to the second information.

[0199] The terminal 101 determines the frequency domain resources in the UL subband according to the second information. For example, reference may be made to the textual description of step S2103 and other parts above, which will not be repeated here.

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

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

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

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

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

[0205] Optionally, the terminal 101 is a terminal SBFD Aware UE that can perceive sub-band full-duplex.

[0206] Optionally, the FDRA field in the DCI for uplink scheduling is determined according to the Active UL BWP or the Initial UL BWP. In short, the DCI format for scheduling uplink transmission has a fixed size and does not change due to the different slot types of the uplink transmission it schedules.

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

[0208] Optionally, resource allocation of the SBFD Aware UE on the UL subband includes:

[0209] The highest bit in FDRA corresponds to the RBG with the largest RBG Index in the UL BWP, or the highest bit in 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, resource allocation of the SBFD Aware UE on the UL subband includes:

[0211] The highest bit in FDRA corresponds to the RBG with the largest RBG Index in the UL subband, or the highest bit in 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 that network device 102 schedules an SBFD-Aware UE for uplink transmission on a UL subband within the SBFD slot. Assume that the bitmap in the FDRA information field in the DCI is 1110000000 or 0000111000, 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. Accordingly, terminal 101 determines the resource location for uplink transmission within the UL subband based on the indication.

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

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

[0215] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

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

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

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

[0219] In some embodiments, terms such as "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", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

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

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

[0223] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

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

[0225] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0226] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, 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 recipient to respond to the content sent.

[0228] The communication method involved in the embodiment of the present 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, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0230] FIG3A is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of 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 refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0233] Step S3102, obtaining first information.

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

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

[0236] In some embodiments, terminal 101 obtains first information specified by a protocol.

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

[0238] In some embodiments, the terminal 101 performs processing 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 by default.

[0240] In some embodiments, the first information is used to configure a UL subband for the 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] Step S3103: Terminal 101 determines a UL subband according to the first information.

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

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

[0246] In some embodiments, the UL subband is a UL subband configured by the 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, obtaining the second information.

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

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

[0252] Step S3105: Terminal 101 determines frequency domain resources in the UL subband according to the second information.

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

[0254] In some embodiments, the terminal 101 determines frequency domain resources for uplink transmission in the UL subband according to the second information.

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

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

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

[0258] In some embodiments, the DCI includes the second information. The DCI is, 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 to schedule uplink transmission.

[0259] Step S3106: The terminal 101 determines the FDRA region according to the activated uplink bandwidth part Active UL BWP.

[0260] The optional implementation of step S3106 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0261] Step S3107: The terminal 101 determines the FDRA domain according to the initial uplink bandwidth part Initial UL BWP.

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

[0263] In some embodiments, the DCI format used for scheduling uplink transmission has a fixed size and does not change due to the different slot types in which the uplink transmission it schedules is located.

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

[0265] In some embodiments, the frequency domain resource allocation type of uplink transmission is resource assignment (RA) type0.

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

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

[0268] In step S3108, the terminal 101 determines the granularity of the RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP.

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

[0270] In step S3109, the terminal 101 determines a resource block set RBG for uplink transmission in the UL Subband according to the bitmap Bitmap in the FDRA field.

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

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

[0273] The optional implementation of step S3110 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment 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 one by one to the other RBGs in sequence.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0288] The communication method involved in the embodiments of the present 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 steps S3101+S3102+S3102 may be implemented as independent embodiments, but are not limited thereto.

[0289] In some embodiments, step S3105 and step S3106 are optional, and one or more of these steps may be omitted or replaced 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 replaced in different embodiments.

[0291] FIG3B is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0292] Step S3201: Determine the FDRA domain.

[0293] Optional implementations of step 3201 may refer to step S2105 of FIG. 2 , optional implementations of steps S3106 to S3107 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0294] Step S3202: determine frequency domain resources for uplink transmission.

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

[0296] The communication method involved in the embodiment of the present disclosure may include at least one of step S3201 and step S3202. For example, step S3201 may be implemented as an independent embodiment, and step S3202 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0297] FIG4A is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a communication indication method, which includes:

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

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

[0300] Step S4102 , the network device 102 sends first information to the terminal 101 .

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

[0302] In some embodiments, the first information is used to configure a UL subband for the 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 refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

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

[0306] Step S4103 , the network device 102 sends second information to the terminal 101 .

[0307] The optional implementation of step S4103 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

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

[0309] In some embodiments, step S4105 and step S3106 are optional, and one or more of these steps may be omitted or replaced 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 replaced in different embodiments.

[0311] FIG4B is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0312] Step S4201: configure an uplink subband UL subband.

[0313] In an optional embodiment, step S4201 includes a lower-level solution. The optional implementation method of step S4201 can be found in step S2101 of Figure 2, the optional implementation method 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: indicating frequency domain resources for uplink transmission.

[0315] In an optional embodiment, step S4202 includes a lower-level solution. The optional implementation method of step S4202 can be found in step S2103 of Figure 2, the optional implementation method 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 the present disclosure may include at least one of step S4201 and step S4202. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, and steps S4201+S4202 may be implemented as independent embodiments, but are not limited thereto.

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

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

[0319] The optional implementation of step S5101 can refer to the optional implementation 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 an uplink subband UL Subband;

[0321] The optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2, 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] 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 refer to 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] Step S5104: The terminal receives the DCI and determines uplink frequency domain resources based on the DCI. The uplink frequency domain resources are resources used for uplink transmission in the UL Subband.

[0325] Optional implementations of step S5104 may refer to step S2104 in FIG. 2 , steps S3104 to S3116 in FIG. 3 , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 , which will not be described in detail here.

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

[0327] Figure 6 is a schematic diagram of a communication indication method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of 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 is 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 may be within the UL subband of the SBFD slot, or within the active UL BWP of the non-SBFD slot.

[0331] Optionally, the terminal is a SBFD Aware UE that can perceive sub-band full-duplex.

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

[0333] FIG9A is a schematic diagram of a BWP according to an embodiment of the present disclosure. As shown in FIG9A , the frequency domain resources used for uplink transmission and downlink transmission in the same time slot have the following three situations:

[0334] Case 1: The frequency domain resources used for DL ​​transmission and UL transmission in a DL slot are independent and non-overlapping.

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

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

[0337] Optionally, the TDD UL-DL configuration of the current system is DDDDDDSUUU, where D represents a DL slot and U represents a UL slot. 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 frequency band, the center frequencies of the DL BWP and the UL BWP need to be aligned. Figure 9B is a schematic diagram of a BWP according to an embodiment of the present disclosure. As shown in Figure 9B, the center frequencies of the DL BWP and the UL BWP are aligned.

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

[0339] Optionally, the terminal determines the RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the activated uplink bandwidth part Active UL BWP; or,

[0340] Optionally, the terminal determines an RBG Index corresponding to a resource block set RBG in the uplink bandwidth part UL BWP according to 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 in the FDRA field corresponds to an RBG Index.

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

[0344] Optionally, the DCI format used for scheduling uplink transmission has a fixed size and does not change due to the different slot types in which the uplink transmission scheduled thereby is located.

[0345] Step S6103: The terminal determines frequency domain resources for uplink transmission according to the FDRA field 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 indicates the RBG used for uplink transmission through the bitmap in the FDRA field in the uplink DCI.

[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 according to the Active UL BWP.

[0349] The highest bit in FDRA corresponds to the RBG with the largest RBG Index in the UL BWP, or the highest bit in 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, resource allocation of the SBFD Aware UE on the UL subband includes:

[0351] The highest bit in FDRA corresponds to the RBG with the largest RBG Index in the UL subband, or the highest bit in 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 the UL BWP, and the other bits are mapped one-to-one with the remaining RBGs, that is, the highest bit in the bitmap corresponds to RBG#0, and the remaining bits correspond to RBG#1 to RBG#N respectively.

[0353] In one possible embodiment, part of the frequency domain of the UL subband is within the UL BWP. The UL BWP has 10 RBGs, and the bitmap in the FDRA information field in the DCI is 1110000000. The RBGs corresponding to positions coded as 1 in the bitmap are used for uplink transmission. RBG#0, RBG#1, and RBG#2 are then determined as resource locations 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 the UL BWP, and the other bits are mapped one-to-one with the remaining RBGs, that is, the highest bit in the bitmap corresponds to RBG#0, and the remaining bits correspond to RBG#1 to RBG#N respectively.

[0355] Part of the frequency domain of the UL subband lies within the UL BWP. The UL BWP has 10 RBGs, and the bitmap in the FDRA information field in the DCI is 0000111000. Positions coded as 1 in the bitmap correspond to RBGs used for uplink transmission. RBG#4, RBG#5, and RBG#6 are then determined as resource locations for uplink transmission. Accordingly, terminal 101 determines the resource locations within the UL subband used for uplink transmission based on the indication.

[0356] Optionally, resource allocation of the SBFD Aware UE on the UL subband includes:

[0357] Optionally, the Active UL BWP contains 10 RBGs. Assume that network device 102 schedules an SBFD-Aware UE for uplink transmission on a UL subband within the SBFD slot. Assume that the bitmap in the FDRA information field in the DCI is 1110000000 or 0000111000, 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. Accordingly, terminal 101 determines the resource location for uplink transmission within the UL subband based on the indication.

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

[0359] The communication method involved in the embodiments of the present 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, steps S6102+S6103 may be implemented as independent embodiments, and steps S6101+S6102+S6103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0360] In the embodiments of the present disclosure, 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 of other embodiments.

[0361] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0362] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0363] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0364] Figure 7A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 7A, terminal 7100 may include at least one of a transceiver module 7101 and a processing module 7102. In some embodiments, the transceiver module is configured to obtain an uplink subband (UL subband) configured by an access network device and determine the frequency domain resource allocation (FDRA) field in the downlink control information (DCI) for scheduling the physical uplink shared channel (PUSCH) transmitted in the UL subband. The processing module is configured to determine the frequency domain resources 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 sending and / or receiving performed by the terminal 101 in any of the above methods (for example, step 2102, but not limited thereto), which are not described in detail here. Optionally, the processing module is used to perform at least one of the other steps (for example, step 2104, but not limited thereto) performed by the terminal 101 in any of the above methods, which are not described in detail here.

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

[0367] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step 2101, step 2103 but not limited thereto) performed by the network device 102 in any of the above methods, which will not be repeated here.

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

[0369] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0370] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of 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, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform 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 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 transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2101 and step 2103, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step 2102 and step 2104, but not limited thereto).

[0374] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit 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. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0377] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0378] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0379] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the 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 (for example, step 2101, step 2103, but not limited to this), and the processor 8201 performs at least one of the other steps (for example, step 2102, step 2104, but not limited to this).

[0381] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

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

[0383] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0384] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0385] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication indication method, characterized in that: The method comprises: Determine the uplink subband UL Subband; receiving downlink control information DCI, where the DCI is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband; An uplink frequency domain resource is determined based on the DCI, where the uplink frequency domain resource is a resource used for uplink transmission in a UL Subband.

2. The method according to claim 1, characterized in that The DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine the uplink frequency domain resources.

3. The method according to claim 2, characterized in that The determining the uplink frequency domain resources based on the DCI includes: The uplink frequency domain resources are determined according to a bit map Bitmap in the FDRA field, wherein the uplink frequency domain resources include a resource block set RBG, and the bit map is used to indicate an RBG Index corresponding to the RBG in the uplink frequency domain resources.

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

5. The method according to claim 3, characterized in that: The determining the uplink frequency domain resources according to the bitmap Bitmap in the FDRA domain also includes: The highest bit of the bitmap in the FDRA field corresponds to the RBG with the largest RBG Index in the UL Subband, and the other bits in the bitmap are mapped one by one with the other RBGs in sequence; or, The highest bit of the Bitmap in the FDRA field corresponds to the RBG with the smallest RBG Index in the UL Subband, and the other bits in the Bitmap are mapped one by one with the other RBGs in sequence.

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

7. The method according to any one of claims 3 to 6, characterized in that: The Bitmap indicates a first frequency domain resource, the first frequency domain resource includes a first RBG, the first RBG 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.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Determine the RBG index Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP according to the activated uplink bandwidth part Active UL BWP; or, The RBGIndex corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined according to the initial uplink bandwidth part Initial UL BWP.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Determine the granularity of RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP; Or, the granularity of the RBG in the UL Subband is determined according to the size of the Active UL BWP.

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

11. The method according to any one of claims 1 to 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 comprises: Configure an uplink subband UL subband for the terminal; Sending DCI, wherein the DCI is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband, and the DCI is used to indicate uplink frequency domain resources, and the uplink frequency domain resources are resources used for uplink transmission in the UL Subband.

13. The method according to claim 12, characterized in that The DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine the uplink frequency domain resources.

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

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

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

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

18. The method according to any one of claims 14 to 17, characterized in that: The Bitmap indicates a first frequency domain resource, the first frequency domain resource includes a first RBG, the first RBG 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.

19. The method according to any one of claims 12 to 18, characterized in that: The RBGIndex corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined by the activated uplink bandwidth part Active UL BWP; or, The RBG Index corresponding to the resource block set RBG in the uplink bandwidth part UL BWP is determined by the initial uplink bandwidth part Initial UL BWP.

20. The method according to any one of claims 12 to 19, characterized in that The method further comprises: Determine the granularity of RBG in the uplink bandwidth part UL BWP according to the size of the Active UL BWP; Or, the granularity of the RBG in the UL Subband is determined according to the size of the Active UL BWP.

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

22. The method according to any one of claims 1 to 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 comprises: The network device configures an uplink subband UL subband for the terminal; The terminal determines the uplink subband UL Subband; The network device sends a DCI, where the DCI is used to schedule a physical uplink shared channel PUSCH transmitted in the UL subband; The terminal receives the DCI, and determines uplink frequency domain resources based on the DCI, where the uplink frequency domain resources are resources used for uplink transmission in a UL Subband.

24. The method according to claim 23, characterized in that The DCI includes a frequency domain resource allocation FDRA field, and the FDRA field is used to determine the uplink frequency domain resources.

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

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 to 11.

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

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

29. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of claims 1-11 or 12-22.

Images