Uplink transmission method and device

Abstract

An embodiment of the present application provides an uplink transmission method and apparatus; the method comprises: a terminal device receives indication information that does not include an indication field for indicating a resource block set, wherein the indication information schedules an uplink transmission on an uplink partial bandwidth including at least two resource block sets; and sends the uplink transmission on at least one predefined or preconfigured resource block set.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Unlicensed bands, or shared spectrum, are an important part of spectrum resources. Currently, many systems support data transmission in unlicensed bands, such as WiFi, Long Term Evolution (LTE), License Assisted Access (LAA), etc. However, the New Radio (NR) system does not support unlicensed bands yet.

[0003] With the introduction of BandWidth Part (BWP), one or more BWPs can be pre-configured for the terminal device. Different sub-carrier spacings (SCS) can be configured for different BWPs, for example, SCS can be 15kHz, 30kHz, etc. The terminal device can work with an activated BWP (active BWP) and can switch BWPs based on signaling, such as Radio Resource Control (RRC) messages, downlink control information (DCI) or timer status.

[0004] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of the present application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because they are described in the background technology section of the present application. Summary of the invention

[0005] However, the inventors have discovered that when an uplink transmission is scheduled on an uplink BWP including at least two resource block sets (RB sets), or when the terminal device is indicated that the frequency resources have no guard band, or when the terminal device is instructed to perform BWP switching, the terminal device may be unable to determine the resources used for the uplink transmission, thereby causing the uplink transmission to not be correctly sent and received.

[0006] In response to at least one of the above problems, an embodiment of the present application provides an uplink transmission method and apparatus, which can support a terminal device to determine resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0007] According to one aspect of an embodiment of the present application, there is provided an uplink transmission method, including:

[0008] The terminal device receives indication information that does not include an indication field for indicating a resource block set, wherein the indication information schedules uplink transmission on an uplink portion of a bandwidth including at least two resource block sets; and

[0009] The uplink transmission is sent on at least one predefined or preconfigured set of resource blocks.

[0010] According to another aspect of an embodiment of the present application, an uplink transmission device is provided, including:

[0011] a receiving unit, configured to receive indication information not including an indication field for indicating a resource block set, wherein the indication information schedules uplink transmission on an uplink partial bandwidth including at least two resource block sets; and

[0012] A sending unit is configured to send the uplink transmission on at least one predefined or preconfigured resource block set.

[0013] According to another aspect of an embodiment of the present application, there is provided an uplink transmission method, including:

[0014] The terminal device receives indication information for scheduling the terminal device to send uplink transmission;

[0015] The number of frequency domain resource allocation bits is determined according to the subcarrier spacing of the activated uplink portion of the bandwidth when the indication information is received and / or the number of resource block sets included; or, the number of frequency domain resource allocation bits is determined according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, the number of frequency domain resource allocation bits is determined according to the subcarrier spacing of a specific uplink portion of the bandwidth configured in at least one uplink portion of the bandwidth and / or the number of resource block sets included.

[0016] According to another aspect of an embodiment of the present application, an uplink transmission device is provided, including:

[0017] A receiving unit, which receives indication information for scheduling the terminal device to send uplink transmission;

[0018] A processing unit, which determines the number of frequency domain resource allocation bits according to the subcarrier spacing of the activated uplink partial bandwidth and / or the number of resource block sets included when receiving the indication information; or, determines the number of frequency domain resource allocation bits according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink partial bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, determines the number of frequency domain resource allocation bits according to the subcarrier spacing of a specific uplink partial bandwidth in at least one configured uplink partial bandwidth and / or the number of resource block sets included.

[0019] According to another aspect of an embodiment of the present application, there is provided an uplink transmission method, including:

[0020] The terminal device receives first configuration information indicating a guard band and / or a resource block set of an uplink carrier; and

[0021] The terminal device determines the resource blocks included in the resource block set on the uplink carrier according to the frequency domain position of the starting resource block and / or the frequency domain position of the ending resource block of the protection band.

[0022] According to another aspect of an embodiment of the present application, an uplink transmission device is provided, including:

[0023] a receiving unit, configured to receive first configuration information indicating a guard band and / or a resource block set of an uplink carrier; and

[0024] A processing unit determines the resource blocks included in the resource block set on the uplink carrier according to the frequency domain position of the starting resource block and / or the frequency domain position of the ending resource block of the guard band.

[0025] According to another aspect of an embodiment of the present application, there is provided an uplink transmission method, including:

[0026] receiving indication information for scheduling uplink transmission, the indication information comprising an indication field for indicating a resource block set (RBset), the indication information indicating at least two resource block sets (RBset); and

[0027] A resource block for sending the uplink transmission is determined according to the indication information, and the uplink transmission is sent on the determined resource block.

[0028] According to another aspect of an embodiment of the present application, an uplink transmission device is provided, including:

[0029] a receiving unit, configured to receive indication information for scheduling uplink transmission, wherein the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RB sets); and

[0030] a sending unit, which determines a resource block for sending the uplink transmission according to the indication information,

[0031] The sending unit also sends the uplink transmission on the determined resource block.

[0032] According to another aspect of an embodiment of the present application, there is provided an uplink transmission method, including:

[0033] receiving indication information indicating resources used by a terminal device for sending uplink transmission; and

[0034] In the case where the downlink carrier is configured without a guard band, a predetermined number of resource blocks in a downlink partial bandwidth (DLBWP) is used as a predefined or preconfigured resource block set, and the uplink transmission is sent on the predefined or preconfigured resource block set.

[0035] According to another aspect of an embodiment of the present application, an uplink transmission device is provided, including:

[0036] A receiving unit, which receives indication information indicating resources used by a terminal device to send uplink transmission; and

[0037] A sending unit, which, when a downlink carrier is configured to have no guard band, uses a predetermined number of resource blocks in a downlink partial bandwidth (DL BWP) as a predefined or preconfigured resource block set, and sends the uplink transmission on the predefined or preconfigured resource block set.

[0038] According to another aspect of an embodiment of the present application, there is provided an uplink transmission receiving method, including:

[0039] Sending indication information for scheduling uplink transmission, the indication information comprising an indication field for indicating a resource block set (RBset), the indication information indicating at least two resource block sets (RBset); and

[0040] A resource block for receiving the uplink transmission is determined according to the indication information, and the uplink transmission is received on the determined resource block.

[0041] According to another aspect of an embodiment of the present application, there is provided an uplink transmission receiving device, including:

[0042] a first sending unit, configured to send indication information for scheduling uplink transmission, wherein the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RB sets); and

[0043] A first receiving unit receives the uplink transmission according to whether the terminal device indicates that the terminal device can send the uplink transmission in an intra-cell guard band.

[0044] One of the beneficial effects of the embodiments of the present application is that it can support a terminal device to determine resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0045] With reference to the following description and accompanying drawings, the specific embodiments of the present application are disclosed in detail, indicating the way in which the principles of the present application can be adopted. It should be understood that the embodiments of the present application are not limited in scope. Within the scope of the spirit and clauses of the appended claims, the embodiments of the present application include many changes, modifications and equivalents.

[0046] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0047] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The elements and features described in one figure or one implementation of the present application embodiment may be combined with the elements and features shown in one or more other figures or implementations. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one implementation.

[0049] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0050] Figure 2 This is an example diagram of BWP switching;

[0051] Figure 3 is an example diagram of a guard band and a resource block set;

[0052] Figure 4 An example diagram of the relationship between carriers, guard bands, and resource block sets

[0053] Figure 5 This is an example diagram of interlace frequency domain resources;

[0054] Figure 6 It is a schematic diagram of the interaction between network devices and terminal devices;

[0055] Figure 7 is a schematic diagram of an uplink transmission method according to an embodiment of the present application;

[0056] Fig. 8A is another schematic diagram of the uplink transmission method according to an embodiment of the present application;

[0057] Figure 8B This is a schematic diagram of a DL carrier that is not configured with an intra-cell guard band;

[0058] Figure 8C This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0059] Fig.8D This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0060] Fig. 8E This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0061] Fig.8F This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0062] Figure 8G This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0063] Figure 8H This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0064] Figure 8I This is another diagram of a DL carrier that is not configured with an intra-cell guard band;

[0065] Figure 8J This is a schematic diagram of a DL carrier configured with an intra-cell guard band;

[0066] Figure 8K This is another diagram of a DL carrier configured with an intra-cell guard band;

[0067] Figure 8LThis is another diagram of a DL carrier configured with an intra-cell guard band;

[0068] Figure 8M It is a schematic diagram of complete overlap;

[0069] Figure 8N It is a schematic diagram of complete overlap;

[0070] Fig. 9 is an example diagram of the relationship between the downlink RB set of the downlink carrier and the uplink RB set of the uplink carrier in an embodiment of the present application;

[0071] Fig.10 is an example diagram of the relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP in an embodiment of the present application;

[0072] Fig.11 is another example diagram of the relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP in an embodiment of the present application;

[0073] Fig.12 is another example diagram of the relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP in an embodiment of the present application;

[0074] Fig.13 is another schematic diagram of the uplink transmission method according to an embodiment of the present application;

[0075] Fig.14 is another schematic diagram of the uplink transmission method according to an embodiment of the present application;

[0076] Fig.15 is another schematic diagram of the uplink transmission method according to an embodiment of the present application;

[0077] Fig.16A is another schematic diagram of the uplink transmission method according to an embodiment of the present application;

[0078] Fig. 16B A schematic diagram of a terminal device determining a resource block for sending an uplink transmission when the terminal device indicates that it can send an uplink transmission in an intra-cell guard band;

[0079] Fig. 16C is a schematic diagram of a terminal device determining a resource block for sending an uplink transmission when the terminal device does not indicate that it can send an uplink transmission in an intra-cell guard band;

[0080] Fig.17is a schematic diagram of an uplink transmission receiving method according to an embodiment of the present application;

[0081] Fig.18A is a schematic diagram of a UL BWP including a portion of RBs of an RB set;

[0082] Fig.18B is a schematic diagram of a UL BWP including a portion of RBs of an RB set;

[0083] Fig.18C is a schematic diagram of a UL BWP including a portion of RBs of an RB set;

[0084] Fig.18D It is a schematic diagram of a terminal device determining resources for sending a PUSCH based on the RB set included in the active UL BWP after receiving downlink control information;

[0085] Fig.18E It is a schematic diagram of a terminal device determining resources for sending a PUSCH based on the RB set included in the active UL BWP after receiving a random access response;

[0086] Fig.18F is a schematic diagram of an uplink transmission method according to an embodiment of the present application;

[0087] Figure 18G is a schematic diagram of an uplink transmission method according to an embodiment of the present application;

[0088] Fig.19 is a schematic diagram of an uplink transmission device according to an embodiment of the present application;

[0089] Fig. 20 is a schematic diagram of a network device according to an embodiment of the present application;

[0090] Fig.21 It is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0091] With reference to the accompanying drawings, the above and other features of the present application will become apparent through the following description. In the description and the accompanying drawings, specific embodiments of the present application are specifically disclosed, which show some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents falling within the scope of the attached claims.

[0092] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0093] In the embodiments of the present application, the singular forms "a", "the", etc. include plural forms and should be broadly understood as "a kind" or "a type" rather than being limited to the meaning of "one"; in addition, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least in part according to...", and the term "based on" should be understood as "at least in part based on...", unless the context clearly indicates otherwise.

[0094] In an embodiment of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed ​​Packet Access (HSPA, High-Speed ​​Packet Access), etc.

[0095] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0096] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. The network device may include, but is not limited to, the following devices: a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.

[0097] Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.). And the term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographical area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0098] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. The terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and the like.

[0099] Among them, the terminal device may include but is not limited to the following devices: cellular phone, personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, cordless phone, smart phone, smart watch, digital camera, etc.

[0100] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measuring, such as but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device to device (D2D) terminal, machine to machine (M2M) terminal, and the like.

[0101] In addition, the term "network side" or "network device side" refers to one side of the network, which may be a base station, or may include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to one side of the user or terminal, which may be a UE, or may include one or more terminal devices as described above.

[0102] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0103] Figure 1 Schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation in which a terminal device and a network device are used as an example. Figure 1 As shown, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 Only two terminal devices and one network device are taken as an example for description, but the embodiments of the present application are not limited to this.

[0104] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), and the like.

[0105] Figure 2 This is an example diagram of BWP switching. Figure 2 As shown, the terminal device can switch between BWP1, BWP2, and BWP3.

[0106] For unlicensed frequency bands (or shared frequency bands), RRC signaling is added to configure frequency domain resources.

[0107] On the one hand, considering the coexistence between systems, in some cases, it is necessary to introduce an intra-cell guard band (hereinafter referred to as guard band), that is, within the carrier bandwidth, some resource blocks cannot be used to send downlink transmission or uplink transmission.

[0108] Figure 3 is an example diagram of a guard band and a resource block set, such as Figure 3 As shown, for example, for a carrier bandwidth with an SCS of 15 kHz, there is a guard band 201 between two resource block sets. Further, when configuring a BWP for the terminal device, a BWP should not overlap with a resource block set. That is, a BWP should include an integer number of resource block sets.

[0109] Figure 4 This is an example diagram of the relationship between carriers, guard bands, and resource block sets, applicable to both downlink and uplink. Figure 4 As shown, BWP0 and BWP1 each include an integer number (eg, two) of RBsets.

[0110] The network device can indicate the intra-cell guard band and / or resource block set through high-layer signaling. For example, intraCellGuardBandUL-r16 and intraCellGuardBandDL-r16 are used to configure the intra-cell guard band and / or resource block set (RB set) for uplink and downlink respectively; these two parameters can also indicate that there is no intra-cell guard band for uplink and downlink respectively. If the terminal device is not provided with these two parameters, the terminal device can determine the intra-cell guard band and / or resource block set according to the RAN4 protocol.

[0111] On the other hand, in some cases, uplink transmission needs to be sent using interlaced resource blocks (i.e., uplink frequency resource allocation Type 2). For example, the correspondence between the subcarrier spacing and the number of interlaces is shown in Table 1 below. That is, if the subcarrier spacing is 15kHz (μ=0), it is divided into 10 RB interlaces (M=10); if the subcarrier spacing is 30kHz (μ=1), it is divided into 5 RB interlaces (M=5).

[0112] Table 1

[0113] μ M 0 10 1 5

[0114] Figure 5This is an example diagram of interlace frequency domain resources. Assume that the uplink carrier includes 100 RBs with a subcarrier spacing of 15kHz. Figure 5 As shown, the RBs may be divided into a plurality of groups (referred to as RB interlaces), where group 0 (RB interlace 0) includes, for example, RB0, RB10, ..., RB90, and group 1 (RB interlace 1) includes RB1, RB11, ..., RB91, .... According to the scheduling of the network device, the terminal device may use an integer number of groups (RB interlaces) to send an uplink transmission, for example, RB0, RB10, ..., RB90 (i.e., RB interlace 0) may be used to send an uplink transmission.

[0115] The network device can instruct the terminal device to use interlaced resource blocks (i.e., uplink frequency resource allocation Type 2) to send uplink transmission through high-level signaling. The high-level signaling is, for example, useInterlacePUSCH-Common-r16, useInterlacePUSCH-Dedicated-r16, useInterlace PUCCH-Common-r16, useInterlacePUCCH-Dedicated, useInterlacePUCCH-PUSCH, useInterlacePUCCH-PUSCH-r16, etc.

[0116] Figure 6 It is a schematic diagram of the interaction between network devices and terminal devices, such as Figure 6 As shown, the network device can send guard band and / or RB set configuration information to the terminal device, and can also send BWP configuration information to the terminal device. These two types of configuration information can be sent simultaneously (for example, included in the same RRC message) or separately (not simultaneously).

