WO2022127732A1 - 由用户设备执行的方法以及用户设备 - Google Patents

由用户设备执行的方法以及用户设备 Download PDF

Info

Publication number
WO2022127732A1
WO2022127732A1 PCT/CN2021/137411 CN2021137411W WO2022127732A1 WO 2022127732 A1 WO2022127732 A1 WO 2022127732A1 CN 2021137411 W CN2021137411 W CN 2021137411W WO 2022127732 A1 WO2022127732 A1 WO 2022127732A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
coreset0
random access
terminal
bandwidth
Prior art date
Application number
PCT/CN2021/137411
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 夏普株式会社
Publication of WO2022127732A1 publication Critical patent/WO2022127732A1/zh

Links

Images

Classifications

    • 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18Negotiating wireless communication parameters
    • H04W28/20Negotiating bandwidth
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • 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
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access

Definitions

  • the present invention relates to the technical field of wireless communication, and in particular, to a method performed by a user equipment and a corresponding user equipment.
  • enhanced mobile broadband eMBB
  • massive machine-type communication mMTC
  • ultra-reliable and low Delay service Ultra-Reliable and Low Latency communication, URLLC
  • TSC time-sensitive communication
  • 5G connectivity can serve as a catalyst for the next wave of industrial transformation and digitization, enhancing flexibility, increasing productivity and efficiency, reducing maintenance costs, improving operational safety, and more.
  • Devices in this environment include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, and the like. These sensors and actuators need to be connected to the 5G radio access network and core network.
  • Large-scale industrial wireless sensor network (IWSN) use cases and requirements are described in documents such as TR 22.804, which include, in addition to URLLC services with very high demand, relatively low-end services that require smaller size, and/or wireless Years of battery life in state. The requirements for these services are higher than LPWA (Low Power Wide Area Network), but lower than URLCC and eMBB.
  • LPWA Low Power Wide Area Network
  • 5G connectivity can be a catalyst for the next wave of smart city innovation.
  • TSR 22.804 describes smart city use cases and requirements. Smart cities vertically cover data collection and processing, which can more effectively monitor and control urban resources and provide services to urban residents. In particular, the deployment of surveillance cameras is an important part of smart cities, as well as factories and industries.
  • wearable devices include smart watches/rings, eHealth related devices, medical monitoring devices, etc.
  • a feature of this scenario is the compact size of the device required.
  • Device complexity The primary motivation for the new device type is to reduce device cost and complexity compared to eMBB and URLLC devices. This is especially the case with industrial sensors.
  • Deployment scenario The system should support all FR1/FR2 bands for FDD and TDD.
  • Video Surveillance In TSR 22.804, the reference economical video bit rate is 2-4Mbps, the delay is less than 500ms, and the reliability is 99%-99.9%. High-end video, such as agriculture requires 7.5-25Mbps. The business model may be UL transmission dominated.
  • the reference bit rate for smart wearable applications can be 5-50 Mbps, in DL, a minimum of 2-5 Mbps.
  • Devices have higher peak bit rates, say up to 150Mbps downlink, up to 50Mbps uplink.
  • the device's battery should last 1-2 weeks.
  • New demand scenarios place more requirements on network transmission, especially when terminal devices need to obtain business matching under the constraints of smaller size, lower processing complexity, fewer antennas, and smaller bandwidth Therefore, it is necessary to improve the existing air interface resource allocation method and channel transmission method.
  • the present invention provides a method executed by user equipment and user equipment, which can enable terminals with smaller bandwidth capabilities to access the network and perform related service transmission, thereby improving the network.
  • a method performed by a user equipment UE comprising: receiving bandwidth segment BWP configuration information configured by a network for a UE type of the UE, wherein the BWP corresponding to the BWP configuration information is the same as the initial downlink of a cell The BWPs are different; and according to the received BWP configuration information, determine the physical downlink control channel PDCCH position in the common search space, the width and value of the frequency domain indication field in the downlink control information DCI used for data scheduling, and the scheduled at least one of the locations of the PDSCH resources of the Physical Downlink Shared Channel.
  • the UE determines the width and value of the frequency domain indication field in the DCI using the bandwidth of CORESET0 and the subcarrier spacing parameter and at least one of the positions of the scheduled PDSCH resources; if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0, the UE uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the The frequency domain in the DCI indicates at least one of the width, the value of the domain, and the location of the scheduled PDSCH resources.
  • the UE receives the random access procedure for the UE using the random access search space on the initial BWP of the cell.
  • PDCCH if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE receives the PDCCH for the random access procedure of the UE using the random access search space on the BWP , the PDCCH of the random access search space on the initial BWP of the cell is not received.
  • the UE uses the bandwidth and subcarrier spacing parameter of CORESET0 to determine The frequency domain in the DCI indicates at least one of the width, the value, and the location of the scheduled PDSCH resources; if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 or uses different sub- A carrier spacing parameter or a different cyclic prefix parameter, the UE uses the bandwidth of the BWP and the subcarrier spacing parameter to determine at least one of the width and value of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resources .
  • the UE uses the random access search on the initial BWP of the cell space to receive the PDCCH used for the random access procedure of the UE; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the The UE receives the PDCCH for the random access procedure of the UE using the random access search space on the BWP, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.
  • the UE uses the bandwidth and subcarrier spacing parameter of CORESET0 to determine The frequency domain in the DCI indicates at least one of the width, the value, and the location of the scheduled PDSCH resources; if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 and uses the same sub- The carrier spacing parameter and the cyclic prefix parameter, the UE uses the bandwidth of the CORESET0, the subcarrier spacing parameter and the starting position of the BWP to determine the width and value of the frequency domain indication field in the DCI and the position of the scheduled PDSCH resource At least one of: if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the bandwidth of the BW
  • the UE uses the random access search on the initial BWP of the cell Space to receive the PDCCH for the random access procedure of the UE; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE Use the CORESET on the BWP with the same size as CORESET0 to receive the PDCCH for the random access procedure of the UE, and do not receive the PDCCH for the random access procedure on the random access search space on the initial BWP of the cell;
  • the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, and the UE uses CORESET on the BWP to receive random The PDCCH
  • the UE uses the bandwidth of the BWP to determine the width and value of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resources At least one of: if the UE does not receive the BWP configured by the network for the UE, the UE uses the cell-related initial BWP or CORESET0 to determine the width and value of the frequency domain indication field in the DCI and the scheduled PDSCH At least one of the locations of the resources.
  • the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive a cell The PDCCH of the random access search space on the initial BWP; if the UE does not receive the BWP configured by the network for the UE, the UE receives the random access search space for the UE using the random access search space on the initial BWP of the cell PDCCH of the access procedure.
  • a user equipment comprising: a processor; and a memory storing instructions, wherein the instructions execute the above-mentioned method when executed by the processor.
  • a terminal with a small bandwidth capability can access the network and perform related service transmission, thereby improving the service capability of the network, expanding the compatibility of the network, and greatly reducing the cost of communication network deployment.
  • FIG. 1 is a flowchart illustrating a method performed by a user equipment according to Embodiment 1 of the present invention.
  • FIG. 2 is a block diagram schematically showing the user equipment involved in the present invention.
  • the 5G/NR mobile communication system and its subsequent evolution versions are used as an example application environment to specifically describe various embodiments according to the present invention.
  • the present invention is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as communication systems after 5G, 4G mobile communication systems before 5G, 802.11 wireless networks, and the like.
  • LTE Long Term Evolution, long term evolution technology
  • UE User Equipment, user equipment
  • eNB evolved NodeB, evolved base station
  • gNB NR base station
  • kssb SSB subcarrier offset, SSB subcarrier offset
  • TTI Transmission Time Interval, transmission time interval
  • OFDM Orthogonal Frequency Division Multiplexing, Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing, Orthogonal Frequency Division Multiplexing with Cyclic Prefix
  • C-RNTI Cell Radio Network Temporary Identifier, the temporary identifier of the cell wireless network
  • CSI Channel State Information, channel state information
  • CSI-RS Channel State Information Reference Signal, channel state information reference signal
  • CRS Cell Reference Signal, cell-specific reference signal
  • PBCH Physical broadcast channel, physical broadcast channel
  • PUCCH Physical Uplink Control Channel, physical uplink control channel
  • PUSCH Physical Uplink Shared Channel, physical uplink shared channel
  • PRACH Physical random-access channel, physical random access channel
  • PDSCH Physical downlink shared channel, physical downlink shared channel
  • PDCCH Physical downlink control channel, physical downlink control channel
  • UL-SCH Uplink Shared Channel, uplink shared channel
  • DL-SCH Downlink Shared Channel, uplink shared channel
  • RACH random-access channel, random access channel
  • DCI Downlink Control Information, downlink control information
  • MCS Modulation and Coding Scheme, modulation and coding scheme
  • RB Resource Block, resource block
  • CRB Common Resource Block, common resource block
  • CP Cyclic Prefix, cyclic prefix
  • PRB Physical Resource Block, physical resource block
  • VRB Virtual resource block, virtual resource block
  • FDM Frequency Division Multiplexing, frequency division multiplexing
  • TDD Time Division Duplexing
  • FDD Frequency Division Duplexing, frequency division duplexing
  • RRC Radio Resource Control
  • RSRP Reference Signal Receiving Power
  • SRS Sounding Reference Signal
  • DMRS Demodulation Reference Signal, demodulation reference signal
  • CSI-RS Channel state information reference signal
  • CRC Cyclic Redundancy Check, Cyclic Redundancy Check
  • SIB system information block, system information block
  • SIB1 System Information Block Type 1, system information block type 1
  • PSS Primary Synchronization Signal, the main synchronization signal
  • SSS Secondary Synchronization Signal, secondary synchronization signal
  • SSB Synchronization Signal Block, synchronization system information block
  • CRB Common resource block, common resource block
  • BWP BandWidth Part, Bandwidth Fragment/Part
  • SFN System Frame Number, system (wireless) frame number
  • PCI Physical Cell ID, physical cell identification
  • EN-DC EUTRA-NR Dual Connection, LTE-NR dual connection
  • MCG Master Cell Group, the main cell group
  • SCG Secondary Cell Group, secondary cell group
  • PCell Primary Cell, the main cell
  • SCell Secondary Cell, secondary cell
  • SPS Semi-Persistant Scheduling, semi-static scheduling
  • PT-RS Phase-Tracking Reference Signals, phase tracking reference signal
  • Transport Block transport block
  • TBS Transport Block Size, transport block size
  • CB Code Block, coding block/code block
  • QPSK Quadrature Phase Shift Keying, quadrature phase shift keying
  • 16/64/256 QAM 16/64/256 Quadrature Amplitude Modulation, Quadrature Amplitude Modulation
  • AGC Auto Gain Control, automatic gain control
  • ARFCN Absolute Radio Frequency Channel Number, absolute radio frequency channel number
  • CORESET Control resource set, control resource set
  • CCE Control channel element, control channel element
  • MIB Master Information Block, the main information block
  • UCI Uplink Control Information, uplink control information
  • SCS sub-carrier spacing, sub-carrier spacing
  • RIV Resource indicator value, resource indicator value
  • SS-RSRP Synchronization Signal Reference Signal Received Power, synchronization reference signal received power
  • SS-RSRQ Synchronization Signal Reference Signal Received Quality, synchronization reference signal received quality
  • FR1 Frequency range 1 as defined in TS 38.104, frequency range 1 defined by TS38.104
  • FR2 Frequency range 2 as defined in TS 38.104, frequency range 2 defined by TS38.104
  • a network device is a device that communicates with a terminal, including but not limited to base station devices, gNBs, eNBs, wireless APs, etc., which are not specifically distinguished and limited in the following.
  • the network uses the BWP configuration to determine information such as bandwidth required for service transmission with the terminal.
  • the BWP configuration includes the corresponding bandwidth, location, subcarrier spacing, cyclic prefix and other parameters.
  • the network and the terminal carry out data transmission on the BWP.
  • the network can use the scheduling information DCI in the PDCCH to indicate which symbols the scheduled resource blocks use on which RBs of the BWP, and other related receiving or sending configuration information, etc., to perform data transmission with the terminal.
  • the network configures the CORESET on the BWP for PDCCH reception, and the network also configures search space parameters to determine the CORESET that the terminal needs to detect and the corresponding time domain location and other parameters.
  • the network may configure an initial uplink BWP and an initial downlink BWP for the cell for the terminal to perform random access or data transmission. If the network does not configure the initial downlink BWP through the field in the SIB1 signaling, the terminal uses the bandwidth determined by CORESET0 as the initial downlink BWP.
  • the terminal device may receive the PDCCH according to the received parameters and related protocol procedures.
  • the PDCCH indicates the transmission configuration information of the scheduled PDSCH, including the time-frequency position of the PDSCH, resource configuration and other necessary parameters.
  • the terminal receives the relevant PDSCH according to the configuration parameters of the PDSCH.
  • the network device periodically sends broadcast information, including parameters used to determine various configurations of the cell.
  • the cell sends MIB information, indicating the configuration information of CORESET and search space for receiving PDCCH, and the terminal can obtain the time-frequency position, bandwidth and other related configuration parameters of the channel of SIB1 and other information according to the PDCCH instruction.
  • Information about services such as cell access and data transmission.
  • the network indicates the relevant parameters of CORESET0 and search space 0 in the MIB, and the terminal can receive the PDCCH on the corresponding time-frequency resource.
  • the PDCCH indicates parameters used to transmit the PDSCH of SIB1.
  • the terminal receives the PDSCH, obtains SIB1 information, and obtains information such as configuration and parameters for service transmission.
  • the terminal can also receive other SIB information in a similar manner to obtain more service configuration information.
  • the SIB1 information may include parameters for the terminal to perform random access and data transmission, such as downlink initial BWP parameters, uplink initial BWP parameters, random access channel parameters, random access search space parameters, and the like.
  • parameters for the terminal to perform random access and data transmission such as downlink initial BWP parameters, uplink initial BWP parameters, random access channel parameters, random access search space parameters, and the like.
  • the terminal can send a random access signal through the random access channel.
  • Access the network After receiving the random access signal of the terminal, the network responds and indicates relevant information through the PDCCH and scheduled PDSCH signals of the relevant common search space, such as informing the UE of the resource configuration for uplink transmission.
  • the terminal initiates a related request on the indicated uplink resource, such as wireless network connection request signaling.
  • the network can respond to the request and send appropriate response information through the PDCCH scheduling PDSCH in the common search space, thereby establishing a wireless link connection between the network and the terminal.
  • the network can also indicate configuration parameters for a certain type of terminal through SIB1 or other RRC signaling, so that the terminal of this type can perform random access or data transmission process in the network.
  • the network can define the type or type of the terminal. For example, it can define a low-complexity type according to a certain physical layer capability of the terminal or a combination of multiple capabilities, such as the number of channels, processing time limit, maximum bandwidth, duplex capability, etc. Degree Terminal.
  • a network may also define a terminal type to identify multiple capability sets with different combinations of capabilities.
  • the type information of the terminal can be used by the network to allow or prohibit the access of this type of terminal, or used by the network to configure appropriate parameters for this type of terminal for its access or data transmission, or used by the network to restrict this type of terminal from using a certain type of terminal. some parameters.
  • the network can configure an uplink and/or downlink BWP different from the uplink initial BWP or the downlink initial BWP for these devices, and the bandwidth of the BWP is less than or equal to the maximum bandwidth supported by the terminal device, so that these terminal devices in the cell can Perform random access, and send and receive related information.
  • the network configuration enables a terminal with a smaller bandwidth capability to access the network and perform related service transmission when the initial BWP bandwidth notified in the SIB1 of the network is greater than the terminal capability, thereby improving the service capability of the network , expand the compatibility of the network, so that the cost of communication network deployment is greatly reduced.
  • the solution also reduces the bandwidth requirement for the terminal, so that the cost and compatibility of the terminal can obtain obvious benefits.
  • the terminal receives the network indication information sent by the system. If the maximum uplink or downlink transmission bandwidth supported by the terminal is less than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network, and the uplink or downlink bandwidth supported by the terminal is greater than or equal to the BWP bandwidth configured by the network for this type of terminal, the terminal shall apply a bandwidth greater than or equal to that of the terminal. Or the bandwidth equal to the BWP bandwidth configured in this type is taken as the transmission bandwidth of the terminal, otherwise the terminal considers that the cell prohibits the access of the terminal.
  • the terminal receives the network indication information sent by the system. If the network indication information does not contain the BWP bandwidth configured for this type of terminal, if the maximum uplink or downlink transmission bandwidth supported by the terminal is greater than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network, the terminal shall apply a bandwidth that is greater than or equal to that indicated by the network. The bandwidth of the initial uplink or downlink BWP bandwidth is used as the transmission bandwidth of the terminal, otherwise the terminal considers that the cell prohibits the access of the terminal.
  • FIG. 1 is a flowchart illustrating a method performed by a user equipment UE according to Embodiment 1 of the present invention.
  • step 101 the BWP configuration information configured by the network for the UE type of the UE is received, wherein the BWP corresponding to the BWP configuration information is different from the initial downlink BWP of the cell.
  • step 103 according to the received BWP configuration information, determine the PDCCH position in the common search space, the width and value of the frequency domain indication field in the DCI used for data scheduling, and the position of the scheduled PDSCH resources at least one of the.
  • the terminal may perform a random access procedure or a data transmission procedure in a cell configured with CORESET0 according to the type and/or capability of the terminal and an indication of the network.
  • the terminal determines the PDCCH search position in the relevant public search space, the width and value of the frequency domain indication field in the DCI for data scheduling, the position of the scheduled PDSCH resources, the reference beam of the DMRS and other information.
  • the DCI carried by the PDCCH in the common search space uses the PDSCH frequency domain resource allocation method of Type 1 when scheduling PDSCH data transmission.
  • the network can provide this PDSCH in size of A contiguous RB is allocated within the BWP frequency band for data transmission.
  • the frequency resource allocation indication field in the DCI uses an RIV (resource indication value, resource indication value) to indicate a time-frequency resource location specifically allocated for data transmission.
  • the RIV value determines that the bandwidth covered by the scheduled continuous RBs in the indication field is The relative start position RB start and length L RBs of the resource.
  • the following method can be used to determine the RIV value transmitted in the DCI according to the RB start and the length L RBs .
  • the corresponding RB start and the length L RBs can also be deduced according to the RIV value, so as to determine the resource location for PDSCH transmission. .
  • the DCI used for downlink data scheduling includes a frequency domain resource allocation indication field, which indicates the bandwidth configuration of the resources used for the scheduled PDSCH.
  • a frequency domain resource allocation indication field which indicates the bandwidth configuration of the resources used for the scheduled PDSCH.
  • the bit length of the indication field is in is the bandwidth of the BWP used.
  • the terminal also determines the mapping position of the resource block indicated in the DCI in the actual physical channel according to an appropriate method, that is, the relative position of the resource indicated by the terminal according to the RIV, the starting position of the relevant physical resource, and other configuration parameters such as interleaving. Parameters, etc., map the indicated resources to the actually transmitted PDSCH resource locations. For example, the terminal determines the RB resources indicated by the RIV one by one according to the determined starting position of the resource, or the terminal starts to interleave the RB number of the bandwidth associated with the RIV according to the determined starting position of the resource, and performs the RIV information according to the rules of interleaving. Indicates the mapping of the resource.
  • the network configures a BWP for a terminal of a certain type for random access or data transmission of the terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal.
  • the terminal determines the positional relationship between the BWP and CORESET0 according to the type and/or capability of the terminal and the indication of the network. If the BWP includes all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width and value of the frequency domain indication field in the DCI related to data scheduling, and the location of the scheduled PDSCH resources.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width and value of the frequency domain indication field in the DCI related data scheduling, and the location of the scheduled PDSCH resources.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for the random access procedure of this type of terminal. If the BWP does not contain all RBs of CORESET0, the terminal uses the random access search space on the BWP to receive the PDCCH for the random access procedure of this type of terminal, and does not receive the PDCCH of the random access search space on the initial BWP.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type.
  • the BWP includes all RBs of CORESET0
  • the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, The number of RBs determined for this BWP bandwidth and its SCS.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type.
  • the BWP includes all RBs of CORESET0
  • the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS
  • RB start is the offset of the scheduled resource relative to the minimum RB of CORESET0
  • L RBs is the number of RBs of the scheduled resource.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI used for the common search space is determined by the bandwidth of the BWP, is the number of RBs determined by the BWP bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB in the CORESET where the DCI is located in the BWP, and L RBs is the number of RBs of the scheduled resource.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP includes all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the minimum RB sequence number of CORESET0. If the BWP does not contain all the RBs of CORESET0, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the resource configuration of the data channel, and the scheduled PDSCH resource position is mapped from the minimum RB sequence number of the CORESET that schedules the PDSCH on the BWP .
  • the network configures a BWP for a terminal of a certain type for random access or data transmission of the terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal.
  • the terminal determines the positional relationship between the BWP and CORESET0 and the subcarrier spacing parameter relationship according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the width, value and schedule of the frequency domain indication field in the DCI related data scheduling location of PDSCH resources.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width of the frequency domain indication field in the DCI that determines the related data scheduling, The value and the location of the scheduled PDSCH resource.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for this type of terminal random access procedure. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH used for the random access procedure of this type of terminal, and does not receive PDCCH used for random access procedure on random access search space on initial BWP.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, The number of RBs determined for this BWP bandwidth and its SCS.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the network uses the CORESET0 bandwidth and subcarrier spacing parameters to determine the value of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB of CORESET0, and L RBs is the number of RBs of the scheduled resource. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, is the number of RBs determined by the BWP bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB in the CORESET where the DCI is located in the BWP, and L RBs is the number of RBs of the scheduled resource.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP includes all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is from the minimum CORESET0 RB sequence number for mapping.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, the scheduled PDSCH resource location Mapping is performed from the minimum RB sequence number of the CORESET that schedules the PDSCH on the BWP.
  • the network configures a BWP for a terminal of a certain type for random access or data transmission of the terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal.
  • the terminal determines the positional relationship between the BWP and CORESET0 and the subcarrier spacing parameter relationship according to the type and/or capability of the terminal and the indication of the network.
  • the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width, value and schedule of the frequency domain indication field in the DCI related data scheduling location of PDSCH resources. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of CORESET0, the bandwidth of the BWP and the subcarrier spacing parameters to determine the DCI mid-frequency indication for related data scheduling Field width, value and location of scheduled PDSCH resources.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for this type of terminal random access procedure. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH used for the random access procedure of this type of terminal, and does not receive PDCCH used for random access procedure on random access search space on initial BWP.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the bit length of the frequency domain indication field in the DCI used for the common search space is determined by the bandwidth of CORESET0, which is the number of RBs determined by the bandwidth of CORESET0 and its SCS.
  • the terminal uses the CORESET0 bandwidth and the number of RBs determined by the SCS to determine the width of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the network uses the CORESET0 bandwidth and subcarrier spacing parameters to determine the value of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS, RBstart is the offset of the scheduled resource relative to the minimum RB of CORESET0, and LRBs is the number of RBs of the scheduled resource. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0 and the bandwidth of BWP. remember the number of RBs determined for the CORESET0 bandwidth and its SCS, The number of RBs determined for the BWP bandwidth and its SCS. RIV values are used to determine usage on BWP and Some combination of VRB mapping locations.
  • L' RBs L RBs /K
  • RB' start RB start /K
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP includes all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is from the minimum CORESET0 RB sequence number for mapping.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, the scheduled PDSCH resource location Mapping is performed from the minimum RB sequence number of the CORESET that schedules the PDSCH on the BWP.
  • the network configures a BWP for a terminal of a certain type for random access or data transmission of the terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal.
  • the terminal determines the positional relationship between the BWP and CORESET0 and the subcarrier spacing parameter relationship according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the width, value and schedule of the frequency domain indication field in the DCI related data scheduling location of PDSCH resources.
  • the terminal uses the CORESET0 bandwidth, subcarrier spacing parameters and the starting position of the BWP to determine the relevant data scheduling DCI in the frequency domain indication field The width, value and location of the scheduled PDSCH resources. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width and value of the frequency domain indication field in the DCI of the related data scheduling and the location of the scheduled PDSCH resources.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for this type of terminal random access procedure.
  • the terminal uses the CORESET with the same size of CORESET0 on the BWP to receive the PDCCH used for the random access procedure of this type of terminal, and does not receive the PDCCH used for the random access procedure of the terminal on CORESET0 PDCCH for random access procedure. If the BWP does not contain all the RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH for this type of terminal random access procedure, and does not receive The PDCCH of the random access search space on the initial BWP.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type.
  • the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter
  • the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the terminal uses the CORESET0 bandwidth, subcarrier spacing parameters and the starting position of the BWP to determine the frequency domain indication field in the DCI of the relevant data scheduling width.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, The number of RBs determined for this BWP bandwidth and its SCS.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth and subcarrier spacing parameter of CORESET0 to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB of CORESET0, and L RBs is the number of RBs of the scheduled resource. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the CORESET0 bandwidth, subcarrier spacing parameters and the starting position of the BWP to determine the frequency domain indication field in the DCI of the relevant data scheduling value of .
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0. is the number of RBs determined by the CORESET0 bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located, and L RBs is the number of RBs of the scheduled resource.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, is the number of RBs determined by the BWP bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB in the CORESET where the DCI is located in the BWP, and L RBs is the number of RBs of the scheduled resource.
  • the network configures a BWP for a terminal of a certain type, which is used for random access or data transmission of the terminal of this type. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the resource location of the data channel, and the scheduled PDSCH resource location is from the CORESET0 The minimum RB sequence number is mapped.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the resource configuration of the data channel, and the scheduled PDSCH resource location starts from the BWP. Mapping is performed on the minimum RB sequence number of the CORESET where the DCI that schedules the PDSCH is located.
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, the location of the scheduled PDSCH resources Mapping is performed from the minimum RB sequence number of the CORESET that schedules the PDSCH on the BWP.
  • the network configures BWP for a certain type of terminal, or does not configure BWP for this type of terminal equipment, for random access or data transmission of this type of terminal. If the terminal receives the BWP configuration related to the terminal type, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal type, the terminal uses the BWP bandwidth to determine the width, value and The location of the scheduled PDSCH resources. If the terminal does not receive the BWP configuration for this type of terminal, the terminal uses the cell-related initial BWP or CORESET0 to determine the width and value of the frequency domain indication field in the DCI related data scheduling and the location of the scheduled PDSCH resources.
  • the network configures BWP for a terminal of a certain type, or does not configure BWP for the terminal device of this type, for random access or data transmission of the terminal of this type. If the terminal receives the BWP configuration related to the terminal type, the terminal uses the random access search space on the BWP on the BWP to receive the PDCCH for the random access procedure of the terminal of this type, and does not receive the random access search space on the initial BWP. PDCCH. If the terminal does not receive the BWP configuration for this type of terminal, the terminal uses CORESET0 to receive the PDCCH for this type of terminal random access procedure.
  • the network configures a BWP for a terminal of a certain type, or does not configure a BWP for a terminal device of this type, for random access or data transmission of the terminal of this type.
  • the terminal receives the BWP configuration related to the terminal type, the terminal uses the BWP bandwidth to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI used for the common search space is determined by the bandwidth of the BWP, The number of RBs determined for this BWP bandwidth and its SCS.
  • the terminal uses the initial BWP of the cell to determine the width of the frequency domain indication field in the DCI of the relevant data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the network configures BWP for a terminal of a certain type, or does not configure BWP for the terminal device of this type, for random access or data transmission of the terminal of this type.
  • the terminal receives the BWP configuration related to the terminal type, uses the BWP bandwidth to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, is the number of RBs determined by the BWP bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB in the CORESET where the DCI is located in the BWP, and L RBs is the number of RBs of the scheduled resource.
  • the terminal uses the cell-related initial BWP to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB of CORESET0, and L RBs is the number of RBs of the scheduled resource.
  • the network configures BWP for a terminal of a certain type, or does not configure BWP for the terminal device of this type, for random access or data transmission of the terminal of this type. If the terminal receives the BWP configuration related to the terminal type, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, and the scheduled PDSCH resource position is from the BWP to schedule the minimum RB sequence number of the PDSCH CORESET to map. If the terminal does not receive the BWP configuration for this type of terminal, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the minimum RB sequence number of CORESET0.
  • the network configures BWP for a certain type of terminal, or does not configure BWP for this type of terminal equipment, for random access or data transmission of this type of terminal. If the terminal receives the BWP related to the terminal type and the CORESET used to carry the random access search space on the BWP, the terminal uses the BWP bandwidth configuration to determine the width and value of the frequency domain indication field in the DCI of the related data scheduling and the scheduled Location of PDSCH resources. If the terminal does not receive the BWP configuration for this type of terminal or the CORESET configuration for carrying the random access search space on the BWP, the terminal uses the cell-related initial BWP or CORESET0 to determine the DCI in the frequency domain indication field of the relevant data scheduling. Width, value, and location of scheduled PDSCH resources.
  • the network configures BWP for a certain type of terminal, or does not configure BWP for this type of terminal equipment, for random access or data transmission of this type of terminal. If the terminal receives the BWP configuration related to the terminal type and the CORESET used for the random access search space on the BWP, the terminal uses the CORESET on the BWP to receive the PDCCH used for the random access process of the terminal of this type, and does not receive the CORESET on the CORESET0. PDCCH for random access procedure. If the terminal does not receive the BWP configuration for the terminal of this type or the CORESET configuration for the random access search space on the BWP, the terminal uses CORESET0 to receive the PDCCH for the random access procedure of the terminal of this type.
  • the network configures BWP for a terminal of a certain type, or does not configure BWP for the terminal device of this type, for random access or data transmission of the terminal of this type.
  • the terminal receives the BWP related to the terminal type and the CORESET or search space configuration for carrying type1-PDCCH on the BWP
  • the terminal uses the BWP bandwidth configuration to determine the width of the frequency domain indication field in the DCI of the related data scheduling.
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, The number of RBs determined for this BWP bandwidth and its SCS.
  • the terminal uses the cell-related initial BWP to determine the width of the frequency domain indication field in the DCI of the relevant data scheduling .
  • the bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, Number of RBs determined for CORESET0 bandwidth and its SCS.
  • the network configures BWP for a terminal of a certain type, or does not configure BWP for the terminal device of this type, for random access or data transmission of the terminal of this type. If the terminal receives the BWP related to the terminal type and the CORESET and search space configuration for random access search space on the BWP, the terminal uses the BWP bandwidth configuration to determine the value of the frequency domain indication field in the DCI of the related data scheduling.
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of the BWP, is the number of RBs determined by the BWP bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB in the CORESET where the DCI is located in the BWP, and L RBs is the number of RBs of the scheduled resource. If the terminal does not receive the BWP configuration for this type of terminal or the CORESET or search space configuration for carrying type1-PDCCH on the BWP, the terminal uses the cell-related initial BWP to determine the value of the frequency domain indication field in the DCI of the relevant data scheduling .
  • the RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of CORESET0, is the number of RBs determined by the CORESET0 bandwidth and its SCS, RB start is the offset of the scheduled resource relative to the minimum RB of CORESET0, and L RBs is the number of RBs of the scheduled resource.
  • the network configures a BWP for a terminal of a certain type, or does not configure a BWP for a terminal device of this type, for random access or data transmission of the terminal of this type.
  • the terminal receives the BWP configuration related to the terminal type and the CORESET or search space configuration for random access search space on the BWP
  • the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the resource configuration of the data channel.
  • the scheduled PDSCH resource location is mapped from the minimum RB sequence number of the CORESET that schedules the PDSCH on the BWP.
  • the terminal uses the CORESET0 bandwidth and subcarrier spacing parameters to determine the resource location of the data channel,
  • the scheduled PDSCH resource locations are mapped from the minimum RB sequence number of CORESET0.
  • the terminal can determine the width of the frequency domain indication field in the DCI used for data scheduling in the common search space of the terminal, and thus can determine the size of the DCI.
  • the network and the terminal may also be used to determine the size of the DCI for the user search space. For example, when the size of the DCI used for the user search space is not equal to that of the common search space, and the total number of DCI types exceeds the receiving capability of the terminal, the size of the partial DCI is aligned to the specified size by zero-padded or truncation. Determines the size of the common search space DCI.
  • the resource location information of the related scheduling PDSCH or PUSCH can be determined according to the value represented by zero-padded or truncated bits.
  • FIG. 2 is used to describe a user equipment that can execute the method performed by the user equipment described in detail above in the present invention as a modification.
  • FIG. 2 is a block diagram showing a user equipment UE according to the present invention.
  • the user equipment UE20 includes a processor 201 and a memory 202 .
  • the processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • Memory 202 may include, for example, volatile memory (such as random access memory RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory, and the like.
  • Program instructions are stored on the memory 202 . When the instruction is executed by the processor 201, the above method described in detail in the present invention and executed by the user equipment can be executed.
  • the method and related apparatus of the present invention have been described above with reference to the preferred embodiments. Those skilled in the art can understand that the methods shown above are only exemplary, and the various embodiments described above can be combined with each other under the condition that no contradiction occurs.
  • the method of the present invention is not limited to the steps and sequences shown above.
  • the network node and user equipment shown above may include more modules, for example, may also include modules that can be developed or developed in the future and can be used for base stations, MMEs, or UEs, and so on.
  • the various identifiers shown above are only exemplary and not restrictive, and the present invention is not limited to the specific information elements exemplified by these identifiers. Numerous changes and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments.
  • the above-described embodiments of the present invention may be implemented by software, hardware, or a combination of both.
  • the various components inside the base station and the user equipment in the above embodiments may be implemented by various devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processing Controllers, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (CPLDs), etc.
  • DSP digital signal processing
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • CPLDs Programmable Logic Devices
  • base station may refer to a mobile communication data and control switching center with larger transmission power and wider coverage area, including functions such as resource allocation and scheduling, data reception and transmission, and the like.
  • User equipment may refer to a user mobile terminal, for example, including a mobile phone, a notebook, and other terminal equipment that can wirelessly communicate with a base station or a micro base station.
  • embodiments of the invention disclosed herein may be implemented on a computer program product.
  • the computer program product is a product having a computer-readable medium on which computer program logic is encoded that, when executed on a computing device, provides relevant operations to achieve The above technical solutions of the present invention.
  • computer program logic When executed on at least one processor of a computing system, computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention.
  • Such arrangements of the present invention are typically provided as software, code and/or other data structures arranged or encoded on a computer readable medium such as an optical medium (eg CD-ROM), floppy or hard disk, or such as one or more Firmware or other medium of microcode on a ROM or RAM or PROM chip, or a downloadable software image in one or more modules, a shared database, etc.
  • Software or firmware or such a configuration may be installed on a computing device, so that one or more processors in the computing device execute the technical solutions described in the embodiments of the present invention.
  • each functional module or each feature of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is usually one or more integrated circuits.
  • Circuits designed to perform the various functions described in this specification may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs) or general purpose integrated circuits, field programmable gate arrays (FPGAs) or other Program logic devices, discrete gate or transistor logic, or discrete hardware components, or any combination of the above.
  • a general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each circuit described above may be configured by digital circuits, or may be configured by logic circuits.
  • the present invention can also use the integrated circuit obtained by using the advanced technology.

