WO2022002199A1 - Pusch信号的映射方法、终端及网络侧设备 - Google Patents

Pusch信号的映射方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2022002199A1
WO2022002199A1 PCT/CN2021/104005 CN2021104005W WO2022002199A1 WO 2022002199 A1 WO2022002199 A1 WO 2022002199A1 CN 2021104005 W CN2021104005 W CN 2021104005W WO 2022002199 A1 WO2022002199 A1 WO 2022002199A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
pusch
prb
terminal
resource allocation
Prior art date
Application number
PCT/CN2021/104005
Other languages
English (en)
French (fr)
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 CA3187284A priority Critical patent/CA3187284A1/en
Priority to JP2022581345A priority patent/JP7488378B2/ja
Priority to AU2021298712A priority patent/AU2021298712B2/en
Priority to EP21833013.2A priority patent/EP4178291A4/en
Priority to KR1020237003747A priority patent/KR20230035072A/ko
Publication of WO2022002199A1 publication Critical patent/WO2022002199A1/zh
Priority to US18/090,588 priority patent/US20230138775A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • H04W72/1263Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0035Resource allocation in a cooperative multipoint environment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044Arrangements for allocating sub-channels of the transmission path allocation of payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application belongs to the technical field of wireless communication, and in particular relates to a PUSCH signal mapping method, a terminal and a network side device.
  • the Physical Uplink Shared Channel (PUSCH) or the Temporary Cell Temporary Cell is scheduled by the Random Access Response (RAR) uplink (Up Link, UL) grant (grant).
  • Radio Network Temporary Identifier, TC-RNTI Radio Network Temporary Identifier, TC-RNTI) scrambled downlink control information (Downlink Control Information, DCI) format 0-0 PUSCH scheduling, generally use type (type) 1 UL resource allocation (that is, the frequency domain resource allocation type is type 1 UL resource allocation, also known as frequency domain resource allocation type 1).
  • the terminal (UE) determines the allocated virtual resource block (Virtual Resource Block, VRB) resource according to the frequency domain resource allocation indication field (FDRA) in the DCI.
  • VRB Virtual Resource Block
  • the PUSCH signal is first mapped to the VRB, and then mapped from the VRB to the corresponding physical resource block (Physical Resource Block). Block, PRB).
  • the terminal activates (active) the UL carrier bandwidth part (Bandwidth Part, BWP) includes all resource blocks (Resource Block, RB) of the initial (initial) UL BWP, and has the same subcarrier spacing (SCS) and cycle as the initial UL BWP
  • SCS subcarrier spacing
  • CP subcarrier spacing
  • the base station may not know whether the corresponding UE is in the radio resource control (Radio Resource Control, RRC) connected state or the RRC idle state. Knowing whether the UE corresponds to the active UL BWP or the initial UL BWP, in order to avoid blind detection by the base station, the terminal maps the PUSCH to the initial UL BWP.
  • RRC Radio Resource Control
  • the purpose of the embodiments of the present application is to provide a PUSCH signal mapping method, which can solve the problem that the terminal cannot use a corresponding manner to map the PUSCH signal according to different frequency domain resource allocation types.
  • a first aspect provides a method for mapping a physical uplink shared channel (PUSCH) signal, which is applied to a terminal, the method comprising: determining a frequency domain resource allocation type of the terminal and frequency domain resource allocation information of the terminal, determining A target resource block allocated for PUSCH, wherein the target resource block includes a first target VRB or a first target PRB; according to the frequency domain resource allocation type and/or the way the PUSCH is scheduled, it is determined that the PUSCH signal is mapped to A mapping method of the second target PRB, wherein the second target PRB is the first target PRB or a PRB corresponding to the first target VRB; using the mapping method, the PUSCH signal is mapped to the second target PRB Target PRB.
  • PUSCH physical uplink shared channel
  • a device for mapping a PUSCH signal including: a first determining module configured to determine a target resource block allocated for the PUSCH according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal , wherein the target resource block includes a first target VRB or a first target PRB; a second determination module is configured to determine, according to the frequency domain resource allocation type and/or the way the PUSCH is scheduled, that the PUSCH signal is mapped to A second target PRB mapping method, wherein the second target PRB is the first target PRB or a PRB corresponding to the first target VRB; a mapping module, configured to use the mapping method to map the PUSCH signal to the second target PRB.
  • a method for receiving a PUSCH signal is provided, which is applied to a network side device.
  • the method includes: according to a frequency domain resource allocation type configured for the terminal and the indicated frequency domain resource allocation information, determining a PUSCH for the terminal.
  • the allocated PRB; the PUSCH signal transmitted by the terminal is received on the PRB.
  • a device for receiving a PUSCH signal comprising: a third determining module configured to determine a PUSCH allocation for the terminal according to the frequency domain resource allocation type configured for the terminal and the indicated frequency domain resource allocation information The PRB; a receiving module, configured to receive the PUSCH signal transmitted by the terminal on the PRB.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a network side device in a sixth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the third aspect when executed.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect, or the The steps of the method described in the third aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running a terminal device program or instruction, and the implementation is as described in the first aspect method, or the processor is used to run a network side device program or instruction to implement the method described in the third aspect.
  • the target VRB or target PRB allocated for the PUSCH is determined according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal, and then according to the frequency domain resource allocation type and/or the PUSCH
  • the mapping mode in which the PUSCH signal is mapped to the target PRB is determined, and the PUSCH signal is mapped to the target PRB by using the mapping mode. Therefore, the terminal can map the PUSCH signal in a corresponding manner according to different frequency domain resource allocation types, so that the base station can effectively detect the PUSCH signal sent by the terminal and improve the effectiveness of the communication system.
  • FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied
  • FIG. 2 shows a schematic flowchart of a method for mapping a PUSCH signal provided by an embodiment of the present application
  • FIG. 3a shows a schematic diagram of RB set division in an embodiment of the present application
  • FIG. 3b shows a schematic diagram of RB set division in an embodiment of the present application
  • FIG. 4 shows another schematic diagram of RB set division in an embodiment of the present application
  • FIG. 5 shows a schematic structural diagram of an apparatus for mapping a PUSCH signal provided by an embodiment of the present application
  • FIG. 6 shows a schematic flowchart of a method for receiving a PUSCH signal provided by an embodiment of the present application
  • FIG. 7 shows a schematic structural diagram of an apparatus for receiving a PUSCH signal provided by an embodiment of the present application
  • FIG. 8 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 shows a schematic diagram of a hardware structure of a terminal provided by an embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a hardware structure of a network side device provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR new air interface
  • NR sixth generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of this application, only the NR system is used. The base station in the example is taken as an example, but the specific type of the base station is not limited.
  • FIG. 2 shows a schematic flowchart of a method for mapping a PUSCH signal provided by an embodiment of the present application, and the method 200 may be executed by a terminal.
  • the method may be performed by software or hardware installed on the terminal.
  • the method may include the following steps.
  • S210 Determine a target resource block allocated for the PUSCH according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal, where the target resource block includes a first target VRB or a first target PRB.
  • the determined target resource block may be a VRB or a PRB.
  • the terminal can determine the target PRB according to the frequency domain resource allocation information, and when the domain resource allocation type is Type 0/1 UL resource allocation, the terminal can determine the target PRB according to the frequency domain resource allocation information.
  • the resource allocation information determines the target VRB.
  • the PUSCH may be scheduled by a RAR UL grant (grant), or the PUSCH may also be scheduled by a preset downlink control information format (for example, DCI 0_0) scrambled by TC-RNTI, Alternatively, the PUSCH may also be scheduled in other ways, for example, scheduled by DCI 0_1, or scheduled by DCI 0_0 scrambled by C-RNTI, etc.
  • S212 Determine, according to the frequency domain resource allocation type and/or the manner in which the PUSCH is scheduled, a mapping manner for mapping the PUSCH signal to a second target PRB, where the second target PRB is the first target PRB or A PRB corresponding to the first target VRB.
  • the second target PRB is the first target PRB
  • the first target VRB is determined in S210
  • the second target PRB is the same as the first target VRB the corresponding PRB.
  • mapping manner map the PUSCH signal to the second target PRB.
  • the PUSCH signal is mapped to the second target PRB by using the mapping method.
  • the target VRB or target PRB allocated for the PUSCH is determined according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal, and then according to the frequency domain resource allocation type and/or the PUSCH
  • the mapping mode in which the PUSCH signal is mapped to the target PRB is determined, and the PUSCH signal is mapped to the target PRB by using the mapping mode. Therefore, the terminal can map the PUSCH signal in a corresponding manner according to different frequency domain resource allocation types, so that the base station can effectively detect the PUSCH signal sent by the terminal and improve the effectiveness of the communication system.
  • the UE can determine the VRB allocated by the PUSCH in the low frequency band within the active UL BWP according to the FDRA indication information , that is, FDRA starts from the first RB of the active UL BWP and the maximum number of RBs is equal to the number of RBs of the initial UL BWP. Then, the mapping of VRB to PRB can ensure that the PUSCH is transmitted within the initial UL BWP.
  • the UE when the UE operates in an unlicensed frequency band, it may be configured to use type 2 uplink resource allocation.
  • the UE determines the RB set allocated by the PUSCH according to the RB set where the PRACH is located, and the corresponding RB may already correspond to the initial UL BWP.
  • the UE can configure (N RB-set -1) intra-cell guard bandwidths (intra-cellguardband) of the carrier through the parameters intraCellGuardBandUL-r16 or intraCellGuardBandDL-r16.
  • each intra-cellguardband is defined as the initial common resource block (common resource block, CRB) and the number of CRBs, that is and
  • CRB common resource block
  • the intra-cell guard bands divide the carrier into N RB-set RB-sets (RB sets), each RB set is defined by the start CRB and the end CRB, namely and The UE determines the start and end CRB indices of each RB set according to the following methods:
  • N RB-set -1)th RB set: in is the CRB index at the beginning of the carrier, is the total number of RBs contained in the carrier, and the corresponding links are identified by different subscripts x as DL or UL;
  • the UE determines the corresponding subcarrier spacing (SCS) ⁇ and the carrier size according to the corresponding predefined nominal intracellguardband and RB patterns (nominal intra-cell guard band and RB set pattern) determine the CRB index (if any) corresponding to the intracellguardband.
  • SCS subcarrier spacing
  • the UE determines the corresponding subcarrier spacing (SCS) ⁇ and the carrier size according to the Under the predefined nominal intra-cellguardband and RB modes determine the CRB index (if any) corresponding to the intra-cellguardband.
  • SCS subcarrier spacing
  • BWP i For a carrier, there are For BWP i, use the parameter BWP-DownlinkCommon or BWP-DownlinkDedicated to configure DL BWP, or use BWP-UplinkCommon or BWP-UplinkDedicated to configure UL BWP. Among them, 0 ⁇ s0 ⁇ s1 ⁇ N RB-set, x -1. Within BWP i, RB set goes from 0 to Numbered in ascending order, where Indicates the number of RB sets included in BWP i, RB set 0 of BWP i corresponds to RB set s0 of carrier, and RB set of BWP i Corresponds to the RB set s1 of the carrier.
  • the carrier when the bandwidth of a carrier is 40MHz and the SCS is 30kHz, the carrier contains 106 RBs and 5 interlaces in total, assuming that the corresponding CRB numbers are 0, 1, ..., 105 respectively.
  • the initial UL BWP corresponds to the first RB set of the carrier, namely RB set 0.
  • UE1 works on the initial UL BWP
  • UE 2 works on the active UL BWP.
  • the active UL BWP contains two RB sets. Since the intra-cellguardband can be configured for each UE (that is, per UE), UE1 and UE2 may be configured with different intra-cellguardbands on the carrier.
  • UE 1 works on the initial UL BWP (the initial UL BWP ranges from CRB0 to CRB49, which is equivalent to the RB set 0 of the carrier when the intra-cellguardband is configured as CRB 50 to CRB 55).
  • the intra-cellguardband configured by UE 2 is 0, that is, there is no intra-cellguardband between RB set 0 and RB set 1.
  • the initial UL BWP (RB set 0 of the carrier, here is also the RB set 0 of the initial UL BWP) only contains 50 available RBs, while for UE 2, the RB set 0 of the carrier, here is also the active UL BWP
  • the RB set 0 of RB set 0 contains 53 RBs.
  • the number of RBs corresponding to UE1 and UE2 is different.
  • the index of the CRB corresponding to UE1 RB set 0 interlace 0 includes 0, 5, 10, 15,20,...,40,45.
  • the indices of the CRB corresponding to UE2 RB set 0 interlace 0 include 0, 5, 10, 15, 20,..., 40, 45, 50. It can be found that the CRB corresponding to RB set 0 interlace 0 of UE 2 has one more CRB corresponding to RB set 0 interlace 0 of UE 1.
  • the base station When the PRACH resources of UE 1 and UE 2 are both configured in the physical resource location corresponding to the initial UL BWP (that is, on the carrier's RB set 0), if the base station receives PRACH at this location, the base station sends a RAR UL grant to schedule the UE in this RB.
  • the PUSCH is transmitted in the set, but the base station cannot judge whether it is the PRACH sent by UE1 or UE2. Therefore, the base station cannot know the value of the intra-cellguardband corresponding to the PUSCH, and therefore cannot judge whether the scheduled PUSCH is in the CRB 0,5,10,15 ,20,...,40,45 or 0,5,10,15,20,...,40,45,50.
  • the same problem also exists for DCI 0_0 scrambled by TC-RNTI.
  • UE1 and UE2 both work on the active UL BWP, but since the intra-cellguardband can be configured for each UE separately, the intra-cellguardband of UE1 and UE2 may be different.
  • the intra-cell guardband of UE 1 is configured as CRB 50 ⁇ CRB 55
  • the intra-cell guardband of UE 2 is configured as 0, that is, there is no intra-cell guardband between RB set 0 and RB set 1.
  • the base station sends a RAR UL grant after receiving the PRACH to schedule the UE to transmit PUSCH in the RB set, but the base station cannot judge It is the PRACH sent by UE1 or UE2, therefore, the value of intra-cellguardband corresponding to the PUSCH cannot be known.
  • DCI 0_0 scrambled by TC-RNTI the same problem also exists for DCI 0_0 scrambled by TC-RNTI.
  • S210 may include: when the frequency domain resource allocation type is Type 2 UL resource allocation, and the PUSCH is scheduled by the RAR UL grant or the PUSCH When scheduled by the preset downlink control information format scrambled by TC-RNTI, determine the common resource block (CRB) range of the target RB set, where the target RB set is the RB set allocated by the PUSCH; The CRB range and the frequency domain resource allocation information are used to determine the first target PRB allocated for the PUSCH.
  • CRB common resource block
  • the resource allocation type in the frequency domain is Type 2 UL resource allocation
  • the PUSCH is scheduled by the RAR UL grant or the PUSCH is scrambled by the TC-RNTI
  • the CRB range of the target RB set is first determined, and then the first target RPB allocated for the PUSCH is determined according to the CRB range of the target RB set and frequency domain resource allocation information. For example, after determining the CRB range of the target RB set, the intersection of the interval indicated by the frequency domain resource allocation information and the target RB set is taken to determine the CRB or PRB allocated for the PUSCH (ie, the first target PRB).
  • the first target VRB allocated for the PUSCH may be determined according to the frequency domain resource allocation information. If the frequency domain resource allocation type is configured as the type 2 UL resource allocation method, but the PUSCH is scheduled in a form other than the RAR UL grant and the preset downlink control information scrambled by the TC-RNTI, then in S210, it can be scheduled according to The frequency domain resource allocation information and the RB set determined by the intra-cellguardband configured by the UE are determined as the first target PRB allocated by the PUSCH.
  • the CRB range of the target RB set when determining the CRB range of the target RB set, may be determined according to the first RB set division manner. That is, in this possible implementation manner, the UE determines the CRB range of the target RB set according to the first RB set division manner.
  • the first RB set division mode on the carrier may also be determined according to the nominal intra-cell guard bandwidth and the RB set mode of the carrier. That is, in this possible implementation, the UE determines the first RB set division mode on the carrier according to the nominal intra-cell guard band (nominal intra-cell guard band) and the RB set mode defined by the protocol.
  • the CRB range of the target RB set when determining the CRB range of the target RB set, if the activated UL BWP satisfies the first condition and the second condition, the CRB range of the target RB set is determined according to the first RB set division manner;
  • the first condition is that the activated UL BWP includes all RBs in the initial UL BWP
  • the second condition is that the activated UL BWP and the initial UL BWP have the same subcarrier spacing (SCS) and Cyclic prefix (CP); if the activated UL BWP does not satisfy the first condition and/or the second condition, the CRB range of the resource blocks of the target RB set is determined according to the second RB set division manner.
  • SCS subcarrier spacing
  • CP Cyclic prefix
  • the division manner of the second RB set on the carrier may also be determined according to the intra-cell guard bandwidth configured for the terminal.
  • the range of the RB set where the PUSCH is located is the RRB corresponding to the initial UL BWP
  • the range is the same (that is, the division of the RB set is determined according to the nominal intra-cell guard bandwidth and the RB set mode), otherwise, the PRB range corresponding to the RB set where the PUSCH is located is determined according to the RB set determined by the intra-cell guardband configured by the UE. It should be noted that, if the UE is not configured with intra-cell guardband at this time, the UE can also be determined according to the nominal intra-cell guardband and the RB set determined by the RB set mode.
  • the terminal can determine that the mapping method of the PUSCH signal to the second target PRB can be directly mapped to the second target PRB, or it can also be mapped first.
  • UE 1 works on the initial UL BWP (corresponding to the position of the RB set 1 of the carrier or UE2's active UL BWP)
  • UE 2 works on the active UL BWP
  • the active UL BWP of UE 2 includes the initial UL All RBs of the BWP, and have the same SCS and CP as the initial UL BWP.
  • the UE After the UE determines the VRB allocated by the PUSCH, it determines the corresponding PRB according to the mapping from VRB to PRB.
  • a non-interleaving mapping manner is used for mapping.
  • For non-interleaved mapping for RAR UL grant or TC-RNTI scrambled DCI format 0_0 scheduling in active BWP i (starting RB index is ), if the active UL BWP includes the initial UL BWP (the starting CRB index is ) and have the same SCS and CP length as the initial UL BWP, VRB n is mapped to Besides, VRB n is mapped to PRB n.
  • UE 2 sends PRACH on RB set 1
  • the base station sends a RAR UL grant to schedule UE to transmit PUSCH after receiving it. Since the RB set where the PUSCH is located is the same as the RB set where the PRACH is located, UE 2 will determine the corresponding The PUSCH is allocated RB set1. If the frequency domain resource allocation type of UE2 is type 2 UL resource allocation, UE2 determines the interlace index of PUSCH allocation according to the FDRA indication in the RAR UL grant, and determines the allocated CRB/PRB according to RB set 0 (for example, in FIG.
  • UE 2 sends PRACH on RB set1, and the base station RAR UL grant instructs to allocate interlace 0.
  • the intra-cell guard band is CRB 50 ⁇ 55
  • the CRB corresponding to interlace 0 on RB set 1 is 60,65,....,,105 ), according to the corresponding relationship:
  • S212 may include the following steps 1-3.
  • Step 1 Determine the index value of the second target VRB allocated for the PUSCH according to the frequency domain resource allocation type of the terminal.
  • the terminal is configured to use the interleaved PUSCH or is configured to use the type 2 UL resource allocation mode, it is determined that the index value of the second target VRB is equal to the index value of the first target PRB determined in S210.
  • the first target PRB is determined by the interlace index M allocated by PUSCH and the RB set allocated for PUSCH, for example, according to the intersection of the RB corresponding to the allocated interlace, the RB corresponding to the set of the allocated RB set and the intra cell guard band to determine the allocated RB, or, when an RB set is allocated, according to the intersection of the RB corresponding to the allocated interlace and the RB corresponding to the allocated RB set, that is, the CRB range of the RB set allocated for the PUSCH is determined, and the determined CRB range is combined with the interlace.
  • the corresponding CRBs are intersected to determine the RBs (CRBs or PRBs, where the PRBs can be determined according to the CRBs) allocated for the PUSCH.
  • VRB index PRB index.
  • PRB index PRB index
  • the second target VRB is determined to be the first target VRB. That is, the second target VRB is determined according to the frequency domain resource allocation information of the UE.
  • Step 2 After multiplying the PUSCH signal by an amplitude scaling factor, it is mapped to the second target VRB.
  • Power control of the PUSCH signal may be facilitated by multiplying the PUSCH signal by an amplitude scaling factor.
  • Step 3 if the PUSCH is scheduled by the RAR UL grant or the PUSCH is scheduled by the preset downlink control information format scrambled by TC-RNTI, then according to whether the terminal is configured to use the interleaved PUSCH or is configured For type 2 UL resource allocation, a mapping manner for mapping the PUSCH signal from the second target VRB to the second target PRB is determined.
  • whether the terminal is configured to use the interlaced PUSCH can be determined by whether the terminal is configured with high-level signaling, such as the useInterlacePUCCH-PUSCH-Common parameter. If this parameter is configured, it indicates that the terminal is configured to use the interlaced PUSCH. Not configured to use interleaved PUSCH.
  • the terminal is configured to use the interlaced PUSCH, which can be determined by the terminal is configured with high-level signaling, such as the useInterlacePUCCH-PUSCH-Common parameter. If this parameter is configured, it indicates that the terminal is configured to use the interlaced PUSCH. parameter, which can also indicate that the terminal is configured for Type 2 UL resource allocation.
  • the PUSCH is not scheduled by the RAR UL grant and is not scheduled by the preset downlink control information format scrambled by the TC-RNTI, then it can be used regardless of whether the UE is in the type 0/1 resource allocation method or the type 2 resource allocation method.
  • the mapping method of the PUSCH signal from the second target VRB to the second target PRB is from VRB n to PRB n.
  • the PUSCH signal is mapped from the second target VRB to the second target PRB in a non-interleaved manner, if the terminal is not configured to use the interleaved PUSCH or is not configured to type 2 UL Resource allocation method, wherein, if the activated ULBWP includes all RBs in the initial UL BWP and has the same subcarrier spacing SCS and cyclic prefix CP as the initial UL BWP, then the nth second target VRB is mapped to the the second target PRBs, wherein is the index of the CRB starting with the initial UL BWP, is the index of the CRB starting from the activated UL BWP, n is an integer greater than or equal to 0; if the activated ULBWP includes all RBs in the initial UL BWP and has the same subcarrier spacing SCS and cyclic prefix CP as the initial UL BWP, then the nth second target VRB is mapped to the the second target PRB
  • the nth second target VRB is mapped to the nth second target PRB in the manner of mapping the The PUSCH signal is mapped from the second target VRB to the second target PRB, which can avoid exceeding the size of the UE's active UL BWP when mapping from the VRB to the PRB, or in some cases, the PUSCH is mapped in the non-initial UL BWP, which leads to the problem that the base station cannot detect or detect incomplete PUSCH signals.
  • S212 when determining a mapping manner for mapping the PUSCH signal to the second target PRB, S212 may further include: if the terminal is configured to use interleaved PUSCH or is configured as type 2 UL resources allocation, then the mapping mode is determined to be the second mapping mode, otherwise, the mapping mode is determined to be the first mapping mode, wherein the first mapping mode is to first map the PUSCH signal to the VRB, and then map the PUSCH signal from the VRB to the VRB. Mapping to PRBs, the second mapping manner is to directly map the PUSCH signal to PRBs.
  • the mapping method is determined to directly map the PUSCH signal to the PRB determined in S210, otherwise, the mapping method is determined to be The PUSCH signal is mapped to the VRB, and then mapped from the VRB to the PRB, that is, the mapping is performed according to the mapping method of type 0/1 UL resource allocation.
  • the mapping manner is the second mapping manner, then in S214, the PUSCH signal is multiplied by an amplitude scaling factor, and then mapped to the determined first target PRB.
  • the UE determines the resource mapping mode of the PUSCH according to whether the useInterlace PUCCH-PUSCH-Common is configured or whether the type 2 UL resource allocation (resourceallocation) is configured, which improves the effectiveness of the communication system.
  • the execution subject of the PUSCH signal mapping method provided by the embodiments of the present application may be a PUSCH signal mapping apparatus, or a control module in the PUSCH signal mapping apparatus for executing the PUSCH signal mapping method.
  • the method for mapping a PUSCH signal performed by a device for mapping a PUSCH signal is used as an example to describe the device for mapping a PUSCH signal provided in the embodiment of the present application.
  • FIG. 5 shows a schematic structural diagram of a PUSCH signal mapping apparatus provided by the present application.
  • the PUSCH signal mapping apparatus 500 mainly includes: a first determination module 501 , a second determination module 502 and a mapping module 503.
  • the first determining module 501 is configured to determine a target resource block allocated for the PUSCH according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal, wherein the target resource block includes the first resource block. a target virtual resource block VRB or a first target physical resource block PRB; a second determination module 502, configured to determine that the PUSCH signal is mapped to the second target according to the frequency domain resource allocation type and/or the way the PUSCH is scheduled A mapping method of PRBs, wherein the second target PRB is the first target PRB or a PRB corresponding to the first target VRB; the mapping module 503 is configured to use the mapping method to map the PUSCH signal to the Describe the second target PRB.
  • the first determining module 501 determines the target resource block allocated for the PUSCH according to the frequency domain resource allocation type of the terminal and the frequency domain resource allocation information of the terminal, including: if the The frequency domain resource allocation type is Type 2 UL resource allocation, and the PUSCH is scheduled by the random access response RAR uplink UL grant or the PUSCH is a preset scrambled by the temporary cell wireless network temporary identifier TC-RNTI In the downlink control information format scheduling, determine the common resource block CRB range of the target resource block RB set, where the target RB set is the RB set allocated by the PUSCH; according to the CRB range and the frequency domain resource allocation information, The first target PRB allocated for the PUSCH is determined.
  • the first determining module 501 determines the common resource block CRB range of the target resource block RB set, including: determining the CRB range of the target RB set according to the first RB set division manner.
  • the first determining module 501 is further configured to, before determining the CRB range of the target RB set according to the first RB set division method, determine the nominal intra-cell guard bandwidth and the RBs of the carrier according to the nominal intra-cell guard bandwidth.
  • Set mode which determines the division mode of the first RB set on the carrier.
  • the determining module determines the common resource block CRB range of the target resource block RB set, including: if the activated UL carrier bandwidth part BWP satisfies the first condition and the second condition, according to the first RB Set division method, determine the CRB range of the target RB set; wherein, the first condition is that the activated UL BWP includes all RBs in the initial UL BWP, and the second condition is that the activated UL BWP and all RBs
  • the initial UL BWP has the same subcarrier spacing SCS and cyclic prefix CP; if the activated UL BWP does not meet the first condition and/or the second condition, the target RB set is determined according to the second RB set division method The CRB range of the resource block.
  • the first determining module 501 is further configured to, before determining the CRB range of the resource blocks of the target RB set according to the second RB set division manner, according to The guard bandwidth is to determine the division mode of the second RB set on the carrier.
  • the second determining module 502 determines a mapping manner for mapping the PUSCH signal to the second target PRB according to the frequency domain resource allocation type of the terminal and/or the manner in which the PUSCH is scheduled , including: determining the index value of the second target VRB allocated for the PUSCH according to the frequency domain resource allocation type of the terminal; after multiplying the PUSCH signal by the amplitude scaling factor, mapping the PUSCH signal to the second target VRB; if the If the PUSCH is scheduled by the RAR UL grant or the PUSCH is scheduled by the preset downlink control information format scrambled by TC-RNTI, then according to whether the terminal is configured to use the interleaved PUSCH or whether it is configured as a type 2 UL resource Allocation, determining a mapping manner for mapping the PUSCH signal from the second target VRB to the second target PRB.
  • the second determining module 502 determines the index value of the second target VRB allocated for the PUSCH according to the frequency domain resource allocation type of the terminal, including: if the terminal is configured to use the interleaved PUSCH Or is configured as Type 2 UL resource allocation mode, then determine that the index value of the second target VRB is equal to the determined index value of the first target PRB; if the terminal is not configured to use interleaved PUSCH or is not configured as Type 2 UL resource allocation method, the second target VRB is determined to be the first target VRB.
  • the second determining module 502 determines to send the PUSCH signal from the second target VRB to the second target VRB according to whether the terminal is configured to use the interleaved PUSCH or is configured to use the type 2 UL resource allocation manner
  • the mapping mode mapped to the second target PRB includes:
  • the nth second target VRB is mapped to the the second target PRBs, wherein is the index of the CRB starting with the initial UL BWP, is the index of the CRB started by the activated UL BWP, and n is an integer greater than or equal to 0; if one or more of the first target condition, the second target condition and the third target condition are not met, the The nth second target VRB is mapped to the nth second target PRB; wherein, the first target condition is: the terminal is not configured to use interleaved PUSCH or is not configured for type 2 UL resource allocation
  • the second target condition is: the activated ULBWP includes all RBs in the initial UL BWP; the third target condition is: the activated UL BWP and the initial UL BWP have the same subcarrier spacing SCS and cyclic prefix CP .
  • the second determining module 502 determines a mapping manner for mapping the PUSCH signal to the second target PRB according to the frequency domain resource allocation type and/or the manner in which the PUSCH is scheduled, including: if If the terminal is configured to use the interleaved PUSCH or is configured for type 2 UL resource allocation, the mapping mode is determined to be the second mapping mode, otherwise, the mapping mode is determined to be the first mapping mode, wherein the first mapping mode The method is to first map the PUSCH signal to the virtual resource block VRB, and then map the PUSCH signal from the VRB to the PRB, and the second mapping method is to directly map the PUSCH signal to the PRB.
  • the mapping module 503 uses the mapping manner to map the PUSCH signal to the second target PRB, including: if the mapping manner is the second mapping manner, mapping the PUSCH signal to the second target PRB After being multiplied by the amplitude scaling factor, it is mapped to the determined first target PRB.
  • the apparatus for mapping a PUSCH signal in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the apparatus for mapping the PUSCH signal in the embodiment of the present application may be an apparatus having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the PUSCH signal mapping apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiments in FIG. 2 to FIG. 4 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 6 shows a schematic flowchart of a method for receiving a PUSCH signal provided by an embodiment of the present application, and the method 600 may be executed by a network side device.
  • the method can be executed by software or hardware installed on the network side device.
  • the method may include the following steps.
  • the network side device may determine the PRB allocated for the PUSCH of the terminal in the same manner as the terminal.
  • S610 may include: when the frequency domain resource allocation type is Type 2 UL resource allocation, and the PUSCH is scheduled by the RAR UL grant or the PUSCH is added by the TC-RNTI When scheduling the preset downlink control information format for scrambled, determine the CRB range of the target resource block RB set, where the target RB set is the RB set allocated by the PUSCH; according to the CRB range and the frequency domain resource allocation information to determine the PRB allocated for the PUSCH.
  • determining the common resource block CRB range of the target resource block RB set may include: determining the CRB range of the resource blocks of the target RB set according to the first RB set division manner. For details, reference may be made to the relevant description in the foregoing S210, which is not repeated here.
  • the method before determining the CRB range of the target RB set according to the first RB set division manner, the method further includes: determining the first RB set on the carrier according to the nominal intra-cell guard bandwidth and the RB set mode of the carrier.
  • An RB set division method before determining the CRB range of the target RB set according to the first RB set division manner, the method further includes: determining the first RB set on the carrier according to the nominal intra-cell guard bandwidth and the RB set mode of the carrier.
  • determining the common resource block CRB range of the target resource block RB set may also include: if the activated UL carrier bandwidth part BWP satisfies the first condition and the second condition, then according to the first RB set
  • the division method is to determine the CRB range of the resource blocks of the target RB set; wherein, the first condition is that the activated UL BWP includes all RBs in the initial UL BWP, and the second condition is that the activated UL BWP Have the same subcarrier spacing SCS and cyclic prefix CP as the initial UL BWP; if the activated UL BWP does not meet the first condition and/or the second condition, determine the target according to the second RB set division method The CRB range of the resource blocks of the RB set.
  • the method before determining the CRB range of the resource blocks of the target RB set according to the second RB set division manner, the method further includes: determining the second RB set according to an intra-cell guard bandwidth configured for the terminal. RB set division method.
  • S612 Receive the PUSCH signal transmitted by the terminal on the PRB.
  • the network side equipment after determining the PRB allocated to the terminal, the network side equipment (including but not limited to the base station) can detect the PUSCH signal on the PRB, which avoids the need for the network side equipment to blindly detect the PUSCH signal, and improves the Accuracy of PUSCH signal detection.
  • the main body of execution may be a device for receiving a PUSCH signal, or a control module for executing a method for receiving a PUSCH signal in the device for receiving a PUSCH signal.
  • a method for receiving a PUSCH signal performed by a device for receiving a PUSCH signal is used as an example to describe the device for receiving a PUSCH signal provided by the embodiment of the present application.
  • FIG. 7 shows a schematic structural diagram of a PUSCH signal receiving apparatus provided by the present application.
  • the PUSCH signal mapping apparatus 700 mainly includes: a third determining module 701 and a receiving module 702 .
  • the third determining module 701 is configured to determine the PRB allocated for the PUSCH of the terminal according to the frequency domain resource allocation type configured for the terminal and the indicated frequency domain resource allocation information; the receiving module 702 is configured to use receiving the PUSCH signal transmitted on the terminal on the PRB.
  • the third determining module 701 determines the PRB allocated for the PUSCH of the terminal according to the frequency domain resource allocation type configured for the terminal and the indicated frequency domain resource allocation information, including: when the The frequency domain resource allocation type is Type 2 UL resource allocation, and the PUSCH is scheduled by the random access response RAR uplink UL grant or the PUSCH is a preset scrambled by the temporary cell wireless network temporary identifier TC-RNTI When the downlink control information format is scheduled, determine the common resource block CRB range of the target resource block RB set, where the target RB set is the RB set allocated by the PUSCH; according to the CRB range and the frequency domain resource allocation information , determine the PRB allocated for the PUSCH.
  • the third determining module 701 determines the common resource block CRB range of the target resource block RB set, including: determining the CRB range of the resource blocks of the target RB set according to the first RB set division manner .
  • the third determining module 701 is further configured to, before determining the CRB range of the target RB set according to the first RB set division manner, according to the nominal intra-cell guard bandwidth and the RB of the carrier Set mode, which determines the division mode of the first RB set on the carrier.
  • the third determining module 701 determines the common resource block CRB range of the resource blocks of the target resource block RB set, including: if the activated UL carrier bandwidth part BWP satisfies the first condition and the second condition, then Determine the CRB range of the resource blocks of the target RB set according to the first RB set division; wherein, the first condition is that the activated UL BWP includes all RBs in the initial UL BWP, and the second The condition is that the activated UL BWP and the initial UL BWP have the same subcarrier spacing SCS and cyclic prefix CP; if the activated UL BWP does not meet the first condition and/or the second condition, according to the second RB set
  • the division mode is to determine the CRB range of the resource blocks of the target RB set.
  • the third determining module 701 is further configured to, before determining the CRB range of the resource blocks of the target RB set according to the second RB set division manner, according to the intra-cell configured for the terminal The protection bandwidth is determined, and the division mode of the second RB set is determined.
  • the apparatus for receiving a PUSCH signal in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network-side device.
  • the apparatus may be a base station.
  • a base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Transmitting Receiving Point (TRP) or any Other suitable terms in the field are not specifically limited in the embodiments of the present application.
  • BSS Basic Service Set
  • ESS Extended Service Set
  • eNB Evolved Node B
  • TRP Transmitting Receiving Point
  • the apparatus for receiving a PUSCH signal in this embodiment of the present application may be an apparatus having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for receiving a PUSCH signal provided by the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 6 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 800, including a processor 801, a memory 802, a program or instruction stored in the memory 802 and executable on the processor 801,
  • a communication device 800 including a processor 801, a memory 802, a program or instruction stored in the memory 802 and executable on the processor 801,
  • the communication device 800 is a terminal
  • the program or instruction is executed by the processor 801
  • each process of the foregoing PUSCH signal mapping method embodiment can be implemented, and the same technical effect can be achieved.
  • the communication device 800 is a network-side device, when the program or instruction is executed by the processor 801, each process of the above-mentioned PUSCH signal receiving method embodiment can be realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • FIG. 9 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processor 910 and other components .
  • the terminal 900 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 910 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 9 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 904 may include a graphics processor (Graphics Processing Unit, GPU) 9041 and a microphone 9042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 907 includes a touch panel 9071 and other input devices 9072.
  • the touch panel 9071 is also called a touch screen.
  • the touch panel 9071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 901 receives the downlink data from the network side device, and then processes it to the processor 910; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 909 may be used to store software programs or instructions as well as various data.
  • the memory 909 may mainly include a storage program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 909 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM) ), erasable programmable read-only memory (ErasablePROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • ErasablePROM ErasablePROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 910 may include one or more processing units; optionally, the processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 910.
  • the processor 910 is configured to perform the following method steps:
  • the target resource block includes a first target virtual resource block VRB or a first target physical resource block. resource block PRB;
  • the mapping method of the PUSCH signal to the second target PRB where the second target PRB is the first target PRB or the same as the first target PRB. Describe the PRB corresponding to the first target VRB;
  • the PUSCH signal is mapped to the second target PRB.
  • the target VRB or target PRB allocated for the PUSCH is determined, and then the mapping method for mapping the PUSCH signal to the target PRB is determined, and the mapping is adopted.
  • the PUSCH signal is mapped to the target PRB. Therefore, the terminal can map the PUSCH signal in a corresponding manner according to different frequency domain resource allocation types, so that the base station can effectively detect the PUSCH signal sent by the terminal and improve the effectiveness of the communication system.
  • the network device 1000 includes: an antenna 1001 , a radio frequency device 1002 , and a baseband device 1003 .
  • the antenna 1001 is connected to the radio frequency device 1002 .
  • the radio frequency device 1002 receives information through the antenna 1001, and sends the received information to the baseband device 1003 for processing.
  • the baseband device 1003 processes the information to be sent and sends it to the radio frequency device 1002
  • the radio frequency device 1002 processes the received information and sends it out through the antenna 1001 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 1003 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 1003 .
  • the baseband apparatus 1003 includes a processor 1004 and a memory 1005 .
  • the baseband device 1003 may include, for example, at least one baseband board on which multiple chips are disposed, as shown in FIG. 10 , one of the chips is, for example, the processor 1004 , which is connected to the memory 1005 to call a program in the memory 1005 to execute
  • the network device shown in the above embodiment of the method for receiving a PUSHC signal operates.
  • the baseband device 1003 may further include a network interface 106 for exchanging information with the radio frequency device 1002, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: instructions or programs stored in the memory 1005 and executable on the processor 1004, and the processor 1004 invokes the instructions or programs in the memory 1005 to execute the modules shown in FIG. 7 .
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned PUSHC signal mapping method or PUSHC signal receiving method embodiment is implemented and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned PUSHC signal.
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network-side device program or instruction to implement the above-mentioned PUSHC signal.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Stereo-Broadcasting Methods (AREA)
  • Stereophonic System (AREA)
  • Circuits Of Receivers In General (AREA)

Abstract

本申请公开了一种PUSCH信号的映射方法、终端及网络侧设备。该PUSCH信号的映射方法包括:根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标VRB或第一目标PRB;根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。

Description

PUSCH信号的映射方法、终端及网络侧设备
交叉引用
本发明要求在2020年07月02日在中国提交的申请号为202010634269.0、发明名称为“PUSCH信号的映射方法、终端及网络侧设备”的中国专利申请的优先权,该申请的全部内容通过引用结合在本发明中。
技术领域
本申请属于无线通信技术领域,具体涉及一种PUSCH信号的映射方法、终端及网络侧设备。
背景技术
目前,随机接入响应(Random Access Response,RAR)上行链路(Up Link,UL)授权(grant)调度的物理上行共享信道(Physical Uplink Shared Channel,PUSCH)或临时小区无线网络临时标识(Temporary Cell Radio Network Temporary Identifier,TC-RNTI)加扰的下行控制信息(Downlink Control Information,DCI)格式0-0调度的PUSCH,一般都采用类型(type)1 UL资源分配(即频域资源分配类型为类型1 UL资源分配,也称为频域资源分配类型1)。终端(UE)根据DCI中的频域资源分配指示域(FDRA)确定分配的虚拟资源块(VirtualResource Block,VRB)资源,PUSCH信号先映射到VRB,再从VRB映射到对应的物理资源块(PhysicalResource Block,PRB)。当终端激活(active)UL载波带宽部分(Bandwidth Part,BWP)包含初始(initial)UL BWP的所有资源块(Resource Block,RB),并与initial UL BWP具有相同的子载波间隔(SCS)及循环前缀(Cyclic Prefix,CP)时,需要通 VRB到PRB的映射使得PUSCH调度在初始BWP内。因为当基站发送RAR UL grant或TC-RNTI加扰的DCI格式0-0时,基站可能不知道对应的UE是在无线资源控制(Radio Resource Control,RRC)连接状态还是RRC空闲状态,因此,不知道UE对应的是active UL BWP还是initial UL BWP,为了避免基站盲检,终端将PUSCH都映射在initial UL BWP内。
在相关技术中,对于RAR UL grant调度的PUSCH或TC-RNTI加扰的DCI格式0-0调度的PUSCH,只给出采用上行资源分配类型1进行资源分配。如果网络侧为终端配置类型(type)2 UL资源分配(即频域资源分配类型2),则终端无法根据不同的频域资源分配类型采用对应的方式进行PUSCH信号的映射,进而可能导致网络侧检测不到PUSCH信号。
发明内容
本申请实施例的目的是提供一种PUSCH信号的映射方法,能够解决终端无法根据不同的频域资源分配类型采用对应的方式进行PUSCH信号的映射的问题。
为了解决上述技术问题,本申请是这样实现的:
第一方面,提供了一种物理上行共享信道(PUSCH)信号的映射方法,应用于终端,该方法包括:根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标VRB或第一目标PRB;根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
第二方面,提供了一种PUSCH信号的映射装置,包括:第一确定模块,用于根据终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标VRB或第 一目标PRB;第二确定模块,用于根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;映射模块,用于采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
第三方面,提供了一种PUSCH信号的接收方法,应用于网络侧设备,该方法包括:根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB;在所述PRB上接收所述终端上传输的PUSCH信号。
第四方面,提供了一种PUSCH信号的接收装置,包括:第三确定模块,用于根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB;接收模块,用于在所述PRB上接收所述终端上传输的PUSCH信号。
第五方面,提供了一种终端,该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种网络侧设备,该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第七方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
第八方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行终端设备程序或指令,实现如第一方面所述的方法,或所述处理器用于运行网络侧设备程序或指令,实现如第三方面所述的方法。
在本申请实施例中,根据终端的频域资源分配类型和终端的频域资源分配信息,确定为PUSCH分配的目标VRB或目标PRB,再根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到目标PRB的映射方式,采用该映射方式,将PUSCH信号映射到目标PRB。从而可以使得终端可以根据不同的频域资源分配类型,采用相应的方式进行PUSCH信号的映射,进而使得基站可以有效地检测到终端发送的PUSCH信号,提高通信系统的有效性。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的框图;
图2示出本申请实施例提供的PUSCH信号的映射方法的一种流程示意图;
图3a示出本申请实施例中一种RB集划分示意图;
图3b示出本申请实施例中一种RB集划分示意图;
图4示出本申请实施例中又一种RB集划分示意图;
图5示出本申请实施例提供的PUSCH信号的映射装置的一种结构示意图;
图6示出本申请实施例提供的PUSCH信号的接收方法的一种流程示意图;
图7示出本申请实施例提供的PUSCH信号的接收装置的一种结构示意图;
图8示出本申请实施例提供的一种通信设备的结构示意图;
图9示出本申请实施例提供的一种终端的硬件结构示意图;
图10示出本申请实施例提供的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,还可用于其他无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。然而,以下描述出于示例目的描述了新空口(NewRadio,NR)系统,并且在以下大部分描述中使用NR术语,这些技术也可应用于NR系统应用以外的应用,如第6代(6 thGeneration,6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系 统包括终端11和网络侧设备12。其中,终端11也可以称作终端设备或者用户终端(User Equipment,UE),终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备,可穿戴式设备包括:手环、耳机、眼镜等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网,其中,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(TransmittingReceivingPoint,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例,但是并不限定基站的具体类型。
下面结合附图,通过具体的实施例及其应用场景对本申请实施例提供的PUSCH信号的映射方法进行详细地说明。
图2示出本申请实施例提供的PUSCH信号的映射方法的一种流程示意图,该方法200可以由终端执行。换言之,所述方法可以由安装在终端上的软件或硬件来执行。如图2所示,该方法可以包括以下步骤。
S210,根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标VRB或第一目标PRB。
也就是说,在本申请中,在S210中,确定的目标资源块可以是VRB也可以是PRB。例如,当频域资源分配类型为类型2 UL资源分配时,终端可 以根据频域资源分配信息确定出目标PRB,而当域资源分配类型为类型0/1 UL资源分配时,终端可以根据频域资源分配信息确定出目标VRB。
在本申请中,所述PUSCH可以是由RAR UL授权(grant)调度的,或者,所述PUSCH也可以是由TC-RNTI加扰的预设下行控制信息格式(例如,DCI 0_0)调度的,或者,PUSCH也可以是由其它方式调度的,例如,由DCI 0_1调度的,或者由C-RNTI加扰的DCI 0_0调度的等。
S212,根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB。
在本申请中,如果S210中确定的为第一目标PRB,则第二目标PRB即为第一目标PRB,如果S210中确定的为第一目标VRB,则第二目标PRB为与第一目标VRB对应的PRB。
S214,采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
在S214中,在确定映射方式之后,采用该映射方式,将PUSCH信号映射到第二目标PRB上。
在本申请实施例中,根据终端的频域资源分配类型和终端的频域资源分配信息,确定为PUSCH分配的目标VRB或目标PRB,再根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到目标PRB的映射方式,采用该映射方式,将PUSCH信号映射到目标PRB。从而可以使得终端可以根据不同的频域资源分配类型,采用相应的方式进行PUSCH信号的映射,进而使得基站可以有效地检测到终端发送的PUSCH信号,提高通信系统的有效性。
在实际应用中,对于频域资源分配类型1,例如,对于TC-RNTI加扰的DCI 0_0调度的PUSCH,UE可以根据FDRA指示信息在激活(active)UL BWP内的低频段确定PUSCH分配的VRB,即FDRA从active UL BWP的第一个RB开始且最大RB数等于initial UL BWP的RB数。然后,通过VRB到PRB 的映射可以确保PUSCH在initial UL BWP内传输。但是当UE工作在非授权频段中,可能配置使用type 2上行资源分配。对于频域资源分配类型2,UE根据PRACH所在的RB set确定PUSCH分配的RB set,对应的RB可能已经在对应initial UL BWP。
当UE工作在非授权频段,即共享频谱信道接入时,UE可以通过参数intraCellGuardBandUL-r16或intraCellGuardBandDL-r16配置载波(carrier)的(N RB-set-1)个小区内保护带宽(intra-cellguardband)(可以等于0,即没有intra-cellguardband),每一个intra-cellguardband定义为起始公共资源块(common resource block,CRB)和CRB数目,即
Figure PCTCN2021104005-appb-000001
Figure PCTCN2021104005-appb-000002
intra-cell guard bands将carrier划分N RB-set个RB-sets(RB集),每一个RB集通过起始CRB和结束CRB定义,即
Figure PCTCN2021104005-appb-000003
Figure PCTCN2021104005-appb-000004
UE根据以下方式确定每个RB set的起始和结束CRB索引:
对于第一个RB set:
Figure PCTCN2021104005-appb-000005
第(N RB-set-1)个RB set:
Figure PCTCN2021104005-appb-000006
其中,
Figure PCTCN2021104005-appb-000007
为载波起始的CRB索引,
Figure PCTCN2021104005-appb-000008
为载波包含的RB总数,通过不同的下标x标识对应的链路是为DL或UL;
对于其余的RB set:
Figure PCTCN2021104005-appb-000009
以及
Figure PCTCN2021104005-appb-000010
Figure PCTCN2021104005-appb-000011
当UE没有配置intraCellGuardBandUL-r16时,UE根据对应子载波间隔(Subcarrier Spacing,SCS)μ和载波大小
Figure PCTCN2021104005-appb-000012
下预定义的名义的intracellguardband和RB模式(nominal intra-cell guard band and RB set pattern)确定对应intracellguardband的CRB索引(如果有)。
当UE没有配置intraCellGuardBandDL-r16时,UE根据对应子载波间隔(Subcarrier Spacing,SCS)μ和载波大小
Figure PCTCN2021104005-appb-000013
下预定义的名义的intra-cellguardband和RB模式确定对应intra-cellguardband的CRB索引(如 果有)。
对于DL和/或UL,如果预定义的名义的intra-cellguardband和RB模式不包含intra-cellguardband,则carrier的RB set数为1,即N RB-set,x=1。
对于一个carrier,有
Figure PCTCN2021104005-appb-000014
Figure PCTCN2021104005-appb-000015
其中对于BWP i,使用参数BWP-DownlinkCommon或者BWP-DownlinkDedicated配置DL BWP,或者,使用BWP-UplinkCommon或者或者BWP-UplinkDedicated配置UL BWP。其中,0≤s0≤s1≤N RB-set,x-1。在BWP i内,RB set从0到
Figure PCTCN2021104005-appb-000016
按照升序编号,其中
Figure PCTCN2021104005-appb-000017
表示BWP i包含的RB set数,BWP i的RB set 0对应于carrier的RB set s0,BWP i的RB set
Figure PCTCN2021104005-appb-000018
对应于carrier的RB set s1。
例如,在图3a中,一个carrier带宽为40MHz,SCS为30kHz时,carrier中共包含106个RB,5个交织(interlace),假设对应的CRB编号为分别0,1,…,105。初始UL BWP对应于carrier的第一个RB set,即RB set 0,UE1工作在初始UL BWP上,UE 2工作在active UL BWP上,其active UL BWP包含两个RB set。由于intra-cellguardband可以是针对每个UE(即per UE)配置的,因此,UE1和UE2在该carrier上可能配置不同的intra-cellguardband。例如,在图3a中UE 1工作在initial UL BWP上(initial UL BWP的范围为CRB0~CRB49,相当于intra-cellguardband配置为CRB 50~CRB 55时候的carrier的RB set 0)。而UE 2配置的intra-cellguardband为0,即RB set 0和RB set 1之间没有intra-cellguardband。因此,对于UE 1,初始UL BWP(carrier的RB set 0,这里也是initial UL BWP的RB set 0)只包含了50个可用RB,而对于UE 2,carrier的RB set 0,这里也是active UL BWP的RB set 0,则包含了53个RB,同样对于RB set 0的interlace 0,UE1和UE2对应的RB数则不同,例如UE1 RB set 0 interlace 0对应的CRB的索引包括0,5,10,15,20,…,40,45。而UE2 RB set 0 interlace 0对应的CRB的索引包括0,5,10,15,20,…,40,45,50。可以发现UE 2的RB set 0 interlace 0对应的CRB对UE  1的RB set 0 interlace 0对应的CRB多一个。
当UE 1和UE 2的PRACH资源都配置在初始UL BWP对应的物理资源位置(即carrier的RB set 0上)时,如果基站在该位置接收到PRACH,基站发送RAR UL grant调度UE在该RB set内传输PUSCH,但是基站无法判断是UE1还是UE2发送的PRACH,因此,基站不能获知该PUSCH对应的intra-cellguardband的值,进而将无法判断其调度的PUSCH是在CRB 0,5,10,15,20,…,40,45上发送还是在0,5,10,15,20,…,40,45,50上发送。而对于TC-RNTI加扰的DCI 0_0也同样存在这样的问题。
又如,在图3b中,UE1和UE2均工作在active UL BWP上,但是由于intra-cellguardband可以是每个UE分别配置的,因此UE 1和UE2的intra-cellguardband可能不同。如图3b所示,UE 1的intra-cell guard band配置为CRB 50~CRB 55,UE 2的intra-cellguardband配置为0,即RB set 0和RB set 1之间没有intra-cellguardband。因此,当UE 1和UE2同时在RB set 0或同时在RB set 1上配置了PRACH资源时,基站在接收到PRACH后发送RAR UL grant调度UE在该RB set内传输PUSCH,但是,基站无法判断是UE1还是UE2发送的PRACH,因此,不能获知该PUSCH对应的intra-cellguardband的值,例如PUSCH分配的是interlace 0时,无法判断其调度的PUSCH是在CRB 0,5,10,15,20,…,40,45上发送还是在0,5,10,15,20,…,40,45,50上发送。而对于TC-RNTI加扰的DCI 0_0也同样存在这样的问题。
为了解决该问题,在本申请实施例的一个可能的实现方式中,S210可以包括:当频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的时,确定目标RB集的公共资源块(CRB)范围,其中,所述目标RB集为所述PUSCH分配的RB集;再根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的所述第一目标PRB。也就是说,在该可 选的实现方式中,在频域资源分配类型为类型2 UL资源分配方式,且所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的时,先确定目标RB集的CRB范围,再根据目标RB集的CRB范围以及频域资源分配信息确定为PUSCH分配的第一目标RPB。例如,在确定目标RB集的CRB范围后,取频域资源分配信息指示的interlace与目标RB集的交集,确定为PUSCH分配的CRB或PRB(即第一目标PRB)。
在上述可能的实现方式中,如果频域资源分配类型未被配置为类型2 UL资源分配方式,则在S210中可以根据频域资源分配信息确定为PUSCH分配的第一目标VRB。若频域资源分配类型被配置为类型2 UL资源分配方式,但所述PUSCH是采用RAR UL授权以及TC-RNTI加扰的预设下行控制信息之外其它形式调度的,则在S210中可以根据频域资源分配信息以及UE被配置的intra-cellguardband确定的RB set确定为PUSCH分配的第一目标PRB。
在上述可能的实现方式中,在一个可能的实现方式中,在确定目标RB集的CRB范围时,可以根据第一RB集划分方式,确定目标RB集的CRB范围。即在该可能的实现方式中,UE根据第一RB集划分方式,确定目标RB集的CRB范围。
在上述可能的实现方式中,在确定目标RB集的CRB范围之前,还可以根据名义的小区内保护带宽以及载波的RB集模式,确定载波上的第一RB集划分方式。即在该可能的实现方式中,UE根据协议定义的名义的小区内保护带宽(nominal intra-cell guard band)和RB集模式,来确定载波上的第一RB集划分方式。
在另一个可能的实现方式,在确定目标RB集的CRB范围时,若激活UL BWP满足第一条件和第二条件,则根据第一RB集划分方式,确定所述目标RB集的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL  BWP具有相同的子载波间隔(SCS)及循环前缀(CP);若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
在上述可能的实现方式中,在确定目标RB集的CRB范围之前,还可以根据为所述终端配置的小区内保护带宽,确定载波上的所述第二RB集划分方式。
也就是说,在该可能的实现方式中,当active UL BWP包含initial UL BWP的所有RB,并与initial UL BWP具有相同的SCS及CP时,PUSCH所在RB set的范围与initial UL BWP对应的RRB范围相同(即按照名义的小区内保护带宽和RB集模式确定RB set的划分),否则,PUSCH所在RB set对应的PRB范围根据UE被配置的intra-cell guardband确定的RB set确定。需要说明的是,如果此时UE没有被配置intra-cell guardband,也可以UE根据名义的小区内保护带宽和RB集模式确定的RB set确定。
在实际应用中,当频域资源分配类型为类型2 UL资源分配时,终端可以确定PUSCH信号映射到第二目标PRB的映射方式可以为直接映射到第二目标PRB,或者,也可以采用先映射到VRB再映射到PRB的映射方式,由于UE根据资源分配信息确定的是CRB或PRB,如果按照现有方式进行映射,可能会导致PUSCH的物理资源偏离UE的初始UL BWP。
例如,在图4中,UE 1工作在initial UL BWP上(对应carrier或UE2active UL BWP的RB set 1的位置),UE 2工作在active UL BWP上,且UE 2的active UL BWP包含了initial UL BWP的所有RB,且与initial UL BWP具有相同的SCS及CP。
UE确定PUSCH分配的VRB后,根据VRB到PRB的映射确定对应的PRB。按照相关技术中的规定,采用非交织的映射方式进行映射。对于非交织的映射,对于RAR UL grant或TC-RNTI加扰的DCI格式0_0调度的在active BWP i(起始RB索引为
Figure PCTCN2021104005-appb-000019
)上传输的PUSCH,如果active UL BWP 包括了initial UL BWP(起始CRB索引为
Figure PCTCN2021104005-appb-000020
)的所有RB,且和initial UL BWP具有相同的SCS和CP长度时,VRB n映射到
Figure PCTCN2021104005-appb-000021
除此之外,VRB n映射到PRB n。
例如,图4中,如果UE 2在RB set 1上发送PRACH,基站接收到之后发送RAR UL grant调度UE传输PUSCH,由于PUSCH所在的RB set与PRACH所在RB set相同,因此,UE 2将确定对应的PUSCH分配的是RB set1。如果UE2的频域资源分配类型为类型2 UL资源分配,则UE 2根据RAR UL grant中的FDRA指示确定PUSCH分配的interlace索引,并根据RB set 0确定分配的CRB/PRB(例如,图4中UE 2在RB set1上发送PRACH,基站RAR UL grant指示分配interlace 0,假设intra-cell guard band为CRB 50~55,则RB set 1上interlace 0对应的CRB为60,65,….,,105),可以根据对应关系:
Figure PCTCN2021104005-appb-000022
确定对应的PRB为60,65,….,,105,其中,
Figure PCTCN2021104005-appb-000023
为所述激活UL BWP起始的CRB的索引,且
Figure PCTCN2021104005-appb-000024
),然后确定对应VRB(PRB n对应VRB n),最后将信号映射在VRB上,并根据VRB到PRB的映射规则映射至PRB。如果按照上述的规则,由于active UL BWP包含initial UL BWP的所有RB,并与initial UL BWP具有相同的SCS及CP,因此,UE 1将VRB n映射至
Figure PCTCN2021104005-appb-000025
其中
Figure PCTCN2021104005-appb-000026
则VRB 55将映射至PRB 55+56=111,而111大于UE的active UL BWP的大小。因此,上述VRB到PRB的映射规则并不适用于类型2上行资源分配。
因此,在本申请的一个可能的实现方式中,S212可以包括以下步骤1-步骤3。
步骤1,根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值。
可选地,若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资 源分配方式,则确定所述第二目标VRB的索引值等于S210中确定的所述第一目标PRB的索引值。其中,第一目标PRB通过PUSCH分配的interlace索引M和为PUSCH分配的RB set确定,例如,根据分配interlace对应的RB、与分配RB set和intra cell guard band的合集对应的RB的交集确定分配的RB,或者,当分配的是一个RB set时,根据分配的interlace对应的RB与分配的RB set对应的RB的交集,即确定为PUSCH分配的RB set的CRB范围,将确定的CRB范围与interlace对应的CRB取交集,确定为PUSCH分配的RB(CRB或者PRB,其中PRB可以根据CRB确定)。
然后确定VRB索引=PRB索引。例如,在图4中,假设UE2分配的是RB set 1以及interlace 0,则对应的VRB索引为60,65,70,…,100,105。
若所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式,则确定所述第二目标VRB为所述第一目标VRB。即根据UE的频域资源分配信息确定第二目标VRB。
步骤2,将所述PUSCH信号乘以幅度缩放因子后,映射到与所述第二目标VRB。
通过将所述PUSCH信号乘以幅度缩放因子,可以利于PUSCH信号的功率控制。
步骤3,若所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的,则根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式。
其中,所述终端是否被配置使用交织PUSCH可以通过该终端是否被配置高层信令,如useInterlacePUCCH-PUSCH-Common参数来确定,如果被配置该参数,则指示终端被配置使用交织PUSCH,否则指示终端未被配置使用交织PUSCH。
另外,所述终端被配置使用交织PUSCH可以通过该终端被配置高层信令,如useInterlacePUCCH-PUSCH-Common参数来确定,如果被配置该参数, 则指示终端被配置使用交织PUSCH,同时如果被配置该参数,也可以表示终端被配置为类型2 UL资源分配。
其中,可选地,若PUSCH不是由RAR UL授权调度且也不是由TC-RNTI加扰的预设下行控制信息格式调度的,则可以不论UE是类型0/1资源分配方式还是类型2资源分配方式,PUSCH信号从第二目标VRB映射到第二目标PRB的映射方式为从VRB n映射到PRB n。
在一个可能的实现方式中,根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配方式,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式时,按照非交织的方式将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB,若所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式,其中,若激活ULBWP包含了初始UL BWP中的所有RB,且与初始UL BWP具有相同的子载波间隔SCS及循环前缀CP,则第n个所述第二目标VRB映射到第
Figure PCTCN2021104005-appb-000027
个所述第二目标PRB,其中
Figure PCTCN2021104005-appb-000028
为所述初始UL BWP起始的CRB的索引,
Figure PCTCN2021104005-appb-000029
为所述激活UL BWP起始的CRB的索引,n为大于或等于0的整数;若激活ULBWP未包含初始UL BWP中的所有RB,和/或,激活UL BWP与初始UL BWP不具有相同的SCS和/或CP,则第n个所述第二目标VRB映射到第n个所述第二目标PRB;若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则按照第n个所述第二目标VRB映射到第n个所述第二目标PRB的方式将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB。
通过上述可能的实现方式,如果终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则按照第n个所述第二目标VRB映射到第n个所述第二目标PRB的方式将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB,可以避免从VRB映射到PRB时,超过UE的active UL BWP的大小,或者在某些情况下,PUSCH映射在非initial UL BWP上,从而导致基站检测不到或检测不全PUSCH信号的问题。
在另一个可能的实现方式中,在S212中,在确定PUSCH信号映射到第二目标PRB的映射方式时,S212还可以包括:若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则确定所述映射方式为第二映射方式,否则,确定所述映射方式为第一映射方式,其中,所述第一映射方式为先将PUSCH信号映射到VRB,再将PUSCH信号从VRB映射到PRB,所述第二映射方式为将所述PUSCH信号直接映射到PRB。即在该可能的实现方式中,若终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则确定映射方式为直接将PUSCH信号映射到S210确定的PRB上,否则,确定映射方式为将PUSCH信号映射到VRB,再从VRB映射到PRB,即按照类型0/1 UL资源分配的映射方式进行映射。
在上述可能实现方式中,所述映射方式为第二映射方式,则在S214中,将所述PUSCH信号乘以幅度缩放因子后,映射到确定的所述第一目标PRB。
通过本申请提供的上述技术方案,当不同UE共享相同的RACH资源时,避免了因不同UE配置的intra-cellguardband不同,造成基站盲检PUSCH的问题。另外,UE根据是否被配置useInterlace PUCCH-PUSCH-Common或者是否被配置type 2 UL资源分配(resourceallocation),确定PUSCH的资源映射方式,提高了通信系统的有效性。
需要说明的是,本申请实施例提供的PUSCH信号的映射方法,执行主体可以为PUSCH信号的映射装置,或者,该PUSCH信号的映射装置中的用于执行PUSCH信号的映射方法的控制模块。本申请实施例中以PUSCH信号的映射装置执行PUSCH信号的映射的方法为例,说明本申请实施例提供的PUSCH信号的映射装置。
图5示出了本申请提供的PUSCH信号的映射装置的一种结构示意图,如图5所示,该PUSCH信号的映射装置500主要包括:第一确定模块501、第二确定模块502和映射模块503。
在本申请中,第一确定模块501,用于根据终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中, 所述目标资源块包括第一目标虚拟资源块VRB或第一目标物理资源块PRB;第二确定模块502,用于根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;映射模块503,用于采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
在一个可能的实现方式中,所述第一确定模块501根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,包括:若所述频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由随机接入响应RAR上行链路UL授权调度的或者所述PUSCH是由临时小区无线网络临时标识TC-RNTI加扰的预设下行控制信息格式调度的,确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的所述第一目标PRB。
在一个可能的实现方式中,所述第一确定模块501确定目标资源块RB集的公共资源块CRB范围,包括:根据第一RB集划分方式,确定所述目标RB集的CRB范围。
在一个可能的实现方式中,所述第一确定模块501还用于在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
在一个可能的实现方式中,所述确定模块确定目标资源块RB集的公共资源块CRB范围,包括:若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
在一个可能的实现方式中,所述第一确定模块501还用于在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,根据为所述终端配置的小区内保护带宽,确定载波上的所述第二RB集划分方式。
在一个可能的实现方式中,所述第二确定模块502根据所述终端的频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到所述第二目标PRB的映射方式,包括:根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值;将所述PUSCH信号乘以幅度缩放因子后,映射到所述第二目标VRB;若所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的,则根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式。
在一个可能的实现方式中,所述第二确定模块502根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值,包括:若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配方式,则确定所述第二目标VRB的索引值等于确定的所述第一目标PRB的索引值;若所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式,则确定所述第二目标VRB为所述第一目标VRB。
在一个可能的实现方式中,所述第二确定模块502根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配方式,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式,包括:
若同时符合第一目标条件、第二目标条件以及第三目标条件,则将第n个所述第二目标VRB映射到第
Figure PCTCN2021104005-appb-000030
个所述第二目标PRB,其中
Figure PCTCN2021104005-appb-000031
为所述初始UL BWP起始的CRB的索引,
Figure PCTCN2021104005-appb-000032
为所述激活UL BWP起始的CRB的索引,n为大于或等于0的整数;若不符合所述第一目标条件、第二目标条件以及第三目标条件中的一个或多个,则将第n个所述 第二目标VRB映射到第n个所述第二目标PRB;其中,所述第一目标条件为:所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式;所述第二目标条件为:激活ULBWP包含了初始UL BWP中的所有RB;所述第三目标条件为:所述激活UL BWP与初始UL BWP具有相同的子载波间隔SCS及循环前缀CP。
在一个可能的实现方式中,所述第二确定模块502根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,包括:若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则确定所述映射方式为第二映射方式,否则,确定所述映射方式为第一映射方式,其中,所述第一映射方式为先将PUSCH信号映射到虚拟资源块VRB,再将PUSCH信号从VRB映射到PRB,所述第二映射方式为将所述PUSCH信号直接映射到PRB。
在一个可能的实现方式中,所述映射模块503采用所述映射方式,将PUSCH信号映射到所述第二目标PRB,包括:若所述映射方式为第二映射方式,则将所述PUSCH信号乘以幅度缩放因子后,映射到确定的所述第一目标PRB。
本申请实施例中的PUSCH信号的映射装置可以是装置,也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端,也可以为非移动终端。示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例中的PUSCH信号的映射装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
本申请实施例提供的PUSCH信号的映射装置能够实现图2至图4的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再 赘述。
图6示出了本申请实施例提供的一种PUSCH信号的接收方法的一种流程示意图,该方法600可以由网络侧设备执行。换言之,所述方法可以由安装在网络侧设备上的软件或硬件来执行。如图6所示,该方法可以包括以下步骤。
S610,根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB。
在具体应用中,网络侧设备可以采用与终端相同的方式,确定为终端的PUSCH分配的PRB。
例如,在一个可能的实现方式中,S610可以包括:当所述频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的时,确定目标资源块RB集的CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的PRB。
其中,在上述可能的实现方式中,确定目标资源块RB集的公共资源块CRB范围可以包括:根据第一RB集划分方式,确定所述目标RB集的资源块的CRB范围。具体可以参见上述S210中的相关描述,在此不再赘述。
可选地,在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,所述方法还包括:根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
其中,在上述可能的实现方式中,确定目标资源块RB集的公共资源块CRB范围也可以包括:若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的资源块的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;若激活UL BWP不满足所述第一条件和/ 或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
可选地,在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,所述方法还包括:根据为所述终端配置的小区内保护带宽,确定所述第二RB集划分方式。
具体方式可以参见方法200中S210的相关描述,在此不再赘述。
S612,在所述PRB上接收所述终端上传输的PUSCH信号。
在本申请提供的技术方案中,在确定为终端分配的PRB之后,网络侧设备(包括但不限于基站)可以在该PRB上检测PUSCH信号,避免了网络侧设备需要盲检PUSCH信号,提高了PUSCH信号检测的准确性。
需要说明的是,本申请实施例提供的PUSCH信号的接收方法,执行主体可以为PUSCH信号的接收装置,或者,该PUSCH信号的接收装置中的用于执行PUSCH信号的接收方法的控制模块。本申请实施例中以PUSCH信号的接收装置执行PUSCH信号的接收方法为例,说明本申请实施例提供的PUSCH信号的接收装置。
图7示出了本申请提供的PUSCH信号的接收装置的一种结构示意图,如图7所示,该PUSCH信号的映射装置700主要包括:第三确定模块701和接收模块702。
在本申请实施例中,第三确定模块701,用于根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB;接收模块702,用于在所述PRB上接收所述终端上传输的PUSCH信号。
在一个可能的实现方式中,所述第三确定模块701根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB,包括:当所述频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由随机接入响应RAR上行链路UL授权调度的或者所述PUSCH是由临时小区无线网络临时标识TC-RNTI加扰的预设下行控制信息格式调度 的时,确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的PRB。
在一个可能的实现方式中,所述第三确定模块701确定目标资源块RB集的公共资源块CRB范围,包括:根据第一RB集划分方式,确定所述目标RB集的资源块的CRB范围。
在一个可能的实现方式中,所述第三确定模块701还用于在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
在一个可能的实现方式中,所述第三确定模块701确定目标资源块RB集的资源块的公共资源块CRB范围,包括:若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的资源块的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
在一个可能的实现方式中,所述第三确定模块701还用于在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,根据为所述终端配置的小区内保护带宽,确定所述第二RB集划分方式。
本申请实施例中的PUSCH信号的接收装置可以是装置,也可以是网络侧设备中的部件、集成电路、或芯片。该装置可以是基站。示例性的,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(TransmittingReceivingPoint,TRP)或所述领域中其他某个合适的术语,本 申请实施例不作具体限定。
本申请实施例中的PUSCH信号的接收装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
本申请实施例提供的PUSCH信号的接收装置能够实现图6的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
可选的,如图8所示,本申请实施例还提供一种通信设备800,包括处理器801,存储器802,存储在存储器802上并可在所述处理器801上运行的程序或指令,例如,该通信设备800为终端时,该程序或指令被处理器801执行时实现上述PUSCH信号的映射方法实施例的各个过程,且能达到相同的技术效果。该通信设备800为网络侧设备时,该程序或指令被处理器801执行时实现上述PUSCH信号的接收方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
图9为实现本申请实施例的一种终端的硬件结构示意图。
该终端900包括但不限于:射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909、以及处理器910等部件。
本领域技术人员可以理解,终端900还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理系统与处理器910逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图9中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元904可以包括图形处理器(Graphics Processing Unit,GPU)9041和麦克风9042,图形处理器9041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元906可包括显示面板9061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板9061。用户输入单 元907包括触控面板9071以及其他输入设备9072。触控面板9071,也称为触摸屏。触控面板9071可包括触摸检测装置和触摸控制器两个部分。其他输入设备9072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元901将来自网络侧设备的下行数据接收后,给处理器910处理;另外,将上行的数据发送给网络侧设备。通常,射频单元901包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器909可用于存储软件程序或指令以及各种数据。存储器909可主要包括存储程序或指令区和存储数据区,其中,存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器909可以包括高速随机存取存储器,还可以包括非易失性存储器,其中,非易失性存储器可以是只读存储器(Read-OnlyMemory,ROM)、可编程只读存储器(ProgrammableROM,PROM)、可擦除可编程只读存储器(ErasablePROM,EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM,EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器910可包括一个或多个处理单元;可选的,处理器910可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序或指令等,调制解调处理器主要处理无线通信,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器910中。
其中,处理器910,用于执行以下方法步骤:
根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标虚拟资源块VRB或第一目标物理资源块PRB;
根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为 所述第一目标PRB或与所述第一目标VRB对应的PRB;
采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
在本申请实施例中,根据终端的频域资源分配类型和终端的频域资源分配信息,确定为PUSCH分配的目标VRB或目标PRB,再确定PUSCH信号映射到目标PRB的映射方式,采用该映射方式,将PUSCH信号映射到目标PRB。从而可以使得终端可以根据不同的频域资源分配类型,采用相应的方式进行PUSCH信号的映射,进而使得基站可以有效地检测到终端发送的PUSCH信号,提高通信系统的有效性。
具体地,本申请实施例还提供了一种网络侧设备。如图10所示,该网络设备1000包括:天线1001、射频装置1002、基带装置1003。天线1001与射频装置1002连接。在上行方向上,射频装置1002通过天线1001接收信息,将接收的信息发送给基带装置1003进行处理。在下行方向上,基带装置1003对要发送的信息进行处理,并发送给射频装置1002,射频装置1002对收到的信息进行处理后经过天线1001发送出去。
上述频带处理装置可以位于基带装置1003中,以上实施例中网络侧设备执行的方法可以在基带装置1003中实现,该基带装置1003包括处理器1004和存储器1005。
基带装置1003例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图10所示,其中一个芯片例如为处理器1004,与存储器1005连接,以调用存储器1005中的程序,执行以上PUSHC信号的接收方法实施例中所示的网络设备操作。
该基带装置1003还可以包括网络接口106,用于与射频装置1002交互信息,该接口例如为通用公共无线接口(common public radio interface,简称CPRI)。
具体地,本发明实施例的网络侧设备还包括:存储在存储器1005上并可在处理器1004上运行的指令或程序,处理器1004调用存储器1005中的指令或程序执行图7所示各模块执行的方法,并达到相同的技术效果,为避免重 复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述PUSHC信号的映射方法或PUSHC信号的接收方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行网络侧设备程序或指令,实现上述PUSHC信号的接收方法实施例的各个过程,或者,所述处理器用于运行终端设备程序或指令,实现上述PUSHC信号的映射方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (37)

  1. 一种物理上行共享信道PUSCH信号的映射方法,应用于终端,其特征在于,包括:
    根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标虚拟资源块VRB或第一目标物理资源块PRB;
    根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;
    采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
  2. 根据权利要求1所述的方法,其中,根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,包括:
    若所述频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由随机接入响应RAR上行链路UL授权调度的或者所述PUSCH是由临时小区无线网络临时标识TC-RNTI加扰的预设下行控制信息格式调度的,则确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;
    根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的所述第一目标PRB。
  3. 根据权利要求2所述的方法,其中,确定目标资源块RB集的公共资源块CRB范围,包括:
    根据第一RB集划分方式,确定所述目标RB集的CRB范围。
  4. 根据权利要求3所述的方法,其中,在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,所述方法还包括:
    根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
  5. 根据权利要求2所述的方法,其中,确定目标资源块RB集的公共资源块CRB范围,包括:
    若激活UL载波带宽部分BWP满足第一指定条件和第二指定条件,则根据第一RB集划分方式,确定所述目标RB集的CRB范围;其中,所述第一指定条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二指定条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;
    若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  6. 根据权利要求5所述的方法,其中,在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,所述方法还包括:
    根据为所述终端配置的小区内保护带宽,确定载波上的所述第二RB集划分方式。
  7. 根据权利要求1至6任一项所述的方法,其中,根据所述终端的频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到所述第二目标PRB的映射方式,包括:
    根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值;
    将所述PUSCH信号乘以幅度缩放因子后,映射到所述第二目标VRB;
    若所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的,则根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配方式,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式。
  8. 根据权利要求7所述的方法,其中,根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值,包括:
    若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配方式,则确定所述第二目标VRB的索引值等于确定的所述第一目标PRB的索 引值;或
    若所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式,则确定所述第二目标VRB为所述第一目标VRB。
  9. 根据权利要求7所述的方法,其中,根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配方式,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式,包括:
    若同时符合第一目标条件、第二目标条件以及第三目标条件,则将第n个所述第二目标VRB映射到第
    Figure PCTCN2021104005-appb-100001
    个所述第二目标PRB,其中
    Figure PCTCN2021104005-appb-100002
    为所述初始UL BWP起始的CRB的索引,
    Figure PCTCN2021104005-appb-100003
    为所述激活UL BWP起始的CRB的索引,n为大于或等于0的整数;
    若不符合所述第一目标条件、第二目标条件以及第三目标条件中的一个或多个,则将第n个所述第二目标VRB映射到第n个所述第二目标PRB;其中,
    所述第一目标条件为:所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式;
    所述第二目标条件为:激活ULBWP包含了初始UL BWP中的所有RB
    所述第三目标条件为:所述激活UL BWP与初始UL BWP具有相同的子载波间隔SCS及循环前缀CP。
  10. 根据权利要求1至6任一项所述的方法,其中,确定PUSCH信号映射到第二目标PRB的映射方式,包括:
    若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则确定所述映射方式为第二映射方式,否则,确定所述映射方式为第一映射方式,其中,所述第一映射方式为先将PUSCH信号映射到虚拟资源块VRB,再将PUSCH信号从VRB映射到PRB,所述第二映射方式为将所述PUSCH信号直接映射到PRB。
  11. 根据权利要求10所述的方法,其中,采用所述映射方式,将PUSCH信号映射到所述第二目标PRB,包括:
    若所述映射方式为第二映射方式,则将所述PUSCH信号乘以幅度缩放因子后,映射到确定的所述第一目标PRB。
  12. 一种PUSCH信号的接收方法,应用于网络侧设备,其特征在于,所述方法包括:
    根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB;
    在所述PRB上接收所述终端上传输的PUSCH信号。
  13. 根据权利要求12所述的方法,其中,根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB,包括:
    若所述频域资源分配类型为类型2 UL资源分配方式,且所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的,则确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;
    根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的PRB。
  14. 根据权利要求13所述的方法,其中,确定目标资源块RB集的公共资源块CRB范围,包括:
    根据第一RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  15. 根据权利要求14所述的方法,其中,在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,所述方法还包括:
    根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
  16. 根据权利要求13所述的方法,其中,确定目标资源块RB集的资源块的公共资源块CRB范围,包括:
    若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的资源块的CRB范围;其中,所述 第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;
    若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  17. 根据权利要求16所述的方法,其中,在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,所述方法还包括:
    根据为所述终端配置的小区内保护带宽,确定所述第二RB集划分方式。
  18. 一种PUSCH信号的映射装置,其特征在于,包括:
    第一确定模块,用于根据终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,其中,所述目标资源块包括第一目标虚拟资源块VRB或第一目标物理资源块PRB;
    第二确定模块,用于根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,其中,所述第二目标PRB为所述第一目标PRB或与所述第一目标VRB对应的PRB;
    映射模块,用于采用所述映射方式,将PUSCH信号映射到所述第二目标PRB。
  19. 根据权利要求18所述的装置,其中,所述第一确定模块根据所述终端的频域资源分配类型和所述终端的频域资源分配信息,确定为PUSCH分配的目标资源块,包括:
    若所述频域资源分配类型为类型2 UL资源分配,且所述PUSCH是由随机接入响应RAR上行链路UL授权调度的或者所述PUSCH是由临时小区无线网络临时标识TC-RNTI加扰的预设下行控制信息格式调度的,确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;
    根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的所述第一目标PRB。
  20. 根据权利要求19所述的装置,其中,所述第一确定模块确定目标资源块RB集的公共资源块CRB范围,包括:
    根据第一RB集划分方式,确定所述目标RB集的CRB范围。
  21. 根据权利要求20所述的装置,其中,所述第一确定模块还用于在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
  22. 根据权利要求19所述的装置,其中,所述确定模块确定目标资源块RB集的公共资源块CRB范围,包括:
    若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;
    若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  23. 根据权利要求22所述的装置,其中,所述第一确定模块还用于在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,根据为所述终端配置的小区内保护带宽,确定载波上的所述第二RB集划分方式。
  24. 根据权利要求18至23任一项所述的装置,其中,所述第二确定模块根据所述终端的频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到所述第二目标PRB的映射方式,包括:
    根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值;
    将所述PUSCH信号乘以幅度缩放因子后,映射到所述第二目标VRB;
    若所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI 加扰的预设下行控制信息格式调度的,则根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式。
  25. 根据权利要求24所述的装置,其中,所述第二确定模块根据所述终端的频域资源分配类型,确定为PUSCH分配的第二目标VRB的索引值,包括:
    若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配方式,则确定所述第二目标VRB的索引值等于确定的所述第一目标PRB的索引值;或
    若所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式,则确定所述第二目标VRB为所述第一目标VRB。
  26. 根据权利要求24所述的装置,其中,所述第二确定模块根据所述终端是否被配置使用交织PUSCH或是否被配置为类型2 UL资源分配方式,确定将所述PUSCH信号从所述第二目标VRB映射到所述第二目标PRB的映射方式,包括:
    若同时符合第一目标条件、第二目标条件以及第三目标条件,则将第n个所述第二目标VRB映射到第
    Figure PCTCN2021104005-appb-100004
    个所述第二目标PRB,其中
    Figure PCTCN2021104005-appb-100005
    为所述初始UL BWP起始的CRB的索引,
    Figure PCTCN2021104005-appb-100006
    为所述激活UL BWP起始的CRB的索引,n为大于或等于0的整数;
    若不符合所述第一目标条件、第二目标条件以及第三目标条件中的一个或多个,则将第n个所述第二目标VRB映射到第n个所述第二目标PRB;其中,
    所述第一目标条件为:所述终端未被配置使用交织PUSCH或者未被配置为类型2 UL资源分配方式;
    所述第二目标条件为:激活ULBWP包含了初始UL BWP中的所有RB;
    所述第三目标条件为:所述激活UL BWP与初始UL BWP具有相同的子载波间隔SCS及循环前缀CP。
  27. 根据权利要求18至23任一项所述的装置,其中,所述第二确定模块根据所述频域资源分配类型和/或所述PUSCH被调度的方式,确定PUSCH信号映射到第二目标PRB的映射方式,包括:
    若所述终端被配置使用交织PUSCH或者被配置为类型2 UL资源分配,则确定所述映射方式为第二映射方式,否则,确定所述映射方式为第一映射方式,其中,所述第一映射方式为先将PUSCH信号映射到虚拟资源块VRB,再将PUSCH信号从VRB映射到PRB,所述第二映射方式为将所述PUSCH信号直接映射到PRB。
  28. 根据权利要求27所述的装置,其中,所述映射模块采用所述映射方式,将PUSCH信号映射到所述第二目标PRB,包括:
    若所述映射方式为第二映射方式,则将所述PUSCH信号乘以幅度缩放因子后,映射到确定的所述第一目标PRB。
  29. 一种PUSCH信号的接收装置,其特征在于,包括:
    第三确定模块,用于根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB;
    接收模块,用于在所述PRB上接收所述终端上传输的PUSCH信号。
  30. 根据权利要求29所述的装置,其中,所述第三确定模块根据为终端配置的频域资源分配类型和指示的频域资源分配信息,确定为所述终端的PUSCH分配的PRB,包括:
    若所述频域资源分配类型为类型2 UL资源分配方式,且所述PUSCH是由RAR UL授权调度的或者所述PUSCH是由TC-RNTI加扰的预设下行控制信息格式调度的,则确定目标资源块RB集的公共资源块CRB范围,其中,所述目标RB集为所述PUSCH分配的RB集;
    根据所述CRB范围以及所述频域资源分配信息,确定为PUSCH分配的PRB。
  31. 根据权利要求30所述的装置,其中,所述第三确定模块确定目标资源块RB集的公共资源块CRB范围,包括:
    根据第一RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  32. 根据权利要求31所述的装置,其中,所述第三确定模块还用于在根据第一RB集划分方式,确定所述目标RB集的CRB范围之前,根据名义的小区内保护带宽、以及载波的RB集模式,确定载波上的第一RB集划分方式。
  33. 根据权利要求31所述的装置,其中,所述第三确定模块确定目标资源块RB集的资源块的公共资源块CRB范围,包括:
    若激活UL载波带宽部分BWP满足第一条件和第二条件,则根据所述第一RB集划分方式,确定所述目标RB集的资源块的CRB范围;其中,所述第一条件为所述激活UL BWP包含了初始UL BWP中的所有RB,所述第二条件为所述激活UL BWP与所述初始UL BWP具有相同的子载波间隔SCS及循环前缀CP;或
    若激活UL BWP不满足所述第一条件和/或所述第二条件,根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围。
  34. 根据权利要求33所述的装置,其中,所述第三确定模块还用于在根据第二RB集划分方式,确定所述目标RB集的资源块的CRB范围之前,根据为所述终端配置的小区内保护带宽,确定所述第二RB集划分方式。
  35. 一种终端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的PUSCH信号的映射方法的步骤。
  36. 一种网络侧设备,其特征在于,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求12至17任一项所述的PUSCH信号的接收方法的步骤。
  37. 一种可读存储介质,其特征在于,所述可读存储介质上存储程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的PUSCH信号的映射方法,或者实现如权利要求12至17任一项所述的 PUSCH信号的接收方法的步骤。
PCT/CN2021/104005 2020-07-02 2021-07-01 Pusch信号的映射方法、终端及网络侧设备 WO2022002199A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CA3187284A CA3187284A1 (en) 2020-07-02 2021-07-01 Method for mapping pusch signal, terminal, and network-side device
JP2022581345A JP7488378B2 (ja) 2020-07-02 2021-07-01 Pusch信号のマッピング方法、端末及びネットワーク側機器
AU2021298712A AU2021298712B2 (en) 2020-07-02 2021-07-01 Method for Mapping Pusch Signal, Terminal, and Network-Side Device
EP21833013.2A EP4178291A4 (en) 2020-07-02 2021-07-01 PUSH SIGNAL IMAGING METHOD, TERMINAL AND NETWORK-SIDE DEVICE
KR1020237003747A KR20230035072A (ko) 2020-07-02 2021-07-01 Pusch 신호의 매핑 방법, 단말 및 네트워크 측 기기
US18/090,588 US20230138775A1 (en) 2020-07-02 2022-12-29 Method for mapping pusch signal, terminal, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010634269.0A CN113891463A (zh) 2020-07-02 2020-07-02 Pusch信号的映射方法、终端及网络侧设备
CN202010634269.0 2020-07-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/090,588 Continuation US20230138775A1 (en) 2020-07-02 2022-12-29 Method for mapping pusch signal, terminal, and network-side device

Publications (1)

Publication Number Publication Date
WO2022002199A1 true WO2022002199A1 (zh) 2022-01-06

Family

ID=79012814

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/104005 WO2022002199A1 (zh) 2020-07-02 2021-07-01 Pusch信号的映射方法、终端及网络侧设备

Country Status (8)

Country Link
US (1) US20230138775A1 (zh)
EP (1) EP4178291A4 (zh)
JP (1) JP7488378B2 (zh)
KR (1) KR20230035072A (zh)
CN (1) CN113891463A (zh)
AU (1) AU2021298712B2 (zh)
CA (1) CA3187284A1 (zh)
WO (1) WO2022002199A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115866759A (zh) * 2022-07-18 2023-03-28 中兴通讯股份有限公司 一种子信道的配置方法、通信节点及存储介质
CN116455544B (zh) * 2023-06-14 2023-08-18 北京智芯微电子科技有限公司 资源分配方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734692A (zh) * 2016-08-11 2018-02-23 株式会社Kt 在无线通信系统中分配数据信道资源的方法和装置
CN110324897A (zh) * 2018-03-28 2019-10-11 北京展讯高科通信技术有限公司 频域资源分配的指示信息发送方法及装置、接收方法及装置、存储介质、基站、用户终端
CN110832931A (zh) * 2017-09-07 2020-02-21 Lg电子株式会社 在无线通信系统中分配资源的方法和使用该方法的设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734692A (zh) * 2016-08-11 2018-02-23 株式会社Kt 在无线通信系统中分配数据信道资源的方法和装置
CN110832931A (zh) * 2017-09-07 2020-02-21 Lg电子株式会社 在无线通信系统中分配资源的方法和使用该方法的设备
CN110324897A (zh) * 2018-03-28 2019-10-11 北京展讯高科通信技术有限公司 频域资源分配的指示信息发送方法及装置、接收方法及装置、存储介质、基站、用户终端

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MODERATOR (LG ELECTRONICS): "Summary of email discussion [101-e-NR-unlic-NRU-WB-01] on DL/UL", 3GPP DRAFT; R2-2004737, vol. RAN WG1, 30 May 2020 (2020-05-30), pages 1 - 3, XP051888338 *
See also references of EP4178291A4 *
VIVO: "Remaining Issues on Physical UL Channel Design in Unlicensed Spectrum", 3GPP DRAFT; R1-2005332, vol. RAN WG1, 8 August 2020 (2020-08-08), pages 1 - 6, XP051917358 *

Also Published As

Publication number Publication date
EP4178291A4 (en) 2023-12-13
US20230138775A1 (en) 2023-05-04
JP7488378B2 (ja) 2024-05-21
AU2021298712B2 (en) 2024-05-02
EP4178291A1 (en) 2023-05-10
KR20230035072A (ko) 2023-03-10
CN113891463A (zh) 2022-01-04
JP2023532116A (ja) 2023-07-26
AU2021298712A1 (en) 2023-02-02
CA3187284A1 (en) 2022-01-06

Similar Documents

Publication Publication Date Title
US20230138775A1 (en) Method for mapping pusch signal, terminal, and network-side device
WO2022152176A1 (zh) 传输处理方法及相关设备
WO2022001815A1 (zh) 信道监听、传输方法、终端及网络侧设备
EP4383871A1 (en) Sidelink resource determining method and apparatus, terminal, and storage medium
CN114390694A (zh) 数据传输方法、装置、终端、网络侧设备及存储介质
WO2022148389A1 (zh) 编码调制符号数的确定方法、装置及通信设备
WO2022143654A1 (zh) Pdcch监测能力的处理方法、终端及网络侧设备
US20240172277A1 (en) Channel access method and processing method for sidelink feedback information, and related device
WO2021249476A1 (zh) Srs资源指示方法、srs资源确定方法及相关设备
WO2022012618A1 (zh) 资源确定方法、装置及终端
WO2022188745A1 (zh) 随机接入方法、装置、终端及存储介质
WO2022033424A1 (zh) 资源传输方法、装置及通信设备
WO2022012592A1 (zh) 反馈信息传输方法、装置、终端及网络侧设备
WO2022017492A1 (zh) 定位处理方法、装置及设备
CN111836382B (zh) 一种结束符号位置的指示方法、终端及网络侧设备
CN115315016A (zh) Msg1传输资源的确定方法、终端及网络侧设备
WO2022068869A1 (zh) 传输处理方法、装置及相关设备
WO2022194216A1 (zh) 信息确定方法和设备
WO2022143875A1 (zh) 信道的调度方法及通信设备
WO2022206593A1 (zh) Pdcch监听处理方法、监听配置方法及相关设备
WO2022194275A1 (zh) 物理上行控制信道资源的确定方法、终端及网络侧设备
WO2022127898A1 (zh) 消息传输方法、装置及设备
WO2022007951A1 (zh) 资源传输方法、装置及通信设备
WO2022188836A1 (zh) Cot确定方法、上行传输方法和设备
US20230254867A1 (en) Uplink transmission processing method and apparatus, and terminal

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: 21833013

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3187284

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2022581345

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20237003747

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021298712

Country of ref document: AU

Date of ref document: 20210701

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2021833013

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021833013

Country of ref document: EP

Effective date: 20230202

NENP Non-entry into the national phase

Ref country code: DE