[0117] like Figure 6 As shown, the network device can send indication information for scheduling uplink transmission to the terminal device on the active DL BWP. After the terminal device determines the frequency domain resources on the UL BWP, it sends the uplink transmission on the determined frequency domain resources.

[0118] Figure 6 The interaction between the network device and the terminal device in the embodiment of the present application is schematically described, but the present application is not limited thereto, for example, one or more operations therein may be omitted, or one or more other operations may be added.

[0119] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" may be used interchangeably, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" may be used interchangeably without causing confusion;

[0120] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, and the terms “downlink data signal” and “downlink data information” or “physical downlink shared channel (PDSCH)” are interchangeable.

[0121] In addition, sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH, sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH, and sending or receiving PRACH can be understood as sending or receiving preamble carried by PRACH; uplink signals can include uplink data signals and / or uplink control signals, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channels. Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0122] In the embodiment of the present application, the high-level signaling may be, for example, radio resource control (RRC) signaling; for example, called an RRC message, including, for example, MIB, system information, dedicated RRC message; or called an RRC IE (RRC information element). The high-level signaling may also be, for example, MAC (Medium Access Control) signaling; or called a MAC IE (MAC information element). However, the present application is not limited thereto.

[0123] Embodiments of the first aspect

[0124] In the case where uplink transmission is scheduled on an uplink BWP including at least two resource block sets (RB sets), the terminal device may be unable to determine the resources used for the uplink transmission, thereby causing the uplink transmission to be unable to be correctly sent and received.

[0125] For example, DCI format 0_0 does not include an indication field for indicating an RB set, but DCI format 0_0 is used to schedule uplink transmission on a UL BWP including at least two RB sets. In this case, it is currently not possible to support the terminal device to determine the RB set used to send the uplink transmission. In other words, if the terminal device receives DCI format 0_0, and the activeUL BWP includes at least two RB sets, the terminal device cannot uniquely determine the resources used for the uplink transmission, which may cause the uplink transmission to not be correctly sent and received.

[0126] At least for this problem, the embodiment of the present application provides an uplink transmission method, which is explained from the terminal device side. The interaction process between the terminal device and the network device can refer to Figure 6 .

[0127] Figure 7 is a schematic diagram of an uplink transmission method according to an embodiment of the present application. Figure 7 As shown, the method includes:

[0128] 701, a terminal device receives configuration information of an uplink bandwidth (UL BWP), where the configuration information of the uplink bandwidth (UL BWP) indicates that the uplink bandwidth includes at least two resource block sets (RB sets);

[0129] 702. The terminal device does not monitor or receive first indication information for scheduling uplink transmission, which does not include an indication field for indicating a resource block set, on a downlink partial bandwidth (DL BWP) corresponding to the uplink partial bandwidth.

[0130] It is worth noting that the above Figure 7 The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order of the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the above appended Figure 7 Records of.

[0131] In some embodiments, the configuration information of the uplink bandwidth (UL BWP) may be BWP-Uplink, for example, as shown in the following Table 2:

[0132] Table 2

[0133]

[0134] More specifically, the genericParameters included in BWP-UplinkCommon includes an information element (IE) for indicating the SCS, frequency domain position and bandwidth of the UL BWP, as shown in Table 3. The terminal device can determine the number of RB sets (and frequency domain positions) included in the UL BWP based on the IE.

[0135] Table 3

[0136]

[0137] In some embodiments, one DL BWP among the configured at least one DL BWP is linked / associated / paired with, corresponds to, one UL BWP among the configured at least one UL BWP. Generally, one DL BWP is linked / associated with only one UL BWP. One UL BWP may be linked / corresponded to one or more than one DL BWP.

[0138] The association / correspondence between the DL BWP and the UL BWP here means, for example, that when a terminal device receives indication information for scheduling uplink transmission on a DL BWP, if the indication information does not include an indication field for indicating the BWP, or the indication information includes an indication field for indicating the BWP but the terminal device ignores the indication field, then the terminal device sends uplink transmission on the UL BWP associated / corresponding to the DLBWP.

[0139] The association / correspondence relationship may be predefined, for example, the uplink bandwidth portion and the corresponding downlink bandwidth portion have the same identifier (bwp-Id) or index (index). For downlink and uplink respectively, the index is provided by the bwp-Id in BWP-Downlink (downlink) / BWP-Uplink (uplink), which can uniquely identify a BWP. That is, the UL BWP with an index of n (n is a natural number) is associated / corresponding to the DL BWP with an index of n (n is a natural number). At this time, a ULBWP has at most one associated / corresponding DL BWP, and vice versa.

[0140] Alternatively, the association / correspondence relationship may be configured by high-level signaling. For example, an IE is added in BWP-Uplink to indicate the UL BWP is associated with / corresponds to the DL BWP, as shown in Table 4 or Table 5. Alternatively, an IE is added in BWP-Downlink to indicate the DL BWP is associated with / corresponds to the UL BWP, as shown in Table 6.

[0141] Table 4

[0142]

[0143] Table 5

[0144]

[0145] Table 6

[0146]

[0147]

[0148] In some embodiments, the first indication information includes: downlink control information having a downlink control information format 0_0, or downlink control information having a downlink control information format 0_2 (excluding an indication field for indicating a resource block set), or a random access response (RAR) in a random access procedure.

[0149] In some embodiments, the terminal device does not expect to configure or determines not to configure to monitor or receive the first indication information on the downlink partial bandwidth corresponding to the uplink partial bandwidth. That is, the terminal device expects to configure or determines to configure to monitor or receive the indication information for scheduling uplink transmission on the DL BWP corresponding to the UL BWP, including an indication field for indicating a resource block set, such as downlink control information with downlink control information format 0_1, or downlink control information with downlink control information format 0_2 (including an indication field for indicating a resource block set).

[0150] For example, if a UL BWP includes two or more RB sets, the terminal device is not configured on the DLBWP associated / corresponding to the UL BWP to monitor downlink control information with DCI format 0_0 and / or downlink control information with DCI format 0_2. Thus, the configuration of the network device can be limited to prevent the UE from monitoring or receiving indication information for scheduling uplink transmission that does not include an indication field for indicating a resource block set when the active UL BWP is a UL BWP including at least two RB sets, thereby avoiding the above-mentioned problem and saving power consumption of the terminal device (power saving).

[0151] In some embodiments, the terminal device does not monitor or receive the second indication information for scheduling downlink transmission on the downlink partial bandwidth corresponding to the uplink partial bandwidth. The second indication information includes: downlink control information having downlink control information format 1_0.

[0152] For example, if a UL BWP includes two or more RB sets, the terminal device is not configured on the DL BWP corresponding to the UL BWP to monitor DCI format 0_0 and DCI format 1_0. Thus, the configuration of the network device can be limited to prevent the UE from monitoring or receiving the indication information for scheduling uplink transmission that does not include the indication field for indicating the resource block set when the active UL BWP is a UL BWP including at least two RB sets, thereby avoiding the above-mentioned problem and saving the power consumption of the terminal device (power saving).

[0153] In some embodiments, the terminal device does not send a physical random access channel (PRACH) for contention-based random access (CBRA) on the uplink portion of the bandwidth; or, the terminal device does not send a physical random access channel (PRACH) other than that used for CFRA-based beam failure recovery (BFR) on the uplink portion of the bandwidth; or, the terminal device does not send a physical random access channel (PRACH) on the uplink portion of the bandwidth.

[0154] For example, in a contention-based random access (CBRA) process, the indication information used to schedule uplink transmission includes a random access response (RAR) and a DCI (TC-RNTI scrambled DCI format 0_0) used to schedule retransmission of msg.3.

[0155] If these indication information do not include an indication field for indicating an RB set, in the case where the use of these indication information to schedule an uplink transmission on a UL BWP including at least two RB sets is not supported, or in other words, if the terminal device does not support determining the frequency domain resources for sending the uplink transmission on a UL BWP including at least two RB sets based on these indication information, if a UL BWP includes two or more RB sets, the UE cannot perform CBRA on the UL BWP. In other words, if a UL BWP includes at least two RB sets, the terminal device does not perform CBRA on the UL BWP (including not sending PRACH for CBRA).

[0156] In some embodiments, the configuration information of the uplink bandwidth portion (UL BWP) does not include information for indicating a physical random access channel configuration for contention-based random access. Specifically, in order to avoid unnecessary signaling overhead, if a UL BWP includes two or more RB sets, a PRACH for CBRA is not configured on the UL BWP. That is, if a UL BWP includes two or more RB sets, the configuration information of the uplink bandwidth portion (UL BWP) does not include information for indicating a physical random access channel configuration for CBRA. For example, rach-ConfigCommon is not included in BWP-UplinkCommon, as shown in Table 7 below.

[0157] Table 7

[0158]

[0159] For another example, for non-contention random access (CFRA, Contention-Free Random Access) other than that used for BFR, it is necessary to indicate the PDSCH corresponding to the RAR through DCI format 1_0 (RA-RNTI scrambling).

[0160] If monitoring or receiving downlink control information with DCI format 0_0 and monitoring or receiving downlink control information with DCI format 1_0 are bound configurations, then if the terminal device is not configured to monitor or receive downlink control information with DCI format 0_0 on a DL BWP, the terminal device will not be configured to monitor or receive downlink control information with DCI format 1_0 on a DL BWP.

[0161] Therefore, if a UL BWP includes two or more RB sets, in the case where the use of downlink control information with DCI format 0_0 to schedule uplink transmission on a UL BWP including at least two RB sets is not supported, or in other words, if the terminal device does not support determining the frequency domain resources for sending the uplink transmission on a UL BWP including at least two RB sets according to the downlink control information with DCI format 0_0, in order to avoid unnecessary signaling overhead, the terminal device should not be configured to monitor / receive DCI format 1_0 on the DL BWP associated / corresponding to the UL BWP. In this way, the terminal device cannot perform non-competitive random access other than that for BFR on the UL BWP. That is to say, if a UL BWP includes at least two RB sets, the terminal device does not perform non-competitive random access other than that for BFR on the UL BWP (including not sending PRACH for non-competitive random access other than that for BFR).

[0162] In some embodiments, the configuration information of the uplink bandwidth portion (UL BWP) does not include information for indicating the configuration of a physical random access channel other than for beam failure recovery. Specifically, in order to avoid unnecessary signaling overhead, if a UL BWP includes two or more RB sets, the UL BWP should not be configured with a PRACH for CFRA other than for BFR. That is, if a UL BWP includes at least two RB sets, the configuration information of the uplink bandwidth portion (UL BWP) does not include information for indicating the configuration of a PRACH for CFRA other than for BFR.

[0163] For another example, considering the possible problems of the above-mentioned CBRA and CFRA, in order to simplify the design and reduce the complexity, if a UL BWP includes at least two RB sets, the terminal device does not perform random access in the UL BWP (including not sending PRACH). In some embodiments, in order to avoid unnecessary signaling overhead, the uplink partial bandwidth (UL BWP) configuration information does not include information for indicating the physical random access channel configuration.

[0164] For example, rach-ConfigCommon is not included in BWP-UplinkCommon, and beamFailureRecoveryConfig is not included in BWP-UplinkDedicated, as shown in Table 8 below.

[0165] Table 8

[0166]

[0167]

[0168] In some embodiments, the terminal device receives configuration information of the DL BWP, and the configuration information of the DL BWP does not include configuration information instructing the terminal device to listen to or receive the first indication information, and / or does not include configuration information instructing the terminal device to listen to or receive the second indication information.

[0169] That is to say, in order to support the network device to schedule the terminal device to send uplink transmission on a UL BWP including at least two RB sets, the configuration information of the UL BWP associated / corresponding DL BWP should instruct the terminal device to listen to or receive indication information including an indication field for indicating the RB set, such as downlink control information having DCI format 0_1.

[0170] For example, the configuration information of DL BWP is BWP-Downlink, as shown in Table 9 below.

[0171] Table 9

[0172]

[0173]

[0174] For another example, BWP-DownlinkCommon does not include pdcch-ConfigCommon, as shown in Table 10 below.

[0175] Table 10

[0176]

[0177] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0178] It can be seen from the above embodiments that it is possible to support a terminal device to determine resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0179] Embodiments of the second aspect

[0180] The embodiment of the present application provides an uplink transmission method, which is described from the perspective of a terminal device. The interaction process between the terminal device and the network device can be referred to as follows: Figure 6 The embodiments of the present application may be combined with the embodiments of the first aspect, or may be implemented separately, and the contents that are the same as those of the embodiments of the first aspect will not be repeated.

[0181] refer to Figure 6 For example, the terminal device may receive configuration information of a UL BWP (first configuration information) and configuration information of a DL BWP corresponding to the UL BWP (second configuration information). The first configuration information indicates that the UL BWP includes at least two RBsets; the second configuration information indicates that the terminal device monitors or receives indication information for scheduling uplink transmission in the DL BWP that does not include an indication field for indicating a resource block set. For another example, the association / correspondence between the UL BWP and the DL BWP may refer to the embodiment of the first aspect.

[0182] Fig. 8A is a schematic diagram of an uplink transmission method according to an embodiment of the present application. Fig. 8A As shown, the method includes:

[0183] 801, a terminal device receives indication information that does not include an indication field for indicating a resource block set, the indication information scheduling the terminal device to send an uplink transmission on an uplink bandwidth portion (UL BWP) including at least two resource block sets (RB sets); and

[0184] 802: Send the uplink transmission on at least one predefined or preconfigured resource block set.

[0185] It is worth noting that the above Fig. 8A The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order of the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the above appended Fig. 8A Records of.

[0186] In some embodiments, the indication information includes: downlink control information having downlink control information format 0_0. The downlink control information is scrambled using a Cell Radio Network Temporary Identifier (C-RNTI), a Configured Scheduling RNTI (CS-RNTI), a Modulation and Coding Scheme C-RNTI, or a Temporary C-RNTI (TC-RNTI).

[0187] For example, the at least one resource block set is predefined, and the predefined resource block set includes at least one of the following:

[0188] An uplink resource block set in the at least two resource block sets that is associated with a downlink resource block set where a frequency domain resource for sending the indication information is located;

[0189] An uplink resource block set corresponding to the frequency domain resources used to send the indication information in the at least two resource block sets;

[0190] A resource block set having a smallest resource block set index value among the at least two resource block sets;

[0191] The resource block set with the lowest frequency domain position among the at least two resource block sets;

[0192] The resource block set with the highest frequency domain position in the at least two resource block sets;

[0193] A resource block set overlapping with the initial uplink portion bandwidth in the at least two resource block sets;

[0194] A resource block set in the at least two resource block sets that overlaps with part or all of the resource block sets included in the initial uplink portion of the bandwidth;

[0195] Part or all of the at least two resource block sets.

[0196] The above only schematically illustrates the predefined RB set, and the present application is not limited thereto. In addition, one or any combination of the above resource block sets may be used, and one or more of them may be used preferentially, and the present application does not limit the specific implementation manner.

[0197] Example 1: If the frequency range of RBs included in a UL RB set is greater than the frequency range of the frequency domain resources used to send the indication information, the UL RB set used is the uplink resource block set corresponding to the frequency domain resources used to send the indication information.

[0198] Example 2: If there is an RB set in the active UL BWP that overlaps with the initial UL BWP, the overlapping RB set can be used; otherwise, the uplink resource block set associated with the downlink resource block set where the frequency domain resources for sending the indication information are located in the at least two resource block sets is used, or the resource block set with the smallest resource block set index value in the at least two resource block sets is used.