Landscapes

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

Abstract

一种由用户设备UE执行的方法,包括:接收网络针对UE的UE类型配置的带宽片段BWP配置信息,与BWP配置信息相对应的BWP与小区初始下行BWP不同;以及UE根据接收到的BWP配置信息,确定公共搜索空间中的物理下行控制信道PDCCH位置、用于数据调度的下行控制信息DCI中的频域指示域的宽度、数值、以及所调度的物理下行共享信道PDSCH资源的位置中的至少一个。

Description

由用户设备执行的方法以及用户设备 技术领域
本发明涉及无线通信技术领域,具体涉及由用户设备执行的方法以及相应的用户设备。
背景技术
现有的5G/NR网络中,定义了三种典型的业务模型,增强移动宽带业务(enhanced mobile broadband,eMBB),海量机器类型通信业务(massive machine-type communication,mMTC)以及超可靠性及低时延业务(Ultra-Reliable and Low Latency communication,URLLC)。除了这几种还有时间敏感业务(time sensitive communication,TSC)等。
5G的一个重要目标是实现互联产业。5G互联可以作为下一波产业变革和数字化的催化剂,可以增强灵活性,提高生产率和效率,降低维护成本,提高运行安全性等。在这种环境中的装置包括压力传感器、湿度传感器、温度计、运动传感器、加速度计、执行器等。需要将这些传感器和执行器连接到5G无线接入网络和核心网络。TR 22.804等文献中描述了大规模的工业无线传感器网络(IWSN)用例和需求,除了包含具有非常高的需求URLLC业务之外,也包含需求较小尺寸的相对低端的服务,和/或无线状态下数年的电池寿命。对这些服务的要求高于LPWA(Low Power Wide Area Network),但低于URLCC和eMBB。
与互联网行业相似,5G互联互通可以成为下一波智能城市创新的催化剂。作为一个例子,TSR 22.804描述了智能城市用例和需求。智能城市垂直覆盖数据收集和处理,可以更有效地监测和控制城市资源,并为城市居民提供服务。特别是监控摄像头的部署是智能城市的重要组成部分,也是工厂和行业的重要组成部分。
最后,可穿戴设备的实例包括智能手表/环、eHealth相关设备、医疗 监测设备等。这种场景的一个特点是要求设备大小紧凑。
作为基线,这三个用例的需求是:
一般要求:
·设备复杂性:新设备类型的主要动机是相比eMBB和URLLC设备降低设备成本和复杂性。尤其是工业传感器的情况。
·设备尺寸:大多数用例的要求设备设计紧凑。
·部署场景:系统应该支持FDD和TDD的所有FR1/FR2波段。
用例具体要求:
·工业无线传感器:在TR 22.832和TS 22.104中描述引用用例和要求:通信服务可用性是99.99%,端到端延迟小于100毫秒。参考比特率小于2Mbps(可能不对称,比如上行重载),对于所有用例和设备是平稳的。电池应该持续至少几年。对于安全相关的传感器,延迟要求较低,5-10ms(TR 22.804)
·视频监控:在TSR 22.804中,参考经济视频比特速率为2-4Mbps,延迟小于500ms,可靠性99%-99.9%。高端视频,例如农业需要7.5-25Mbps。业务模式可能是UL传输为主的。
·可佩戴设备:智能可佩戴应用的参考比特率可以是5-50Mbps,在DL中,最小2-5Mbps。设备的峰值比特率更高,比如高达150Mbps的下行链路,高达50Mbps的上行链路。该设备的电池应持续1-2周。
新需求场景对网络传输提出了更多的要求,尤其是在终端设备需要在更小的体积,更低的处理复杂度,更少的天线数以及更小的带宽等约束条件下获得和业务匹配的接收能力,这些都需要对现有的空口的资源配置方法以及信道传输的方法进行改进。
发明内容
为了解决上述问题中的至少一部分,本发明提供了一种由用户设备执行的方法以及用户设备,能够使得具有较小带宽能力的终端能够接入网络,并进行相关的业务传输,从而提升了网络的业务能力,扩大网络的兼容性,使得通信网络部署的成本大大降低。
根据本发明,提出了一种由用户设备UE执行的方法,包括:接收网络针对所述UE的UE类型配置的带宽片段BWP配置信息,其中与所述BWP配置信息相对应的BWP与小区初始下行BWP不同;以及根据接收到的所述BWP配置信息,确定公共搜索空间中的物理下行控制信道PDCCH位置、用于数据调度的下行控制信息DCI中的频域指示域的宽度、数值、以及所调度的物理下行共享信道PDSCH资源的位置中的至少一个。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB或者使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述 DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB或者使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用该CORESET0的带宽,子载波间隔参数以及BWP的起始位置确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
优选地,如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用所述BWP上与CORESET0大小相 同的CORESET接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间上用于随机接入过程的PDCCH;如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用在所述BWP上的CORESET接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
优选地,如果所述UE收到网络针对所述UE配置的BWP,所述UE使用所述BWP的带宽确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;如果所述UE没有收到网络针对所述UE配置的BWP,所述UE使用小区相关的初始BWP或CORESET0确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
优选地,如果所述UE收到网络针对所述UE配置的BWP,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH;如果所述UE没有收到网络针对所述UE配置的BWP,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH。
此外,根据本发明,提出了一种用户设备,包括:处理器;以及存储器,存储有指令,其中,所述指令在由所述处理器运行时执行上述的方法。
根据本发明,能够使得具有较小带宽能力的终端能够接入网络,并进行相关的业务传输,从而提升了网络的业务能力,扩大网络的兼容性,使得通信网络部署的成本大大降低。
附图说明
通过下文结合附图的详细描述,本发明的上述和其它特征将会变得更加明显,其中:
图1是示出了根据本发明的实施例1的由用户设备执行的方法的流 程图。
图2是示意性示出本发明所涉及的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意,本发明不应局限于下文所述的具体实施方式,这些实施方式仅作为示例提供,以将主题的范围传达给本领域技术人员。另外,为了简便起见,省略了对与本发明没有直接关联的公知技术的详细描述,以防止对本发明的理解造成混淆。
通常,除非在使用该术语的上下文中清楚地给出和/或隐含不同的含义,否则本文中使用的所有术语将根据其在相关技术领域中的普通含义来解释。除非明确说明,否则对一/一个/该元件、设备、组件、部件、步骤等的所有引用应公开地解释为是指该元件、装置、组件、部件、步骤等的至少一个实例。除非必须明确地将一个步骤描述为在另一个步骤之后或之前和/或隐含地一个步骤必须在另一个步骤之后或之前,否则本文所公开的任何方法的步骤不必以所公开的确切顺序执行。在适当的情况下,本文公开的任何实施例的任何特征可以适用于任何其它实施例。同样,任何实施例的任何优点可以适用于任何其它实施例,反之亦然。
下文以5G/NR移动通信系统及其后续的演进版本作为示例应用环境,具体描述了根据本发明的多个实施方式。然而,需要指出的是,本发明不限于以下实施方式,而是可适用于更多其它的无线通信系统,例如5G之后的通信系统以及5G之前的4G移动通信系统,802.11无线网络等。
下面描述本发明涉及的部分术语,如未特别说明,本发明涉及的术语采用此处定义。本发明给出的术语在LTE、LTE-Advanced、LTE-Advanced Pro、NR以及之后的或其他的通信系统中可能采用不同的命名方式,但本发明中采用统一的术语,在应用到具体的系统中时,可以替换为相应系统中采用的术语。
3GPP:3rd Generation Partnership Project,第三代合作伙伴计划
LTE:Long Term Evolution,长期演进技术
NR:New Radio,新无线、新空口
UE:User Equipment,用户设备
eNB:evolved NodeB,演进型基站
gNB:NR基站
kssb:SSB subcarrier offset,SSB子载波偏移
TTI:Transmission Time Interval,传输时间间隔
OFDM:Orthogonal Frequency Division Multiplexing,正交频分复用
CP-OFDM:Cyclic Prefix Orthogonal Frequency Division Multiplexing,带有循环前缀的正交频分复用
C-RNTI:Cell Radio Network Temporary Identifier,小区无线网络临时标识
CSI:Channel State Information,信道状态信息
HARQ:Hybrid Automatic Repeat Request,混合自动重传请求
CSI-RS:Channel State Information Reference Signal,信道状态信息参考信号
CRS:Cell Reference Signal,小区特定参考信号
PBCH:Physical broadcast channel,物理广播信道
PUCCH:Physical Uplink Control Channel,物理上行控制信道
PUSCH:Physical Uplink Shared Channel,物理上行共享信道
PRACH:Physical random-access channel,物理随机接入信道
PDSCH:Physical downlink shared channel,物理下行共享信道
PDCCH:Physical downlink control channel,物理下行控制信道
UL-SCH:Uplink Shared Channel,上行共享信道
DL-SCH:Downlink Shared Channel,上行共享信道
RACH:random-access channel,随机接入信道
DCI:Downlink Control Information,下行控制信息
CG:Configured Grant,配置调度许可
MCS:Modulation and Coding Scheme,调制编码方案
RB:Resource Block,资源块
RE:Resource Element,资源单元
CRB:Common Resource Block,公共资源块
CP:Cyclic Prefix,循环前缀
PRB:Physical Resource Block,物理资源块
VRB:Virtual resource block,虚拟资源块
FDM:Frequency Division Multiplexing,频分复用
TDD:Time Division Duplexing,时分双工
FDD:Frequency Division Duplexing,频分双工
RRC:Radio Resource Control,无线资源控制
RSRP:Reference Signal Receiving Power,参考信号接收功率SRS:Sounding Reference Signal,探测参考信号
DMRS:Demodulation Reference Signal,解调参考信号
CSI-RS:Channel state information reference signal
CRC:Cyclic Redundancy Check,循环冗余校验
SFI:Slot Format Indication,时隙格式指示
SIB:system inforrnation block,系统信息块
SIB1:System Information Block Type 1,系统信息块类型1
PSS:Primary Synchronization Signal,主同步信号
SSS:Secondary Synchronization Signal,辅同步信号
SSB:Synchronization Signal Block,同步系统信息块
CRB:Common resource block,公共资源块
BWP:BandWidth Part,带宽片段/部分
SFN:System Frame Number,系统(无线)帧号
PCI:Physical Cell ID,物理小区标识
IE:Information Element,信息元素
EN-DC:EUTRA-NR Dual Connection,LTE-NR双连接
MCG:Master Cell Group,主小区组
SCG:Secondary Cell Group,辅小区组
PCell:Primary Cell,主小区
SCell:Secondary Cell,辅小区
SPS:Semi-Persistant Scheduling,半静态调度
TA:Timing Advance,上行定时提前量
PT-RS:Phase-Tracking Reference Signals,相位跟踪参考信号
TB:Transport Block,传输块
TBS:Transport Block Size,传输块大小
CB:Code Block,编码块/码块
QPSK:Quadrature Phase Shift Keying,正交相移键控
16/64/256 QAM:16/64/256 Quadrature Amplitude Modulation,正交幅度调制
AGC:Auto Gain Control,自动增益控制
TDRA(field):Time Domain Resource Assignment,时域资源分配指示(域)
FDRA(field):Frequency Domain Resource Assignment,频域资源分配指示(域)
ARFCN:Absolute Radio Frequency Channel Number,绝对无线频率信道编号
RedCap Device:Reduced Capability Device,降能力设备
CORESET:Control resource set,控制资源集合
CORESET0:Control resource set 0,控制资源集合序号0
CCE:Control channel element,控制信道单元
REG:Resource Element Group,资源单元组
MIB:Master Information Block,主信息块
DRX:Discontinuous Reception,不连续接收
AL:Aggregation Level,汇聚级别
UCI:Uplink Control Information,上行控制信息
CSS:Common search space,公共搜索空间
USS:UE-specific search space,用户搜索空间
SCS:sub-carrier spacing,子载波间隔
SLIV:Start and length indicator value,起始和长度指示值
RIV:Resource indicator value,资源指示值
SS-RSRP:Synchronization Signal Reference Signal Received Power,同步参考信号接收功率
SS-RSRQ:Synchronization Signal Reference Signal Received Quality,同步参考信号接收质量
FR1:Frequency range 1 as defined in TS 38.104,由TS38.104定义的频率范围1
FR2:Frequency range 2 as defined in TS 38.104,由TS38.104定义的频率范围2
下文是与本发明方案相关联现有技术的描述。如无特别说明,具体实施例中与现有技术中相同术语的含义相同。
值得指出的是,本发明说明书中涉及的用户设备与终端设备含义相同,文中的UE也可以表示终端,后文中不做具体区分和限定。类似的,网络设备为与终端进行通信的设备,包括并不限于基站设备,gNB,eNB,无线AP等,后文中不做具体区分和限定。
网络使用BWP配置来确定和终端进行业务传输所需要的带宽等信息。BWP配置包含相应的带宽,位置,子载波间隔,循环前缀等参数。网络和终端在BWP上进行数据传输。比如网络可以通过PDCCH中的调度信息DCI指示所调度的资源块在BWP的哪些RB上使用哪些符号,以及其他相关的接收或发送配置信息等和终端进行数据传输。
网络配置BWP上的CORESET用于PDCCH接收,网络还配置搜索空间参数确定终端所需要检测的CORESET以及相应的时域位置等参数。
网络可以为小区配置初始上行BWP和初始下行BWP,用于终端进行随机接入或数据传输。如果网络没有通过SIB1信令中的字段配置初始下行BWP,终端将CORESET0确定的带宽作为初始下行BWP。
终端设备可以根据接收到的参数以及相关协议过程,接收到PDCCH。 PDCCH中指示所调度的PDSCH的传输配置信息,包括PDSCH的时频位置,资源配置以及其他必要的参数。终端根据PDSCH的配置参数进行相关PDSCH的接收。
网络设备周期性地发送广播信息,包含用于确定小区各种配置的参数。比如小区发送MIB信息,指示用于接收PDCCH的CORESET和搜索空间的配置信息,终端根据PDCCH的指示可以获得SIB1和其他信息的信道的时频位置,带宽等等相关配置参数可以获得更多的用于接入小区和数据传输等业务的相关信息。
一个具体的实例是网络在MIB中指示CORESET0和搜索空间0的相关参数,终端可以在相应的时频资源上接收PDCCH。PDCCH指示了用于传输SIB1的PDSCH的参数。终端接收PDSCH,获得SIB1信息,获得用于进行业务传输的配置,参数等信息。终端还可以通过类似的方式接收其他SIB信息,获得更多的业务配置信息。
SIB1信息中可以包含用于终端进行随机接入和数据传输的参数,比如下行初始BWP参数,上行初始BWP参数,以及随机接入信道参数,随机接入搜索空间参数等。一个具体的实例,终端在满足接入该网络条件的情况下,比如终端所支持的上行或下行带宽大于网络配置的上行或下行BWP带宽时,终端可通过随机接入信道发送随机接入信号来接入网络。网络接收到终端的随机接入信号后,进行响应,并通过相关公共搜索空间的PDCCH和调度的PDSCH信号指示相关信息,比如通知UE进行上行传输的资源配置。终端在指示的上行资源上发起相关的请求,比如无线网络连接请求信令。网络可对该请求进行响应,并通过公共搜索空间的PDCCH调度PDSCH发送适当的响应信息,从而建立起网络和终端的无线链路连接。
网络还可以通过SIB1或其他RRC信令指示用于某种类型终端的配置参数,使得该类型终端在网络中可以进行随机接入或数据传输过程。
网络可以定义终端的类型或种类(type),例如可以根据终端的某种物理层能力或多个能力的组合,比如通道数,处理时间限制,最大带宽,双工能力等,定义一种低复杂度终端。网络也可以定义一种终端类型用 于标识多种具有不同能力组合的能力集。终端的类型信息可以用于网络允许或禁止该类型的终端接入,或者用于网络为该类型终端配置适当的参数,用于其接入或数据传输,或者用于网络限制该类型终端使用某些参数。
对于某些终端设备,在接入某个网络时,根据接收到的SIB1信息,发现其支持的最大带宽小于网络指示的上行初始BWP或下行初始BWP的带宽,但是大于网络用于发送SIB1信息的最大带宽。这时,网络可为这些设备配置一个不同与上行初始BWP或下行初始BWP的上行和/或下行BWP,该BWP的带宽小于等于该终端设备所支持的最大带宽,使得这些终端设备在该小区可以进行随机接入,以及相关信息的发送和接收等。这种情况下,网络配置使得具有较小带宽能力的终端在网络的SIB1中通知的初始BWP带宽大于终端能力时,也能够接入网络,并进行相关的业务传输,从而提升了网络的业务能力,扩大网络的兼容性,使得通信网络部署的成本大大降低。同时该方案也降低了对终端的带宽要求,使得终端的成本,兼容性等获得明显的好处。
终端接收系统发送的网络指示信息。如果终端支持的最大上行或下行传输带宽小于或等于网络指示的初始上行或下行BWP的载波带宽,并且终端支持的上行或下行带宽大于或等于网络为该类型终端配置的BWP带宽,终端应用一个大于或等于该类型配置的BWP带宽的带宽作为终端的传输带宽,否则终端认为该小区禁止该终端的接入。
终端接收系统发送的网络指示信息。如果网络指示信息中不包含为该类型终端配置的BWP带宽,如果终端支持的最大上行或下行传输带宽大于或等于网络指示的初始上行或下行BWP的载波带宽,终端应用一个大于或等于网络指示的初始上行或下行BWP带宽的带宽作为终端的传输带宽,否则终端认为该小区禁止该终端的接入。
图1是示出了根据本发明的实施例1的由用户设备UE执行的方法的流程图。
如图1所示,在步骤101,接收网络针对UE的UE类型配置的BWP配置信息,其中与所述BWP配置信息相对应的BWP与小区初始下行 BWP不同。
然后,在步骤103,根据接收到的所述BWP配置信息,确定公共搜索空间中的PDCCH位置、用于数据调度的DCI中的频域指示域的宽度、数值、以及所调度的PDSCH资源的位置中的至少一个。
具体地,终端可根据终端的类型和/或能力以及网络的指示在配置了CORESET0的小区中,进行随机接入过程或数据传输过程。终端根据配置情况确定相关的公共搜索空间中PDCCH搜索位置,数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置,DMRS的参考波束等信息。
公共搜索空间中PDCCH所承载的DCI在调度PDSCH数据传输使用Type1的PDSCH频域资源分配方式。网络可以为该PDSCH在大小为
Figure PCTCN2021137411-appb-000001
的BWP频带内分配一段连续的RB用于数据传输。DCI中的频率资源分配指示域使用RIV(resource indication value,资源指示值)指示具体分配到用于数据传输的时频资源位置。RIV值确定所调度的连续RB在指示域所覆盖的带宽为
Figure PCTCN2021137411-appb-000002
的资源中的相对起始位置RB start和长度L RBs。例如可以使用下面的方法根据RB start和长度L RBs确定DCI中所传输的RIV值,同样的也可以根据该RIV值推导出相应的RB start和长度L RBs,从而确定用于PDSCH传输的资源位置。
如果
Figure PCTCN2021137411-appb-000003
那么
Figure PCTCN2021137411-appb-000004
否则
Figure PCTCN2021137411-appb-000005
这里L RBs≥1并且不大于
Figure PCTCN2021137411-appb-000006
用于下行数据调度的DCI中包含频域资源分配指示域,指示用于所调度的PDSCH使用的资源在带宽上的配置情况。例如,当使用Type1的PDSCH资源分配方式时,指示域的比特长度为
Figure PCTCN2021137411-appb-000007
其中
Figure PCTCN2021137411-appb-000008
为所使用的BWP的带宽。
终端还要根据适当的方法确定DCI中所指示的资源块在实际物理信道中的映射位置,也就是终端根据RIV所指示的资源相对位置,相关的 物理资源起始位置,以及其他配置参数比如交织参数等将指示的资源映射到实际发送的PDSCH资源位置。比如终端根据所确定的资源起始位置逐个确定RIV所指示的RB资源,或者终端根据所确定的资源起始位置开始对RIV所关联的带宽的RB数进行交织,并按交织的规则进行RIV所指示资源的映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输,终端支持的带宽大于或等于网络为该终端配置的BWP。在配置了CORESET0的小区中,终端根据终端的类型和/或能力以及网络的指示,确定BWP与CORESET0的位置关系。如果该BWP包含CORESET0的所有RB,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置等信息。如果该BWP不包含CORESET0的全部RB,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置等信息。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,终端使用网络指示的初始BWP上随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH。如果该BWP不包含CORESET0的全部RB,终端使用在该BWP上的随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH,不接收初始BWP上随机接入搜索空间的PDCCH。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000009
为CORESET0带宽及其SCS所确定的RB数。如果该BWP不包含CORESET0的全部RB,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由BWP的带 宽确定,
Figure PCTCN2021137411-appb-000010
为该BWP带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000011
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对CORESET0的最小RB的偏移,L RBs为所调度资源的RB数。如果该BWP不包含CORESET0的全部RB,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由BWP的带宽确定,
Figure PCTCN2021137411-appb-000012
为BWP带宽及其SCS所确定的RB数,RB start为所调度资源相对BWP中该DCI所在CORESET的最小RB的偏移,L RBs为所调度资源的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。如果该BWP不包含CORESET0的全部RB,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输,终端支持的带宽大于或等于网络为该终端配置的BWP。在配置了CORESET0的小区中,终端根据终端的类型和/或能力以及网络的指示,确定BWP与CORESET0的位置关系和子载波间隔参数关系。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终 端使用该BWP的带宽以及子载波间隔参数确定确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用网络指示的初始BWP上随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用在BWP上的随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH,不接收初始BWP上随机接入搜索空间上用于随机接入过程的PDCCH。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,网络使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000013
为CORESET0带宽及其SCS所确定的RB数。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由BWP的带宽确定,
Figure PCTCN2021137411-appb-000014
为该BWP带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,网络使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000015
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对CORESET0的最小RB的偏移,L RBs为所调度资源的RB数。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波 间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由BWP的带宽确定,
Figure PCTCN2021137411-appb-000016
为BWP带宽及其SCS所确定的RB数,RB start为所调度资源相对BWP中该DCI所在CORESET的最小RB的偏移,L RBs为所调度资源的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输,终端支持的带宽大于或等于网络为该终端配置的BWP。在配置了CORESET0的小区中,终端根据终端的类型和/或能力以及网络的指示,确定BWP与CORESET0的位置关系和子载波间隔参数关系。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度,数值以及所调度的PDSCH资源的位置。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用CORESET0的带宽以及该BWP的带宽以及子载波间隔参数确定确定相关的数据调度的DCI中频域指示域的宽度,数值以及所调度的PDSCH资源的位置。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用网络指示的初始BWP 上随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用在BWP上的随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH,不接收初始BWP上随机接入搜索空间上用于随机接入过程的PDCCH。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,网络使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,为CORESET0带宽及其SCS所确定的RB数。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用CORESET0带宽及其SCS所确定的RB数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000017
为CORESET0带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,网络使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000018
为CORESET0带宽及其SCS所确定的RB数,RBstart为所调度资源相对CORESET0的最小RB的偏移,LRBs为所调度资源的RB数。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽和BWP的带宽确定。记
Figure PCTCN2021137411-appb-000019
为CORESET0带宽及其SCS所确定的RB数,
Figure PCTCN2021137411-appb-000020
为BWP带宽及其SCS所确定的RB数。RIV值用于确定BWP上的使用
Figure PCTCN2021137411-appb-000021
Figure PCTCN2021137411-appb-000022
的某种组合的VRB的映射位置。
如果
Figure PCTCN2021137411-appb-000023
然后
Figure PCTCN2021137411-appb-000024
否则
Figure PCTCN2021137411-appb-000025
其中L′ RBs=L RBs/K,RB′ start=RB start/K并且L′ RBs不大于
Figure PCTCN2021137411-appb-000026
如果
Figure PCTCN2021137411-appb-000027
K为集合{1,2,4,8}中满足
Figure PCTCN2021137411-appb-000028
的最大值,否则K=1。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。如果该BWP不包含CORESET0的全部RB或者使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输,终端支持的带宽大于或等于网络为该终端配置的BWP。在配置了CORESET0的小区中,终端根据终端的类型和/或能力以及网络的指示,确定BWP与CORESET0的位置关系和子载波间隔参数关系。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。如果该BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用该CORESET0的带宽,子载波间隔参数以及BWP的起始位置确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。如果该BWP不包含CORESET0的全部RB并且使用不同的 子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用网络指示的初始BWP上随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH。如果该BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用BWP上CORESET0大小相同的CORESET接收用于该类型终端随机接入过程的PDCCH,不接收CORESET0上用于随机接入过程的PDCCH。如果该BWP不包含CORESET0的全部RB并且使用不同的子载波间隔参数或不同的循环前缀参数,终端使用在BWP上的随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH,不接收初始BWP上随机接入搜索空间的PDCCH。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000029
为CORESET0带宽及其SCS所确定的RB数。如果该BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用该CORESET0的带宽,子载波间隔参数以及BWP的起始位置确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000030
为CORESET0带宽及其SCS所确定的RB数。如果该BWP不包含CORESET0的全部RB并且使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置。用于公共搜索空间的DCI中频域指示域的比特长度由BWP的带宽确定,
Figure PCTCN2021137411-appb-000031
为该BWP带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000032
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对CORESET0的最小RB的偏移,L RBs为所调度资源的RB数。如果该BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用该CORESET0的带宽,子载波间隔参数以及BWP的起始位置确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定。
Figure PCTCN2021137411-appb-000033
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对该DCI所在的CORESET的最小RB的偏移,L RBs为所调度资源的RB数。
如果该BWP不包含CORESET0的全部RB并且使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由BWP的带宽确定,
Figure PCTCN2021137411-appb-000034
为BWP带宽及其SCS所确定的RB数,RB start为所调度资源相对BWP中该DCI所在CORESET的最小RB的偏移,L RBs为所调度资源的RB数。
可选的,网络为某一类型的终端配置BWP,用于该类型终端的随机接入或数据传输。如果该BWP包含CORESET0的全部RB,并且使用相同的子载波间隔参数和循环前缀参数,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。如果该BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的DCI所在的CORESET的最小RB序号进行映射。如果该BWP不包含CORESET0 的全部RB并且使用不同的子载波间隔参数或不同的循环前缀参数,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置,并且终端支持的带宽大于或等于网络为该终端类型配置的BWP,终端使用该BWP带宽确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。如果终端没有收到用于该类型终端的BWP配置,终端使用小区相关的初始BWP或CORESET0确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置,终端使用在BWP上的BWP上的随机接入搜索空间接收用于该类型终端随机接入过程的PDCCH,不接收初始BWP上随机接入搜索空间的PDCCH。如果终端没有收到用于该类型终端的BWP配置,终端使用CORESET0接收用于该类型终端随机接入过程的PDCCH。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置,终端使用该BWP带宽确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由BWP的带宽确定,
Figure PCTCN2021137411-appb-000035
为该BWP带宽及其SCS所确定的RB数。如果终端没有收到用于该类型终端的BWP配置,终端使用小区的初始BWP确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000036
为CORESET0带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设 备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置,终端使用该BWP带宽确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由BWP的带宽确定,
Figure PCTCN2021137411-appb-000037
为BWP带宽及其SCS所确定的RB数,RB start为所调度资源相对BWP中该DCI所在CORESET的最小RB的偏移,L RBs为所调度资源的RB数。如果终端没有收到用于该类型终端的BWP配置,终端使用小区相关的初始BWP确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000038
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对CORESET0的最小RB的偏移,L RBs为所调度资源的RB数。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。如果终端没有收到用于该类型终端的BWP配置,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。
作为该示例的实施例,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP以及该BWP上用于承载随机接入搜索空间的CORESET,终端使用该BWP带宽配置确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。如果终端没有收到用于该类型终端的BWP配置或该BWP上用于承载随机接入搜索空间的CORESET配置,终端使用小区相关的初始BWP或CORESET0确定相关的数据调度的DCI中频域指示域的宽度、数值以及所调度的PDSCH资源的位置。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设 备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置以及该BWP上用于随机接入搜索空间的CORESET,终端使用在BWP上的CORESET接收用于该类型终端随机接入过程的PDCCH,不接收CORESET0上用于随机接入过程的PDCCH。如果终端没有收到用于该类型终端的BWP配置或该BWP上用于随机接入搜索空间的CORESET配置,终端使用CORESET0接收用于该类型终端随机接入过程的PDCCH。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP以及该BWP上用于承载type1-PDCCH的CORESET或搜索空间配置,终端使用该BWP带宽配置确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由BWP的带宽确定,
Figure PCTCN2021137411-appb-000039
为该BWP带宽及其SCS所确定的RB数。如果终端没有收到用于该类型终端的BWP配置或该BWP上用于承载type1-PDCCH的CORESET或搜索空间配置,终端使用小区相关的初始BWP确定相关的数据调度的DCI中频域指示域的宽度。用于公共搜索空间的DCI中频域指示域的比特长度由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000040
为CORESET0带宽及其SCS所确定的RB数。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP以及该BWP上用于随机接入搜索空间的CORESET和搜索空间配置,终端使用该BWP带宽配置确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的RIV数值由BWP的带宽确定,
Figure PCTCN2021137411-appb-000041
为BWP带宽及其SCS所确定的RB数,RB start为所调度资源相对BWP中该DCI所在CORESET的最小RB的偏移,L RBs为所调度资源的RB数。如果终端没有收到用于该类型终端的BWP配置或该BWP上用于承载type1-PDCCH的CORESET或搜索空间配置,终端使用小区相关的初始BWP确定相关的数据调度的DCI中频域指示域的数值。用于公共搜索空间的DCI中频域指示域的 RIV数值由CORESET0的带宽确定,
Figure PCTCN2021137411-appb-000042
为CORESET0带宽及其SCS所确定的RB数,RB start为所调度资源相对CORESET0的最小RB的偏移,L RBs为所调度资源的RB数。
可选的,网络为某一类型的终端配置BWP,或不为该类型的终端设备配置BWP,用于该类型终端的随机接入或数据传输。如果终端收到该终端类型相关的BWP配置以及该BWP上用于随机接入搜索空间的CORESET或搜索空间配置,终端使用该BWP的带宽以及子载波间隔参数确定所述数据信道的资源配置,所调度的PDSCH资源位置从BWP上调度该PDSCH的CORESET的最小RB序号进行映射。如果终端没有收到用于该类型终端的BWP配置或该BWP上用于随机接入搜索空间的CORESET或搜索空间配置,终端使用CORESET0的带宽以及子载波间隔参数确定所述数据信道的资源位置,所调度的PDSCH资源位置从CORESET0的最小RB序号进行映射。
根据上述方法的一种或其组合,终端可以确定用于该类型终端的公共搜索空间的用于数据调度的DCI中频域指示域的宽度,从而可以确定DCI的大小。网络和终端根据确定的公共搜索空间DCI的大小,还可以用于确定用于用户搜索空间的DCI的大小。比如,当用于用户搜索空间的DCI与公共搜索空间的DCI大小不相等,并且总的DCI类型数量超过了终端的接收能力时,通过补零或截位的方式将部分DCI的大小对齐到所确定的公共搜索空间DCI的大小。相应地,根据补零或截位后所表示的数值可以确定相关调度PDSCH或PUSCH的资源位置信息。
[变形例]
下面,利用图2来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图2是表示本发明所涉及的用户设备UE的框图。
如图2所示,该用户设备UE20包括处理器201和存储器202。处理器201例如可以包括微处理器、微控制器、嵌入式处理器等。存储器202例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动 器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器202上存储有程序指令。该指令在由处理器201运行时,可以执行本发明详细描述的由用户设备执行的上述方法。
上文已经结合优选实施例对本发明的方法和涉及的设备进行了描述。本领域技术人员可以理解,上面示出的方法仅是示例性的,而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。上面示出的网络节点和用户设备可以包括更多的模块,例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的,本发明并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解,本发明的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如,上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现,这些器件包括但不限于:模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD),等等。
在本申请中,“基站”可以指具有较大发射功率和较广覆盖面积的移动通信数据和控制交换中心,包括资源分配调度、数据接收发送等功能。“用户设备”可以指用户移动终端,例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
此外,这里所公开的本发明的实施例可以在计算机程序产品上实现。更具体地,该计算机程序产品是如下的一种产品:具有计算机可读介质,计算机可读介质上编码有计算机程序逻辑,当在计算设备上执行时,该计算机程序逻辑提供相关的操作以实现本发明的上述技术方案。当在计算系统的至少一个处理器上执行时,计算机程序逻辑使得处理器执行本发明实施例所述的操作(方法)。本发明的这种设置典型地提供为设置或编码在例如光介质(例如CD-ROM)、软盘或硬盘等的计算机可读介 质上的软件、代码和/或其他数据结构、或者诸如一个或多个ROM或RAM或PROM芯片上的固件或微代码的其他介质、或一个或多个模块中的可下载的软件图像、共享数据库等。软件或固件或这种配置可安装在计算设备上,以使得计算设备中的一个或多个处理器执行本发明实施例所描述的技术方案。
此外,上述每个实施例中所使用的基站设备和终端设备的每个功能模块或各个特征可以由电路实现或执行,所述电路通常为一个或多个集成电路。设计用于执行本说明书中所描述的各个功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)或通用集成电路、现场可编程门阵列(FPGA)或其他可编程逻辑器件、分立的门或晶体管逻辑、或分立的硬件组件、或以上器件的任意组合。通用处理器可以是微处理器,或者所述处理器可以是现有的处理器、控制器、微控制器或状态机。上述通用处理器或每个电路可以由数字电路配置,或者可以由逻辑电路配置。此外,当由于半导体技术的进步,出现了能够替代目前的集成电路的先进技术时,本发明也可以使用利用该先进技术得到的集成电路。
尽管以上已经结合本发明的优选实施例示出了本发明,但是本领域的技术人员将会理解,在不脱离本发明的精神和范围的情况下,可以对本发明进行各种修改、替换和改变。因此,本发明不应由上述实施例来限定,而应由所附权利要求及其等价物来限定。

