WO2022067783A1 - Procédé et appareil d'émission-réception de données, et système de communication - Google Patents

Procédé et appareil d'émission-réception de données, et système de communication Download PDF

Info

Publication number
WO2022067783A1
WO2022067783A1 PCT/CN2020/119699 CN2020119699W WO2022067783A1 WO 2022067783 A1 WO2022067783 A1 WO 2022067783A1 CN 2020119699 W CN2020119699 W CN 2020119699W WO 2022067783 A1 WO2022067783 A1 WO 2022067783A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
configuration information
resource
bwp
resource block
Prior art date
Application number
PCT/CN2020/119699
Other languages
English (en)
Chinese (zh)
Inventor
蒋琴艳
张磊
Original Assignee
富士通株式会社
蒋琴艳
张磊
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 蒋琴艳, 张磊 filed Critical 富士通株式会社
Priority to PCT/CN2020/119699 priority Critical patent/WO2022067783A1/fr
Publication of WO2022067783A1 publication Critical patent/WO2022067783A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • the unlicensed frequency band or shared spectrum is an important part of spectrum resources.
  • many systems support data transmission in the unlicensed frequency band, such as WiFi, Long Term Evolution (LTE, Long Term Evolution) licensed spectrum auxiliary access.
  • Access LAA, License Assisted Access
  • NR New Radio
  • the NR system supports multiple sub-carrier spacings (SCS, Sub-Carrier Spacing) and introduces the concept of a partial bandwidth (BWP, BandWidth Part).
  • the network device can configure one or more BWPs (UL BWPs) on the uplink carrier and one or more BWPs (DL BWPs) on the downlink carriers for the terminal device through high-layer signaling.
  • Different sub-carrier spacing (SCS, Sub-Carrier Spacing) can be configured for different BWPs, for example, SCS can be 15kHz, 30kHz, etc.
  • the terminal device can use the active BWP (active BWP) to work, that is, to receive downlink data on the active DL BWP, and send uplink data on the active UL BWP.
  • intra-cell guard bands intra-cell guard bands
  • GB guard bands, guard bands, or GB
  • resource block sets RB set
  • RB sets resource block sets
  • the inventor found that: according to the existing RB set configuration method and BWP configuration method, in some cases, the requirement that the BWP should include an integer number of resource block sets (RB sets) cannot be met, or the network device cannot uniquely determine the Which part of resources (i.e. RBs) receive the Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • the embodiments of the present application provide a method, apparatus, and communication system for sending and receiving data, which can meet the requirement that the BWP should include an integer number of resource block sets (RB sets), or enable network devices to uniquely Determines on which part of the resource the Physical Uplink Shared Channel (PUSCH) is received.
  • RB sets resource block sets
  • PUSCH Physical Uplink Shared Channel
  • a method for sending and receiving data is provided, which is applied to a terminal device, and the method includes:
  • Second configuration information is received, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • an apparatus for sending and receiving data which is applied to terminal equipment, and the apparatus includes:
  • a first receiving unit that receives first configuration information for configuring a resource block set (RB set) in a carrier
  • a second receiving unit which receives second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K predefined resource block sets, where K is a natural number.
  • a method for sending and receiving data is provided, which is applied to a terminal device, and the method includes:
  • the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, and K is a natural number;
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured by the first configuration information is the same as the predefined resource block set .
  • an apparatus for sending and receiving data which is applied to terminal equipment, and the apparatus includes:
  • a third receiving unit which receives first configuration information, the first configuration information is used to configure a resource block set (RB set) in the carrier;
  • a fourth receiving unit which receives second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), and the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, K is a natural number,
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured by the first configuration information is the same as the predefined resource block set .
  • a method for sending and receiving data is provided, which is applied to a network device, and the method includes:
  • Send second configuration information where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • an apparatus for sending and receiving data which is applied to network equipment, and the apparatus includes:
  • a first sending unit which sends first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • a second sending unit which sends second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • a method for sending and receiving data is provided, which is applied to a network device, and the method includes:
  • the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, and K is a natural number
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined resource block set the same.
  • an apparatus for sending and receiving data which is applied to network equipment, and the apparatus includes:
  • a third sending unit which sends first configuration information, where the first configuration information is used to configure a resource block set (RB set) in the carrier;
  • a fourth sending unit which sends second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), and the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, K is a natural number,
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined resource block set the same.
  • the BWP can meet the requirement of including an integer number of resource block sets (RB sets), or the network device can uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is an exemplary diagram of carriers and resource blocks
  • 3A is an exemplary diagram of a guard band and a resource block set
  • 3B is an exemplary diagram of the relationship between guard bands, resource block sets and partial bandwidths
  • Fig. 4 is an example diagram of interlace frequency domain resources
  • Fig. 5 is a schematic diagram of the interaction between network equipment and terminal equipment
  • FIG. 6 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application.
  • Fig. 7 is a schematic diagram of RB set and Initial BWP of different devices in the prior art
  • Fig. 8 is a schematic diagram of RB set and Initial BWP predefined in this application.
  • Fig. 9 is a schematic diagram of the RB set sending PRACH and PUSCH in the random access process
  • Figure 10 is a schematic diagram of the resources used by different terminal equipment in the CBRA process
  • Fig. 11 is a schematic diagram of the resources used in the CBRA process of the related art.
  • Fig. 12 is a schematic diagram of a predefined RB set in this application and a UL BWP configured with PRACH resources;
  • FIG. 13 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application.
  • FIG. 13A is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application.
  • Fig. 14 is a schematic diagram of RB set and Initial BWP predefined in this application.
  • Fig. 15 is a schematic diagram of a predefined RB set in this application and a UL BWP configured with PRACH resources;
  • Figure 16 is another schematic diagram of a predefined RB set and a UL BWP configured with PRACH resources in this application;
  • 17 is a schematic diagram of a method of an uplink transmission receiving method according to an embodiment of the seventh aspect
  • FIG. 18 is a schematic diagram of a method of an uplink transmission receiving method according to an embodiment of the seventh aspect
  • 19 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • 20 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • 21 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • 22 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • FIG. 23 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
  • FIG. 24 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access) and so on.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • 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.
  • Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femeto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic 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.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates the case of a terminal device and a network device as an example.
  • a communication system 100 may include a network device 101 and terminal devices 102 and 103 .
  • FIG. 1 only takes two terminal devices and one network device as an example for description, but the embodiment of the present application is not limited to this.
  • the network device 101 and the terminal devices 102 and 103 may perform transmission of existing services or services that can be implemented in the future.
  • these services may include, but are not limited to: Enhanced Mobile Broadband (eMBB, enhanced Mobile Broadband), Massive Machine Type Communication (mMTC, massive Machine Type Communication), and Ultra-Reliable and Low Latency Communication (URLLC, Ultra-Reliable and Low). -Latency Communication), etc.
  • FIG. 2 is an example diagram of carriers and resource blocks, which are applicable to both uplink and downlink.
  • 201 denotes a resource block (RB), and the bandwidth of the carrier includes an integer number of RBs.
  • 201a is the RB corresponding to the starting position of the carrier.
  • the carrier width can be configured by carrierBandwidth in SCS-SpecificCarrier IE, and the starting position of the carrier can be configured by offsetToCarrier in SCS-SpecificCarrier IE.
  • FIG. 3A is an example diagram of guard bands and resource block sets.
  • 201 represents a resource block (RB)
  • each RB set for example, RB set 0, RB set 1, RB set 2, RB set 3
  • each GB respectively includes an integer number of RBs.
  • There is a guard band between two resource block sets e.g. GB 0 between RB set 0 and RB set 1. .
  • the bandwidth of the carrier includes an integer number of RBs, for example, in Figure 3A, the bandwidth of the carrier includes RB set 0, RB set 1, RB set 2, RB set 3 and GB 0, GB 1, GB 2, each RB set and GB Each includes an integer number of RBs, so the bandwidth of the carrier includes an integer number of RBs.
  • 201a is the first RB of RB set 0, and is also the RB (ie, the first RB) corresponding to the starting position of the carrier.
  • FIG. 3B is an exemplary diagram of the relationship among guard bands, resource block sets and partial bandwidths, which are applicable to both downlink and uplink.
  • a BWP includes an integer number of RB sets, and the starting RB and the last RB of the BWP are the starting RB of the first RB set and the last RB of the last RB set, respectively.
  • the BWP of Figure 3B includes RB set 1 and RB set 2, with GB 1 between RB set 1 and RB set 2, the starting RB of BWP is the starting RB of RB set 1, and the last RB of BWP is RB set 2's last RB.
  • a second type of resource allocation (Type 2 resource allocation) is also introduced.
  • the network device may instruct the terminal device to use interlaced resource blocks (Interlaced resource blocks) to send uplink transmission through higher layer signaling. If this resource allocation method is adopted, when scheduling the terminal device to send the PUSCH or PUCCH, the network device will instruct the terminal device which interlaced resource blocks (Interlaced resource blocks) to use to send.
  • Fig. 5 is a schematic diagram of the interaction between the network device and the terminal device.
  • the network device can send first configuration information to the terminal device, the first configuration information is used to configure the RB set, and can also be sent to the terminal device.
  • the second configuration information, the second configuration information is used to configure the BWP, the two kinds of configuration information may be sent simultaneously (for example, included in the same RRC message), or may be sent separately (not simultaneously).
  • the network device may 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, the Send upstream transmission.
  • FIG. 5 schematically illustrates the interaction between the network device and the terminal device according to the embodiment of the present application.
  • the present application is not limited to this, for example, one or more operations may be omitted, or one or more other operations may be added.
  • uplink control signal and “uplink control information (UCI, Uplink Control Information)” or “physical uplink control channel (PUCCH, Physical Uplink Control Channel)” can be used interchangeably without causing confusion.
  • uplink data signal and “uplink data information” or “physical uplink shared channel (PUSCH, Physical Uplink Shared Channel)” can be interchanged;
  • downlink control signal and “downlink control information (DCI, Downlink Control Information)” or “physical downlink control channel (PDCCH, Physical Downlink Control Channel)” are interchangeable, and the terms “downlink data signal” and “downlink data information” Or “Physical Downlink Shared Channel (PDSCH, Physical Downlink Shared Channel)” can be interchanged.
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • 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
  • sending or receiving PRACH can be understood as sending or receiving data carried by PRACH preamble
  • uplink signals may include uplink data signals and/or uplink control signals, etc., and may also be referred to as uplink transmission (UL transmission) or uplink information or uplink channel.
  • Sending the uplink transmission on the uplink resource can be understood as using the uplink resource to send the uplink transmission.
  • downlink data/signal/channel/information can be understood accordingly.
  • the high-level signaling may be, for example, Radio Resource Control (RRC) signaling; for example, it is called an RRC message (RRC message), for example, including MIB, system information (system information), and dedicated RRC message; RRC IE (RRC information element).
  • RRC Radio Resource Control
  • the high-layer signaling can also be MAC (Medium Access Control) signaling; or called MAC CE (MAC control element).
  • MAC Medium Access Control
  • MAC CE MAC control element
  • the BWP cannot meet the requirement of including an integer number of resource block sets (RB sets), or the network device cannot uniquely determine which part of the resources to receive the Physical Uplink Shared Channel (PUSCH).
  • RB sets resource block sets
  • PUSCH Physical Uplink Shared Channel
  • an embodiment of the present application provides a method for sending and receiving data, which is described from the side of the terminal device, and reference may be made to FIG. 5 for the interaction process between the terminal device and the network device.
  • FIG. 6 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application. As shown in FIG. 6 , the method includes:
  • Operation 601. Receive first configuration information, where the first configuration information is used to configure a resource block set (RB set); and
  • Operation 602 Receive second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • FIG. 6 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 6 .
  • the BWP configured by the second configuration information includes K predefined resource block sets, so that the BWP can meet the requirement of including an integer number of resource block sets (RB sets), or,
  • the network device can uniquely determine on which part of the resource the PUSCH is received.
  • the first configuration information may be intraCellGuardBandsUL-r16 or intraCellGuardBandsDL-r16.
  • the network device may send the first configuration information through high-layer signaling.
  • intraCellGuardBandsUL-r16 and intraCellGuardBandsDL-r16 are used to configure resource block sets (RB sets) of uplink carriers and downlink carriers, respectively.
  • the first configuration information provides the starting RB information (provided by startCRB -r16 in the first configuration information) and size (provided by nrofCRBs- r16) information, and further, according to the first configuration information, the UE may determine N RB-set, x -1 GB and N RB-set, RBs respectively included in the x RB sets in the carrier. That is, the first configuration information is used to configure the RB set.
  • the terminal device determines the guard band and/or resource block set (that is, the predefined resource block) in the cell according to the nominal intra-cell guard band and RB set pattern defined by the RAN4 protocol. block set). For example, in the above example, when the terminal device is configured with intraCellGuardBandsUL-r16, the terminal device determines the GB and RB set according to the parameters included in the intraCellGuardBandsUL-r16.
  • the terminal device determines the RBs (for example, CRB indices of RBs) included in the GB and RB set according to the predefined GB and RB set.
  • the RBs for example, CRB indices of RBs
  • the second configuration information is, for example, initialUplinkBWP, initialDownlinkBWP, BWP-Uplink or BWP-Downlink, or the like.
  • the first configuration information and the second configuration information may be sent by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the resource block set configured by the first configuration information is the same as or different from the predefined resource block set.
  • the carrier may be an uplink carrier, whereby the BWP is an uplink bandwidth part (UL BWP); or, the carrier may also be a downlink carrier, whereby the BWP is a downlink bandwidth part (DL BWP) .
  • UL BWP uplink bandwidth part
  • DL BWP downlink bandwidth part
  • the first configuration information (for example, intraCellGuardBandsUL-r16) is UE-specific, different terminal devices may have different understandings of the RBs included in each GB and RB set on the carrier; while the Initial BWP is cell-specific ( cell-specific), that is, the Initial BWP of each terminal device in the same cell is the same. That is to say, for different terminal devices in the same cell, in the case where the second configuration information configures the initial BWP, the RBs included in the BWP configured by the second configuration information received by the second configuration information are the same. Therefore, in the prior art, for some terminal devices (for example, UE2 in FIG. 7 ), the Initial BWP may include a non-integer number of RB sets, which does not meet the requirement that the BWP includes an integer number of RB sets.
  • Fig. 7 is a schematic diagram of RB set and Initial BWP of different devices in the prior art.
  • the terminal equipment UE1 and UE2 have different understandings of the RBs included in the GB and the RB set on the carrier.
  • the GB of the terminal equipment UE2 is 0, that is, the GB is not configured.
  • the RB sets of the terminal equipment UE1 and UE2 are different.
  • the Initial BWP includes an integer number (eg, 1) of RB sets of the terminal equipment UE1, whereas the Initial BWP includes a non-integer number of RB sets of the terminal equipment UE2. Therefore, for the terminal device UE2, the Initial BWP does not satisfy the requirement that the BWP includes an integer number of RB sets.
  • the BWP involved in operation 602 is the initial bandwidth part (Initial BWP), for example, the initial uplink bandwidth part (Initial UL BWP) or the initial downlink bandwidth Part (Initial DL BWP).
  • Initial BWP the initial bandwidth part
  • Initial UL BWP the initial uplink bandwidth part
  • Initial DL BWP the initial downlink bandwidth Part
  • the BWP configured by the second configuration information includes K predefined resource block sets; for the initial downlink bandwidth Part (Initial DL BWP), the BWP configured by the second configuration information (for example, initialDownlinkBWP) should include K predefined resource block sets.
  • the Initial UL BWP or Initial DL BWP configured by the second configuration information includes 1 predefined RB set, that is, the first RB of the Initial UL BWP or Initial DL BWP is the starting RB of the predefined RB set , the last RB of the Initial UL BWP or Initial DL BWP is the last RB of the predefined RB set. That is to say, whether the initial BWP satisfies the requirement that an integer number of RB sets should be included is always based on whether an integer number of predefined RB sets are included, rather than the RB set configured by the first configuration information. In this way, while ensuring that the initial BWP can meet the requirement of including an integer number of RB sets, it can also allow the network device to flexibly configure a UE-specific RB set for each terminal device through the first configuration information.
  • Figure 8 is a schematic diagram of RB set and Initial BWP predefined in this application.
  • the Initial BWP may be an Initial UL BWP or an Initial DL BWP.
  • the Initial BWP includes 1 predefined RB set.
  • the RB set configured by the first configuration information is different from the predefined RB set.
  • the present application may not be limited to this, and the RB set configured by the first configuration information may be the same as the predefined RB set.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information.
  • an initial UL BWP may also be referred to as a UL BWP configured by initialUplinkBWP
  • an initial DL BWP may also be referred to as a DL BWP configured by initialDownlinkBWP
  • a DL BWP that is not an initial UL BWP may also be referred to as configured by BWP-Uplink UL BWP
  • DL BWP not initial DL BWP can also be called DL BWP configured by BWP-Downlink.
  • the terminal device After the terminal device sends a preamble (ie, PRACH), if the terminal device receives a random access response (RAR) or a downlink scrambled by a Temporary Cell Radio Network Temporary Identity (TC-RNTI) Control information (DCI), the terminal device will use the RB set that sent the PRACH to send the PUSCH scheduled by the RAR or DCI.
  • RAR random access response
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • DCI Temporary Cell Radio Network Temporary Identity
  • FIG. 9 is a schematic diagram of the RB set for transmitting PRACH and PUSCH in the random access process.
  • the active UL BWP of the terminal device includes two RB sets (ie, RB set 0 and RB set 1).
  • the terminal device uses RB set 0 to send PRACH, and after receiving the RAR or TC-RNTI scrambled DCI associated with the sent PRACH, the terminal device uses RB set 0 to send the PUSCH scheduled by the RAR or TC-RNTI scrambled DCI .
  • the RAR and DCI indicate the interlace, and the terminal device can determine the resource for sending the PUSCH according to the indicated interval and the RB set for sending the PRACH. More specifically, the terminal device transmits the PUSCH by using the RBs in the intersection of the RB set where the PRACH is located and the RBs included in the interlace indicated by the RAR or DCI.
  • the network device cannot determine which terminal device is scheduled for when the terminal device transmits PUSCH using RAR or TC-RNTI scrambled DCI. Since the BWP and RB set configurations of different terminal devices are different, the network device cannot uniquely determine which part of the resources to receive the PUSCH.
  • FIG. 10 is a schematic diagram of resources used by different terminal equipments in the CBRA process.
  • the terminal equipment UE1 and the terminal equipment UE2 use the same resources to send PRACH respectively, but due to different understandings of the RBs included in the GB and the RB set on the carrier, the RBs included in the RB set determined by the two terminal equipment are different, that is, the RBs included in the RB set 0 of UE1 and the RB set 0 of UE2 in the figure are different.
  • the resources finally determined for transmitting the PUSCH are different. Therefore, the network device cannot uniquely determine on which part of the resource the PUSCH is received.
  • FIG. 11 is a schematic diagram of the resources used in the CBRA process in the related art.
  • UEs in a cell all use a predefined RB set to send uplink data.
  • the restrictions on the BWP configuration are also different.
  • the terminal device can only send and receive data within the range of the BWP, even if the terminal device UE2 assumes that the predefined RB set 0 is used to send the PUSCH, due to the limitation of the BWP range of the UE2, the resources that the UE2 can actually use to send the PUSCH are the BWP and the PUSCH of the UE2.
  • the overlapping part of the predefined RB set 0, the overlapping part is still different from the resource used by UE1 to send the PUSCH (that is, the RB set 0 of UE1 is the same as the predefined RB set 0, and the BWP of UE1 includes 1 RB set 0 of UE1, therefore, the resource used by UE1 to send PUSCH is RB set 0). Therefore, the network device still cannot uniquely determine the resource. That is to say, in the situation shown in Fig. 11, the related art still has the technical problem that the network device cannot uniquely determine which part of the resources to receive the PUSCH. .
  • the BWP involved in operation 602 is a bandwidth portion configured with physical random access channel (PRACH) resources.
  • PRACH physical random access channel
  • the second configuration information includes K predefined resource block sets, where K is a natural number.
  • the network device can determine the resources of the BWP, so as to receive or transmit data correctly.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information.
  • FIG. 12 is a schematic diagram of a predefined RB set and a UL BWP configured with PRACH resources (PRACH resource) in this application.
  • the UL BWP may include 2 predefined RB sets (ie, predefined RB set 0 and RB set 1).
  • the RB set configured by the first configuration information is different from the predefined RB set.
  • the present application may not be limited to this, and the RB set configured by the first configuration information may be the same as the predefined RB set.
  • the physical random access channel (PRACH) resource may also be a physical random access channel resource not used for contention-free random access (CFRA) based beam failure recovery (BFR), eg, the UL
  • the BWP is configured with rach-ConfigCommon and/or rach-ConfigDedicated.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information; or, the physical random access channel (PRACH) resources are physical random access channel resources for contention-based random access (CBRA), for example, the UL BWP is configured with rach-ConfigCommon, and for other BWPs of the terminal device, the other BWPs It can include a natural number of RB sets configured by the first configuration information; or, the physical random access channel (PRACH) resource is the PRACH resource that the terminal device will receive the RAR after using the PRACH resource to send the PRACH.
  • PRACH physical random access channel
  • the other BWPs may include a natural number of RB sets configured by the first configuration information; or, the physical random access channel (PRACH) resource is a terminal device that uses the PRACH resource to send a PRACH that will receive random access.
  • DCI Downlink Control Information
  • RA-RNTI Radio Network Temporary Identity
  • the method for sending and receiving data according to the embodiment of the first aspect of the present application is not only applicable to the above scenarios 1 and 2, but also applicable to other scenarios.
  • the method for sending and receiving data further includes the following operations:
  • Operation 603 Send or receive data in the partial bandwidth according to the predefined resource block set or the resource block set configured according to the first configuration information.
  • the terminal device can send and receive data according to the appropriate RB set.
  • data can be sent or received on the BWP involved in operation 602 .
  • the BWP is a UL BWP
  • operation 603 sends uplink data on the UL BWP
  • the BWP is a DL BWP
  • operation 603 receives downlink data on the DL BWP.
  • the predefined resource block set may be, for example, the predefined resource block set shown in FIG. 8 or FIG. 12 ; the resource block set configured by the first configuration information may be, for example, shown in FIG. 8 or FIG. 12 .
  • the resource block set configured by the first configuration information may be, for example, shown in FIG. 8 or FIG. 12 .
  • data may be sent or received at the BWP according to a predefined RB set or an RB set configured by the first configuration information.
  • the data to be sent is a physical uplink shared channel (PUSCH) scheduled by a random access response (RAR) or downlink control information (DCI) scrambled by a temporary cell radio network temporary identity (TC-RNTI), then according to the predefined
  • the data is sent by the resource block set; for another example, the data to be sent is the downlink control of Random Access Response (RAR) in Contention-Based Random Access (CBRA) or Temporary Cell Radio Network Temporary Identity (TC-RNTI) scrambled Information (DCI) scheduled physical uplink shared channel (PUSCH), the data is sent according to a predefined set of resource blocks.
  • RAR Random Access Response
  • CBRA Contention-Based Random Access
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • the RB set configured according to the first configuration information sends or receives data at the BWP
  • the RB set configured by the first configuration information and the BWP configured by the second configuration information are used to overlap the RBs (that is, the RBs included in the two include RBs). RBs in the intersection) to send or receive data.
  • the BWP configured by the second configuration information includes K predefined resource block sets, so that the BWP can meet the requirement of including an integer number of resource block sets (RB sets), or,
  • the network device can uniquely determine on which part of the resource the PUSCH is received.
  • the embodiment of the second aspect of the present application provides a method for sending and receiving data, which is described from the terminal device side, and the interaction process between the terminal device and the network device can be referred to FIG. 5 .
  • FIG. 13 is a schematic diagram of a method for sending and receiving data according to an embodiment of the present application. As shown in FIG. 13 , the method includes:
  • Operation 1301. Receive first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • Operation 1302 Receive second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, where K is a natural number.
  • BWP bandwidth part
  • the resource block set configured in the first configuration information corresponds to the bandwidth part (BWP) resource block set configured in operation 1302 and/or the resource block set corresponding to the physical random access channel (PRACH) resource and the predefined resource block set same.
  • BWP bandwidth part
  • PRACH physical random access channel
  • FIG. 13 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 13 .
  • the BWP can be made to meet the requirement of including an integer number of resource block sets (RB sets), or the network device can uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • the description about the first configuration information is the same as that of the embodiment of the first aspect.
  • the first configuration information may be intraCellGuardBandsUL-r16 or intraCellGuardBandsDL-r16.
  • the network device may send the first configuration information through high-layer signaling.
  • intraCellGuardBandsUL-r16 and intraCellGuardBandsDL-r16 are used to configure resource block sets (RB sets) of uplink carriers and downlink carriers, respectively.
  • the first configuration information provides the starting RB information (provided by startCRB -r16 in the first configuration information) and size (provided by nrofCRBs- r16) information, and further, according to the first configuration information, the UE may determine N RB-set, x -1 GB and N RB-set, RBs respectively included in the x RB sets in the carrier. That is, the first configuration information is used to configure the RB set.
  • the terminal device determines the guard band and/or resource block set (that is, the predefined resource block) in the cell according to the nominal intra-cell guard band and RB set pattern defined by the RAN4 protocol. block set). For example, in the above example, when the terminal device is configured with intraCellGuardBandsUL-r16, the terminal device determines the GB and RB set according to the parameters included in the intraCellGuardBandsUL-r16.
  • the terminal device determines the RBs (for example, CRB indices of RBs) included in the GB and RB set according to the predefined GB and RB set.
  • the RBs for example, CRB indices of RBs
  • the second configuration information is, for example, initialUplinkBWP, initialDownlinkBWP, BWP-Uplink or BWP-Downlink, or the like.
  • the first configuration information and the second configuration information may be sent by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the resource block set configured by the first configuration information is the same as or different from the predefined resource block set.
  • the carrier may be an uplink carrier, whereby the BWP is an uplink bandwidth part (UL BWP); or, the carrier may also be a downlink carrier, whereby the BWP is a downlink bandwidth part (DL BWP) .
  • UL BWP uplink bandwidth part
  • DL BWP downlink bandwidth part
  • the BWP configured by the second configuration information is the initial bandwidth part (Initial BWP), for example, the initial uplink bandwidth part (Initial UL BWP) or the initial downlink bandwidth part (Initial DL BWP).
  • the RB set configured in the first configuration information corresponds to the Initial UL
  • the RB set of the BWP is the same as the predefined RB set
  • the RB set configured by the first configuration information corresponds to the initial DL BWP RB set is the same as the predefined RB set.
  • the Initial UL BWP or Initial DL BWP configured by the second configuration information includes one RB set configured by the first configuration information, that is, the first RB of the Initial UL BWP or Initial DL BWP is the RB configured by the first configuration information
  • the starting RB of the set, the last RB of the Initial UL BWP or the Initial DL BWP is the last RB of the RB set configured by the first configuration information. Therefore, for different UEs in the cell, the initial BWP can meet the requirement of including an integer number of RB sets.
  • Figure 14 is a schematic diagram of RB set and Initial BWP predefined in this application.
  • the Initial BWP may be an Initial UL BWP or an Initial DL BWP.
  • the Initial BWP includes one RB set configured by the first configuration information.
  • the RB set configured by the first configuration information is the same as the predefined RB set.
  • an initial UL BWP may also be referred to as a UL BWP configured by initialUplinkBWP
  • an initial DL BWP may also be referred to as a DL BWP configured by initialDownlinkBWP
  • a DL BWP that is not an initial UL BWP may also be referred to as configured by BWP-Uplink UL BWP
  • DL BWP not initial DL BWP can also be called DL BWP configured by BWP-Downlink.
  • the BWP configured by the second configuration information involved in operation 1302 is a bandwidth portion configured with physical random access channel (PRACH) resources.
  • PRACH physical random access channel
  • FIG. 15 is a schematic diagram of a predefined RB set and a UL BWP configured with PRACH resources in this application.
  • the UL BWP is configured with PRACH resources.
  • the UL BWP may include 2 RB sets configured by the first configuration information (that is, RB set 0 and RB set 1 configured by the first configuration information).
  • the RB set configured by the first configuration information is the same as the predefined RB set, that is, the RB set 0 and RB set 1 configured by the first configuration information are respectively the same as the predefined RB set 0 and the predefined RB set 1.
  • FIG. 16 is another schematic diagram of the RB set predefined in this application and the UL BWP configured with PRACH resources.
  • the UL BWP is configured with PRACH resources.
  • the RB set configured by the first configuration information ie, the RB set 0 configured by the first configuration information
  • the RB set configured by the first configuration information is a resource block set corresponding to a physical random access channel (PRACH) resource of the UL BWP.
  • PRACH physical random access channel
  • the first The RB set corresponding to the UL BWP and/or the RB set corresponding to the PRACH resource configured in the configuration information is the same as the predefined RB set.
  • the network device can determine the resources of the BWP, so as to receive or transmit data correctly.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information.
  • the physical random access channel (PRACH) resource may also be a physical random access channel resource not used for contention-free random access (CFRA) based beam failure recovery (BFR), eg, the UL
  • the BWP is configured with rach-ConfigCommon and/or rach-ConfigDedicated.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information; or, the physical random access channel (PRACH) resources can also be physical random access channel resources for contention-based random access (CBRA), eg, the UL BWP is configured with rach-ConfigCommon
  • the other The BWP may include a natural number of RB sets configured by the first configuration information; or, the physical random access channel (PRACH) resource may also be the PRACH resource that the terminal device will receive the RAR after using the PRACH resource to send the PRACH.
  • the other BWPs may include a natural number of RB sets configured by the first configuration information; alternatively, the physical random access channel (PRACH) resource is also a random access channel that the terminal device will receive after using the PRACH resource to send PRACH.
  • DCI downlink control information
  • RA-RNTI incoming wireless network temporary identity
  • the set of resource blocks corresponding to Physical Random Access Channel (PRACH) resources may be used to send downlink control scrambled by Random Access Response (RAR) or Temporary Cell Radio Network Temporary Identity (TC-RNTI)
  • RAR Random Access Response
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • the resource block set of the physical uplink shared channel (PUSCH) scheduled by the information (DCI); alternatively, the resource block set corresponding to the physical random access channel (PRACH) resources may be used to send the random access response (RAR) in the CBRA Or a physical uplink shared channel (PUSCH) resource block set scheduled by downlink control information (DCI) scrambled by a temporary cell radio network temporary identity (TC-RNTI).
  • a second aspect of the embodiments of the present application further provides a method for sending and receiving data.
  • the method for sending and receiving data includes:
  • Operation 1301A receiving first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • Operation 1302A Receive second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, where K is a natural number, wherein, The BWP includes all RBs of the predefined RB set corresponding to the PRACH resource.
  • BWP bandwidth part
  • the terminal device may send or receive data on a part of the bandwidth according to the resource block set configured by the first configuration information.
  • the BWP can be made to meet the requirement of including an integer number of resource block sets (RB sets), or the network device can uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • Embodiments of the third aspect of the present application provide a method for sending and receiving data, which is applied to a network device and corresponds to the embodiments of the first aspect.
  • FIG. 17 is a schematic diagram of a method of an uplink transmission receiving method according to an embodiment of the seventh aspect. As shown in FIG. 17 , the method includes:
  • Operation 1701. Send first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • Operation 1702 Send second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • the resource block set configured by the first configuration information is the same as or different from the predefined resource block set.
  • the carrier is an uplink carrier, and the bandwidth portion is an uplink bandwidth portion; or, the carrier is a downlink carrier, and the bandwidth portion is a downlink bandwidth portion.
  • the bandwidth portion is an initial bandwidth portion, eg, Initial UL BWP or Initial DL BWP.
  • the bandwidth portion is a bandwidth portion configured with Physical Random Access Channel (PRACH) resources.
  • the physical random access channel (PRACH) resource is not a physical random access channel resource used for contention-free random access (CFRA) based beam failure recovery (BFR) triggering; or, the physical random access channel (PRACH) ) resource is the contention-based random access (CBRA) physical random access channel resource; or, the physical random access channel (PRACH) resource is the physical random access channel resource that the terminal device uses to send the physical random access channel resource After accessing the channel, it will receive a physical random access channel (PRACH) resource of a random access response (RAR); or, the physical random access channel (PRACH) resource is the physical random access channel resource that the terminal device uses After the physical random access channel is sent, a physical random access channel (PRACH) resource of downlink control information (DCI) scrambled by a random access radio network temporary identity (RA-RNTI) will be received.
  • DCI downlink control information
  • the method for sending and receiving data further includes:
  • Operation 1703 Receive or send data in a partial bandwidth according to a predefined resource block set or a resource block set configured according to the first configuration information.
  • data sent by the terminal device is received on the UL BWP, or data is sent to the terminal device on the DL BWP.
  • the network receives data according to a predefined set of resource blocks.
  • PUSCH physical uplink shared channel
  • RAR random access response
  • DCI downlink control information
  • TC-RNTI temporary cell radio network temporary identity
  • the received data is Random Access Response (RAR) in Contention Based Random Access (CBRA) or Downlink Control Information (DCI) scrambled by Temporary Cell Radio Network Temporary Identity (TC-RNTI) scheduling
  • RAR Random Access Response
  • CBRA Contention Based Random Access
  • DCI Downlink Control Information
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • PUSCH physical uplink shared channel
  • the BWP can be made to meet the requirement of including an integer number of resource block sets (RB sets), or the network device can uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • Embodiments of the fourth aspect of the present application provide a method for sending and receiving data, which is applied to a network device and corresponds to the embodiments of the second aspect.
  • FIG. 18 is a schematic diagram of a method of an uplink transmission receiving method according to an embodiment of the seventh aspect. As shown in FIG. 18 , the method includes:
  • Operation 1801. Send first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • Operation 1802 Send second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, where K is a natural number.
  • BWP bandwidth part
  • the resource block set corresponding to the bandwidth part (BWP) configured in the second configuration information and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined
  • the set of resource blocks is the same.
  • the carrier is an uplink carrier, and the bandwidth portion is an uplink bandwidth portion; or, the carrier is a downlink carrier, and the bandwidth portion is a downlink bandwidth portion.
  • the bandwidth portion is an initial bandwidth portion, eg, Initial UL BWP or Initial DL BWP.
  • the bandwidth portion is a bandwidth portion configured with Physical Random Access Channel (PRACH) resources.
  • the physical random access channel (PRACH) resource is not a physical random access channel resource used for contention-free random access (CFRA) based beam failure recovery (BFR) triggering; or, the physical random access channel (PRACH) ) resource is the contention-based random access (CBRA) physical random access channel resource; or, the physical random access channel (PRACH) resource is the physical random access channel resource that the terminal device uses to send the physical random access channel resource After accessing the channel, it will receive a physical random access channel (PRACH) resource of a random access response (RAR); or, the physical random access channel (PRACH) resource is the physical random access channel resource that the terminal device uses After the physical random access channel is sent, a physical random access channel (PRACH) resource of downlink control information (DCI) scrambled by a random access radio network temporary identity (RA-RNTI) will be received.
  • DCI downlink control information
  • the network device receives and sends data according to the RB set configured by the first configuration information.
  • the BWP can be made to meet the requirement of including an integer number of resource block sets (RB sets), or the network device can uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • An embodiment of the present application provides an apparatus for sending and receiving data.
  • the apparatus may be, for example, a terminal device, or may be one or some components or components configured in the terminal device.
  • the apparatus corresponds to an embodiment of the first aspect.
  • FIG. 19 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • the apparatus 1900 for sending and receiving data includes:
  • a first receiving unit 1901 which receives first configuration information, the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • the second receiving unit 1902 receives second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • apparatus 1900 for sending and receiving data further includes:
  • the first transceiving unit 1903 which transmits or receives data in the partial bandwidth according to a predefined resource block set or a resource block set configured according to the first configuration information.
  • the apparatus 1900 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • the apparatus 1900 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • For the specific content of these components or modules reference may be made to the related art.
  • For the specific description of each unit in the apparatus 1900 for sending and receiving data reference may be made to the embodiments of the first aspect.
  • This embodiment of the present application provides another apparatus for sending and receiving data.
  • the apparatus may be, for example, a terminal device, or may be one or some components or components configured in the terminal device.
  • the apparatus corresponds to an embodiment of the second aspect.
  • FIG. 20 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application.
  • the apparatus 2000 for sending and receiving data includes:
  • a third receiving unit 2001 which receives first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • a fourth receiving unit 2002 which receives second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, K is a natural number.
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined resource block set the same.
  • the apparatus 2000 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • the apparatus 2000 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • For the specific contents of these components or modules reference may be made to the related art.
  • For the specific description of each unit in the apparatus 2000 for sending and receiving data reference may be made to the embodiments of the first aspect.
  • the apparatuses 1900 and 2000 for sending and receiving data only exemplarily show the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various bus connections, such as bus connections, may be used. related technologies.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the above embodiments can enable the BWP to meet the requirement of including an integer number of resource block sets (RB sets), or enable the network device to uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • An embodiment of the present application provides an apparatus for sending and receiving data.
  • the apparatus may be, for example, a network device, or may be one or some components or components configured in the network device.
  • the apparatus corresponds to the embodiment of the third aspect.
  • FIG. 21 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application. As shown in FIG. 21 , the apparatus 2100 for sending and receiving data includes:
  • a first sending unit 2101 which sends first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • the second sending unit 2102 sends second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • the apparatus 2100 for sending and receiving data further includes:
  • the second transceiving unit 2103 is configured to receive or transmit data in the partial bandwidth according to the predefined resource block set or the resource block set configured according to the first configuration information.
  • the apparatus 2100 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • the apparatus 2100 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • For the specific content of these components or modules reference may be made to the related art.
  • This embodiment of the present application provides another apparatus for sending and receiving data.
  • the apparatus may be, for example, a network device, or may be one or some components or components configured in the network device.
  • the apparatus corresponds to an embodiment of the second aspect.
  • FIG. 22 is a schematic diagram of an apparatus for sending and receiving data according to an embodiment of the present application. As shown in FIG. 22 , the apparatus 2200 for sending and receiving data includes:
  • a third sending unit 2201 which sends first configuration information, where the first configuration information is used to configure a resource block set (RB set) in a carrier;
  • a fourth sending unit 2202 which sends second configuration information, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, K is a natural number.
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined resource block set the same.
  • the apparatus 2200 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • the apparatus 2200 for sending and receiving data by an uplink transmission apparatus may further include other components or modules.
  • For the specific contents of these components or modules reference may be made to the related art.
  • the apparatuses 2100 and 2200 for sending and receiving data only exemplarily show the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various bus connections, such as bus connections, may be used. related technologies.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the above embodiments can enable the BWP to meet the requirement of including an integer number of resource block sets (RB sets), or enable the network device to uniquely determine which part of the resources to receive the PUSCH.
  • RB sets resource block sets
  • An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same contents as those of the embodiments of the first aspect to the sixth aspect will not be repeated.
  • the communication system 100 may include:
  • the network device 101 which includes the apparatus 2100 or 2200 for transmitting and receiving data according to the embodiment of the sixth aspect;
  • the terminal device 102 includes the apparatus 1900 or 2000 for transmitting and receiving data according to the embodiment of the fifth aspect.
  • the embodiment of the present application also provides a network device, which may be, for example, a base station, but the present application is not limited to this, and may also be other network devices.
  • a network device which may be, for example, a base station, but the present application is not limited to this, and may also be other network devices.
  • FIG. 23 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 2300 may include: a processor 2310 (eg, a central processing unit CPU) and a memory 2320 ; the memory 2020 is coupled to the processor 2310 .
  • the memory 2320 can store various data; in addition, a program 2330 for information processing is also stored, and the program 2330 is executed under the control of the processor 2310 .
  • the processor 2310 may be configured to execute a program to implement the method of transceiving data according to the embodiments of the third to fourth aspects.
  • the processor 2310 may be configured to perform the following control: send configuration information and/or indication information to the terminal device.
  • the processor 2010 may be configured to execute a program to implement the uplink transmission receiving method according to the embodiment of the seventh aspect.
  • the network device 2300 may also include an apparatus 2100 or 2200 for transmitting and receiving data.
  • the network device 2300 may further include: a transceiver 2340, an antenna 2350, etc.; wherein, the functions of the above components are similar to those in the prior art, and are not repeated here. It is worth noting that the network device 2300 does not necessarily include all the components shown in FIG. 23 ; in addition, the network device 2300 may also include components not shown in FIG. 20 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a terminal device, but the present application is not limited to this, and may also be other devices.
  • FIG. 24 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 2400 may include a processor 2410 and a memory 2420 ; the memory 2420 stores data and programs, and is coupled to the processor 2410 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 2410 may be configured to execute a program to implement the method of transceiving data as described in the embodiment of the first or second aspect.
  • the terminal device 2400 may further include: a communication module 2430 , an input unit 2440 , a display 2450 , and a power supply 2460 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 2400 does not necessarily include all the components shown in FIG. 24 , and the above components are not required; in addition, the terminal device 2400 may also include components not shown in FIG. 24 . There is technology.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method for sending and receiving data according to the embodiments of the first to second aspects.
  • An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method for sending and receiving data described in the embodiments of the first to second aspects.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method for sending and receiving data according to the embodiments of the third to fourth aspects.
  • the embodiments of the present application further provide a storage medium storing a computer program, wherein the computer program enables a network device to execute the data sending and receiving methods described in the third to fourth aspects.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • 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, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figures may correspond to either individual software modules of the computer program flow, or may also correspond to individual hardware modules.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • a method for sending and receiving data, applied to a terminal device comprising:
  • Second configuration information is received, where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part (BWP) includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • the resource block set configured by the first configuration information is the same as or different from the predefined resource block set.
  • the method also includes:
  • Data is sent or received in the partial bandwidth according to a predefined resource block set or a resource block set configured according to the first configuration information.
  • the data is a Physical Uplink Shared Channel (PUSCH) scheduled by Downlink Control Information (DCI) scrambled by Random Access Response (RAR) or Temporary Cell Radio Network Temporary Identity (TC-RNTI), and sent according to a predefined set of resource blocks the data.
  • DCI Downlink Control Information
  • RAR Random Access Response
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • the data is a physical uplink shared channel (PUC) scheduled by Random Access Response (RAR) in Contention-Based Random Access (CBRA) or Downlink Control Information (DCI) scrambled by Temporary Cell Radio Network Temporary Identity (TC-RNTI).
  • PUC physical uplink shared channel
  • RAR Random Access Response
  • CBRA Contention-Based Random Access
  • DCI Downlink Control Information
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • a method for sending and receiving data, applied to a terminal device comprising:
  • the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, and K is a natural number;
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured by the first configuration information is the same as the predefined resource block set .
  • the carrier is an uplink carrier, and the bandwidth part is an uplink bandwidth part, or,
  • the carrier is a downlink carrier, and the bandwidth portion is a downlink bandwidth portion.
  • the bandwidth portion is an initial bandwidth portion or a bandwidth portion configured with physical random access channel (PRACH) resources.
  • PRACH physical random access channel
  • the physical random access channel (PRACH) resources are physical random access channel resources that are not used for contention-free random access (CFRA) based beam failure recovery (BFR).
  • PRACH physical random access channel
  • CFRA contention-free random access
  • BFR beam failure recovery
  • the physical random access channel (PRACH) resource is a physical random access channel resource for contention based random access (CBRA).
  • the physical random access channel (PRACH) resource is a physical random access channel (PRACH) on which the terminal device will receive a random access response (RAR) after using the physical random access channel resource to send the physical random access channel. )resource.
  • the physical random access channel (PRACH) resource is the scrambled random access radio network temporary identifier (RA-RNTI) that the terminal device will receive after using the physical random access channel resource to send the physical random access channel.
  • a method for sending and receiving data, applied to a network device comprising:
  • Send second configuration information where the second configuration information is used to configure a bandwidth part (BWP), where the bandwidth part includes K predefined resource block sets, where K is a natural number.
  • BWP bandwidth part
  • the resource block set configured by the first configuration information is the same as or different from the predefined resource block set.
  • the method also includes:
  • Data is received or transmitted in the partial bandwidth according to the predefined resource block set or the resource block set configured according to the first configuration information.
  • the data is a Physical Uplink Shared Channel (PUSCH) scheduled by Downlink Control Information (DCI) scrambled by Random Access Response (RAR) or Temporary Cell Radio Network Temporary Identity (TC-RNTI), received according to a predefined set of resource blocks the data.
  • DCI Downlink Control Information
  • RAR Random Access Response
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • the data is a physical uplink shared channel (PUC) scheduled by Random Access Response (RAR) in Contention-Based Random Access (CBRA) or Downlink Control Information (DCI) scrambled by Temporary Cell Radio Network Temporary Identity (TC-RNTI).
  • PUC physical uplink shared channel
  • RAR Random Access Response
  • CBRA Contention-Based Random Access
  • DCI Downlink Control Information
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • a method for sending and receiving data, applied to a network device comprising:
  • the bandwidth part (BWP) includes K resource block sets configured by the first configuration information, and K is a natural number
  • the resource block set corresponding to the bandwidth part (BWP) and/or the resource block set corresponding to the physical random access channel (PRACH) resource in the resource block set configured in the first configuration information is configured to be the same as the predefined resource block set the same.
  • the carrier is an uplink carrier
  • the bandwidth part is an uplink bandwidth part
  • the carrier is a downlink carrier, and the bandwidth portion is a downlink bandwidth portion.
  • the bandwidth portion is an initial bandwidth portion or a bandwidth portion configured with physical random access channel (PRACH) resources.
  • PRACH physical random access channel
  • the physical random access channel (PRACH) resource is not a physical random access channel resource used for contention-free random access (CFRA) based beam failure recovery (BFR) triggering.
  • CFRA contention-free random access
  • BFR beam failure recovery
  • the physical random access channel (PRACH) resource is a contention based random access (CBRA) physical random access channel resource.
  • PRACH physical random access channel
  • CBRA contention based random access
  • the physical random access channel (PRACH) resource is a physical random access channel (PRACH) that the terminal device will receive a random access response (RAR) after using the physical random access channel resource to send the physical random access channel.
  • PRACH physical random access channel
  • the physical random access channel (PRACH) resource is the scrambled random access radio network temporary identifier (RA-RNTI) that the terminal device will receive after using the physical random access channel resource to send the physical random access channel.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation de la présente demande concernent un procédé et un appareil d'émission-réception de données, ainsi qu'un système de communication. L'appareil d'émission-réception de données est appliqué à un dispositif terminal. L'appareil comprend : une première unité de réception permettant de recevoir des premières informations de configuration, les premières informations de configuration servant à configurer un ensemble de blocs de ressources (ensemble RB) dans un support ; et une seconde unité de réception permettant de recevoir des secondes informations de configuration, les secondes informations de configuration servant à configurer une partie de bande passante (BWP), la BWP comprenant K ensembles RB prédéfinis, K étant un nombre naturel.