[0199] Example 3: The at least one resource block set is indicated by high-level signaling; the high-level signaling indicates an association between an uplink resource block set and a downlink resource block set, or the high-level signaling configures an uplink resource block set scheduled by the indication information.

[0200] In addition, the above method of predefining a resource block set may also be combined with certain conditions.

[0201] Example 4, when the downlink carrier (DL carrier) is configured without an intra-cell guard band (intra-cell guard band) (or, when the DL carrier is not configured with an intra-cell guard band): if the uplink partial bandwidth (i.e., the activated uplink partial bandwidth (active UL BWP)) has an overlapping resource block set (RB set) with the first reference resource, the predefined RB set may be the resource block set in the uplink partial bandwidth (UL BWP) that overlaps with the first reference resource, wherein if the number of resource block sets in the UL BWP that overlap with the first reference resource is more than 2, the predefined resource block set may include the resource block set with the lowest frequency domain position or the smallest index value among the more than 2 resource block sets in the UL BWP that overlap with the first reference resource.

[0202] In Example 4, the first reference resource is, for example, all or part of the resources used to send the downlink control information (i.e., downlink control information having a downlink control information format 0_0, which is scrambled using C-RNTI or CS-RNTI or MCS-C-RNTI or TC-RNTI), wherein, in the case where the first reference resource is part of the resources used to send the downlink control information, the first reference resource is, for example, the resource element group (REG) or RB with the lowest frequency domain position or the smallest index value in the resources used to send the downlink control information.

[0203] Figure 8B This is a schematic diagram of a DL carrier that is not configured with an intra-cell guard band. Figure 8B As shown in FIG. 1 , the DL carrier is not configured with an intra-cell guard band, and the UL carrier is configured with an intra-cell guard band. Figure 8B In the example, it is assumed that the active UL BWP of the terminal device has an RB set (RB set 0) overlapping with the first reference resource, and the terminal device uses RB set 0 in the active UL BWP to send the PUSCH.

[0204] In addition, Figure 8BAnd in other figures: f represents frequency, UE's active UL BWP represents the activated uplink bandwidth of the terminal equipment; the frequency domain range of PUSCH represents the range of frequency domain resources used by the terminal equipment to send PUSCH (that is, the range of RBs included in the RB set where it is located in the active UL BWP, wherein the frequency domain resources (RBs) actually used to send PUSCH also depend on the interlace indicated by the indication information); in UE's active UL BWP, RB sets have corresponding indexes, such as RB set 0, RB set 1, etc.; in the RB set of the UL carrier, RB sets have corresponding indexes, such as RB set 0, RB set 1, etc.; the index of each RB set in the RB set of the UL carrier is independent of the index of each RB set in the UE's active UL BWP.

[0205] Figure 8C This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Figure 8C As shown in FIG. 1 , the DL carrier is not configured with an intra-cell guard band, and the UL carrier is not configured with an intra-cell guard band. Figure 8C In the example 5, assuming that the active UL BWP of the terminal device has an RB set (RB set 0) overlapping with the first reference resource, the terminal device uses RB set 0 in the active UL BWP to send PUSCH. Example 5, when the downlink carrier (DL carrier) is configured without an intra-cell guard band (or, when the DL carrier is not configured with an intra-cell guard band): If the uplink partial bandwidth (i.e., the activated uplink partial bandwidth (active UL BWP)) does not have an overlapping resource block set (RB set) with the first reference resource, the predefined RB set can be the resource block set with the lowest frequency domain position or the smallest index value of the UL BWP (e.g., RBset 0).

[0206] In Example 5, the first reference resource is, for example, all or part of the resources used to send the downlink control information (i.e., downlink control information having a downlink control information format 0_0, which is scrambled using C-RNTI or CS-RNTI or MCS-C-RNTI or TC-RNTI), wherein, in the case where the first reference resource is part of the resources used to send the downlink control information, the first reference resource is, for example, the resource element group (REG) or RB with the lowest frequency domain position or the smallest index value in the resources used to send the downlink control information.

[0207] Fig.8D This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Fig.8D As shown in FIG. 1 , the DL carrier is not configured with an intra-cell guard band, and the UL carrier is configured with an intra-cell guard band. Fig.8D In the present invention, it is assumed that the active UL BWP of the terminal device does not have a resource block set (RB set) overlapping with the first reference resource, and therefore, RB set 0 of the active UL BWP is used to send the PUSCH.

[0208] Fig. 8E This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Fig. 8E As shown, the DL carrier is not configured with an intra-cell guard band, and the UL carrier is not configured with an intra-cell guard band. Fig. 8E In the present invention, it is assumed that the active UL BWP of the terminal device does not have a resource block set (RB set) overlapping with the first reference resource, and therefore, RB set 0 of the active UL BWP is used to send the PUSCH.

[0209] Example 6, when the downlink carrier (DL carrier) is configured without an intra-cell guard band (or, the DL carrier is not configured with an intra-cell guard band): the predefined RB set can be the resource block set with the lowest frequency domain position or the smallest index value of the UL BWP (eg RB set 0).

[0210] Fig.8FThis is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Fig.8F As shown, the DL carrier is not configured with an intra-cell guard band, and the UL carrier is configured with an intra-cell guard band. Therefore, RB set 0 of the active UL BWP is used as the predefined RB set to send the PUSCH.

[0211] Figure 8G This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Figure 8G As shown, the DL carrier is not configured with an intra-cell guard band, and the UL carrier is not configured with an intra-cell guard band. Therefore, RB set 0 of the active UL BWP is used as the predefined RB set to send the PUSCH.

[0212] Figure 8H This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Figure 8H As shown, the DL carrier is not configured with an intra-cell guard band, and the UL carrier is configured with an intra-cell guard band. Therefore, RB set 0 of the active UL BWP is used as the predefined RB set to send the PUSCH.

[0213] Figure 8I This is another diagram showing that the DL carrier is not configured with an intra-cell guard band. Figure 8I As shown, the DL carrier is not configured with an intra-cell guard band, and the UL carrier is not configured with an intra-cell guard band. Therefore, RB set 0 of the active UL BWP is used as the predefined RB set to send the PUSCH.

[0214] Considering that when the DL carrier is not configured with an intra-cell guard band (or when the DL carrier is configured without an intra-cell guard band), there may be no corresponding RB set definition in the downlink, and therefore it is not possible to rely on the RB set of the DL BWP to determine which RB set of the UL BWP to use. In the above Examples 4, 5, and 6, which RB set in the UL BWP to use does not depend on the RB set of the DL BWP. Therefore, when the downlink carrier (DL carrier) is configured without an intra-cell guard band (intra-cell guard band) (or when the DL carrier is not configured with an intra-cell guard band), the terminal device can also determine the RB set in the UL BWP used to send uplink transmissions (e.g., PUSCH). In addition, the above Example 4, Example 5 or Example 6 can also be combined with other examples. For example, when the DL carrier is not configured with an intra-cell guard band (or when the DL carrier is configured without an intra-cell guard band), the predefined resource block set is as described in the above Example 4, Example 5 or Example 6, and when the DL carrier is configured with an intra-cell guard band, the predefined resource block set is as described in one of the following examples.

[0215] Example 7: When the DL carrier is configured with an intra-cell guard band, if the uplink partial bandwidth (i.e., the activated partial bandwidth (active UL BWP)) has a resource block set (RB set) that overlaps with the RBset in the DL BWP where the first reference resource is located, the predefined RB set may be a resource block set in the uplink partial bandwidth (UL BWP) that overlaps with the RB set in the DL BWP where the first reference resource is located, wherein if the number of resource block sets in the UL BWP that overlap with the RB set in the DL BWP where the first reference resource is located is 2 or more, the predefined resource block set may include the resource block set with the lowest frequency domain position or the smallest index value among the 2 or more resource block sets in the UL BWP that overlap with the RB set in the DL BWP where the first reference resource is located.

[0216] Figure 8J Figure 1 is a schematic diagram of a DL carrier configured with an intra-cell guard band. Figure 8JAs shown in FIG. 1 , the DL carrier is configured with an intra-cell guard band, and the UL carrier is also configured with an intra-cell guard band. Figure 8J RB set 0 in the activated partial bandwidth (active UL BWP) overlaps with the RB set in the DLBWP where the first reference resource is located, and thus, RB set 0 of the active UL BWP is used as the predefined RB set to send the PUSCH.

[0217] Figure 8K FIG. 1 is another schematic diagram of a DL carrier configured with an intra-cell guard band. Figure 8K As shown in FIG. 1 , the DL carrier is configured with an intra-cell guard band, and the UL carrier is not configured with an intra-cell guard band. Figure 8K RB set 0 in the activated partial bandwidth (active UL BWP) overlaps with the RB set in the DL BWP where the first reference resource is located, thereby using RB set 0 of the active UL BWP as the predefined RB set to send PUSCH. Example 8: In the case where the DL carrier is configured with an intra-cell guard band, if the uplink partial bandwidth (i.e., the activated partial bandwidth (active UL BWP)) does not have a resource block set (RB set) that overlaps with the RB set in the DL BWP where the first reference resource is located, the predefined RB set can be the resource block set with the lowest frequency domain position or the smallest index value in the uplink partial bandwidth (UL BWP).

[0218] Figure 8L Figure 1 is a schematic diagram of a DL carrier configured with an intra-cell guard band. Figure 8L As shown in FIG. 1 , the DL carrier is configured with an intra-cell guard band, and the UL carrier is also configured with an intra-cell guard band. Figure 8L The activated partial bandwidth (active UL BWP) has no RB set overlapping with the RB set in the DL BWP where the first reference resource is located, thus, the resource block set with the smallest index value of the active UL BWP (ie, RB set0) is used as the predefined RB set to send the PUSCH.

[0219] In some embodiments, the indication information includes: a random access response (RAR) in a random access procedure, or downlink control information having a downlink control information format 0_0 scrambled by using TC-RNTI.

[0220] For example, the at least one resource block set is predefined, and the predefined resource block set includes at least one of the following:

[0221] An uplink resource block set in the at least two resource block sets that is associated with a downlink resource block set where a frequency domain resource for sending the indication information is located;

[0222] An uplink resource block set corresponding to the frequency domain resources used to send the indication information in the at least two resource block sets;

[0223] A resource block set overlapping with the initial uplink portion bandwidth in the at least two resource block sets;

[0224] A resource block set in the at least two resource block sets that overlaps with part or all of the resource block sets included in the initial uplink portion of the bandwidth;

[0225] Some or all of the resource block sets in the at least two resource block sets;

[0226] The at least two resource block sets are resource block sets used to send the random access preamble sequence corresponding to the uplink transmission.

[0227] The above only schematically illustrates the predefined RB set, and the present application is not limited thereto. In addition, one or any combination of the above resource block sets may be used, and one or more of them may be used preferentially, and the present application does not limit the specific implementation manner.

[0228] In addition, the above method of predefining a resource block set may also be combined with certain conditions.

[0229] Example 9: If the uplink partial bandwidth (ie, the activated uplink partial bandwidth (active UL BWP)) has an overlapping resource block set (RB set) with the second reference resource, then the predefined resource block set includes: the resource block set in the uplink partial bandwidth that overlaps with the second reference resource.

[0230] Example 10, if the uplink partial bandwidth (i.e., the activated uplink partial bandwidth (active UL BWP)) does not have an overlapping resource block set (RB set) with the second reference resource, then the predefined resource block set includes: a resource block set in the uplink partial bandwidth used to send a random access preamble sequence (preamble) or a physical random access channel (PRACH). The preamble or PRACH is a preamble or PRACH sent by the terminal device before receiving a random access response (including RAR UL grant) in a random access process or receiving downlink control information (DCI format 0_0 addressed to TC-RNTI) with downlink control information format 0_0 scrambled by TC-RNTI.

[0231] In the above Examples 9 and 10: for uplink transmission scheduled by DCI format 0_0 addressed to TC-RNTI (e.g., PUSCH), the second reference resources include all or part of the resources used to send the downlink control information (e.g., downlink control information with downlink control information format 0_0 scrambled by TC-RNTI); for uplink transmission scheduled by RAR UL grant (PUSCH), the second reference resources include first downlink control information used to send a physical downlink shared channel (PDSCH) for scheduling a random access response, and the first downlink control information has, for example, a downlink control information format 1_0 (DCI format 1_0).

[0232] Example 11: If the uplink partial bandwidth (i.e., the activated uplink partial bandwidth (active UL BWP)) completely overlaps with the initial uplink partial bandwidth (initial UL BWP), the predefined resource block set includes: the resource block set in the initial uplink partial bandwidth, or the resource blocks in the resource block set of the uplink partial bandwidth that overlap with the initial uplink partial bandwidth.

[0233] Figure 8M is a schematic diagram of complete overlap. Figure 8MAs shown in FIG. 1 , the active UL BWP includes all RBs of the initial UL BWP, and the subcarrier spacing (SCS) and cyclic prefix (CP) length of the active UL BWP and the initial UL BWP are also the same (the active UL BWP and the initial UL BWP have same SCS and same CPlength and the active UL BWP includes all RBs of the initial UL BWP). In addition, as Figure 8M As shown, the UL carrier can be configured with an intra-cell guard band.

[0234] Figure 8N is a schematic diagram of complete overlap. Figure 8N As shown in FIG. 1 , the active UL BWP includes all RBs of the initial UL BWP, and the subcarrier spacing (SCS) and cyclic prefix (CP) length of the active UL BWP and the initial UL BWP are also the same (the active UL BWP and the initial UL BWP have same SCS and same CPlength and the active UL BWP includes all RBs of the initial UL BWP). In addition, as Figure 8N As shown, the UL carrier is not configured with an intra-cell guard band.

[0235] Example 12: If the uplink partial bandwidth (i.e., the activated uplink partial bandwidth (active UL BWP)) does not completely overlap with the initial uplink partial bandwidth (initial UL BWP), the predefined resource block set includes: a resource block set in the uplink partial bandwidth used to send a random access preamble sequence in a random access process.

[0236] Considering that when the DL carrier is not configured with an intra-cell guard band (or when the DL carrier is configured without an intra-cell guard band), there may be no corresponding RB set definition in the downlink, and therefore it is not possible to rely on the RB set of the DL BWP to determine which RB set of the UL BWP to use. For the PUSCH scheduled by DCI 0_0 addressed to TC-RNTI or RAR UL grant, in the above-mentioned Example 7, Example 8 or Example 9, which RB set in the UL BWP is used and the UL BWP are not dependent on the RB set of the DL BWP, even when the DL carrier is not configured with an intra-cell guard band (or when the DL carrier is configured without an intra-cell guard band), it is possible to support the terminal device to determine the RB set where the resources for sending the PUSCH are located; and, in contention-based random access (CBRA), even when the network device cannot confirm the active UL BWP of the terminal device, it is possible to easily determine the resources used by the terminal device to send uplink transmissions, and will not affect the scheduling of other terminal devices, thereby ensuring the performance of the communication system. On the other hand, when configuring PRACH and the UL BWP where the PRACH is located, the network device configures the subcarrier spacing (SCS) of PRACH to be the same as the SCS of the UL BWP. Thus, when the terminal device sends a random access preamble sequence (preamble) before receiving the indication information, the subcarrier spacing (SCS) of the physical random access channel (PRACH) used to send the random access preamble sequence is the same as the subcarrier spacing (SCS) of the uplink partial bandwidth (UL BWP) where the physical random access channel (PRACH) is located. In this way, in CBRA, the network device can determine the bits used to indicate frequency domain resources included in the RAR UL grant and / or TC-RNTI-scrambled DCI 0_0 based on the received SCS of the PRACH, and the terminal device can still determine the bits used to indicate frequency domain resources included in the RAR UL grant and / or TC-RNTI-scrambled DCI 0_0 based on the activated UL BWP. As a result, the network device and the terminal device can have the same understanding of the interlaces allocated for sending PUSCH, thereby reducing the complexity of the network device receiving PUSCH, and will not affect the network device's scheduling of other terminal devices, thereby ensuring the performance of the communication system.