Claims (10)

  1. 一种由用户设备UE执行的方法,包括:
    接收网络针对所述UE的UE类型配置的带宽片段BWP配置信息,其中与所述BWP配置信息相对应的BWP与小区初始下行BWP不同;以及
    根据接收到的所述BWP配置信息,确定公共搜索空间中的物理下行控制信道PDCCH位置、用于数据调度的下行控制信息DCI中的频域指示域的宽度、数值、以及所调度的物理下行共享信道PDSCH资源的位置中的至少一个。
  2. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
  3. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
  4. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB或者使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
  5. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB或者使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
  6. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用CORESET0的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用该CORESET0的带宽,子载波间隔参数以及BWP的起始位置确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的 所有RB并且使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用所述BWP的带宽以及子载波间隔参数确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
  7. 根据权利要求1所述的方法,其中,
    如果与所述BWP配置信息相对应的所述BWP包含CORESET0的所有资源块RB,并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用相同的子载波间隔参数和循环前缀参数,所述UE使用所述BWP上与CORESET0大小相同的CORESET接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间上用于随机接入过程的PDCCH;
    如果与所述BWP配置信息相对应的所述BWP不包含CORESET0的所有RB并且使用不同的子载波间隔参数或不同的循环前缀参数,所述UE使用在所述BWP上的CORESET接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH。
  8. 根据权利要求1所述的方法,其中,
    如果所述UE收到网络针对所述UE配置的BWP,所述UE使用所述BWP的带宽确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个;
    如果所述UE没有收到网络针对所述UE配置的BWP,所述UE使用小区相关的初始BWP或CORESET0确定所述DCI中的频域指示域的宽度、数值以及所调度的PDSCH资源的位置中的至少一个。
  9. 根据权利要求1所述的方法,其中,
    如果所述UE收到网络针对所述UE配置的BWP,所述UE使用在所述BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH,不接收小区初始BWP上的随机接入搜索空间的PDCCH;
    如果所述UE没有收到网络针对所述UE配置的BWP,所述UE使用小区初始BWP上的随机接入搜索空间接收用于所述UE的随机接入过程的PDCCH。
  10. 一种用户设备,包括:
    处理器;以及
    存储器,存储有指令,
    其中,所述指令在由所述处理器运行时执行根据权利要求1至9中的任一项所述的方法。