PCT/CN2020/119699 2020-09-30 2020-09-30 Procédé et appareil d'émission-réception de données, et système de communication WO2022067783A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119699 WO2022067783A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil d'émission-réception de données, et système de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119699 WO2022067783A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil d'émission-réception de données, et système de communication

Publications (1)

Publication Number Publication Date
WO2022067783A1 true WO2022067783A1 (fr) 2022-04-07

Family

ID=80949477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119699 WO2022067783A1 (fr) 2020-09-30 2020-09-30 Procédé et appareil d'émission-réception de données, et système de communication

Country Status (1)

Country Link
WO (1) WO2022067783A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108882376A (zh) * 2017-11-10 2018-11-23 华为技术有限公司 一种通信方法、装置以及系统
WO2019060676A1 (fr) * 2017-09-21 2019-03-28 Qualcomm Incorporated Calcul d'informations d'état de canal à l'aide d'une hypothèse de ressources de commande
CN110972515A (zh) * 2018-07-31 2020-04-07 Lg电子株式会社 在无线通信系统中监测终端的控制信号的方法及其终端
EP3703300A1 (fr) * 2019-01-11 2020-09-02 LG Electronics Inc. -1- Procédé et dispositif permettant d'effectuer une communication basée sur une bwp en nr v2x

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019060676A1 (fr) * 2017-09-21 2019-03-28 Qualcomm Incorporated Calcul d'informations d'état de canal à l'aide d'une hypothèse de ressources de commande
CN108882376A (zh) * 2017-11-10 2018-11-23 华为技术有限公司 一种通信方法、装置以及系统
CN110972515A (zh) * 2018-07-31 2020-04-07 Lg电子株式会社 在无线通信系统中监测终端的控制信号的方法及其终端
EP3703300A1 (fr) * 2019-01-11 2020-09-02 LG Electronics Inc. -1- Procédé et dispositif permettant d'effectuer une communication basée sur une bwp en nr v2x

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MODERATOR (LG ELECTRONICS): "Summary#2 of email discussion [100b-e-NR-unlic-NRU-WB-01] on RB", 3GPP DRAFT; R1-2002955, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200430, 1 May 2020 (2020-05-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051879531 *

Similar Documents

Publication Publication Date Title
CN111165060B (zh) 随机接入方法、装置以及通信系统
WO2022027521A1 (fr) Procédé et appareil d'envoi et de réception de signaux de liaison montante
WO2020199000A1 (fr) Procédé et appareil d'accès aléatoire
WO2021159510A1 (fr) Procédé et appareil de transmission en liaison montante
WO2020191679A1 (fr) Procédé d'accès aléatoire, dispositif terminal et dispositif de réseau
US20220210777A1 (en) Methods and apparatuses for transmitting and receiving uplink signal
CN111972032B (zh) 随机接入的方法和设备
US20220007396A1 (en) Uplink transmission method, uplink scheduling method, apparatuses thereof and system
JP2024069386A (ja) アップリンク伝送方法及び装置
WO2021203956A1 (fr) Procédé et dispositif de communication
WO2022067519A1 (fr) Procédés et terminaux d'accès aléatoire
WO2022077322A1 (fr) Procédé et appareil d'envoi de signal de référence de sondage, et procédé et appareil de réception de signal de référence de sondage
CN113228807B (zh) 数据发送方法、装置和通信系统
EP3557921A1 (fr) Dispositif et procédé de mutlplexage de données, et système de communication
CN113273115B (zh) 信息发送和接收方法以及装置
WO2020210963A1 (fr) Procédé et dispositif de transmission de message
WO2020029299A1 (fr) Procédé d'indication d'interruption de données et appareil associé, et système de communication
WO2022067783A1 (fr) Procédé et appareil d'émission-réception de données, et système de communication
WO2020206658A1 (fr) Procédé de communication sans fil, équipement terminal et dispositif réseau
WO2022213293A1 (fr) Procédés et appareils pour envoyer et configurer une séquence de préambule d'accès aléatoire
CN112369105A (zh) 随机接入方法，数据接收方法及其装置、通信系统
WO2022027527A1 (fr) Procédé et appareil d'envoi et de réception de signaux, et système de communication
US20240031092A1 (en) Terminal device and network device
US20220225433A1 (en) Wireless communication method, terminal device, and network device
WO2023010368A1 (fr) Procédé et appareil d'émission-réception de signal, et système de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20955806

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20955806

Country of ref document: EP

Kind code of ref document: A1