[0237] In addition, the terminal device may also receive a RAR UL grant in certain non-contention random access (CFRA) processes, such as: a CFRA triggered by a physical downlink control channel order (PDCCH order), a CFRA for acquiring a TA of a STAG, or a CFRA for switching, etc. The RAR UL grant received in the CFRA may include information for indicating interlace and information for indicating an RB set, or include information for indicating interlace but not information for indicating an RB set.

[0238] Unlike CBRA, in the CFRA process, the network device can determine the currently activated ULBWP of the terminal device. In the CFRA process, the terminal device can determine the resources for sending uplink transmission (PUSCH) in the following manner:

[0239] Method 1: In order to reduce the complexity of the design and simplify the terminal device to reduce the product development cost, for the RAR UL grant in the CFRA process, the terminal device can use the same method as in Example 7, Example 8, Example 9 or Example 10 above to determine the resources for sending the PUSCH;

[0240] Method 2: In order to improve data transmission efficiency, for the RAR UL grant received in CFRA and CBRA, the terminal device can use different methods to determine the resources used to send PUSCH. For example: for the RAR UL grant received in CFRA and CBRA, the terminal device can determine the bits of the RAR UL grant used to indicate the frequency domain resources based on the active UL BWP and the initial UL BWP, respectively. More specifically, for example, in CFRA triggered by the PDCCH order, the terminal device determines the bits of the RAR UL grant used to indicate the frequency domain resources based on the active UL BWP; in CBRA, the terminal device determines the bits of the RAR UL grant used to indicate the frequency domain resources based on the initial UL BWP.

[0241] In at least one embodiment, the at least one resource block set is configured by high-level signaling; the high-level signaling configures the association relationship between the uplink resource block set and the downlink resource block set, or the high-level signaling configures the uplink resource block set scheduled by the indication information.

[0242] In some embodiments, the index of the resource block set is predefined. For example, if the index of the resource block set is predefined based on the carrier (or per carrier), then if the (UL / DL) carrier includes N1 (UL / DL) RB sets, for example, according to the frequency position from low to high, the indexes of the N1 RB sets are 0, 1, ..., N1-1 respectively. For example, if the index of the resource block set is predefined based on the BWP (or per BWP), then if the (UL / DL) BWP includes N2 (UL / DL) RB sets, for example, according to the frequency position from low to high, the indexes of the N2 RB sets are 0, 1, ..., N2-1 respectively. A resource block set.

[0243] In some embodiments, the index of the resource block set is indicated by high-layer signaling. The index indicated by high-layer signaling may also be based on a carrier indication or a BWP indication.

[0244] In some embodiments, on a carrier, a resource block set may have both a carrier-based index and a BWP-based index.

[0245] In some embodiments, there is an association relationship between the DL RB set and the UL RB set. The association relationship between the DL RB set and the UL RB set here means, for example, that when the terminal device receives indication information for scheduling uplink transmission on the DL RB set, if the indication information does not include an indication field for indicating the UL RB set, or the indication information includes an indication field for indicating the UL RB set but the terminal device ignores the indication field, the terminal device sends uplink transmission in the UL RB set associated with / corresponding to the DL RB set.

[0246] Generally, a DL RB set may be linked / associated / paired with / corresponds to one or more UL RB sets. A UL RB set may be associated / corresponds to one or more DL RB sets.

[0247] In some embodiments, the association relationship between the DL RB set and the UL RB set is predefined, for example, based on the frequency domain position of the resource block set or the index of the resource block set.

[0248] For example, if the frequency range of RBs included in a DL RB set is greater than the frequency range of RBs included in a UL RB set, the UL RB set is the UL RB set associated with the DL RB set. For example, the DL RB set and the associated UL RB set have the same index. That is, the DL RB set with index n (n is a natural number) is associated / corresponding to the UL RB set with index n (n is a natural number).

[0249] In some embodiments, the association relationship between the DL RB set and the UL RB set is indicated by a higher-level signaling, for example, according to an index of a resource block set.

[0250] In some embodiments, the association relationship between the DL RB set and the UL RB set is carrier-based or BWP-based. Carrier-based, for example, means that the association relationship between the DL RB set and the UL RB set is determined based on the RB sets included in the uplink carrier and the downlink carrier. BWP-based, for example, means that the association relationship between the DL RB set in the UL BWP and the RB set included in the DL BWP associated with the UL BWP is determined based on the UL BWP and the RB set included in the DL BWP associated with the UL BWP.

[0251] Fig. 9 It is an example diagram of the connection / correspondence / association relationship between the downlink RB set of the downlink carrier and the uplink RB set of the uplink carrier in an embodiment of the present application, wherein the RB set index is defined per carrier.

[0252] Fig.10 It is an example diagram of the connection / correspondence / association relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP in an embodiment of the present application, wherein the RB set index is defined per carrier or per BWP.

[0253] Fig.11 It is another example diagram of the connection / correspondence / association relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP according to the embodiment of the present application.

[0254] Fig.12It is another example diagram of the connection / correspondence / association relationship between the downlink RB set of the downlink BWP and the uplink RB set of the uplink BWP according to the embodiment of the present application.

[0255] Thus, the configuration of the network device may not be restricted, but may be processed by the terminal device. For example, if the terminal device receives DCI format 0_0 scheduling uplink transmission on a UL BWP including at least two RB sets, the uplink transmission is sent on the RB set predefined or configured (or indicated) by high-level signaling.

[0256] In some embodiments, a terminal device receives indication information for scheduling the terminal device to send an uplink transmission; the indication information includes an indication field for indicating a resource block set; and the terminal device sends the uplink transmission on at least one resource block set indicated by the indication field.

[0257] For example, the indication information is downlink control information having downlink control information format 0_0, or downlink control information having downlink control information format 0_2, or a random access response (RAR). In addition, the size of the indication field may be determined according to the number of RB sets in the active ULBWP.

[0258] Therefore, by adding the RB set indication field in the indication information, the terminal device can determine the resources used for uplink transmission, so that the uplink transmission can be correctly sent and received.

[0259] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0260] It can be seen from the above embodiments that it is possible to support a terminal device in determining resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0261] Embodiments of the third aspect

[0262] When the terminal device is instructed to perform BWP switching, the terminal device may be unable to determine the resources used for uplink transmission, thereby causing the uplink transmission to be unable to be correctly sent and received.

[0263] For example, in the current scheme, the size / number of bits of the FDRA indication field (including the size / number of bits Y of the indication field used to indicate the RB set) is determined according to the BWP where the uplink transmission is located. If the indication information (e.g., DCI format 0_1) used to schedule the terminal device to send uplink transmission includes an indication field for indicating the BWP, and the indication field instructs the terminal device to switch the uplink BWP (e.g., from the activated UL BWP, i.e., the first UL BWP, to the second UL BWP), if the above scheme is adopted, the terminal device will not be able to correctly send the uplink transmission. This is because, before receiving the indication information, the terminal device cannot determine which BWP the indication information will instruct the terminal device to send the uplink transmission, and therefore cannot determine the size / number of bits of the FDRA indication field of the indication information according to the above method, which results in the terminal device being unable to receive the indication information and unable to correctly send the uplink transmission.

[0264] For another example, if the indication information (e.g., DCI format 0_1) used to schedule the terminal device to send uplink transmission includes an indication field for indicating BWP, and the number of bits of the FRDA (Frequency domain resourceassignment) indication field included in the indication information is determined according to the SCS and / or RB set number of the active UL BWP, i.e., the first UL BWP, and the indication field used to indicate BWP instructs the terminal device to switch the uplink BWP (e.g., from the activated UL BWP, i.e., the first UL BWP to the second UL BWP), the SCS and / or the number of RB sets included in the first UL BWP and the second UL BWP may be different. Currently, there is no corresponding solution to support the terminal device in determining the frequency domain resources on the second UL BWP for sending uplink transmission, which will result in the incorrect determination of the resources used for uplink transmission, thereby causing the terminal device to be unable to correctly send uplink transmission.

[0265] To address at least one of the above problems, the present application provides an uplink transmission method, which is described from the terminal device side. The present application can be combined with the first and second embodiments, or can be implemented separately, and the same contents as the first and second embodiments are not repeated.

[0266] Fig.13 is a schematic diagram of an uplink transmission method according to an embodiment of the present application. Fig.13 As shown, the method includes:

[0267] 1301, a terminal device receives indication information for scheduling the terminal device to send uplink transmission;

[0268] 1302, determining the number of frequency domain resource allocation (FRDA) bits according to the subcarrier spacing (SCS) of the activated uplink portion of the bandwidth when the indication information is received and / or the number of resource block sets included; or, determining the number of FRDA bits according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, determining the number of frequency domain resource allocation (FRDA) bits according to the subcarrier spacing (SCS) and / or the number of resource block sets included in a specific uplink portion of the at least one configured uplink portion of the bandwidth.

[0269] It is worth noting that the above Fig.13 The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order of the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the above appended Fig.13 Records of.

[0270] In some embodiments, the indication information includes: downlink control information having a downlink control information format 0_1, downlink control information having a downlink control information format 0_2, downlink control information having a downlink control information format 0_0, or a random access response (RAR) in a random access procedure.

[0271] In some embodiments, the number of FRDA (Frequency domain resource assignment) bits is related to the number of SCSs and / or RB sets.

[0272] In some embodiments, the number of frequency domain resource allocation (FRDA) bits is determined according to the subcarrier spacing (SCS) of the activated uplink portion of the bandwidth when the indication information is received and / or the number of resource block sets included.

[0273] For example, if PUSCH is sent using interlace resource blocks (Interlaced resource blocks, that is, uplink frequency resource allocation Type 2) (for example, when useInterlacePUSCH-Dedicated-r16 is configured), then when the SCS of the activated uplink bandwidth is 30kHz, the number of FRDA bits is 5 bits, and when the SCS of the activated uplink bandwidth is 15kHz, the number of FRDA bits is 6 bits.

[0274] For example, if PUSCH is sent using interlaced resource blocks (i.e., uplink frequency resource allocation Type 2) (e.g., useInterlacePUSCH-Dedicated-r16 is configured), then when the SCS of the activated uplink bandwidth is 30kHz, the number of FRDA bits is 5+Y bits, and when the SCS of the activated uplink bandwidth is 15kHz, the number of FRDA bits is 6+Y bits. The value of Y is based on Determine, N is the number of RB sets included in the activated UL BWP.

[0275] In some embodiments, the number of FRDA bits is determined according to the subcarrier spacing of the carrier where the uplink transmission is located or the activated uplink portion of the bandwidth, and / or the number of resource block sets included in the carrier where the uplink transmission is located.

[0276] For example, if PUSCH is sent using interlaced resource blocks (i.e., uplink frequency resource allocation Type 2) (e.g., useInterlacePUSCH-Dedicated-r16 is configured), then when the SCS of the uplink carrier is 30kHz, the number of FRDA bits is 5+Y bits, and when the SCS of the uplink carrier is 15kHz, the number of FRDA bits is 6+Y bits. The value of Y is based on Determine, N is the number of RB sets included in the uplink carrier.

[0277] For another example, if PUSCH is sent using interlaced resource blocks (i.e., uplink frequency resource allocation Type 2) (e.g., useInterlacePUSCH-Dedicated-r16 is configured), then when the SCS of the activated uplink bandwidth is 30kHz, the number of FRDA bits is 5+Y bits, and when the SCS of the activated uplink bandwidth is 15kHz, the number of FRDA bits is 6+Y bits. The value of Y is based on Determine, N is the number of RB sets included in the uplink carrier.

[0278] In some embodiments, the number of frequency domain resource allocation (FRDA) bits is determined according to a subcarrier spacing (SCS) and / or the number of resource block sets included in a specific uplink partial bandwidth of the configured at least one uplink partial bandwidth.

[0279] For example, if PUSCH is sent using interlaced resource blocks (i.e., uplink frequency resource allocation Type 2) (e.g., useInterlacePUSCH-Dedicated-r16 is configured), then when the SCS of a specific uplink bandwidth in at least one configured uplink bandwidth is 30kHz, the number of FRDA bits is 5+Y bits, and when the SCS of a specific uplink bandwidth in at least one configured uplink bandwidth is 15kHz, the number of FRDA bits is 6+Y bits. The value of Y is based on Determine that N is the number of RB sets included in a specific uplink partial bandwidth in the at least one configured uplink partial bandwidth.

[0280] In some embodiments, the terminal device needs to determine a specific uplink partial bandwidth in the at least one configured uplink partial bandwidth. For example, in the at least one configured UL BWP, the number of bits of the FDRA indication field determined according to the number of SCS and / or RB sets of the specific UL BWP is the largest.

[0281] Therefore, the number of frequency domain resource allocation (FRDA) bits is determined according to the subcarrier spacing (SCS) of the activated uplink part bandwidth and / or the number of resource block sets included when receiving the indication information; or, the number of FRDA bits is determined according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink part bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, the number of frequency domain resource allocation (FRDA) bits is determined according to the subcarrier spacing (SCS) and / or the number of resource block sets included in a specific uplink part bandwidth in at least one configured uplink part bandwidth, which can support the terminal device to determine the size / number of bits of the FDRA indication field including the indication information for indicating the BWP indication field, even if the indication field for indicating the BWP in the indication information indicates that the terminal device switches the uplink BWP (for example, from the activated UL BWP, i.e., the first UL BWP to the second UL BWP), the terminal device can receive the indication information, thereby enabling the uplink transmission to be correctly sent and received.

[0282] In some embodiments, if PUSCH is sent using interlace resource blocks (Interlaced resource blocks, i.e., uplink frequency resource allocation Type 2) (for example, when useInterlace PUSCH-Dedicated-r16 is configured), the indication information does not include an indication field for indicating a partial bandwidth (BWP); or, the indication information includes an indication field for indicating a partial bandwidth (BWP) and the terminal device ignores the indication field for indicating a partial bandwidth (BWP) included in the indication information.

[0283] For example, if the high-layer parameter useInterlacePUSCH-Dedicated-r16 is configured, DCI format 0_1 ​​does not include the Bandwidth part indicator; or, even if the terminal device receives the DCI format 0_1 ​​and the DCI format 0_1 ​​includes the Bandwidth part indicator, the terminal device ignores the Bandwidth part indicator.

[0284] Therefore, if PUSCH is sent using interlace resource blocks (Interlaced resource blocks, ie, uplink frequency resource allocation Type 2) (for example, when useInterlacePUSCH-Dedicated-r16 is configured), the indication information cannot instruct the terminal device to switch UL BWP, thereby avoiding the above-mentioned problem.

[0285] In some embodiments, the indication information includes an indication field for indicating a BWP, and the indication field indicates a second UL BWP that is different from the activated UL BWP, ie, the first UL BWP.

[0286] In some embodiments, when the terminal device is configured to send the uplink transmission using interlace frequency domain resources, the terminal device expects or determines that the subcarrier spacing (SCS) of the first uplink portion of the bandwidth is the same as the SCS of the second uplink portion of the bandwidth.

[0287] For example, if the higher layer parameter useInterlacePUSCH-Dedicated-r16 is configured and DCI format 0_1 ​​instructs the terminal device to switch UL BWP, the SCS of the second UL BWP should be the same as that of the first UL BWP.