PCT/CN2021/137411 2020-12-15 2021-12-13 由用户设备执行的方法以及用户设备 WO2022127732A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011479922.7A CN114640430A (zh) 2020-12-15 2020-12-15 由用户设备执行的方法以及用户设备
CN202011479922.7 2020-12-15

Publications (1)

Publication Number Publication Date
WO2022127732A1 true WO2022127732A1 (zh) 2022-06-23

Family

ID=81944376

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/137411 WO2022127732A1 (zh) 2020-12-15 2021-12-13 由用户设备执行的方法以及用户设备

Country Status (2)

Country Link
CN (1) CN114640430A (zh)
WO (1) WO2022127732A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024093878A1 (zh) * 2022-11-04 2024-05-10 华为技术有限公司 一种通信方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024020814A1 (en) * 2022-07-26 2024-02-01 Nec Corporation Method, device and computer readable medium for communications

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020017525A1 (ja) * 2018-07-17 2020-01-23 シャープ株式会社 基地局装置、端末装置、および、通信方法
WO2020026988A1 (ja) * 2018-07-31 2020-02-06 シャープ株式会社 基地局装置、端末装置、および、通信方法
CN111565461A (zh) * 2019-02-14 2020-08-21 夏普株式会社 由用户设备执行的方法以及用户设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020017525A1 (ja) * 2018-07-17 2020-01-23 シャープ株式会社 基地局装置、端末装置、および、通信方法
WO2020026988A1 (ja) * 2018-07-31 2020-02-06 シャープ株式会社 基地局装置、端末装置、および、通信方法
CN111565461A (zh) * 2019-02-14 2020-08-21 夏普株式会社 由用户设备执行的方法以及用户设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Summary of Bandwidth Part Remaining Issues", 3GPP DRAFT; R1-1805543_SUMMARY OF BWP REMAINING ISSUES_R1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 18 April 2018 (2018-04-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051435622 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024093878A1 (zh) * 2022-11-04 2024-05-10 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
CN114640430A (zh) 2022-06-17