[0288] For another example, if the higher layer parameter useInterlacePUSCH-Dedicated-r16 is configured, the SCSs of all UL BWPs in the configured at least one UL BWP should be the same, or only one SCS is configured for the uplink carrier.

[0289] In some embodiments, the terminal device further expects or determines that the number of resource block sets on the first uplink portion of the bandwidth is the same as the number of resource block sets on the second uplink portion of the bandwidth.

[0290] For example, if the high-level parameter useInterlacePUSCH-Dedicated-r16 is configured and DCI format 0_1 ​​instructs the terminal device to switch UL BWP, the SCS of the second UL BWP should be the same as that of the first UL BWP, and their number is also the same when RB sets are configured.

[0291] For another example, if the high-level parameter useInterlacePUSCH-Dedicated-r16 is configured, the SCS and the number of RB sets included in all UL BWPs in at least one configured UL BWP should be the same, or, the uplink carrier is configured with only one SCS and the number of RB sets included in all UL BWPs in at least one configured UL BWP should be the same.

[0292] Thereby, the configuration of the network device can be restricted, thereby supporting the terminal device to determine the resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0293] In some embodiments, the terminal device ignores the indication field used to indicate the resource block set in the indication information.

[0294] For example, for SCS, if DCI format 0_1 ​​indicates that the terminal device switches UL BWP, the SCS of the second UL BWP should be the same as that of the first UL BWP. In addition, for RB set, the terminal device can ignore the indication field in DCI for indicating the resource block set (i.e., the Y bit information when FDRA includes 5 / 6+Y bits), and determine the RB set using the method described in the embodiment of the second aspect, for example.

[0295] For example, the uplink resource block set associated with the downlink resource block set where the frequency domain resources for sending indication information are located in the RB set of the second UL BWP may be used; or the uplink resource block set corresponding to the frequency domain resources for sending indication information in the RB set of the second UL BWP may be used; and so on.

[0296] The above describes the case where the configuration of the network device is restricted and the terminal device ignores the indication field. In addition, the indication field in the DCI can also be reinterpreted.

[0297] In some embodiments, the terminal device determines the frequency domain resources for sending the uplink transmission on the second uplink bandwidth based on the subcarrier spacing and / or the number of resource block sets included in the first uplink bandwidth and the second uplink bandwidth.

[0298] In some embodiments, the terminal device determines an actual number of FRDA bits of the first uplink portion of the bandwidth and an assumed number of FRDA bits of the second uplink portion of the bandwidth; and determines frequency domain resources on the second uplink portion of the bandwidth for sending the uplink transmission based on the actual number of FRDA bits and the assumed number of FRDA bits.

[0299] In some embodiments, the terminal device uses at least one bit in the FRDA indication field of the indication information for indicating a resource block set to indicate an interleaved frequency resource, and uses at least one bit in the FRDA indication field of the indication information for indicating an interleaved frequency resource to indicate a resource block set.

[0300] In some embodiments, the terminal device ignores at least one bit in the FRDA indication field of the indication information.

[0301] For example, the min(X1+Y1, X2+Y2) bit in the FRDA indication field of the indication information is used to indicate the frequency domain resources on the second uplink part bandwidth; wherein min() represents an operation of taking a smaller value, X1 and Y1 are the actual number of FRDA bits of the first uplink part bandwidth, and X2 and Y2 are the assumed number of FRDA bits of the second uplink part bandwidth.

[0302] Among them, the least significant bit (LSB) of min(X1+Y1,X2) is used to indicate the interleaved frequency domain resources, and the most significant bit (MSB) of min(X1+Y1-min(X1+Y1,X2),Y2) is used to indicate the resource block set.

[0303] If X1 + Y1 < X2, the LSB of min(X1 + Y1, X2) can indicate an interleaved frequency-domain resource that is one of the predefined first 2^min(X1 + Y1, X2) interleaved frequency-domain resources corresponding to the second uplink partial bandwidth;

[0304] If X1 + Y1 - min(X1 + Y1, X2) < Y2, the MSB of min(X1 + Y1 - min(X1 + Y1, X2), Y2) can indicate a resource block set that is one of the predefined first 2^min(X1 + Y1 - min(X1 + Y1, X2), Y2) resource block sets corresponding to the second uplink partial bandwidth.

[0305] For another example, min(X1, X2) + min(Y1, Y2) bits in the FRDA indication field of the indication information are used to indicate the frequency-domain resources on the second uplink partial bandwidth; where min() represents the operation of taking the smaller value, X1 and Y1 are the actual FRDA bits of the first uplink partial bandwidth, and X2 and Y2 are the assumed FRDA bits of the second uplink partial bandwidth.

[0306] Among them, min(X1, X2) bits in X1 are used to indicate the interleaved frequency-domain resources, and min(Y1, Y2) bits in Y1 are used to indicate the resource block sets.

[0307] If X1 < X2, the interleaved frequency-domain resource that min(X1, X2) can indicate is one of the predefined first min(X1, X2) interleaved frequency-domain resources corresponding to the second uplink partial bandwidth;

[0308] If Y1 < Y2, the resource block set that min(Y1, Y2) can indicate is one of the predefined first 2^min(Y1, Y2) bits, Y2) resource block sets corresponding to the second uplink partial bandwidth.

[0309] In some embodiments, if Y1 = 0, the method described in the embodiments of the second aspect can be used to determine the RBset. For example, the uplink resource block set associated with the downlink resource block set where the frequency-domain resource for sending the indication information is located in the RB set of the second UL BWP can be used; or, the uplink resource block set corresponding to the frequency-domain resource for sending the indication information in the RB set of the second UL BWP can be used; and so on.

[0310] Each of the above embodiments only exemplarily illustrates the embodiments of the present application, but the present application is not limited thereto, and appropriate variations can also be made on the basis of each of the above embodiments. For example, each of the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0311] It can be seen from the above embodiments that it is possible to support a terminal device in determining resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0312] Embodiments of the fourth aspect

[0313] The terminal device may be instructed that the uplink carrier or the downlink carrier has no guard band (intra-cell guardband), but there is currently no corresponding solution for instructing the terminal device that the uplink carrier or the downlink carrier has no guard band.

[0314] On the other hand, if only the uplink carrier or downlink carrier of the terminal device is indicated without a guard band, but the RB set included in the uplink carrier or downlink carrier is not indicated, when the terminal device is indicated that the frequency resource has no guard band, the terminal device may not be able to determine the resources used for uplink transmission, thereby causing the uplink transmission to not be correctly sent and received.

[0315] For example, if PUSCH is sent using interlace resource blocks (i.e., uplink frequency resource allocation Type 2) (e.g., useInterlacePUSCH-Dedicated-r16 is configured), but high-level signaling intraCellGuardBandUL-r16 indicates that there is no guard band, the current solution does not provide how to indicate frequency domain resources.

[0316] At least for the above problems, the embodiment of the present application provides an uplink transmission method, which is described from the terminal device side. The embodiment of the present application can be combined with the embodiments of the first to third aspects, or can be implemented separately, and the same contents as the embodiments of the first to third aspects are not repeated.

[0317] Fig.14 is a schematic diagram of an uplink transmission method according to an embodiment of the present application. Fig.14 As shown, the method includes:

[0318] 1401, a terminal device receives first configuration information for indicating a guard band and / or a resource block set (RBset) of an uplink carrier; and

[0319] 1402. The terminal device determines the resource blocks included in the resource block set on the uplink carrier according to the frequency domain position (eg, CRB index) of the starting resource block and / or the frequency domain position of the ending resource block of the guard band.

[0320] It is worth noting that the above Fig.14 The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order of the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the above appended Fig.14 Records of.

[0321] In some embodiments, the first configuration information further indicates that there is no guard band. For example, the first configuration information includes intraCellGuardBandUL-r16, or intraCellGuardBandDL-r16.

[0322] In some embodiments, the first configuration information (e.g., intraCellGuardBandUL-r16, intraCell GuardBandDL-r16) includes information for indicating the frequency domain position of the starting resource block of the guard band (e.g., represented by a CRB index) and / or the frequency domain position of the ending resource block. If the frequency domain position of the starting resource block of the guard band indicated by the first configuration information is higher than or equal to the frequency domain position of the ending resource block of the guard band, the uplink carrier or the downlink carrier has no guard band.

[0323] For example, assuming that 2N CRB indices are indicated in intraCellGuardBandUL-r16 or intraCellGuardBandDL-r16, that is, {index 1, index2, ...index 2N}, the 2n-1th and 2nth CRB indexes are the starting CRB index and the ending CRB index of the nth (n = 1, 2, ..., N)th guard band, respectively. If the 2n-1th CRB index is greater than or equal to the 2nth CRB index (for example, the 2n-1th CRB index is equal to the 2nth CRB index plus 1), there is no guard band n, that is, there is no guard band between the two RB sets (the nth RB set and the n+1th RB set) corresponding to the 2n-1th and 2nth CRB indexes.

[0324] Further, if for n=1, 2, ..., N, the 2n-1th CRB index is respectively greater than or equal to the 2nth CRB index (for example, the 2n-1th CRB index is equal to the 2nth CRB index plus 1), then the uplink carrier or downlink carrier has no guard band.

[0325] When the index of the start common resource block (CRB) of the guard band is equal to the end CRB index plus 1, the terminal device determines the resource blocks included in the resource block set on the downlink carrier or the uplink carrier, for example, according to the following method:

[0326] Assumptions and Respectively represent an intra-cell guardband start CRB index and an end CRB index indicated by the first configuration information, wherein, Indicates the index of the guard band, which is numbered in ascending order according to the CRB index; for downlink, x is DL, and for uplink, x is UL. The index in the RB set is The starting CRB index of the RB set (numbered in ascending order according to the CRB index) is

[0327]

[0328] End CRB index is

[0329]

[0330] Therefore, even if the first configuration information indicates that there is no intra-cell guard band, the terminal device can determine the resource blocks included in the resource block set on the downlink carrier or uplink carrier according to the frequency domain position of the starting resource block (for example, CRB index) and / or the frequency domain position of the ending resource block of the guard band indicated by the first configuration information, thereby supporting the terminal device to determine the resources used for downlink transmission or uplink transmission, thereby enabling the downlink transmission or uplink transmission to be correctly sent and received.

[0331] In some embodiments, the first configuration information indicates that there is no guard band through a specific value. The specific value is, for example, Null, but the present application is not limited thereto.

[0332] In some embodiments, when the first configuration information indicates that there is no guard band, the resource blocks included in the resource subset of the uplink carrier are predefined.

[0333] Therefore, through the predefined RB set, it is possible to support the terminal device to determine the resources used for uplink transmission, so that the uplink transmission can be correctly sent and received.

[0334] In some embodiments, the terminal device receives second configuration information indicating a resource block set of the uplink carrier.

[0335] Therefore, the terminal device configures the RB set according to other high-level signaling, which can support the terminal device to determine the resources used for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0336] In some embodiments, the terminal device receives third configuration information of the UL BWP of the uplink carrier; if the first configuration information indicates that there is no guard band, the third configuration information does not include information instructing the terminal device to use staggered frequency domain resources to send uplink transmission; or, if the third configuration information includes information instructing the terminal device to use staggered frequency domain resources to send uplink transmission, the first configuration information does not indicate that there is no guard band.

[0337] For example, if the terminal device is configured with the higher-layer parameter useInterlacePUSCH-Dedicated-r16, intraCellGuardBandUL-r16 cannot be used to indicate that there is no guard band; if intraCellGuardBandUL-r16 is used to indicate that there is no guard band, the higher-layer parameter useInterlacePUSCH-Dedicated-r16 is not configured.

[0338] In some embodiments, when a terminal device is indicated that there is no frequency guard band, the terminal device receives indication information for scheduling the terminal device to send an uplink transmission; wherein the indication information does not include an indication field for indicating a resource block set. Alternatively, the indication information includes an indication field for indicating a resource block set but the terminal device ignores the indication field. The method of the embodiment of the second aspect may be used to determine the resources for sending an uplink transmission.

[0339] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0340] It can be seen from the above embodiments that it is possible to support a terminal device to determine resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0341] Embodiments of the fifth aspect

[0342] An embodiment of the present application provides an uplink transmission method.

[0343] Fig.15 is a schematic diagram of an uplink transmission method of an embodiment of the fifth aspect, such as Fig.15 As shown, the method includes:

[0344] 1501. The terminal device receives indication information indicating resources used by the terminal device for sending uplink transmission; and

[0345] 1502. When the downlink carrier is configured to have no guard band, the terminal device regards a predetermined number of resource blocks in a downlink partial bandwidth (DL BWP) as a predefined or preconfigured resource block set, and sends the uplink transmission on the predefined or preconfigured resource block set.

[0346] In at least one embodiment, the predetermined number of resource blocks in a downlink bandwidth portion (DL BWP) may be, for example, all resource blocks in a downlink bandwidth portion (DL BWP).

[0347] In at least one embodiment, the terminal device may operate 1502 according to a predefined operation or configuration of the network device.

[0348] According to an embodiment of the fifth aspect, an RB set is defined for a case where a DL carrier is not configured with an intra-cell guard band.

[0349] For example, if the DL carrier is not configured with an intra-cell guard band, the RBs in a DL BWP belong to one RB set.

[0350] In this way, when the DL carrier is not configured with an intra-cell guard band, the terminal device can also determine the RB set for sending the PUSCH in the UL BWP according to the RB set of the DL BWP.

[0351] Embodiments of the sixth aspect

[0352] When the UL carrier is configured with an intra-cell guard band, whether the terminal device can send uplink transmissions in the intra-cell guard band depends on the capabilities of the terminal device.

[0353] According to the current resource allocation method, part of the PUSCH data may be mapped on the intra-cell guardband. If the terminal device is limited by its capabilities and cannot send on the intra-cell guard band as mentioned above, the terminal device will not be able to send this part of the data, which will reduce the reliability and efficiency of data transmission.

[0354] An embodiment of the present application provides an uplink transmission method.

[0355] Fig.16Ais a schematic diagram of a method of an uplink transmission method of an embodiment of the sixth aspect, such as Fig.16A As shown, the method includes:

[0356] 1601. A terminal device receives indication information for scheduling uplink transmission, where the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RB sets); and

[0357] 1602. The terminal device determines a resource block for sending the uplink transmission according to the indication information, and sends the uplink transmission on the determined resource block.

[0358] In operation 1601, the indication information can indicate the resources used by the terminal device to send uplink transmission (e.g., PUSCH). The PUSCH can be semi-statically / semi-persistently / dynamically scheduled; the indication information can be DCI 0_0 (inUSS), DCI 0_1 or DCI 0_2, or RRC signaling for configuring Type 1 or Type 2 CG PUSCH. At least two resource block sets (RB sets) indicated by the indication information are continuous.

[0359] In operation 1602, a resource block for sending the uplink transmission is determined according to whether the terminal device has a predetermined capability or indicates that the terminal device has a predetermined capability and the indication information. The predetermined capability includes: the terminal device can send uplink transmission in an intra-cell guard band.

[0360] For example, when the terminal device indicates that it is capable of sending uplink transmission in an intra-cell guard band, the terminal device determines that the resource blocks used to send the uplink transmission are: the intersection of the at least two resource block sets and the resource blocks in the intra-cell guard band between the at least two resource block sets and the interlace resource blocks indicated by the indication information.

[0361] Fig. 16B FIG. 1 is a schematic diagram of a terminal device determining a resource block for sending an uplink transmission when the terminal device indicates that it can send an uplink transmission in an intra-cell guard band. Fig. 16BAs shown, since the terminal device indicates that it is capable of sending uplink transmission in the intra-cell guard band, the resource blocks used to send PUSCH may include resource blocks in the intra-cell guard band. For another example, when the terminal device is capable of sending uplink transmission in the intra-cell guard band and indicates that it is capable of sending uplink transmission in the intra-cell guard band, the terminal device determines that the resource blocks used to send the uplink transmission are: the intersection of the at least two resource block sets and the resource blocks in the intra-cell guard band between the at least two resource block sets and the interlace resource blocks indicated by the indication information.

[0362] For another example, when the terminal device does not indicate that it is capable of sending uplink transmission in an intra-cell guard band, the terminal device determines that the resource block used to send the uplink transmission is: the intersection of the interlace resource block indicated by the indication information and the resource blocks in the at least two resource block sets.

[0363] Fig. 16C FIG. 1 is a schematic diagram of a terminal device determining a resource block for sending an uplink transmission when the terminal device does not indicate that it can send an uplink transmission in an intra-cell guard band. Fig. 16C As shown, since the terminal device has not indicated that it can send uplink transmission in the intra-cell guard band, the resource blocks used to send PUSCH do not include resource blocks in the intra-cell guard band.

[0364] The situation in which the terminal device does not indicate that it is capable of sending uplink transmission in the intra-cell guard band means: the terminal device is capable of sending uplink transmission in the intra-cell guard band, but does not indicate that it is capable of sending uplink transmission in the intra-cell guard band; or, the terminal device is unable to send uplink transmission in the intra-cell guard band and does not indicate that it is capable of sending uplink transmission in the intra-cell guard band.

[0365] Specifically, taking the case where PUSCH is dynamically scheduled and the indication information is DCI (for example, DCI 0_0 (in USS) or DCI0_1) as an example, the method for determining the resource block used to send the uplink transmission in operation 1602 may be, for example, as shown in the following example 1 or example 2:

[0366] Example 1: For DCI 0_0monitored in a UE-specific search space and DCI 0_1, if the UE indicates the capability of transmitting in intra-cell guard band, theUE shall determine the resource allocation in frequency domain as anintersection of the resource blocks of the indicated interlaces, and resourceblocks of the indicated set of RB sets and intra-cell guard bands defined inClause 7 between the indicated RB sets, if any. Otherwise, the UE shall determine the resource allocation in frequency domain as an intersection of the resourceblocks of the indicated interlaces and the resource blocks the indicated set of RB sets.

[0367] Example 2: For DCI 0_0monitored in a UE-specific search space and DCI 0_1, if the UE indicates the capability of transmitting in intra-cell guard band, theUE shall determine the resource allocation in frequency domain as anintersection of the resource blocks of the active UL BWP, the resource blocks of the indicated interlaces, and the resource blocks of the indicated set ofRB sets and intra-cell guard bands defined in Clause 7 between the indicatedRB sets, if any. Otherwise, the UE shall determine the resource allocation infrequency domain as an intersection ofthe resource blocks of the active ULBWP, theresource blocks of the indicated interlaces,and the resource blocks of the indicated set of RB sets.

[0368] In addition, in another method of the uplink transmission method of the embodiment of the sixth aspect of the present application: if the terminal device is not capable of sending uplink transmission in the intra-cell guard band, the terminal device does not expect the indication information to indicate the above-mentioned two or more RB sets; or, if the terminal device does not indicate that the terminal device is capable of sending uplink transmission in the intra-cell guard band, the terminal device does not expect the indication information to indicate the above-mentioned two or more RB sets.

[0369] The fact that the terminal device does not expect the indication information to indicate the two or more RB sets means that the terminal device does not process the indication information.

[0370] According to the embodiment of the sixth aspect, the resources used to send uplink transmission can be determined based on the capabilities of the terminal device, thereby improving the reliability and efficiency of data transmission.

[0371] Embodiment of the seventh aspect

[0372] The embodiment of the seventh aspect of the present application provides an uplink transmission reception method, which is applied to a network device and corresponds to the embodiment of the sixth aspect.

[0373] Fig.17 is a schematic diagram of a method of an uplink transmission reception method of an embodiment of the seventh aspect, such as Fig.17 As shown, the method includes:

[0374] 1701. A network device sends indication information for scheduling uplink transmission, where the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RB sets); and

[0375] 1702. The network device receives the uplink transmission according to whether the terminal device has indicated that the terminal device can send uplink transmission in an intra-cell guard band.

[0376] In operation 1701, the indication information can indicate the resources used by the terminal device to send uplink transmission (e.g., PUSCH). The PUSCH can be semi-statically / semi-persistently / dynamically scheduled; the indication information can be DCI 0_0 (inUSS), DCI 0_1 or DCI 0_2, or RRC signaling for configuring Type 1 or Type 2 CG PUSCH. At least two resource block sets (RB sets) indicated by the indication information are continuous.

[0377] In operation 1702, the network device receives the uplink transmission, wherein the network device may receive the uplink transmission according to whether the terminal device has a predetermined capability or whether it indicates that the terminal device has a predetermined capability. The predetermined capability includes: the terminal device can send an uplink transmission in an intra-cell guard band.

[0378] For example, when the terminal device indicates that it is capable of sending uplink transmission in an intra-cell guard band, the network device receives the uplink transmission on the following resources: the intersection of the at least two resource block sets and the resource blocks in the intra-cell guard band between the at least two resource block sets and the interlace resource blocks indicated by the indication information.

[0379] For another example, when the terminal device is capable of sending uplink transmission in an intra-cell guard band and indicates that it is capable of sending uplink transmission in an intra-cell guard band, the network device receives the uplink transmission on the following resources: an intersection of the at least two resource block sets and the resource blocks in the intra-cell guard band between the at least two resource block sets and the interlace resource blocks indicated by the indication information.

[0380] For another example, when the terminal device does not indicate that it can send uplink transmission in an intra-cell guard band, the network device receives the uplink transmission in the following resources: the intersection of the interlace resource block indicated by the indication information and the resource blocks in the at least two resource block sets.

[0381] The situation in which the terminal device does not indicate that it is capable of sending uplink transmission in the intra-cell guard band means: the terminal device is capable of sending uplink transmission in the intra-cell guard band, but does not indicate that it is capable of sending uplink transmission in the intra-cell guard band; or, the terminal device is unable to send uplink transmission in the intra-cell guard band and does not indicate that it is capable of sending uplink transmission in the intra-cell guard band.

[0382] In addition, in operation 1702, the network device may determine the resources for receiving the uplink transmission according to whether the terminal device has the above-mentioned predetermined capability or whether it indicates that the terminal device has the predetermined capability, and receive the uplink transmission on the determined resources. However, the operation of determining the resources is not necessary, and there may be no operation of determining the resources in operation 1702.

[0383] According to the embodiment of the seventh aspect, resources for receiving uplink transmission can be determined based on the capabilities of the terminal device, thereby improving the reliability and efficiency of data transmission.

[0384] Embodiments of the eighth aspect

[0385] In some cases, a UL BWP may include only some RBs (not including all RBs) of an RB set.

[0386] Fig.18A FIG. 1 is a schematic diagram of a UL BWP including part of RBs in an RB set. Fig.18A As shown, an avtive UL BWP includes multiple complete RB sets, and the UL BWP includes a partial RB of an RB set.

[0387] Fig.18B FIG. 1 is another schematic diagram of a UL BWP including a portion of RBs in an RB set. Fig.18B As shown in FIG. 1 , an avtive UL BWP includes part of the RBs in an RB set, and the UL BWP also includes part of the RBs in an RB set. Fig.18B In this case, the UL carrier is not configured with intra-cell guard band.

[0388] Fig.18C FIG. 1 is another schematic diagram of a UL BWP including a portion of RBs in an RB set. Fig.18CAs shown in FIG. 1 , an avtive UL BWP includes part of the RBs in an RB set, and the UL BWP also includes part of the RBs in an RB set. Fig.18C In the UL carrier, the UL carrier is configured with an intra-cell guard band.

[0389] according to Fig.18A , 18B , 18C, for the same per-carrier RB set, the RBs in the per-carrier RB set actually included in different UL BWPs may be different.

[0390] In this case, considering CBRA, if the terminal device UE receives a random access response (RAR) or downlink control information with downlink control information format 0_0 encrypted with TC-RNTI, and determines the resources for sending PUSCH based on the RBset included in the active UL BWP (from the perspective of per BWP, the RBs in this RB set are less than or equal to the RBs in the corresponding per carrier RB set), the network device may not be able to uniquely determine the resources for receiving the PUSCH.

[0391] Fig.18D It is a schematic diagram of a terminal device determining resources for sending PUSCH based on the RB set included in the active UL BWP after receiving downlink control information. Fig.18D It is a schematic diagram of a terminal device determining resources for sending a PUSCH based on the RB set included in the activeUL BWP after receiving a random access response.

[0392] like Fig.18D and Fig.18E As shown, the resources determined by UE1 and UE2 for sending PUSCH are different. In CBRA, the network device does not know which UE sends PUSCH, and therefore cannot uniquely determine which part of the resources to receive PUSCH.

[0393] also, Fig.18D and Fig.18E This is the case where the UL carrier is not configured with an intra-cell guard band. The case where the UL carrier is configured with an intra-cell guard band is similar.

[0394] An embodiment of the present application provides an uplink transmission method.

[0395] 1) In some embodiments, when the active UL BWP includes partial RBs of a per carrier RB set, the UE determines the resource blocks used to send the uplink transmission as: the intersection of the resource blocks mapped by the PRACH used by the UE to send the preamble before receiving the indication information and the interlace resource blocks indicated by the indication information.

[0396] Fig.18F FIG. 1 is a schematic diagram of an uplink transmission method according to an embodiment of the present application. Fig.18F As shown, by using the above method 1), the resources determined by UE1 and UE2 are the same. Even if the network device does not know which UE sends the PUSCH, it can uniquely determine which part of the resources to receive the PUSCH, thereby successfully receiving the PUSCH and appropriately scheduling other UEs.

[0397] 2) In some embodiments, when the active UL BWP includes partial RBs of a per carrier RB set, if the active UL BWP completely overlaps with the initial UL BWP, the UE determines the resource blocks used to send the uplink transmission as: the intersection of the resource blocks in the initial UL BWP and the interlace resource blocks indicated by the indication information.

[0398] 3) In some embodiments, when the active UL BWP includes partial RBs of a per carrier RB set, if the active UL BWP does not completely overlap with the initial UL BWP, the UE determines the resource blocks used to send the uplink transmission as: the intersection of the resource blocks mapped by the PRACH used by the UE to send the preamble before receiving the indication information and the interlace resource blocks indicated by the indication information.

[0399] Figure 18G FIG. 1 is another schematic diagram of the uplink transmission method according to an embodiment of the present application. Figure 18G As shown, by adopting the above method 3), the resources determined by UE1 and UE2 are the same. Even if the base station does not know which UE sends the PUSCH, it can uniquely determine which part of the resources to receive the PUSCH, thereby successfully receiving the PUSCH and appropriately scheduling other UEs.

[0400] The above indication information is a random access response (RAR), or downlink control information with downlink control information format 0_0 scrambled by using TC-RNTI.

[0401] Embodiment of the ninth aspect

[0402] The embodiment of the present application provides an uplink transmission device. The device may be, for example, a terminal device, or may be one or more components or assemblies configured in the terminal device. The contents of the embodiment of the present application that are the same as the embodiments of the first to sixth aspects and the eighth aspect are not repeated here.

[0403] Fig.19 is a schematic diagram of an uplink transmission device according to an embodiment of the present application. Fig.19 As shown, the uplink transmission device 1900 includes:

[0404] A receiving unit 1901 receives configuration information of an uplink bandwidth, wherein the configuration information of the uplink bandwidth indicates that the uplink bandwidth includes at least two resource block sets; and

[0405] The processing unit 1902 does not monitor or receive the first indication information for scheduling uplink transmission and does not include an indication field for indicating a resource block set on the downlink partial bandwidth corresponding to the uplink partial bandwidth.

[0406] In some embodiments, the uplink portion of the bandwidth has the same identifier as the corresponding downlink portion of the bandwidth; the first indication information includes: downlink control information having a downlink control information format 0_0, or downlink control information having a downlink control information format 0_2, or a random access response in a random access process.

[0407] In some embodiments, the terminal device does not expect to be configured or determines not to be configured to monitor or receive the first indication information on the downlink portion of the bandwidth corresponding to the uplink portion of the bandwidth.

[0408] In some embodiments, the processing unit 1902 is further configured to:

[0409] On the downlink partial bandwidth corresponding to the uplink partial bandwidth, second indication information for scheduling downlink transmission is not monitored or received; the second indication information includes: downlink control information having downlink control information format 1_0.

[0410] In some embodiments, the processing unit 1902 is further used to: not send a physical random access channel for contention-based random access on the uplink portion of the bandwidth; or, not send a physical random access channel other than one used for beam failure recovery on the uplink portion of the bandwidth; or, not send a physical random access channel on the uplink portion of the bandwidth.

[0411] In some embodiments, the uplink portion of the bandwidth configuration information does not include information for indicating a physical random access channel configuration for contention-based random access; or, the uplink portion of the bandwidth configuration information does not include information for indicating a physical random access channel configuration other than for beam failure recovery; or, the uplink portion of the bandwidth configuration information does not include information for indicating a physical random access channel configuration.

[0412] In some embodiments, the receiving unit 1901 is also used to: receive configuration information of the downlink portion of the bandwidth, the configuration information of the downlink portion of the bandwidth does not include configuration information instructing the terminal device to listen to or receive the first indication information, and / or does not include configuration information instructing the terminal device to listen to or receive the second indication information.

[0413] In some embodiments, Fig.19 As shown, the uplink transmission apparatus 1900 further includes a sending unit 1903. The receiving unit 1901 is further configured to: receive indication information that does not include an indication field for indicating a resource block set, wherein the indication information schedules an uplink transmission on an uplink partial bandwidth including at least two resource block sets; and the sending unit 1903 sends the uplink transmission on at least one predefined or preconfigured resource block set.

[0414] In some embodiments, the indication information includes: downlink control information having downlink control information format 0_0; wherein the downlink control information is scrambled using C-RNTI or CS-RNTI or MCS-C-RNTI or TC-RNTI; or, the indication information includes: a random access response in a random access process.

[0415] In some embodiments, the at least one resource block set is predefined, and the predefined resource block set includes at least one of the following:

[0416] An uplink resource block set in the at least two resource block sets that is associated with a downlink resource block set where the frequency domain resource for sending the indication information is located;

[0417] An uplink resource block set corresponding to the frequency domain resource for sending the indication information in the at least two resource block sets;

[0418] A resource block set having a smallest resource block set index value among the at least two resource block sets;

[0419] The resource block set with the lowest frequency domain position among the at least two resource block sets;

[0420] The resource block set with the highest frequency domain position in the at least two resource block sets;

[0421] A resource block set overlapping with the initial uplink portion bandwidth in the at least two resource block sets;

[0422] A resource block set in the at least two resource block sets that overlaps with part or all of the resource block sets included in the initial uplink portion of the bandwidth;

[0423] Some or all of the resource block sets in the at least two resource block sets;

[0424] The at least two resource block sets are resource block sets used to send the random access preamble sequence corresponding to the uplink transmission.

[0425] In some embodiments, the at least one resource block set is configured by high-level signaling; the high-level signaling configures the association relationship between the uplink resource block set and the downlink resource block set, or the high-level signaling configures the uplink resource block set scheduled by the indication information.