Similar Documents

Publication Publication Date Title
US20220061066A1 (en) Cross Carrier Scheduling with Multiple Active Bandwidth Parts
JP7131559B2 (ja) 端末装置、及び方法
US8780833B2 (en) Control channel monitoring apparatus in multi-carrier system and method thereof
JP2021508201A (ja) Ss/pbchブロック周波数位置インディケーションのための方法及び装置
WO2019216430A1 (ja) 端末装置、基地局装置、および、通信方法
EP3860246A1 (en) Wireless resource exclusion
WO2018199240A1 (ja) 端末装置、基地局装置、および、通信方法
WO2022063025A1 (zh) 由用户设备执行的方法以及用户设备
WO2022028413A1 (zh) 由用户设备执行的方法以及用户设备
WO2022127732A1 (zh) 由用户设备执行的方法以及用户设备
JP2019004195A (ja) 端末装置、基地局装置、通信方法、および、集積回路
JPWO2019031135A1 (ja) 通信装置及び通信制御方法
WO2022068685A1 (zh) 由用户设备执行的方法以及用户设备
US20230276473A1 (en) Method performed by user equipment, and user equipment
WO2021190521A1 (zh) 由用户设备执行的方法以及用户设备
WO2020059419A1 (ja) 端末装置、基地局装置、および、通信方法
WO2023051677A1 (zh) 由用户设备执行的方法以及用户设备
WO2022152113A1 (zh) 由用户设备执行的方法以及用户设备
WO2021228136A1 (zh) 由用户设备执行的方法以及用户设备
WO2021228138A1 (zh) 由用户设备执行的方法以及用户设备
WO2022078377A1 (zh) 由用户设备执行的方法以及用户设备
WO2022022415A1 (zh) 由网络节点和用户设备执行的方法以及设备
WO2022267993A1 (zh) 由用户设备执行的方法以及用户设备
WO2024061282A1 (zh) 由用户设备执行的方法以及用户设备
WO2022188767A1 (zh) 由用户设备执行的方法以及用户设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21905661

Country of ref document: EP

Kind code of ref document: A1