[0426] In some embodiments, the receiving unit 1901 receives indication information for scheduling the terminal device to send uplink transmission; the processing unit 1902 determines the number of frequency domain resource allocation bits according to the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included when the indication information is received; or, determines the number of frequency domain resource allocation bits according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, determines the number of frequency domain resource allocation (FRDA) bits according to the subcarrier spacing (SCS) and / or the number of resource block sets included in a specific uplink portion of the bandwidth configured at least one uplink portion.

[0427] In some embodiments, when the terminal device is configured to send the uplink transmission using staggered frequency domain resources, the indication information does not include an indication field for indicating a partial bandwidth; or, the indication information includes an indication field for indicating a partial bandwidth and the terminal device ignores the indication field for indicating the partial bandwidth included in the indication information.

[0428] In some embodiments, the indication information includes an indication field for indicating a partial bandwidth, and the indication field indicates a second uplink partial bandwidth that is different from the activated uplink partial bandwidth, ie, the first uplink partial bandwidth.

[0429] In some embodiments, when the terminal device is configured to send the uplink transmission using staggered frequency domain resources, the terminal device expects or determines that the subcarrier spacing of the first uplink portion of the bandwidth is the same as the subcarrier spacing of the second uplink portion of the bandwidth.

[0430] In some embodiments, the terminal device further expects or determines that the number of resource block sets on the first uplink portion of the bandwidth is the same as the number of resource block sets on the second uplink portion of the bandwidth.

[0431] In some embodiments, the terminal device ignores the indication field used to indicate the resource block set in the indication information.

[0432] In some embodiments, the processing unit 1902 is further used to determine the frequency domain resources for sending the uplink transmission on the second uplink bandwidth based on the subcarrier spacing and / or the number of resource block sets included in the first uplink bandwidth and the second uplink bandwidth.

[0433] In some embodiments, the receiving unit 1901 receives first configuration information for indicating a guard band and / or a resource block set of an uplink carrier; and the processing unit 1902 determines the resource blocks included in the resource block set on the uplink carrier based on the frequency domain position of the starting resource block and / or the frequency domain position of the ending resource block of the guard band.

[0434] In some embodiments, the processing unit 1902 is further configured to: when the first configuration information indicates that there is no guard band, determine that the resource blocks included in the resource block set of the uplink carrier are predefined.

[0435] In some embodiments, the first configuration information includes information for indicating the frequency domain position of the starting resource block and / or the frequency domain position of the ending resource block of the guard band; wherein the frequency domain position of the starting resource block of the guard band indicated by the information is higher than or equal to the frequency domain position of the ending resource block of the guard band.

[0436] In some embodiments, the starting common resource block index is equal to the ending common resource block index plus one.

[0437] In some embodiments, the receiving unit 1901 is further used to: receive second configuration information indicating a resource block set of the uplink carrier;

[0438] In some embodiments, the receiving unit 1901 is also used to: receive third configuration information of the UL BWP of the uplink carrier; if the first configuration information indicates that there is no guard band, the third configuration information does not include information instructing the terminal device to use staggered frequency domain resources to send uplink transmission; or, if the third configuration information includes information instructing the terminal device to use staggered frequency domain resources to send uplink transmission, the first configuration information does not indicate that there is no guard band.

[0439] In some embodiments, the receiving unit 501 receives indication information indicating resources used by a terminal device for sending uplink transmission; the sending unit 1902, when the downlink carrier is configured to have no guard band, treats a predetermined number of resource blocks in a downlink partial bandwidth (DL BWP) as a predefined or preconfigured resource block set, and sends the uplink transmission on the predefined or preconfigured resource block set.

[0440] In some embodiments, the receiving unit 1901 receives indication information for scheduling uplink transmission, the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RBset); the sending unit 1902 determines the resource block used to send the uplink transmission according to the indication information, and the sending unit also sends the uplink transmission on the determined resource block.

[0441] For example, in the case where the terminal device indicates that it is capable of sending uplink transmission in an intra-cell guard band, the sending unit determines that the resource blocks used to send the uplink transmission are: the intersection of the at least two resource block sets and the resource blocks in the intra-cell guard band between the at least two resource block sets, and the interlace resource blocks indicated by the indication information. For another example, in the case where the terminal device does not indicate that it is capable of sending uplink transmission in an intra-cell guard band, the sending unit determines that the resource blocks used to send the uplink transmission are: the intersection of the interlace resource blocks indicated by the indication information and the resource blocks in the at least two resource block sets.

[0442] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink transmission device 1900 may also include other components or modules, and the specific contents of these components or modules may refer to the relevant technology.

[0443] Furthermore, for simplicity, Fig.19 The connection relationship or signal direction between the various components or modules is only exemplified, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned various components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of this application is not limited to this.

[0444] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0445] It can be seen from the above embodiments that it is possible to support a terminal device in determining resources for uplink transmission, thereby enabling the uplink transmission to be correctly sent and received.

[0446] Embodiments of the tenth aspect

[0447] The present application also provides a communication system. Figure 1 , the contents that are the same as those in the embodiments of the first to ninth aspects will not be repeated.

[0448] In some embodiments, the communication system 100 may include:

[0449] The terminal device 102 comprises the uplink transmission device 1900 as described in the embodiment of the ninth aspect.

[0450] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0451] Fig. 20 Schematic diagram of the network device in the embodiment of the present application. Fig. 20 As shown, the network device 2000 may include: a processor 2010 (such as a central processing unit CPU) and a memory 2020; the memory 2020 is coupled to the processor 2010. The memory 2020 can store various data; in addition, it also stores a program 2030 for information processing, and executes the program 2030 under the control of the processor 2010.

[0452] For example, the processor 2010 may be configured to execute a program to implement the uplink transmission method as described in the embodiments of the first to sixth aspects. For example, the processor 2010 may be configured to perform the following control: sending configuration information and / or indication information to the terminal device. In addition, the processor 2010 may be configured to execute a program to implement the uplink transmission reception method as described in the embodiments of the seventh aspect.

[0453] In addition, the network device 2000 may also include an uplink transmission receiving device, which may include a first sending unit and a first receiving unit. The first sending unit sends indication information for scheduling uplink transmission, the indication information includes an indication field for indicating a resource block set (RB set), and the indication information indicates at least two resource block sets (RB sets); the first receiving unit receives the uplink transmission according to whether the terminal device indicates that the terminal device can send uplink transmission in an intra-cell guard band.

[0454] In addition, if Fig. 20 As shown, the network device 2000 may also include: a transceiver 2040 and an antenna 2050, etc.; wherein the functions of the above components are similar to those of the prior art and are not described in detail here. It is worth noting that the network device 2000 does not necessarily have to include Fig. 20 In addition, the network device 2000 may also include Fig. 20For components not shown, reference may be made to the prior art.

[0455] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0456] Fig.21 Schematic diagram of a terminal device in an embodiment of the present application. Fig.21 As shown, the terminal device 2100 may include a processor 2110 and a memory 2120; the memory 2120 stores data and programs and is coupled to the processor 2110. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0457] For example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the first aspect. For example, the processor 2110 may be configured to perform the following control: receiving configuration information of an uplink partial bandwidth (UL BWP), wherein the configuration information of the uplink partial bandwidth (UL BWP) indicates that the uplink partial bandwidth includes at least two resource block sets (RB sets); on the downlink partial bandwidth corresponding to the uplink partial bandwidth, not monitoring or not receiving the first indication information for scheduling uplink transmission that does not include an indication field for indicating a resource block set.

[0458] For example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the second aspect. The processor 2110 may be configured to perform the following control: receiving indication information that does not include an indication field for indicating a resource block set, the indication information scheduling an uplink transmission on an uplink partial bandwidth (ULBWP) including at least two resource block sets (RB sets); and sending the uplink transmission on at least one predefined or preconfigured resource block set.

[0459] Alternatively, the processor 2110 may be configured to perform the following control: receiving indication information for scheduling the terminal device to send uplink transmission; the indication information includes an indication field for indicating a resource block set, and the indication information is downlink control information having a downlink control information format 0_0, or downlink control information having a downlink control information format 0_2, or a random access response (RAR); and sending the uplink transmission on at least one resource block set indicated by the indication field.

[0460] For another example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the third aspect. For example, the processor 2110 may be configured to perform the following control: receiving indication information for scheduling the terminal device to send uplink transmission; determining the number of frequency domain resource allocation (FRDA) bits according to the subcarrier spacing (SCS) of the activated uplink portion of the bandwidth when receiving the indication information and / or the number of resource block sets included; or, determining the number of frequency domain resource allocation bits according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, determining the number of frequency domain resource allocation (FRDA) bits according to the subcarrier spacing (SCS) of a specific uplink portion of the bandwidth in at least one configured uplink portion of the bandwidth and / or the number of resource block sets included.

[0461] For another example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the fourth aspect. For example, the processor 2110 may be configured to perform the following control: receiving first configuration information indicating a guard band and / or a resource block set (RB set) of an uplink carrier; and determining the resource blocks included in the resource block set on the uplink carrier according to the frequency domain position (e.g., CRB index) of the starting resource block of the guard band and / or the frequency domain position of the ending resource block.

[0462] Alternatively, the processor 2110 may be configured to perform the following control: when being indicated that there is no guard band, receiving indication information for scheduling the terminal device to send uplink transmission; wherein the indication information does not include an indication field for indicating a resource block set.

[0463] For another example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the fifth aspect. For example, the processor 2110 may be configured to perform the following control: receiving indication information indicating resources used by a terminal device to send uplink transmission; and when a downlink carrier is configured to have no guard band, treating a predetermined number of resource blocks in a downlink partial bandwidth (DL BWP) as a predefined or preconfigured resource block set, and sending the uplink transmission on the predefined or preconfigured resource block set.

[0464] For another example, the processor 2110 may be configured to execute a program to implement the uplink transmission method as described in the embodiment of the sixth aspect. For example, the processor 2110 may be configured to perform the following control: receiving indication information for scheduling uplink transmission, the indication information including an indication field for indicating a resource block set (RB set), the indication information indicating at least two resource block sets (RB sets); and determining a resource block for sending the uplink transmission according to the indication information, the sending unit also sending the uplink transmission on the determined resource block.

[0465] like Fig.21 As shown, the terminal device 2100 may also include: a communication module 2130, an input unit 2140, a display 2150, and a power supply 2160. The functions of the above components are similar to those of the prior art and are not described here. It is worth noting that the terminal device 2100 does not necessarily include Fig.21 All components shown in the figure are not necessary; in addition, the terminal device 2100 may also include Fig.21 For components not shown, reference may be made to the prior art.

[0466] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the uplink transmission method described in the first to fourth embodiments.

[0467] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the uplink transmission method described in the first to fourth embodiments.

[0468] The above devices and methods of the present application can be implemented by hardware, or by hardware combined with software. The present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0469] The method / device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules. These software modules may correspond to the various steps shown in the figure, respectively. These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0470] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if a device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0471] For one or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks, it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application. For one or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks, it can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0472] The present application is described above in conjunction with specific implementation methods, but it should be clear to those skilled in the art that these descriptions are exemplary and are not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on the spirit and principles of the present application, and these modifications and variations are also within the scope of the present application.

[0473] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0474] Note 1: An uplink transmission method, comprising:

[0475] The terminal device receives configuration information of an uplink portion bandwidth (UL BWP), wherein the configuration information of the uplink portion bandwidth indicates that the uplink portion bandwidth includes at least two resource block sets (RB sets); and

[0476] On a downlink partial bandwidth (DL BWP) corresponding to the uplink partial bandwidth, first indication information for scheduling uplink transmission and not including an indication field for indicating a resource block set is not monitored or received.

[0477] Note 2: The method according to Note 1, wherein the uplink portion of the bandwidth and the corresponding downlink portion of the bandwidth have the same identifier (ID).

[0478] Note 3. The method according to Note 1 or 2, wherein the first indication information includes: downlink control information having a downlink control information format 0_0, or downlink control information having a downlink control information format 0_2, or a random access response (RAR) in a random access process.

[0479] Note 4. The method according to any one of Notes 1 to 3, wherein the method further comprises:

[0480] The terminal device does not expect to be configured or determines not to be configured to monitor or receive the first indication information on the downlink portion of the bandwidth corresponding to the uplink portion of the bandwidth.

[0481] Note 5. The method according to any one of Notes 1 to 4, wherein the method further comprises:

[0482] The terminal device does not monitor or receive the second indication information for scheduling downlink transmission on the downlink portion of the bandwidth corresponding to the uplink portion of the bandwidth.

[0483] Note 6. The method according to Note 5, wherein the second indication information includes: downlink control information having a downlink control information format 1_0.

[0484] Note 7. The method according to any one of Notes 1 to 6, wherein the method further comprises:

[0485] The terminal device does not send a physical random access channel (PRACH) of contention-based random access (CBRA) on the uplink portion of the bandwidth;

[0486] Alternatively, the terminal device does not send a physical random access channel (PRACH) other than that used for beam failure recovery (BFR) on the uplink portion of the bandwidth;

[0487] Alternatively, the terminal device does not send a physical random access channel (PRACH) on the uplink portion of the bandwidth.

[0488] Note 8. The method according to Note 7, wherein the uplink partial bandwidth configuration information does not include information for indicating a physical random access channel configuration for contention-based random access (CBRA);

[0489] Alternatively, the uplink partial bandwidth configuration information does not include information for indicating a physical random access channel configuration other than that used for beam failure recovery;

[0490] Alternatively, the uplink partial bandwidth configuration information does not include information for indicating a physical random access channel configuration.

[0491] Note 9. The method according to any one of Notes 1 to 8, wherein the method further comprises:

[0492] The terminal device receives configuration information of the downlink portion of bandwidth (DL BWP), and the configuration information of the downlink portion of bandwidth does not include configuration information instructing the terminal device to monitor or receive the first indication information, and / or does not include configuration information instructing the terminal device to monitor or receive the second indication information.

[0493] Note 10: An uplink transmission method, comprising:

[0494] The terminal device receives indication information that does not include an indication field for indicating a resource block set, wherein the indication information schedules uplink transmission on an uplink part bandwidth (UL BWP) including at least two resource block sets (RB sets); and

[0495] The uplink transmission is sent on at least one predefined or preconfigured set of resource blocks.

[0496] Note 11. The method according to Note 10, wherein the indication information includes: downlink control information having a downlink control information format 0_0.

[0497] Note 12. The method according to Note 11, wherein the downlink control information is scrambled using C-RNTI or CS-RNTI or MCS-C-RNTI or TC-RNTI.

[0498] Note 13. The method according to any one of Notes 10 to 12, wherein the at least one resource block set is predefined, and the predefined resource block set includes at least one of the following:

[0499] An uplink resource block set in the at least two resource block sets that is associated with a downlink resource block set where the frequency domain resource for sending the indication information is located;

[0500] An uplink resource block set corresponding to the frequency domain resource for sending the indication information in the at least two resource block sets;

[0501] A resource block set having a smallest resource block set index value among the at least two resource block sets;

[0502] The resource block set with the lowest frequency domain position among the at least two resource block sets;

[0503] The resource block set with the highest frequency domain position in the at least two resource block sets;

[0504] A resource block set overlapping with the initial uplink portion bandwidth in the at least two resource block sets;

[0505] A resource block set in the at least two resource block sets that overlaps with part or all of the resource block sets included in the initial uplink portion of the bandwidth;

[0506] Part or all of the at least two resource block sets.

[0507] Note 14. A method according to any one of Notes 10 to 12, wherein the at least one resource block set is configured or indicated by high-level signaling; the high-level signaling configures the association relationship between the uplink resource block set and the downlink resource block set, or the high-level signaling configures the uplink resource block set scheduled by the indication information.

[0508] Note 15. The method according to Note 10, wherein the indication information includes: a random access response (RAR) in a random access process, or downlink control information with downlink control information format 0_0 encrypted with TC-RNTI.

[0509] Note 16. The method according to Note 15, wherein the at least one resource block set is predefined, and the predefined resource block set includes at least one of the following:

[0510] An uplink resource block set in the at least two resource block sets that is associated with a downlink resource block set where the frequency domain resource for sending the indication information is located;

[0511] An uplink resource block set corresponding to the frequency domain resource for sending the indication information in the at least two resource block sets;

[0512] A resource block set overlapping with the initial uplink portion bandwidth in the at least two resource block sets;

[0513] A resource block set in the at least two resource block sets that overlaps with part or all of the resource block sets included in the initial uplink portion of the bandwidth;

[0514] Some or all of the resource block sets in the at least two resource block sets;

[0515] The at least two resource block sets are resource block sets used to send the random access preamble sequence corresponding to the uplink transmission.

[0516] Note 17. The method according to Note 15, wherein the at least one resource block set is configured or indicated by high-level signaling; the high-level signaling configures the association relationship between the uplink resource block set and the downlink resource block set, or the high-level signaling configures the uplink resource block set scheduled by the indication information.

[0517] Note 18: An uplink transmission method, comprising:

[0518] The terminal device receives indication information for scheduling the terminal device to send uplink transmission; the indication information includes an indication field for indicating a resource block set, and the indication information is downlink control information having a downlink control information format 0_0, or downlink control information having a downlink control information format 0_2, or a random access response (RAR); and

[0519] The terminal device sends the uplink transmission on at least one resource block set indicated by the indication field.

[0520] Note 19: An uplink transmission method, comprising:

[0521] The terminal device receives indication information for scheduling the terminal device to send uplink transmission;

[0522] The number of frequency domain resource allocation (FRDA) bits is determined according to the subcarrier spacing (SCS) of the activated uplink portion of the bandwidth when the indication information is received and / or the number of resource block sets included; or, the number of frequency domain resource allocation bits is determined according to the carrier where the uplink transmission is located or the subcarrier spacing of the activated uplink portion of the bandwidth and / or the number of resource block sets included in the carrier where the uplink transmission is located; or, the number of frequency domain resource allocation (FRDA) bits is determined according to the subcarrier spacing (SCS) and / or the number of resource block sets included in a specific uplink portion of the bandwidth configured at least one uplink portion.

[0523] Note 20. The method according to Note 19, wherein the indication information includes: downlink control information having a downlink control information format of 0_1, downlink control information having a downlink control information format of 0_2, downlink control information having a downlink control information format of 0_0, or a random access response (RAR) in a random access procedure.

[0524] Note 21. The method according to Note 19, wherein:

[0525] In a case where the terminal device is configured to send the uplink transmission using interlace frequency domain resources, the indication information does not include an indication field for indicating a partial bandwidth; or, the indication information includes an indication field for indicating a partial bandwidth and the terminal device ignores the indication field for indicating the partial bandwidth included in the indication information.

[0526] Note 22. The method according to Note 19, wherein the indication information includes an indication field for indicating a partial bandwidth, and the indication field indicates a second uplink partial bandwidth that is different from the activated uplink partial bandwidth, i.e., the first uplink partial bandwidth.

[0527] Note 23. The method according to Note 22, wherein the method further comprises:

[0528] In a case where the terminal device is configured to send the uplink transmission using interlace frequency domain resources, the terminal device expects or determines that the subcarrier spacing (SCS) of the first uplink portion of the bandwidth is the same as the subcarrier spacing of the second uplink portion of the bandwidth.

[0529] Note 24. The method according to Note 23, wherein the method further comprises:

[0530] The terminal device further expects or determines that the number of resource block sets on the first uplink portion of bandwidth is the same as the number of resource block sets on the second uplink portion of bandwidth.

[0531] Note 25. The method according to Note 22, wherein the method further comprises:

[0532] The terminal device ignores the indication field used to indicate the resource block set in the indication information.

[0533] Note 26. The method according to Note 22, wherein the method further comprises:

[0534] The terminal device determines the frequency domain resources for sending the uplink transmission on the second uplink bandwidth based on the subcarrier spacing and / or the number of resource block sets included in the first uplink bandwidth and the second uplink bandwidth.

[0535] Note 27. A method according to Note 26, wherein the terminal device determines an actual number of FRDA bits of the first uplink portion of the bandwidth and an assumed number of FRDA bits of the second uplink portion of the bandwidth; and determines frequency domain resources for sending the uplink transmission on the second uplink portion of the bandwidth based on the actual number of FRDA bits and the assumed number of FRDA bits.

[0536] Note 28. A method according to Note 22, wherein the terminal device uses at least one bit in the FRDA indication field of the indication information for indicating a resource block set to indicate an interleaved frequency resource, and uses at least one bit in the FRDA indication field of the indication information for indicating an interleaved frequency resource to indicate a resource block set.

[0537] Note 29. A method according to Note 28, wherein the terminal device ignores at least one bit in the FRDA indication field of the indication information.

[0538] Note 30. The method according to any one of Notes 26 to 29, wherein:

[0539] The min(X1+Y1,X2+Y2) bits in the FRDA indication field of the said indication information are used to indicate the frequency-domain resources on the second uplink partial bandwidth; where min() represents the operation of taking the smaller value, X1 and Y1 are the actual FRDA bits of the first uplink partial bandwidth, and X2 and Y2 are the assumed FRDA bits of the second uplink partial bandwidth.

[0540] Appendix Note 31. According to the method described in Appendix Note 30, where the least significant bit (LSB) of min(X1+Y1,X2) is used to indicate the interleaved frequency-domain resources, and the most significant bit (MSB) of min(X1+Y1-min(X1+Y1,X2),Y2) is used to indicate the resource block set.

[0541] Appendix Note 32. According to the method described in Appendix Note 31, where if X1+Y1<X2, the interleaved frequency-domain resource that the LSB of min(X1+Y1,X2) can indicate is one of the predefined first 2^min(X1+Y1,X2) interleaved frequency-domain resources corresponding to the second uplink partial bandwidth;

[0542] if X1+Y1-min(X1+Y1,X2)<Y2, the resource block set that the MSB of min(X1+Y1-min(X1+Y1,X2),Y2) can indicate is one of the predefined first 2^min(X1+Y1-min(X1+Y1,X2),Y2) resource block sets corresponding to the second uplink partial bandwidth.

[0543] Appendix Note 33. According to the method described in any one of Appendix Notes 26 to 29, where

[0544] the min(X1,X2)+min(Y1,Y2) bits in the FRDA indication field of the said indication information are used to indicate the frequency-domain resources on the second uplink partial bandwidth; where min() represents the operation of taking the smaller value, X1 and Y1 are the actual FRDA bits of the first uplink partial bandwidth, and X2 and Y2 are the assumed FRDA bits of the second uplink partial bandwidth.

[0545] Appendix Note 34. According to the method described in Appendix Note 33, where the min(X1,X2) bits in X1 are used to indicate the interleaved frequency-domain resources, and the min(Y1,Y2) bits in Y1 are used to indicate the resource block set.

[0546] Appendix Note 35. According to the method described in Appendix Note 34, where if X1<X2, the interleaved frequency-domain resource that min(X1,X2) can indicate is one of the predefined first min(X1,X2) interleaved frequency-domain resources corresponding to the second uplink partial bandwidth;

[0547] If Y1 < Y2, the resource block set that min(Y1, Y2) can indicate is one of the predefined first 2^min(Y1, Y2) resource block sets corresponding to the second uplink partial bandwidth.

[0548] Supplementary Note 36: An uplink transmission method, comprising:

[0549] The terminal device receives first configuration information for indicating a guard - band and / or an RB set of an uplink carrier; and

[0550] The terminal device determines the resource blocks included in the resource block set on the uplink carrier according to the frequency - domain position (e.g., CRB index) of the start resource block of the guard - band and / or the frequency - domain position of the end resource block.

[0551] Supplementary Note 37: The method according to Supplementary Note 36, wherein the first configuration information further indicates that there is no guard - band.

[0552] Supplementary Note 38: The method according to Supplementary Note 36 or 37, wherein the method further comprises:

[0553] When the first configuration information indicates that there is no guard - band, determining that the resource blocks included in the resource block set of the uplink carrier are predefined.

[0554] Supplementary Note 39: The method according to Supplementary Note 37, wherein the first configuration information indicates that there is no guard - band by a specific value.

[0555] Supplementary Note 40: The method according to Supplementary Note 36 or 37, wherein the first configuration information includes information for indicating the frequency - domain position (e.g., CRB index) of the start resource block of the guard - band and / or the frequency - domain position of the end resource block of the guard - band; wherein the frequency - domain position of the start resource block of the guard - band indicated by the information is higher than or equal to the frequency - domain position of the end resource block of the guard - band.

[0556] Supplementary Note 41: The method according to Supplementary Note 40, wherein the start common resource block (CRB) index is equal to the end CRB index plus 1.

[0557] Supplementary Note 42: The method according to Supplementary Note 36 or 37, wherein the method further comprises:

[0558] The terminal device receives second configuration information for indicating the resource block set of the uplink carrier.

[0559] Supplementary Note 43: An uplink transmission method, comprising:

[0560] The terminal device receives first configuration information for indicating a guard band and / or a resource block set (RB set) of an uplink carrier; and

[0561] The terminal device receives third configuration information of the UL BWP of the uplink carrier;

[0562] If the first configuration information indicates that there is no guard band, the third configuration information does not include information instructing the terminal device to use staggered frequency domain resources to send uplink transmission; or, if the third configuration information includes information instructing the terminal device to use staggered frequency domain resources to send uplink transmission, the first configuration information does not indicate that there is no guard band.

[0563] Note 44. A method according to any one of Notes 36 to 43, wherein the first configuration information includes intraCellGuardBandUL-r16.

[0564] Note 45. An uplink transmission method, comprising:

[0565] When a terminal device is indicated that there is no frequency guard band, the terminal device receives indication information for scheduling the terminal device to send uplink transmission; wherein the indication information does not include an indication field for indicating a resource block set.

[0566] Note 46. The method according to Note 45, wherein the presence or absence of a frequency guard band is indicated by intraCellGuardBandUL-r16.

[0567] Note 47: An uplink transmission method, comprising:

[0568] receiving indication information indicating resources used by a terminal device for sending uplink transmission; and

[0569] In the case where the downlink carrier is configured without a guard band, a predetermined number of resource blocks in a downlink partial bandwidth (DLBWP) is used as a predefined or preconfigured resource block set, and the uplink transmission is sent on the predefined or preconfigured resource block set.

[0570] Note 48. A terminal device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink transmission method as described in any one of Notes 1 to 47.

[0571] Note 49. A communication system, comprising the terminal device as described in Note 48.

Claims

1. An uplink transmission device, comprising: a receiving unit, configured to receive indication information, wherein the indication information schedules an uplink transmission on an uplink partial bandwidth including at least two resource block sets, and the indication information does not include an indication field for indicating a resource block set allocated for the uplink transmission; as well as A sending unit is configured to send the uplink transmission on a default resource block set of the uplink portion of the bandwidth.

2. The device according to claim 1, wherein: The indication information includes: downlink control information having downlink control information format 0_0; wherein the downlink control information adopts C-RNTI or CS-RNTI or MCS-C-RNTI.

3. The device according to claim 2, wherein: The default set of resource blocks is: a resource block set in the uplink bandwidth corresponding to the frequency resources used to send the indication information; or The resource block set with the lowest resource block set index in the uplink portion of the bandwidth; or The resource block set with the lowest frequency position in the uplink part of the bandwidth.

4. The device according to claim 1, wherein: The instruction information includes: A random access response (RAR) in a random access procedure, or downlink control information having downlink control information format 0_0 and scrambled by TC-RNTI.

5. The device according to claim 4, wherein: The default set of resource blocks is: A resource block set in the uplink portion of bandwidth is used to send a physical random access channel (PRACH) corresponding to the uplink transmission.

6. The device according to claim 1, wherein: The uplink transmission is a physical uplink shared channel (PUSCH) transmission.

7. The device according to claim 1, wherein: The receiving unit is further configured to: Configuration information of a resource block set for a guard band and / or an uplink carrier in a cell is received, and configuration information of an uplink portion of bandwidth on the carrier is received.

8. The device according to claim 7, wherein: The uplink bandwidth includes an integer number of resource block sets of the carrier. The starting resource block of the uplink portion of the bandwidth is the same as the starting resource block of the resource block set with the lowest resource block set index in the uplink portion of the bandwidth, The end resource block of the uplink bandwidth portion is the same as the end resource block in the resource block set with the highest resource block set index in the uplink bandwidth portion.

9. The device according to claim 7, wherein: The resource block set has a resource block set index for the carrier and a resource block set index for the uplink portion of the bandwidth. The resource block sets are indexed in order of frequency positions, and the resource block set with the lowest frequency position has the lowest resource block set index.

10. The device according to claim 1, wherein: The configuration information for the intra-cell guard band and / or the resource block set of the uplink carrier indicates that there is no intra-cell guard band for the uplink carrier.

11. An uplink transmission device, comprising: a sending unit, configured to send indication information, wherein the indication information schedules an uplink transmission on an uplink portion of a bandwidth including at least two resource block sets, and the indication information does not include an indication field for indicating a resource block set allocated for the uplink transmission; as well as A receiving unit receives the uplink transmission on a default resource block set of the uplink portion of the bandwidth.

12. The device according to claim 11, wherein The indication information includes: downlink control information having downlink control information format 0_0; wherein the downlink control information adopts C-RNTI or CS-RNTI or MCS-C-RNTI.

13. The device according to claim 12, wherein: The default set of resource blocks is: a resource block set in the uplink bandwidth corresponding to the frequency resources used to send the indication information; or The resource block set with the lowest resource block set index in the uplink portion of the bandwidth; or The resource block set with the lowest frequency position in the uplink part of the bandwidth.

14. The device according to claim 11, wherein: The instruction information includes: A random access response (RAR) in a random access procedure, or downlink control information having downlink control information format 0_0 and scrambled by TC-RNTI.

15. The device according to claim 14, wherein: The default set of resource blocks is: A resource block set in the uplink portion of bandwidth is used to send a physical random access channel (PRACH) corresponding to the uplink transmission.

16. The device according to claim 11, wherein The uplink transmission is a physical uplink shared channel (PUSCH) transmission.

17. The device according to claim 11, wherein: The sending unit is further configured to: Configuration information of a resource block set for a guard band and / or an uplink carrier in a cell is received, and configuration information of an uplink portion of bandwidth on the carrier is received.

18. The device according to claim 17, wherein: The uplink bandwidth includes an integer number of resource block sets of the carrier. The starting resource block of the uplink portion of the bandwidth is the same as the starting resource block of the resource block set with the lowest resource block set index in the uplink portion of the bandwidth, The end resource block of the uplink bandwidth portion is the same as the end resource block in the resource block set with the highest resource block set index in the uplink bandwidth portion.

19. The device according to claim 17, wherein: The resource block set has a resource block set index for the carrier and a resource block set index for the uplink portion of the bandwidth. The resource block sets are indexed in order of frequency positions, and the resource block set with the lowest frequency position has the lowest resource block set index.

20. The device according to claim 11, wherein The configuration information for the intra-cell guard band and / or the resource block set of the uplink carrier indicates that there is no intra-cell guard band for the uplink carrier.

21. A communication system comprising: A terminal device comprising an uplink transmission device as claimed in any one of claims 1 to 10; as well as A network device comprising the uplink transmission device according to any one of claims 11 to 20.

Images